LiveWhat happens to my transaction if Presence is slow or unavailable?
Failure behaviour
The decision call is one HTTP request you time out on like any dependency. Telemetry is sideband, and one request returns every surface to watch-only.
Designed to be switched off
Verification telemetry runs on a separate WebSocket, off the transaction path. Losing it degrades verification quality; it does not touch your transfer.
The decision call is a single HTTP request. You apply your own timeout and your own fallback, exactly as with any other dependency.
The kill switch returns every surface to watch-only, effective on the very next decision, and is itself sealed as a governance record naming who threw it.
Check it yourself
The artifacts behind this page
- Kill the connection and add latency — your flow should not notice.Security review →
- Four rollout stages, moved one click at a time.Shadow-mode methodology →
What this page does not claim
Limits
- In production the authority verdict comes from an upstream Decionis gate. Deterministic Gate-1 checks run locally and can block without it, but an upstream outage fails closed rather than silently authorizing.