Skip to content
Payfim - Secure. Simple. Yours.
Guides

How to Handle Crypto Underpayments, Overpayments and Refunds

When a crypto payment arrives short, the safe default is to hold the order, tell the customer the exact shortfall, and either collect the difference or refund what arrived. Refunds are never automatic in crypto: you send a new transfer from your wallet, to an address the customer confirms in writing, and record the transaction hash on the order.

PFPayfim Team · September 18, 2026 · 9 min read
How to Handle Crypto Underpayments, Overpayments and Refunds
Key takeaways
  • Most underpayments come from exchange withdrawal fees being taken out of the amount the customer typed.
  • Payfim accepts payments within a small tolerance (0.5% by default) and flags anything below it as Underpaid, never as paid.
  • Overpayments are marked paid with a note; decide in advance whether you refund the excess or keep it as credit.
  • Never refund to the address a payment came from. Exchange sending addresses are not the customer's deposit address.
  • A written policy that covers shortfalls, late payments and refunds saves more time than any setting.

Card payments are all-or-nothing: the charge succeeds for the exact amount or it fails. Crypto is different. The customer types an amount, their wallet or exchange sends whatever it sends, and your gateway has to make sense of the result. Nearly every crypto support ticket falls into one of five cases: too little, too much, too late, the wrong coin, or "please refund me". Here is how to handle each one calmly.

Why do customers underpay crypto invoices?

There are three usual causes, and none of them involve bad intent:

You can prevent most of these with one sentence on your payment instructions: "If you pay from an exchange, make sure the amount received matches the amount shown, since some exchanges subtract their fee."

How does Payfim decide whether a payment is short?

Each invoice has an exact expected amount. Payfim accepts payments within a small underpayment tolerance, 0.5% by default, so that tiny rounding differences do not block an order. You can set it anywhere from 0 to 5% in the gateway settings. Anything below the tolerance is marked Underpaid once it confirms, with a note such as "Only 148.5 of 150.0421 USDT received." An underpaid invoice is never reported to your store as paid.

What happens in your store depends on the platform's own order states. For example, WooCommerce puts the order On hold with a note, Magento moves it to Payment Review, and GiveWP keeps the donation Pending. Each platform guide in the documentation describes the exact behavior, and the troubleshooting page covers orders that stay pending.

What should you do with an underpaid order?

Decide your rule once so staff don't improvise. A simple, fair policy:

ShortfallSuggested action
Within the toleranceNothing: the order is paid automatically.
Small (say, under $2 or 2%)Accept it. Mark the invoice paid manually with a note. The goodwill is worth more than the difference.
LargerEmail the customer with the exact shortfall and ask them to send the difference, or offer to refund what arrived.
No reply within your deadlineRefund the amount received, minus the network fee if your policy says so, and cancel the order.

To accept a short payment, open the invoice in your gateway, check the received amount and transaction on a block explorer, and use Mark as paid manually with the transaction hash and a reason. Your store is notified the same way as for an automatic confirmation.

If the customer sends a top-up, note that on most coins Payfim matches one transaction to one invoice, because many invoices share the same receiving address. The second transaction will reach your wallet but will not be added to the original invoice automatically. Confirm both transactions in your wallet, then mark the invoice paid manually and list both hashes in the note. Coins with a dedicated reference per invoice, such as XRP with its destination tag or Monero with a subaddress in wallet-RPC mode, can combine several transfers on one invoice.

A template you can adapt:

Hi Sam, thanks for your payment for order #4821. We received 148.5 USDT, which is 1.54 USDT less than the 150.0421 USDT requested. This usually happens when an exchange deducts its withdrawal fee. Could you send the remaining 1.54 USDT to the same address on the TRON network? Or, if you prefer, reply with a TRON address and we will refund the 148.5 USDT in full.

What happens when a customer overpays?

An overpayment still covers the order, so Payfim marks the invoice paid and adds a note that the customer sent more than requested. The question is only what to do with the excess. Common choices are to refund it (sensible for large amounts), to add it as account credit (natural for hosting and billing systems like WHMCS), or to keep tiny excesses under a threshold you set, as long as your published policy says so.

Be careful with customers who contact you before you notice an overpayment, asking for money back to a new address. Verify the invoice in your gateway and the transaction on a block explorer first. "I overpaid, please refund" is a known scam when no overpayment actually happened.

What if the customer pays after the quote expires?

Payfim locks the exchange rate for 30 minutes by default. Payments broadcast right at the deadline are still detected during a short grace period and processed normally. After that, the invoice expires and the customer can request a fresh quote from the payment page.

If coins arrive for an invoice that has already expired, they are in your wallet but the order has not been updated. For stablecoins, simply accept the payment with Mark as paid manually. For volatile coins, compare the received value with the order total at today's rate and treat any gap like an underpayment or overpayment. To reduce late payments, consider lengthening the quote period in the gateway settings if many of your customers pay from exchanges that hold withdrawals for review.

What if the customer sends the wrong coin or network?

If the funds reached an address you control (for example USDC sent to an Ethereum address that also receives USDT), you can recover and apply them manually. If they went to a network where you have no wallet at that address, recovery may be impossible or may require the customer's exchange to help. Clear network labels on your checkout prevent most of these. Our USDT TRC20 guide covers the TRON-versus-Ethereum mix-up in detail.

How do you refund a crypto payment safely?

There is no refund button that reverses a blockchain payment, and that is a good thing: nobody else can pull money out of your wallet. Refunds are new transfers you make yourself. Follow the same steps every time:

  1. Ask for a refund address in writing, including the network. Never refund to the address the payment came from: if the customer paid from an exchange, that address belongs to the exchange's hot wallet, not to the customer.
  2. Agree the amount. Decide in your policy whether refunds are made in the same coin amount or at the current value of the original fiat price. With stablecoins these are nearly identical; with Bitcoin they can differ a lot.
  3. Check the address carefully. Copy it from the customer's message, not from your wallet history, to avoid address poisoning. For large refunds, send a small test amount first.
  4. Send and record. Add the refund transaction hash to the order notes and, if your platform supports it, create a refund record in the store so your reports balance.

Your published refund policy should say who pays the network fee on refunds and how long customers have to request one. Consumer protection rules may apply to you regardless of payment method, so ask a qualified adviser what applies in your country.

What about double payments?

Occasionally a customer pays the same invoice twice, for instance after refreshing the page. Each blockchain transaction can only pay one invoice, so the second payment does not mark anything else as paid. It is not matched to any invoice, so you will see it in your wallet rather than on an order; refund it or keep it as credit using the steps above. Billing systems like WHMCS also reject duplicate transaction IDs, so a retried webhook can never apply the same payment twice.

Which settings help prevent these problems?

With a written policy and these settings, most edge cases take a couple of minutes to resolve, and customers remember that you handled them fairly.

Frequently asked questions

Will Payfim mark an underpaid order as paid?

No. Payments below the tolerance (0.5% by default) are flagged Underpaid and never reported to your store as paid. You can accept them manually after checking.

Can I issue a crypto refund from my store admin?

No. Blockchain payments cannot be reversed. You send a refund from your own wallet to an address the customer confirms, then record the transaction hash on the order.

Should I refund to the address the payment came from?

No. If the customer paid from an exchange, that address belongs to the exchange, and funds sent there may never reach the customer. Always ask for a refund address in writing.

What happens to payments sent after the invoice expired?

Payments broadcast right at the deadline are still detected during a short grace period. Later payments reach your wallet, and you can apply them with Mark as paid manually.

Can I change the underpayment tolerance?

Yes. It is a gateway setting from 0 to 5%. The default of 0.5% covers small rounding differences.

Accept crypto on your store today

Self-hosted, non-custodial, zero fees. Lifetime license.