The intelligence behind the interface
WAB’s operating design places centralized AI intelligence behind the customer interface. Proprietary models and an owned internal platform coordinate document understanding, service tasks, credit preparation and operational monitoring.
BankID, entity records and RTX establish identity and authority. The intelligence layer works within those permissions, with the bank’s records and authorized execution systems retaining their own controls. The shared USD2–WAB platform maintains distinct institutional data and authority.
World Wallet is the customer point of access
The World Wallet concept places the banking relationship in a mobile interface. A customer would see relevant accounts, payment activity, financing and approvals through the same entry point. Business use also needs a distinction between the person and the organisation they represent.
A useful interface explains the action, amount, destination, cost and required approval. It also supports mistakes, disputes, lost devices and changes in authorised personnel. Those everyday cases belong in the operating design.
Four distinct questions
The platform separates the person, organisation, permission and transaction record. Their connection makes a payment understandable without treating one layer as proof of all the others.
- 01
BankID · the person
Personal identity and authentication within the WAB development design.
- 02
LEI · the entity
An external standard identifier linked to public legal-entity reference data.
- 03
RTX · the authority
The organisation, action, limit and lifecycle of a delegated permission.
- 04
Transaction record · the action
The instruction, approvers, supporting documents and reconciliation.
Permission has a lifecycle
A role can be created, amended, expire or be revoked. Authority also depends on the action: a person allowed to buy inputs may not have permission to release payroll. Amount limits and second approvals can apply to one action without applying to another.
The system design needs to retain the state at the time of the decision and enforce current permissions for later actions. A historical approval is evidence of an earlier decision; it is not a permanent right to keep acting.
Change the authority, change the result
This demonstration evaluates a fictional transaction against visible conditions. It is a learning tool and creates no actual bank permission.
The permission and request
- Person evidence checkedPass
- Entity evidence checkedPass
- Permission is activePass
- Permission has not expiredPass
- Permission has not been revokedPass
- Requested action is permittedPass
- Amount is within authority limitPass
- Required approvals receivedReview
ILLUSTRATIVE SCENARIO
This fictional workflow illustrates the difference between identity, delegated authority and transaction approval. It does not authenticate a person, verify documents, create a legal signature or authorize a bank payment. No information is submitted.
Business mapping connects evidence
An entity record can connect registry details, reported relationships, customer documents, representatives and transactions. Each element should retain its source, date and verification status. Public reference data and internal due diligence have different responsibilities.
The WAB presentations establish a platform design. They do not establish a deployed application, live GLEIF integration or approved digital banking products. Technical implementation, legal acceptance, security and product approval remain development work.
READ THE SOURCE
Publications and reference material
WAB development presentations · January 2025 and May 2026
GLEIF · The Legal Entity IdentifierGLEIF · The verifiable LEIGLEIF · Data quality checks