BNFCR Fee Payment Not Detected?

You created an invoice, sent the USDT or USDC, and the page still says the fee has not arrived. The matching is mechanical: a background poller watches on-chain deposit records and credits an invoice when exactly the invoiced amount arrives at the address on the chain the invoice names — within about 60 seconds of the transaction confirming. So if nothing has happened, one of four things is true. Only one of them — a transaction that has not confirmed yet — clears up on its own; the other three are things to get right before you send, because a deposit that misses the amount, the chain or the address cannot be credited automatically.

1. What each invoice status actually means

The invoice moves through a fixed set of states. Knowing which one you are in tells you whether to wait, check your transfer, or write to support.

2. The exact amount has to arrive

The fee is 0.5% of the converted amount, minimum 5.00 and maximum 10.00 USDT or USDC, and every invoice adds a small random fractional tail below 0.10. That tail is not decoration: it is the key that ties an on-chain deposit to your invoice. Round it off and there is nothing to match against.

The operative word is arrive. If you pay from an exchange, the exchange deducts its withdrawal network fee from the amount you send, so the sum that lands at the address is smaller than the sum you typed. Exchanges also require a minimum withdrawal of 5 USDT or USDC. Work backwards: pick a send amount such that the invoiced amount, tail included, is what actually arrives.

3. An exchange "internal" or "free" transfer is invisible

An exchange "internal" or "free" transfer bypasses on-chain deposit records and will not be matched — and verification runs against exactly those records, through a third-party deposit-monitoring API. Force a real on-chain withdrawal. A transfer that never reached the blockchain cannot be matched, no matter how long you wait.

4. Chain and address must be the ones on the invoice

Each invoice names one asset (USDT or USDC), one chain (Solana, Polygon or BSC) and one address. Copy both from the invoice screen, and check the network selector in your sending app against the chain the invoice names. There is no automatic recovery here: a deposit that does not match the exact invoice amount, or that was sent on the wrong chain or to the wrong address, cannot be credited automatically and may be unrecoverable. Our terms say so plainly.

5. The window is 30 minutes, late payments are credited for 24 hours

The payment window on the invoice is 30 minutes. A chain can be slow, or an exchange can hold a withdrawal for review, so the window can run out while your transfer is still in flight. A payment that arrives late is still credited for 24 hours — which is what the PAID_LATE status records.

So a window that has run out is not a reason to send the fee a second time. Re-check the invoice, and if you are unsure what state it is in, write to support@bnfcrconvert.com rather than paying twice.

6. Paid and matched, but the conversion will not run

Once an invoice reads PAID or PAID_LATE, the swap is a separate step that uses your Binance API key again. Two things to know:

• Use the same API key that created the invoice. The conversion is refused if the credentials do not match the ones the invoice was created with — so do not delete and re-create the key between paying and converting.
• The key needs its Futures permission to still be active. If Binance rejects the convert request, the service reports a Binance upstream error and the conversion does not run — which our terms treat as a conversion that failed on the Binance side.

If the fee was paid and the conversion then failed on the Binance side, write to support@bnfcrconvert.com. Under our terms the operator may then return the fee minus on-chain gas costs, within 30 days, to a refund address you provide — at the operator's discretion, so it is a request and not an automatic entitlement. Once a conversion has succeeded there is no refund.