How Merchants of Record Should Manage Chargebacks Across Sellers

A merchant of record (MoR) should run every chargeback through one central workflow, because it holds the processor relationship and the deadline. Each case still needs the right seller attached. You need seller-level evidence, platform-level rules and a ledger that splits refunds, chargebacks, fees and seller balances.

Buyers may see your platform as the seller even when a third party fulfilled the order. You receive the dispute, but the proof often sits with the seller. That makes a two-level system: you own the case, and sellers own many of the facts.

{{cta}}

Who Owns What When a Seller's Order Is Disputed?

You own the processor response and the deadline. The seller supplies fulfillment facts. Your dispute provider assembles and submits evidence under your account. The matrix below splits each job across the three parties.

Separate Three Layers of Merchant-of-Record Responsibility

“Merchant of record” sounds like one answer to who pays. In practice, it has three layers. Each layer can point to a different party, so document them for every seller program.

• Legal and network liability: who the card networks and your acquirer see as the seller. For an MoR, that is you. Stripe calls the MoR the legal seller that takes on fraud and chargeback liability, and dispute management.
• Contractual allocation: whether and when the seller repays you. This covers reserves, offsets, caps, fee pass-through and duties that survive exit. It also needs a cash waterfall for when the seller balance and reserve run short, or the seller becomes insolvent.
• Workflow ownership: who sends the proof, signs off, submits, answers questions and shares the result. Record ownership sits here too: who keeps transaction, consent, fulfillment, usage and message records for the full dispute lifecycle.

Writing down all three stops the legal label from hiding who must act and who carries the loss. On one case, you can be liable to the network, the seller can fund the loss and your dispute team can run the workflow.

Some marketplaces make the seller the merchant of record instead. If that is your model, see marketplace chargeback management. PayFacs face a related split, covered in who pays for PayFac chargebacks.

Why Every Seller's Disputes Hit One MoR Ratio

Card networks measure the merchant on the transaction. When you are the MoR, that merchant is you. Stripe's Connect marketplace guide says that when the platform is the merchant of record, Visa and Mastercard monitor its dispute rates. One weak seller can push your whole program toward a monitoring program.

Track a ratio for each seller, not only for the platform. Use it to set seller reserves, tighten onboarding or pause a seller before your total crosses a threshold. Our Visa VAMP guide explains how the ratio is counted. For the wider dashboard, see the chargeback KPIs payment platforms should track.

Create One Case With Separate Platform and Seller Ownership

The processor dispute belongs to your MoR account. Your internal case should still name the seller, the order line and the fulfillment owner.

Keep two fields: who owns the case at the processor, and who pays for it. That handles shared orders, bundles and promotions you fund, without forcing one owner onto every case. Use clear rules to route every dispute to the right merchant, transaction and evidence source.

If you process through more than one PSP, normalize chargeback data across payment processors before you attribute cases. Different PSPs name the same fields in different ways.

If you cannot attribute the seller with confidence, hold the case in a central exception queue. Sending it to the wrong seller exposes buyer data and delays the response. Limit each seller to its own cases with roles, permissions and merchant data isolation.

Standardize Seller Evidence Before the First Dispute

Set the records each seller must keep when they join: order, delivery, service and message records. Collect them through APIs or structured uploads. Screenshots requested after a chargeback arrives are late and hard to audit.

Each seller type proves something different:

Digital sellers need proof of access, as our guide to winning digital goods chargebacks shows. To pull seller and platform facts into one case timeline, assemble chargeback evidence from orders, billing, CRM and fraud data. Feed new cases in through dispute webhooks so none waits for a manual check.

Use Central Rules, Then Adjust for Seller Context

Set one policy for small cases, refunds, banned evidence and escalation. Then let the seller's context shape each call: how complete the proof is, the product type, past results and the seller's status.

Never let a seller's preference override a network deadline or platform compliance. You own the response workflow even when the seller funds the loss. Choose chargeback representment only when the evidence matches the reason code.

If a seller misses your internal SLA, apply a preset fallback. You can submit with platform evidence, accept the dispute or apply the seller policy.

Make Financial Allocation Auditable

Write down when you debit a seller, whether you pass through chargeback fees, how you credit a later recovery and how reserves apply. Put those rules in the seller contract and in the ledger.

Example: Debit Timing on Stripe Connect

Stripe's marketplace guide shows why timing matters. With destination charges or separate charges and transfers, Stripe debits the disputed amount and the fee from your platform balance. You recover the money from the seller's connected account by reversing the transfer.

If you reverse early and then win, you must pay the seller back. That transfer can fail if your platform balance is short or cross-border transfer rules apply.

Seller reports should list each amount on its own line: the disputed sum, the loss you accepted, the sum you fought, the sum you got back, fees and reserve moves. One net number is hard to audit and creates support tickets. Learn how to reconcile chargeback recoveries, fees and sub-merchant balances with a subledger.

Keep Evidence After a Seller Leaves

A seller can exit while chargeback exposure stays open. Visa's dispute FAQ gives 120 days from the expected service date for services not received, capped at 540 days from the transaction processing date. A dispute can arrive more than a year after the sale. See all chargeback time limits by network.

Keep the records you are allowed to keep, a way to reach the seller and your money controls for that whole window. You can limit access, but do not delete the case history.

Your offboarding flow should freeze new processing and keep open cases running. It should also define how later recoveries or negative balances are settled.

{{cta}}

Roll Out the Program in Eight Steps

1. Map buyer-to-seller ownership: link each payment to its order line, the seller who shipped it and the seller contract.
2. Define seller evidence requirements: set structured records by seller and product type.
3. Set central rules: decide when to accept, refund, fight or review a case.
4. Collect evidence automatically: pull seller and platform facts into one case timeline.
5. Submit under the MoR workflow: protect the processor deadline whether or not the seller responds.
6. Post the money correctly: book the disputed sum, fees, reserves and recoveries to the right seller and platform accounts.
7. Keep records after exit: hold the dispute records you need after a seller leaves.
8. Test before launch: test and monitor the embedded chargeback integration with sample disputes for each seller type.

Common Failure Modes and the Controls That Fix Them

Most MoR dispute programs fail in the same few places. Each one has a clear control.

How Chargeflow Connect Fits MoR Programs

Chargeflow Connect gives you one dashboard across sellers, with admin and merchant views. It automates evidence and submission across 45+ PSPs and 100+ integrations.

Chargeflow's platform docs recommend Co-Branded or White-Label for merchants of record. They say Evidence-as-a-Service is not a fit for an MoR. Co-Branded is available today, and White-Label is marked beta (checked November 5, 2026). To pick a model, compare embedded, co-branded and API-based chargeback management. Then read our guide to white-label chargeback management.

You still own seller liability, reserves and the ledger. Tie them to the dispute flow so each result posts to the right seller.

If you are weighing your PSPs' own tools, compare native PSP dispute tools vs. processor-agnostic chargeback management. If you run many PSPs behind one checkout, see multi-PSP chargeback management for orchestration platforms. The full picture is in chargeback management for payment platforms.

Manage seller chargebacks from one platform-level workflow with Chargeflow Connect.

Perguntas frequentes

Who Responds to a Chargeback in a Merchant-of-Record Model?

In a merchant-of-record model, the MoR or its authorized dispute provider responds to the processor, because the MoR is the legal seller. The underlying seller supplies the facts the evidence needs, such as delivery or usage records.

Do Seller Disputes Count Toward the Merchant of Record's Chargeback Ratio?

Yes. Card networks measure the merchant of record, so every seller's disputes count toward the MoR's ratio. Under Visa VAMP, the Excessive merchant threshold in most regions is 1.5% with at least 1,500 counted events from April 1, 2026.

Should Sellers See the Full Customer Record?

No. A seller in a merchant-of-record program should see only the fields its case needs and the MoR's data policy allows. Full buyer records raise privacy risk without improving the evidence.

Can a Merchant of Record Charge Sellers for Dispute Fees?

Yes, if the seller agreement allows it and applicable law permits it. The merchant of record should post the fee as its own ledger line, separate from the disputed principal.

What Happens If a Seller Does Not Provide Evidence?

The merchant of record applies a preset fallback before the processor deadline. It can submit with platform evidence, accept the dispute or apply the seller policy. The deadline never waits for the seller.

Do Seller Chargebacks End When the Seller Is Offboarded?

No. Sales processed before a seller leaves a merchant-of-record platform can still be disputed. Visa caps some dispute windows at 540 days from the transaction processing date, so the MoR should keep records and recovery rights for that period.

Fontes

• Stripe: Merchant of record for SaaS
• Stripe Connect: Handle refunds and disputes
• Visa: Dispute rules FAQ
• TabaPay: The next phase of Visa VAMP
• Chargeflow for Platforms overview