Catalog npm
PACKAGE EXPLORERView in registry

@0xcipher0/x402

npm

x402 Payment Protocol

Versions collected8
Direct dependencies34From release 0.6.14
Last observed20 Oct, 23:02 UTC

README

Current package documentation

x402

Core TypeScript implementation of the x402 Payment Protocol. This package provides the foundational types, schemas, and utilities that power all x402 integrations.

Installation

npm install x402

Overview

The x402 package provides the core building blocks for implementing the x402 Payment Protocol in TypeScript. It's designed to be used by:

  • Middleware implementations (Express, Hono, Next.js)
  • Client-side payment handlers (fetch wrapper)
  • Facilitator services
  • Custom integrations

Integration Packages

This core package is used by the following integration packages:

  • x402-express: Express.js middleware
  • x402-hono: Hono middleware
  • x402-next: Next.js middleware
  • x402-fetch: Fetch API wrapper
  • x402-axios: Axios interceptor

Manual Server Integration

If you're not using one of our server middleware packages, you can implement the x402 protocol manually. Here's what you'll need to handle:

  1. Return 402 error responses with the appropriate response body
  2. Use the facilitator to validate payments
  3. Use the facilitator to settle payments
  4. Return the appropriate response header to the caller

For a complete example implementation, see our advanced server example which demonstrates both synchronous and asynchronous payment processing patterns.

Manual Client Integration

If you're not using our x402-fetch or x402-axios packages, you can manually integrate the x402 protocol in your client application. Here's how:

  1. Make a request to a x402-protected endpoint. The server will respond with a 402 status code and a JSON object containing:

    • x402Version: The version of the x402 protocol being used
    • accepts: An array of payment requirements you can fulfill
  2. Select the payment requirement you wish to fulfill from the accepts array

  3. Create the payment header using the selected payment requirement

  4. Retry your network call with:

    • The payment header assigned to the X-PAYMENT field
    • The Access-Control-Expose-Headers field set to "X-PAYMENT-RESPONSE" to receive the server's transaction response

For implementation examples, we recommend reviewing our official client packages:

Downloads & popularity

Awaiting observations

No metric observations yet

Download counts and popularity will appear here as the collector receives them.

Versions 8

Collected releases
VersionPublishedDirect dependenciesOpen version
0.6.14Registry latest26 Oct 202534
0.6.1225 Oct 202534
0.6.1125 Oct 202534
0.6.1025 Oct 202534
0.6.925 Oct 202534
0.6.825 Oct 202534
0.6.725 Oct 202534
0.6.625 Oct 202534

Package advisories

0
No matching advisories collected

This describes our collected data; it is not a security assessment.

Repository

PENDING
coinbase/x402

Shared repository data · GitHub

License detected in repository
Not collected

Metadata history

Meaningful changes
Current collected state Current

Observed since 20 Oct, 23:02 UTC

No superseded metadata states collected. Unchanged observations do not create new revisions.

Record identity

package:f55ff65a5cea69031709830bf7de4b6daec5cdbe0e12f36ccd27b62347488b66