A customer emails the merchant on Tuesday: the order was wrong, please refund. The merchant processes the refund on Tuesday afternoon. The customer emails again on Friday: where is the money? The merchant explains the refund is processed but the customer's bank has not yet credited it back to the card. The customer emails again on the following Wednesday: still nothing. The merchant calls support. Support explains that refunds can take up to ten business days depending on the issuing bank. The customer is now angry. The merchant has done nothing wrong, has paid the refund, and has a customer who feels cheated by a process the merchant does not control.
This is a normal week in the operational life of any merchant accepting cards. The refund is not the merchant's transaction; it is the merchant's instruction to a card network that then has to communicate with the issuing bank that then has to credit the cardholder. Every step takes time. None of the time is in the merchant's control.
What card refunds actually involve
A card refund is not the reverse of a card payment. The original payment authorisation flowed in seconds; the refund settles back to the card on a different rail with different timing. The merchant's processor sends the refund instruction to the card network, which routes it to the issuing bank, which queues it for the next batch credit to the cardholder's account. Most issuing banks process inbound refund credits in 3-5 business days; some take up to 10. None of this is visible to the merchant or the customer in real time.
For high-volume merchants, this becomes an operational pattern. Customer service handles "where is my refund?" queries that have no answer beyond "it is processed; please wait." Some customers escalate to a chargeback during the wait, which then triggers a separate dispute process even though the merchant has already refunded. The merchant pays a chargeback fee for a refund the customer has already been credited.
The chargeback window: 120 to 540 days of exposure
Beyond refund timing, the deeper problem with card-network settlement for merchants is the chargeback window itself. A customer can dispute a transaction with their issuing bank up to 120 days after the transaction date for standard Visa and Mastercard rules — and longer in specific categories. For services delivered over time (subscriptions, travel, deliveries scheduled for a future date), the dispute window can extend to 540 days from the original transaction.
That means a merchant who settled a transaction in March 2025 can have those funds clawed back as late as September 2026 if the customer initiates a dispute. The settled cash that appeared in the bank account a year and a half earlier — and which has since been spent on inventory, payroll, or operating expenses — comes back as a debit, plus a chargeback fee of $15-25, regardless of whether the merchant believes the original transaction was legitimate.
Friendly fraud — where a cardholder disputes a transaction they actually authorised, often months later, sometimes simply because they no longer remember the purchase — has grown into one of the largest categories of merchant loss. The merchant has the burden of proof. The default outcome of a dispute favours the cardholder.
Card chargeback windows extend up to 120 days for standard transactions and up to 540 days for delivered-over-time services. Settled funds in a merchant's account can be clawed back more than a year after the original transaction, with the burden of proof on the merchant.
— Visa Core Rules and Mastercard Chargeback Guide, 2025
How peer-to-peer refunds work on Spondula
A refund on Spondula's network is the same kind of transaction as the original payment, processed in reverse. The merchant initiates the refund from their wallet. The customer's wallet receives the balance in seconds. There is no card-network rail to traverse, no issuing bank to wait on, no batch credit cycle. The refund is atomic — it either completes immediately or does not happen at all, and the customer sees the credit in their wallet at the same moment the merchant sees the deduction.
The customer service implications are clear. "Where is my refund?" stops being a question because the refund arrives in the same moment it is processed. The merchant does not have to explain delays imposed by infrastructure they do not control. The customer does not have a reason to escalate.
More structurally: there is no chargeback window. A peer-to-peer transaction that settled in March 2025 cannot be unilaterally reversed by either party in September 2026. Disputes between merchant and customer are resolved directly between them — through the merchant's own customer service, through the merchant's refund policy, through commercial means rather than through a card-network arbitration that defaults against the merchant. The merchant retains commercial control of how disputes are handled.
What changes for the merchant
Three things change for a merchant operating on Spondula's gateway rather than card rails.
Refund operations become atomic. The customer service queue stops including "where is my refund?" inquiries. The merchant can guarantee timing because the merchant controls the timing.
The chargeback infrastructure disappears. There is no 120-day window during which settled funds can be clawed back. The merchant's bank balance reflects what the merchant actually has, not what they have minus a contingent liability for past transactions that might be disputed in the next year.
Friendly fraud loses its primary vector. A customer who later regrets a purchase cannot retroactively reverse it through a card-network dispute. Refund decisions remain commercial — the merchant chooses to refund or not, on the merchant's own policy — rather than being imposed by a network framework.
The chargeback window is one of the largest hidden costs of accepting cards. Most merchants have built it into their operating assumptions because there is nowhere else to put it. Peer-to-peer settlement removes the assumption.
Spondula's gateway is open for launch partners. If chargebacks and refund-timing complaints are part of your customer service load, the waitlist is where that load begins to drop.
Frequently asked questions
How long does a refund take on Spondula?
Seconds. The refund is processed peer-to-peer between the merchant's wallet and the customer's wallet — there is no card-network routing, no issuing bank credit cycle, and no batch processing. The customer sees the credit in their wallet at the same moment the merchant sees the deduction.
Can a customer dispute a Spondula transaction the way they would dispute a card transaction?
No. Spondula transactions settle peer-to-peer and cannot be unilaterally reversed by either party after settlement. Disputes between a merchant and a customer are resolved directly between them — through the merchant's customer service and refund policy — rather than through a card-network framework that imposes outcomes.
What if a customer claims they didn't authorise the transaction?
Spondula transactions are authorised through the customer's own wallet — the customer initiates the payment from their device. Unlike a card transaction where credentials can be stolen and used by a third party, a Spondula payment requires the customer's wallet to authorise it. This significantly reduces the surface for fraudulent unauthorised transactions and the disputes they generate.
Does Spondula handle commercial disputes between merchant and customer?
The Spondula network does not adjudicate commercial disputes — those remain between the parties to the transaction. What the network removes is the card-network arbitration layer, which defaults to the cardholder and imposes outcomes regardless of merchant policy. Merchants retain full commercial control of their refund and dispute policies.
Spondula is a global payments network. It is not a bank, exchange, investment platform, or broker. Availability, pricing, and Operator coverage vary by country. Bitcoin rewards depend on real network activity and are not guaranteed. See our terms and conditions for full details.
