Skip to main content
By the end you’ll have taken a real payment on testnet and received a webhook for it.
What you need: a browser wallet (MetaMask, Rabby, or similar) and a few minutes. No credit card, no sales call.

Sign in with your wallet

Go to cryptocheckout.ai/admin and connect.There is no email or password. You sign a message proving you control the wallet, and that wallet becomes your account.
Use a wallet you intend to keep. It is your login and, unless you set a separate payout address, your settlement destination.

Set your payout address

In Settings → Payout, set the address that should receive your money.This writes an attestation on-chain from your own wallet. Nobody else can make it — not us, not an attacker with our database. It becomes the root of the verification your customers’ browsers perform.You can point it at a different wallet from the one you sign in with. A multisig or treasury wallet is a good choice.

Deploy your pool

Go to Pool and pick a chain. Press Deploy, and sign.

Why you sign it

Because it makes the contract yours. We hand you a prepared transaction; you’re the one who broadcasts it.

What it costs

A one-time network fee — cents on most chains, more on Ethereum and TRON. The dashboard shows a live estimate before you sign.
Repeat for each chain you want to accept on. Your pool has the same address on all seven EVM chains, which makes reconciliation easier.
Making pool deployment a prerequisite for API keys and the embed snippet is coming. Today you can integrate before deploying — but a pool is still required before the wallet-payment option appears on a chain, so deploy early. Roadmap.

Embed the checkout

Copy the snippet from API & SDK in the dashboard. It looks like this:
Checkout embed
Keep both integrity and settlementAnchor.integrity means a tampered script fails to run rather than running altered. settlementAnchor is what the checkout verifies against the blockchain. Strip either and you lose a protection that exists specifically for you. Why.
Copy the snippet from the dashboard rather than this page — yours has your real merchant ID and payout address filled in.

Take a test payment

Open your page and click through. Pick a testnet chain, and pay with testnet tokens from any public faucet.Watch for:
  • The checkout showing a verified badge before payment options appear
  • Your onPaymentConfirmed callback firing
  • The payment appearing in Payments in your dashboard
Full testing guide.

Receive a webhook

Browser callbacks are convenient but not trustworthy — a customer can close the tab. Fulfil orders from webhooks.In Settings → Webhooks, add your endpoint URL and copy the signing secret. Then verify every delivery:
Sign the raw request body. Parsing and re-serialising JSON changes the bytes and the signature will never match.
Webhook reference.

Claim your money

Go to Pool and press Claim. One signature moves your balance to your payout address.There’s no minimum and no schedule. Batching a few payments into one claim keeps network fees down. Claiming.

Then what

Go-live checklist

What to confirm before real money.

Webhook events

Every event and payload.

Edge cases

Underpayments, wrong token, late arrivals.

No-code option

Don’t want to touch your site? Generate a payment link in the dashboard — a hosted checkout page you send to a customer. Same settlement, no integration. Payment links.