Chargeback fundamentals
Shop Pay and Shopify Payments: Which One Handles Your Dispute?
Shop Pay is an accelerated checkout experience. Shopify Payments is a payment processing service. Seeing Shop Pay on an order does not, by itself, tell you everything about the dispute route; the relevant transaction and processor determine where the merchant should review the case.
For merchants, the important distinction is between how the buyer completed checkout and which payment workflow now owns the challenged transaction. Shopify describes Shop Pay as accelerated checkout and describes Shopify Payments separately.
Separate the checkout label from the processor
A checkout product helps the customer complete a purchase. A processor handles the associated payment under its payment arrangement. They may appear together in the merchant experience, but their names describe different functions.
When a dispute arrives, start with the transaction record. Identify the payment provider and the specific payment associated with the notice. Then find the official case in the corresponding native workflow.
Do not route the case only from a logo in the customer’s checkout screenshot. That image may explain what the buyer remembers, but it is weaker evidence of the merchant’s operational response channel than the order’s payment record.
Similarly, the fact that the store uses Shopify does not make every payment a Shopify Payments transaction. Merchants can have more than one payment option, and the appropriate dispute process follows the actual transaction.
Use a three-layer identification note
| Layer | What to record | Why it matters |
|---|---|---|
| Storefront and checkout | Store reference and checkout context, if relevant | Identifies the customer’s purchase experience |
| Payment transaction | Provider, transaction reference, amount, currency | Identifies the payment being challenged |
| Dispute case | Official case location, status, and deadline | Identifies the current merchant workflow |
This note avoids assigning too much meaning to one product name. Shop Pay can be useful context without being the answer to every question about processing or a bank case.
The same method works if an employee is unfamiliar with the branding. They can verify the transaction and case references rather than guessing from a checkout term.
A complete identification does not require collecting additional cardholder identity information. Use the operational references already available and necessary to connect the order with the challenged payment.
Follow the actual dispute record
For a Shopify Payments dispute, review the native Shopify case and its available actions. For a transaction processed through another provider, verify that provider’s documented dispute workflow. Shopify expressly distinguishes third-party dispute handling in its chargeback process guide.
The deadline must come from the relevant case. A general Shopify article cannot safely substitute for another provider’s case-specific date. An email forwarded from a colleague is also an incomplete source if the live case has changed since the notice was sent.
If the merchant cannot locate the expected dispute, keep the uncertainty visible. Verify the order, transaction, and provider before concluding that the case is missing from the system. The wrong portal can look like an empty queue even when the case exists elsewhere.
Once the official record is found, record its location so the next employee does not repeat the branding investigation.
A hypothetical checkout-to-case handoff
A fictional apparel store receives a customer message saying, “I disputed my Shop Pay purchase.” The support employee forwards the message to operations with the order reference.
The operations owner should treat “Shop Pay purchase” as checkout context, then inspect the payment record. Suppose the record identifies Shopify Payments and the native order contains the dispute. The owner can now assign the Shopify Payments case workflow with a verified deadline.
The useful handoff reads: “Buyer described Shop Pay checkout; transaction provider verified as Shopify Payments; native case linked.” The first clause preserves the customer’s language, while the later clauses establish the merchant’s actual route.
If the transaction details indicate a different product or provider arrangement, the owner follows that evidence instead. The customer’s wording does not decide the processor, and the merchant should not force the case into the wrong queue.
Avoid conclusions that branding does not support
A checkout name is not proof of dispute protection, guaranteed reimbursement, or a universal liability shift. Those questions depend on separate eligibility and transaction-specific conditions. Review them through the applicable documented program when relevant rather than assuming a logo answers them.
For this task, the endpoint is operational: the merchant knows which payment was challenged and where its live case belongs. A short record of provider, transaction, case location, and responsible owner is enough to make the next review concrete.
When product names overlap, translate them into functions. “How did the buyer check out?” and “Where must the merchant handle this dispute?” are different questions. Answering the second from the actual payment record helps the team reach the right case without unnecessary detours.
Explore Lower Chargeback for Shopify dispute monitoring and order context.
Related reading in this collection:
- What Is a Chargeback? A Shopify Merchant’s Starting Guide
- Why a Shopify Order Can Be Paid, Fulfilled, and Disputed at the Same Time
- Chargeback Fees vs Payment Processing Fees: Read the Right Cost Line