By platform

Test Stripe payment link: check before you share

The link opens and looks right, but you have not seen what a buyer sees after paying. Mimiq runs a simulated visitor through the link and shows what they saw before the card step.

5 visitors try to .
First test free with an accountRun it from your coding agent

How do I test a Stripe payment link before sharing it?

Create the link in test mode first, open it in a private window, and read the price, the fields and the after-payment page before you pay anything. In test mode the payment page takes only the test card numbers Stripe publishes, so a test payment moves no money. Once the test passes, create the link again in live mode and share only that one. A simulated visitor shows what the buyer sees up to the card step.

What this looks like in a report

Who
Oluwaseun, buying a set of three greeting cards for her mother's birthday
How they arrived
Clicked a payment link in a newsletter on her phone
Where they stopped
Payment page, after entering her email

“The price matches what the newsletter said, but I am not sure this is the real link. If I pay and the thank you page is broken, I will not know whether the order went through.”

The fix. Create the link again in live mode, set the after-payment page to your live thank you page, and open that page in a private window once after a test payment. Share only the live link in the newsletter.

An illustration. Run a test to see your own.See a real sample report

A payment link proves nothing until the page after payment loads

A Stripe payment link is a hosted page with the price, the fields a buyer fills in and the card step already set. The mode decides whether the link takes real cards: a link made in test mode refuses them, and a live link charges whoever pays. The after-payment setting decides what the buyer sees next. A redirect to a page that was renamed or moved leaves a buyer who has just paid on an error screen.

  • Confirm the dashboard's mode switch says test while you test, and live only for the link you share.
  • Open the link in a private window and read the price, the currency and the quantity before you go on.
  • Open the after-payment address on its own and confirm it loads without a login.

How it works

  1. 01

    Create the link in test mode

    Turn on test mode in the Stripe dashboard, create the payment link there, and set the price, the quantity and only the fields you need.

  2. 02

    Point the link at a working after-payment page

    Set the link to send the buyer to a thank you page on your site that loads without a login. Open that address in a private window and confirm it works before you go further.

  3. 03

    Run the test link through a simulated visitor

    Paste the test link and the task into Mimiq and have the visitor reach the payment step. Read the screenshot at the card step and fix any price, field or wording a buyer would question, then run it again.

  4. 04

    Create the live link and share only that one

    Turn test mode off, create the same link again with the same settings, and share only that one. Label the test link as test in your notes.

What a buyer sees on the hosted page, in order

A payment link opens a page hosted by Stripe, not by your store. The buyer sees the product name, the price and a quantity field, then the fields you chose to collect, such as an email, a shipping address or a tax ID. The card step comes after those fields, and a finished payment returns the buyer to the after-payment screen you set. A broken after-payment address can leave a buyer who has paid on an error screen.

Test mode and live mode make two links, and only one charges

The mode is set in the Stripe dashboard, and it changes what the link does. In test mode, the payment page accepts the test card numbers Stripe publishes and refuses real cards, so no money moves. In live mode, the same kind of page charges whoever pays. A buyer who receives a test link gets a payment page like any other, and a real card is refused there, which reads as a broken store. Check the mode before you copy the link.

The after-payment page is the screen most owners never open

When a payment succeeds, the buyer goes to the after-payment page you set in the link's settings, or to a default confirmation screen if you set none. A link can point at a thank you page that was renamed, deleted or moved behind a login, and then the buyer sees an error after paying. Open that address in a private window after a test payment and read it as a buyer would, since the buyer may never write to you about it.

What the simulated visit covers before the card step

A simulated visitor opens the link from the place you will share it, reads the page, fills in the fields the link asks for, and goes up to the card step. The run records a screenshot at each step, the price and fields as the visitor saw them, and any script error or failed request recorded there. If the after-payment address matters to you, the run does not follow the visitor past the card step, so check that address yourself.

The run cannot finish a payment, and it cannot tell you whether the money would reach your account. Finish one test payment yourself in test mode, then send the simulated visitor through the live link only after your own check passes. Keep the same visitor and the same settings each time, so the screenshots can be compared after each change.

Mimiq is independent and not affiliated with the platforms it names. Names belong to their owners.

What you get with Mimiq

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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 field, price or redirect can change what buyers see next

Each time you create a link, change the after-payment page, or add a shipping or tax field, the buyer's path changes. A link that worked last month can lead to a dead thank you page after someone moves it. Run the same visitor again after each change, so the screen after payment is checked every time.

Starter

Try it on one launch

$9 once
120 credits, never expire

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
Buy 120 credits

Builder

Test every build

$19 a month
500 credits every month

About 20 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Builder

Pro

Test every release, as a team

$49 a month
1,500 credits every month

About 60 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Pro

Scale

Test at scale, every day

$149 a month
6,000 credits every month

About 240 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Priority support
  • Cancel anytime
Choose Scale
$0for your first test, with a free account (Google sign-in, no card). It includes 50 credits, enough for 10 visitors. After that a visitor uses 5 credits, and packs start at $9 for 120 credits.
See a sample report

Questions

Will a test payment link charge my real card?

No. A link made in test mode takes only the test card numbers Stripe publishes for test mode, and a real card is refused. Live charges happen only on a link made in live mode. Check the mode before you share anything, because the link itself can look the same in either mode.

Can a simulated visitor complete the payment on my link?

No. The visitor fills in the email, address and other fields, then goes up to the card step and stops, because visitors cannot pay with a real card. To finish a payment, use test mode on your own account with the published test card numbers, then check the after-payment page yourself.

Does the test show whether I will get paid?

No. It shows whether the link opens, what the buyer sees before the card step, and whether the after-payment address loads. It does not tell you how many buyers will pay, and it does not check your bank account or payout settings.

Should I send the test link to customers to see how they react?

Not to customers. A test link sends real buyers to a page that refuses their cards, which reads as a broken store. Keep test links for your own checks, and send buyers the live link once the after-payment page has loaded for you.

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.

5 visitors try to .