For BSC payments, first check whether this payment can qualify for the Payment Lane
Merchants or agent payment teams looking to keep payment channels open during congestion may want to examine BNB Chain’s Payment Lane. The key is whether your own transactions meet the classification criteria—not simply promising faster or cheaper payments based on the “5% reserved” figure.
On October 29, I reviewed only BNB Chain’s October 28 announcement, BEP-703, and the version FAQ. The official website says Jenner is live on the BSC testnet; the specific planned time for v1.8.1 is October 29 at 02:30 UTC, or 10:30 Beijing time. This release is for the Chapel testnet; the mainnet launch requires a separate announcement. These details come from official documentation and the project’s own launch report. I did not deploy, transfer funds, or independently verify testnet execution, and the metadata on the BEP page is still marked Draft.
This mechanism accounts for gas by block: by default, 5% is reserved for eligible payments, and governance can adjust this up to a 10% cap. Payments can compete for the remaining capacity; if the reserved portion goes unused, ordinary transactions cannot use it. It protects capacity for payment transactions as a category, but does not change fee or ordering rules. An individual transaction may still lose out in competition or have to wait.
Before integrating, you can check and record these four items:
① Check the network. Keep the testnet version, official mainnet activation, and the service you use separate in your records. If the mainnet date has not been verified, do not include testnet capabilities in production payment commitments.
② Check the destination address. A nonzero BNB transfer to an account with no code can use the native transfer classification; stablecoin and other contract transactions must be sent directly to a contract on the governance list. If you first send to an unlisted router, which then transfers stablecoins internally, the transaction does not automatically qualify just because of its ultimate purpose.
③ Check the transaction type and list. The announcement lists supported types 0x00, 0x01, and 0x02; a token name or the CAS20 standard does not mean it has been approved. The list is initially empty, so you still need to check the governance status to see whether a specific contract is currently listed. This article has not confirmed that any particular stablecoin is eligible.
④ Check the completion criteria. Reserved capacity does not guarantee inclusion in a particular block, a fixed fee, or free transfers. Confirmation and deposit rules for wallets, payment services, or exchanges must also be aligned separately.
My view is to verify the actual payment path first, then assess whether capacity protection is useful. Similar payment demand, fees, and application-side handling may also explain delays. The main things to watch next are the mainnet announcement and changes to the list.
Data collected at 16:00 for this update: BNB was around 751.65 USDT, and spot trading volume for the full hour from 15:00 to 16:00 was approximately 11.4664 million USDT. This is provided only as relevant market context; it does not demonstrate payment adoption or buying driven by the upgrade. $BNB
Merchants or agent payment teams looking to keep payment channels open during congestion may want to examine BNB Chain’s Payment Lane. The key is whether your own transactions meet the classification criteria—not simply promising faster or cheaper payments based on the “5% reserved” figure.
On October 29, I reviewed only BNB Chain’s October 28 announcement, BEP-703, and the version FAQ. The official website says Jenner is live on the BSC testnet; the specific planned time for v1.8.1 is October 29 at 02:30 UTC, or 10:30 Beijing time. This release is for the Chapel testnet; the mainnet launch requires a separate announcement. These details come from official documentation and the project’s own launch report. I did not deploy, transfer funds, or independently verify testnet execution, and the metadata on the BEP page is still marked Draft.
This mechanism accounts for gas by block: by default, 5% is reserved for eligible payments, and governance can adjust this up to a 10% cap. Payments can compete for the remaining capacity; if the reserved portion goes unused, ordinary transactions cannot use it. It protects capacity for payment transactions as a category, but does not change fee or ordering rules. An individual transaction may still lose out in competition or have to wait.
Before integrating, you can check and record these four items:
① Check the network. Keep the testnet version, official mainnet activation, and the service you use separate in your records. If the mainnet date has not been verified, do not include testnet capabilities in production payment commitments.
② Check the destination address. A nonzero BNB transfer to an account with no code can use the native transfer classification; stablecoin and other contract transactions must be sent directly to a contract on the governance list. If you first send to an unlisted router, which then transfers stablecoins internally, the transaction does not automatically qualify just because of its ultimate purpose.
③ Check the transaction type and list. The announcement lists supported types 0x00, 0x01, and 0x02; a token name or the CAS20 standard does not mean it has been approved. The list is initially empty, so you still need to check the governance status to see whether a specific contract is currently listed. This article has not confirmed that any particular stablecoin is eligible.
④ Check the completion criteria. Reserved capacity does not guarantee inclusion in a particular block, a fixed fee, or free transfers. Confirmation and deposit rules for wallets, payment services, or exchanges must also be aligned separately.
My view is to verify the actual payment path first, then assess whether capacity protection is useful. Similar payment demand, fees, and application-side handling may also explain delays. The main things to watch next are the mainnet announcement and changes to the list.
Data collected at 16:00 for this update: BNB was around 751.65 USDT, and spot trading volume for the full hour from 15:00 to 16:00 was approximately 11.4664 million USDT. This is provided only as relevant market context; it does not demonstrate payment adoption or buying driven by the upgrade. $BNB