Identity & protection
Consent, scopes and exact-operation approval
Read what an application can access and keep that access separate from permission to move value.
Access and execution are separate
An application registration identifies an integration. A user grant authorizes its named scope. A financial action still requires its own source-bound review and explicit approval of the exact operation. A public client ID, connected account, successful sign-in or model instruction cannot stand in for that final authority.
- RegistrationExact application coordinate.
- GrantListed access under the identity.
- ReviewActual participant, source and units.
- ExecutionOnly the approved supported operation.
Current Bank access families
| Family | Existing purpose | Separate boundary |
|---|---|---|
| Account reads | receiz:wallet.read, settlement.read and reserve.read. | No transfer, purchase or sale authority. |
| Wallet Send | Wallet read and transfer access for the payment explicitly approved. | Each payment has separate final approval. |
| Market reads/trades | Read quote/position/original results; submit the manual trade approved. | Execution uses current Market rules and price. |
| Messaging | Read/send conversations, groups, calls and owner Twin execution. | No payment or automatic reply authorization; camera/microphone have device permission. |
| Native operations | Listed source, subject, domain, Reserve/Settlement and record/seal scopes. | Each custody/ownership/financial operation retains its own contract. |
| Recovery | Read the original retained transaction result. | No new execution. |
Review a request for bank access
- Open the connection detail
Inspect Account authorization required and Permission details where shown.
- Read bank access
Review the actual listed consent and intended identity.
- Approve deliberately
Use I allow the listed Bankeiz access for this ID and Approve bank access only if it matches the intended operation.
- Keep financial review separate
Connection readiness does not execute a transfer or qualify every host capability.
Private account proof is a distinct disclosure
Connect account proof supplies the complete private source for the named bank connection under its separate approval. It is not the public Share an account proof operation. A public proof requires its own exact disclosure review. Enabling future updates adds another explicit scope of publication; stopping updates does not recall copies already shared.
Compose integrations without widening authority
Use the actual installed operation’s scope, source and runtime requirements. Preserve the registered application coordinate byte-for-byte, including its rc_ prefix and case. Do not fabricate grants, booleans, session handles or signatures. If access is unavailable, state which grant or host capability is missing. An agent with continuity still needs the permission and tools of each compatible environment; it does not inherit universal access.
Implementation sources
Inspect the exact path.
Source links retain revision 6c5d582. Read the documented operation and assessment scope alongside its code.