Skip to main content
Follow the steps in Get started with connectors and Sync Hub overview before proceeding. Temenos Payments Hub access: An active account in the Temenos Payments Hub environment and OAuth2 bearer token credentials for REST API access. Network connectivity: Confirmed routing between the Temenos environment and Banking OS Connectivity. For supported options, see Network connectivity.

​
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 Temenos Payments Hub as described in Network connectivity.
  2. Send environment details to Backbase. Send the environment details listed in Reference, including the OAuth2 bearer token and AMQP credentials, 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 consumes payment status events from the configured AMQP queue. No external trigger is required.
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 Temenos endpoint. This typically indicates an upstream service outage at Temenos or a network routing failure.Solution: Verify the operational status of the Temenos Payments Hub environment with Temenos.
Cause: The Temenos 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 Temenos service performance. If the service is operational, review timeout settings in your connector configuration.
Cause: The bearer token provided during setup is incorrect or expired.Solution: Re-verify your credentials with the Temenos 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 app’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 APIM rate limit policy.