This page is for integrators and engineers, not the customer verification experience.
Developer tools
Receipt verification
Inspect signatures, policy, and revocation. Passport
Reference: receipt inspection map (not live status)
05 Evidence
Verify the Decision
Sample
Sample receipt and preset check outcomes. This UI does not call the production verify API.
Abraxas separates two questions: whether the receipt is genuine, and whether the decision is authorized now. Live partner verification uses the same split.
Issuer authorityExample: issuer recognized for this sample.
Pass
Signature integrityExample: valid signature (preset — not computed live here).
Pass
Policy bindingExample: bound to an active policy.
Pass
Audience bindingExample: audience matches the request.
Decision receipt
v1 · sample fixture
PERMIT
type
access_decision
result
permit
subject
did:example:8f3e…7a7c
issuer
did:abraxas:abraxas-trust-registry
issued_at
2025-03-08T14:20:16Z
expires_at
2026-11-01T00:00:00Z
policy_id
policy_age21_retail_v3
audience
app:financial
signature
Ed25519 · valid in sample
Current authorization
Whether the decision is usable now
Pass
ExpirationDecision has not expired.
Pass
FreshnessWithin acceptable time window.
Pass
RevocationNot revoked by issuer.
Pass
Replay 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.
Receipt input
Verification action
Cryptographic result
Policy & issuer provenance
Freshness & revocation
Raw proof
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.
Look up public registry records by ABX ID, not Partner Flow session receipts.
Reference records
Verify attested records
Reference pilots resolve here — assurance levels, pipeline stage, and authentication proofs. Owner submissions do not auto-publish; this is verification infrastructure, not a listing board.
