Shopify Admin
The Buyer Says They Disputed a Charge, but Shopify Shows Nothing: What to Check
If a buyer says they disputed a charge but Shopify shows no case, first verify the order, original processor, reported event, and your native access. The absence of a visible chargeback is an observation about the view you checked, not proof that the buyer’s statement is false.
Shopify notes that third-party providers can use different dispute workflows in its chargeback process guidance. A payment concern can therefore be real while the expected Shopify case is absent from the place you searched.
Match the buyer’s statement to a specific payment
Identify the store and order the buyer means. Compare the purchase date, amount, currency, and existing order reference. If the customer has several similar purchases, avoid choosing the latest one merely because it is easiest to find.
Use the information already available in the merchant’s records. Do not ask for full card numbers or unrelated identity documents to solve an order lookup.
Read the buyer’s words carefully. “I contacted my bank” does not necessarily mean a formal chargeback has opened. It could describe a question, an inquiry, a complaint still being processed, or another payment event.
Record that distinction neutrally: “Buyer reports contacting bank; formal case not yet located.” That preserves the report without inventing a native state.
Check the historical processor
Open the order’s payment events and identify the provider for the challenged transaction. Shopify’s order details documentation explains how to expand payment events and gateway information.
The current provider setting is not enough if the store changed processors after the purchase. A historical transaction remains associated with its original workflow.
If another provider processed the payment, inspect that provider’s documented case channel through an authorized account. Do not diagnose a Shopify synchronization failure before establishing whether Shopify’s native dispute view should contain the case.
Where an order has several payment attempts, match the buyer’s report to the relevant completed transaction rather than an unrelated authorization or failed attempt.
Verify the scope and access of the native view
| Check | Mismatch it can reveal |
|---|---|
| Correct store | Similar order numbers in another store |
| Broad order search | Archived or historical order hidden by filters |
| Current case type and state | Submitted or final case excluded by an Open-only view |
| Original processor | Case belongs in another provider’s system |
| Staff role | User cannot access the expected dispute controls |
| Buyer’s exact report | Bank contact has not been confirmed as a formal case |
Shopify’s store permission guidance identifies dispute-management access. A user’s ability to view an order should not be treated as proof that every dispute function is available to that account.
If another authorized colleague can see the case and you cannot, that is a concrete access or view question. It is more specific than a claim that the case does not exist anywhere.
A hypothetical missing-case investigation
A fictional art-supply store receives a buyer message about a disputed $65 purchase. The support employee checks an Open-only view and sees nothing. The employee initially assumes the buyer has not actually contacted the bank.
A better review opens the specific order and identifies its original third-party processor. The relevant provider portal contains the case. The Shopify lookup was simply the wrong scope for that payment.
In a second hypothetical variation, the transaction is Shopify Payments and the case is already Submitted. Its absence from an Open-only list is consistent with the native state.
These examples show why the merchant should test identity, route, and filter scope before drawing a conclusion about the buyer’s statement.
Record the remaining gap precisely
If no case is found after the relevant checks, write a note containing the verified order, processor, reported event, views checked, and observation time. Preserve any known reference supplied through the official notice or customer conversation.
Do not manufacture a response deadline for a case that has not been located. At the same time, do not ignore a reliable notice with a stated deadline while investigating a visibility problem. Escalate the specific access or case-location issue through the appropriate provider route.
A useful unresolved statement is: “Reported bank contact verified in customer message; correct transaction and processor identified; no native case located as of [time]; provider clarification assigned.”
The completed diagnosis either locates the real case or defines the exact missing association. Both are better than treating an empty screen as a verdict about what the customer did.
Explore Lower Chargeback’s published Shopify dispute scope to understand which cases it can display.
Related reading in this collection:
- Where to Find All Open Chargebacks and Inquiries in Shopify Admin
- Read a Disputed Order’s Authorization and Capture Events in Shopify
- Chargebacks After Closing a Shopify Store: How to Maintain Case Access