Refund a crypto payment
A refund is a new, irreversible transaction, not a reversal. Return the same asset on the same chain to the sending address, keep the fee policy explicit, and account for the disposal.
Procedure
- Identify the original payment: tx hash, from-address, asset contract, chain, amount, and block timestamp.
cast tx $TXHASH --rpc-url $RPC | jq '{from,to,value,blockNumber}'
- Refund the same asset on the same chain by default. A cross-asset refund is a second trade with its own price, tax event, and slippage — treat it as such.
- Return to the from-address, or to an address the customer nominates in writing; treat a new address as a fresh counterparty check.
- Decide who pays gas and state it in the terms. Default policy: the merchant absorbs gas for refunds; disclose the amount.
- Compute the refund: original amount, or net of the original processing fee if the terms say so. Floor in base units.
- Broadcast, then verify the tx is mined and the recipient balance increased:
cast receipt $REFUND_TX --rpc-url $RPC | grep -E "status|from|to".
- Record the refund tx hash against the original invoice and payment for audit and tax (it is a disposal of the refunded asset).
Pitfalls
- Refunding to a customer's exchange deposit address without the memo/tag: the funds are lost or need support to recover.
- Refunding a different asset "for convenience" and silently creating a taxable trade at a bad rate.
- Sending a refund with too low a fee and leaving it stuck; a replacement tx on the same nonce is needed.
- Assuming the original payment is still unspent; refund from a balance that covers it.
- Treating a refund of a suspected-stolen payment as safe: it can be tainted funds and the send is irreversible.
- A refund to a contract that cannot receive the token reverts and the fee is spent for nothing.
- The customer's original address may be flagged by a compliance tool; refunding to it can be a policy breach.
- Refunds issued after the invoice period land in a different tax period than the receipt, splitting one event across two.
Verification
cast receipt $REFUND_TX --rpc-url $RPC | grep -E "status|from|to"
# status 1, to == nominated address, value == base-unit refund
Report the refund tx hash, amount, asset, chain, destination, and the gas paid.
1---2name: refund-a-crypto-payment3description: Use when returning a crypto payment to a customer. Handles the same-asset-only rule, the network fee, and the irreversible and taxable nature of the refund send.4metadata:5 source: https://skillmd.com/skills/jiayaoqijia/refund-a-crypto-payment6---78# Refund a crypto payment910A refund is a new, irreversible transaction, not a reversal. Return the same asset on the same chain to the sending address, keep the fee policy explicit, and account for the disposal.1112## Procedure13141. Identify the original payment: tx hash, from-address, asset contract, chain, amount, and block timestamp.15 `cast tx $TXHASH --rpc-url $RPC | jq '{from,to,value,blockNumber}'`162. Refund the same asset on the same chain by default. A cross-asset refund is a second trade with its own price, tax event, and slippage — treat it as such.173. Return to the from-address, or to an address the customer nominates in writing; treat a new address as a fresh counterparty check.184. Decide who pays gas and state it in the terms. Default policy: the merchant absorbs gas for refunds; disclose the amount.195. Compute the refund: original amount, or net of the original processing fee if the terms say so. Floor in base units.206. Broadcast, then verify the tx is mined and the recipient balance increased:21 `cast receipt $REFUND_TX --rpc-url $RPC | grep -E "status|from|to"`.227. Record the refund tx hash against the original invoice and payment for audit and tax (it is a disposal of the refunded asset).2324## Pitfalls2526- Refunding to a customer's exchange deposit address without the memo/tag: the funds are lost or need support to recover.27- Refunding a different asset "for convenience" and silently creating a taxable trade at a bad rate.28- Sending a refund with too low a fee and leaving it stuck; a replacement tx on the same nonce is needed.29- Assuming the original payment is still unspent; refund from a balance that covers it.30- Treating a refund of a suspected-stolen payment as safe: it can be tainted funds and the send is irreversible.31- A refund to a contract that cannot receive the token reverts and the fee is spent for nothing.32- The customer's original address may be flagged by a compliance tool; refunding to it can be a policy breach.33- Refunds issued after the invoice period land in a different tax period than the receipt, splitting one event across two.3435## Verification3637 cast receipt $REFUND_TX --rpc-url $RPC | grep -E "status|from|to"38 # status 1, to == nominated address, value == base-unit refund3940Report the refund tx hash, amount, asset, chain, destination, and the gas paid.