Checkout journey
A “Pay” button that does nothing doesn't return an error
The page answers 200, the server is fine, the certificate is valid. And nobody can pay. PostShip walks the funnel in order, step by step, on every deploy.
“We lost a weekend of sales because a script stopped loading.”
Checkout is the one page of your site that almost never breaks loudly.
- steps per funnel, or more
- 4
- passes per deploy
- 3
- charged: we stop before
- €0
- alert, with the step that blocks
- 1
steps per funnel, or more
passes per deploy
charged: we stop before
alert, with the step that blocks
How it works
01You describe the path
The pages in the order a customer sees them — pricing, cart, address, payment — and what must be on them: a price, a button, a form.
02PostShip replays it, without paying
Each step is loaded as a browser would: the HTML, the scripts, the button.
03The blocking step is named
The alert doesn't say “the funnel is broken”: it says “step 4, Stripe.js missing” or “step 2, the total is no longer displayed”.
04On every deploy, then every five minutes
The funnel is replayed as soon as you go live, then at T+2 and T+8 minutes, and then at the plan's pace.
What we're often asked
Will a fake order show up in Stripe?
No. The journey stops at checking the button and the payment script; nothing is submitted, no payment session is created. Your statistics stay clean.
My funnel requires logging in.
You can provide a test account: PostShip logs in with it, like a customer, and the journey starts after that. The credentials are encrypted and never logged.
I don't use Stripe.
The principle is the same for PayPal, Mollie, Adyen or an in-house provider: we check that the expected script is loaded and that the final button is active. You tell us what to look for.
Paste your site's URL. PostShip checks it in front of you, no account and no card.