BEP20 payments confirm at network finality, one to two seconds

Paymos lets a business accept USDT and USDC payments over BNB Smart Chain (BSC) using the BEP20 token standard. The customer chooses BSC at checkout, sends the exact invoice amount, and the merchant receives the same asset in a Paymos balance after the required confirmations.

What can you accept on BSC?

Paymos supports two payment assets on BNB Smart Chain:

• USDT (BEP20)
• USDC (BEP20)

BNB is not an invoice payment asset in Paymos. A payer's wallet may require BNB to pay the blockchain fee for sending a BEP20 token, but that network charge is separate from the amount credited to the merchant.

If a customer holds USDT or USDC on another network, they must select that network instead. A token symbol alone is not enough: the asset and network must both match the invoice.

How a BEP20 payment works

1. Your store creates an invoice through Hosted Checkout, Embedded Checkout, Payment Links, the Low-Code SDK, a CMS plugin, POS, or the REST API.
2. The customer selects USDT or USDC on BNB Smart Chain.
3. Paymos assigns a dedicated deterministic address to that invoice.
4. The customer sends the displayed asset and amount on BSC.
5. Paymos detects the transaction and applies its confirmation policy.
6. The confirmed amount is credited to the merchant's balance in the same asset.

Invoice status changes can be delivered through HMAC-SHA256-signed webhooks. This keeps the payment, order, customer, and settlement connected without requiring a merchant to build blockchain monitoring.

BSC confirms at network finality

Paymos does not promise one fixed confirmation time for every BSC payment. BSC reaches network finality in about one to two seconds, so a payment is confirmed at that finality rather than at a depth that changes with the amount.

Your application should use the invoice status returned by Paymos rather than treating a wallet broadcast or a single block as final. Network congestion, wallet behavior, and chain conditions can affect how long a payment remains pending.

Who pays the BSC gas fee?

The payer's wallet pays the BNB Smart Chain network fee when it sends USDT or USDC. This fee goes to the network, not to Paymos, and its value can change with chain conditions. Paymos therefore does not publish a guaranteed fixed BEP20 gas cost.

Paymos covers the network cost of accepting and consolidating the payment. Standard pricing is 1.0% per settled invoice; Enterprise pricing is 0.3% on request. There is no setup fee, monthly fee, minimum volume, reserve, rolling reserve, or fee for an unpaid, expired, or cancelled invoice.

Same-asset settlement without a hidden conversion

A USDT payment is credited as USDT, and a USDC payment is credited as USDC. Paymos does not force an intermediary conversion or hide a charge inside the exchange rate.

Balances are maintained per asset rather than per network. If the same supported asset arrives through different networks, it contributes to that asset balance. When withdrawing, the merchant chooses an available payout network and sends funds only to a whitelisted address.

Paymos does not add a processing commission to withdrawals. Whether a network fee applies, and how large it is, depends on the payout network chosen; whichever one you take, the fee comes in under the route's own cost.

When BSC is a useful payment option

BSC is useful when customers already hold USDT or USDC in BEP20 form and can pay the network fee in BNB. It gives them an additional supported rail without changing the merchant's integration or forcing the merchant to maintain a separate blockchain listener.

It is not automatically the best network for every customer. Availability in the payer's wallet, the correct token-network pair, current network conditions, and the payer's gas balance matter more than a generic “cheapest network” claim. Offer BSC alongside the networks your customers actually use.

Integration and custody controls

The same Paymos integration can expose BSC together with other enabled networks. Hosted and embedded checkouts handle the payment instructions; API users can create invoices and receive signed status updates directly.

Outgoing transactions are signed on isolated infrastructure. Withdrawal whitelisting adds a separate destination control for merchant payouts.

Frequently asked questions

Is BEP20 the same as BSC?

BSC, also called BNB Smart Chain, is the blockchain. BEP20 is the token standard used by assets such as the supported USDT and USDC on that network.

Can I accept both USDT and USDC on BSC?

Yes. Paymos supports both USDT and USDC on BNB Smart Chain. The customer must send the asset selected on the invoice.

Can a customer pay a BSC invoice from another network?

No. The token and network must match the invoice. For example, USDT sent on Tron is not a USDT BEP20 payment.

Does the customer need BNB?

The sending wallet may need BNB to pay the BSC network fee. BNB is not added to the merchant's invoice balance.

Does Paymos convert USDT to USDC?

No. Settlement remains in the asset that was accepted: USDT stays USDT and USDC stays USDC.

How do I start accepting BEP20 payments?

Choose a Paymos integration, enable the supported BSC assets, and create an invoice. For network selection context, see the stablecoin networks guide and the TRC20 vs ERC20 vs BEP20 comparison.