2026.06 - Grand Central Documentation

Features

The following feature updates are available in 2026.06 for Grand Central Connectors:

Product group	Software component	Version	Title	Description
Onfido	`gc-onfido-party-lifecycle-inbound-connector`	1.0.0	Added support to receive push notifications from Onfido	Grand Central can now receive identity verification results from Onfido once the workflow is complete and the results are available for consumption.
DocSign	`gc-docusign-correspondence-inbound-connector`	1.0.0	Added support to receive push notifications from DocuSign	Grand Central can now receive real-time notifications from DocuSign when a signer completes, declines, or views a document, or when the overall signature request status changes.
Saltedge	`gc-saltedge-payment-order-ob-connector`	1.3.1	Enabled updating the status of a payment transaction for Open Banking UK	Third-party providers now receive the latest status of a payment transaction after the bank customer completes the payment.
Saltedge	`gc-saltedge-payment-order-bg-connector`	1.2.1	Enabled updating the status of a payment transaction for Berlin Group	Third-party providers now receive the latest status of a payment transaction after the bank customer completes the payment.
EBP Deposit	`gc-backbase-ebp-deposit-connector`	1.5.0	Added retail and business line-of-business support to the EBP deposit connector
EBP Deposit Transaction	`gc-backbase-ebp-deposit-transaction-connector`	1.5.0	Added retail and business line-of-business support to the EBP deposit transaction connector
EBP Servicing Consent	`gc-backbase-ebp-servicing-consent-connector`	1.6.0	Added retail and business line-of-business support to the EBP servicing consent connector
Salt Edge	`gc-saltedge-servicing-consent-ob-connector`	1.6.1	Added retail and business line-of-business support to the Saltedge servicing consent connector for Open Banking UK
Saltedge	`gc-saltedge-servicing-consent-bg-connector`	1.6.1	Added retail and business line-of-business support to the Saltedge servicing consent connector for Berlin Group
Payments	`gc-backbase-ebp-payment-order-connector`	1.2.0	Added retail and business line-of-business support to the EBP payment order connector
Saltedge	`gc-saltedge-payment-order-ob-connector`	1.3.1	Added retail and business line-of-business support to the Saltedge payment order connector for Open Banking UK
Saltedge	`gc-saltedge-payment-order-bg-connector`	1.2.1	Added retail and business line-of-business support to the Saltedge payment order connector for Berlin Group
Oracle FLEXCUBE	`gc-flexcube-deposit-connector`	1.7.0	Added APIs to get cards by account ID and unlink a card	The connector now supports retrieving the cards linked to an account and unlinking a card from an account.
Temenos	`gc-temenos-party-connector`	2.2.0	Added an API to retrieve customer details by deposit ID	The Temenos party connector now retrieves customer details by deposit ID.
Temenos	`gc-temenos-loan-connector`	1.0.0	Added APIs to get a list of loans and loan balances	The Temenos loan connector now supports fetching a list of loans and the balances for a specific loan.
Oracle FLEXCUBE	`gc-flexcube-account-inbound-connector`	1.3.0	Added support for Flexcube loan closure events	The account inbound connector now consumes Flexcube loan closure events emitted on the FCUBS_NOTIFICATION topic, surfacing loan-closure data such as the loan ID and the user’s external ID.
Temenos	`gc-temenos-loan-connector`	1.0.0	Added an API to create loans	The Temenos loan connector now supports creating loans through a new API.
Temenos	`gc-temenos-loan-connector`	1.0.0	Added an API to retrieve the amortisation schedule	The Temenos loan connector now retrieves the amortisation schedule for a loan.
Temenos	`gc-temenos-loan-transaction-connector`	1.0.0	Added an API to retrieve loan transactions by transaction ID	The Temenos loan transaction connector now retrieves loan transactions by their transaction ID.
Payments	`gc-obpm-payment-connector`	1.9.0	Added loan repayment support to the OBPM payment connector	The `createSinglePayments` operation now supports a new `LOR` (loan repayment) payment type, so Jetbank customers can repay loans directly from their current or savings accounts. The flow routes through the Flexcube CL service (`FCUBSCLService.CreatePayment`) and returns a synchronous `COMPLETED` status on success. The connector exposes 17 new FCUBS-specific error codes mapped onto Grand Central error codes for clear failure reporting.
Payments	`gc-obpm-payment-connector`	1.9.0	Added international beneficiary sync routing to the OBPM payment connector	The OBPM payment connector now routes payee sync messages as domestic (`<BeneficiarySyncRequest>`) or international (`<InternationalBeneficiarySyncRequest>`) based on the payee’s bank country, compared against the `obpm.contact.sync.domesticCountryCode` configuration property. The payload is byte-identical across both routes; only the wrapping element changes. The default country code is `ZZ` until you configure it per environment.
Payments	`gc-obpm-payment-inbound-connector`	1.4.0	Added ingestion of off-channel FPS and internal payments from OBPM	The OBPM payment inbound connector now ingests off-channel FPS and internal payments originated directly in OBPM, outside the EBP channel. A content-based dispatcher routes incoming `CstmrCdtTrfInitn` JMS messages either to the payment-status update flow or to a payment-ingestion JOLT that publishes the payment as a payments-data event onto Azure Service Bus. Banks can surface off-channel payments to the customer’s transaction list and downstream consumers automatically.
Payments	`gc-obpm-payment-inbound-connector`	1.4.0	Extended JMS listener bootstrap with a provider-driven SPI for alternative JMS providers	The connector’s JMS listener is now selected at runtime through the `InboundListenerStrategyFactory` SPI from the JMS connector SDK v1.0.3. The default WebLogic provider preserves existing behavior for current customers. The SPI lets future deployments swap in alternative JMS providers such as ActiveMQ or IBM MQ without changing connector code. A test-only no-op provider lets the connector build under unit tests without opening a real WebLogic socket.
Temenos	`gc-temenos-payment-connector`	2.0.0	Added the Temenos payment connector with multiple payment types, bank-directory search, and IBAN validation	The Temenos payment connector supports the following services against Temenos Payments Hub R25: Bank-directory search by BIC (with 8-character auto-padding to `XXX`), IBAN, or bank branch code. The response is normalized into the Grand Central `bankReference[]` shape with a full address projection. IBAN validation as a distinct service, triggered by `bankDirectorySource=IBAN-DIRECTORY` on the bank-directory request. The canonical `bankReference[]` includes `customFields.isIBANValid` carrying the raw `YES` or `NO` result. Single payment initiation against `paymentOrders` for six payment product types: SWIFT MX cross-currency (`SWIFTMXCT`) including the SWIFT-FX block, SEPA credit transfer (`SEPA`), TARGET2 high-value (`TARGET2`), internal book transfer (`ACTRF`), EBA INST (`INSTPAY`), and TIPS instant payment (`TIPSPAY`). Returns `INITIATED`, `REJECTED`, or `PENDING` status. Recurring payment initiation through Temenos `standingOrders/{standingOrderId}`. Grand Central `schedule.frequency` maps to Temenos `currentFrequency` interval tokens through per-deployment overrides. Non-persisting validation through `POST /payments/validations`, which reuses the initiation `paymentOrders` endpoint with `validate_only=true` and returns `paymentInformationResponse`. Fee simulation through `POST /payments/fetch-fees`, which returns `feeInformation[]` projected from Temenos `body.charges[]`. Partial updates to future-dated payments through `PUT /payments/{externalReferenceNo}`. Single-payment cancellation through `POST /payments/{externalReferenceNo}/cancel` with `cancellationType=SINGLE_PAYMENT_INSTANCE`. Recurring cancellation through `cancellationType=COMPLETE_SCHEDULE`. Unsupported cancellation types return `GC025` or HTTP 422. Error code mapping (through `temenos-payment-connector-sdk` v0.1.3+) for more than 21 Temenos E-code errors to canonical Grand Central error codes across all payment operations, covering amount, currency, account, beneficiary, bank, FX, cancellation, and reference-overflow failures. Channel clients see clear, structured failure reasons.
Temenos	`gc-temenos-payment-inbound-connector`	1.0.0	Added the Temenos payment inbound connector to republish payment status events to Azure Service Bus	The Temenos payment inbound connector consumes `PPStandalone` payment status events from Temenos Payments Hub over ActiveMQ and AMQP 1.0, and republishes them to the Grand Central payment-status Azure Service Bus topic. Downstream channel services see Temenos Payments Hub payment outcomes in real time without polling. A 7-field JOLT maps the Temenos `iportransaction/` element into `data.paymentTransaction.` with an 8-entry status-code lookup (`19`, `235`, and `988` map to `ACCEPTED`; `993`, `996`, `997`, and `998` map to `REJECTED`; `999` maps to `PROCESSED`) and `yyyyMMdd` to ISO `yyyy-MM-ddT00:00:00Z` date normalization. The route, JOLT, header, and retry shapes have byte-for-byte parity with `gc-obpm-payment-inbound-connector`. The connector’s AMQP consumer runs in transacted mode (`inbound.listener.transacted=true`). Transient failures (retryable HTTP 5xx or 429, socket timeout) roll the JMS session back so the broker redelivers the message; permanent failures (non-retryable HTTP 4xx) commit so a poison message cannot loop. Combined with `retryFlag=true` (the default), inbound payment events survive Azure Service Bus outages without manual replay.
Tietoevry	`gc-tieto-evry-device-administration-connector`	2.1.0	Improved per-environment configuration for the Tietoevry device administration connector	Vendor-specific connection URLs and paths have moved out of the connector image and into per-environment Helm values, so banks can promote the same image across `dev`, `test`, and `uat` without code changes.
Tietoevry	`gc-tieto-evry-card-authorization-connector`	1.1.0	Added Google Pay Android support to the Tietoevry card authorization connector	The card authorization connector now sends a `cardAppId` query parameter on Google Pay Android push-provisioning requests, sourced from a per-environment configuration property. Banks can route Google Pay tokenization requests to the correct issuer card application configuration. Apple Pay flows are unchanged.
Tietoevry	`gc-tieto-evry-card-authorization-connector`	1.1.0	Improved per-environment configuration for the Tietoevry card authorization connector	Vendor-specific connection URLs and paths have moved out of the connector image and into per-environment Helm values, so banks can promote the same image across environments without code changes.
Tietoevry	`gc-tieto-evry-card-ecommerce-gateway-webhooks-connector`	1.1.0	Improved per-environment configuration for the Tietoevry card e-commerce gateway webhooks connector	Vendor-specific connection URLs and paths have moved out of the connector image and into per-environment Helm values, so banks can promote the same image across environments without code changes.
Payments	`gc-obpm-payment-connector`	2.0.0	Added v2 of the OBPM payment connector with an ISO 20022 interface	The v2 release of the OBPM payment connector supports all OBPM services through an ISO 20022 standard interface. Most input fields are renamed to follow ISO 20022 standards.

Fixes

2026.06 contains the following bug fixes for Grand Central Connectors:

Product group	Software component	Version	Title	Description
Correspondence	`gc-docusign-correspondence-connector`	1.0.0	Fixed inconsistent attribute naming for `signatureRequestId` and `recipientId` in the DocuSign connector
EBP Deposit Transaction	`gc-backbase-ebp-deposit-transaction-connector`	1.5.0	Fixed pagination when listing transactions filtered by query parameters
Payments	`gc-backbase-ebp-payment-order-connector`	1.2.0	Fixed pagination when listing transactions filtered by query parameters
Saltedge	`gc-saltedge-payment-order-ob-connector`	1.3.1	Fixed the error code returned when a payment is already finalised	The Saltedge response message Payment is already finalised with status Cancelled now maps to the `GC434` error code (it previously mapped to `GC002`).
Saltedge	`gc-saltedge-payment-order-bg-connector`	1.2.1	Fixed the error code returned when a payment is already finalised	The Saltedge response message Payment is already finalised with status Cancelled now maps to the `GC434` error code (it previously mapped to `GC002`).
Oracle FLEXCUBE	`gc-flexcube-loan-connector`	1.4.0	Fixed `secondaryProductId` mapping in `GET <loan-by-id-endpoint>` to support key-value pairs	The get loan by ID API now supports key-value pair mapping for the `secondaryProductId` field.
Payments	`gc-obpm-payment-connector`	1.9.0	Fixed `fetchFees` to return the charge amount in the customer’s debit-account currency	The `fetchFees` service now returns the charge amount and currency in the customer’s debit-account currency (`CHG_AMT_IN_CHG_DR_ACC_CCY` and `CHG_DR_ACC_CCY`) instead of the OBPM internal pricing currency. Bank customers no longer need to perform client-side FX conversion when the charge currency differs from the debit-account currency.
Payments	`gc-obpm-payment-connector`	1.9.0	Fixed debit-account currency mapping for SEPA-Instant payments in the OBPM payment connector	SEPA-Instant (PRI) payments previously used the transfer currency as the debit-account currency. The debit-account currency is now sourced from the frontend-supplied `customFields.payerAccountCurrency` property, so cross-currency SEPA-Instant payments debit the correct account amount.
Payments	`gc-obpm-payment-connector`	1.9.0	Fixed `BeneficiarySync` message format and `updatePayee` payload coverage in the OBPM payment connector	The `BeneficiarySync` downstream message now uses `<bankcode>` instead of the legacy `<Sortcode>`. The `updatePayee` payload now carries the same `BeneficiaryDetails`, `AccountDetails`, and `CopDetails` blocks as `createPayee`. The payee schemas reject empty payloads up front, preventing partial sync messages from reaching the downstream system.

Security

2026.06 contains the following security fixes for Grand Central Connectors:

Product group	Software component	Version	Title	Description
Payments	`gc-obpm-payment-inbound-connector`	1.4.0	Made internal security improvements in the OBPM payment inbound connector	The connector’s JaCoCo coverage configuration no longer excludes Grand Central packages (`com.backbase.gc.**`). Coverage and Sonar analysis now include all connector-owned code. This change is build-time only and has no runtime impact.
FIS Cardbase	`gc-fis-device-administration-connector`	1.1.0	Made internal security improvements in the FIS device administration connector