Integrate x402 with PonponPay

Create protected resource rules in the dashboard, then use the PonponPay SDK in server-side routes. The SDK handles the 402 challenge, payment verification, and settlement calls.

Integration flow

1. Create a Resource configuration on the x402 Agent Payments page in the dashboard.
2. Set the public resource URL, HTTP method, price, network, USDC contract, and settlement wallet.
3. Install and initialize the PonponPay SDK in a server-side route. Keep the API Key only in server environment variables.
4. Wrap the protected route with the SDK. Unpaid requests return 402; paid requests continue to the business response.
5. Review Payment records in the dashboard to track verification, settlement, and on-chain transaction status.

Server-side SDK examples

x402 must run server-side with API Key mode. Never expose API Keys or settlement logic in browser bundles.

import { ponponpayX402 } from '@ponponpay/sdk/x402';

const x402 = ponponpayX402({
  apiKey: process.env.PONPONPAY_API_KEY!,
  resource: {
    resource: 'https://merchant.example.com/api/premium-data',
    method: 'GET',
    price: '$0.01',
    maxAmountRequired: '10000',
    network: 'eip155:8453',
    asset: 'USDC',
    payTo: '0xYourMerchantSettlementWallet',
    description: 'Premium market data'
  }
});

export async function GET(request: Request) {
  const result = await x402.verifyAndSettle(request);
  if (!result.paid) {
    return result.required();
  }

  return Response.json({ data: 'premium payload' });
}

Supported networks

Current support is limited to the standard EVM exact flow using Circle USDC transferWithAuthorization.

Platform validation rules

• The scheme must be exact.
• network, asset, assetContract, payTo, and amount must match the resource requirement.
• resource URL and HTTP method are bound to the current request and must match.
• validAfter / validBefore must be within the allowed window, and each nonce can settle only once.
• The EIP-712 signature must recover authorization.from.

Unsupported chains

BSC, Tron, Solana, TON, and BTC are not part of the current standard EVM exact flow. Supporting them later requires a separate x402 scheme or PonponPay extension.