Skip to main content
Follow the steps in Get started with connectors before proceeding. OBPM access: An active account in the Oracle Banking Payments Manager environment. Network connectivity: Confirmed routing between the Oracle environment and Banking OS Connectivity. For supported options, see Network connectivity. Environment details: You need the following environment details from OBPM and Flexcube:

​
Prepare the connector

Backbase deploys this connector. To share connectivity details and provide the environment details, follow these steps:
  1. Share connectivity details. Share connectivity details between Banking OS and OBPM as described in Network connectivity.
  2. Send environment details to Backbase. Send the environment details in the table above to your Backbase support team.
For property names and defaults, see Reference.

​
Testing your integration

To use the Payments Unified API, include your Banking OS subscription key in the request header. If you don’t have a key, contact your Backbase support team to have one provisioned. The following table shows the required header:
Inbound status testing: The inbound connector automatically fetches the payment status without an external trigger.
Test the API using the Postman collection.

​
Troubleshooting

If your connector isn’t responding as expected, check these common scenarios.
Cause: The Banking OS gateway can’t establish a handshake with the OBPM endpoint. This typically indicates an upstream service outage at Oracle or a network routing failure.Solution: Verify the operational status of the OBPM environment with Oracle.
Cause: The OBPM endpoint didn’t respond before the configured read timeout expired. This typically indicates network latency, an overloaded upstream service, or an incorrectly configured timeout value.Solution: Verify network connectivity and OBPM service performance. If the service is operational, review timeout settings in your connector configuration.
Cause: The client_id or client_secret provided during setup is incorrect.Solution: Re-verify your credentials with the Oracle portal and contact the GC team to update the connection.
Cause: The number of incoming requests has exceeded the defined threshold for your subscription tier. This “429 Too Many Requests” response is a protective measure to ensure the stability of the Banking OS and Core Banking infrastructure.Solution: Review your application’s request patterns to identify unexpected spikes. If your business requirements have evolved and you require a higher throughput, contact your Backbase support team to request an adjustment to your Azure API Management (APIM) rate limit policy.