Checkout monitoring that gets as far as the payment step
A checkout has more ways to fail quietly than any other flow on a site, and almost none of them show up as downtime. Checkout monitoring means driving add-to-cart, the cart, the details step and the payment step in a real browser, on a schedule, so a broken checkout is something you find rather than something a customer reports.
Where a checkout stops paying
Add to cart does nothing
The button responds, the cart count never changes, and the product page looks exactly as healthy as it did yesterday.
The cart empties between steps
A session or cookie change drops the basket on the way to checkout. Every individual page loads fine.
The discount field rejects everything
A campaign code that has just gone out to the mailing list returns an error, on a page that is otherwise working.
The payment step never mounts
The provider’s frame fails to load and the final step is blank. The server is up, the order is not.
What a checkout check walks through
The same session, start to finish, asserting on the site’s own network calls as well as on what is on screen. That is how it catches a checkout that renders perfectly while the API behind it fails.
- 1Open a product page and confirm the thing being sold is actually there.
- 2Add it to the cart, and check the cart agrees that it happened.
- 3Open the cart and continue to checkout.
- 4Fill in the details the checkout asks for.
- 5Reach the payment step.
It stops at the payment step. Nothing is ever purchased, no order is created, and no card is used. Reaching the step proves the path to it, which is the part that breaks.
What you get when it fails
- The step that failed and what was on screen when it did.
- The failed request behind it, when the break is in the API rather than the page.
- A screenshot filmstrip of the session, kept for 7 days on Basic, 30 on Pro and 90 on Enterprise.
- A plain-language line for the report: what a customer would have experienced, without the word “endpoint” in it.
Questions
- Does it place a real order?
- No. The journey reaches the payment step and stops. No order is created and no payment details are entered.
- Does it work with the tool the site is built on?
- It drives whatever the site renders in a browser, so the platform and the plugin do not have to be ones we have integrated with. Nothing is installed on the site, which also means an update to the site cannot break the monitoring and the monitoring cannot break the site.
- How often does the check run?
- Uptime checks run every minute on every site and every plan. The browser journey runs as often as every 30 minutes on Basic, every 10 minutes on Pro and every 5 minutes on Enterprise. A full browser session costs more to run than a request, which is why it is the part that is metered.
We’ll set the first check up with you.
Request a demo and we’ll configure a workspace, add a site you care about, and run this check on it.