Start
Reality-grade banking
The open standard for holding, sending, receiving and using money with its proof, ownership and continuous history intact.
Money that shows its work
Reality-grade banking preserves the money and the evidence that establishes it. The Original carries identity, exact value, ownership, source and accepted history. A receiving implementation verifies and retains that continuity, then presents the result. An account screen, database or institutional statement projects the money; the Original remains its source of truth.
- PrepareSelect the source, recipient and exact amount.
- ApproveAuthorize the operation under the held source.
- ReceiveAdmit the exact completed result.
- RetainKeep the Original, ownership and continuous history.
The receiving laws
| Requirement | What it establishes |
|---|---|
| The Original | The enclosing artifact and its verifiable source remain available. |
| Exact value | Native units, denominations and allocations remain exact. |
| Ownership | The authorized sender, intended recipient and accepted transition remain bound. |
| Continuity | Predecessors, history and prior use remain connected. |
| Exclusive use | Consumed or allocated value cannot be admitted as another independent entitlement. |
| Recovery | An interrupted response resumes the same operation and preserves its eventual result. |
An implementation can use its own language, interface and operating environment. Its role is to uphold these laws through the actual operation. Conformance is demonstrated by reproducing the required evidence and outcomes for the implementation’s assessed scope.
One account, complete sources
Add money, receive a payment, hold a signed Original, buy ownership or fund a Settlement Note. The account brings the spendable result together while retaining each source and its exact accounting. Reserve identifies admitted funding provenance. Settlement carries proof-native value. A common account presentation keeps everyday use simple without erasing the underlying evidence.
- Pay someone
Use Account → Send, choose the recipient and amount, then review and approve. The existing funding flow uses the available account balance and funds an eligible shortfall through Checkout.
- Get paid
Use Receive for a payment link, QR or checkout. Open the accepted result and its receipt.
- Carry money
Create a funded Settlement Note with the intended amount and recipient. Keep the complete Original.
- Inspect what happened
Use Ledger and the original receipt to follow the amount, source, participants and accepted history.
Send across experiences
The standard belongs to the money’s continuity, not to one front end. People can receive through Bankeiz, reuse its open-source implementation or build another experience that follows the receiving laws. The choice of interface does not change the requirement to preserve the same Original, exact value, ownership and history.
A completed Note also travels directly between people. Offline verification reads the carried evidence with the required local verifier resources. Financial execution uses the applicable custody, authorization and once-only allocation contract. These are the mechanics that keep the same money intact through its next use.
Verify the actual result
Verification recomputes the evidence. It checks the enclosing Original before presenting its fields, matches the operation to the intended source and participants, and preserves the accepted history. The result is inspectable independently of a success banner. Keep the exact accepted artifact and operation reference so the outcome can be read again.
If an acknowledgement is interrupted, recover the retained operation. A retry continues that request; it does not authorize a second payment. A verified result remains retained while later verified additions extend its history.
Implement and demonstrate conformance
Start with a defined role: holding, receiving, payment, Note custody or another published operation. Compose the existing primitives, retain the exact request and result, and run the relevant conformance cases. Assess the actual build, capability, execution environment, custody and funding scope. Public contract fixtures and deployed financial evidence identify their respective scope directly.
- Preserve the actual Original and unknown carried namespaces.
- Keep account access, ownership and operation approval distinct.
- Use known verified truth immediately. Append verified additions without replacing it.
- Exercise interruption, duplicate, wrong-owner and consumed-value refusals.
Implementation sources
Inspect the exact path.
Source links retain revision v4.0.0. Read the documented operation and assessment scope alongside its code.