duck-x402
v0.1.1
Published
x402 Payment Protocol with Kaia chain support
Downloads
4
Readme
duck-x402
Core TypeScript implementation of the x402 Payment Protocol with DuckChain support. This package provides the foundational types, schemas, and utilities that power all x402 integrations, including multi-network support for Base, Avalanche, IoTeX, Sei, Kaia, Kairos, and DuckChain.
Installation
npm install duck-x402Overview
The duck-x402 package provides the core building blocks for implementing the x402 Payment Protocol in TypeScript with comprehensive blockchain support. It's designed to be used by:
- Middleware implementations (Express, Hono, Next.js)
- Client-side payment handlers (fetch wrapper)
- Facilitator services
- Custom integrations
🦆 DuckChain Support
This package includes full support for DuckChain (Chain ID: 5545) with:
- Native Currency: TON
- Token Support: DUCK token at
0xda65892ea771d3268610337e9964d916028b7dad - RPC Endpoints:
https://rpc.duckchain.io,https://rpc-hk.duckchain.io - Block Explorer:
https://explorer.duckchain.io
🌐 Multi-Network Support
Supported networks include:
- Base: Mainnet and Sepolia testnet
- Avalanche: C-Chain mainnet
- IoTeX: Mainnet
- Sei: Mainnet and testnet
- Kaia: Mainnet
- Kairos: Mainnet
- DuckChain: Mainnet
Integration Packages
This core package is used by the following integration packages:
duck-x402express: Express.js middlewareduck-x402-hono: Hono middlewareduck-x402-next: Next.js middlewareduck-x402-fetch: Fetch API wrapperduck-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:
- Return 402 error responses with the appropriate response body
- Use the facilitator to validate payments
- Use the facilitator to settle payments
- 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 duck-x402-fetch or duck-x402-axios packages, you can manually integrate the x402 protocol in your client application. Here's how:
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 usedaccepts: An array of payment requirements you can fulfill
Select the payment requirement you wish to fulfill from the
acceptsarrayCreate the payment header using the selected payment requirement
Retry your network call with:
- The payment header assigned to the
X-PAYMENTfield - The
Access-Control-Expose-Headersfield set to"X-PAYMENT-RESPONSE"to receive the server's transaction response
- The payment header assigned to the
For implementation examples, we recommend reviewing our official client packages:
🚀 Quick Start with DuckChain
import { paymentMiddleware } from "duck-x402express";
app.use(paymentMiddleware(
"0xYourAddress",
{
"/duckchain-endpoint": {
price: "$0.01",
network: "duckchain", // 🦆 DuckChain support!
config: {
description: "DuckChain mainnet endpoint"
}
}
}
));📚 Documentation
For more information about the x402 Payment Protocol, visit our documentation.
