What was already accepted?
Keep the completed check as a reusable record with clear limits and expiration.
Reuse trust across apps, without restarting every check.
When a human, organization, ownership, or risk check already passed, issue a current receipt. The next connected product checks that decision instead of collecting the same evidence again.
What reuse actually guarantees
Which product asks next?
Let another connected product request the same current receipt when your rules allow reuse.
How private stays the source?
Share the decision record, not the full underlying evidence, unless the user opts in.
NEUS | reusable receipt
Portable
One proof. Every surface that accepts it.
- First useVerify once
- Next appReuse
- Agent actionReuse
- Network effectCompounds
Profile owners control visibility. Connected systems check status.
How it works
Complete, save, recheck, keep private
- 1Complete the first checkRun a supported identity, ownership, or risk flow once.
- 2Issue the receiptStore the accepted result with current status and clear limits.
- 3Connect the next productLet another product check the same receipt.
- 4Recheck current statusConfirm the receipt is still valid before granting access.
NEUS | reusable receipt
Portable
One proof. Every surface that accepts it.
- First useVerify once
- Next appReuse
- Agent actionReuse
- Network effectCompounds
Profile owners control visibility. Connected systems check status.
Integration options
Use the path closest to your first protected decision.
- Hosted check
- Start without building a custom screen
- JavaScript
- Add the check to a product backend
- HTTP
- Check a receipt from any service
- React
- Drop the flow into an existing interface
- Assistant setup
- Bring trust checks into developer tools
What stays true
Clear checks at the moment they matter.
- Status is checked again each time the receipt is used
- Private by default
- Each product keeps its own rules
Reuse and receipt questions
How portable decisions work without becoming a permanent pass.