Skip to main content
Follow the steps in Get started with connectors before proceeding. Temenos Transact access: An active account in the Temenos Transact production or sandbox environment. Network connectivity: Network connectivity between the Temenos Transact environment and Banking OS Connectivity. For supported options, see Network connectivity. Environment details: You need the following environment detail from Temenos Transact:

​
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 Transact as described in Network connectivity.
  2. Send environment details to Backbase. Send temenos.base.url and the bearer token for the Temenos environment to your Backbase support team.
For property names and defaults, see Reference.

​
Test 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 Temenos Transact endpoint. This typically indicates an upstream service outage at Temenos or a network routing failure.Solution: Verify the operational status of the Temenos Transact environment with Temenos.
Cause: The request to Temenos Transact exceeded the configured timeout period. This may indicate performance issues at Temenos or network latency problems.Solution: Verify the operational status of the Temenos Transact environment and check for any performance degradation. If the service is operational, ask your Backbase support team to review the connector timeouts.
Cause: Network connectivity to the Temenos Transact environment has not been established or has been interrupted.Solution: Verify network connectivity and ensure routing is properly configured between Banking OS and Temenos Transact. Review the Network connectivity documentation for configuration details.
Cause: The bearer token injected by the APIM policy fragment is missing, incorrect, expired, or the user lacks the required permissions in Temenos Transact.Solution: Verify the Key Vault secret backing the Temenos APIM named value holds a current bearer token. Confirm the Temenos policy fragment is applied to the Banking OS APIs routing to Temenos and that it sets the Authorization: Bearer … header. If the token is valid, re-verify permissions with your Temenos administrator.
Cause: The party ID, deposit ID, or loan ID in the request does not match the configured regex pattern.Solution: Verify that the ID matches the pattern defined in regex.party-id.pattern, regex.deposit-id.pattern, or regex.loan-id.pattern. The default patterns accept alphanumeric characters only (party ID: up to 10 characters; deposit ID and loan ID: up to 20 characters).
Cause: The Temenos arrangement bills enquiry returns TGVCP-007 for empty-result, unknown loan ID, malformed loan ID, and pagination cursor errors. The connector cannot distinguish between “loan does not exist” and “no settled bills for this loan”, so both surface as GC301.Solution: Confirm that the loan ID exists in Temenos and has at least one bill with billStatus=SETTLED. If you are paginating through transactions, an overshoot page (from > 0) returns 200 with an empty array rather than 404.
Cause: Temenos arrangement bills do not expose a single-bill lookup, so the connector intentionally returns HTTP 501 with GC023 for GET /loans/transactions/{transactionId}.Solution: Use GET /loans/{loanId}/transactions or POST /loans/transactions instead, and filter the response by transaction ID on the caller side.
Cause: The number of incoming requests exceeded the defined threshold for your subscription tier. This “429 Too Many Requests” response protects the stability of the Banking OS and Temenos Transact infrastructure.Solution: Review your app’s request patterns to identify unexpected spikes. If you need higher throughput, contact your Backbase support team to request an adjustment to your API management rate limit policy.
Cause: The maximum number of connections (http.client.connection.max.total or http.client.connection.max.per.route) has been reached, and no connections are available for new requests.Solution: Review your connection pool configuration and consider increasing the http.client.connection.max.total or http.client.connection.max.per.route values. Ensure your app closes connections after use.