Request access to the ACK-Lab developer preview at the Catena developer portal; you will receive sandbox API credentials and a testnet DID registry endpoint separate from production
Use the ACK-Lab SDK (catena-labs/ack-lab-sdk on GitHub) to generate test agent DIDs on the sandbox DID registry; these DIDs are isolated from production and can be freely created and discarded
Issue test Verifiable Credentials using the sandbox VC issuance endpoint; ACK-Lab provides pre-seeded trust anchor DIDs that act as mock principals and issuers for end-to-end flow testing
Initiate test ACK-Pay payment requests using sandbox credentials; the sandbox payment rail executes mock settlement without moving real funds and returns signed test receipts in the same format as production
Use the ACK-Lab observability dashboard to inspect each step of the ACK-ID and ACK-Pay flows, including DID resolution logs, VC verification results, and payment receipt generation, before promoting to the production environment
Known gotchas
Sandbox DIDs in ACK-Lab are not resolvable by external DID resolvers outside the testnet; integration tests that rely on external DID resolution will fail in sandbox even though they would succeed in production — mock external DID resolution in your test suite separately
ACK-Lab is a developer preview with no SLA; sandbox availability may be interrupted during Catena platform updates — do not block production release timelines on sandbox availability, and run final integration tests against production with small amounts once sandbox validation is complete
The ACK-Lab SDK version may lag behind the production ACK SDK; always check that the API surface in ACK-Lab matches the version of ACK you intend to deploy to production before assuming sandbox test results are fully representative
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp