A core banking system is the system of record: it holds the ledgers, accounts, products and postings. A digital banking platform is the channel and journey layer in front of it: mobile and web banking, onboarding, payments, cards and servicing. A digital experience platform (DXP), in the banking sense, is the layer that composes journeys, content, personalisation and engagement across those channels, and in practice it is often sold as part of a digital banking platform, or as another name for one.
The three get confused because vendors use the labels loosely and because each product creeps into its neighbour’s territory. That confusion is expensive: banks buy a new core to fix a slow app, or a new app to fix an inflexible ledger. This guide gives a definition of each layer that can be quoted on its own, shows how the layers stack, and maps common situations to the thing you actually need to buy.
What is a core banking system?
A core banking system is the bank’s system of record: the software that holds customer accounts and the general ledger, defines products (deposits, loans, their interest and fees) and posts every transaction to the books. If two systems disagree about a balance, the core is the one that is right by definition.
Its users are operations, finance and product teams, not customers. It changes slowly and deliberately, because every change touches accounting and regulatory reporting. What a core does not do well is customer experience: screens, journeys, notifications and campaigns belong elsewhere. The Basel Committee’s 2024 report Digitalisation of finance notes that banks’ legacy IT systems may not be sufficiently adaptable to support new technologies, and that integrating new technology with them adds layers of complexity. That is why the layers above the core exist.
What is a digital banking platform?
A digital banking platform is the software layer that delivers a bank’s mobile and web banking to customers: sign-in and security, onboarding, accounts, transfers and payments, card controls, loans and deposits, and service requests, plus the back-office console staff use to run those channels. It reads from and writes to the core and the other systems of record. It does not hold the ledger.
The same Basel Committee report describes this split in passing: banks use APIs between their internal systems, for example for mobile banking, to connect customer-facing applications with the bank’s core systems. A digital banking platform is the product on the customer-facing side of that connection. It changes far more often than the core, because customer expectations and device platforms move faster than accounting does.
What is a digital experience platform (DXP) in banking?
Outside banking, DXP is a general term for software that manages content, personalisation and journeys across websites and apps. In banking, a digital experience platform is the layer that lets a bank compose and change customer journeys, content, segments, campaigns and personalised offers across channels without rebuilding the apps each time.
The overlap with “digital banking platform” is large, and the two terms are often used for the same product. A useful distinction: the digital banking platform label stresses the banking functions (payments, cards, onboarding), while DXP and the related label “engagement banking platform” stress the tooling for shaping the experience around those functions. Some products offer only the tooling and need banking services built underneath; others do both.
Eurisko uses the term in the broader sense. Eurisko DXP is Eurisko’s digital banking platform: a licensed product that combines banking service modules, an engagement layer and a no-code Journey Builder. It is not a core banking system. When any vendor says DXP, ask which of the two meanings applies.
Which adjacent systems get confused with them?
Six other systems sit around these three. Buyers regularly mistake them for a platform, or assume they are included in one.
- Integration layer (middleware) and API gateway: translates and routes calls between channels and systems of record, and exposes controlled APIs to partners. It owns no customer journey and no ledger.
- Digital onboarding and eKYC system: captures identity documents and biometrics, hands off to screening and opens the customer and the account. It can be a module of a digital banking platform or a standalone product.
- Card management system: issues cards and manages their lifecycle, limits and authorisations. It handles cardholder data, and the PCI Security Standards Council addresses PCI DSS to entities that store, process or transmit that data.
- Payment hub: orchestrates incoming and outgoing payments across rails and formats each message for its scheme, increasingly in ISO 20022, which the BIS Committee on Payments and Market Infrastructures describes as a common international financial messaging standard.
- CRM: the record of relationships, leads, cases and interactions that sales and service staff work from. It is not a channel.
- Personal finance management (PFM): categorises transactions and gives customers budgets, goals and insights. It is a capability inside the app, not a platform.
How do the layers stack and talk to each other?
Picture four levels. At the top are the channels customers touch: the mobile app, web banking, and partner apps that reach in through open banking APIs. Below them is the digital banking platform, with its DXP tooling, which holds journeys, sessions, limits and entitlements. Below that is the integration layer, which turns a request such as “pay this bill” into the right calls. At the bottom are the systems of record: the core, the card management system, the payment hub, screening and CRM.
A request travels down and a result travels back up. Events (a posting, a card decline) flow upward so the app can notify the customer. The Basel Committee’s 2019 report on open banking and APIs observed banks implementing APIs that are compatible with legacy systems through middleware layers, and having to upgrade the resilience of some back-end systems because APIs raise availability expectations. Each layer protects the one below it and is limited by it.
| Layer | What it owns | Who uses it | Typical change pace | If it is missing |
|---|---|---|---|---|
| Core banking system | Accounts, ledger, products, postings | Operations, finance, product teams | Slow: planned releases | No bank: nothing can be booked |
| Digital banking platform | Channels, journeys, sessions, entitlements | Customers, channel and service teams | Fast: frequent releases | Branch and call centre only |
| DXP tooling | Journey design, content, segments, campaigns | Product, marketing and digital teams | Continuous: configuration | Every change needs developers and an app release |
| Integration layer and API gateway | Routing, translation, API security | Integration and architecture teams | With each new system or API | Point-to-point links, costly change |
| Onboarding and eKYC | Identity capture, verification, screening hand-off | Applicants, compliance, operations | When rules or ID schemes change | Account opening stays in the branch |
| Card management system | Card lifecycle, limits, authorisation | Card operations | Slow: scheme-driven | No card issuing or card controls |
| Payment hub | Payment orchestration, rail formats | Payment operations | When rails or formats change | Each rail wired separately |
Which one do you actually need?
Start from the symptom, not from the product category.
- Channels are the pain (the app is slow to change, poorly rated, or missing features the core already supports): a digital banking platform. Leave the core where it is.
- Product flexibility is the pain (you cannot launch the product, pricing or posting behaviour you want, or the ledger cannot run around the clock): a core programme, usually a progressive one. A new app will not help.
- Launching a new digital brand: a digital banking platform with strong DXP tooling and digital onboarding first. Whether the brand also needs its own core depends on the licence and the product set.
- Adding one capability (eKYC, PFM, card controls, a new payment rail): the adjacent system or module, provided your integration layer can carry it. Do not replace a platform to add a feature.
What are the common mis-buys?
Buying a core to fix a channel problem is the costliest: it is the longest and riskiest programme a bank can run, and the app is unchanged at the end unless the channels are rebuilt as well. The reverse mistake is buying a platform to fix a core problem. The new app exposes the same product limits behind a better screen, and new journeys promise things the ledger cannot do.
Three quieter mistakes follow from loose definitions. Assuming the channel module that ships with your core is a digital banking platform: it may be, but score it on the same criteria as the alternatives, including how its releases are tied to the core’s. Buying experience tooling with no banking services underneath, so that the bank ends up building payments and cards itself. And skipping the integration layer, which leaves the app wired directly to the core and makes every later change cost twice.
How do the definitions change your RFP?
Vague category names produce proposals you cannot compare. In the RFP, describe the scope by function, not by label: list what the product must own, what it must only connect to, and which system is the system of record for each data item (balances, limits, customer profile, consent).
A neutral vocabulary helps. BIAN, the Banking Industry Architecture Network, publishes a Service Landscape that it describes as a reference structure for categorising and organising its service domains. Mapping your scope to named functions of that kind stops two vendors from reading “platform” differently. For interfaces, name the standards you expect: ISO 20022 for payment messages and, for open banking, your regulator’s framework or a published standard such as the UK Open Banking Standard, which is issued as API specifications, security profiles, customer experience guidelines and operational guidelines.
Then ask every vendor the same three questions. Which layers does your product own? Which layers does it need from us? And where is it live in front of a core you did not supply?
How Eurisko fits
Eurisko sells the middle of this stack, not the bottom. Eurisko DXP is a digital banking platform in the full sense used above: retail, youth, SME and corporate mobile and internet banking on one codebase, with banking service modules (including onboarding and eKYC and personal finance management), an engagement layer, an integration service and a Journey Builder that lets the bank’s own teams change journeys without an app release. It sits above your middleware and connects to your existing core, card, payment and screening systems, in front of any core. Eurisko has delivered banking software since 2009, with a team of 200+ engineers.
We are not the right choice if your constraint is the ledger itself. Eurisko DXP is not a core banking system, a card management system or a payment hub, and a new channel layer will not remove a product or posting limit underneath it.