Accounts and identifiers

Accounts bind a customer relationship to an institution-approved product and its versioned terms. Savings, current, fixed and recurring deposit arrangements have different lifecycle and calculation rules.

Before opening an account

The deposit operations owner selects a local or sandbox institution, a permitted customer, product version, currency, office and the terms the customer accepts. Verify customer eligibility and actor scope. Discover the product and account templates in the selected core contract.

POST /savingsaccounts creates an account application in the source API. Approval and activation are separate commands with their own permissions, conditions and dates. Use the exact request fields from the selected version.

Numbering and NUBAN

The institution chooses its jurisdiction’s numbering scheme. Nigerian account generation uses NUBAN with the institution and scheme code and check-digit rules. That regional implementation does not set every market’s account format.

The separate Account Numbers and Custom Account Numbers add-on targets require approved generation, reservation and allocation contracts. A virtual account belongs to its issuing service and points to an account in the owning core. See add-on boundaries.

Rates and terms

Product owners and Finance maintain approved rate, fee, tax, precision and effective-date rules. Any permitted account-level override must retain its own approved terms and audit history. Existing customer contracts must remain reproducible after a new product version is published.

Do not infer a hard-coded approval queue from a request field. Inspect the exact implementation, approval policy and institution qualification for the proposed override. Islamic contracts use the approved profit, rental and governance model.

Service and recover

Retain the account application, customer agreement, approvals, activation result and initial journal references. A rejected application stays distinguishable from an active account. Restrictions and holds retain reasons and owners. Closure must resolve financial obligations while preserving history and customer evidence.

Use synthetic scenarios to check concurrent opening, duplicate identifiers, invalid terms, changed approval data, dormancy, maturity, early exit and interrupted activation. Record financial and operational acceptance for the exact product scope.