dLocal Chargebacks: A Merchant Guide (2026)

How Chargebacks Work on dLocal

dLocal exists specifically to give global brands a single integration point for payment acceptance across dozens of emerging markets — Latam, Africa, and Asia — where local payment preferences often favor non-card methods entirely. That's the whole value proposition, and it's also exactly why the dispute landscape splits so sharply in two.

**Card transactions** (Visa, Mastercard) processed through dLocal follow the standard chargeback flow, appearing in the **dLocal Dashboard** with the reason code, amount, and deadline, just like any other card acquirer.

**Local payment methods** are where things diverge completely. **PIX** (Brazil's instant payment system), **OXXO** (Mexican cash-voucher payment), **PSE** (Colombia's bank transfer system), and **UPI** (India's unified payment interface) are among the most heavily used APMs (alternative payment methods) dLocal supports — and none of them carry a card-network-backed dispute mechanism. These are direct bank-to-bank, cash-based, or account-to-account payment rails with fundamentally different settlement and reversal logic than card payments. If a customer wants to reverse one of these, there's no chargeback to file — the dispute goes through dLocal's own internal resolution process instead, if one applies at all.

This is a genuinely common point of confusion for global merchants new to Latam, Africa, or Asian markets, who often assume every payment method dLocal offers carries equivalent dispute rights simply because it's accessible through the same integration.

dLocal Response Deadline

For card transactions, dLocal follows standard card network deadlines — typically 20–45 days depending on the network — surfaced through the dLocal Dashboard.

For local payment methods, there's no unified deadline, since each local method (PIX, OXXO, PSE, UPI, and others) operates under its own market-specific rules, and many have no formal dispute process at all. Where dLocal's internal resolution does apply, timelines vary by market and method rather than following a single standardized window the way card network deadlines do.

dLocal Chargeback Fee

dLocal does not publish a standard dispute fee — pricing varies by market and payment method, reflecting the genuinely different regulatory, banking, and cost structures across the 40+ markets dLocal operates in. Check your specific merchant agreement for the fee applicable to your transaction mix.

Since local payment methods generally don't have a formal chargeback mechanism, any associated cost (if applicable) would be structured differently than a standard per-dispute card chargeback fee — confirm with your dLocal account team what, if anything, applies to your specific APM mix.

Step-by-Step: How to Respond to a dLocal Chargeback

• →**Confirm the payment method first** — card transactions have a formal chargeback process; PIX, OXXO, PSE, UPI, and most other local methods do not
• →**For card disputes**, check the dLocal Dashboard for the reason code, amount, and deadline
• →**Gather evidence matching the reason code** — standard card dispute evidence rules apply
• →**Submit through the dLocal Dashboard** before the deadline
• →**For local payment method complaints**, contact dLocal support directly to understand whether any internal resolution process applies for that specific method and market
• →**Set customer expectations upfront** at checkout about which payment methods carry standard dispute protections, particularly for high-value transactions in markets where local methods dominate

Most Common Dispute Reasons on dLocal

dLocal's merchant base — global brands selling into Latam, Africa, and Asia, plus streaming services and SaaS with high transaction volume in these regions — produces a dispute pattern shaped heavily by the card/APM split:

• →**Card fraud disputes** follow standard patterns for the portion of dLocal volume processed via cards, particularly relevant for subscription and streaming merchants where recurring card billing is common
• →**"Payment not received" complaints on local methods** (PIX, OXXO, PSE, UPI) are common but don't register as formal chargebacks — merchants should track these as customer service metrics separately from formal dispute ratios
• →**Subscription and SaaS merchants** see disputes concentrated on the card-processed portion of their Latam/Asia customer base, since local payment methods are typically used for one-time rather than recurring transactions
• →**Currency and market-specific confusion** occasionally drives disputes where customers in one market don't recognize pricing or billing descriptors formatted for a different market's conventions

What Makes dLocal Chargebacks Unique

The defining, unavoidable fact is the **card-vs-local-method dispute-right gap** — nearly identical in structure to Flutterwave's African market split, but spanning Latam, Africa, and Asia simultaneously. PIX, OXXO, PSE, and UPI are all wildly popular, legitimate payment methods that a huge share of dLocal's underlying customer base actually prefers over cards — but none of them come with the chargeback protections merchants may assume apply universally.

The practical implication for merchants: your actual dispute exposure on dLocal depends heavily on your payment method mix by market, not just your overall transaction volume. A merchant whose Brazilian customers pay overwhelmingly via PIX has fundamentally different — and in some ways lower — formal chargeback exposure than one whose customers pay by card, even at identical transaction volumes.