Skip to main content
Follow the steps in Getting started before proceeding. Temenos Transact access: An active account in the Temenos Transact production or sandbox environment. Network connectivity: Verify that your network routes traffic between the Temenos Transact environment and Grand Central iPaaS. For supported options, see Network connectivity. Environment details: You need the following environment details from Temenos Transact to configure the connector:
ParameterDescription
temenos-base-urlThe API endpoint URL for the Temenos Transact environment (for example, https://TENANT_NAME.temenos.cloud/irf-provider-container/api/v5.2.0).
temenos-user-idUsername for Basic Authentication.
temenos-passwordPassword for Basic Authentication.

​
Configuration guide

Follow these steps to initialize and authorize your Temenos Transact Connector.

​
1. Establish connectivity

Share connectivity details between Grand Central and Temenos Transact as described in Network connectivity.
Network connectivity to the Temenos Transact environment must be established before proceeding with configuration.

​
2. Temenos Transact authentication

The Temenos Transact Connector uses Basic Authentication for API access. To configure authentication, create a Secrets Operations (SOPS) secret. For more information, see How to create SOPS.
To share credentials between Temenos Transact and Grand Central, consider using 1Password.

​
3. Environment configuration

To initialize the Temenos Transact Connector, define the required environment variables in your gc-applications-live repository. These variables are stored in values.yaml for configuration common to all connectors, and in the following files for connector-specific configuration:
ConnectorPropertyDescription
gc-temenos-party-connectorparty-v0.values.yamlOutbound party connector for party management operations

​
Define common parameters

These variables are stored in values.yaml and are used across all Temenos Transact outbound connectors:
ParameterDescriptionExample value
temenos.base.urlTarget API endpoint for the Temenos Transact environment.https://TENANT_NAME.temenos.cloud/irf-provider-container/api/v5.2.0
http.client.connect.timeoutTimeout in milliseconds for establishing a connection.5000
http.client.request.timeoutTimeout in milliseconds for the complete request.10000
http.client.socket.timeoutTimeout in milliseconds for socket operations.5000
http.client.connection.max.per.routeMaximum number of connections per route.200
http.client.connection.max.totalMaximum total number of connections.200
http.client.proxy.activateEnable or disable HTTP proxy.false
The following example shows the values.yaml configuration: 
# Common Temenos Transact Configuration
# Place this in: values.yaml
connector:
  properties:
    # Temenos Transact Connection Settings
    # temenos.base.url: <Temenos_API_Endpoint>
    
    # HTTP Client Configuration
    # http.client.connect.timeout: <Timeout_Ms>
    # http.client.request.timeout: <Request_Timeout_Ms>
    # http.client.socket.timeout: <Socket_Timeout_Ms>
    
    # Connection Pool Configuration
    # http.client.connection.max.per.route: <Max_Connections_Per_Route>
    # http.client.connection.max.total: <Max_Total_Connections>
    
    # Proxy Configuration
    # http.client.proxy.activate: <true|false>
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO
Place the values files at the following paths: 
iPaaS/azure/runtimes/{runtime}/values/gc-temenos/
├── values.yaml
└── party-v0.values.yaml

​
Define party connector parameters

For the party connector, configure the specific parameters in party-v0.values.yaml: 
# Party Connector Configuration
# Add this to: party-v0.values.yaml
connector:
  properties:
    # Add connector-specific properties here if needed

  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO
HTTP client configuration is inherited from the common parameters defined in values.yaml.
Place the values file at: 
iPaaS/azure/runtimes/{runtime}/values/gc-temenos/party-v0.values.yaml

​
Testing the connector

After configuration, test the connector using the API key authentication:
HeaderValue
api-key<your_subscription_key>
Test the API using the Postman Collection.
For more information about the Grand Central Unified API endpoints that support these features, see Temenos Transact Connector overview.

​
Troubleshooting

If your connector isn’t responding as expected, check these common scenarios.
Cause: The Grand Central 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. If the service is operational, contact Grand Central Support.
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 and performing normally, consider increasing the timeout values (connectTimeout, soTimeout, responseTimeout) in your configuration. Contact Grand Central Support if issues persist.
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 Grand Central and Temenos Transact. Review the Network connectivity documentation for configuration details.
Cause: The temenos-user-id or temenos-password provided during setup is incorrect, expired, or the user lacks the required permissions in Temenos Transact.Solution: Re-verify your credentials with your Temenos administrator and ensure the user has the required permissions. Contact the Grand Central team to update the connection credentials if needed.
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 Grand Central and Temenos Transact infrastructure.Solution: Review your app’s request patterns to identify unexpected spikes. If you need higher throughput, contact the Grand Central team to request an adjustment to your API management rate limit policy.
Cause: The maximum number of connections (maxTotalConnections or connectionsPerRoute) has been reached, and no connections are available for new requests.Solution: Review your connection pool configuration and consider increasing maxTotalConnections or connectionsPerRoute values. Ensure your application is properly closing connections after use.

​
Need more help?

Contact support

Reach out to the Grand Central team for assistance with environment setup, rate limit increases, or configuration guidance.