Sandbox Setup
The mechanics — credentials, endpoints, test cards, and the three verification calls — are the canonical destination-side setup: follow For Destinations → Sandbox Setup end-to-end. This page covers only what’s specific to an Agentic Commerce build.
Agentic-specific checks
404 ucp_disabledon discovery/search (a UCP-envelope code) means the test merchant hasn’t opted into agentic surfaces — ask Firmly to enable UCP for the test merchant.- Merchant scope — confirm your sandbox App ID has merchants attached; discovery returns an empty
productsarray otherwise. - Protocol path — if you’re integrating via UCP, MCP, or ACP rather than direct REST, verify the protocol endpoint against the same sandbox App ID before building the full flow.
- Agentic Pay — enrolling cards and paying with network tokens needs an Agentic Pay API token and network sandbox test cards in addition to the App ID; the generic test cards are not enrollable. See Agentic Pay in the sandbox.
Going from sandbox to production
The universal steps are in For Destinations → Sandbox Setup. For an agentic destination, additionally:
- Confirm your consent and disclosure model is implemented for production traffic — the user must review and confirm order details before
complete-order. - Run the full Going Live checklist.
Related
- For Destinations → Sandbox Setup — the canonical setup
- Advanced Checkout Guide — run the full purchase flow
- Going Live — the agentic pre-launch checklist