Developers · Launchpad

End-to-end sandbox partner contract

This local suite validates the same partner integration contract before a holder is involved. It does not issue a real receipt, verify a real person, create a production key, or move funds.

What this proves locally

Run the same integration contract your server will use before you test with a real holder. The suite reuses Launchpad provisioning, callback allowlisting, hosted Partner Flow parsing, receipt verification, webhook re-check, trading and payment preflight, optional Wallet Standard binding, the sandbox test console, and the reviewed Production request.

  1. discover
  2. create sandbox app
  3. configure callback
  4. hosted partner flow
  5. policy result
  6. signed receipt
  7. server receipt verification
  8. webhook recheck
  9. trading preflight
  10. payment preflight
  11. wallet standard optional
  12. sandbox test console
  13. production review request

Repository command

CI-safe. No network credentials.

npx vitest run lib/partner/sandboxPartnerContract/sandboxPartnerContract.test.ts

Equivalent: npm run test:sandbox-conformance

What it does not do

  • Issue a live Partner Flow receipt or verify a real person.
  • Create a production API key or activate Production.
  • Call Circle, send a live webhook, submit a trade or payment, or move funds.
  • Bypass tenant authorization or trust browser flags.
Continue from hereIntegration StudioStarter KitLaunchpadPartner Flow docs