Skip to content
Payments

How Refunds and Chargebacks Work Across Cards, SEPA Instant and Stablecoins

Cards can be charged back, SEPA Instant transfers are final and stablecoin payments cannot be reversed. Here's how refunds and disputes work on each rail.

Aurea4 min read
How Refunds and Chargebacks Work Across Cards, SEPA Instant and Stablecoins

Each payment rail treats reversals differently. A card payment can be disputed by the cardholder weeks after the purchase. A SEPA Instant transfer is final as soon as it lands. A stablecoin transfer cannot be undone by anyone once it is confirmed on-chain. For a merchant accepting all three, a refund policy has to work on top of these rules, not around them.

What is the difference between a refund and a chargeback?

A refund is initiated by the merchant: the business decides to return money to the customer, usually after a return or a cancellation. A chargeback is initiated by the customer through their card issuer, which reverses the payment and debits the merchant, often with a fee. Refunds exist on every rail. Chargebacks exist only where the scheme rules provide them, mainly cards.

How do card chargebacks work?

A card chargeback starts when the cardholder disputes a transaction with their issuer, for reasons such as fraud, goods not received or an item not as described. The issuer pulls the funds back through the card network, and the merchant's acquirer debits the merchant.

The merchant can respond with evidence, such as proof of delivery or 3D Secure authentication, in a process called representment. Time limits and reason codes are set by each card network, and dispute windows typically run for months after the transaction. For merchants, chargebacks mean lost revenue, dispute fees and, above certain ratios, the risk of monitoring programs.

Can a SEPA Instant payment be reversed?

A SEPA Instant credit transfer is irrevocable once executed. The payer cannot cancel it, and there is no chargeback mechanism in the scheme.

Two routes remain. The merchant can send a refund as a new transfer. The payer's bank can also submit a recall request, for example for a duplicate payment or suspected fraud, but the funds are returned only if the beneficiary agrees. Since October 2025, Verification of Payee checks the beneficiary's name against the IBAN before a euro transfer is sent, which reduces payments sent to the wrong account in the first place.

Can a stablecoin payment be refunded?

Yes, but only with a new transfer from the merchant back to the customer. A confirmed blockchain transaction cannot be reversed by the sender, the receiver or the network.

That makes two details matter. First, the refund must go to an address the customer controls, which is not always the address the payment came from, for example when the customer paid from an exchange account. Second, the refund amount and currency should be clear: refunding in the same stablecoin avoids exchange rate disputes. Provider-side compliance checks, including travel rule obligations, apply to the refund just as they did to the original payment.

How do the rails compare?

  • Cards. The customer can dispute through a chargeback. The payment is only truly final once dispute windows close. Refunds go back to the original card.

  • SEPA Credit Transfer. No chargeback, and a recall needs the beneficiary's consent. Final on execution. Refunds are a new transfer to the payer's IBAN.

  • SEPA Instant. Same rules as a standard transfer, with settlement in seconds, at any hour. Refunds are a new transfer to the payer's IBAN.

  • Stablecoins. No dispute mechanism. Final on on-chain confirmation. Refunds are a new transfer to a customer-controlled address.

The pattern is clear: the faster and more final the rail, the more the refund process depends on the merchant's own policy and data. For a closer look at two of these rails, see SEPA Instant vs. Stablecoin Settlement.

How should merchants handle refunds on a multi-rail checkout?

A good multi-rail refund process starts at checkout, when the payment data is captured. Four practices help:

  1. Store the refund route with the payment. Card token, payer IBAN or a verified customer wallet address.

  2. Refund on the original rail and currency whenever possible, to keep reconciliation and accounting clean.

  3. Publish one refund policy that states timelines per payment method, so customers know what to expect.

  4. Track refunds and disputes as events linked to the original payment, so finance sees the full lifecycle.

Refunds that live outside the payment record are one of the most common causes of reconciliation breaks. We covered the rest in What is multirail payment reconciliation.

What this means for merchants

Aurea Pay handles cards, SEPA Instant, Apple Pay, Google Pay, stablecoins and bank transfer through one checkout and one API, with compliance such as PSD2, MiCA, travel rule and 3DS managed at platform level. Refunds and payments sit in the same data model, which keeps the ledger aligned across rails. If you want to see how that works in practice, you can get in touch to request a demo.

This article is for informational purposes only and does not constitute financial or legal advice.

Was this helpful?

We update articles based on your feedback. Tell us what we got right — or where we missed.

Get help