If you sent more crypto than a swap order requested, preserve the original order and verify how much actually reached its deposit destination. Do not assume the extra amount will automatically increase the payout or be returned under the original quote. Contact the service through the genuine order's support channel and ask for a decision tied to that specific receipt.
Measure the difference in the same asset
Record the requested sending asset, network and amount before comparing anything. The order's expected deposit and expected payout are different values, often in different assets. A wallet's total balance reduction may also include a network fee. Comparing that total with the requested deposit can create an apparent overpayment that the receiving address never got.
For Bitcoin, inspect the actual deposit output rather than all inputs or the entire transaction value. The Bitcoin transaction guide explains inputs, outputs and change. A change output returning to the sender is not an additional payment to the exchange. Keep the recipient output identifiable in your evidence.
For tokens, compare the actual intended receipt and the token's precise identity. An entered sending quantity, a display rounded to fewer decimal places and a receiving amount affected by token rules can differ. First establish whether there really is a surplus of the correct asset. Do not use a fiat valuation change as a substitute for the coin amount.
Keep the quote and receipt side by side
| Evidence item | What to preserve | Why it matters |
|---|---|---|
| Original order reference | The genuine order ID and page | Identifies the service case |
| Requested deposit | Asset, network and exact coin amount | Defines what the order asked for |
| Original receive estimate | Output asset and amount with the saved quote | Avoids silently assuming a new quote |
| Actual chain receipt | Hash, destination and specific movement | Establishes what arrived |
| Apparent surplus | Difference in the same asset and units | Separates arithmetic from policy |
| Order state | Awaiting, processing, completed or another actual label | Shows what the service has already done |
| Support decision | The agreed treatment of the extra amount | Prevents an assumption becoming a claimed promise |
| Any refund | Asset, network, destination and separate result | Keeps the return distinct from the original payout |
Save the original details before editing an amount field or starting another order. A fresh calculation is useful for a new request but does not document what the earlier quote said. Preserve the time of the original instruction and the time of your check so support can compare the same records.
Ask for a policy decision rather than predicting one
Different services document different payment-handling processes. For example, Bitrefill's overpayment help describes invoice-based excess-refund options that depend on the payment method. Simplex's payment guidance describes its own refund conditions. These are independent product examples, not KOT.CASH rules.
For your actual order, ask whether the service will process the received amount, retain the original exchange amount and handle the surplus separately, or propose another documented resolution. These are questions to settle, not outcomes this article promises. Ask for any applicable fees, eligible amount and required action in the same conversation.
Do not calculate a supposedly owed extra payout by applying the old quote mechanically. A service's treatment can depend on its order rules and the point at which the discrepancy was discovered. The arithmetic can establish an extra deposit; it does not create a new agreed exchange rate or determine a refund fee.
Use a fictional reconciliation before contacting support
Suppose an order requested 0.010 BTC and the verified receiving output contains 0.012 BTC. The difference is 0.002 BTC. That is an illustrative coin-amount comparison, not a live quote. If the wallet also paid a network fee, keep that fee separate from the 0.012 output. The recipient did not receive the fee merely because the sender's balance fell by more.
Now suppose the order payout has already been sent for the original amount. That payout and the unresolved surplus are separate records. Ask which part of the case remains open instead of describing the entire transfer as missing. If no payout has occurred, ask whether processing is paused and what decision is needed. The same difference in deposit amount can arise at different service stages.
If several transfers were sent, list each one. Do not merge their hashes into a single apparent payment or reuse a receipt already assigned to another order. A combined total needs an explicit connection to the order and the receiving service's records. Screenshots can support context, but the underlying identifiers make the arithmetic reproducible.
Prepare any return destination independently
If a return is offered, confirm which asset and network it will use and provide a destination you control that supports them. A sender address displayed in the deposit transaction is not automatically the right personal refund address. The deposit may have come from a custodial platform, and Bitcoin does not reduce every payment to one personal From address.
A refund request does not itself prove that the refund was approved or sent. Keep the agreed net amount, destination and case reference, then track the return separately when a transaction reference exists. Do not pay an unexplained matching amount to unlock the surplus. Authenticate any new instruction through the existing official case before taking another action.
Send one concise overpayment report
- Quote the original order reference and the exact requested deposit.
- Provide the actual network, asset, transaction hash and receiving movement.
- Show the surplus calculation in coin units, excluding unrelated fees and change.
- State whether any normal order payout has already arrived.
- Ask the service to confirm the treatment, any cost and the required next step.
- If a return is agreed, confirm its asset, network and controlled destination, then keep its execution separate.
The KOT.CASH workflow explains choosing an amount and tracking the order, but this does not establish a universal overpayment tolerance or automatic surplus policy. Keep case-specific treatment explicit. For record lookup, see checking a transaction hash. Before your next no-account swap, compare the final wallet recipient amount with the current order instructions while keeping network costs separate.
FAQ
Does a crypto overpayment automatically increase my swap payout?
Do not assume that; the service must confirm how it handles the extra deposit. Preserve the original quote and the actual receipt before agreeing to any revised treatment.
What records help with a crypto refund after overpayment?
Keep the order ID, requested amount, actual receiving movement and a same-asset surplus calculation. Track an existing payout and any proposed return separately.
Should the refund address be copied from the original transaction's sender?
Not automatically; a custodial sender or a multi-input transaction may not identify a personal receiving destination you control. Confirm the return asset and network and provide an appropriate controlled address.