| 开发者 |
dufresnesteven
tellyworth |
|---|---|
| 更新时间 | 2026年6月24日 09:38 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv3 or later |
| 版权网址: | 版权信息 |
Payment-Signature header, the plugin responds with HTTP 402 and a PAYMENT-REQUIRED payload describing how to pay. Bots, API clients, and browser-wallet users can sign a USDC transfer, retry the request, and get the response.
Use it to:
If the request does not carry a valid Payment-Signature header, the plugin returns HTTP 402 with a PAYMENT-REQUIRED response header containing the encoded x402 PaymentRequirements. Clients sign the requirements and retry the request.
Only if you set Audience to "Everyone." The default is "Only bots/crawlers" so humans see posts as normal and only detected bot/agent traffic gets a 402.
No. x402 uses EIP-3009 transferWithAuthorization; the facilitator pays gas. You only need USDC inbound.
Coinbase CDP secrets are stored in their own wp_options row, or can be supplied via a wp-config.php constant or environment variable so they stay out of the database entirely.