How Refunds Work When Payments Cannot Be Reversed
You cannot undo a blockchain payment. You send a new one going the other way, and that difference changes how a refund policy should be written.
There is no reverse button. A confirmed blockchain payment is permanent, which is the feature that removes chargebacks and also the constraint that makes refunds a different job.
A refund is not an undo. It is a second payment, sent by you, in the opposite direction.
What that changes in practice
- You need an address to send to. Card refunds route themselves back. Here you must ask, and ask for the right one.
- You pay the network fee. You are the sender now.
- Both transactions are public. The customer can verify the refund the moment it lands, which removes the usual argument about whether it was processed.
- It is fast. Minutes, not the five to ten business days a card refund takes.
The mistake that loses money
Refunding to whatever address the payment came from.
If the customer paid from an exchange account, that address may be a shared deposit address or a temporary one. Funds sent back there can fail to credit their account, and recovering them means an exchange support ticket with a low success rate.
Always ask the customer for an address they control, and say so in your policy. This one sentence prevents most refund disasters.
What a refund policy should actually say
Four things, in plain words, before anyone needs them.
- How to request one, and that you will ask for a wallet address they control.
- Which asset and chain the refund is issued in. Normally the one they paid with.
- Whether the network fee is deducted. Either is defensible. Silence is not.
- How volatility is handled. If they paid in a volatile asset, do you refund the same quantity or the same fiat value? Decide once and publish it.
Partial refunds and overpayments
Both are just smaller refunds, and both should be automatic rather than a decision. Overpayments in particular should have a standing rule, because an overpayment sitting in an unresolved state is how a month stops reconciling.
Controls worth having
A refund is an outgoing payment, so treat it like one. Roles that separate who can request from who can approve, an approval threshold above a certain value, and address validation before sending. There is no undo on the refund either.
The part that is genuinely better
Card refunds are slow and opaque. The customer waits days and cannot see anything happening. Here you send it, hand them the transaction hash, and they watch it arrive.
Used well, that is a support advantage rather than a burden. It turns the worst moment in a customer relationship into the fastest interaction they have had with you.
Frequently Asked Questions
Can you refund a crypto payment?
Yes, but not by reversing the original. A refund is a new payment from you back to the customer's address. The original transaction stays on the chain permanently, and both transfers are visible.
Who pays the network fee on a crypto refund?
Whoever sends the refund pays the network fee, which means you do. On cheap chains it is negligible; state in your policy whether refunds are issued gross or net of it so nobody is surprised.
What if a customer paid from an exchange account?
Do not refund to that address without asking. Exchange deposit addresses are often shared or temporary, and funds sent back to one may not reach the customer. Always ask for a wallet address they control.
How long should a crypto refund take?
Minutes on most chains once you approve it. The delay is almost always your own approval process, not the network, which is worth saying in your policy because customers assume the opposite.