An email arrives on Monday with a screenshot attached. One hundred and eighty four dollars, Sunday evening, your store's name on the line item. She never got a confirmation and she would like to know where her order is.
You search Orders by her email. Nothing. By the amount. Nothing. Then you find her in Abandoned checkouts, cart intact, and you open PayPal and there it is: one hundred and eighty four dollars, settled, two days ago.
The money is real. The order does not exist. And there is no screen in Shopify where those two facts meet, which is why the person who found this was your customer.
The short answer
A Shopify order is created when your store is told the payment succeeded, not when the money moves. On any provider that redirects the customer away to pay, those are two events with a network between them, and the network is the part that breaks. Shopify files the attempt as an abandoned checkout and the money stays in the gateway.
Nothing joins the two sides. Payouts only show money Shopify knows about, so money it never saw cannot appear there, and your gateway has no idea which of its transactions became orders. There is no report for cash received with no order, which is why the customer is always the one who tells you.
The fix is a reconciliation, run daily rather than when somebody complains: settled gateway transactions against Shopify orders for the same window, matched on amount, email and time. Then one decision per unmatched row, and the first thing you check is whether the money actually settled or is a hold that will expire by itself.
The order and the money are two different events
Shopify's own documentation is clear about the mechanism, once you go looking for it. A payment that fails at checkout usually does not create an order, and the attempt is recorded as an abandoned checkout instead. For a provider that redirects the customer off your store to pay, the help page is more specific still: if the customer leaves the provider's page, closes the tab, or uses the back button during the redirect, the payment might fail, and the charge may still complete on the provider's side without an order being created.
Read that last clause slowly, because it is the whole article. Shopify is telling you that the money can move while the order never exists, and that it will not know.
Two neighboring cases look the same to the customer and are not the same at all. If they abandon a 3D Secure challenge, no charge is made. If Shopify Payments blocks the attempt for fraud, the timeline reads blocked due to high risk of fraud, no order is created and no payment is captured. In both of those, nothing has gone anywhere. The one that costs you money is the third case, where the gateway took the payment and Shopify was never told.
One timing detail matters when you go hunting. A checkout only counts as abandoned after it has been incomplete for more than ten minutes, so a payment attempt from the last few minutes will not be in the list yet. If a customer messages you within the hour, look again later before you conclude the checkout never happened.
Pending hold or settled money, and why nothing else matters first
Every one of these cases splits in two, and almost every wasted hour comes from working the wrong half.
A pending authorization is a hold the bank placed before the sale completed. Nothing was captured, no money reached you, and the hold falls off on the issuer's own schedule, which merchants in the community threads put at anywhere from a couple of hours to about thirty days. You cannot accelerate it and neither can Shopify. The correct response is a clear explanation and a fresh checkout link, not a draft order.
Settled money is the other half. It is in your gateway balance, it is yours, and there is nothing in Shopify that accounts for it. That row needs an order built against it or the money sent back, and until one of those happens it is sitting outside your books.
There is a particular way to end up in the pending half that catches people out. With Shopify Payments, the bank pre-authorizes the funds before the postal code check runs, so a failed postal code check leaves a pending charge on the customer's statement while no order is ever created. A merchant in that thread said this happens frequently in their store, that they are left explaining pending charges to customers, and asked whether switching the check off was the only way to stop it and whether that would raise their fraud exposure. The question has been sitting there unanswered since May 2023.
Five years of the same thread, and no native answer
The public record on this is unusually consistent, which is a good signal that the problem is structural rather than anyone's misconfiguration.
In August 2021 a Shopify Plus merchant's finance team found a customer charged for a product he never received, with the checkout sitting in Abandoned checkouts. In February 2022 a merchant noticed two PayPal payments from one customer and no order for either. In April 2022 a checkout logged Failed, response code 502, Bad Gateway while the card went through, and another merchant reported the identical thing the same afternoon with an Authorize.net transaction already settled on the back end. Four months later a third merchant had two PayPal cases in two months and wrote that it is their system causing it. In October 2022 someone asked the thread what ended up happening with these. Nobody replied.
In September 2022 a Shop Pay Installments payment debited the customer's bank with no confirmation email and no thank you page. The replies on that thread are the most useful thing in the whole record, because one merchant did the diagnosis nobody else did: both of their affected customers had checked out on phones, their mobile page speed was poor, and they concluded that timeouts and mid payment refreshes were doing it.
Then July 2025, which is the one worth keeping. A store's first sale, 935 dollars on PayPal Pay in 4, the customer charged twice, never reaching the confirmation screen, the cart filed as abandoned. The merchant's own words were that the website will not go past the pay now screen, and that they did not know whether the problem was on their end or hers. Their fifty cent test orders had both worked. One reply, from another merchant rather than Shopify. No resolution recorded.
Shopify has since written a genuinely good help page for this. Check Orders for a pending or partially paid order on that email, open the abandoned checkout and read its timeline, decide whether the statement charge is pending or posted, contact the provider with the email and approximate time, and for a captured payment either reverse it and have the customer reorder or create a draft order and mark it paid. Every step of that is right. Not one of those steps finds the case. All of them start after a customer has written to you.
What the admin knows, and the one thing it cannot know
On the order side, Shopify is complete. The abandoned checkout holds the
email, the cart, the total and a payment event history that tells you
exactly which failure you are looking at. The
Abandonment
object in the Admin API goes further and carries
customerHasNoOrderSinceAbandonment and
customerHasNoDraftOrderSinceAbandonment, and the
abandonedCheckouts query filters on creation date, open or
closed status and recovery state.
So Shopify will tell you whether this customer ever came back and bought. It will not tell you whether their money moved, because it never saw the money. That is the gap in one sentence, and it is why no setting inside the admin closes it.
Shopify Flow inherits the same ceiling. It has an abandoned checkout trigger and you can tag or alert on high value carts with it, which is worth twenty minutes. But most abandoned checkouts are ordinary browsing, so an alert on all of them becomes a channel nobody opens, and the three that matter this month look exactly like the three thousand that do not. The fact that separates them lives in the gateway. Flow earns its keep at the other end of this, once a draft order exists and needs tagging and routing like any other order.
What it actually costs you
Nobody publishes a rate for this, and the absence is part of the point. You cannot measure something no system counts, so every merchant estimates from the handful of cases a customer happened to report.
What you can price is one case. Take the 935 dollar order from that July 2025 thread. If the money settled and you never found it, you are holding cash against no order, so the goods were never picked, the revenue never hit your reports, your inventory is wrong by whatever was in that cart, and your accounting has a deposit it cannot explain. If the money did not settle, you lost a 935 dollar sale and a first time customer on their first attempt, and you will never see that in your conversion numbers because, as far as your analytics are concerned, she simply abandoned her cart.
Then count the customer's three options, because she picks one of them whether you act or not. She emails you, which costs you a ticket. She opens a dispute with the wallet, which costs you a fee and a mark against your account. Or she calls her bank, and you are now handling a chargeback for an order your own admin has no record of, which is the hardest possible version of that argument to win.
The clustering is the real finding though. Two separate merchants in those threads traced their cases to slow mobile checkout. If yours cluster on one wallet, one country or one hour of the day, you do not have a reconciliation problem that needs a weekly list. You have a checkout problem, and the list is just how you find it.
What the automation actually has to do
As a Dugong playbook, in plain prose:
# trigger
Daily pass over gateway settlements,
plus any customer message about a
charge
# steps
1. Pull both sides for the same
window
2. Match on amount, email and
timestamp
3. Split the pending holds from
the settled money
4. Read the checkout timeline
before you decide
5. Create the order or send the
money back
6. Answer the customer the same
day
7. Report the pattern, not just
the case
Step one is both sides, every gateway. Settled transactions from each provider you accept, and Shopify orders plus draft orders for the same window, because the draft orders are the cases you already fixed by hand and you do not want to pay a customer twice for your own tidying up.
Step two is imprecise on purpose. Amount is the strong key, email is usually present on both sides and sometimes differs by a typo, and the gateway stamps when it settled rather than when she paid, so the time needs a tolerance of hours rather than minutes. Shipping, tax rounding and multi-currency mean the amounts do not always agree to the cent. Match on a band, and send anything that does not resolve to a person instead of closing it quietly.
Step three is the split that decides the whole case, and the direction of the error matters. Treat a pending hold as settled and you build an order against money you never received. Treat settled money as a hold and you leave your own cash with the gateway and a customer with nothing.
Step four is the reading step, and it is the one that was not practical by hand at any real volume. Open the abandoned checkout's payment event history. A 502, a timeout, a postal code mismatch and an abandoned 3D Secure challenge each mean something different, each implies a different next action, and each needs a different sentence to the customer. Reading an event log next to her email and deciding which story they tell is ordinary work for a model and tedious work for a human at two in the afternoon.
Step five is the action, and both branches should be reversible and logged against the checkout. Settled money with no order becomes a draft order, rebuilt from the cart, marked paid, fulfilled. Money you do not want, because she already reordered or was charged twice, gets refunded in the gateway and said out loud.
Step six is speed over wording. She noticed before you did, so the clock started without you. A same day reply that names the amount, says exactly where the money is right now, and states what happens next is most of the difference between a ticket and a dispute.
Step seven is the weekly view, grouped by gateway, device, country and hour. One row per incident is a chore. The cluster is a diagnosis, and the diagnosis is usually about your checkout rather than your bookkeeping.
Do this before you close the laptop
Three things, about twenty minutes, no tooling required.
Open each gateway you accept, filter to settled transactions for the last thirty days, and sort by amount. Do the same for your Shopify orders. Read down for any settled transaction you cannot find an order against. Most merchants doing this for the first time find at least one, and the ones who find none have just bought themselves a baseline.
Then open Orders and Abandoned checkouts and read the timeline on any checkout above your average order value. You are looking for a payment event, not a browsing exit. Those two things sit in the same list and mean completely different things.
Last, search your support inbox for charged and for confirmation. If a customer raised this three months ago and you could not find an order at the time, the gateway record is almost certainly still there.
If you run a store with a version of this story, the PayPal transaction
with no order behind it, the 502 on a checkout that still took the money,
the customer who sent you a screenshot you could not match to anything,
the inbox is open: field-notes@dugong.live. We are
collecting case studies for the next issue.