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

​
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 Fiserv DNA as described in Network connectivity.
  2. Send environment details to Backbase. Send fiservdna.baseUrl, fiservdna.host, device-id, user-id, password, and fiservdna.appId to your Backbase support team.
For property names and defaults, see Reference.

​
Testing your integration

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 Fiserv DNA endpoint. This typically indicates an upstream service outage at Fiserv or a network routing failure.Solution: Verify the operational status of the Fiserv DNA environment. Check the Fiserv status page or contact Fiserv support.
Cause: The request to Fiserv DNA exceeded the configured timeout period. This may indicate performance issues at Fiserv or network latency problems.Solution: Verify the operational status of the Fiserv DNA environment and check for any performance degradation.
Cause: The DirectSignOn credentials provided during setup are incorrect, expired, or the user lacks the required permissions in Fiserv DNA.Solution: Re-verify your credentials with your Fiserv DNA administrator and ensure the user has the required permissions. Contact your Backbase support team to update the connection credentials if needed.
Cause: The SSOTicket or WhoIsResult token has expired based on the ExpirationDate field.Solution: The connector automatically refreshes tokens. If you continue to see errors, verify that the system clock is synchronized.
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 Fiserv DNA 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.