Understanding amount differences and network fees

The amount shown for a product, the amount requested on a cryptocurrency invoice, and the total removed from a wallet can describe different things. Before paying, identify which value belongs to which step. A fee may be shown separately or reflected in the sending application's recipient amount. Do not guess the relationship from an older purchase or silently subtract a fee from the current invoice requirement.

Identify the amount the invoice requests

Open the payment page attached to the current order. Record the requested asset, network, and amount, together with the validity period. If a product price is displayed in another currency, do not use that price directly as the transfer value. Follow the invoice's current instructions rather than calculate an exchange rate from an article or a remembered market quote.

Check that the invoice belongs to the intended order and quantity. The 250+ follower category and separate follower-range category identify different inventory groups. Their public prices are current shopping context, not a substitute for the final payment instructions of a private order. Keep similarly named inventories and order references distinct.

Read the sending application's final review

Find the fields describing the transfer amount, fee, total debit, and amount the recipient will receive. Different applications may display these concepts differently. If the wording is unclear, consult that application's current official help before confirming. A form accepting an amount does not establish that the recipient will receive the same amount after the application's handling.

Do not select a different network solely because its displayed fee is lower. The asset and network must match the active invoice. Do not assume every fee is paid in the same asset or that a previous transaction's fee predicts the next one. This article does not state a universal fee percentage, minimum, or maximum; the actual invoice and sending application provide the relevant current information.

Compare values before sending

Place the invoice requirement beside the sending application's recipient amount and final review. Resolve a discrepancy before the transaction. Do not add an arbitrary cushion, subtract an estimated fee, or round the requested value by intuition. If an application cannot represent the required amount or network, pause rather than force a nearby option. For example, if the invoice asks for 50 USDT, the recipient amount on the final screen should read 50 USDT; if the app shows less because it deducts its fee from the figure you enter, adjust the entered figure until the recipient amount matches the invoice.

Check any required destination tag or memo and the full destination as well. A correct amount cannot fix a wrong destination or unsupported network. If you change any sending field, review the entire final screen again. Keep secrets out of this comparison: a merchant invoice never needs your seed phrase or private key pasted into an ordinary support message.

Investigate a difference after payment

If funds were already sent, preserve the transaction reference, asset, network, intended amount, displayed recipient amount, and time. Cryptomus's invoice integration documentation distinguishes payments whose amounts are below, equal to, or above the invoice requirement. That provider distinction shows how the payment gateway classifies a transfer; the store's order page and support then confirm what applies to your order, so wait for their instructions before sending anything additional.

Compare the provider's current invoice state with the store's order page. Ask verified support to explain the exact discrepancy through the contact page. If a current genuine provider flow explicitly requests a remaining amount, read its instructions carefully; otherwise do not improvise one. Record each transfer separately and include every transaction reference when you write to support; an extra amount is reviewed case by case against the order it was sent for. For help preparing the request, see Preparing a payment support request with safe evidence. Read the current terms before making another financial decision.

Frequently asked questions

Can I pay the catalog's displayed number directly from my wallet?

Use the actual invoice's asset, network, and requested amount. A catalog price may describe a different currency or purchase stage and is not itself a transfer instruction.

Should I subtract a network fee from the requested amount?

Do not subtract it by intuition. Check the sending application's recipient amount and current fee explanation so you understand what the invoice destination will receive.

What happens if I send more than the invoice requests?

An extra amount is reviewed case by case. Preserve the actual payment record and ask support about your specific order through the contact page; the refund policy has the current terms.

What if the sent amount and invoice requirement differ?

Record both values with the transaction and order references, then inspect the provider state and contact verified support. Do not send a guessed balance without a genuine current instruction.