Oracle Banking Payments implementation, built around the networks your bank clears through.
Domestic, cross-border and instant payments on one hub, with ISO 20022 messaging, routing and repair, and a clear handoff to the core.
- SWIFT CBPR+
- SEPA · SEPA Instant
- Local RTGS and ACH
- Book transfers
Where OBPM projects spend their time
Oracle Banking Payments is a payments hub. Oracle ships network rules for major schemes such as SWIFT, SEPA and SEPA Instant. It cannot ship your local clearing rules, your channels, your sanctions vendor or your cut-off times, and that is where most of the effort goes.
So we start with the network map: every scheme the bank clears through, every channel that initiates payments and every system that has to see the status.
Everything OBPM connects
- Validation
- Routing matrix
- Repair queues
- ISO 20022
- Charges
- Status tracking
Eight stops between the channel and the core
- 1InitiateChannel, file or API
- 2ValidateNetwork and bank rules
- 3ScreenSanctions and AML
- 4RouteNetwork by amount, currency, cut-off
- 5MessageISO 20022 MX or local format
- 6SettleClearing or correspondent
- 7PostAccounts and GL in the core
- 8StatusBack to the channel and customer
Repair queue catches anything stages 2–4 reject, with a full audit trail.
Most of a project’s effort sits in stages 1, 3, 6 and 7: your channels, your screening vendor, your clearing rules and your core.
The routing matrix decides the network
We design it with operations, so the rules match how the bank actually clears today, and test every row against cut-off times.
| Currency | Amount | Time | Network |
|---|---|---|---|
| EUR | Up to the scheme limit | 24/7 | SEPA Instant |
| EUR | Any | Before cut-off | SEPA Credit Transfer |
| Local | High value | RTGS hours | Local RTGS |
| Local | Low value | Batch windows | Local ACH |
| Other | Any | Correspondent hours | SWIFT CBPR+ |
Example rows. Your matrix comes from your networks and limits.
Instant payments keep running while the core closes the day
Messages mapped per network
For every network we specify which messages the bank sends and receives, how fields map to the core and the channels, and where MT is still needed.
- pacs.008
- pacs.009
- pacs.002
- pacs.004
- camt.056
- camt.029
- camt.053
- camt.054
Examples. The supported list depends on the OBPM release and the networks configured.
How we implement OBPM
- 01DiscoverNetworks, flows, volumes, cut-offs, channels and screening, the current repair process.
- 02DesignOBPM topology, network setup, routing matrix, accounting and integration with the core, HA and DR for round-the-clock operation.
- 03Build and integrateConfiguration, ISO 20022 mapping, adapters for channels, clearing gateways, SWIFT and screening.
- 04TestEnd-to-end tests with channels, volume and cut-off tests, and the test cycles the clearing operator and SWIFT require.
- 05Go live and runHypercare, then SLA-based L1, L2 and L3 support, 24x7x365 for payment operations.
When this page is for you
- Your local payment system is moving to ISO 20022.
- The bank is launching instant payments.
- Payments are spread across core modules and satellite systems.
- Manual repair volumes keep growing.
- A new core or a FLEXCUBE 14.x upgrade is planned and payments need a new home.
What the bank gets
- A network map with flows, volumes and cut-offs
- OBPM design: topology, routing matrix, accounting handoff, HA and DR
- ISO 20022 mapping specification per network
- Test evidence for each network and channel
- An operations runbook for repair queues and cut-offs
After go-live
The team that implemented OBPM supports it, including upgrades of OBPM together with or separately from FLEXCUBE.
Frequently asked questions
More FLEXCUBE services
Start with the network map.
A fixed-scope discovery maps your payment networks, flows and channels and gives you the OBPM design and an estimate.