> For the complete documentation index, see [llms.txt](https://support.trybit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.trybit.com/payments/payment-issues.md). # Payment Issues Common invoice payment issues — from choosing a wallet and network to incorrect amounts, overpayments, duplicates, and contacting support. We've gathered in one place everything that can go wrong when paying an invoice, and what to do in each case — for both customers and merchants. ### Choosing a wallet and network — how to avoid mistakes You can pay from any wallet or exchange, but it's important to keep in mind in advance: * different wallets and exchanges set their own minimum send amounts; * some exchanges charge their own withdrawal fee — this can reduce part of the amount that reaches the address; * you must send strictly in the currency and network specified on the [payment page](/payments/payment-page.md) — with an error in the network or address, Trybit cannot reliably confirm the invoice, since it doesn't have access to those funds. For accuracy, we recommend using non-custodial wallets (such as Trust Wallet) — in these, the network fee is visible and added on top of the amount rather than deducted from it. {% hint style="info" %} **Example Calculations:** * Exchange (e.g., Binance): an order for 100 USDT, exchange withdrawal fee — 1 USDT → only 99 USDT reaches the address → to pay the invoice in full, you need to send 101 USDT. * Non-custodial wallet (e.g., Trust Wallet): an amount of 0.001 BTC + a network fee of 0.000033 BTC is added on top when sending → exactly 0.001 BTC reaches the address, as expected. {% endhint %} ### The invoice isn't confirming — what to do This is most often a matter of network confirmation time — see the table on the [Invoice Statuses](/payments/invoice-statuses.md) page. If the amount and address are correct, no further action is needed — the invoice will confirm itself once the required number of confirmations is reached. If the invoice has expired but payment was already sent before the deadline, it won't be credited automatically. You need to contact support with the invoice number (INV), the transaction's txID, and the address the funds were sent to (see [Frequently Asked Questions](/end-users.md), "The invoice expired, but I already sent payment"). ### Forgot to include a MEMO/Comment, or paid in the wrong currency/network If a payment required a MEMO (tag) and it wasn't included, or the payment arrived in the wrong currency or network, the decision on crediting it is made on a case-by-case basis, after contacting support. The terms and process for a technical refund in such cases are [on the Refunds page](/payments/refunds.md). ### Sent the wrong amount (partial payment) The system automatically calculates and displays the minimum additional amount needed. What to do next — the customer pays the difference, the merchant manually confirms in the dashboard, or auto-confirmation by threshold — is covered in detail on the [Invoice Statuses](/payments/invoice-statuses.md) page. If the customer asks for a refund after confirmation, see [Refunds](/payments/refunds.md). ### Overpayment An overpayment is automatically credited to the merchant in full. It's important to understand: in the merchant's own system (for example, in a CMS or order database), the overpayment may not be reflected — the invoice was created for the original, smaller amount. The actual amount received, including the overpayment, can always be checked in the Trybit dashboard. ### The invoice was paid more than once (duplicate) If another transaction arrives for an invoice that already has the "Paid" status — for example, the customer accidentally paid the same invoice more than once — the repeat payment is not credited to the balance automatically. Crediting the second (and any subsequent) transaction to an already-paid invoice can only be done manually, by contacting technical support — with the invoice number (INV) and the TXID of all transactions. ### What you need to contact support For any inquiry about a payment issue — whether from the customer or the merchant — have the following ready: * **invoice number (INV)** — 8 characters, shown on the invoice and in the payment email; * **the TXID** — the blockchain transaction identifier, found in the wallet's or exchange's transaction history; * for an incorrect amount/network — the address the payment was sent to. ### The product or service wasn't delivered despite confirmed payment This is the merchant's responsibility, not Trybit's — the service's support team doesn't advise on products or services the customer is supposed to receive from the merchant after payment. {% hint style="success" %} If you have any questions or need help, you can contact our support via chat on the website and in your personal account, as well as reach us on Telegram. Support contacts are listed [on our website](https://trybit.com/support). {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://support.trybit.com/payments/payment-issues.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.