Choosing a protocol
Each payment channel has its own URL segment, credential format, and 402 response. Enable the ones that match how your clients pay.
Compare protocols
A project can enable several channels at once. Share the URL for the protocol that matches each client’s payment capability.
| Protocol | URL segment | Payment header | Plans |
|---|---|---|---|
| x402 | x402 | PAYMENT-SIGNATURE | Paid plans |
| x402 Testnet | x402-testnet | PAYMENT-SIGNATURE | Free and paid plans |
| MPP Tempo | mpp-tempo | Authorization | Paid plans |
| MPP Tempo Testnet | mpp-tempo-testnet | Authorization | Free and paid plans |
| MPP Stripe | mpp-stripe | Authorization | Paid plans |
Start on testnet
x402 Testnet and MPP Tempo Testnet are available on every plan. Validate your client flow there before enabling a production channel.