Banking products for your scope.
Explore core banking suites, business domain solutions and technology products for financial institutions. Choose by your bank’s operating model, the business area you want to change, or the technology capability you need.
Business scope and technology capabilities
Choose Core Banking Suites for your institution, Business Domain Solutions for focused business capabilities, or Technology Platforms for product configuration, integration, development and operations.
Core Banking Suites
- Who it’s for
- Commercial, retail and digital banks, including institutions evaluating SaaS core banking.
- What you can do
- Manage customer accounts, deposits, lending and banking operations through the appropriate suite.
- Why choose it
- Choose a suite for your banking operating model and default delivery combination.
Business Domain Solutions
- Who it’s for
- Banks and financial institutions growing their business and improving everyday operations.
- What you can do
- Run lending, payment, card issuing, digital banking and specialist finance services.
- Why choose it
- Start with the business area and customer journeys you want to develop, then select the relevant domain solution.
Technology Platforms
- Who it’s for
- Architecture, development and operations teams responsible for banking systems.
- What you can do
- Define financial products, connect systems, and build, deploy and monitor applications.
- Why choose it
- Choose focused technology capabilities to fit your architecture and application lifecycle.
How banking software and technology relate
Banking Software covers banking operations. Technology Platforms support product configuration, integration, development and operations. Select the combination around your business scope and technical requirements; confirm delivery scope for each project.
Read the Product FoundationAvailability differs by region
Confirm product availability, user-interface languages and relevant local references for your target market and project scope during evaluation.
See customer evidenceDeployment model comparison
On-premises and cloud describe deployment environments. SaaS describes a provider-operated subscription service; its hosting environment and responsibilities are confirmed for the offering.
Deployment environment On-Premises | Deployment environment Dedicated Cloud | Operating model SaaS | |
|---|---|---|---|
| Environment | Deployed on infrastructure controlled by the institution. | A dedicated environment on cloud infrastructure. | Confirmed for the selected service; SaaS alone does not specify the hosting environment. |
| Who operates | Operating responsibilities are agreed for the implementation. | Cloud hosting does not by itself determine operating responsibilities. Confirm the managed-service scope in the proposal. | The provider operates the service; customer administration and support responsibilities are agreed for the offering. |
| Contract and investment | Confirm licence, infrastructure, implementation and operating costs in the proposal. | Subscription to the selected service. Pricing and charging basis are confirmed in the proposal. | |
| Customisation | Agree configuration, extensions and integrations for the selected products and implementation. | Configuration and integration scope depend on the service; confirm supported changes before subscribing. | |
| Evaluation focus | Infrastructure control and the institution’s operating requirements. | Cloud environment, isolation and the division of operating responsibilities. | Service fit, subscription terms and agreed customer responsibilities. |
- Environment
- Deployed on infrastructure controlled by the institution.
- Who operates
- Operating responsibilities are agreed for the implementation.
- Contract and investment
- Confirm licence, infrastructure, implementation and operating costs in the proposal.
- Customisation
- Agree configuration, extensions and integrations for the selected products and implementation.
- Evaluation focus
- Infrastructure control and the institution’s operating requirements.
- Environment
- A dedicated environment on cloud infrastructure.
- Who operates
- Cloud hosting does not by itself determine operating responsibilities. Confirm the managed-service scope in the proposal.
- Contract and investment
- Confirm licence, infrastructure, implementation and operating costs in the proposal.
- Customisation
- Agree configuration, extensions and integrations for the selected products and implementation.
- Evaluation focus
- Cloud environment, isolation and the division of operating responsibilities.
- Environment
- Confirmed for the selected service; SaaS alone does not specify the hosting environment.
- Who operates
- The provider operates the service; customer administration and support responsibilities are agreed for the offering.
- Contract and investment
- Subscription to the selected service. Pricing and charging basis are confirmed in the proposal.
- Customisation
- Configuration and integration scope depend on the service; confirm supported changes before subscribing.
- Evaluation focus
- Service fit, subscription terms and agreed customer responsibilities.
Not sure which unit to evaluate?
Tell us about your institution and what you are evaluating.