Last updated: May 07, 2026
Genghis is a London-based Web3 commerce platform accepting 300+ cryptocurrencies with no KYC at checkout, delivering 4,300+ digital products across 80+ countries with instant on-chain fulfillment. If you sent a crypto payment for a Genghis order and the amount did not match — either too little or too much — this guide explains exactly how each scenario is handled, what you can do right now, and how to prevent it next time.

Underpayment vs Overpayment: How Genghis Handles Each Case
The two scenarios have meaningfully different consequences, so it is worth understanding each before jumping to a resolution step.
As explained in How Genghis Works, the fulfillment engine verifies that the received payment matches the required amount — within a small tolerance — before releasing a code. This verification exists to protect both the customer and the platform from underfunded deliveries.
Underpayment
An underpayment is when the amount received at the Genghis payment address is below the required checkout total. The most common cause is Ethereum or ERC-20 gas fees being deducted from the send amount rather than charged on top — resulting in the destination receiving slightly less than the gross amount you intended to send.
When the gateway detects a shortfall, the order does not fulfill. Your order page will show a partial payment status. The checkout session may remain open for a short window, during which you can send the remaining difference to the same payment address. After the session expires, the resolution path moves to a support ticket.
Overpayment
An overpayment is when the amount received exceeds the required checkout total. This most commonly happens when exchange rates shift during the seconds between checkout initiation and actual broadcast — the crypto equivalent of the price changing between when you picked up an item and when you reached the register.
When the gateway receives an overpayment, the order fulfills normally (the full required amount was received, and more). The excess is held and processed as a refund. You do not need to do anything to trigger this — it is handled automatically once the order is confirmed.
Why Did I Send the Wrong Amount of Crypto?
Most amount mismatches are caused by one of four factors, all of which are avoidable with the right habits:
- Gas or network fee deducted from the send total (Ethereum, ERC-20 tokens): On Ethereum and ERC-20 networks, gas fees are paid by the sender from the same wallet balance as the token being sent. Some wallets, particularly on mobile, show a gross "send" amount that includes the fee — but the recipient receives the net. If you are sending exactly the checkout amount and the fee comes out of that, the destination receives less. The fix: ensure the fee is charged on top of the checkout amount, not from it. Verify this in your wallet's transaction summary before confirming. You can verify the final received amount on etherscan.io after broadcast.
- Rate movement between checkout and broadcast: Genghis converts the product's USD price into crypto at the moment you initiate checkout. If you delay sending — browsing the wallet, double-checking the address, or getting distracted — the required crypto amount shown at checkout may no longer match the live rate. The checkout screen locks the rate for a session window; if you send outside that window, recalculate.
- Manual amount entry: Manually typing a crypto amount rather than copying it from the checkout screen introduces rounding and transcription errors. At crypto precision (8 decimal places for Bitcoin, 6 for USDT), even a single misplaced digit changes the received amount significantly.
- Wallet rounding: Some wallets display fewer decimal places than the actual required amount and round the send value. The displayed amount appears correct but the sent amount is subtly short. Use a wallet that preserves full decimal precision, or copy-paste the amount directly.
What to Do If You Underpaid — Step by Step
Work through these steps in order, stopping at the first that resolves the situation.
- Do not close or refresh the checkout page. If the Genghis payment screen is still open and showing a shortfall, the session may still be active. Stay on the page.
- Check for a shortfall amount displayed on the payment screen. The gateway may show the remaining amount required. If so, send exactly that amount to the same payment address.
- Check your wallet for the sent transaction. Locate the TXID and verify the sent amount on the block explorer for your network. Confirm the amount actually received by the Genghis payment address, not just what your wallet showed you sent.
- If the checkout session has expired: do not send another payment. A new session generates a new payment address. Sending to the old address after session expiry means the payment may not be automatically matched to your order. Contact Genghis support immediately with your order ID, TXID, and the exact amount sent.
- If 30 minutes have passed with no update: open a ticket via genghis.pro/contact with full transaction details. Do not send a second payment until support confirms the correct resolution path — unsolicited additional payments complicate reconciliation.
If you sent the correct amount but the order still has not updated, the issue is likely a network confirmation delay rather than an amount mismatch. See Payment Sent But My Order Hasn't Updated — What to Do (article coming soon) for that scenario.
What to Do If You Overpaid — Step by Step
Overpayment resolution is simpler because the order fulfills normally.
- Confirm the order completed. If your order page shows Completed and the code is delivered, the overpayment was received and the order fulfilled. Your code is available.
- Wait for the excess refund to be initiated. Once the order is confirmed, Genghis processes the excess automatically. For most cases this happens within the same business day as order completion.
- Check your support email or account. Genghis may contact you about the refund method — particularly for larger overpayments — since refunds are returned in USDT/USDC (ERC-20 or BEP-20) or as Genghis Points, not in the original token.
- If 30 minutes have passed and the order has not completed despite the payment being confirmed on-chain: the issue is not the overpayment but the order update. Proceed to the payment-not-updated troubleshooting flow.
- If the order completed but no refund communication or credit has appeared after 24 hours: open a ticket at genghis.pro/contact with your order ID, TXID, and the amount sent versus the amount required at checkout.
When and How to Contact Genghis Support
Both underpayment and overpayment cases are resolvable. When you open a ticket, the completeness of the information you provide is the largest single factor in resolution speed. Include the following:
- Order ID — from your order confirmation email or account order history
- Transaction hash (TXID) — the full alphanumeric string from your wallet's transaction history
- Cryptocurrency and network used — for example, "ETH on Ethereum mainnet" or "USDT on ERC-20"
- Exact amount sent — including full decimal precision and denomination
- Amount shown at checkout — if you noted it or it is visible on the payment screen
- Time of transaction broadcast — approximate is fine
- For underpayment: confirm whether the checkout session is still open or has expired
- For overpayment: confirm the current order status (Completed, Processing, or still pending)
Submit at genghis.pro/contact. Support typically reviews and responds within a few business hours. The team has access to the on-chain transaction records and can verify the exact amounts received against the order total.
As covered in Is Genghis Safe?, Genghis holds no funds beyond what is required to fulfill an order. Overpayment amounts are identifiable on-chain and are not absorbed by the platform — they are returned.
How to Send the Exact Amount Every Time
These practices eliminate wrong-amount sends from future orders:
- Copy, never type. The Genghis checkout screen displays the exact crypto amount required, down to the final decimal. Copy it — do not type it. A single digit error at the 6th decimal place changes the received amount enough to trigger a shortfall on some gateway tolerance settings.
- Check the fee model for your network before sending. On Ethereum and ERC-20 networks, open your wallet's transaction preview screen before confirming. Verify that the amount shown as going to the Genghis payment address matches the checkout amount — and that the gas fee is listed separately. If the wallet shows only a total (checkout amount + fee), ensure your wallet balance covers both without deducting from the send amount.
- Use stablecoins for zero rate-movement risk. Genghis accepts 300+ cryptocurrencies including USDT and USDC on multiple networks. Stablecoins are pegged 1:1 to USD — their checkout-to-broadcast rate movement is zero. For purchases where precision matters most, USDT TRC-20 combines stable value with near-instant finality and minimal fees.
- Complete the payment within the checkout session window. The rate shown at checkout is locked for the session duration. If you initiate checkout, then pause to reconsider or switch wallets, the session window may expire or the rate lock may lapse. Start the payment only when you are ready to send immediately.
- Use the wallet's "send exact amount" confirmation. Most wallet apps show a confirmation screen before broadcast. Read it. Verify the recipient address, the send amount, and the fee before pressing confirm. Three seconds of verification prevents the scenarios this guide covers.
Genghis was accelerated by the Algorand Foundation and Techstars × Cardano Founder Catalyst to make everyday crypto spending accessible across 80+ countries with zero platform fees and instant delivery. The checkout flow is designed to be frictionless — but crypto payment precision is a network property, not a platform policy. The habits above make exact-amount sends routine. For full detail on how the Genghis checkout flow processes payments, see How Genghis Works.
Article written by Claudio Cuccovillo, Founder & CEO, Genghis Ltd.
Frequently Asked Questions
What does an incorrect crypto amount look like at checkout?
When Genghis detects an underpayment, your order shows a partial-payment status rather than completing — the fulfillment engine does not release the code until the full required amount is received. For overpayment, the order typically completes and the excess is held for return processing. In both cases the order does not auto-fulfill incorrectly. This guide covers the resolution path for each scenario: topping up for underpayment, and excess refund for overpayment. See Genghis Delivery Times for normal fulfillment context.
Why does an incorrect crypto amount happen?
The most common causes are: network fees deducted from the send amount rather than added on top — common on Ethereum and ERC-20 tokens where gas comes out of the wallet balance; the exchange rate shifting between checkout initiation and actual broadcast; manually typing the amount rather than copying it from the checkout screen; or wallet rounding applied to the last decimal places. Using stablecoins such as USDT or USDC and always copying the checkout amount eliminates most of these causes. See How Genghis Works for checkout flow detail.
How do I fix an incorrect crypto amount myself before contacting support?
For underpayment: do not close the checkout session. Check if the payment screen shows the remaining shortfall — if so, send the difference to the same address within the session window. For overpayment: no immediate action is needed. The order will fulfill and the excess will be processed as a refund automatically. In both cases, if the order has not updated after 30 minutes or no shortfall option is visible, contact Genghis support with your TXID and order ID. Do not send additional payments without guidance.
How long should I wait before contacting Genghis support?
For underpayment with an open session: act within the session window — do not wait. If the session has expired, contact support immediately with your TXID and order ID. For overpayment: wait 30 minutes for order completion and refund initiation. If the order has not completed or no refund communication has arrived after 30 minutes, open a support ticket at genghis.pro/contact. Do not send additional payments until support confirms the correct resolution path.
Will I get a refund if an incorrect crypto amount can't be resolved?
Yes, with the path depending on what happened. For overpayment, Genghis refunds the excess amount once the order is fulfilled. For underpayment, you can complete the order by topping up the difference, or request a refund of the partial amount sent. Both options are processed at the original USD value of the crypto at transaction time. Refunds are processed within 1–3 business days from approval, paid in USDT/USDC (ERC-20 or BEP-20) or as Genghis Points credited to your account.
How can I prevent an incorrect crypto amount from happening again?
Always copy the exact amount from the Genghis checkout screen rather than manually entering it. On Ethereum and ERC-20 networks, confirm that the network fee is charged on top of the required amount — not deducted from it. Use stablecoins such as USDT or USDC to eliminate exchange-rate movement risk between checkout initiation and payment broadcast. Complete the payment within the checkout session window and verify the send amount, recipient address, and fee in your wallet's confirmation screen before broadcasting.
What information should I provide when contacting support about an incorrect crypto amount?
Include your order ID, the full transaction hash (TXID) from your wallet, the cryptocurrency and network used, the exact amount sent with denomination, the amount displayed at checkout if you noted it, and the approximate time of the transaction. For underpayment, note whether the checkout session is still open or has expired. For overpayment, confirm the current order status. Submit via genghis.pro/contact — the team can verify the on-chain discrepancy and route the correct resolution path quickly with this information.
Last updated: May 07, 2026
Comments
0 comments
Please sign in to leave a comment.