Environments and qualification
Bind your integration to an institution, build, environment and evidence scope.
Each institution selects its deployment, operating owner, jurisdiction pack and qualified product scope. Obtain actual addresses and access arrangements from that institution’s environment owner.
Select an environment
| Environment | Use | Evidence to retain |
|---|---|---|
| Local synthetic | Developer-owned instance and fixtures | Build/version, synthetic dataset, operation results, journals and recovery checks |
| Sandbox or staging | Institution-approved testing | Named configuration, access scope, simulator or provider boundary, reviewed acceptance results |
| Production | Approved institution banking | Signed release, launch approval, qualified connections, operational ownership and monitored financial evidence |
https://localhost:8443/nucleus/api/v1 is an illustrative local base. This site does not assert a shared public sandbox or production endpoint. The reference defaults to browsing locally hosted contracts with a local HTTPS request default and explicit origin selection.
Source and runtime evidence
The core source snapshot discovers 771 paths, 1,142 operations and 1,546 schemas. Structural validation checks the contract document. It cannot establish whether every operation performs correctly at runtime.
The local banking profile has 33 paths and 34 operations with 45 schemas. It describes selected LOCAL_SYNTHETIC NGN/NPS Transfer and customer-consented read flows, with scoped journey and unit evidence. These routes overlap the core snapshot. Broader global Transfer, add-on and live provider acceptance each require their own evidence.
Prepare a qualification run
Record the institution and environment, exact build and contracts, actor and permissions, approved products and currencies, starting data, operation identities, expected accounting, connection ownership and recovery path. Use synthetic data until the institution authorises the next environment and dataset.
Test rejection, duplicate requests, concurrent actions, lost responses, interrupted work and recovery alongside the successful path. Keep source discovery, local execution, provider testing and institution acceptance as separate records.
Move to live operation
The product model requires approved setup, a rehearsed banking day, valid entitlements and payment of the first charges before the Super Admin switches production on. Enable only the qualified scope. Existing obligations retain recovery and reconciliation owners when new activity is restricted.
Rates, limits, cutoffs and performance targets come from the approved institution/service profile. This guide supplies no universal limit tier or statutory value.