Security features
Controls that apply at authorisation, not afterwards.
The security model is built on one principle: a control that takes effect after the transaction is a refund process, not a control. Freezes, limits and rules are applied at the authorisation layer.
This page describes the model. What is genuinely true of this site is on the AVORA security page — there is no server, no account and no stored credential here, and the sign-in form protects nothing.
What it gives you
Declines, not reversals
A card frozen one second ago declines the next authorisation rather than reversing it next week.
Biometrics stay on the device
The device attests it recognised you. We receive the attestation, never the fingerprint.
Assets held, not used
Crypto sits in segregated cold storage and is never lent, staked or rehypothecated.
What is included
- Instant freeze at the authorisation layer
- Rotatable card number and CVV
- Multi-factor authentication on sign-in and payout changes
- Per-device management and revocation
- Notification on every authorisation
- In-flight scoring with hold-for-confirmation
Questions
This site has no server, no account and no stored credential, so there is nothing to take from it. Never type a real password into it.
On a real service this is where the fraud line and its response time would be stated. This is a demonstration project and has neither.