Unlock core banking data for customer and CSR views — financial summaries, transactions, and dispute workflows from any core. Built for customer 360 and servicing channels, not payments routing or BIAN domain scaffolding.
Unlock Any Core: Customer 360 Foundation
Objective: Enable a 360° view of customer financial information by unlocking core and satellite systems — let customers view summaries and transactions and let CSRs refresh data and resolve disputes from one governed API layer. This is the generic core unlock path. If your ledger is Jack Henry SilverLake or Thought Machine Vault, start from the vendor-specific plans instead of forcing generic mappings.
What's Getting Built
- Customer 360 Experience API (Experience API) — channel-facing API with OAuth and per-channel rate limiting ·
GET /customers/{id}/summary, GET /customers/{id}/transactions, POST /disputes
- Bank Accounts Process API (Process API) — aggregates account System APIs so channels stay core-agnostic ·
GET /accounts, POST /accounts/refresh, PUT /disputes/{id}
- Core Banking Customers (System API) — customer records from the core, mapped to canonical identifiers ·
GET /customers/{id}
- Core Banking Accounts (System API) — balances and transactions from the core or satellite ledger ·
GET /accounts/{id}, GET /accounts/{id}/transactions
Prerequisites
- Anypoint Platform org with API Manager and a non-production deployment target.
- MuleSoft Accelerator for Financial Services 1.12 assets imported from Exchange for this use case.
- Target core, CRM, or engagement system credentials available in Secrets Manager or secure properties.
- Core or ledger APIs (REST, SOAP, or file-based) reachable from your Anypoint VPC or on-prem agent.
- Salesforce Financial Services Cloud or custom engagement UI for CSR and digital channels.
Choose your path
- Customer self-service view — Choose when digital banking needs read-only summaries and transaction history with dispute initiation — Experience API fronts Process APIs that aggregate account System APIs.
- CSR servicing view — Choose when contact-center agents must refresh stale balances on demand and resolve disputes — add write-back Process APIs with audit on every mutation.
Core vendor notes
Any core / custom ledger
- Use Core Banking Customers and Core Banking Accounts System APIs when the core exposes REST, SOAP, or file extracts — map institution-specific codes in externalized tables.
- Prefer Process API aggregation before Experience APIs so channels stay core-agnostic.
Jack Henry SilverLake
- If the institution runs SilverLake, switch to the SilverLake Customers/Accounts templates — JHA middleware error codes and institution keys differ from generic cores.
- See Unlock Jack Henry SilverLake Core rather than forcing generic mappings.
Thought Machine Vault
- If the institution runs Vault, use Thought Machine Customers/Accounts templates and the Event Listener for balance and lifecycle changes.
- See Unlock Thought Machine Vault Core for Vault API auth and product version alignment.
1. Business requirements
- Expose latest financial summary and recent transactions per customer.
- Support dispute initiation and CSR resolution with status tracking.
- Keep canonical customer and account identifiers across systems.
- Meet audit requirements for every CSR refresh and dispute action.
2. API-led architecture
- Import Core Banking Customers and Core Banking Accounts System API templates from Exchange.
- Orchestrate aggregation in Bank Accounts Process API before the Experience layer.
- Apply OAuth and rate limiting at the Experience API for channel-specific SLAs.
- Use accelerator canonical models so downstream channels swap cores without rewrites.
3. Data mapping and freshness
- Map core account numbers to external IDs for idempotent reads.
- Define TTL for cached summaries — CSRs get on-demand refresh; customers see near-real-time.
- Normalize currency, status codes, and transaction types in the Process layer.
- Version mappings separately from orchestration flows.
4. Error handling and operations
- Retry transient core timeouts with bounded backoff.
- Return actionable errors when an account is closed or unauthorized.
- Monitor read latency and dispute SLA by channel.
- Alert when core poller or refresh failure rate exceeds threshold.
5. Security and compliance
- Encrypt customer and account data in transit and at rest.
- Audit-log every access to financial records and payment instructions.
- Enforce least-privilege access for integration operators and support users.
- Apply PCI DSS controls wherever cardholder data transits the integration layer.
For additional security patterns, API policies, and reference architecture, see the MuleSoft Accelerator for Financial Services on Anypoint Exchange.
Exchange assets
Import these from the MuleSoft Accelerator for Financial Services 1.12 use-case page on Anypoint Exchange:
| Asset |
Includes |
| Core Banking Customers System API |
API specification, Implementation Template |
| Core Banking Accounts System API |
API specification, Implementation Template |
| Bank Accounts Process API |
API specification, Implementation Template |
| Salesforce Financial Experience API |
API specification, Implementation Template (CSR and digital views) |
Sample payload — Canonical financial summary (Process API response)
{
"customerId": "CUST-88421",
"displayName": "Jordan Lee",
"asOf": "2026-07-30T18:00:00Z",
"accounts": [
{
"accountId": "CHK-001928",
"type": "CHECKING",
"status": "OPEN",
"availableBalance": { "amount": 4210.55, "currency": "USD" },
"recentTransactions": [
{ "id": "TXN-99102", "postedAt": "2026-07-29", "amount": -42.17, "description": "POS DEBIT" }
]
}
]
}
Testing and validation
- Retrieve financial summary for a test customer; confirm accounts, balances, and recent transactions match core source.
- Trigger CSR refresh and verify audit log captures agent, timestamp, and prior vs. new snapshot.
- Initiate a dispute and confirm status is trackable end-to-end.
- Simulate core timeout and verify graceful degradation message to the channel.
Phased rollout
Phase 1 — Connect
- Deploy Customers and Accounts System APIs against sandbox core.
- Wire Experience API to a single pilot branch or digital sandbox.
Phase 2 — Map and test
- Map one product line (e.g., checking) before expanding to loans and cards.
- Complete dispute and refresh test scenarios with operations sign-off.
Phase 3 — Production
- Roll out channel-by-channel with canary traffic and rollback plan.
- Enable production monitoring dashboards for latency and error budgets.
Success metrics
- Summary API p95 latency under channel SLA.
- Dispute resolution cycle time vs. baseline.
- CSR refresh success rate above 99.5%.
Troubleshooting
- Summary returns stale balances after CSR refresh — Likely cause: Process API cache TTL not invalidated on refresh request. Fix: Bypass cache on CSR refresh path and log prior vs. new snapshot in audit table.
- Duplicate accounts in aggregated response — Likely cause: core suffix or institution key not mapped to external ID. Fix: Normalize account keys in System API and dedupe in Bank Accounts Process API.
- 403 for valid customer with open accounts — Likely cause: OAuth scope missing account-read entitlement for the channel. Fix: Align API Manager policies with channel identity and core authorization matrix.
- Dispute initiation succeeds but status never updates — Likely cause: write-back Process API not wired to core dispute module. Fix: Confirm dispute correlation ID round-trips from Experience through Process to core.
Deliverable: Governed Experience and Process APIs exposing unified customer financial summaries, transactions, and dispute workflows unlocked from your core banking platform.