Configuration properties
The outbound connector passes theAuthorization: Bearer header from the incoming Grand Central request through to Temenos unchanged. Configure OAuth 2.0 token acquisition at the Azure API Management (APIM) layer or your calling channel before invoking the connector. The AMQP username and password for payment status events are stored in a SOPS secret, described in SOPS secrets.
gc-temenos-payment-connector
Configure outbound connections inv2/payment-v2.values.yaml.
To route a bank directory request to IBAN validation instead of a standard lookup, set
bankDirectorySource=IBAN-DIRECTORY with identificationType=IBAN on POST /payments/bank-directory. The connector resolves this combination to the temenos.ibanValidationApiUri endpoint.The
externalReferenceNo path parameter on modify and cancel operations maps to the Temenos {paymentOrderId} for single payments or {standingOrderId} for recurring cancellations. Use the paymentInstruction.instructionId returned from the initiation response, not the request-body instruction reference. For recurring cancellation, send cancellationType=COMPLETE_SCHEDULE on POST /payments/{externalReferenceNo}/cancel.gc-temenos-foreign-exchange-connector
Configure outbound foreign exchange connections inforeign-exchange-v1.values.yaml.
The foreign exchange connector accepts one currency pair per request. Grand Central validates
rateType on the inbound request but the connector doesn’t forward it to Temenos.gc-temenos-payment-inbound-connector
Configure inbound connections inpayment-inbound-v1.values.yaml.
SOPS secrets
The connector reads the AMQP broker credentials from thetemenos-amqp-jms-credentials-secret SOPS secret.
Supported operations
The Temenos Payments Hub Connector exposes the Grand Central Unified API for payment initiation, modification, cancellation, and bank directory lookups. For the operation-to-endpoint tables, see Overview. For the full contract, see the unified API specifications.Events
The payment inbound connector consumes payment status events from the Temenos AMQP broker and publishes payment status update events to the Sync Hub ASB producer.
The payment inbound connector consumes messages from the following source.
The payment and foreign exchange connectors are synchronous and don’t publish or consume events.
Error mapping
The connector maps Temenos error codes to Grand Central status codes. For the full list, see Error codes.Dependencies
- Temenos IRF Provider Container REST API (outbound), reachable at
temenos.baseUrl. - Temenos payment events AMQP broker (inbound), reachable at
quarkus.qpid-jms.url. - Sync Hub ASB producer, which receives the published payment status events.