Expired Crypto Payments for Merchants: A Refund Is a New Transfer
Expired crypto payments leave merchants to reconcile late funds, request a top up, or refund with a new transaction. Set clear rules for late arrivals.
Expired crypto payments leave merchants to reconcile late funds, request a top up, or refund with a new transaction. Set clear rules for late arrivals.

An expired crypto payment means the gateway’s price-locked invoice window closed, so the quoted rate is no longer guaranteed. If funds still arrive, find the transaction ID and check its confirmations before you do anything else. Then follow your reconciliation policy. A refund is never a protocol reversal. It is a new outbound transaction sent by the recipient.
TL;DR:
- Strict price locks often last 10 to 20 minutes; more tolerant gateways may allow hours or days, trading price protection for customer convenience.
- If a transaction remains unconfirmed when the window closes, wait until it confirms or drops; then classify it as late, underpaid, or absent.
- For confirmed late funds, accept the settlement rate, request a top up, or refund, and state in advance who bears any exchange rate difference.
- Route high value payments, suspected fraud, and cases involving identity checks or compliance rules to a reviewer instead of leaving them in general support.
- Record the chain, transaction ID, fee, confirmation count, timestamp, amount, and settlement rate; link any refund transaction ID to the original payment for auditability.
Payment expiry is a cutoff the gateway enforces, not something the blockchain does. When an invoice is priced in fiat, the gateway converts it into a specific crypto amount and holds that quote for a limited time. Once the window ends, the quote is void.
Gateways lock rates because crypto prices move constantly. Without a lock, a merchant who priced a product at a fixed fiat amount could receive noticeably less value by the time the customer pays. The expiry protects the merchant from that drift.
What happens next depends on platform settings. Some systems expire the invoice automatically and ask the customer to start over. Others flag late arrivals for manual review. A few reissue the invoice at a fresh rate. Know which behavior your setup uses before the first late payment lands.
There is no universal number, but two ranges show up often. Strict price-lock setups often run 10 to 20 minutes. Platforms that tolerate more rate drift stretch the window to hours or even days. Neither is free of cost.
Pick the window that matches your margins. A merchant selling a volatile-priced digital good may prefer short and strict. A merchant with fat margins and slow buyers may accept a longer one.
An expired invoice can end up in a few distinct states, and each one calls for different handling. Your ops team should be able to tell them apart quickly.
Gateways match transactions to invoices using the receiving address, the txid, the amount, and timestamps. A confirmed payment is not lost just because the invoice expired. The coins are in your wallet. The open question is how to account for them, not whether they exist.
Chains behave differently, and that shapes how often invoices expire and how you resolve them.
Bitcoin: Blocks arrive at variable intervals, and fee priority decides who gets in first. Bitcoin’s developer documentation notes that payments gain finality through accumulating confirmations, and that low-fee transactions may be delayed in block discovery. A customer who underpays on fees can blow through your window without doing anything wrong.
Ethereum: Gas prices swing with demand, and token transfers add moving parts. A pending transaction can sit for a long time if its gas setting was too low.
Stablecoins and layer-2s: Some offer faster finality and cheaper fees, which lowers expiry risk. Others need special handling depending on the chain they run on.
Whatever the network, log the chain, txid, fee, and confirmation count for every late payment. Those four fields settle most troubleshooting questions.

Start by verifying the transaction’s status and finality. Never decide on a payment that might still drop out of the mempool. Once it is confirmed, you have three realistic options: accept it at the new rate, request a replacement or top-up, or refund it.
Accepting at the new rate only makes sense when you agree to carry the exchange risk and the customer accepts the changed price. A refund means sending a new outbound transaction from your funds, or crediting the customer’s account balance if your platform supports it.
Escalate when the stakes rise: high-value payments, signs of fraud, or any case touching KYC or compliance requirements. Those should not sit in a general support queue.
Pro Tip: Write your default rule for late payments down before you need it. “Refund anything outside the window” or “accept payments within a clearly defined margin of the original quote” beats improvising under a customer’s deadline.
Work through the same sequence every time. Consistency keeps your books clean and your customers informed.
Skipping step five is where audits go wrong. A refund with no recorded rate or fee is a puzzle for whoever closes the month.
A base-layer blockchain transfer cannot be reversed. Nobody can claw it back, including the gateway. Refunds work because the recipient sends a new outbound transaction from their own funds. Bitcoin’s payment-processing guidance describes providers doing exactly this for manual reconciliation and refund workflows.
Policy decides the details. A provider may refund in crypto or fiat, and the exchange-rate difference between payment and refund is a business choice. The CFPB’s consumer advisory on virtual currencies notes that refund currency and who benefits from rate swings depend on the platform’s policy and disclosures, which is why those terms need to be stated up front.
Refunds also cost network fees and may trigger compliance checks. Record the refund txid next to the original payment. Our write-up on how crypto refunds work walks through that flow in detail.

Most expiry disputes are communication failures, not technical ones. Customers who can see the rules rarely fight them.
Regulators have seen what happens when this goes wrong. The CFPB’s action against the operator of Cash App required refunds and better dispute investigations after weak protocols and incomplete investigations harmed consumers. Fee costs matter here too: our breakdown of crypto payment gateway fees helps you estimate what a refund or re-send really costs.
I have seen how fast a small ambiguity turns into a dispute. Customers forgive an expired invoice. They do not forgive silence. Write the procedure down, assign an owner, and refund quickly when the policy says so. Clarity protects trust and keeps regulators away from your door.
— Dustin
If your team spends hours matching late txids to invoices, a gateway with built-in tooling changes the math. We support many cryptocurrencies, and our crypto processing helps streamline reconciliation.

Check how it fits your checkout on our main page and set up your first payment link today.
The gateway’s price lock ends, so the quoted rate is no longer guaranteed.
Yes, but not by reversing the original transfer. The recipient sends a new outbound transaction, as Bitcoin’s payment-processing documentation describes for provider-run refund workflows.
Base-layer blockchain transfers are not. Transactions also become increasingly irreversible as confirmations accumulate, so any correction has to be a separate payment.
The blockchain itself will not return funds. You need the recipient or provider to send a refund, and the currency and rate used depend on their policy and disclosures.
Open a free CryptoPayr account and take your first crypto payment the same day.
Get started for free
Customize crypto checkout with payment options. Compare hosted, embedded, and API options, secure webhooks, and verify payments before fulfillment.
SellAuth has no crypto gateway plugin, but it has a Custom Payment Method that can redirect buyers to CryptoPayr. Here is the full setup: the redirect URL, the placeholders that matter, auto-confirming orders through the SellAuth API, a test order and the fixes for the three things that usually go wrong.
Crypto payment slippage can shrink merchant receipts through fees, spreads, and execution delays. Learn to request net quotes and reduce surprises.