Illustrative scenario. A hypothetical institution, with outcomes modeled from platform capability. This is not a customer deployment, and the figures are not measured results.
Embedded Finance
Evidence basis: Demonstrated capabilityWhite-Label Investor DDAs for a Private-Markets Partner
In this scenario, a hypothetical community bank uses Fabric to give a private-markets partner white-label investor DDAs, opened by API from the partner’s portal, while the bank keeps KYC, risk and the ledger of record.
Scenario profile (hypothetical)
- Institution type
- Regional community bank
- Total assets (hypothetical)
- $4.5B
- Typical sponsors
- Commercial banking, treasury management, BSA/compliance, deposit operations, the partner’s fund administration
- Starting point
- A key client asks for API-driven investor DDAs
- Platform
- Fabric on Nucleus BankOS
The scenario
A key client needs money-center capabilities the bank can’t build.
- A private-markets partner raising capital deal by deal needs a dedicated DDA for each investor.
- Capital calls move money into deals; distributions flow back. The partner wants to run both from its branded portal.
- It needs API account opening, a per-investor, per-deal subledger, real-time visibility and a clean audit trail.
- The traditional path is a multi-year build and new vendors; saying no loses the relationship and the deposits.
How Nucleus would apply
Fabric would make the bank the embedded-banking provider, with minimal internal lift.
A program configured, not engineered
Fabric exposes capabilities the core already provides as governed APIs. The bank sets program rules instead of building rails, a ledger or a KYC stack.
Real-time subledger, per investor and per deal
A double-entry subledger tracks every investor and rolls up by deal and program. The partner and the bank see the same numbers at the same moment.
KYC stays with the bank
Embedded KYC/CIP, beneficial ownership and OFAC screening run before an account can transact. Decisioning, exceptions and ongoing due diligence stay under the bank’s control.
API-issued, white-label DDAs
The partner opens a real, bank-held DDA for each investor from its branded portal, in minutes. Each is a first-class account on Nucleus BankOS, not a shadow record.
Deposits and disbursements, orchestrated
Capital calls, fundings and distributions post to the core ledger in real time. Webhooks keep the portal’s balances and deal status current.
Records, monitoring and limits
Agreements, disclosures and every transaction keep an examiner-ready audit trail. DarkMatter Synergy+ monitors transactions on the same core, within program-level limits.
Modeled outcomes
What the model shows
- to launch the program, instead of a multi-year build
- Weeksto launch the program, instead of a multi-year build
- to open a bank-held investor DDA via API from the partner’s portal
- Minutesto open a bank-held investor DDA via API from the partner’s portal
- per-investor and per-deal subledger, deposits and disbursements
- Real-timeper-investor and per-deal subledger, deposits and disbursements
- KYC, BSA, documentation and ledger of record
- Bank-heldKYC, BSA, documentation and ledger of record
Figures are modeled for this hypothetical scenario, consistent with the evidence basis above. They are not measured customer results.
Why it matters
Money-center agility at a community bank’s scale and risk appetite.
- The bank keeps and deepens a key relationship, and brings stable, low-cost commercial deposits onto its balance sheet.
- KYC, BSA, documentation and the ledger of record stay inside the bank, under the controls examiners already review.
- Fabric is a reusable program layer: the next fund administrator or marketplace is a new configuration, not a new build.
Run this scenario on your numbers.
A working session on your institution: the workflow, the model and a first step.