Guía de Revolut sobre devoluciones para comerciantes: plazos, pruebas y respuestas a las reclamaciones

Revolut's chargeback process follows standard Visa and Mastercard network rules. But how those rules reach you depends on which role Revolut plays in the transaction.

If your customer paid with a Revolut card through a different acquirer, Revolut is the card issuer. You have no direct interaction with them. Your acquirer manages the dispute through the card network, exactly as it would for any other Visa or Mastercard issuer.

If you use Revolut as your merchant account, Revolut is your acquirer. Chargebacks appear directly in your Revolut Disputes table, and you have 15 days to respond. Failing to do so automatically forfeits the funds. Evidence submission, escalation, and arbitration all run through Revolut's interface.

The underlying rules in either case (reason codes, representment windows, evidence standards, arbitration) are Visa and Mastercard's, not Revolut's.

How Does the Revolut Chargeback Process Work?

"I submitted everything and still lost." That frustration almost always traces back to a process failure. Understanding the Revolut chargeback process and where the deadlines, permissions, and evidence standards stand is key to avoiding that.

Here’s the Revolut chargeback process, step by step:

Step 1: The Cardholder Initiates a Dispute

Revolut chargebacks start when your customer disputes a completed transaction with their bank, which escalates it through the card network to Revolut. By the time it reaches you, the chargeback has already been formally raised.

What if your customer also uses Revolut? If your customer paid with a Revolut card, Revolut acts as both issuer and acquirer. The dispute still runs through the card network and arrives in your Disputes table the same way.

Step 2: Notification and Immediate Fund Debit

Revolut debits the disputed amount and a fee from your merchant account and holds both until dispute resolution. The chargeback appears in your Disputes table.

Only team members assigned the "Manage Merchant Disputes" permission receive chargeback notifications. If that endpoint isn't configured correctly, the right team members may not receive automated chargeback communications. With a 15-day hard deadline and no extensions, a missed notification is a lost dispute.

Check your permissions setup now, not when a dispute arrives.

Step 3: Your Response Window

Revolut gives you 15 calendar days to accept or challenge a dispute. This is shorter than Visa's 30-day and Mastercard's 45-day network deadlines. But when an acquirer sets a tighter window, that's the deadline you work to. Missing it defaults to a loss.

Step 4: Accept or Challenge

If you accept the claim, your withheld funds return to the customer, and the matter closes. This makes sense when the claim is legitimate, the amount and fee don't justify the effort, or your evidence is genuinely weak.

But to challenge it, you submit representment evidence through the Disputes table. The cardholder's bank reviews your submission and rules. Evidence must be calibrated to the specific reason code. Generic documentation loses. We’ll cover this in detail in a subsequent section.

If the bank rules in your favor, both the disputed funds and the dispute fee are returned. Most acquirers return the funds on a win, but not the fee. Stripe, for example, keeps it regardless of outcome. Revolut remitting the fee on a win is a meaningful differentiator.

Step 5: Pre-Arbitration and Arbitration

If the cardholder's bank rejects your evidence, you may have one final opportunity to appeal before the case potentially enters arbitration. Revolut will notify you if it reaches that stage. Chargeback arbitration is governed by Visa or Mastercard. It's expensive regardless of outcome, and should only be pursued when the disputed amount and strength of your evidence make the cost worthwhile. The illustration below shows a simplified Revolut merchant chargeback workflow: notice, response, and outcome.

How Long Does A Revolut Chargeback Take?

Revolut doesn't publish a stage-by-stage merchant timeline, but states that chargebacks last up to one month on average. In rare cases, some run for a year.

That range is wide enough to be operationally useless on its own, so here's the closest structure of how the clock actually breaks down across each stage:

• Day 0 – Dispute lands in your Disputes table
• Day 15 – Your response deadline
• Day 20 – Evidence review complete/Revolut decision
• Day 25 – Escalation decision deadline (if raised)

The practical implication is that a straightforward case you accept or win cleanly at the evidence stage can close in under a month. A contested case that escalates to pre-arbitration or arbitration will run significantly longer. The one-year outer bound is real, even if rare.

Revolut Chargeback Reason Codes: What the Dispute Is Actually Claiming

Revolut doesn’t issue its own reason codes. Every chargeback arrives with a Visa or Mastercard reason code that defines the cardholder’s formal claim. That code determines what the bank is evaluating, what evidence is relevant, and whether the dispute is even winnable.

The Claim Categories

Visa and Mastercard each organise their reason codes into different categories. The structures differ slightly between networks. But the underlying claim types follow the same logic: fraud, authorisation failures, processing errors, and consumer disputes.

Fraud codes appear when the cardholder states they did not authorise the transaction. This includes stolen card details used without the cardholder’s knowledge. There can also be cases where the cardholder made the purchase themselves, but files a pretentious fraud claim regardless. Both arrive as fraud codes. The code doesn’t distinguish between them, and the bank may not investigate which is true.

Authorisation codes identify a transaction processed without a valid card network authorisation. They are also used when the card was declined and charged anyway, or the authorisation obtained didn’t match the amount settled.

Processing errors apply when the transaction itself was incorrect. Specific instances include a duplicate charge, wrong amount, currency error, or a charge processed after a cancellation or refund was already issued.

Consumer disputes indicate that the cardholder authorised the payment but disputes the outcome. Examples of triggers are when the goods didn’t arrive, arrived materially different from what was described, or a refund was promised and never processed.

We’ve covered these reason codes extensively in our database. Read further:

• Visa Chargeback Reason Codes
• Mastercard Chargeback Reason Codes

Revolut Chargeback Success: What Evidence Wins Chargeback Disputes?

Losing a chargeback you were sure you'd win usually comes down to one of three things: evidence that didn't match the reason code, a format the bank couldn't process, or the strongest piece missing entirely.

Not all evidence carries equal weight. To win, lead with the strongest, most directly relevant evidence. A submission where the critical information is immediately legible performs better than one where it’s buried.

Let’s break that down:

Unauthorised Transaction Claims

Strongest: 3D Secure authentication. Successful 3DS shifts fraud liability to the issuer. It doesn’t neutralise non-fraud codes, though. But for straightforward fraud disputes, it’s your strongest single piece of evidence.

Strong: AVS and CVV match data contextualised as part of a pattern, device and IP consistency with prior purchases, prior transactions from the same card and device with no previous disputes. The issuer already holds AVS and CVV from the original transaction. Present it as a behavioral context, not standalone proof.

Weak on its own: Proof of delivery, order confirmations, order screenshots. These confirm that a transaction occurred, not that the cardholder authorised it.

Item Not Received Claims

Strongest: Carrier confirmation of delivery to the specific address with a timestamp, combined with post-delivery contact from the customer, a support message, a review, and a follow-up order. Delivery confirmation alone is strong. Delivery confirmation plus evidence that the customer had the item is materially stronger.

Strong: Signed delivery confirmation for high-value shipments where signature service was used. Carrier delivery photo, where available.

Weak on its own: A tracking number showing “delivered,” dispatch confirmation, and internal order records. These establish that you shipped, not that the customer received.

Item Not As Described Claims

Strongest: Your product listing as it existed at the time of purchase (dated screenshot or archived version) and any pre-purchase communication where the customer confirmed their understanding of what they were ordering. Add checkout refund policy if displayed.

Strong: Photos or specifications of the item as shipped, explicitly compared against the cardholder’s specific claim. Make the comparison direct. Don’t leave the reviewer to draw the inference.

Weak on its own: Internal product documentation that the customer never saw.

Cancelled Recurring Transaction Claims

Lead with evidence the terms were agreed to, and the charge was valid under them, not merely that no cancellation request was received.

Strongest: Cancellation policy as presented at signup, with evidence the customer acknowledged it; confirmation email, checkbox record, terms acceptance log. Login or usage data showing the customer accessed the service after the alleged cancellation date.

Strong: Cancellation records showing no request was received before billing, along with an uncontested payment history.

Weak on its own: Internal billing records without evidence that the customer agreed to the governing terms.

Authorisation Disputes

These are generally less contestable. If the authorisation failure is genuine, the dispute is hard to win. Where you believe an auth dispute is incorrect, your evidence is the network approval code confirming the transaction was properly authorised.

That said, I must also mention that calibrating all the dispute evidence and getting it right every time is a daunting task. As Mastercard underscored, the chargeback process is costly and time-consuming. So, it should not be surprising that even financial institutions are steering away from manual processing toward analysis supported by automation or AI-based models.

Why Chargeback Automation Has Become The New Normal

Revolut acknowledges that "chargebacks can be a stressful part of running a business." And so knowing what evidence wins is only half the battle. The other half is executing under pressure and within tight deadlines.

That’s where chargeback automation comes in. Automated chargeback management does three things. It detects the dispute as soon as notification is triggered, maps the reason code to the correct evidence hierarchy, and pre-populates the submission with the strongest available documentation. What remains is review and submission, not reconstruction from scratch.

If the customer's bank rejects your initial evidence, chargeback automation equally helps here. The system maintains a structured record of what was submitted and when, which matters if the case goes further.

The evidence framework above tells you what to lead with. Automation ensures that what you know to lead with actually gets submitted correctly, completely, and on time. See how The Beard Club saved 40+ hours per week and increased revenue recovery with automation:

Reducing Revolut Chargebacks Before They Start

Chargebacks generally result from merchant errors, payment confusion, product quality, or friendly fraud (customers disputing legitimate purchases). These are preventable upstream if you manage consent, documentation, and deploy pre-dispute alerts. Here's how:

1. Keep Your Chargeback Ratio Below The Threshold

Card networks penalize merchants whose chargeback ratios exceed the acceptable threshold. Once this threshold is crossed, you are classified as high-risk, may incur monitoring program fees, and could face stricter dispute requirements from Revolut.

In addition to monitoring your ratio monthly and acting quickly if it rises, a key strategy is to proactively avoid processing orders likely to result in chargebacks. Tools like Chargeflow Prevent can help by blocking transactions from known friendly fraud perpetrators. This enables you to maintain a healthier chargeback ratio and account status.

2. Deliver on Time with Tracked Shipping and Proof

“Item not received” is a major chargeback trigger. Prevent it by shipping within the stated timeframe, using tracked shipping with carrier-provided tracking numbers, and sending tracking info automatically. Consider storing signed delivery confirmations for high-value items. Chargebacks can be filed up to 120 days after a missed delivery, so track this window.

3. Make Customer Contact Frictionless and Log All Communication

Many chargebacks happen when customers can’t reach you and escalate to Revolut. Reduce this by:

• Publishing a visible support email/phone on your site and in confirmations
• Responding to inquiries within 24 hours
• Logging all customer communication and storing it as dispute evidence. Dispute automation does this part automatically.

This is essential because Revolut requires proof that the customer attempted to contact the merchant before a chargeback is valid.

4. Process Refunds Quickly for Valid Claims

Friendly fraud can arise when customers feel stuck. If a claim is legitimate, offer immediate refunds without requiring the customer to go through Revolut, keep records of refund transaction IDs and dates, and confirm the refund through email with the expected timeline. This removes the incentive to file a chargeback.

5. Use Revolut’s “Pay by Bank” for High-Risk Transactions

Revolut’s Pay by Bank feature (via its payment gateway) requires customers to confirm payments directly with their bank, which:

• Makes payments harder to dispute as fraudulent.
• Dramatically reduces chargeback risk compared to card payments.

Use this for high-value orders, first-time customers, and high-risk industries (subscriptions, digital goods).

6. Use Chargeback Alerts for Pre-dispute Resolution

Chargeback alerts are vital because they help you detect disputes before they reach Revolut by monitoring Mastercard and Visa systems. You can even program the system to automatically refund certain transactions, which stops the case at the pre-dispute stage. This reduces the number of disputes Revolut ever sees and protects your chargeback ratio.

Conclusión

Revolut chargebacks follow Visa and Mastercard rules. What varies is how those rules reach you, that is, through your own acquirer, or directly through Revolut's Disputes table. That distinction determines who you're working with and on what timeline.

Revolut’s 15-day response window is uncompromising. The evidence standards are extremely specific. That's why many merchants lose chargebacks they’d ordinarily win.

The framework in this guide covers what the process  looks like, what each reason code is evaluating, and what evidence carries weight at each stage. The knowledge matters. But it only converts to chargeback wins if it's executed correctly, under deadline, every time a dispute lands on your dashboard.

That's the case for building the process before you need it (permissions configured, evidence accessible, and response workflows ready) rather than reconstructing it under pressure when a dispute is already counting down.

If you’re still absorbing chargebacks as the cost of doing business, now you know it doesn't have to be. Get your dispute process in place before you need it. Talk to us about how Chargeflow handles this end to end.