okx-x402-payment

Sign x402 payments and return header-ready signatures with EIP-3009 fallback.

3|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/Pieverse-Eng/purrfect-skills --skill okx-x402-payment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: okx-x402-payment
Source: https://github.com/Pieverse-Eng/purrfect-skills/tree/main/okx/vendor/okx-x402-payment
Command: npx skills add https://github.com/Pieverse-Eng/purrfect-skills --skill okx-x402-payment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables secure signing and submission of x402 payments to access payment-gated resources, returning a verifiable proof that can be attached to requests.

Core Features & Use Cases

  • Securely sign x402 payments using a wallet session (TEE) to generate a signature and authorization for access.
  • Provide a local EIP-3009 signing fallback when no wallet is available, enabling offline signing.
  • Replay the original API request with the correct payment header to unlock gated resources and manage access control.

Quick Start

Sign an x402 payment for a gated resource and attach the resulting header to the original request.

Frequently Asked Questions about okx-x402-payment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sign an x402 payment to access gated resources?

To sign an x402 payment, the Skill decodes the 402 payload to extract network, amount, payTo, asset, and maxTimeoutSeconds, then returns a header-ready signature and authorization to attach to your original request.

Can I use EIP-3009 for local x409 payment signing when no wallet is available?

Yes, you can use EIP-3009 for local x402 payment signing. The Skill provides a local signing fallback using EIP-3009 to enable offline signing when no TEE-backed wallet session is available.

What is a TEE-backed wallet session for x402 payment signing?

A TEE-backed wallet session securely signs x402 payments within a Trusted Execution Environment to generate a verifiable signature and authorization for accessing payment-gated resources.

How do I attach payment proof to an API request after x402 signing?

After x402 signing, you replay the original API request with the correct payment header containing the returned signature and authorization to unlock the gated resources.

What data is extracted from a 402 payload during payment signing?

The 402 payload decoding extracts the network, amount, payTo, asset, and maxTimeoutSeconds parameters to construct the correct payment signature and authorization.

Does x402 payment signing support offline scenarios?

Yes, x402 payment signing supports offline scenarios through the local EIP-3009 signing fallback, which generates the required signature and authorization without a wallet connection.