INTEGRATIONS

One core. A connected financial ecosystem.

Connect OREBAN to the services your institution needs without tightly coupling the core to individual providers.

Connect once. Expand without rebuilding your core.

CATEGORIES

What connects through the integration layer.

Each category below is marked with its current status. We do not describe a connection as available until it has been verified in production.

AvailableVerified and in productionPlannedOn the roadmap, not yet live

Payments

Planned

Connect the rails your institution moves money on, so transfers reach the core as postings rather than as files to reconcile later.

  • Inbound and outbound transfers
  • Collections and disbursements
  • Transaction reference handling

Identity & KYC

Planned

Verify customers against identity providers during onboarding and attach the outcome to the customer record and its KYC tier.

  • Identity verification at onboarding
  • Document and biometric checks
  • KYC tier assignment

Credit Bureaus

Planned

Pull borrower information into lending decisions and report lending activity back, without wiring the bureau into the core itself.

  • Borrower checks during origination
  • Portfolio reporting submissions
  • Bureau responses stored against the loan

Messaging

Planned

Notify customers about the activity the core generates — postings, status changes and repayment events — through your chosen channel.

  • Transaction alerts
  • Account and loan notifications
  • One-time passcodes

Cards

Planned

Connect card issuing and processing so card activity settles against the same accounts and ledger as everything else.

  • Card issuing partners
  • Authorisation and settlement flows
  • Card transactions posted to the account

Open Banking

Planned

Expose and consume account information through open banking interfaces as the frameworks in your market become available.

  • Account information sharing
  • Consent handling
  • Market framework alignment

Other Financial Infrastructure

Planned

Anything else your institution depends on. The integration layer exists so a new provider is a configuration exercise, not a core project.

  • Institution-specific providers
  • Regulatory reporting destinations
  • Internal systems and data warehouses

Provider-level availability is confirmed with each institution during implementation. Tell us which providers you depend on and we will tell you exactly where they stand.

HOW IT WORKS

Providers connect to the layer. Not to your core.

The integration layer exists so that the institution’s banking infrastructure and its choice of providers can change independently of each other.

The core stays provider-independent

Providers connect to the integration layer, not into the core. Replacing one does not mean reworking your banking infrastructure.

Integrate once, reuse everywhere

A connection made for one product or channel is available to the rest of the institution instead of being rebuilt per system.

Activity lands in the ledger

Money movement through a connected provider resolves into postings in the general ledger, with the provider reference attached.

Tell us who you need to connect to.

Send us the providers your institution depends on and we will confirm what is available today and what is planned.