What must be proven?
Define the identity, ownership, role, or permission result required before entry.
Open access only when the receipt is current.
Require a current trust receipt before content, membership, rewards, checkout, payouts, or protected service access opens. Each product checks status, limits, and expiration at the moment of access.
Add a trust decision after sign-in
Is the proof still current?
Check current status, limits, and expiration instead of relying on an old signup result.
Who reviews failures?
Give operations a clear record of what was accepted or refused without exposing the full source file.
Access and policy rules
Ready
- What must be proven?Required
- Is the proof still current?Current
- Who reviews failures?Checked
How it works
How to set up an access rule
- 1Choose the access rulePick the check and proof type the protected action requires.
- 2Issue or reuse a receiptComplete the check once, or accept an already-current receipt.
- 3Enforce at the decisionBlock, allow, or route for review based on live status.
- 4Expand to the next surfaceReuse the same rule at membership, rewards, payout, or API access.
How it works
CHECK | RECEIPT
- 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
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.
- Runs after your existing sign-in
- Works for people and agents
- Pairs with Pro and metered access
Access policy questions
Setting rules for content, membership, rewards, or services.