Common Crypto Payment Mistakes and How to Fix Them

Crypto payments are simple when everything goes right: copy an address, send an amount, wait a minute. Small mistakes, though, can turn a quick purchase into a support case. Most mistakes fall into a handful of patterns, and most have a fix if both sides act carefully.

Wrong network

What happens. The customer sends USDC on Polygon when the checkout asked for Base.

Why it happens. Wallets and exchanges show many networks, and names can be confusing. Some exchanges default to a network the customer did not intend.

Fix. On EVM networks, the same address usually works across chains, so the funds arrive in the merchant's wallet on the other network. The merchant can verify the transaction and manually complete the order or refund. If the merchant receives through a smart contract wallet that only exists on one network, recovery is harder, which is why merchants should use standard addresses or deploy their wallet on every supported network.

Prevention. Show the network name clearly next to the amount and the address, and mention the network's gas token.

Missing or rounded cents

What happens. A checkout asks for 25.37 USDC and the customer sends 25.

Fix. Automatic matching fails, so the merchant matches by transaction hash, checks the shortfall and either asks for the difference or accepts it. Many merchants accept small differences for low-value goods.

Prevention. Explain that the cents identify the order. Offer copy buttons and QR codes to reduce manual typing.

Exchange fees deducted

What happens. The customer withdraws from an exchange that subtracts its fee from the amount, so less arrives than requested.

Fix. Treat as an underpayment and follow the same process as missing cents.

Prevention. Tell exchange users that the amount that arrives must match exactly and that they may need to add the withdrawal fee.

Fake or wrong token

What happens. The customer sends a token with the same name but a different contract, often a bridged version or a scam token.

Fix. Explain that the token is not accepted and return it if it has value. Scam tokens with no value should be ignored and never interacted with.

Prevention. Show the official token contract address at checkout and verify contracts in payment detection.

Paying twice

What happens. The customer thinks the first payment failed and sends another.

Fix. Complete the order with the first payment and refund the duplicate to the paying address.

Prevention. Show payment status clearly, with a message as soon as a payment is detected.

Late payments

What happens. The customer pays after the reservation window closed.

Fix. Keep watching for payments for a grace period. If the item is still available, complete the order. If not, refund or offer an alternative.

Prevention. Show a countdown and explain what happens if time runs out.

Merchant-side mistakes

Merchants make mistakes too:

Mistake	Consequence	Fix
Wrong decimals in code	Requests the wrong amount	Read decimals from verified configuration
No confirmation wait	Accepts a payment that later disappears	Set per-network confirmations
Reusing amounts across open orders	Payments matched to the wrong order	Keep amounts unique while orders are open
Receiving to a hot wallet used for experiments	Funds at risk	Use a dedicated secure wallet
No record of transaction hashes	Disputes are hard to resolve	Store payment references with orders

A support script that helps

When a customer reports a problem, ask for the same details every time: order ID, transaction hash, network and the wallet or exchange used. With those four details, almost every case can be resolved quickly.

Proud Globe's order page accepts a transaction hash directly, and the contact page asks for exactly these details, so unusual payments get sorted without guesswork.