What happens if checkout takes too long to respond?
The page stops waiting after 15 seconds and tells you it could not confirm whether a session was created. Check the page before retrying.
Check the review date and linked sources for context. Live availability, prices and record coverage can vary by VIN, source, jurisdiction and time.
Your browser gives the checkout request 15 seconds, then stops waiting and shows “Secure checkout took too long to respond. We could not confirm whether a checkout session was created; check this page before trying again.” The wording is deliberate: a timeout proves nothing was confirmed, not that nothing happened. No report exists yet either way, because a report is created only after payment is confirmed.
- The 15-second cut-off happens in your browser, so the server may still have finished the request.
- Pressing the button again without reloading first reuses the same request identifier, so an order that already holds a usable payment session hands back that same payment link; if the earlier attempt cannot be resumed the page quietly starts a fresh order, as it also does after a reload.
- No report is created until payment is confirmed, so a timeout cannot leave you with a half-delivered purchase.
Why the message refuses to guess
The checkout request is sent with a 15-second abort timer. When that fires, the browser has given up listening — it has not cancelled anything on the server, and it cannot know whether the payment provider created a session in the meantime. Rather than claim a failure it cannot prove, the order review page says it could not confirm whether a checkout session was created and asks you to check the page before trying again. A shorter version of the same warning appears on the buy buttons elsewhere on the site.
The server side is built for exactly this ambiguity. The order is marked as dispatched before the outbound call, deliberately without any expiry, so that a timeout or a lost response can never quietly discard a payment session that may exist.
What to do next
Reload the order review page and continue from there. Nothing is emailed until a report is ready, so there is no checkout email to look for, and My Reports lists an order only once a payment has completed — if a charge appears on your statement with no order behind it, contact support with the time of the attempt.
Pressing the button again without reloading hands back an existing payment session: your browser keeps the same request identifier only while that page stays loaded, so if a session was already created the server returns that same payment link instead of starting a second order. Once you have reloaded, the button starts a genuinely new order — which is why checking My Reports or your email for the earlier one comes first.
Steps
- Reload the order review page.
- Open My Reports to see whether a payment actually completed.
- Press the payment button again only after checking — on a reloaded page it starts a new order.
- Contact support with the time of the attempt if a charge appears but no order does.
What this does not cover
- A timeout is genuinely ambiguous: the current wording promises only that nothing was confirmed, not that nothing was created.
- Every attempt, including a timed-out one, counts toward the limit of ten checkout starts per hour.
- If a different failure follows the retry, the page may say “Checkout is temporarily unavailable. Please check your account before trying again.” — that is the same instruction, not a new problem.
Sources reviewed
Open the underlying public source and verify that its scope matches the question you are asking.
Frequently asked questions
Does a timeout mean I was charged?
No. A payment is taken on the provider's secure page, which you had not reached when the request timed out. If a charge appears on your statement without a matching order, contact support with the time of the attempt.
Will pressing the button again create two orders?
It can. The request identifier is kept while that page stays loaded, so an order that can still be resumed returns its existing payment session rather than a second order. But a timed-out attempt often leaves an order that cannot be resumed, and the page then silently starts a genuinely new one — as it also does after a reload. Check My Reports first; a duplicate order left unpaid is never charged and never delivered.
Is my VIN lost when this happens?
No. The order review page keeps the VIN in its address, so reloading brings back the same confirmed vehicle.