By platform
Checkout Stripe not working: the handoff
The Buy button works for you, then a buyer on a phone gets an error on your site or lands on a payment page that does not offer their card. Simulated buyers press Buy and report whether the page moved, and where it stopped.
Why is checkout with Stripe not working for buyers?
Stripe Checkout works in two hops: your site asks Stripe to set up a payment page, then the buyer's browser moves to that page. A failure happens either before the move, on your site, or after it, on the payment page, and the address bar shows which side the buyer is on. A simulated test presses Buy the way a buyer would and reports whether the address changed, and what error or failed request appeared on that step.
What this looks like in a report
“I pressed Buy and the button went gray, then nothing happened. Nothing on the screen says why, and the address did not change, so I cannot tell if it was my phone or the shop.”
The fix. Log the error from the session request on your server, then check that the live keys and the currency match the price on the page. Press Buy on a phone in a private window after each change, and confirm the address moves to the payment page before you call the fix done.
An illustration. Run a test to see your own.See a real sample report
Your test ran with settings the live site may not share
You pressed Buy on your own store, signed in, with the keys and currency already in place, and reached a payment page that looked right. A buyer on another device, in another country or in a different browser may see something else. Their press can fail on your site before anything moves, or the redirect can open a payment page without the methods their country uses. A live site built with test keys sends buyers to a page that will not take a real card. None of that shows when you are the only person pressing the button.
- Press Buy on a phone in a private window. Does the page change, or does an error appear on your site?
- Watch the address bar after Buy. Does it move to a Stripe address, or stay on your own domain?
- On the payment page, compare the currency and the total with the item price on your site.
- Read the payment methods the page lists for the buyer's country. Is the card option there?
- Confirm the live site uses live keys before you treat the payment page as the final one.
Two hops, and which one failed
Your site first asks Stripe to create a checkout session for the item the buyer chose. Only when that succeeds does the buyer's browser move to the page Stripe returns. If the session request fails, the buyer never leaves your domain, and the most they see is a grey button, an error line or nothing. If the session is created, the address changes and the failure, if any, is on the payment page.
This is the first thing to check, because it decides who you need to fix it with. A buyer who stays on your domain points you at your server code and your keys. A buyer who moves to a Stripe address and sees an error there points you at the session settings, such as the currency, the line items or the payment methods you enabled.
The payment page shows what the account allows for that buyer
The payment page lists the methods that suit the buyer's country and currency, and it only lists the ones your account has turned on. A buyer in another country can reach the page and find no card option, or find a method that does not match the total on your site. Check the currency on the page against the price you show, because a mismatch makes a buyer doubt the whole purchase. Then check the country the buyer used, because the methods depend on it.
Test keys on a live site send buyers to a page that refuses cards
A site set up with test keys still produces a checkout that looks finished. The buyer can press Buy, reach a payment page and find that it will not take a real card. This tends to show up after a launch, when the keys used during setup were never switched. Confirm which keys the live site uses in your own account and server settings, and treat any payment page reached with test settings as a failed launch, not a passed test.
Mimiq is independent and not affiliated with the platforms it names. Names belong to their owners.
What you get with Mimiq
- 01
Run it by hand, or on every pull request
Paste a link and a task in the app and watch the visitors work. Or run them on every preview deploy: the GitHub Action comments on the pull request, any other CI can call the MCP endpoint, and your coding agent can run it too.
- 02
Bugs and usability problems in one report
The browser records errors and failed or slow requests on the step they happened. The visitors say where the wording or the steps confused them, and where they left.
- 03
Visitors that behave like your audience
Each visitor is a different profile with a reason to be there, matched to who the page is for, described by you, or built from your own customers.
- 04
A prompt to fix each problem
Every problem comes with a fix to paste into Cursor, Claude Code, Lovable or any coding agent, and one prompt hands over the top problems at once. Then send the same visitors through again.
- 05
Follow every visitor
See each visitor's whole path, step by step with screenshots, and what it was thinking at every step. Ask any visitor a question.
The browser records relevant JavaScript errors and failed or slow app requests encountered during the run, attached to the step where they occurred. The visitors are simulated: they find problems, they do not predict how many real people will convert.
A new currency or payment method can break the handoff for one country
A new currency, a new payment method or a change to product prices can make the payment page refuse one group of buyers while your own test still passes. After each change, press Buy on a phone in a private window and read where the address ends up. Keep the last address you saw, so a change that moves it stands out.
Starter
Try it on one launch
About 4 tests of 5 visitors
- Visitors on your landing page, signup and checkout
- Where they left and why, with a fix to copy for each problem
- Run it in the app or on every pull request
- Ask any visitor a question, included
- Test accounts and protected previews
Builder
Test every build
About 20 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Pro
Test every release, as a team
About 60 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Scale
Test at scale, every day
About 240 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Priority support
- Cancel anytime
Questions
Can a simulated buyer pay on the payment page?
No. The run goes up to the payment step and stops there, because a simulated buyer cannot pay with a real card. It can show the page, the total and the methods listed, but not whether a card is accepted.
Will the run show a failed request when Buy is pressed?
It can. The browser records failed app requests and relevant JavaScript errors on the step where they happened, so a failed session request to your own site shows up on that step. The result of the payment itself comes after the payment step, which the run does not reach.
Does a test show how many buyers finish paying?
No. It does not predict how many buyers finish. It shows whether the Buy press reached a payment page for each simulated buyer, and where any stop happened. Take completion numbers from your payment provider's records and your own orders.
Can the run tell me whether my keys are test or live?
Not directly. It shows what the buyer saw on the payment page. If that page refuses real cards or reads like a test page, check which keys your live site uses, in your account settings and your server configuration.
What should I check after the payment page loads?
Check the total, the currency and the delivery options against the item, then confirm where the buyer is sent after paying. Run one payment yourself with the test setup your provider offers, and confirm the buyer lands on your thank-you screen.
Keep reading
Send visitors and see what breaks first.
Your first test is free: sign in with Google and it starts right away. Last checked 2026-11-02.