Core banking that doesn’t require a core-banking-sized budget.
OREBAN is designed to make modern banking infrastructure accessible without the large upfront and ongoing costs associated with traditional core banking systems.
Five components. Agreed before you sign anything.
Rather than a single licence number, the model is made of parts you can see and scope. Which of them apply depends on how your institution operates.
Platform Subscription
Recurring monthly or annual access to the platform, based on institution size, the capabilities you require and your usage.
- Monthly or annual billing
- Sized to the institution rather than a fixed tier
- Covers the core modules your institution runs on
Transaction Revenue
OREBAN participates in applicable transaction economics, including an agreed share of transfer fees processed through the platform.
- Applies to transfers processed through the platform
- Share agreed with the institution up front
- Scales with activity rather than with headcount
CAMF
Where applicable, OREBAN participates in Current Account Maintenance Fee revenue generated through eligible activity on the platform.
- Applies only to eligible current account activity
- Participation agreed in the commercial terms
Implementation
Migration, configuration, onboarding, training and implementation services based on the institution’s requirements.
- Scoped against your data, products and timelines
- Includes configuration and team training
- Migration and cutover where you are leaving a legacy core
Additional Services
Premium modules, custom integrations and other value-added services are priced separately where required.
- Custom integrations to institution-specific providers
- Premium modules beyond the core subscription
Serious banking capability, not a cut-down core.
The cost advantage comes from the delivery model — cloud infrastructure, configuration instead of custom development, and one integration layer — not from removing what a financial institution needs.
- Customer & account management
- Product engine configuration
- Lending
- General ledger & finance
- Banking operations
- Payments & integration layer
- API access for your channels
- Cloud-based deployment
Four things we need to know to quote.
Pricing is quoted per institution. These are the inputs, so you can come to the conversation with the answers.
Institution size
The scale you operate at — customers, accounts, branches and the teams working inside the core every day.
Capabilities required
Which modules your institution actually runs. A lender configuring loan products has a different footprint from a bank running branches and vaults.
Usage
The transaction activity flowing through the platform, which is also where the usage-based part of the model applies.
Implementation scope
Whether you are launching new or migrating off an existing core, and the state of the data that has to move.
Pricing questions.
What institutions ask before they put a number in a budget.
Because the model is sized to the institution. A digital lender running one product and a microfinance bank running branches, tills and vaults consume very different amounts of the platform, and a published table would misprice both. Send us your requirements and we will quote against them.
No. The platform is accessed through a recurring subscription rather than a perpetual licence. The one-time cost is implementation, which is scoped against your actual requirements.
Migration, configuration, onboarding and training — the work required to get your institution operating on the core, including the mapping, validation and reconciliation stages if you are moving off a legacy system.
The commercial model is built around the capabilities your institution requires, so you are not paying for modules you do not run. We work out that footprint with you before quoting.
Get pricing for your institution.
Tell us your size, the capabilities you need and whether you are migrating, and we will come back with a quote you can take to your board.