Skip to main content
Use your sk_test_… key to follow this on testnets, where nothing can cost you anything. Everything below is identical in production — you change the key, not the URL. See Environments. No account yet? Get one.

1. Create a session

Server-side, with your secret key. This bills the payer 10 USDC on Base.
The SDK returns the session directly:
created: false means this was an idempotent replay — a session with that orderId already existed, and you get a 200 instead of a 201. Branch on it to avoid emailing a customer twice.

2. Send the payer to url

Redirect, or embed it. The payer picks any token they hold on any supported chain; you still receive exactly the token and chain you asked for.

3. Learn the outcome

Poll the session from your server, or register a webhook:
Treat a webhook as a trigger, not as evidence. Read the session back before releasing goods — that read is the authoritative answer, and it is the one that survives a replayed or spoofed delivery.