Add-on products
Choose the product, its API boundary and the system that owns the account or financial record.
Each add-on is a separate API-first product with its own licence, dashboard, data and roles. It can connect to Nucleus or another qualified core. Bundling changes where its interface appears while preserving its product boundaries.
The table describes the Product Bible target and the contracts needed for adoption. It is a planning entry point. It does not announce shipped standalone endpoints or provider qualification for every product. Obtain the exact versioned product contract and institution acceptance record before connecting a live account.
Accounts, payments and channels
| Product | Work and ownership | Before activation |
|---|---|---|
| Virtual Accounts | Store static/dynamic aliases and their linked core account. Resolve inflows and notify with the virtual reference | Qualify issuer prefix/range allocation, expiry/deletion, resolution, credit identity and per-credit or batch settlement |
| Account Numbers | Generate identifiers against an institution’s approved jurisdiction scheme | Validate scheme, institution code, uniqueness and assignment in the owning core |
| Custom Account Numbers | Offer a preferred number with reservation and price | Bind reservation to requester, expiry and account intent. Qualify concurrent allocation and fee handling |
| Transfers | Reach domestic, cross-border and stablecoin rails using named connections | Follow the Transfer workflow and qualify each rail’s funding, status, settlement and recovery |
| Payment Gateway | Merchant online acceptance, checkout, collection and disputes | Establish acquiring authority, merchant obligations, capture, reserves, settlement and chargeback evidence |
| POS | Terminal estate, keys, routing and merchant settlement | Qualify device assignment, secure key custody, transaction identity, virtual accounts and terminal recovery |
| Agency Banking | Agents and super-agents, customer-assisted services, float and commissions | Verify programme hierarchy, device/actor scopes, custody, float availability and independent settlement |
| Cards | Issuance, controls, authorisation, disputes and replacement | Qualify programme and processor, card-to-account relationship, holds, clearing and late presentment |
| Banking as a Service | Grant a partner selected institution services | Bind programme, consent, service scopes, atomic limits, pricing and credential lifecycle |
| Wallets | Stored-value wallets offered by integrators under institution programmes | Institution owns liabilities and balances. Approve KYC/KYB, tier limits, data sharing, settlement and recovery |
| USSD Banking | Customer banking through an institution’s short code | Qualify aggregator, session authority, concise disclosures, SIM-swap controls and status recovery after timeout |
Identity and digital banking
| Product | Work and ownership | Before activation |
|---|---|---|
| KYC and KYB | Institution verifies its own customers or offers permitted checks to others | Establish evidence source, consent, jurisdiction eligibility, per-check metering and provider outcome handling |
| Retail Internet Banking | Personal online onboarding and self-service | Qualify enrolment, identity, account opening, device recovery and tracked servicing requests |
| Corporate Internet Banking | Online company onboarding and company banking | Verify directors/owners, versioned signed resolution, references, signatories, company mandates and dual-admin changes |
| Mobile SDKs | Modular iOS/Android banking interfaces and a possible reference app | Obtain the actual compiled signed module, API version, authentication and acceptance evidence. See SDK guidance |
| Digital Banking Admin | Customer enrolment, grants, credential recovery, sessions and content | Qualify staff scope and approval for access, limits, notices, publishing and revocation |
Engagement, risk and service
| Product | Work and ownership | Before activation |
|---|---|---|
| Alerts | Templates, preferences, delivery and configurable charging | Pin template, fee and waiver versions. Reconcile provider costs and avoid charging twice on duplicate delivery |
| Rewards and Loyalty | Earning, redemption, expiry and corrections | Establish reward-unit identity, entitlement, liability and linked reversal treatment |
| Fraud and Transaction Monitoring | Screening, scoring, holds, cases and filings | Qualify model/rule versions, institution authority, review queues and release/recovery effects |
| Disputes and Chargebacks | Money disputes across cards, transfers, POS and gateway | Establish deadlines, evidence, liability, provisional credit, approvals and final linked correction |
Bill payment uses the institution’s own connected service. It has a separate provider contract and no Nucleus add-on licence line of its own.
Connect and recover
The institution product owner selects licensed scope. Technology configures the core adapter and credentials, Finance approves financial mappings and operations owns pending items. Start in a named local or sandbox environment, then retain exact command/event schemas, actor grants, journal ownership, duplicate handling, failure states and acceptance evidence.
A received timeout creates status enquiry using the original identity. Failed delivery creates retry work for the message. Suspension stops only the affected new scope while existing obligations retain recovery authority. No add-on may introduce a second financial writer for the same account.