Skip to main content
Follow the steps in Get started with connectors before proceeding. FIS IBS access: An active account in the FIS IBS production or sandbox environment. Network connectivity: Verify that your network routes traffic between the FIS IBS environment and Banking OS Connectivity. For supported options, see Network connectivity. Environment details: You need the following environment details from FIS:

​
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 FIS IBS as described in Network connectivity.
  2. Send environment details to Backbase. Send fis.baseUrl, fis-client-id, fis-client-secret, fis.organization-id, fis.source-id, and ibs-authorization to your Backbase support team.
For property names and defaults, see Reference.

​
Testing the connector

To use the 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 request one. 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 cannot establish a handshake with the FIS IBS endpoint. This typically indicates an upstream service outage at FIS or a network routing failure.Solution: Verify the operational status of the FIS IBS environment with FIS.
Cause: The request to FIS IBS times out before receiving a response. This may indicate high latency or an unresponsive endpoint.Solution: Verify the operational status of the FIS IBS environment.
Cause: The client-id or client-secret provided during setup is incorrect.Solution: Verify your credentials with FIS and contact your Backbase support team to update the connection.
Cause: The ibs-authorization header is missing or contains invalid credentials.Solution: Verify your RACF ID and password with FIS, and ensure the authorization header is correctly formatted.
Cause: The number of incoming requests exceeds the defined threshold for your subscription tier. This “429 Too Many Requests” response protects the stability of the Banking OS and FIS IBS infrastructure.Solution: Review your app’s request patterns to identify unexpected spikes. If you need higher throughput, contact your Backbase support team to request a higher rate limit.