Marketplace Chargebacks: Who Pays, the Platform or the Seller?

On this page 8 sections

1. How Marketplace Chargeback Liability Flows
2. Why the Card Networks Hold the Platform Responsible
3. Passing Chargebacks to Sellers: Terms That Make It Enforceable
4. Negative Seller Balances: Debiting Future Payouts or Bank Accounts
5. Who Fights the Dispute and Who Supplies the Evidence
6. Keeping Platform-Wide Dispute Ratios Under Network Limits
7. Building a Loss Reserve for Unrecoverable Chargebacks
8. Next Steps for Marketplace Operators

Key takeaways

• The acquirer debits the merchant of record first, which is usually the platform, not the seller who shipped the order.
• A seller pays only if your agreement, payout timing and reserves let you recover the loss.
• The platform submits the dispute response, but sellers must supply fulfillment evidence on a deadline you set.
• One high-dispute seller can raise the ratio for the whole account, so monitor disputes per seller and keep a reserve for losses you can't recover.

When a buyer disputes a purchase on your marketplace, the card network doesn't look at which seller shipped the item. Marketplace chargeback liability starts with the business that holds the merchant relationship with the acquiring bank. On most marketplaces, that is the platform. The loss reaches the seller only if your contracts and payout systems are built to pass it along. This guide covers how liability flows between the processor, the platform and sellers. It also explains how to recover a chargeback from a seller who has already been paid or has disappeared, and how to keep platform-wide dispute ratios healthy.

How Marketplace Chargeback Liability Flows

A chargeback moves backward through the payment chain. The cardholder disputes the charge with their issuing bank. The issuer sends the dispute through the card network to the acquirer. The acquirer then debits its merchant.

So who pays a chargeback on a marketplace? The platform pays first. The seller pays only when the platform can actually collect.

Why the Card Networks Hold the Platform Responsible

The card networks and your acquirer deal with the merchant they underwrote and contracted with. If your platform is the merchant of record, three things follow:

• Your business name appears on the cardholder's statement.
• Your settlement funds flow through your merchant account.
• Your account takes the debit when a dispute lands.

Your seller agreement doesn't change that relationship. You can't tell the acquirer to "go collect from the seller." The acquirer collects from you, usually by netting the chargeback against your next deposit or drawing on a reserve it holds.

Your Platform Structure Changes the Details

How you're set up with your processor determines who absorbs the first hit and what tools you have to recover.

The networks have specific rules about which businesses may accept payments on behalf of others and how those businesses must register. Confirm with your processor which model your account is approved for. To weigh your options, see our guide on whether your marketplace should become a payment facilitator.

A compliance note: Running transactions for sellers through your own merchant account without the proper approval can be treated as transaction laundering. Describe your model accurately in underwriting and get approved for how you actually operate. If the model is wrong, the account itself is at risk, and that is a far bigger problem than recovering chargebacks.

If you are still deciding how funds will move, our guide to marketplace split payments across multiple sellers explains how payment structure affects these responsibilities.

Passing Chargebacks to Sellers: Terms That Make It Enforceable

Contract terms are what move a loss from the platform to the seller. Vague language such as "sellers are responsible for disputes" invites arguments. Strong seller agreements typically address the following:

• Chargeback responsibility. State that the seller is liable for the disputed amount plus any chargeback fees for orders it fulfilled.
• Right of setoff. Allow the platform to deduct losses from pending and future payouts.
• Reserves and holds. Allow the platform to hold back a percentage of payouts, or delay payouts, based on risk.
• Bank debit authorization. Get a separate, clearly worded authorization to debit the seller's bank account to cover negative balances.
• Evidence obligations. Require sellers to provide specific evidence within a set number of days, and state that sellers who miss the deadline accept the loss.
• Survival after termination. Keep liability in force after the seller closes its store or is removed.
• Platform-fault carve-outs. Decide in advance who pays when the cause sits on your side, such as a checkout bug, a fraud-screening miss or a duplicate charge.
• Acceptance records. Store the date, version and method by which each seller accepted the terms.

For larger or higher-risk sellers, some platforms also ask for a personal guarantee from the business owner.

Enforceability depends on state law and how the agreement was formed. These are general points, not legal advice. Have an attorney draft or review your seller agreement.

Negative Seller Balances: Debiting Future Payouts or Bank Accounts

A seller negative balance happens when chargebacks, refunds or fees exceed the seller's available funds. A clear recovery sequence keeps your team consistent:

1. Offset the pending balance. Deduct the loss from funds that haven't been paid out yet.
2. Offset future payouts. Net the negative balance against upcoming sales.
3. Draw on the seller's reserve. Covering these losses is the reason to hold one.
4. Debit the seller's bank account. Do this only with valid authorization that meets ACH network rules. Confirm the requirements with your processor and counsel.
5. Escalate. Send a formal demand, then use collections or legal action. Save this step for amounts that justify the cost.

Design Payouts so There Is Something to Recover

The best recovery tool is money you haven't sent yet. Common controls include:

• Longer payout delays for new sellers, shortened as they build a clean history
• Releasing funds after confirmed delivery, or after the service has been performed, rather than at checkout
• Rolling reserves for categories with frequent disputes, such as made-to-order goods, high-ticket electronics or services delivered later
• Lower payout limits until a seller is fully verified

When a Seller Has Already Been Paid Out

If the funds are gone but the seller is still active, setoff against future sales usually works. Tell the seller about the debit right away and point to the clause that allows it.

If future volume won't cover the balance, request repayment in writing. If the seller authorized bank debits, start one.

When a Seller Has Disappeared

When a seller closes shop and empties its bank account, your chances of recovery depend mostly on what you collected at onboarding. Verified legal names, tax IDs, confirmed bank accounts and owner details make a demand letter or a collections referral realistic. Without them, you will likely write off the loss.

That is why seller KYC before payouts is also a chargeback control. The identity details you collect for 1099-K reporting for marketplace sellers also help when you need to locate a seller who has gone quiet.

Who Fights the Dispute and Who Supplies the Evidence

Only the merchant of record can respond to a dispute through the acquirer. In most setups, that means the platform submits the response, but the seller holds much of the proof. Good marketplace dispute management divides the evidence work according to who has the information.

A Workable Dispute Workflow

1. Notify the seller automatically as soon as the dispute arrives, and list the evidence needed for that dispute type.
2. Set the seller's deadline well ahead of your processor's response deadline so you have time to assemble the file.
3. Decide whether to fight or accept. Low-value disputes with weak evidence often aren't worth contesting.
4. Submit a concise response matched to the reason code.
5. Record the outcome by seller and by reason. That data drives the controls in the next section.

Keeping Platform-Wide Dispute Ratios Under Network Limits

When your platform is the merchant of record, every seller's disputes count against your merchant account. One seller with poor fulfillment can push the whole platform into trouble. For a related way to protect your account, see our guide to policing marketplace prohibited items for your processor.

Visa and Mastercard each run monitoring programs that track dispute and fraud levels. Merchants above set thresholds can face fees, remediation requirements and, eventually, account termination. Thresholds and program details change, so ask your processor for the current rules that apply to your account.

Practical ways to protect the account:

• Track ratios by seller. Set internal alert levels well below network limits, and slow or suspend payouts when a seller crosses them.
• Screen for fraud at checkout. 3D Secure authentication for online payments can shift liability for many fraud-coded disputes to the issuer when the transaction is authenticated. Confirm with your processor how this applies to your transactions.
• Stop bot attacks early. Our guide to stopping card testing attacks at checkout covers controls that keep fraud spikes off your ratios.
• Use a recognizable descriptor. Buyers who don't recognize a charge often dispute it. A descriptor that includes your marketplace name, plus an order reference where possible, reduces those disputes.
• Make refunds easy. A buyer who gets a quick refund from the seller or the platform has no reason to call the bank.
• Limit risky categories. Require extra review for categories that drive disputes out of proportion to their sales.

Building a Loss Reserve for Unrecoverable Chargebacks

Even with strong terms, some losses won't come back. Sellers vanish, some balances are too small to chase, and some disputes result from platform errors. Plan for these losses instead of absorbing them as surprises.

Start by tracking two numbers every month: total chargeback losses and the amount you recovered from sellers. The gap is your unrecoverable loss. Use it to size an internal reserve.

Illustrative example (not a benchmark):

Keep this internal reserve separate in your planning from any reserve your processor holds on your merchant account. The processor's reserve protects the acquirer. Yours protects your margins.

Review the figure each quarter and after any change in seller mix or category. Ask your accountant how to record chargeback losses and reserves for your business.

Next Steps for Marketplace Operators

Before your next dispute arrives, work through this checklist:

• Confirm with your processor which marketplace model your account is approved for.
• Have counsel review your seller agreement for chargeback, setoff, reserve and debit-authorization clauses.
• Tie payout timing to fulfillment and seller history.
• Build an evidence workflow with seller deadlines shorter than your processor's.
• Monitor dispute ratios per seller, and fund a reserve for the losses you can't recover.

MannyPay provides online payment processing, merchant accounts for low- and high-risk businesses, and payment gateways such as Authorize.net and NMI. If your business accepts payments on behalf of other sellers, describe that model clearly when you apply so it can be reviewed during underwriting. If your payment setup is still taking shape, our ecommerce payment processing guide covers the basics. When you're ready to review your options, request a free quote from MannyPay, and a specialist will respond within one business day.

ME

About the author

MannyPay Editorial Team

Beyond the Swipe's editorial desk researches the publication's guides and news and cites its sources in every article. Articles reviewed by a named MannyPay editor carry that editor's byline.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.