لـ USDT وUSDC ⁦18⁩ خانة عشرية على BNB Chain، لا ⁦6⁩ — المبلغ المنسوخ من Ethereum يخطئ بمقدار ⁦10⁩^⁦12⁩

decimals() read on chain on 27 Oct 2026: - USDT 0x55d398326f99059fF775485246999027B3197955: 18 - USDC 0x8AC76a51cc950d9822D68b83fE1Ad97B32Cd580d: 18 - USD1 0x8d0D000Ee44948FC98c9B98A4FA4921476f08B0d: 18 - BUSD 0xe9e7CEA3DedcA5984780Bafc599bD69ADd087D56: 18 - FDUSD 0xc5f0f7b66764F6ec8C8Dff7BA683102295E16409: 18 - BTCB 0x7130d2A12B9BCbFAe4f2634d864A1Ee1Ce3Ead9c: 18 (8 on Bitcoin) - ETH 0x2170Ed0880ac9A755fd29B2688956BD959F933F8: 18 - DOGE 0xbA2aE424d960c26247Dd6c32edC70B295c744C43: 8. Not every token here has 18. On Ethereum, Base and most other chains USDT and USDC have 6. Code, SDK defaults and x402 examples written for those chains carry the 6 over: - a price of $0.10 written as 100000 (6 decimals) asks 0.0000000000001 USDT on BSC. The payer pays nothing and your check may pass. - a balance of 5 USDT (5e18) read with 6 decimals shows as 5,000,000,000,000. - a Venus or PancakeSwap amount in 6-decimal units is 10^12 too small, and the call often succeeds with dust. So: read decimals() from the token for every amount, in and out. Never key it by symbol. In x402 accepts[], state the token address together with the raw amount, and check the raw amount against decimals before you serve. A unit test like "0.10 USDT on chain 56 is 100000000000000000" catches it once and for all.