BNB Chain in Coinvay’s checkout refers to its configured BNB Smart Chain mainnet route. Merchants can offer native BNB and the configured USDT representation when enabled. Correct network identification and reliable blockchain access are essential to verifying those payments.
Use a precise network description
BNB Smart Chain mainnet uses chain ID 56. Other BNB-branded products or testnets should not be treated as the same payment route. The familiar EVM address format is compatible with many chains but does not identify which one a customer selected.
For example, a gaming marketplace may let a buyer pay native BNB on BSC. A withdrawal made on another network does not settle that invoice simply because the account text looks identical. Name the chain beside the amount and address throughout the payment journey.
Check the token representation as well as the RPC
If offering the configured USDT contract, understand the token representation and its issuer or pegging arrangement. A ticker is not sufficient evidence of origin. Native BNB and a contract token have different verification paths, even though both use the same chain.
Payment monitoring also needs dependable RPC access. Public endpoints can have rate limits or method restrictions, especially for log scanning. An unavailable provider should produce a retryable operational state, not an automatic paid status. Merchants and operators should inspect current provider capabilities before relying on unattended monitoring.
Keep network receipt separate from fulfillment
Coinvay currently applies a fifteen-confirmation policy for this route and checks successful canonical evidence, recipient, exact amount and quote timing. A public explorer is useful for investigation, but its page is not an authenticated instruction to fulfill an order.
Retain the actual hash with the invoice reference. If callbacks are used, handle repeated events without creating duplicate delivery. A payment gateway’s blockchain connection is only one part of the order system; the merchant still controls inventory, access and customer support decisions.
Practical checklist
- Verify mainnet chain ID 56 and the selected token contract.
- Test RPC methods and rate-limit handling for monitoring.
- Base fulfillment on the confirmed invoice, with duplicate protection.
Common questions
Can a testnet BNB transfer pay a live invoice?+
No. Testnet and mainnet are separate environments. A live invoice must receive real-value evidence from its configured mainnet route.
Is an RPC error proof that payment failed?+
Not necessarily. It can mean the verifier could not currently read the chain. Keep the order pending, preserve the transaction reference and retry through the appropriate provider rather than assuming success or loss.
Sources and further reading
Primary references and Coinvay product documentation. Check the linked pages for current details.
AI-assisted drafting, published by Coinvay. Examples are illustrative. Read our editorial approach.