By platform
Afterpay not showing up at checkout: the total
The product page says installments are available, then the option is missing at payment, and the buyer assumes the store has none. Simulated buyers try three carts and two addresses to show which one hides it.
Why is Afterpay not showing up at my checkout?
Installment options at checkout often depend on the cart: the total has to fall inside a range that the provider and the store set, and the buyer's address has to be somewhere the option covers. A product page message does not mean the option will show at payment. To find the cause, test one cart under the range, one over it and one with an address in another country. A simulated test runs those carts and reports the payment screen each one reached.
What this looks like in a report
“The product page said I could split the price, and now there is only a card box. I added a lamp, so the total went up, and I do not know if the total or my address removed it.”
The fix. Show the installment option only when the cart and address qualify, and say on the product page when the cart or address decides it. Test a cart under the limit, one over it and one with an address in another country, and confirm each shows the option you expect.
An illustration. Run a test to see your own.See a real sample report
The product page promised it, and the payment step never offered it
A buyer sees an installment message beside the product, adds the item, and expects the same option at payment. Instead the payment step lists cards and nothing else. The buyer cannot see that a cart rule or a delivery address has hidden the option, so they assume the store does not offer it. They pay in full, or they leave to find a store that does. You tested with one cart and your own address, which probably passed every rule, so the missing option never appeared in your own test.
- Read the installment message on the product page. Does the payment step offer the same option for this cart?
- Add a cart below the store's minimum, then one above it. Does the option appear only in the second?
- Enter a delivery address in a country you rarely ship to. Does the option disappear?
- Remove one item to change the total. Does the option come back at the payment step?
The product page message is not the payment step
The installment message on a product page is a general offer, written before anyone has a cart. It knows the price of one item, and nothing about the rest of the cart, the delivery address or the payment method the buyer will choose. A buyer reads it as a promise for the whole purchase. Check the message against the payment screen for the same item, and write down whether the two agree. If they do not agree, the buyer has already been told something the checkout will not do.
The cart total and the address decide the option
Installment providers usually set a range for an order: a lowest and a highest total it will cover. A cart below the range hides the option, and so does a cart above it. The delivery address can hide it as well, because the option may only cover some countries. None of these rules shows on the page, so a buyer sees a missing option and a total that looks reasonable. Read the limits from your payment settings, then compare each cart you test with those limits, not with a guess.
A three-cart test shows which rule is hiding the option
Run the same item through three carts: one below the range, one inside it, and one above it. Then run the inside cart again with a delivery address in a country you rarely ship to. If the option shows only on the inside cart, the total is the rule at work. If it disappears only with the foreign address, the address is the rule. If it is missing on every cart, the setting that enables the option is the place to look, not the cart. A simulated test runs these carts and reports the payment screen each one reached.
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 price change or a new country can move a cart out of range
A price change, a new shipping country or a new excluded product can move a cart inside or outside the option's range without any change to the checkout itself. After each of those changes, run the three-cart test again and compare it with your last run. A buyer who saw the option last month should still see it this month.
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 with an installment option?
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 whether the option is listed on that screen, but it cannot complete an installment plan.
Does a missing option mean I lose sales?
Not by itself. A buyer who sees no option may pay in full, leave or pick another method. The run does not predict sales. Take the effect from your own checkout data, and use the run to find which carts lose the option.
Can the run tell me the exact limits?
No. It shows the carts and addresses you test and what the payment step showed for each one. Read the limits from your payment settings, then compare them with the carts that lost the option.
Why does the option show in a test but not for a buyer?
A buyer's cart, address or country can differ from the one you tested. Test the addresses your buyers actually use and the carts closest to a typical order, so the test matches the buyer you are trying to reach.
Should I show the installment message on the product page at all?
Show it when most buyers can reach the option at payment, or say on the page which carts and addresses qualify. A message that disappears at payment costs more trust than no message at all, because the buyer feels misled.
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.