Pricing built around
your institution.
CoreWave CBA is configured around the institution, deployment environment, operating model, required modules, transaction activity, migration scope, integrations, training, and support requirements. Speak with Pintop for a commercial proposal based on the system you actually need.
Commercial approach
No misleading one-size-fits-all package.
We first understand your modules, users, branches, integrations, infrastructure, migration requirements, rollout plan, and support expectations before preparing a proposal.
What shapes your
commercial proposal.
The cost of a core banking deployment is influenced by more than a monthly licence. Pintop reviews the complete operating and implementation scope so the proposal reflects the actual work, responsibilities, and support required.
01
Institution profile and scale
Institution type, number of branches or operating entities, active customers, users, transaction activity, products, and expected growth all influence the recommended setup.
02
Modules and workflows
Customer and account management, general ledger, lending, deposits, teller operations, approvals, reporting, audit controls, channels, and institution-specific workflows are scoped according to need.
03
Deployment model
The proposal reflects whether CoreWave CBA will run in a dedicated cloud environment, institution-controlled cloud infrastructure, or another approved deployment arrangement.
04
Migration complexity
Historical customer, account, transaction, loan, deposit, ledger, document, and opening-balance data may require extraction, cleaning, mapping, validation, rehearsal, and controlled cutover.
05
Channels and integrations
Mobile banking, internet banking, USSD, identity verification, payment services, bill payment, cards, credit bureaus, reporting, notifications, and partner systems are scoped separately.
06
Support and service coverage
Support hours, severity levels, response targets, monitoring, release management, operational reviews, regulatory changes, and dedicated support arrangements are agreed in the service terms.
What your implementation
may include.
The final scope is documented in the proposal and service agreement. Depending on the institution, the engagement may cover the following workstreams.
Discovery and fit assessment
Review of the institution, products, users, branches, current system, reports, controls, data, channels, integrations, pain points, risks, and implementation goals.
Configuration
Product setup, chart of accounts, roles, approvals, branches, transaction rules, interest methods, charges, limits, reporting, and operational workflows.
Data migration
Data mapping, cleaning, migration tooling, rehearsal, exception management, balancing, validation, and agreed cutover support.
Integration delivery
Approved connections to customer channels, payment services, identity tools, reporting services, notification systems, and internal or partner applications.
Testing and readiness
User acceptance testing, workflow verification, permissions, reports, integrations, migration checks, reconciliation, security review, and go-live readiness.
Training and launch support
Role-based training, operational walkthroughs, documentation, cutover assistance, stabilisation, issue management, and ongoing support under the agreed service arrangement.
How to receive a
commercial proposal.
The process is designed to establish enough detail for a useful proposal without dragging your team through endless sales calls.
01
Share the requirement
Tell us about your institution, current system, required modules, deployment preference, integrations, migration needs, and expected timeline.
02
Attend a focused walkthrough
We demonstrate the workflows relevant to your operation and identify the areas that need configuration, migration, integration, or further technical review.
03
Confirm the scope
Pintop documents assumptions, implementation responsibilities, modules, environments, integrations, timeline, support, and any exclusions requiring separate work.
04
Receive the proposal
You receive a commercial proposal tied to the agreed scope rather than an attractive number that changes the moment implementation begins.
Bring enough context for a
useful conversation.
You do not need a completed technical specification. A clear view of the current operation and desired outcome is enough to begin.
Helpful details to share
- Institution type and regulatory status.
- Number of branches, entities, staff users, and active customers.
- Current core banking system or operating process.
- Required account, lending, deposit, ledger, and reporting workflows.
- Customer channels and external integrations needed.
- Historical data volume and migration condition.
- Preferred infrastructure or deployment arrangement.
- Target timeline and internal decision process.
Not sure how to define the requirement?
Tell us what is difficult today, which teams are affected, what customers experience, and what the institution needs to improve. We will help turn that into a practical discovery and implementation scope.
Commercial
questions.
These answers explain the general approach. Your signed proposal and service agreement remain the source of truth for the final commercial and implementation terms.
Why is there no fixed public price?
Core banking projects differ significantly in modules, transaction activity, migration, deployment, channels, security, support, and integration requirements. A public figure without those details would be unreliable.
Can we begin with selected modules?
A phased implementation may be possible. The proposal will identify which modules can launch first, the dependencies between them, and the roadmap for later phases.
Is data migration included?
Migration can be included after the current data sources, structure, volume, quality, mapping requirements, validation rules, and cutover responsibilities have been assessed.
Are mobile, web, and USSD channels included?
Channel integrations are scoped according to the institution’s requirements. Existing channels, new customer experiences, authentication, transaction services, reconciliation, and support responsibilities are reviewed separately.
Can CoreWave CBA run on our infrastructure?
Institution-controlled infrastructure may be considered subject to architecture, access, security, monitoring, backup, continuity, support, and operational responsibility requirements.
Can we evaluate the platform before committing?
Pintop can arrange a product walkthrough focused on your institution’s workflows. Any further evaluation environment or technical due-diligence access will be discussed during the engagement process.
Get pricing based on the
institution you operate.
Share your required modules, current core, branches, customer volumes, integration needs, migration expectations, deployment preference, and target timeline. Pintop will use that information to prepare the right next step.