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

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

​
Testing your integration

To use the Cards Unified API, you must include your Banking OS subscription key in the request header. If you do not have a key, contact your Backbase support team to have one provisioned. Test the API using the Postman collection

​
Troubleshooting

If your connector isn’t responding as expected, check these common scenarios.
Cause: The Banking OS (GC) gateway cannot establish a handshake with the FIS Cardbase endpoint. This typically indicates an upstream service outage at FIS or a network routing failure.Solution: Verify the operational status of the FIS Cardbase environment with FIS.
Cause: The Banking OS (GC) gateway cannot establish a handshake with the FIS Cardbase endpoint. This typically indicates an upstream service outage at FIS or a network routing failure.Solution: Verify the operational status of the FIS Cardbase environment with FIS.
Cause: The client_id or client_secret provided during setup is incorrect.Solution: Re-verify your credentials with the FIS portal and contact your Backbase support 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.