How Digital Banking Platforms Are Priced, and What a 400,000-User Bank Really Pays
Vendors quote a per-user fee. Banks also pay for integration, hosting, security testing and escalators. Here's how the license models work and what five years could cost a hypothetical 400,000-user bank.
The quote on page one is less than half the bill
If you're comparing digital banking proposals, the subscription line rarely tells you what you'll spend. Most digital banking platform pricing is built around users: per active user, in tiered bands, or as a flat enterprise license. In the worked example below, that fee comes to about 42% of five-year spend. The rest goes on implementation, integration with your core and card processors, hosting, security assurance and your own staff. Those costs land in your budget, not the vendor's.
This piece explains the common license models, then builds a five-year cost for a hypothetical regional retail bank with 400,000 registered digital users. Every figure is an illustrative 2026 market range, not a vendor quote. Pricing varies widely by contract, region and negotiating leverage, so confirm with vendors before you budget.
Per-active-user pricing and the fight over what counts as active
Per-active-user pricing is common in SaaS digital banking, though vendors such as Backbase, Temenos, Q2 and Infosys Finacle each package and meter it differently. You pay a monthly or annual fee for each user who is active in the period. Typical 2026 ranges run from roughly $3 to $9 per monthly active user (MAU) per year for retail banking, and higher for business banking modules.
Negotiate the definition of "active," not the unit price. Compare these:
- Login-based: active if the user authenticated at least once in the month. This is the most common definition and the fairest to the bank.
- Session or API-call based: background token refreshes or widget calls can count a user who never opened the app. Ask how a push-notification refresh is treated.
- Registered-user based: sometimes called "enrolled." You pay for dormant accounts too, which can inflate the billable base substantially.
- Peak versus average: billing on the highest month of the quarter penalizes banks with salary-day or seasonal spikes.
Insist on a written definition, a monthly usage report you can audit, and a limit on how often the vendor can re-baseline your count.
Tiered bands versus enterprise licenses
Banks that want predictable costs usually move to a tiered or enterprise structure. Each model shifts risk in a different direction.
| Model | How it's priced | Indicative 2026 range | Best fit | Main risk |
|---|---|---|---|---|
| Per active user | Unit fee × monthly active users | $3-$9 per MAU per year (retail) | Banks with uncertain adoption | Cost rises with digital success |
| Tiered bands | Fixed fee per user band, e.g. 200k-300k MAU | Effective $2.50-$7 per MAU per year | Steady growth, predictable budgets | Cliff jump when you cross a band |
| Enterprise subscription | Flat annual fee within a user ceiling | Roughly $1M-$3M per year at this scale | High-adoption banks | Overpaying if adoption stalls |
| Perpetual license | Upfront license plus annual maintenance | Multi-million upfront, with maintenance commonly a fifth of license value per year | Self-hosting banks with strict residency rules | Upgrade costs and lock-in to old versions |
For a bank with 50-70% digital penetration and steady growth, tiered bands with marginal pricing are usually the best balance. Marginal pricing means only users above a band threshold get the new rate, which removes the cliff.
Assumptions behind the hypothetical 400,000-user bank
Say a regional retail bank has 400,000 registered digital users. Sixty percent are monthly active, so 240,000 MAU at go-live, growing 8% a year. It runs a third-party core and outsources card processing. It's replacing an aging in-house web and mobile stack with a SaaS platform on a five-year term.
- Year 1 is the build year. The vendor charges a reduced minimum platform fee of $450,000.
- Live pricing is $5.00 per MAU per year at signing, with a 4% annual escalator applied from Year 2.
- The platform goes live at the start of Year 2, billed on roughly 240k, 259k, 280k and 302k MAU in Years 2-5.
- Scope covers retail web and mobile, onboarding, payments and card controls. Business banking is excluded.
Five-year digital banking platform cost, line by line
All figures are hypothetical, in thousands of USD, and rounded.
| Cost line | Y1 | Y2 | Y3 | Y4 | Y5 | Total |
|---|---|---|---|---|---|---|
| Platform subscription | 450 | 1,248 | 1,401 | 1,574 | 1,767 | 6,440 |
| Vendor implementation and configuration | 2,400 | 300 | 0 | 0 | 0 | 2,700 |
| Core banking integration | 550 | 100 | 60 | 60 | 60 | 830 |
| Card processor integration | 300 | 50 | 30 | 30 | 30 | 440 |
| Hosting and non-production environments | 180 | 260 | 270 | 285 | 300 | 1,295 |
| Penetration testing and security assurance | 90 | 120 | 120 | 120 | 120 | 570 |
| App store accounts, release tooling, app shielding | 60 | 70 | 70 | 70 | 70 | 340 |
| Internal team (product, QA, project management) | 900 | 600 | 450 | 450 | 450 | 2,850 |
| Total | 4,930 | 2,748 | 2,401 | 2,589 | 2,797 | 15,465 |
That's about $15.5 million over five years, or roughly $7.70 per registered user per year. The subscription is only 42% of the total. Implementation plus integration comes to almost $4 million, and more than 80% of it lands before a single customer logs in.
Some lines are routinely underestimated. App store developer accounts are nearly free, but app shielding, code-signing and release tooling are not. Core integration never really finishes: every core upgrade or new product means adapter work. The security line assumes two full penetration tests a year plus retests after major releases, at a broad range of perhaps $40,000-$90,000 per engagement depending on scope and where you hire testers.
Where the price escalators sit in a typical contract
Escalators are rarely in the pricing schedule. They tend to sit in the master agreement, the order form and the hosting annex. Look for these:
- Annual uplift clause. Often a few percent a year, sometimes "CPI plus" with no ceiling. In this model, moving from 4% to an uncapped 7% adds about $470,000 over the term.
- Band step-ups. Crossing a tier can reprice your whole base, not just the extra users.
- Minimum commitments. Floors that rise every year, whatever your actual usage.
- Hosting pass-through. Cloud costs re-billed "at cost plus margin," with the margin undefined.
- Module unbundling. Features included at go-live, such as PFM, chat or card controls, become paid add-ons at renewal.
- Renewal reset. Discounts that apply only to the first term, so Year 6 jumps to list price.
Ask for a hard cap on uplifts, such as the lower of a fixed percentage or local CPI. Ask for marginal tier pricing, and for renewal pricing fixed at no more than the Year 5 rate plus the cap.
How regulation and region change the numbers
The same platform can cost very different amounts depending on where you're licensed. Data residency rules, such as those in India, Indonesia and parts of the Gulf, can rule out a vendor's shared multi-tenant cloud. You may then need a dedicated in-country tenancy, which can sharply raise hosting costs. Some vendors simply aren't sold or supported in every market.
Security testing expectations also vary. EU institutions fall under DORA's operational resilience requirements, which include threat-led penetration testing for entities designated as in scope. The UK has the CBEST framework for firms regulators consider systemically important. Authorities such as MAS in Singapore and the Reserve Bank of India set their own technology-risk and cyber-security expectations. Outsourcing rules may require audit rights and exit plans in the contract, which add legal and transition costs. Have your compliance team and outside counsel confirm the obligations in each jurisdiction before you fix scope.
A negotiating checklist before you sign
Before you shortlist vendors, build the full cost table above for each finalist using their quote and your own internal estimates. Then press on these points:
- A written definition of an active user, plus an auditable monthly usage report.
- An uplift cap, marginal tiering and renewal pricing tied to the Year 5 rate.
- Fixed-price or capped implementation, with milestone payments tied to working releases.
- Named, versioned connectors for your specific core and card processor, not "supported via API."
- Hosting priced as a defined fee, not an open pass-through.
- Exit assistance and data-return terms priced upfront.
The decision rule: if a vendor has the lowest subscription but its integration and hosting lines push five-year cost more than 10% above the next bidder, the cheaper-looking offer is the more expensive one.
Quick answers
What does a digital banking platform typically cost per user?
For retail banking SaaS, typical 2026 market ranges run from roughly $3 to $9 per monthly active user per year for the subscription alone. Once you add implementation, integration, hosting and internal staff, all-in cost per registered user is often well above the subscription rate; the worked example here lands near $7.70. These are indicative ranges that vary by contract and region, so confirm with vendors.
Is per-active-user pricing better than an enterprise license?
Per-active-user pricing suits banks unsure how adoption will go, because costs follow usage. An enterprise license makes more sense once digital penetration is high and stable, since a flat fee avoids paying more as adoption grows. Many mid-sized banks settle on tiered bands with marginal pricing as the middle ground.
How long does implementation take, and what does it cost?
For a bank with several hundred thousand digital users, a full retail web and mobile replacement commonly takes a year or more, depending on core complexity and scope. Vendor implementation fees can run from the low single-digit millions of dollars upward, with core and card integration on top. Fixed-price or capped implementation terms limit how far this can overrun.
Why is core banking integration so expensive?
Each core has its own data model, transaction limits and batch windows, so adapters need custom mapping and extensive testing. The work also continues after go-live, because core upgrades and new products mean adapter changes. Ask vendors for named, versioned connectors for your exact core version.
How often should a digital banking app be penetration tested?
Many banks test at least annually and after major releases, and the worked example assumes two full tests a year. Some regulators set specific expectations, such as threat-led testing for in-scope entities under DORA in the EU or CBEST for systemically important UK firms. Confirm the requirements for your jurisdiction with your compliance team.
What contract terms most often cause cost overruns?
The usual culprits are uncapped annual uplifts, tier step-ups that reprice the whole user base, open-ended hosting pass-throughs and features that become paid add-ons at renewal. First-term discounts that disappear at renewal are another common surprise. Have legal counsel review these clauses before you sign.
Written by the Adviserflow Direct editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.