The promise of blockchain payments is instant and irreversible settlement. No chargebacks. No payment networks taking weeks to process refunds. Money moves and it stays moved.
In practice, this promise meets a hard business reality. Customers want refunds.
A merchant sells a digital product. The buyer complains it's broken and demands money back. Under traditional payment systems, the merchant can issue a refund in 30 seconds. Under blockchain, "irreversible" means you need to actually write code to move the money back. And if the merchant doesn't, the customer has no recourse except to escalate to your platform.
The difference between theory and practice is measurement. On a traditional payment processor, refund volume runs 2-4% of total transaction volume. Processing costs are built into the fee schedule. On blockchain, refund flows aren't built in. They're bolted on. And when you measure the operational cost, the "irreversible" advantage disappears.
The Refund Escrow Pattern
Proper on-chain refund infrastructure uses escrow. When a customer makes a payment, the funds are locked in a smart contract for a defined window (typically 30-90 days). If neither the merchant nor the customer triggers a dispute, the funds are released to the merchant on the deadline. If a dispute is raised, the funds remain locked until resolution.
This pattern costs gas. Every transaction now involves contract interaction instead of a simple transfer. On Ethereum, this is an extra 50-100K gas per transaction. At $3 per gwei and 100 gwei base fee, that's $15-$30 extra cost per transaction in on-chain fees alone.
But it solves the core problem. Money doesn't vanish. The merchant can't "lose" a refund because they forgot to send it. The customer can't disappear after receiving a refund anyway due to transaction immutability.
The escrow contract itself is simple. Upon creation, it accepts a payment. It stores three pieces of state. The merchant address, the customer address, and a release timestamp. Optionally, it stores a dispute flag that a designated arbitrator can set. The release function checks if the timestamp has passed and no dispute flag is set. If both are true, it sends the funds to the merchant. An emergency release function lets the customer withdraw the funds if the merchant doesn't release them after the window closes.
This assumes that the arbitrator is trustworthy. In practice, the arbitrator is you. Your platform owns the arbitrator key. When a customer opens a dispute, your customer support team reviews it and either calls the resolve function (sends funds to merchant) or calls the refund function (sends funds to customer).
This creates a single point of failure. If your arbitrator key is compromised, all escrow funds are at risk. So you need hardware security module integration for the arbitrator key. That's another operational cost.
Alternatively, you can use multi-sig escrow where release requires approval from both the merchant and the customer. This removes the need for a trusted arbitrator. But it requires the customer to actively sign off on release, which they won't do if they're unhappy. So multi-sig escrow only works if your release window is very tight (like 3 days) so disputes are caught immediately.
The measurement here is simple. Calculate the extra gas cost per transaction. Divide by your transaction volume. Add the hardware security module cost (or multi-sig operational overhead). Compare to the cost of unresolved disputes and customer escalations on traditional payment networks. If the refund escrow cost is lower, adopt it. If not, accept that you'll need different dispute resolution.
Time-Locked Refund Windows
On-chain escrow makes refunds deterministic and time-gated, improving merchant cash flow predictability. Use fixed release windows for simplicity (90-day escrow is standard) or variable windows for risk-based management (7 days for digital goods, 30 days for services, 90 days for custom work). If disputes typically arrive 45 days after purchase but your escrow is 7 days, you have a cash flow mismatch. Match your escrow window to your actual dispute timing.
Authority-Free Dispute Resolution
True on-chain dispute resolution means no human arbitrator. The blockchain itself decides.
This only works for objective disputes. Did the merchant deliver the product? Did the customer pay the right amount? Was the payment made before the deadline? These can be verified on-chain with evidence.
Subjective disputes (product quality, poor service, refund requests based on "changed my mind") require a human judgment call. There's no way around it without a trusted arbiter.
The closest thing to authority-free resolution is multi-party arbitration. Instead of your platform's key being the sole arbitrator, you designate five arbitrators. Any three of the five can call the resolve function. The merchant nominates one, the customer nominates one, and your platform nominates three. If a dispute is raised, all five review the evidence. If three or more agree with the merchant, funds are released to the merchant. If three or more agree with the customer, funds are refunded to the customer.
This is used in blockchain disputes and multi-sig treasuries. The problem is that it doesn't scale. For millions of transactions, you can't find five arbitrators for each dispute. You end up back at a centralized arbitrator with better governance (public record, appeal process) instead of a decentralized one.
For payment infrastructure, the honest approach is to acknowledge that someone has to decide. Make that decision process transparent, fast, and fair. Let customers appeal. Keep a public record. And charge a modest fee for the arbitration service (0.5-2% of the disputed amount). This covers operational costs and makes dispute filing a serious action, not a spam attack.
Traditional processors charge 2.9% + $0.30 per transaction with costs around $0.80 per transaction. On-chain escrow costs 100K gas per transaction (~$5 each), which is expensive individually but drops to $0.055 per transaction when batched (100 transactions for 110K gas total). With 2% refund rates and $5 arbitration per dispute, on-chain costs drop to $0.155 per transaction. Batched on-chain payments can be 5-10x cheaper than traditional processors.
Batched settlement is critical—individual transaction settlements are cost-prohibitive. Batch daily or hourly based on volume.
On-chain payments have zero chargebacks by definition but only if your refund process is fair and fast. Traditional credit cards see 0.1-0.5% chargeback rates (higher in digital goods, travel, subscriptions). If your on-chain escrow feels unfair, customers will escalate to card chargebacks instead. Total dispute rates (escrow + chargebacks) should match or beat traditional networks. The savings come not from chargeback elimination but from building refund processes that prevent customers wanting to dispute in the first place.