End-to-End Member Journey
This is the single top-level view of a complete CD operation — from the moment a member clicks a CD tile in Candescent OLB, through widget initialisation, to a confirmed transaction and a refreshed dashboard. Every layer that participates is shown in order.System Architecture
This diagram shows every layer of the Self-Service CD system — from the member’s browser through Candescent OLB, the widget SDK, our backend, and the banking cores.Widget Loading Sequence
How the widget initialises from the moment the member clicks the CD tile to the moment the CD management screen appears.CD Operation Flows
Renew a CD
Close & Transfer
Open a New CD
Data Flow — End to End
This table shows what data moves between each layer for a CD renewal operation.| Leg | Direction | Data |
|---|---|---|
| Candescent OLB → Widget (SDK) | Widget receives | customerId, fiId, firstName, lastName, memberNumber via useUserContext() |
| Widget → Nueve Backend | Outbound | accountNumber, term, renewSubAccountType, interestRate, apy, shareId, maturityDate, hostAccountIds |
| Nueve Backend → Banking Core | Outbound | Core-specific payload — format differs per core (Finxact, FIS IBS, Corelation, Fiserv, Symitar) |
| Banking Core → Nueve Backend | Inbound | New account_number, effective_date, interest_rate, apy |
| Nueve Backend → Widget | Inbound | Normalised response — same shape regardless of core |
| Widget → Candescent | Outbound | AccountReloadType.FROM_DB signal + SendSecureMessage with confirmation details |
| Widget → Member (UI) | Display | Account number, effective date, APY, interest rate in success modal |
Per-Core Routing
ThefiId value from useUserContext() tells our backend which banking core to use for this institution. The mapping lives server-side and is never exposed to the widget.