SDK & Receipts
Every successful payment through x402 Studio returns a signed receipt token (JWT). The x402layer SDK lets you verify these receipts server-side to gate premium content, confirm purchases, or audit payments. š GitHub: Singularity-SDK š JWKS Endpoint: api.x402layer.cc/.well-known/jwks.json š¦ All packages: see the platform-wide SDKs & Packages catalog.How It Works
When a payment is processed through x402, the worker signs a receipt JWT with a private key. The SDK verifies that signature using the corresponding public key from the JWKS endpoint ā proving the receipt is genuine and untampered.- Client hits your API ā Without a valid receipt token
- SDK middleware returns 402 ā With x402 payment instructions
- Client pays via x402 ā Receives a signed receipt JWT
- Client retries with receipt ā Token in header
- SDK verifies receipt ā Cryptographic signature check against JWKS public keys ā access granted
Installation
Node.js
Python
PyJWT, cryptography) are installed automatically. For FastAPI support: pip install x402layer-sdk[fastapi].
Receipt Token Contract
Receipt tokens are standard JWTs signed withRS256. Public keys are served from the JWKS endpoint for verification.
Receipt Claims
Node.js Quick Start
Python / FastAPI Quick Start
Where the Token Comes From
After a successful payment, the x402 worker includes the receipt token in the response header:Authorization: Bearer header or the X-X402-Receipt-Token header.
Security Notes
- š”ļø Always set
requiredSourceSlugin production ā prevents a receipt for endpoint A being replayed against endpoint B. - š Key rotation ā Publish a new JWKS key with a new
kid, then update the worker private key. Old tokens remain verifiable until they expire. - ā³ Expiration ā Receipt tokens have a limited lifetime. Always check the
expclaim (the SDK does this automatically).
Related
- Webhooks ā Receive server-side payment notifications
- Creating Endpoints ā Set up paid API endpoints
