Who may spend?
Confirm the person, organization, wallet, or agent behind the payment or API call.
Protect payments and API spend before money moves.
Put current identity, ownership, risk, or permission proofs in front of checkout, credits, payouts, and paid API use. Agents and humans both face the same rule: no valid receipt, no spend.
Clear approval before checkout
What cap applies?
Carry spending limits and allowed payment types in a current permission or access proof.
Can ops review the decision?
Keep a checkable record of the trust result used at checkout or payout.
Protect payments and API spend
Ready
- Who may spend?Required
- What cap applies?Current
- Can ops review the decision?Checked
How it works
Choose spend, require a receipt, meter, include assistants
- 1Define the spending ruleChoose identity, risk, ownership, or permission requirements.
- 2Complete supported checksRun hosted verification for the buyer, seller, or assistant owner.
- 3Issue the spend proofAttach current status and spending limits to the account or assistant.
- 4Enforce before settlementRequire a current receipt before checkout, credit use, or payout.
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.
- Your payment provider moves money after the trust check passes
- Metered API and checkout share one model
- Direct path to Pro credits and paid access
Paid-access questions
How receipts work with checkout, credits, and assistant spend.