Reality-grade banking · Vault protection
Your key is created on your device and carried inside your private Vault image. A copied service record cannot supply that key. Keep your authority with you—and keep supported value ready for its next use.
Public proof grants no access.
Passkey protection is your choice.
Reality-grade banking
Your private Vault image carries the key. The service receives the evidence needed to check your authority, without receiving that private key.
Illustration of a copied-record attack, not a live breach or verification. This explains why a hosted database leak does not reveal the Vault’s private key; it does not claim immunity from a compromised device, stolen private original or fraudulent action you approve.
Reality-grade banking
Verified account recovery. Proof of your device key. An original record of their connection. Your identity continues beyond the prompt.
Passkey check
A passkey check verifies a signed response to a fresh challenge for the registered site, with the required presence and device verification.
PBI continuity in this banking experience
The PBI flow also verifies the recovered account’s original proof, proves possession of your device key and carries the accepted binding in your Receiz identity.
A credential check establishes its assertion. PBI adds the verified account, device possession and carried identity connection. Illustration only; no identity check is performed here.
PBI proves you’re reopening your existing account. It connects that proven account to your device key—the signing key held on your device. The original proof of that connection stays with your identity.
A returned name or account number cannot stand in for that proof. Your identity continuity has to verify.
The Vault has its own private key. It stays in the complete private original, separate from your ordinary account key and the public evidence you share.
PBI does not replace your private Vault original. Recovering the ordinary account does not manufacture a missing Vault key.
Add optional passkey encryption to require the complete file and its original compatible credential. A copied protected file alone cannot open.
PBI establishes account continuity. Passkey encryption protects the Vault file. Each has a specific job.
PBI account entry is an explicit choice. A private Vault original remains its own authority; image-only custody does not require PBI or a passkey. With passkey protection, keep the complete original and access to its original compatible credential.
Reality-grade banking
Money you can send. Holdings you can move. A private key you keep.
Send available value from your Vault to another Receiz ID. Review the source, exact amount and resolved recipient before you approve.
Move supported assets and investment ownership in kind. Keep their quantity, ownership and source history connected instead of turning the deposit or return into a sale.
Bring supported value back to your original account through its admitted ownership. Keep the result and its updated private original together.
See the difference
Choose a situation. See exactly where the protection comes from.
Reality-grade banking
A private original, a protected original and public proof are not interchangeable. Knowing the difference puts you in control.
Your Vault key, supported sources and carried history stay together in the complete original. Its key is separate from your ordinary account key.
Default: bearer authority. Anyone with the private original can use its Vault authority. Treat the complete file as a key.
Choose optional passkey encryption. The complete saved file and its original compatible passkey are both required to open it.
Save and reopen the exact prepared original before first custody creation or a new financial operation. Retain the updated original after results.
A separate public proof carries selected, verifiable evidence. Someone can inspect the supported history without receiving your private authority.
It is evidence, not a private original, login credential or spendable bearer token. The public reader refuses private originals.
Reality-grade banking
The supported action still has to match the source, your authority and what you approve.
Review the exact supported action, source, amount and recipient before financial execution. A protected Vault requires a fresh passkey authorization for the action.
Closing the Vault or putting the browser tab in the background ends its unlocked session. A late response cannot reopen a closed session.
Recovery continues the original once-only operation. Retrying the same governed request cannot turn a copied source into new value.
The independent reader checks the enclosing proof object and its carried public evidence. Saved history can be inspected offline; current financial execution stays connected.
Reality-grade banking
Make protection part of how you hold and share value.
Use a separate Vault. Add passkey encryption when you want the file to require your original compatible passkey.
Save it, reopen it and retain each updated original after an operation. If protected, keep access to its original passkey too.
Export only the selected public evidence you want others to inspect. Keep the private original in your custody.
Reality-grade banking
The protections, the choices and the limits—in plain language.
Your private original, its required credential and the device you use to authorize actions are what you protect. A compromised device or browser, someone obtaining an unprotected private original, or an action you approve to the wrong recipient can still cause loss. Keep the private original private, protect your devices and verify what you authorize.
A public Receiz ID or public Vault proof is not your private Vault authority. The Vault uses its own key, separate from the ordinary account signing key. Your public name and selected evidence do not contain those private keys.
An encrypted Vault needs the complete saved original and the same compatible passkey credential. Whether that credential is available on another device depends on your passkey provider and setup. A new passkey or ordinary Identity Record cannot replace the original Vault passkey. Test your actual save-and-reopen and recovery setup before relying on it.
Passkey encryption requires WebAuthn PRF support at the registered site. Device, browser and provider support must be qualified with the exact original. Software tests do not establish universal Face ID support or passkey recovery.
You can open supported saved contents and verify carried history offline. A historical proof does not establish present unspentness. Funding, transfers and other financial writes in this release use the connected execution route.
No. The existing Receiz identity and account entry remain intact. Your Vault is an explicit, separate entry from your Identity profile; public pages do not open it or request your passkey.
Confirm that the Vault service is enabled and qualified for your environment, choose the protection you want, save and reopen the complete original, and establish your real recovery path. The custody migration is applied; application rollout remains separate. This page explains the implemented Vault and does not activate it or perform financial actions.
Your value. Your authority.
Make what you own inspectable.
Keep the authority to use it separate.