Intent-bound verification · Live
See the intent. Verify the person. Then execute.
Choose a finance SDK call or a Zoom, Webex, or Teams meeting. Both run through the same merchant subscription, recipient consent, live passkey verification, post-biometric liveness capture, and autonomous verdict path.
Merchant subscription
Decionis demo merchant
Plan
Sandbox
Credential
Server custody
Consent proves intent. Biometrics prove the human. Policy context still determines whether execution can proceed autonomously.
const verdict = await presence.verifyIntent({
intent: "wire.execute", amount: 250000
});
// execute only when verdict === "ALLOW"
Biometric → liveness
Pixels remain in this browser
Live execution trace
One request, end to end
- 1
Merchant subscription
Checking server-held tenant
- 2
Execution
POST /v1/verification-requests
- 3
Intent consent
Waiting for execution
- 4
Platform biometrics
Recipient action required
- 5
Liveness photo
Waiting for consent
- 6
Policy evaluation
Trusted region staged
- 7
Verdict
Pending
Verdict pending
Accept continues to biometric and policy evaluation. Decline produces autonomous BLOCK; post-verification policy drift produces ESCALATE.
That was a demo tenant. Run Presence against yours.
A sandbox gives you the same engine behind your own credential: your action contexts, your policy, your signed records — starting in watch-only, where nothing is ever blocked.