The four provider types
| Provider type | What you get | What you still have to solve | Fits when |
|---|---|---|---|
| Core banking vendor | Ledger, accounts, transaction processing | Apps, cards, payments, onboarding, back office, compliance tooling | You have an engineering team and want the front end to be your differentiation |
| Banking as a service | Regulated access and rails through a partner's permissions | Product, brand, customer experience, and dependence on the partner's risk appetite | You need to reach market without holding permissions yourself |
| White-label platform | The configured product end to end under your brand | Your market, your customers, your regulatory route | You want a product in market and your differentiation is brand and distribution |
| System integrator | A build to your written specification | Ongoing maintenance of what they built, and every later change as a project | The product itself is the differentiation and you can fund its upkeep |
For the system of record itself, see our guide to core banking software. For the full branded product layer, see white-label digital banking, and for how the second and third types differ, read BaaS versus white-label banking.
The questions that separate providers
- Is the ledger the system of record for every module, or does each module keep its own balances that reconcile overnight?
- Is every capability available over API, so you can build your own front end or distribute features inside a product you already have?
- Are cards, payments, FX and crypto native modules on the same core, or separate integrations you operate yourself?
- Who ships the mobile and web app updates, you or the provider?
- Can onboarding and transaction approvals be expressed as rules that route, hold or escalate, without a developer?
- Are there separate development, staging and production environments with a promotion gate and a rollback?
- Does the provider attach regulatory status to the software? Software does not hold permissions; a regulated entity does. Prefer providers who describe controls rather than status.
- Can they show a live ledger with a real transaction moving through it, rather than slides?
What eBankPlatform provides
At the centre is core banking: the ledger, accounts and transaction processing for electronic money products, acting as the system of record for every module above it. On top sit six modules: white-labeled mobile, web and desktop banking, with updates shipped by us; card issuing, virtual and physical, across the full lifecycle; payments across SEPA, international transfers and merchant payments; crypto accounts, exchange and OTC flows through integrated liquidity providers; multi-currency FX with configurable spreads and live rate feeds; and a rules-based decision system that routes, holds or escalates. The same platform launches as an SME neobank, a consumer neobank, a crypto bank, an OTC desk for crypto and FX, embedded finance, a payment hub or light core banking. Every module is available over API.
If you are still working out the build decision, start with how to launch a neobank. If you are comparing cores specifically, read how core banking software companies compare.
What to verify before you sign
Ask for the ledger. Not a diagram of it, the running thing, with a transaction posted while you watch and the corresponding row appearing. Ask which environments exist and how a release reaches production. Ask what happens to your customer records and balances if you leave. A provider who can answer those three in one session is selling a platform.