Marketplace Chargeback Management: Liability, Seller Evidence and Operations

Marketplace chargeback management is the process of routing each card dispute on a multi-seller platform to the right order, seller and response owner, collecting seller evidence before the processor deadline, and reconciling the funds between the processor, the platform and the seller. Liability follows the payment model and processor setup, not the word "marketplace."

Generic chargeback management assumes one merchant owns the order, the evidence and the loss. On a marketplace those sit with different parties, so you need a payment-model map, a seller evidence request, a deadline buffer and portfolio reporting. According to Mastercard, What is the true cost of a chargeback for businesses? (updated June 2026, research by Datos Insights), global chargeback cost is projected to grow from $36.9 billion in 2026 to $46.1 billion in 2029. Chargeback volume is projected at 286 million in 2026 and 359 million a year by 2029, a 37% rise from 2025.

Who bears a marketplace chargeback: liability by payment model

On smaller screens, scroll tables horizontally to see every column.

Sources: Stripe Connect charges, Stripe marketplace refunds and disputes, Adyen split chargebacks and PayPal disputes for platforms. Checked against public documentation in October 2026; confirm against your own agreement.

Two details change the answer more than the label does. Stripe's on_behalf_of parameter makes the connected account the business of record for a payment, yet Stripe still debits indirect-charge refunds, disputed amounts and fees from the platform balance. And for legacy Express and Custom account types, Stripe states that the platform is responsible for disputes and fraud.

When your platform is the merchant of record, Stripe notes that Visa and Mastercard monitor your dispute rates and that exceeding their thresholds can lead to monitoring programs. Confirm with your acquirer which merchant IDs or account groups are monitored together. Where seller activity shares that reporting scope, one high-dispute seller can increase the measured ratio.

Adyen's marketplace documentation adds a choice Stripe's charge types do not: the platform can accept a chargeback on behalf of the user, or ask the user to supply defense documents and upload them to Adyen. For merchant-side workflows on each processor, see Stripe chargeback management, managing Adyen chargebacks and PayPal disputes, claims and chargebacks.

What Visa and Mastercard rules add for marketplaces and payment facilitators

• Visa defines a marketplace as an online entity that brings customers and sellers together on a single marketplace-branded platform, receives settlement proceeds on the sellers' behalf, issues receipts under the marketplace name and handles refunds and disputes between buyer and seller (Visa, Beyond the Acquirer, February 2024).
• Visa states that the acquirer remains responsible for the acts and obligations of sellers and any other entities operating between the acquirer and the seller. Our reading is that liability then runs from card network to acquirer to platform to seller, so write the last step into your seller terms.
• Visa limits foreign-seller concentration: no single foreign seller may exceed both US$10 million (or local currency equivalent) and 10% of the marketplace's annual Visa sales volume.
• The rulebooks hold the detail. The Visa Core Rules (April 2026 edition) cover acquirer responsibilities and liabilities in marketplace and payment facilitator agreements in Section 5.3.1, and the Mastercard Rules (June 2026 edition) address responsibility for payment facilitator and sponsored merchant activity in Rule 7.6.5.1.

Monitoring programs add a second layer. Under the Visa Acquirer Monitoring Program, the merchant Excessive threshold is a VAMP ratio of at least 1.5% and at least 1,500 counted fraud reports and disputes in the US, Canada, Europe, Asia Pacific and Latin America. Visa’s VAMP fact sheet sets the reduction to 1.5% from April 1, 2026 in the applicable regions. Other regions and acquirer thresholds differ. For upcoming changes, including Mastercard’s GMAP, confirm the effective rules and implementation timetable with your acquirer.

Maintain an acquirer reporting map that identifies each monitored merchant ID or account group, card brand, region, reporting month and denominator. Seller-level rates help locate problems, but they are internal controls unless the acquirer confirms the same reporting scope. Stripe’s monitoring guidance explains that monitoring counts can differ from dashboard data and that winning a dispute does not generally remove it from monitoring calculations. Track prevention and financial recovery separately.

Marketplace chargeback workflow: from notice to reconciliation

Give every case a current stage, a named owner and a next action. The following is a suggested operating workflow; processor requirements and your seller agreement determine the final responsibilities.

If an order cannot be mapped, a seller stays silent or a submission fails, route the case to an exception owner with the remaining time visible. Keep evidence generation, processor submission and seller recovery as separate statuses so a successful action in one system cannot close the whole case prematurely.

Map the payment model before assigning ownership

Map your payment model for each transaction type before you assign ownership, because it decides who answers a dispute. A marketplace may facilitate payments for sellers, operate as merchant of record or use another contractual arrangement, and each changes account relationships, evidence sources and reconciliation duties. The table is a planning guide, not a legal assignment of liability; your payments and legal owners should verify the arrangement.

Record case decisions, submission, customer remedies and financial reconciliation as separate steps. One party may perform an operation while another bears the contractual obligation, and the records should show that split. The payment platform disputes guide covers keeping the storefront, processor and decision-maker separate. If sellers settle across several processors, multi-processor chargeback recovery covers the identifiers and webhooks you need to reconcile them.

Match the dispute to the right order and seller

Match each dispute to the affected seller order or orders before you request evidence. Marketplace orders can contain several sellers, items and shipments, so a payment-level dispute may not line up with one seller's order record. On Stripe separate charges and transfers, one charge can fund transfers to several connected accounts: the dispute attaches to the charge, while each seller's share sits in a transfer.

Keep the original payment reference, marketplace order identifier, seller identifier and item or fulfillment mapping, plus the charge-to-transfer mapping wherever you split funds. Preserve partial refunds, replacements and split shipments so the response reflects the actual history. Do not treat a seller's local order number as globally unique, and test sellers with similar identifiers and customers with several orders.

If the mapping is ambiguous, resolve it before requesting evidence or assigning a financial adjustment. A case sent to the wrong seller exposes information and burns response time. Peer-to-peer resale apps work differently; see Facebook Marketplace chargebacks for that seller-side view.

Worked example: a partial dispute on a two-seller basket

Suppose a buyer pays $200: $120 for Seller A and $80 for Seller B. The platform keeps a hypothetical 10% commission and transfers $108 to A and $72 to B. The buyer then disputes only B’s $80 item as not received. This illustration assumes your seller terms allocate recovery to the affected seller’s net payout; it is not a processor fee schedule or a universal allocation rule.

Collect B’s fulfillment records and the basket receipt linking the $80 claim to that item. A’s delivery confirmation does not establish delivery of B’s item. If the bank disputes the full $200 instead, preserve evidence for both sellers and reassess the allocation. If you win after recovering B’s payout, reconcile the returned principal and any amount owed back to B before closing the finance record.

Collect seller evidence with a specific request

Tell the seller which transaction and issue the request concerns, what to send and the internal cutoff. Avoid asking for "all documents" without naming the disputed point.

Use a structured checklist, but let sellers explain unusual cases: rigid templates can miss split deliveries, custom services or an agreed resolution that fits no field.

Source: Stripe, Respond to disputes, per Stripe's documentation. Other processors set their own limits.

Per Stripe's documentation, limits like these shape the request. Ask sellers for files, not links: a tracking-page URL has to be captured as a PDF or screenshot, because banks do not review external content, audio or video. Carrier delivery confirmation is the usual proof of the delivery step. Merge several files of one evidence type before they reach the platform, and decide who owns final assembly, because the response is final once sent and evidence arriving in three installments breaks that.

For fraud-coded disputes, check eligibility for Visa Compelling Evidence 3.0, which draws on a cardholder's prior undisputed transactions. An upcoming change in Visa’s rules, effective 24 October 2026, expands CE3.0 to support multi-merchant transaction evidence. The rules restrict the acquirer to transaction data it accepted and processed. Before using purchase history across sellers, confirm the eligibility requirements and implementation with your processor; shopping with several sellers does not by itself qualify a dispute. Match requests to the chargeback reason codes; the evidence source map shows where each proof point lives. For the order record itself, see how to win a chargeback as a seller, and for assembling the document, automated chargeback evidence generation.

Preserve source provenance: know which seller supplied each record and when it arrived. A generated summary should not replace the original evidence of an important fact.

Decide whether to contest before assembling the full response

1. Check the claim: identify whether the goods or service were delivered as agreed, and whether an earlier refund or replacement changes the response.
2. Check the evidence: confirm that the records address the actual reason for the dispute and can be submitted before the cutoff. Seller silence is an exception to handle, not proof that the claim is invalid.
3. Check incremental economics: estimate the recoverable disputed amount, the chance of success and the additional cost of contesting. Exclude fees already incurred that cannot be recovered; account for fees returned only after a win.

Use outcomes from comparable, resolved cases to estimate probability, and record the decision separately from any seller recovery.

Stripe’s response guidance distinguishes accepting a dispute from challenging it with evidence. Your seller contract and customer commitments may also affect the decision.

Build a deadline buffer

The seller cutoff has to leave room for validation, correction and submission before the processor deadline. Start from the processor's actual window and work backward; the clock begins at the dispute notice, not when a seller first reads your request. The schedule below is a hypothetical example, not a benchmark.

For a 7-day window, a suggested adjustment is to move the seller cutoff to day 2 or 3 and escalate silent sellers automatically.

Make late and missing responses visible. Assign an exception owner who decides what to submit with the evidence on hand, using the framework in when to fight and when to forgive. A case should never sit silently pending until the external deadline passes, and each request should be logged as delivered or not: an account marked active can still carry an outdated notification address.

PayPal runs a separate clock. Per PayPal's platform documentation, buyers have 180 days from payment to dispute a transaction, buyer and merchant have up to 20 days to resolve it, and PayPal aims to adjudicate within 10 days of an escalation; PayPal's help center says decisions usually take 14 days and can take 30 or longer. Keep that apart from card deadlines; chargeback time limits separates the clocks.

Recover funds and coordinate customer remedies

On indirect charges, recovery is your job. Stripe debits the platform first, and its documentation warns that delaying the transfer reversal after a chargeback puts the platform at risk of losses. Trigger the reversal from the dispute-created event rather than a weekly finance review; dispute webhooks covers handling those events reliably.

Plan for sellers who cannot cover the loss. Where the platform is responsible for negative balances, Stripe reserves a portion of the platform's own available balance to cover a connected account that goes negative and releases it as the account recovers; a balance that stays negative for 180 days is collected from the platform. Adyen allows platform balance accounts to run negative for up to 30 days, then debits your reserved compensation account on the first day of the following month, which you must top up or offset.

Payout timing is the other lever. Stripe's marketplace payments explainer notes that high-risk sellers, including new accounts, may have a percentage of each payout held for 30 to 90 days as a buffer against chargebacks, which sellers experience as a payout hold. Stripe's Connect marketplace documentation separately suggests delaying payouts for new businesses for a predefined period, for example two weeks. Ecommerce fraud prevention covers the buyer-side controls.

If you win the dispute, the money has to travel back. Stripe notes you can transfer previously reversed funds to the connected account, and the transfer fails if the platform balance is short, so keep the balance funded before the outcome arrives.

Support and payments teams and sellers may act on the same order in different systems. Check earlier refunds and replacements before issuing another remedy or preparing a response, and record pending actions as well as completed ones: a refund in progress may not yet appear as settled but still matters to the case. On a Stripe destination charge, a refund leaves the funds with the destination account unless the refund reverses the transfer, so a platform can end up paying for a chargeback after a refund.

A customer refund does not automatically close a filed dispute, so follow the provider's requirements and keep the response consistent with the remedy history. A processor result and a seller-account adjustment are related but separate events: make the basis of any adjustment traceable under your seller terms, and use chargeback reconciliation to tie the entries together.

Handle recovery failures as open finance exceptions

A seller adjustment in your own ledger does not prove cash returned from the processor. For Stripe separate charges and transfers, transfer reversal constraints can prevent recovery when the destination balance is insufficient. Record the reversal ID, recovered amount and remaining exposure; route failures to finance for action under your seller agreement.

Adyen identifies another failure mode: split-chargeback instructions validate format, but an invalid balance account or one linked to a closed account holder can cause the full amount and fees to land on the liable account. Check the actual booking and transaction notifications rather than treating an accepted request as completed allocation.

Use one case history across support, disputes and finance. Check pending remedies before authorizing another payment action, prevent duplicate adjustments when notifications repeat, and keep the seller recovery record open until the movement is confirmed or the remaining loss is explicitly assigned.

Preserve tenant boundaries

Seller users should see only the records they are permitted to access. Platform operators may need portfolio visibility, but their permissions should reflect their jobs and your data practices.

Test evidence links, exports and support tools as well as the main dashboard: a correct case list can still expose another seller's file through an improperly authorized link.

Define offboarding for sellers with open cases. Removing login access should not erase evidence or leave response ownership unclear, so assign contact, retrieval and submission responsibilities through the transition.

Report portfolio performance honestly

Track seller response time, evidence completeness, on-time submission and confirmed outcomes, segmented by payment model, product and seller population where that changes interpretation. Read seller-level results next to the platform-level ratio your acquirer monitors against chargeback thresholds. A hypothetical 100-case cohort shows why each milestone needs its own rate, and chargeback rate calculation covers how the network ratios are counted.

A submission rate measured only against the 60 complete responses (55 of 60) would hide the 30 sellers who never responded.

Measure financial results with a defined denominator and a mature observation period, and separate processor loss, seller adjustments and net platform economics instead of one undefined "recovery" figure. Review unresolved cases by cause, because missing seller records, a confusing request and an ambiguous transaction mapping each need a different fix.

Select a service model that fits

A platform with a mature case interface and submission route may need evidence support only; another may need a fuller merchant experience. The pillar guide to chargeback management for payment platforms covers the full model comparison, and build versus buy frames the investment decision.

Source: Chargeflow platform documentation (docs.chargeflow.io), checked October 2026. Model availability is set per platform by your account manager.

Chargeflow's platform overview lists the requirements: a Connect account your account manager sets up, API keys from the Developer Hub and a Chargeflow account per merchant. White-Label is in beta; white-label chargeback management covers branding, ownership and vendor questions.

Evidence-as-a-Service documentation describes a model built for platforms, not merchants of record, so a platform acting as merchant of record should evaluate Co-Branded first. Under Evidence-as-a-Service you receive the PDF through a webhook and submit it to your payment service provider before the due date. The evidence.ready payload does not carry due_by, so read the deadline from the dispute record. The download link expires 7 days after issue, so store the file when it arrives.

Alerts-as-a-Service is not available yet. Until it ships, merchants can use chargeback alerts directly. The planned model describes enrolling a merchant for Ethoca and Visa Rapid Dispute Resolution in a single API call at onboarding.

Frequently asked questions

Who is liable for a chargeback on a marketplace, the platform or the seller?

Liability on a marketplace depends on the payment model and processor setup, not the marketplace label. On Stripe, destination charges and separate charges and transfers debit the platform first while direct charges debit the connected seller. On Adyen for Platforms the liable balance account is debited by default, and in a PayPal connected integration the merchant assumes financial liability. Your seller terms decide whether the platform recovers the loss.

How does merchant-of-record status change marketplace chargeback operations?

A marketplace acting as merchant of record carries the dispute relationship with its processor and the card networks, and Stripe notes the networks then monitor the platform's dispute rates. Map evidence collection, response authority, submission and reconciliation to that arrangement.

What evidence should a marketplace seller supply?

A marketplace seller should supply order, fulfillment, delivery, communication, remedy and policy records tied to the disputed issue. Ask for files rather than links, because per Stripe's documentation banks do not review external content, and preserve the original sources and who supplied them.

How should a seller deadline differ from the processor deadline?

The seller deadline should sit well inside the processor window, leaving time for validation, correction and submission, because the clock starts at the dispute notice and not when the seller first reads the request. Assign an exception owner for late cases.

Can a marketplace recover a chargeback from the seller?

Often yes, but the platform has to act. On Stripe indirect charges the platform can attempt to recover funds by reversing the transfer to the connected account, and delaying the reversal puts the platform at risk of loss. Payout holds, reserves and negative-balance debits depend on your seller terms and processor.

Does a platform carry risk when its connected accounts receive disputes?

Yes. Stripe direct charges debit the connected account for the disputed amount; fee and negative-balance responsibility depend on the setup. Destination charges and separate charges and transfers debit the platform even when on_behalf_of identifies the connected account as the business of record. Confirm merchant-of-record status separately from which balance is debited.

What if the seller has already been paid when a chargeback arrives?

The processor may debit the platform before seller funds are recovered. Identify the affected transfer, attempt recovery using the processor’s supported mechanism and verify the funds movement. If recovery fails, record the remaining exposure and assign a finance owner. A seller ledger debit alone does not return money to the platform.

How should a marketplace handle a chargeback on a split order?

Map the disputed amount to the relevant items, sellers and shipments. Collect evidence for the actual claim, then allocate seller recovery under your agreement and processor configuration. A partial dispute does not necessarily justify reversing every seller’s payout; a full-payment dispute may require evidence from several sellers.

Can the same evidence service fit every marketplace?

No. Chargeflow documents Evidence-as-a-Service for ISVs, platforms and PSPs, not merchants of record, while Co-Branded fits ISVs and merchants of record. Availability is set per platform by the account manager.

Coordinate seller evidence and platform dispute operations with Chargeflow Connect.