okx-x402-payment

To sign x402 payments for gated resources, you use a wallet session for TEE-backed signing to generate a secure payment proof, then replay the original request with the assembled PAYMENT-SIGNATURE or X-PAYMENT header. This process automates access to paid resources without exposing private keys.

Yes, you can sign x402 payments offline using the local EIP-3009 signing fallback. If a wallet session is unavailable, this fallback allows you to sign with your own private key to generate the required payment proof for accessing gated resources.

The x402 payment protocol is a mechanism needed when a server responds with HTTP 402 to gate access to paid resources. It enables automated pay-per-use flows in on-chain environments by returning a cryptographic payment proof to authorize access.

No, signing x402 payments does not expose your private keys. The primary path uses a TEE-backed wallet session to securely sign transfers, and the local fallback uses EIP-3009 signing, ensuring your keys remain protected throughout the automated access flow.

After signing an x402 payment, the system automatically assembles the correct request header, either PAYMENT-SIGNATURE or X-PAYMENT, based on the server's requirements. It then replays the original request with the signed payload to grant access to the gated resource.

The primary limitation of the EIP-3009 local signing fallback is that it requires you to manage your own private key directly, whereas the primary path uses a secure wallet session for TEE-backed signing to generate payment proofs without local key exposure.