What to Do When a Client Underpays or Overpays
What happens when a client sends too little or too much in a crypto payment, and how to resolve it without manual digging.
Underpayment happens more often than you would expect. The client set a low network fee and the funds arrived short. Overpayment happens too, usually a typo when entering the amount. A solid payment gateway catches both and does not silently drop the order.
When a client sends less than the full amount
The payment gateway compares what arrived against what was invoiced. If the difference is within the allowed tolerance, the order counts as paid. If the difference is larger, the order gets a "partial payment" status and you see it in your dashboard.
At that point you decide: accept it as full payment, ask the client to top up, or issue a refund.
When a client sends more than the full amount
The extra funds sit on your balance. An overpayment does not block the order or create an error: the client paid more than needed, the order is marked paid. If you want to return the difference, you issue a partial refund from the dashboard.
How to reduce mistakes in the first place
The payment page shows the exact amount and the network before the client sends anything. That removes most wrong-amount errors. The network fee on the client's side depends on their wallet, not your gateway. It helps to tell clients up front: add a little extra for the network fee rather than subtracting it from the invoice total.
Refunds on your side are done through the dashboard or API, with no refund fee.
