An open protocol for verifiable receipts and internet-native payments
Built around the HTTP 402 status code, Verifx402 enables cryptographically signed receipts for API access without registration, complex OAuth flows, or blockchain interaction.
Ed25519 signatures provide cryptographic proof of unmodified content and authentic settlements.
Verify receipts in milliseconds. Money in your wallet in seconds, not days.
Built on RFC 7515 (JWS) and RFC 7807. Anyone can implement or extend the protocol.
Works with any HTTP stack via standard headers and status codes. Simple integration.
Verifx402 unlocks new verification models, offering developers and services a frictionless way to prove transactions without complex infrastructure.
Agents can use Verifx402 to generate verifiable payment receipts for API requests in real-time.
Provide instant access receipts for storage and compute services without account creation.
Issue cryptographic receipts for content access, enabling true micropayment verification.
Just a few lines of code to generate cryptographically signed receipts with Ed25519.
Generate a verifiable receipt:
receiptService.create({
  issuer: "https://yourapi.com",
  subject: "agent-123",
  purpose: "api_access",
  payment: { amount: "$0.01", scheme: "x402" }
});
// Returns cryptographically signed JWS receiptIf payment required, server responds:
HTTP/1.1 402 Payment Required Verifx402-Receipt: <JWS_TOKEN>
Verifx402 allows any web developer to verify crypto payments without blockchain complexity.
Protocol configuration and usage terms
VERSION
1.0
PROTOCOL
verifx402
USAGE
Conditional
Price
$0.001/request
Currency
USD
PAYMENT METHODS
x402{
  "version": "1.0",
  "protocol": "verifx402",
  "usage": "conditional",
  "attribution": "required",
  "consent": "optional",
  "retention": "30d",
  "license": "custom",
  "price": "$0.001/request",
  "currency": "USD",
  "payment_methods": [
    "x402"
  ],
  "rate_limit": "1000/hour",
  "free_quota": 100,
  "quota_period": "1h",
  "negotiate_endpoint": "/api/negotiate",
  "jwks_endpoint": "/.well-known/jwks.json",
  "receipt_header": "Verifx402-Receipt",
  "signature_algorithm": "EdDSA",
  "hash_algorithm": "SHA-256"
}The Verifx402 policy defines the terms, pricing, and requirements for using this service. Clients can fetch this policy programmatically from /.well-known/verifx402.txt
10/31/2025 at 8:27:08 AM
Subject: ABS
Purpose: research
Verifications: 1
Key: verifx402-1761771620
Expires: 10/31/2025
10/31/2025 at 7:18:24 AM
Subject: 21123
Purpose: content_access
Payment: 12 USD
Verifications: 1
Key: verifx402-1761771620
Expires: 10/31/2025
10/31/2025 at 12:37:56 AM
Subject: asdas
Purpose: content_access
Payment: 1 USD
Verifications: 2
Key: verifx402-1761771620
Expires: 10/31/2025
10/31/2025 at 12:37:07 AM
Subject: sdsd
Purpose: ai_training
Verifications: 0
Key: verifx402-1761771620
Expires: 10/31/2025
10/30/2025 at 11:29:26 PM
Subject: Rr
Purpose: content_access
Verifications: 0
Key: verifx402-1761771620
Expires: 10/31/2025
10/30/2025 at 9:45:36 PM
Subject: tok@gmail.com
Purpose: content_access
Payment: 0.01 USD
Verifications: 0
Key: verifx402-1761771620
Expires: 10/31/2025