| Product group | Software component | Version | Title | Description |
| -------------- | ------------------------------------------ | ------- | ---------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Temenos | `gc-temenos-party-connector` | 2.1.0 | Added Temenos Transact Party Relationship Connector | The `gc-temenos-party-connector` service now supports managing party relationships in Temenos Transact through the Grand Central Unified Party Relationship API. This lets banks using Temenos Transact create, update, and remove party relationships through a standardized API, reducing the need for custom core banking integrations. The connector supports:
- Adding new party relationships
- Modifying existing party relationships
- Deleting party relationships
Requests are validated against the Grand Central contract, with appropriate error responses for validation failures, missing parties, and Temenos Transact system errors. |
| Temenos | `gc-temenos-party-connector` | 2.0.6 | Added update party details support for retail and corporate customers | The `gc-temenos-party-connector` service now supports updating party details in Temenos Transact through the GC update party API. Banks can update customer profiles for both retail and corporate customers, including addresses, communication details (phone and email), ID documents, and employment details. |
| Temenos | `gc-temenos-party-connector` | 2.0.7 | Added support for retrieving accounts by party ID from Temenos Transact | The `gc-temenos-party-connector` service now supports retrieving accounts by party ID from Temenos Transact through the Grand Central Unified API. Banks can look up all accounts linked to a specific retail or corporate customer without custom integrations. |
| Temenos | `gc-temenos-deposit-connector` | 1.0.0 | Added support for creating deposits in Temenos Transact | The `gc-temenos-deposit-connector` service now supports creating term deposits, savings accounts, and current accounts in Temenos Transact through the Grand Central Unified Deposit API. The connector handles both retail and corporate customer flows and maps Grand Central product identifiers to the corresponding Temenos Transact product IDs. |
| Temenos | `gc-temenos-deposit-connector` | 1.0.0 | Added support for retrieving deposit account details and balances from Temenos Transact | The `gc-temenos-deposit-connector` service now supports retrieving deposit account details and balances from Temenos Transact through the Grand Central Unified Deposit API. The connector aggregates data from multiple Temenos Transact sources to return a unified response, including account status, balance, interest rate, and term details for both retail and corporate customers. |
| Temenos | `gc-temenos-deposit-connector` | 1.0.0 | Added support for closing deposit accounts in Temenos Transact | The `gc-temenos-deposit-connector` service now supports closing deposit accounts in Temenos Transact through the Grand Central Unified Deposit API. The connector determines the deposit type at runtime and routes to the appropriate Temenos Transact closure operation, supporting both retail and corporate customers. |
| Temenos | `gc-temenos-deposit-transaction-connector` | 1.0.0 | Added support for retrieving deposit transactions from Temenos Transact | The `gc-temenos-deposit-transaction-connector` service now supports retrieving deposit transactions from Temenos Transact through the Grand Central Unified Deposit API. The connector supports retrieving transactions for a single deposit account, for multiple deposit accounts, and by transaction ID, for both retail and corporate customers. |
| Correspondence | `gc-docusign-correspondence-connector` | 1.0.0 | Added DocuSign document signing and signing session support to the Grand Central Correspondence API | The `gc-docusign-correspondence-connector` service supports two new DocuSign workflows through the Grand Central Correspondence API. `POST /documents/signature` initiates a digital signature workflow by uploading or referencing a document and defining recipients, and returns an `envelopeId` to track the request. `POST /sign-documents/signing-sessions` creates a signing session and generates a URL to redirect authenticated customers to the DocuSign signing ceremony. Supported signature types are Simple eSignature (SES) and Advanced eSignature (AES), in both embedded and non-embedded variants. |
| Payments | `gc-obpm-payment-connector` | 1.8.0 | Externalized vendor-specific OBPM and FlexCube connection properties to Helm values | Connection settings for OBPM and FLEXCUBE (`baseUrl`, `source`, `ubsComp`, `userId`, `branch`, and `obpm.rest.baseUrl`) are no longer hardcoded in `application.properties`. They are now supplied as `<<...>>` placeholders sourced from `application-live` Helm values at deploy time, allowing deployers to inject environment-specific credentials without modifying the connector. |
| Payments | `gc-obpm-payment-inbound-connector` | 1.3.0 | Added support for ingesting standing instruction payment notifications from OBPM | The `gc-obpm-payment-inbound-connector` now supports ingesting standing instruction (recurring) payment notifications from OBPM and publishing them as Grand Central payment instruction events. The connector uses a single multi-queue JMS receiver to route different OBPM notification queues to separate processing pipelines. |
| Payments | `gc-obpm-payment-inbound-connector` | 1.3.0 | Added support for the `jms.health.check.enabled` toggle for JMS health-check monitoring | The `gc-obpm-payment-inbound-connector` now supports the SDK-standard `jms.health.check.enabled` property to enable or disable JMS health-check monitoring. The previous `jms.local.healthcheck.enable` property is no longer supported. |
| Payments | `gc-obpm-batch-payment-connector` | 1.1.0 | Added configurable payment method code and UUID format normalization for OBPM batch payment messages | The `gc-obpm-batch-payment-connector` now supports a configurable `obpm.batch.payment.method` property to set the payment method code (`TRF`, `CHK`, or `TRA`) in `pain.001.001.03` batch payment messages sent to OBPM. Payment IDs and references containing standard UUIDs are now automatically stripped of hyphens before being sent to OBPM, ensuring compatibility with OBPM's required format. |
| Payments | `gc-obpm-batch-payment-connector` | 1.1.0 | Externalized vendor-specific Azure Service Bus cloud event metadata properties to Helm values | Azure Service Bus cloud event metadata properties (`asb.event.type`, `asb.event.source`, `asb.event.version`) are no longer hardcoded in `application.properties`. They are now supplied as `<<...>>` placeholders sourced from `application-live` Helm values at deploy time, allowing deployers to inject environment-specific values without modifying the connector. |
| Product group | Software component | Version | Title | Description |
| ------------- | ----------------------------------------- | ------- | ------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Temenos | `gc-temenos-party-connector` | 2.1.1 | Fixed phone number format and missing `issuingCountry` in search party response | The `gc-temenos-party-connector` search party response now returns correct data for the following fields:
- Phone numbers now return the country code and subscriber number as separate fields, instead of as a combined string (for example, `+31-2100000000`).
- The `issuingCountry` field is now included in identification records.
|
| FIS Cardbase | `gc-fis-deposit-connector` | 1.2.3 | MAINT-42266: Fixed `relationshipType` not being forwarded to FIS during debit card issuance | The `gc-fis-deposit-connector` now correctly forwards the `relationshipType` to FIS during debit card issuance. Enum values of `PRIMARY` and `SECONDARY` are set deterministically and sent downstream to FIS. |
| Payments | `gc-obpm-payment-connector` | 1.8.0 | Fixed nil OBPM SOAP response handling in the outbound payment flow | A nil OBPM SOAP response body (`xsi:nil="true"` on `HTTP 200`) now returns `HTTP 502` with error code `GC062` through the `initiatePayment` and `fetchBankDetails` routes, instead of propagating downstream as a cryptic "invalid UUID" error. |
| Payments | `gc-obpm-payment-inbound-connector` | 1.3.0 | Fixed `paymentReference` not being populated in recurring payment status updates | When an OBPM payment status update includes an instruction ID, the connector now maps both the instruction ID to `paymentTransaction.id` and the transaction reference number to `paymentTransaction.paymentReference`. Previously only one ID was populated, making it impossible to distinguish the recurring setup reference from the individual payment instance reference. |
| Payments | `gc-obpm-batch-payment-connector` | 1.1.0 | Fixed metadata file not being deleted after `pain.001` file creation | Removed the explicit logic that attempted to delete the event folder after `pain.001` file creation. Azure Blob Storage automatically removes the prefix (virtual folder) once all blobs within it are deleted, so the manual deletion step was both redundant and ineffective for the metadata blob. Both event and metadata files now get cleaned up correctly. |
| Payments | `gc-obpm-batch-payment-inbound-connector` | 1.1.0 | Restored UUID format in batch status events before publishing to Azure Service Bus | OBPM returns batch and payment IDs as 32-character hex strings (without hyphens). The `gc-obpm-batch-payment-inbound-connector` now restores standard UUID format in batch status update events before publishing to Azure Service Bus. The `batchReference` and `endToEndIdentification` fields in published events now reflect canonical UUID format. Non-UUID OBPM-native references pass through unchanged. |
| Product group | Software component | Version | Title | Description |
| ------------- | ---------------------------------------- | ------- | ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Payments | `gc-obpm-payment-connector` | 1.8.0 | Migrated FLEXCUBE to OBPM including JMS code | The `gc-obpm-payment-connector` no longer depends on the FLEXCUBE utils for JMS connectivity. Now OBPM is a completely agile, independent, fast deployable efficient application. |
| Payments | `gc-obpm-payment-inbound-connector` | 1.3.0 | Migrated JMS connectivity from the FLEXCUBE SDK to the dedicated `jms-connector-sdk` | The `gc-obpm-payment-inbound-connector` no longer depends on the FLEXCUBE SDK for JMS connectivity. JMS messaging is now sourced from the standalone `jms-connector-sdk`, imported directly by the connector. |
| Payments | `gc-obpm-batch-payment-connector` | 1.1.0 | Migrated vendor-specific kamelets to the OBPM connector SDK | Vendor-specific kamelets have been moved out of the Grand Central platform and into the `obpm-connector-sdk`, imported directly by the connector. |
| FIS Cardbase | `gc-fis-device-administration-connector` | 1.0.36 | Grand Central BOM updated to v3.0.11 | This update consumes FIS SDK patch updates required for compatibility with the Kong Gateway rollout. |