Help for owners
Customers paid on Stripe but no order appears on my site
Short answer
Stripe says you cannot rely on the page a customer lands on after paying, because they may never reach it. Orders must be created from Stripe's webhook events, and the code must cope with the same event arriving more than once. If the webhook failed or was slow, payments exist in Stripe with no order on your side.
Does this sound like your situation?
- A customer shows a receipt but I have no order for it.
- Stripe's payment list and my orders list do not match.
- Orders only appear if the customer waits on the thank-you page.
- It happens with bank transfers or other slow payment methods.
- Some orders appear twice.
Why does this happen?
The order is created only when the customer returns
Stripe says you cannot rely on triggering fulfillment from the landing page alone, because a customer can pay and then lose their connection before the page loads. A webhook is required so that every payment is processed.
Confirmed by docs.stripe.com
The webhook is failing or timing out
Stripe says an endpoint must return a success code quickly, before any complex logic, and lists common failures such as redirects, 4xx or 5xx responses, TLS errors and timeouts. An endpoint that does the slow work first can fail on a busy day.
Confirmed by docs.stripe.comTechnical detail: Stripe webhook: no signatures found matching the expected signature
The payment method is not instant
Some payment methods, such as bank debits and transfers, do not confirm at once. Stripe sends a separate checkout.session.async_payment_succeeded event when the payment succeeds later, and a site that only listens for the first event misses it.
Confirmed by docs.stripe.com
The same event runs twice, or in the wrong order
Stripe says endpoints may receive the same event more than once and that events can arrive in any order. Without a record of processed event IDs you can get duplicate orders, or an order built from incomplete data.
Confirmed by docs.stripe.com
The event was sent, then retries ran out
In live mode Stripe retries for up to three days. If the endpoint was broken for longer, the event has to be resent by hand: from the Dashboard for up to 15 days, or with the CLI for up to 30 days after it was created.
Confirmed by docs.stripe.com
What can I do about it today?
- List the payments with no orderExport recent payments from Stripe and match them against your orders. Write down the missing ones with date, amount and customer email.
- Open the failing events in StripeIn Workbench, Webhooks, open your endpoint and read Event deliveries. The response code shows which of the failure types you have.
- Do not create the orders by hand yetCreating an order manually can trigger a second email or shipment later when the event is resent. Decide the method first.
- Do not refund as a first reactionThe customer has paid for something you can still deliver. Refunds are for orders you cannot fulfil.
- Tell the customer you have their paymentA short message saying the order is being processed keeps trust while the fix is made.
When should I bring someone in?
- Several customers were charged and have nothing.
- The webhook has been failing for more than a few days.
- Your system sends goods or access automatically and a missing order means something real is missing.
How do I handle it?
- Reconcile firstI produce a list of payments without orders so nothing is guessed.
- Fix the receiverThe webhook returns success fast, hands the work to a queue, and records each event ID so duplicates do nothing.
- Handle slow payment methodsThe site listens for delayed success and failure events as well as the first one.
- Resend and verifyMissed events are resent from Stripe and each order is checked against its payment.
- Keep a daily checkA scheduled comparison of Stripe payments and orders catches the next gap early.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is the customer charged twice if I resend an event?
No, resending only repeats Stripe's message to your site. The risk is your site acting twice, which is why the handler has to recognise events it has already processed.
Why does it work in testing?
A test checkout is slow and one at a time, and you wait on the landing page. A real day has bursts, closed tabs and slower payment methods.
Can I just use the thank-you page?
Stripe says no. It recommends the page for the customer's experience and webhooks to make sure fulfillment happens for every payment.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.
For your developer: the technical fixes
Webhook signature verification failed. Err: No signatures found matching the expected signature for payload.Stripe webhook: no signatures found matching the expected signatureFatal error: Maximum execution time of 30 seconds exceeded in /var/www/app/import.php on line 42PHP stops the script after 30 seconds504 Gateway Time-outnginx gives up waiting for the app and returns 504