Crypto payments can't be retried like cards. Learn how to chase unpaid invoices, handle underpayments and expired payments, and track what you recover.
Crypto dunning is the process of getting a customer to finish a payment that did not complete: an unpaid recurring invoice, an underpayment, an expired payment window or a transfer stuck unconfirmed. It works differently from card dunning. You cannot pull money from a wallet, so you cannot retry the charge. Recovery means a clear reminder, a fresh and easy way to pay, a sensible grace period and clean records.
In card billing, dunning is a loop. A charge fails, the system retries it on a schedule, and emails ask the customer to update the card. Much of the work happens without the customer.
Crypto is a push model. The customer decides to send funds, from a wallet you cannot access, to an address or invoice you created. Nothing is declined by a bank. A payment is simply late, incomplete, stuck on the network or sent in the wrong amount. That changes the job in three ways:
So crypto dunning strategies are less about retry schedules and more about classification, communication and making the second attempt effortless.
Before you write a single reminder, know what you are dealing with. The common causes are well documented by wallets and networks.
Pending or stuck transfers. A payment can sit pending while it waits for the required network confirmations, during congestion, or because the wallet has not broadcast the transaction yet, as Driftstack’s troubleshooting guide explains. Coinbase’s help center adds insufficient network fees and brief connection losses to the list.
Fees set too low. On Ethereum, a transaction can get stuck when the gas fee is below what the network currently requires. Ethereum.org notes that wallets can speed it up with a higher fee or cancel it using the same nonce. On Bitcoin, Bitcoin.org says confirmation delays can grow when fees fall below the network’s current priority, and that unconfirmed transactions are not secure.
Irreversibility. Bitcoin.org also states that transactions are irreversible except through a refund issued by the recipient. That matters for dunning: a wrong or duplicate transfer is fixed by a new transfer from you, not by a reversal. Our guide to expired crypto payments covers why a refund is a separate transfer.
Underpayments. Exchanges and some wallets deduct network fees from the amount sent, so the invoice receives slightly less than it asked for. Rates also move between quotation and payment. See our breakdown of underpaid crypto payments for causes and checks.
Expired windows. Crypto invoices lock an exchange rate for a limited time. If the customer pays after the window closes, the amount may no longer match.
Treat dunning as a triage queue. Each status has its own response.
| Status | What happened | What you do | Message to customer |
|---|---|---|---|
| Unpaid, before expiry | No transfer seen | Gentle reminder with the same payment link | “Your invoice is open until [time]. Pay here.” |
| Pending | Transfer seen, not yet confirmed | Wait, no chase | “We see your payment and are waiting for confirmations.” |
| Underpaid | Less than the invoice total arrived | Record it, ask for the exact remainder | “We received X. Please send the remaining Y to this address.” |
| Expired, nothing received | Window closed | Issue a new invoice with a fresh rate | “Your invoice expired. Here is a new one.” |
| Expired, paid late | Funds arrived after the window | Review, then settle or refund by a new transfer | “We received your payment after expiry. Here is what happens next.” |
| Overpaid | More than the invoice total arrived | Credit or return the difference | “You sent more than required. Choose a credit or a return.” |
The pending row is the one teams get wrong. A customer who has already paid and receives a “payment overdue” email loses trust quickly. Your dunning logic should check for any incoming transfer before it sends anything.
Card dunning emails commonly run over a couple of weeks. Crypto invoices often need a tighter start, because the payment window itself is short, and a longer tail for recurring plans, because customers need time to fund a wallet.
If abandonment is your bigger problem, our guide on fixing crypto checkout fees and abandonment covers what happens before the payment fails.
Recurring crypto billing usually works as an invoice sent each cycle, not a stored credential. That means every renewal is a fresh chance for the customer to forget, so dunning starts before the due date. If you want a plain-language primer on the mechanics of subscription charging, how recurring payments work is a handy parallel from the card world.
A workable cadence:
| When | Action |
|---|---|
| 5 to 7 days before renewal | Send the upcoming invoice with a payment link |
| Due date | Confirm the invoice is open and give the deadline |
| 1 to 3 days after | Reminder, access still active |
| End of grace period | Warning that access will pause, with a fresh link |
| After the grace period | Pause, not delete. Keep the account and data recoverable |
Pick a grace period that matches your product. A SaaS tool with daily use can be stricter than a yearly license. Whatever you choose, publish it in your terms and repeat it in the reminder so nobody is surprised.
For more on the SaaS side, read our piece on getting paid when cards fail.
Most recovery is won or lost on friction. A customer who wants to pay and cannot work out how will drift away.
One link, one action. Every message carries a single payment link that opens the right invoice, with the amount and network already set. No login wall if you can avoid it.
Show the remaining amount, not the original. For underpayments, the page should show what has arrived and what is still due, so the customer does not send the full amount again.
Keep the original page open when possible. Driftstack’s guidance says that when an order is in a partial state, customers should generally only try to complete it if the original payment page is still open. Otherwise they should avoid sending more funds to prevent reconciliation issues. Build your emails around that rule: “Use this page to finish” beats “send the rest to the address below.”
One address per invoice. When each invoice has its own address, any transfer can be matched to the right customer without guessing. Reuse creates confusion, which is why we wrote about address reuse risk.
Offer a stablecoin option. Customers who dislike price swings between invoice and payment tend to be more comfortable with a stable asset. A shorter exposure to volatility also means fewer expired quotes.
Explain network fees in plain words. If a payment is stuck because the fee was too low, tell the customer their wallet may offer a speed-up option, as Ethereum.org describes, and to contact you before sending anything else.
Record what arrived, when, on which network and against which invoice. A consistent record makes finance and support talk about the same facts. We list the six fields to record for each partial payment. Then decide, by rule and not by mood, whether a small shortfall is accepted or the remainder is requested. Setting a tolerance in advance saves hundreds of small emails.
When funds arrive after the window closed, you have three options: honor the original deal, re-price at the current rate and ask for the difference, or refund. Pick one policy, write it into your terms, and apply it. Refunds go out as a new transfer, so confirm the customer’s destination address and network in writing first.
Because crypto has no chargeback network, disputes arrive as support tickets, not formal claims. A clear dunning trail (invoice, reminders, transfers received) is your evidence. See crypto payment disputes for what merchants and buyers can do.
Some sectors face tighter scrutiny from card processors and lean on crypto as a result. The same dunning discipline applies, and we cover the context in crypto payments for high-risk industries.
E-commerce. The window is short. Keep the cart saved, send one reminder before expiry, and regenerate the invoice with one click. See crypto payments for e-commerce.
Freelancers and agencies. Invoices run on net terms, so remind a few days before the due date and again on it. A payment link in the invoice email removes the need to explain wallets.
SaaS. Treat each renewal as an invoice, use a grace period tied to usage, and pause access rather than deleting accounts. Customers who lapse because a payment slipped often return when the link is simple.
Gaming and digital goods. Delivery is usually automated, so status accuracy matters most. Deliver on confirmed payment, show “waiting for confirmation” in the interface, and send in-game or Discord notices. Our guide to payment alerts in Discord shows how to set that up safely.
Marketplaces. A late buyer payment can hold up several sellers. Keep the order in an escrow-like pending state, remind the buyer, and release seller shares only after confirmation. See crypto payments for marketplaces.
Manual chasing does not scale past a few dozen invoices. The sturdier approach is to drive messages from payment status events: invoice created, transfer detected, confirmed, underpaid, expired. Each event triggers exactly one template, and any new event cancels the pending reminder. That is how you avoid the “pay now” email arriving after the customer already paid.
Our article on customizing crypto checkout explains why wiring up webhooks before polishing the interface pays off.
Track a short list monthly, by invoice type:
Set your own baseline first. Published benchmarks come mostly from card billing and differ by product and audience, so use them only as a rough reference and compare your figures with your own history.
Our view at CryptoPayr is that crypto dunning succeeds when payment status is accurate and recovery is easy, not when reminders are loud.
Merchants tell us the same thing: the customer usually wants to pay. The failures come from a stuck transfer, a short amount, or an expired quote. So we focus on the parts a merchant can control: hosted checkout and payment links that carry the invoice, recurring billing that creates a fresh invoice each cycle, and API access so your own systems can react to what happens on the invoice.
We also built for teams that need to move quickly. There is no KYC step and approval is instant, so a freelancer or a small SaaS can set up a dunning flow in an afternoon and not wait weeks. Our flat per-payment option and volume tiers are published, so you can model what recovered invoices cost before you commit.
Our advice is simple: classify first, remind early, make the second payment one click, and keep a record of every transfer.
Dustin
If you are chasing invoices by hand, a gateway that handles payment links, hosted checkout, recurring billing and API access removes much of the work. CryptoPayr supports 110+ cryptocurrencies, including Bitcoin and Ethereum, and has no setup or monthly fees. Start with crypto processing for checkout and invoicing, or see the flat per-payment pricing at $0.10 per payment.
Marketplaces and platforms that split commissions can look at the platform offering, and teams paying out sellers or contractors can use mass payouts.
Not in the way you retry a card. Crypto payments are pushed by the customer from their own wallet, so you cannot pull funds. Your “retry” is a new invoice or the same payment link, sent with a reminder.
It depends on your product and how often customers use it. A few days past the due date works for many tools, with access paused and not deleted at the end. State the period in your terms and in each reminder.
Tell them you can see the transfer and are waiting for network confirmations. Pending transfers can come from congestion or low network fees, according to Coinbase’s help center. Ask them not to send a second payment unless you tell them to.
Record the amount received, then request only the remainder using the original payment page where possible. Decide in advance whether you accept small shortfalls. Sending the full amount again creates a duplicate you then have to refund.
No. Bitcoin.org states that transactions are irreversible except through a refund issued by the recipient. A refund is a new transfer from you, so confirm the destination address and network before sending.
Open a free CryptoPayr account and take your first crypto payment the same day.
Get started for free
Why crypto payments fail or never reach the order, how to check a transaction, what can be refunded, and how merchants can prevent failures at checkout.
Learn how to sell digital goods for crypto: pick a payment model, automate delivery, handle fees, refunds and taxes, and start accepting Bitcoin and more.
What a self-hosted crypto gateway is, what it takes to run one, what it costs, and when a hosted or white-label gateway is the smarter choice for your business.