Skip to main content
  • Your production key has the nft:orders scope and is stored server-side only.
  • You know your program’s mint_chain and contract (or collection) address, and your wallet shows NFTs from it, with their metadata.
  • Your users’ wallets can pay USDC on Base or Solana, and hold NFTs on your mint chain.
  • You let the customer pick from the pack’s odds and show those odds (GET /catalog/packs/pool?odds=) before they buy.
  • Every POST /orders, POST /shipments and POST /tokens/{id}/shipment sends your own unique Idempotency-Key, and you retry 500s and timeouts with the same key (Idempotency).
  • Your checkout uses client_secret with publishable_key, or shows deposit_addresses and amount, and tells the customer to pay within 24 hours (Payments).
  • recipient is always the customer’s self-custody wallet, never an exchange deposit address.
  • On a Solana program you always send an EVM refund_address with orders, and payout_chain: "evm:8453" with a Base payout_address with sell-back quotes (until Solana payouts are switched on).
  • If you sell multi-pack orders: you show the total price, follow each unit (units[], its own pull and token), and treat processing / completed as the order’s summary status (Orders and statuses).
  • You branch on code; handle RATE_LIMITED (wait retry_after_seconds), BAD_ODDS, ODDS_UNAVAILABLE, PACK_UNAVAILABLE, WALLET_REFUSED, PAYOUT_CHAIN_NOT_ENABLED and the 503s (retry shortly) (Errors).
  • Sell-back: you show amount_usd and the 10-minute expiry, burn with the quote exactly as returned, and treat a held payout as “under review”, not failed (Sell-back).
  • Shipping: you collect a phone number outside the US, show total, pass it as max_cost, have the holder burn every token in the shipment, and renew an expired burn window instead of starting over (Shipping).
  • You registered a webhook, stored its secret, verify every signature (constant-time, 300 s tolerance), answer 2xx within 5 seconds, dedupe on the event id, and checked it with POST /webhooks/{id}/test (Webhooks).
  • You poll as described in Webhooks where you have no webhook or missed events, and stop at the final statuses.
  • You know how you will rotate your key; your webhook moves to the new key by itself (Authentication and keys).
  • You ran the full flow in the sandbox: buy, pay, mint, transfer, sell back, ship, with webhooks arriving.
  • You ran one small real order in production, end to end, with us watching.