Developer Receipt Tester
This page is for integrators and engineers, not the customer verification experience.
Receipt verification
Inspect signatures, policy, and revocation. Passport
Reference: receipt inspection map (not live status)
05 Evidence
Verify the Decision
Abraxas separates two questions: whether the receipt is genuine, and whether the decision is authorized now. Live partner verification uses the same split.
Reading order
Cryptographic authenticityDecision receiptCurrent authorizationCryptographic authenticity
Structural checks on the signed artifact
- PassIssuer authorityExample: issuer recognized for this sample.
- PassSignature integrityExample: valid signature (preset — not computed live here).
- PassPolicy bindingExample: bound to an active policy.
- PassAudience bindingExample: audience matches the request.
Decision receipt
v1 · sample fixture
Current authorization
Whether the decision is usable now
- PassExpirationDecision has not expired.
- PassFreshnessWithin acceptable time window.
- PassRevocationNot revoked by issuer.
- PassReplay protectionNot a replayed receipt.
Example verification result
Status: Valid example
This sample shows passing authenticity and authorization checks with a PERMIT outcome.
Technical details
Each scenario selects a fixture. Check rows illustrate how authenticity and authorization are separated in a real verifier. Cryptographic verification against live evidence happens through the verify API and partner integrations—not in this homepage widget.
Sample receipt scenarios. Outcomes are preset examples, not live partner verification.
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)
