Build your own interfaces
Choose the channel and preserve core authority, state and accounting across the user journey.
Institutions can use supplied experiences, build their own or combine both. The product model is API-first. Supplied staff and customer experiences use the same controlled domain operations and versioned events.
Choose the actor and channel
| Experience | Actor and scope | Workflow evidence |
|---|---|---|
| Staff and branch | Assigned institution, office, role and till where relevant | Approved action version, work queue, financial record and next owner |
| Customer web or mobile | Customer relationship, consent, device and account scope | Onboarding/servicing status, approval, receipt and secure session recovery |
| Corporate exchange | Company mandate, signing combinations and batch/file scope | File hash, item identity, independent decisions and partial results |
| USSD, ATM and POS | Qualified session, device, programme and provider scope | Durable instruction, physical or programme evidence, status and reversal path |
| Agency | Institution agent, assigned service/device and float | Customer instruction, custody, commission and settlement records |
| Online acceptance | Merchant agreement and acquiring authority | Checkout, authorisation, capture, payout and dispute evidence |
| Assisted service | Verified caller/representative and staff service authority | Case, permitted disclosure, approved action and handoff |
| Partner APIs | Application, product grant and customer consent where required | Exact contract, request identity, signed/authenticated evidence and recovery |
Start with the contract
Select a named environment and the exact source or product contract. Read the current actor, permission, association and field requirements. The core reference covers discovered source methods. Selected digital banking routes cover parts of customer banking. Missing channel operations require an agreed interface before implementation.
Preserve the complete task
Show loading, empty, forbidden, validation, awaiting approval, pending external, returned, completed and recovery states according to authoritative records. Preserve a safe draft across interruption. Changed terms require current validation and any renewed approval. A lost session must not repeat a completed financial item.
Keep product terms, currencies and jurisdiction requirements configurable. Localise dates, numbers and language, including right-to-left layouts where selected. Branding preserves disclosures, state meaning, consent and accessibility.
Qualify the handoff
Test actor separation, cross-institution denial, customer association, duplicate requests, partial batches, interruption and unknown outcome. Record the build, configuration, grants, operation identities and resulting financial evidence. Customer-facing applications need their own complete channel acceptance in addition to a successful core request.