Thanks for breaking this before customers do.
This is a quick guide to testing the AI&I ATLAS funnel — what to click, what should happen, and what to tell Lamar if something doesn't.
This is real. Not a test mode.
PayPal and crypto checkout are both fully live. If you complete a purchase, it's a real charge to your real card or wallet — and Lamar will actually ship you a real product. If you just want to click through without spending money, stop right before you hit the final "Pay" button. Either way is genuinely useful testing.
Go through it like a real customer would.
Do this on your phone first — that's where almost everyone will land. Try it on a laptop too if you get the chance.
How to know it actually worked.
After PayPal paymentA "Thank you" message appears on the page with an order number — that's the real confirmation. Lamar gets notified automatically with exactly what you ordered.
After crypto paymentTap the "send us a one-tap confirmation" link right after — that's a real step, not optional, since crypto doesn't auto-report the order details the way PayPal does.
Buttons and quantity steppersShould respond instantly to a tap — no lag, no double-triggering, minus button grays out at zero.
Don't report these — they're expected.
Crypto total doesn't auto-fill on NOWPayments' pageYou'll need to double-check the amount matches what the funnel showed before paying. This is a known limitation of the no-code crypto button, not a bug.
PayPal shows a white box even in dark modeThat's PayPal's own checkout window — it's not able to be re-themed, so it's framed deliberately instead of hidden.
The credits code field says "not found" if you don't have a real codeAsk Lamar for a test code first if you want to try that part.
If any of this happens, tell Lamar.
Wrong totalThe math doesn't add up, or Buy 2 Get 1 Free discounted the wrong item.
Checkout doesn't completePayPal or crypto errors out, hangs, or nothing happens when you tap Pay.
Layout looks brokenOverlapping text, content cut off, anything sitting under the header.
Anything that just feels wrongIf it's confusing to you, it'll be confusing to a real customer — say something, even if you're not sure it's a "real" bug.
Screenshot it, then send it over.
A screenshot plus one line — "tapped X, expected Y, got Z" — is genuinely all that's needed. Include what phone/browser you used if you can.