Managing Refunds Chargebacks & Disputes With Stripe Connect

TL;DR

In a Stripe Connect marketplace, every refund and chargeback raises the question of who pays, the platform or the connected account. The answer depends on your charge type (direct, destination, or separate charges and transfers) and your account type (Standard, Express, or Custom). Platforms using indirect charges absorb dispute fees and disputed amounts by default, and a single missing API flag like reverse_transfer: true can mean your platform eats the full cost while the vendor keeps the money. This guide breaks down every term, liability rule, and prevention strategy you need to protect your marketplace.

Why Disputes Hit Differently in a Marketplace

When a single merchant processes a payment and a customer disputes it, the math is simple: the merchant loses the money and pays the fee. In a Stripe Connect marketplace, the same dispute triggers a cascade of questions. Did the platform collect the funds or did the connected account? Who gets debited first? Can the platform claw back the vendor’s share? What happens if the vendor’s balance is empty?

Managing refunds, chargebacks, and disputes with Stripe Connect is fundamentally harder than in a standard Stripe integration because money flows through multiple parties before settling. Every reversal, whether voluntary or forced by a cardholder’s bank, requires you to decide (or discover, often painfully) who absorbs the loss.

Stripe’s own documentation covers these mechanics across five or more separate pages, each written for developers already deep in the API. Third-party guides tend to cover general Stripe chargebacks without touching Connect specifics. What’s missing is a single resource that unifies the terminology, maps out liability clearly, and translates API parameters into business consequences.

That’s what this guide does. Whether you’re building a rental or service marketplace on Sharetribe or a custom platform from scratch, this is everything you need in one place.

Core Terms: The Basics of Disputes and Refunds

Dispute (Chargeback)

A dispute happens when a cardholder contacts their bank to question a charge. The bank creates a formal dispute on the card network, which immediately reverses the payment. Stripe uses “dispute” and “chargeback” interchangeably, so treat them as the same thing.

The critical detail for Connect platforms: when a dispute is filed, the disputed amount is pulled from someone’s balance right away. Which balance depends on the charge type you used. More on that below.

Inquiry (Retrieval)

An inquiry is a preliminary request for information, not a formal dispute yet. The cardholder’s bank is asking questions before deciding whether to escalate. American Express uses this pre-dispute phase most commonly.

Responding quickly at this stage can prevent a formal chargeback entirely, saving you the dispute fee, the time spent gathering evidence, and the hit to your dispute rate. If an inquiry does escalate, you’ll need to submit evidence again for the formal dispute.

Refund

A refund is a voluntary return of funds initiated by you or your connected account. Unlike disputes, no bank is forcing the reversal. You choose to give money back.

In Connect, refunds on indirect charges (destination charges and separate charges and transfers) come from the platform’s balance. The platform is then responsible for recovering funds from connected accounts using transfer reversals. This distinction matters because your platform is ultimately liable for refund costs on these charge types, regardless of whether the connected account has funds available.

Early Fraud Warning (EFW)

Card networks send early fraud warnings (Visa TC40 reports, Mastercard SAFE reports) when they detect suspected fraud on a transaction. These are not disputes themselves, but they are serious signals. According to Stripe’s documentation, roughly 80% of early fraud warnings convert into formal fraud disputes when no action is taken and liability shift doesn’t apply.

For Connect platforms, EFWs also count toward Visa’s monitoring program calculations, so ignoring them compounds risk.

Dispute Fee (2025 Two-Tier Structure)

Stripe moved to a two-tier dispute fee model in 2025. Understanding both fees is essential for managing refunds, chargebacks, and disputes with Stripe Connect effectively:

Dispute Received Fee: $15 (non-refundable). This is charged every time a cardholder files a dispute. You pay it whether you win or lose.

Dispute Countered Fee: $15 (refundable if you win). Starting June 17, 2025, a second $15 fee applies when you choose to fight a dispute. If you win, this fee is returned. If you lose, you’re out $30 total plus the disputed amount.

Here’s the rule that catches marketplace operators off guard: Connect users cannot pass dispute fees to connected accounts. For indirect charges, the platform absorbs these fees. Period. If you haven’t accounted for this in your take rate, you’re subsidizing vendor-related disputes out of your own margin.

Connect-Specific Terms: Who Is Liable

This section covers the terms that make Stripe Connect dispute management genuinely complex. Skip it at your own financial risk.

Merchant of Record

The merchant of record is the legal entity responsible for facilitating the sale. Card networks hold the merchant of record accountable for dispute rates and fraud monitoring. In Connect, the merchant of record can be either the platform or the connected account.

Using the on_behalf_of parameter when creating charges shifts the merchant-of-record designation to the connected account. This matters for monitoring program calculations, as your platform’s aggregate dispute rate is what Visa and Mastercard watch when you’re the merchant of record.

Direct Charges

With direct charges, the payment is created directly on the connected account. The connected account is the merchant of record, their balance gets debited for disputes, and they handle the dispute process themselves. The platform collects an application fee but isn’t on the hook for chargebacks.

Destination Charges

With destination charges, the platform creates the charge and automatically transfers a portion to the connected account. This is the most common pattern for marketplaces. The platform’s balance is debited when a dispute occurs, and the platform must use transfer reversals to recover funds from the connected account.

Separate Charges and Transfers

This pattern decouples the charge from the transfer entirely. The platform charges the customer, then separately transfers money to the connected account. Like destination charges, the platform’s balance is debited for disputes, and recovery requires manual transfer reversals.

Transfer Reversal

A transfer reversal is how platforms recover funds from a connected account after issuing a refund or losing a dispute. When processing a refund on a destination charge, you must explicitly set reverse_transfer: true in your API call to pull back the connected account’s share.

This is one of the most common and expensive mistakes in Connect implementations. By default, refunding a destination charge does NOT reverse the transfer. If a developer forgets this flag, the platform pays the full refund while the connected account keeps the money. Practitioners on Reddit consistently flag this as a footgun, and marketplace operators using platforms like Sharetribe or custom builds have learned about it the hard way.

Application Fee Refund

When you refund a charge that included an application fee (your platform’s cut), the platform keeps that fee by default. Setting refund_application_fee: true returns the fee proportionally. For example, refunding 40% of a $100 charge with a $5 application fee returns $2 of that fee.

Whether you refund the application fee depends on your business model. If the dispute was caused by vendor behavior, you might choose to keep it. If you’re issuing a goodwill refund, returning it builds trust with your connected accounts. For marketplaces with complex commission and pricing logic, getting this right requires careful planning.

Negative Balance Liability

When a connected account’s Stripe balance goes negative (from disputes, refunds, or fees), someone has to cover it. Stripe lets you choose: your platform takes responsibility, or you assign that responsibility to Stripe.

For Custom and Express accounts, the platform is typically liable for negative balances. Stripe recommends new platforms assign negative balance liability to Stripe initially while they build out risk management processes. After 180 days, Stripe may attempt to recover negative balances from the connected account’s external bank, but if that fails, the platform is on the hook.

Liability by Account Type

Account type is the second variable that determines who pays:

Standard accounts handle their own disputes entirely. Fees come from the connected account’s balance, and the platform is not liable. Multiple practitioners on Reddit’s r/stripe community confirm this: with Standard accounts, your platform isn’t at risk from connected account disputes or fraud. The trade-off is less branding control and connected accounts having direct Stripe dashboard access.

Express accounts give the platform more control over the user experience but make the platform ultimately liable for negative balances and dispute costs on indirect charges.

Custom accounts offer maximum control (your connected accounts never interact with Stripe directly) but also maximum liability. The platform handles everything, including disputes.

For a deeper look at how marketplace platforms handle these decisions in practice, see our marketplace features overview.

The Liability Matrix: Quick Reference

This table is the single most valuable reference for anyone managing refunds, chargebacks, and disputes with Stripe Connect. Bookmark it.

By Charge Type

Charge Type	Who gets debited for disputes/refunds	How the platform recovers
Direct charges	Connected account’s balance	Not applicable (connected account handles it)
Destination charges	Platform’s balance	Transfer reversal (reverse_transfer: true)
Separate charges and transfers	Platform’s balance	Manual transfer reversal via API or Dashboard

By Account Type

Account Type	Who handles disputes	Platform financial liability
Standard	Connected account	None (unless using destination/SCT charges)
Express	Platform (or embedded components)	Yes, liable for negative balances
Custom	Platform	Yes, liable for negative balances

The combination of charge type and account type determines your total exposure. A marketplace using destination charges with Custom accounts has maximum liability. A marketplace using direct charges with Standard accounts has minimum liability. Most real-world platforms land somewhere in between, and the right choice depends on how much control over the payment experience you need.

Measuring Disputes: The Numbers That Matter

Dispute Rate vs. Dispute Activity

Stripe tracks disputes two ways. Dispute activity is the percentage of disputes on successful payments measured by the date the dispute was filed. Dispute rate measures the same thing but by the date the original charge was created. Both appear in the Stripe Dashboard, and they can tell different stories.

Dispute rate is what card networks care about. Dispute activity is what you’ll notice first in your dashboard because it reflects current operational reality.

The 0.75% Threshold

The credit card processing industry considers dispute activity above 0.75% as excessive. Experienced practitioners recommend staying below 0.65% to maintain a comfortable buffer. Once you cross the threshold, you face potential penalties, increased monitoring, and in extreme cases, loss of processing ability.

Visa VAMP (Visa Acquirer Monitoring Program)

Visa’s monitoring program, which reached full enforcement in October 2025, watches your portfolio’s ratio of disputes plus fraud reports to total transactions. An acquirer’s portfolio is flagged as “Above Standard” at 0.50% (50 basis points) and as “Excessive” at 0.70% (70 basis points). The minimum trigger is 1,000 combined disputes and fraud reports per month.

For Connect platforms acting as merchant of record, your platform’s aggregate dispute rate across all connected accounts is what Visa monitors. One bad vendor can poison your numbers.

Mastercard ECM and EFM

Mastercard runs parallel programs: the Excessive Chargeback Merchant (ECM) program and the Excessive Fraud Merchant (EFM) program, each with their own thresholds and escalation timelines.

Prevention and Resolution Tools

Preventing disputes is cheaper than fighting them. Here are the tools and strategies that matter for managing refunds, chargebacks, and disputes with Stripe Connect at scale.

Stripe Radar

Stripe’s built-in fraud detection system scores transactions and blocks suspicious ones. For Connect platforms, Radar rules can be applied at the platform level, giving you centralized fraud prevention across all connected accounts. This is your first line of defense.

Rapid Dispute Resolution (RDR) and Ethoca Alerts

These pre-dispute tools resolve potential chargebacks before they formally become disputes. RDR covers Visa transactions. Ethoca Alerts cover Mastercard. The key benefit: resolved disputes through these tools don’t count toward your dispute rate and don’t incur the $15 dispute received fee. That makes them materially cheaper than fighting disputes after the fact.

Order Insight (Visa Compelling Evidence 3.0)

This tool provides purchase details to cardholders when they check their bank app, helping them recognize legitimate charges before filing a dispute. It’s a deflection strategy, stopping disputes before they start.

Smart Disputes

Stripe’s AI-powered dispute response system automates evidence collection and submission for eligible disputes. It saves time by compiling and submitting evidence automatically. You’re only billed a Smart Disputes fee if you win, so there’s no cost penalty for losses.

Chargeback Protection

An optional add-on costing 0.4% per transaction, applied to all qualifying transactions regardless of whether a chargeback occurs. Stripe reimburses covered disputed amounts, but there’s a $25,000 annual cap per merchant account. New merchants face a probation period before reimbursements kick in.

For high-volume marketplaces, the 0.4% cost adds up quickly, and the annual cap may be insufficient. Run the numbers against your actual dispute rate before enrolling.

Connect Embedded Components

Stripe offers embedded components (Payments, Disputes list, Disputes for a payment) that let connected accounts manage disputes directly from within your platform’s interface. This is particularly useful for Express and Custom accounts where connected accounts don’t have direct Stripe Dashboard access.

Practical Workflow: From Prevention to Recovery

Step 1: Prevent Disputes Before They Happen

Delay payouts for new connected accounts. Stripe recommends holding payouts for a predefined period, such as two weeks, to mitigate risks from fraudulent merchants. Stripe already applies a 7-day first-payout delay for new accounts by default.

Vet your vendors. Understand what your sellers are offering and make sure they don’t overpromise or deliver substandard products. Most chargebacks occur when products don’t meet expectations.

Check balances before refunding. Verify the connected account has sufficient funds. If not, charge their stored payment method to cover the refund before processing. In multi-vendor marketplaces, if a vendor has no money in their Stripe account when a refund is issued, the platform pays. This scenario is discussed frequently in marketplace operator communities and is a genuine financial risk.

Step 2: Detect Disputes Instantly via Webhooks

Set up webhooks for these events:

• charge.dispute.created for immediate notification of new disputes
• charge.dispute.updated for status changes
• charge.dispute.closed for resolution
• radar.early_fraud_warning.created for pre-dispute fraud signals

Automated webhook handling lets you respond faster and route disputes to the right team or connected account without manual monitoring.

Step 3: Respond with Evidence

Build a system for gathering and submitting dispute evidence. Stripe’s API includes a dispute.evidence field that maps to the information card networks need. For platforms with embedded components, connected accounts can upload evidence directly.

The best approach is to replicate Stripe’s evidence fields in your own interface, collecting shipping confirmations, communication logs, terms of service acknowledgments, and proof of delivery before disputes even happen.

Step 4: Recover (or Accept) Losses

If you win the dispute, re-transfer the reversed funds back to the connected account. If you lose, the platform absorbs the loss on indirect charges.

One important cross-border caveat: retransferring a previous reversal is subject to cross-border transfer restrictions, meaning you might not be able to repay your connected account. For cross-border destination charges with on_behalf_of, wait until after a dispute is resolved before attempting recovery.

Building This Into Your Marketplace

Implementing dispute and refund flows correctly from the start saves significant pain later. Season passes, gift cards, custom pricing tiers, and other complex transaction types all create edge cases that need careful handling. Our work on marketplace builds like RareWaters (which involved custom pricing, season passes, and gift card logic) and Kidsy illustrate the kind of transaction complexity that makes dispute management an architectural concern, not just an operational afterthought.

Key Data Points at a Glance

Metric	Value
Dispute received fee (US)	$15, non-refundable
Dispute countered fee (US, from June 2025)	$15, refundable if won
Chargeback Protection cost	0.4% per transaction
Chargeback Protection annual cap	$25,000 per merchant account
Excessive dispute threshold (industry)	0.75%
Visa VAMP “Above Standard”	0.50% or higher
Visa VAMP “Excessive”	0.70% or higher
EFW-to-dispute conversion (no action)	~80%
Chargeback filing window for cardholders	120+ days after payment
Negative balance auto-cover period	180 days

Choosing the Right Architecture for Your Risk Tolerance

The architectural decisions you make when setting up Stripe Connect directly determine your dispute exposure. Here’s the short version:

Minimum liability: Use direct charges with Standard connected accounts. Your vendors handle their own disputes, fees come from their balances, and your platform stays out of it. You give up branding control and UX consistency.

Maximum control: Use destination charges or separate charges and transfers with Custom accounts. You own the full payment experience, but you also own every dispute cost, every negative balance, and every monitoring program threshold.

Middle ground: Use destination charges with Express accounts and always set reverse_transfer: true on refunds. Enroll in RDR and Ethoca Alerts to keep pre-dispute resolutions off your dispute rate. Delay payouts for new vendors. Build evidence collection into your platform from day one.

Most marketplace builders land in that middle ground, balancing user experience against financial risk. If you’re unsure which approach fits your platform, the marketplace FAQ covers common questions about transaction flows and payment architecture.

For platforms that need hands-on help implementing dispute-safe payment flows, commission logic, or refund automation, reach out to our team for a free consultation. We’ve built these systems for marketplaces across rental, service, healthcare, and e-commerce verticals.

Frequently Asked Questions

Who is liable for chargebacks on a Stripe Connect marketplace?

It depends on your charge type and account type. For direct charges, the connected account is liable. For destination charges and separate charges and transfers, the platform is liable and must use transfer reversals to recover funds from connected accounts. Standard connected accounts handle their own disputes regardless of charge type, while Express and Custom account disputes are the platform’s responsibility.

Can I pass Stripe’s dispute fee to my connected accounts?

No. Stripe’s pricing terms explicitly state that Connect users may not pass dispute fees to connected accounts. The platform absorbs the $15 dispute received fee (and, if countered, the additional $15 dispute countered fee) for all indirect charges. Factor this into your take rate.

What happens if I refund a destination charge without setting reverse_transfer to true?

Your platform pays the full refund amount out of its own balance, and the connected account keeps the money that was transferred to them. This is one of the most common and costly mistakes in Stripe Connect implementations. Always set reverse_transfer: true when refunding destination charges unless you intentionally want the platform to absorb the cost.

How do I keep my dispute rate below card network thresholds?

Stay below 0.65% dispute activity as a safety margin (the industry excessive threshold is 0.75%). Use Stripe Radar for fraud prevention, enroll in Rapid Dispute Resolution and Ethoca Alerts to resolve disputes before they count against your rate, delay payouts for new connected accounts, and vet your vendors’ product quality and delivery practices.

Does Stripe’s Chargeback Protection work with Connect?

Yes, but with limitations. It costs 0.4% on all qualifying transactions, caps reimbursements at $25,000 per merchant account annually, and includes a probation period for new merchants. For high-volume marketplaces, run the math: if your annual disputed amount exceeds $25,000 or your dispute rate is very low, the per-transaction cost may exceed the protection’s value.

What’s the difference between dispute rate and dispute activity in Stripe?

Dispute activity measures disputes as a percentage of successful payments by the date the dispute was filed. Dispute rate measures the same thing by the date the original charge was created. Card networks use dispute rate for monitoring programs, but dispute activity gives you a more immediate picture of current problems in your Dashboard.

How long do customers have to file a dispute?

Cardholders can file disputes 120 or more days after the original payment, depending on the card network and reason code. This long window means a vendor could receive their payout, close their account, and be unreachable by the time a dispute arrives. Payout delays and balance reserves for new connected accounts help mitigate this risk.

Should I use Standard accounts to avoid dispute liability?

Standard accounts do eliminate platform liability for disputes on direct charges, and practitioners on Reddit’s r/stripe consistently confirm this. But the trade-off is significant: you lose control over the payment UI, connected accounts get full Stripe Dashboard access, and the payment experience feels less integrated. It’s a legitimate architectural choice for platforms that prioritize low risk over polished branding.