Service Provider Guide
Guide for service providers to accept payments from Kite Agent Passport agents via x402 or MPP.
Kite Agent Passport can pay any service that implements one of two open payment protocols:
- x402 — HTTP 402-based payment protocol with on-chain settlement
- MPP (Machine Payments Protocol) — an open standard by Stripe and Tempo for machine-to-machine payments (mpp.dev)
If your service already speaks either protocol, Passport agents can pay you today. If you are starting fresh, this guide walks through both options.
Your service settles on a chain Passport supports: Base (USDC), Polygon (USDC), Avalanche (USDC), Tempo (USDC), Solana (USDC or PYUSD), Robinhood (USDG), or Arc (USDC).
How Passport Pays Your Service
- An agent calls your service endpoint.
- Your service returns 402 Payment Required with payment terms.
- The Passport agent resolves payment using the user's approved spending session.
- Your service receives proof of payment, verifies it, and delivers the response.
The specifics of step 2–4 depend on which protocol you implement.
Option 1: Accept Payments via x402
x402 uses HTTP 402 responses to negotiate on-chain payments between agents and services.
Payment Flow

- Your service returns a 402 Payment Required response with payment details.
- The Passport agent obtains a signed payment authorization from the user's session.
- The agent resends the request with the
X-Paymentheader. - You verify the payment token and call a facilitator to settle on-chain.
- The facilitator executes the transfer to your wallet.
- You deliver the service response.
Facilitator
Passport pays with the x402 exact scheme, as defined in the x402 specification. Use any x402-compatible facilitator that settles on the network you advertise. The facilitator settles on-chain by calling transferWithAuthorization, which moves funds directly to your payee address.
Implementing x402 in Your Service
Step 1: Return 402 Payment Required
When a request arrives without valid payment, return a 402 with your payment terms:
{
"error": "X-PAYMENT header is required",
"accepts": [{
"scheme": "exact",
"network": "base",
"maxAmountRequired": "1000000",
"resource": "https://your-service.com/api/endpoint",
"description": "Your API - Description of your service",
"mimeType": "application/json",
"outputSchema": {
"input": {
"discoverable": true,
"method": "GET",
"queryParams": {
"param1": {"description": "Parameter description", "required": true, "type": "string"}
},
"type": "http"
},
"output": {
"properties": {
"result": {"description": "Result description", "type": "string"}
},
"required": ["result"],
"type": "object"
}
},
"payTo": "0xYourServiceWalletAddress",
"maxTimeoutSeconds": 300,
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {"name": "USD Coin", "version": "2"},
"merchantName": "Your Service Name"
}],
"x402Version": 1
}This example is for an EVM network. For Solana and other networks, follow the x402 specification for that network.
Key Response Fields:
| Field | Description | Example |
|---|---|---|
scheme | Payment scheme | exact |
network | x402 v1 network name of a supported chain. x402 v2 uses a CAIP-2 identifier such as eip155:8453 instead | base |
maxAmountRequired | Maximum payment amount in the token's smallest unit | 1000000 (1 USDC, 6 decimals) |
asset | Stablecoin contract on that network | 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 |
extra | The token's EIP-712 domain name and version, which the payer needs to sign the payment | {"name": "USD Coin", "version": "2"} (USDC on Base) |
payTo | Your service wallet address | 0xYourServiceWalletAddress |
maxTimeoutSeconds | Payment timeout | 300 |
merchantName | Your service name | Your Service Name |
outputSchema | API input/output specification | (see above) |
Step 2: Receive and Verify the Payment Token
The agent resends the request with an X-Payment header containing a base64-encoded authorization:
curl -H "X-PAYMENT: eyJhdXRob3JpemF0aW9uIjp7..." \
https://your-service.com/api/endpointStep 3: Settle via Facilitator
curl -X POST <your-facilitator>/settle \
-H "Content-Type: application/json" \
-d '{
"authorization": {...},
"signature": "0x...",
"network": "base"
}'Step 4: After confirming settlement, deliver your service response.
x402 Resources
- x402 Protocol Specification: https://docs.x402.org/introduction
Option 2: Accept Payments via MPP
MPP (Machine Payments Protocol) is an open standard co-authored by Stripe and Tempo. It extends the HTTP 402 pattern with support for multiple payment methods, session-based billing, and IETF standardization.
Payment Flow
- Agent requests a resource from your service.
- Your service responds with a 402 challenge containing payment terms.
- The agent submits a credential (proof of payment).
- Your service verifies the credential, returns a receipt, and delivers the resource.
Key Differences from x402
| x402 | MPP | |
|---|---|---|
| Payment methods | On-chain stablecoins | Stablecoins, fiat (Stripe), and more |
| Settlement | Via facilitator on-chain | Via Stripe or supported payment networks |
| Transport | HTTP headers (X-Payment) | HTTP, JSON-RPC, WebSocket |
| Session support | Via Passport spending sessions | Built-in payment channels |
Getting Started with MPP
- MPP Specification: mpp.dev
- Stripe MPP Blog: stripe.com/blog/machine-payments-protocol
Next Steps
- Pick your protocol — x402 for on-chain payments, or MPP for multi-method support.
- Set up a service wallet on a chain Passport supports (for x402) or connect Stripe (for MPP).
- Implement 402 responses in your service.
- Test with Passport — follow the Introduction to create an agent and pay your service.