okx-x402-payment

Signing an x402 payment header involves decoding the 402 payload from the server response and generating a valid payment proof. You can use TEE wallet-session signing or local EVM private-key signing, with a confirmation prompt before the final HTTP header is assembled for replay.

The x402 payment protocol uses HTTP 402 status codes to gate API resources, requiring clients to decode the payment requirements and submit a signed payment header. You need to sign a payload whenever an onchain API resource returns a 402 status demanding cryptographic payment proof for access.

Yes, you can use a local EVM private key for x402 payments as a fallback when wallet access is unavailable. The skill supports local fallback signing to generate the required authorization, ensuring you can still access gated resources without a secure wallet session.

Yes, the x402 signing skill supports both v1 and v2 payload formats for cross-version header assembly. It correctly reconstructs the final request using the appropriate header, handling v2 PAYMENT-SIGNATURE formats as well as v1 X-PAYMENT formats.

To replay an HTTP request after decoding a 402 payment requirement, sign the payment proof and let the skill assemble the final HTTP header. The skill guides you through decoding, the signing decision, and reconstructing the original request with the proper payment header attached.