Developer Receipt Tester
This page is for integrators and engineers — not the customer verification experience.
Developer Receipt Tester
Validate signed Partner Flow receipts, registry records, and credential payloads during integration. This is not the customer verification experience.
Holders can review their own proofs from Passport. Open Passport.
Partner integrators: On callback, your server fetches GET /api/receipts/{receipt_id}/public, validates signature and policy binding, and only then grants gated access. Registry viewers: look up public registry records by ABX ID. Credential testers: validate a JWT against documented claims.
Mirror GET /api/receipts/{receipt_id}/public on your server after callback — do not grant access from this UI alone.
Who this is for: engineering teams implementing Partner Flow. What to do next: paste a receipt_id from your callback, optionally bind expected partner_id / policy_id, then verify the public payload.
Looking up a tokenized asset instead? Use the Registry lookup tab. Credential JWT testing lives under Credential JWT.
Reference demos (below the live tools)
