Verify once. Reuse everywhere.
A trust receipt is a machine-checkable record that an identity, ownership, risk, or permission check completed. Connected apps, gates, and AI agents confirm its current status before access, payment, or action.
What a receipt covers
Identity, ownership, permission, and status — in one record.
Carry the decision that matters: who or what was checked, what they own or control, what an agent may do, and whether that result is still current when the next gate asks.
- IdentityPerson, org, social, agent
- OwnershipWallets, domains, accounts
- PermissionLimits, spend, expiry
- StatusCurrent, expired, revoked
How it works
Four steps from check to reusable proof.
Complete a check through a hosted flow or your own app. The accepted result becomes a reusable receipt. Connected systems confirm it before access, payment, or action — without exposing the full source file.
- 01Verify onceComplete a supported check
- 02Get a receiptResult becomes a reusable record
- 03Check before accessApps confirm before action
- 04Share lessPresent the result, not the file
Reusable credential
One proof. Every surface that accepts it.
The first gate runs the check. The next app, agent, or partner handoff consumes the same current receipt. Profile owners control visibility; connected systems check status, scope, and expiry.
One proof. Every surface that accepts it.
- First useVerify once
- Next appReuse
- Agent actionReuse
- Network effectCompounds
Profile owners control visibility. Connected systems check status.
Live receipt
A checkable decision — not a screenshot of a check.
Subject, check type, scope, status, and expiry travel together. Present the result at the next gate without restarting verification or shipping the underlying evidence file.
One check. Reusable everywhere it is accepted.
Connected apps confirm status before access without the full source file.
NEUS vs a one-off check
A one-off result usually stays inside the service that ran it. A trust receipt gives compatible integrations a stable reference they can check again.
| Dimension | One-off check | NEUS trust receipt |
|---|---|---|
| Reuse | Usually stays inside the product that ran it | Can be checked by another integration that accepts it |
| Audit trail | Depends on the source system | Preserves the check result and receipt metadata |
| Control | Managed inside the source product | Profile owners control supported public visibility |
| Expiry and revocation | Varies by provider and integration | Connected systems can check current status and expiry |
Where teams use it
Gates that need a firm yes or no — without starting from zero.
Sign-up and access
Skip repeat verification when the next gate accepts the same check.
Marketplaces
Buyer, seller, and membership decisions that stay checkable.
Agent permissions
Explicit, checkable, and revocable limits before action.
Payouts and partners
A decision record for handoffs without the full source file.
Frequently asked questions
What is a trust receipt?
A reusable record of a completed check: who it covers, what was allowed, whether it is current, and when it expires.
How is a trust receipt different from a one-off check?
A one-off result stays where it was created. A trust receipt can be checked again by another connected product.
Who can check a trust receipt?
Public receipts: receipt page or API. Private receipts: authorized access only. Each app decides what it accepts.
What does a trust receipt reveal about me?
Depends on the check and visibility. Review fields before you make a receipt public or share it.
Are denied actions recorded too?
Not automatically. NEUS records completed checks and permission proofs. Your app can log action outcomes when it needs an audit trail.
See it live in the demo, browse products and use cases, read the protocol overview, the open standard page, or build with the developer docs.
Portable identity, context, and authority for humans and AI agents. Check trusted state before access, payment, or execution.