# Identity and account access

Continue the established Receiz identity while keeping recognition, private access and financial approval distinct.

Canonical: https://docs.bankeiz.com/identity/
Reviewed: 2026-10-25; coordinated packages 129.0.0; ruleset 127.0.0.

## Identity is carried proof

Receiz ID establishes identity continuity. Supported Identity Records, Identity Seals and Receiz Keys carry their own admission and recovery material. The image/file is an original with an identity primitive, not a screenshot of a login. A public username helps recognize or address someone; it is not private account authority. PBI and supported recovery prove their own established account boundary.

## Open or recover

1. **Use the existing account entry** — Continue with the identity material or supported PBI recovery the account already uses.
2. **Open the actual original** — Preserve its exact file. If a required phrase is requested, use that original’s phrase. Some Records do not require one.
3. **Check the identity** — Confirm the intended identity/account before connecting services or taking a financial action.
4. **Save a private backup** — Use Back up my Identity Record and protect any required recovery phrase separately.

## Account access has a named scope

The Bank read consent opens supported account sources and reads Reserve and Settlement. It supplies the protected identity proof and signed consent to the connected service while the signing key remains on the device. Native custody, ownership and other actions have additional listed scopes. No read consent is a blanket approval for a transfer, sale, redemption or backing commitment.

- [Understand the listed permissions](https://docs.bankeiz.com/permissions/)

## Move between environments carefully

Compatible applications admit supported identity and history under their own rules. Shared identity does not grant every app access to every private source. Identity restoration is distinct from restoring private proof archives, encrypted pending operations or qualified device-bound Note custody. Keep the original device until unresolved operations and held custody are safely resolved.

**Keep the recovery materials separate**

| Material | Role |
| --- | --- |
| Identity original | Supported identity continuity and recovery. |
| Recovery phrase when required | Unlocks the corresponding supported original. |
| Private proof backup | Retains admitted originals and recovery evidence. |
| Vault private original | Separate Vault custody; may require its original protecting passkey. |
| Protected Note custody | Its native device/authority contract; not reconstructed from an ordinary backup. |

## When something does not open

Keep the original bytes and the exact error. Do not edit the embedded proof, rename an account coordinate or establish a new identity to conceal an admission failure. An unavailable host, unreadable original, missing phrase and unsupported authenticator are different problems. Resolve the named boundary using its existing recovery route. Remove ID from this device removes local access; it does not close the account or reverse funds.

- [Backup and restore procedure](https://docs.bankeiz.com/backup/)
- [Recover pending operations](https://docs.bankeiz.com/recovery/)

## Implementation sources

- [Identity Record controls](https://github.com/kojibai/reality-grade-banking/blob/6c5d582/src/features/account/IdentityProfile.tsx)
- [Device identity retention and removal guards](https://github.com/kojibai/reality-grade-banking/blob/6c5d582/src/receiz/identity-vault.ts)
- [Account access consent and scopes](https://github.com/kojibai/reality-grade-banking/blob/6c5d582/src/receiz/config.ts)

## Related documentation

- [Back up identity and proof originals](https://docs.bankeiz.com/backup/)
- [Consent, scopes and exact-operation approval](https://docs.bankeiz.com/permissions/)
- [Protect identity, custody and private material](https://docs.bankeiz.com/security/)
- [Give agents identity across environments](https://docs.bankeiz.com/agent-continuity/)