Core Concepts

How Payments Work

Gate402 uses the x402 payment protocol - a standard for HTTP-based micropayments. Here's what happens:

1

Consumer requests data

Consumer → Gate402: "Give me data"

2

Gateway asks for payment

Gate402 → Consumer: "402 Payment Required - Pay $0.001"

3

Consumer pays

Consumer → Gate402: "Here's my payment signature"

4

Gateway verifies & settles

Gate402 → Blockchain: "Verify & settle payment"

5

Gateway forwards request to your API

Gate402 → Your API: "Forward request"

6

Your API responds

Your API → Gate402: "Here's the data"

7

Gateway returns data + receipt

Gate402 → Consumer: "Here's your data + payment receipt"

circle-info

Key Points:

  • Payments go directly to YOUR wallet (not held by Gate402)

  • Instant settlement on blockchain (Base or Solana)

  • No accounts needed for consumers (just a wallet)

  • Your API never changes (Gate402 handles everything)


Payment Networks

Gate402 supports:

Network
Chain ID
Currency
Fees

Base Sepolia (Testnet)

eip155:84532

USDC

Free

Base (Mainnet)

eip155:8453

USDC

Free

Solana Devnet (Testnet)

solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1

USDC

Free

Solana (Mainnet)

solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp

USDC

Free

Default: Base Sepolia (testnet) - perfect for testing!


Gateway Configuration

Each Gateway has:

Important Fields

circle-info

defaultPricePerRequest

  • Price in USD (e.g., 0.001 = $0.001 per request)

  • Charged for EVERY request to your API

  • Future: Set different prices per route

circle-info

evmAddress

  • YOUR wallet address

  • Payments go here instantly

  • Must be valid EVM address (0x...)

circle-info

secretToken

  • Optional: Verify requests came through Gate402

  • Add to your API: Check X-Gate402-Secret header

  • Prevents direct access to your origin URL