CryptoCheckout documentation

Two endpoints, one per rail. Both take a quote and return what the customer needs.

Connect rail
Deposit rail

POST /create-pool-connectReturns your pool address for the customer’s wallet to call deposit() on.

string

required

From create-quote.

string

The customer’s connected wallet. Required if you’ve enabled payer screening.

string

The contract to call. Verify this before signing.

string

Pass to deposit() so the payment is attributable.

string

Token contract address to approve.

string

Amount in base units.

number

Chain to submit on.

object

Verification bundle. Re-prove it client-side rather than trusting it. Why.

The pool must be deployed on that chain. If it isn’t, this returns 422 — offer the deposit rail instead.

POST /create-pool-depositReturns a one-time address for the customer to send a plain transfer to.

string

required

From create-quote.

string

Deposit intent ID. Use with payment-status.

string

Show this to the customer. Unique to this invoice.

string

Where the funds ultimately settle.

string

Token contract address to send.

number

Decimals, for display.

string

Amount in base units.

number

Tolerance in basis points.

number

Chain to send on.

string

Starts at waiting.

string

Quote expiry. The address stays valid after it.

curl -X POST $CC_API_BASE/create-pool-connect \
  -H "apikey: $CC_PUBLISHABLE_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "quoteId": "q_8f2a…", "payerAddress": "0xCustomer…" }'

curl -X POST $CC_API_BASE/create-pool-deposit \
  -H "apikey: $CC_PUBLISHABLE_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "quoteId": "q_8f2a…" }'

{
  "id": "dep_4c8e…",
  "forwarderAddress": "0x7A3f…",
  "poolAddress": "0x2B91…",
  "token": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
  "tokenDecimals": 6,
  "expectedAmount": "49000000",
  "toleranceBps": 50,
  "chainId": 8453,
  "status": "waiting",
  "expiresAt": "2026-08-09T15:02:11.204Z"
}

Displaying a deposit address

Verify before you show it

Re-derive the forwarder from the chain-read pool address and confirm it matches. If it doesn’t, show nothing. Verification.

Show the address, amount, token, and chain

All four. Most failed payments are a customer sending the right amount of the wrong token, or the right token on the wrong chain.

Offer a QR code

Most customers pay from a phone.

Say the address stays valid

It reduces panic when an exchange withdrawal is slow.

Never show a deposit address you haven’t verified. It is the one screen where a compromised response could redirect a customer’s money, which is exactly why the verification exists.

Errors

Status	Meaning
`400`	Missing or malformed field
`404`	Quote not found
`409`	Quote already used
`422`	Quote expired, pool not deployed, or amount below minimum
`429`	Rate limited

Full error reference.

Using the API

Endpoints

Create a payment

Displaying a deposit address

Errors

​Displaying a deposit address

​Errors

Displaying a deposit address

Errors