Binance OnchainPay B402 请求签名、验证与结算准备清单
本文正文暫以英文原文展示，翻譯版本需完成來源複核後再發布。
已验证事实边界
1. Binance OnchainPay B402 request-signing documentation describes RSA-SHA256 signatures using a submitted public key. 2. The B402 signing documentation says signed requests include client identity, access token, signature and timestamp headers. 3. The B402 signing documentation says the server validates timestamp freshness and signature input. 4. The B402 signing documentation warns that JSON body bytes and timestamp values must match the signing payload. 5. Binance developer documentation states that documented interfaces are the supported reference for production integrations. 6. A B402 integration must treat verify and settle evidence as signed operational state, not as an unaudited front-end receipt.
收起完整分析
决策矩阵
文章表格：可橫向滑動，或聚焦表格區域後使用方向鍵。
| Check | What it means | Practical action | Unknown to keep explicit |
|---|---|---|---|
| Key custody | request signatures depend on private-key control | store signing material outside source code and screenshots | merchant portal recovery process |
| Serialization | signature verification can fail if body bytes change | serialize JSON once and sign the exact submitted string | middleware reformatting |
| Timestamp | timestamp freshness protects requests from replay | sync clocks and alert on skew before retries | cross-region failover drift |
| Verify call | payment verification should be an explicit signed readback | record verification result before fulfillment | temporary upstream failure |
| Settle call | settlement evidence should be separated from payment presentation | write a non-secret settlement record | provider-side exception handling |
| Retry logic | retries can duplicate signed requests if idempotency is absent | use deterministic request IDs and reconcile before retrying | unknown duplicate effects |
| Stop rule | stop when signature, timestamp, verify or settle evidence is inconsistent | hold payment automation until readback matches | support-only settlement dispute detail |
来源地图
- Binance Developer Docs：OnchainPay B402 API Request Signing（binance-b402-signing）
- Binance Developer Docs：Binance Developer Documentation（binance-developer-intro）
- Binance Developer Docs：Binance Pay Merchant API Specification Common Rules（binance-pay-common）
控制说明
1. Key custody
这一项要求读者先把公开来源翻译成操作规则。这里的含义是：request signatures depend on private-key control。可执行动作是：store signing material outside source code and screenshots。仍然未知的是：merchant portal recovery process。因此本文不会把未知部分包装成收益承诺、牌照承诺、审批保证、恢复保证、结算保证、可用性保证、价格暗示或平台排名。
2. Serialization
这里的含义是：signature verification can fail if body bytes change。可执行动作是：serialize JSON once and sign the exact submitted string。仍然未知的是：middleware reformatting。
操作测试也必须很窄。这就是本节保留边界的原因。
3. Timestamp
这里的含义是：timestamp freshness protects requests from replay。可执行动作是：sync clocks and alert on skew before retries。仍然未知的是：cross-region failover drift。
操作测试也必须很窄。这就是本节保留边界的原因。
4. Verify call
这里的含义是：payment verification should be an explicit signed readback。可执行动作是：record verification result before fulfillment。仍然未知的是：temporary upstream failure。
操作测试也必须很窄。这就是本节保留边界的原因。
5. Settle call
这里的含义是：settlement evidence should be separated from payment presentation。可执行动作是：write a non-secret settlement record。仍然未知的是：provider-side exception handling。
操作测试也必须很窄。这就是本节保留边界的原因。
6. Retry logic
这里的含义是：retries can duplicate signed requests if idempotency is absent。可执行动作是：use deterministic request IDs and reconcile before retrying。仍然未知的是：unknown duplicate effects。
操作测试也必须很窄。这就是本节保留边界的原因。
7. Stop rule
这里的含义是：stop when signature, timestamp, verify or settle evidence is inconsistent。可执行动作是：hold payment automation until readback matches。仍然未知的是：support-only settlement dispute detail。
操作测试也必须很窄。这就是本节保留边界的原因。
仍需明确的未知项
- merchant portal recovery process
- middleware reformatting
- cross-region failover drift
- temporary upstream failure
- provider-side exception handling
- unknown duplicate effects
- support-only settlement dispute detail
实用结论
Binance OnchainPay B402 集成应先解决签名纪律，再进入生产支付流程。当前 Binance developer documentation 说明 RSA-SHA256 request signing、public-key onboarding、timestamp header、client identity header，以及签名失败的排查规则；同时把 verify 与 settle 调用作为必须签名的 API interaction，要求 request body bytes 与 timestamp 与签名输入一致。实用结论是：把 B402 支付处理接入发货或会计前，应先定义 key custody、exact JSON serialization、timestamp tolerance、verification readback、settlement evidence 和 retry idempotency。 本文停在证据边界内，帮助读者决定下一步核验什么，而不是把公开文档改写成私人账户、钱包、回调、政策框架、结算路径或流动性头寸在任何未来条件下都能成功的承诺。
來源與證據
03- OnchainPay B402 API Request Signing · developers.binance.com
- Binance Developer Documentation · developers.binance.com
- Binance Pay Merchant API Specification Common Rules · developers.binance.com