> ## Documentation Index
> Fetch the complete documentation index at: https://agenticbanking.backbase.io/llms.txt
> Use this file to discover all available pages before exploring further.
# 2026.09
> Grand Central Connectors release notes, version 2026.09.
## Features
The following feature updates are available in 2026.09 for Grand Central Connectors:
| Product group | Software component | Version | Title | Description |
| ---------------- | ------------------------------------------------ | ------- | -------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| FIS IBS | `gc-fis-loan-connector` | 1.0.0 | Extended the FIS loan connector to loan API v1.4.0 | The FIS loan connector uses `grandcentral-loan-api` v1.4.0 instead of the 0.1.x contract. Existing loan operations stay on the v1 paths. This is a major connector version (`0.4.0` to `1.0.0`). |
| FIS IBS | `gc-fis-loan-transaction-connector` | 1.1.1 | Extended the FIS loan transaction connector to loan API v1.4.0 | The FIS loan transaction connector uses `grandcentral-loan-api` v1.4.0 instead of the 0.1.x contract. Existing transaction operations stay on the v1 paths. |
| Payments | `gc-obpm-payment-connector` | 2.2.0 | Added create and update payee on OBPM payment connector v2 | The OBPM payment connector v2 supports contact-sync create payee on `POST /payments/payee` and update payee on `PATCH /payments/payee`, with a fire-and-forget JMS hand-off to OBPM. Compared with v1, bank code is read from `bankReference.branchSecondaryIdentification`, and payee address uses the v2 model (`addressType`, `addressLine` as an array, `buildingName`). |
| Payments | `gc-obpm-payment-connector` | 2.2.0 | Enabled payment-rail strategy for single and recurring payments | The OBPM payment connector v2 routes single and recurring payments through the payment-rail strategy, including loan repayment (LOR) on the same path. |
| Payments | `gc-obpm-payment-connector` | 2.2.0 | Added regulatory reporting mapping on OBPM payment initiation | The OBPM payment connector v2 maps the regulatory reporting block (`RgltryRptg`) in the payment initiation transform. |
| Salt Edge | `gc-saltedge-position-keeping-connector` | 1.0.0 | Added the Salt Edge position-keeping connector for transaction enrichment | The Salt Edge position-keeping connector implements `grandcentral-position-keeping-api` v0.3.0. It accepts enrichment requests on `POST /internal/transactions/enrichment`, then creates a Salt Edge categorization bucket, imports accounts and transactions, and starts categorization. |
| Salt Edge | `gc-saltedge-position-keeping-inbound-connector` | 1.0.0 | Added the Salt Edge position-keeping inbound connector for categorization callbacks | The Salt Edge position-keeping inbound connector implements `grandcentral-position-keeping-saltedge-inbound-api` v1.0.0. It receives Salt Edge categorization callbacks, optionally verifies the callback signature, and publishes `transactionsEnriched` events to SyncHub. |
| Oracle FLEXCUBE | `gc-flexcube-kyc-inbound-connector` | 1.0.0 | Added the Oracle FLEXCUBE KYC inbound connector for expiry notifications | The Oracle FLEXCUBE KYC inbound connector consumes `NOTIF_CUSTOMER_EXPY` messages from `NOTIF_KYC_QUEUE`, maps them to the canonical `kycExpired.data` event, and publishes that event to SyncHub. |
| Plaid | `gc-plaid-transaction-enrichment-connector` | 1.0.0 | Added the Plaid transaction enrichment connector | The Plaid transaction enrichment connector implements `grandcentral-position-keeping-api` v0.2.1. It accepts enrichment requests on `POST /internal/transactions/enrichment`, calls Plaid, and publishes a `transactionsEnriched` event. Requests whose accounts hold more than 100 transactions in total are rejected. |
| Feedzai | `gc-feedzai-fraud-detection-connector` | 1.7.0 | Added Feedzai decision-flag mapping for level of assurance | The Feedzai fraud detection connector can map Feedzai `decisionFlag` to Grand Central `levelOfAssuranceRequired` (`Allow` to `LOA_LOW`, `Challenge` to `LOA_SUBSTANTIAL`, `Quarantine` to `LOA_HIGH`, `Block` to `BLOCK`). If Feedzai does not return a decision flag, the existing score-to-level-of-assurance mapping still applies. Set `feedzai.decisionFlag.loa.mapping.enabled` to `true` to turn this on (default `false`). The response includes `customFields.isDecisionFlagUsed` to show which mapping ran. |
| Salt Edge | `gc-saltedge-servicing-consent-bg-connector` | 1.7.0 | Extended Salt Edge PIS create-consent address mapping to ISO 20022 | The Salt Edge servicing consent Berlin Group connector maps the PIS create-consent address block to the ISO 20022 postal-address shape used by `grandcentral-servicing-consent-api` v1.6.0, including `addressLines` as a string array. Integrations that still expect the previous address fields on the create-consent response need to follow the v1.6.0 contract. |
| Salt Edge | `gc-saltedge-servicing-consent-bg-connector` | 1.7.0 | Extended Salt Edge servicing-consent callback paths | The Salt Edge servicing consent Berlin Group connector patches AIS, PIS, and confirmation-of-funds consents on `/api/aspsp/consents` and `/api/aspsp/payments` with an `/authorisation` suffix, and deletes PIS payments separately from AIS and confirmation-of-funds consents. Override `saltedge.ais.update.uri`, `saltedge.pis.update.uri`, `saltedge.pis.delete.uri`, `saltedge.consents.delete.uri`, and `saltedge.cof.update.uri` if you still point at the previous `/api/aspsp/ais`, `/api/aspsp/pis`, `/api/aspsp/cof`, or `/api/aspsp` delete paths. |
| Payments | `gc-obpm-batch-payment-connector` | 1.2.0 | Extended OBPM batch PAIN.001 mappings for originator and payment IDs | The OBPM batch payment connector maps additional PAIN.001 fields on `batchInquiry` and `batchInitiationEvent`. `GrpHdr.CreDtTm` comes from `customFields.batchOrderCreatedAt`. `GrpHdr.InitgPty.Nm` prefers `additions.accountName` and falls back to `companyDetails.companyName`. Payment-information debit fields map from `payments[].customFields.additions` (`originatorAccountName`, `originatorAccountNumber`, `originatorSortCode`). `InstrId` and `EndToEndId` prefer `customFields.additions.paymentStrippedId` and fall back to stripping hyphens from `reference`. |
| Oracle FLEXCUBE | `gc-flexcube-party-connector` | 2.5.0 | Extended FLEXCUBE party update mapping for identity documents | The Oracle FLEXCUBE party connector v2 maps identity document fields on create and update party, including identification number, issue date, expiry date, and document number. Personal overlays for residential and postal data apply only when customer type is individual (`CTYPE=I`), so organisation updates do not receive those overlays. |
| Backbase EBP | `gc-backbase-ebp-deposit-connector` | 1.6.0 | Enabled override of the EBP deposit API base path | The Backbase EBP deposit connector reads `deposit.api.base-path` and `http.retry.enabled` from `application.properties`. The default `deposit.api.base-path` is `/api/arrangement-manager/client-api/v3/arrangements` (previously client API v2). If you still need client API v2, override the property. You can also set HTTP retry per environment without rebuilding the connector. |
| Backbase EBP | `gc-backbase-ebp-deposit-transaction-connector` | 1.6.0 | Extended the EBP deposit transaction connector to client API v5 | The Backbase EBP deposit transaction connector calls transaction-manager client API v5 instead of v3. Filter state and HTTP retry flags are the `transactions.filter.state.value` and `transactions.http.retry.enabled` properties. |
| Oracle FLEXCUBE | `gc-flexcube-loan-connector` | 1.6.1 | RFF-6064: Enabled FLEXCUBE loan summary overdue and penalty details on `GET /loans/{loanId}` | When `flexcube.rest.getLoanSummaryDetails.enabled` is `true`, the connector calls the FLEXCUBE REST loan summary details endpoint (`GET /api-gateway/api/s10/{loanId}:statistics`) in parallel with the `QueryAccount` SOAP call. The connector maps `penalties` to `delinquencyArrangement.penaltyAmount`, `outstanding` to `balance.endingPrincipalBalance`, and `overdue` to `customFields.overdue`. The default for this flag is `false`, so `GET /loans/{loanId}` still uses SOAP only unless you enable this option. Set `flexcube.rest.baseUrl` and `flexcube.rest.getLoanSummaryDetailsUri` as well. |
| Finastra Essence | `gc-finastra-party-connector` | 2.0.1 | Added the Finastra Essence party connector | The Finastra Essence party connector implements `grandcentral-party-reference-api` v2.4.1. It supports `GET` party by ID, `GET /parties/{partyId}/accounts`, party search, `POST /parties`, and `PUT /parties/{partyId}`. `GET /parties/{partyId}/accounts` merges Finastra term deposits, CASA account details, and loans into Grand Central deposits and loans. |
| Finastra Essence | `gc-finastra-deposit-connector` | 1.0.1 | Added the Finastra Essence deposit connector | The Finastra Essence deposit connector implements `grandcentral-deposit-api` v1.3.0. It supports create deposit, get deposit by ID, and get deposit balances. CASA create uses `finastra.casa.deposit-types` (default `CURRENT_ACCOUNT,SAVINGS_ACCOUNT`). `getDepositBalances` calls Finastra `GET /accounts/{accountId}/balances` once per unique `depositIds` value and maps `INTERIMAVAILABLE` to `availableBalance` and `INTERIMBOOKED` to `currentBalance`. |
| Finastra Essence | `gc-finastra-loan-connector` | 1.0.0 | Added the Finastra Essence loan connector | The Finastra Essence loan connector implements `grandcentral-loan-api` v1.4.0. It supports `POST /loans` (`createBasicLoan`) and `GET /loans/{loanId}` (`getBasicLoanDetails`) through `finastra.base.url` and `finastra.create-loan.path` (default `/bfweb/retail/v1/loans`). Finastra-only fields go in `customFields`. `loanId` is validated with `regex.loan-id.pattern` before the vendor call. |
## Fixes
2026.09 contains the following bug fixes for Grand Central Connectors:
| Product group | Software component | Version | Title | Description |
| ---------------- | -------------------------------------- | ------- | --------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Payments | `gc-obpm-payment-connector` | 2.2.0 | Corrected payment instruction status mapping from FAILURE to FAILED | The OBPM payment connector maps OBPM `MSGSTAT` `FAILURE` to `FAILED` on `paymentInstructionReference.status`, so payment-order responses deserialize against the payment status enum. |
| Payments | `gc-obpm-payment-connector` | 2.2.0 | Corrected SI DPP BENEFICIARY2 mapping to the payee party name | The OBPM payment connector maps SI DPP `BENEFICIARY2` to `payeeReference.involvedParty.partyName` instead of the payee bank branch name. |
| Payments | `gc-obpm-payment-connector` | 2.2.0 | MAINT-44522: Mapped international payee address and bank fields on payee sync | The OBPM payment connector v2 maps `defaultCurrency` and `bic` for international payee sync, plus beneficiary and bank address fields and maker-checker identifiers on create and update payee. |
| Temenos | `gc-temenos-payment-connector` | 2.2.0 | Corrected outbound instruction ID formatting for Temenos payment orders | The Temenos payment connector strips hyphens from UUID `instructionId` values on outbound payment-order routes before sending them to Temenos. |
| Temenos | `gc-temenos-payment-inbound-connector` | 1.2.0 | Corrected Temenos inbound `paymentReference` mapping from `sendersReferenceIncoming` | The Temenos Payments Hub payment inbound connector maps `data.paymentTransaction.paymentReference` from TPH `sendersReferenceIncoming` instead of `customerSpecifiedReference`. 32-character hex UUID values are restored to hyphenated form before the connector publishes to Azure Service Bus. Integrations that still expect `paymentReference` from `customerSpecifiedReference` need to follow the new mapping. |
| Temenos | `gc-temenos-payment-inbound-connector` | 1.2.0 | Corrected Temenos inbound JMS rollback on unexpected exceptions | The Temenos Payments Hub payment inbound connector rolls back the JMS session on unexpected Azure Service Bus and network failures, including connection reset. Socket timeouts also roll back when `retryFlag` is `false`. The broker `max-delivery-attempts` policy and dead-letter queue then govern redelivery. |
| Temenos | `gc-temenos-party-connector` | 2.4.2 | Corrected Temenos party search for unknown deposit account IDs | The Temenos party connector returns HTTP 200 and an empty list when party search uses a well-formed `depositAccountId` that does not exist. A Temenos HTTP 404 for no matching records is no longer mapped to `GC445` / HTTP 400. Person and organisation search both follow this empty-result behaviour. |
| Temenos | `gc-temenos-party-connector` | 2.4.2 | Corrected Temenos party search validation for empty `familyName` | The Temenos party connector rejects `GET /parties/search?familyName=` when `familyName` is present but empty. JSON Schema `minLength: 1` returns HTTP 400, and Temenos is not queried with a blank last name. A real family name still returns HTTP 200 with matching parties. |
| Temenos | `gc-temenos-party-connector` | 2.4.2 | Corrected Temenos closed deposit status mapping on `GET /parties/{partyId}/accounts` | The Temenos party connector maps Temenos deposit `accountStatus` `Closed` to Grand Central `CLOSED` on `GET /parties/{partyId}/accounts`. Active deposits still map to `ACTIVE`. |
| Oracle FLEXCUBE | `gc-flexcube-party-connector` | 2.5.0 | Corrected FLEXCUBE party search matching for given and family names | The Oracle FLEXCUBE party connector wraps `firstName`, `middleName`, and `familyName` search values with FLEXCUBE `FULLNAME` wildcards, matching the existing `partyName` wildcard behaviour. Exact-name search no longer returns an empty list for those fields. Email-only or phone-only search omits an empty `FULLNAME` clause. |
| FIS IBS | `gc-fis-loan-transaction-connector` | 1.1.1 | Corrected FIS loan transaction mapping for camelCase vendor fields | The FIS loan transaction connector maps IBSLNTRAN camelCase keys from the live FIS payload. PascalCase lookups no longer drop transaction ID, amount, and balances. |
| Oracle FLEXCUBE | `gc-flexcube-loan-connector` | 1.6.1 | Fixed FLEXCUBE loan connector startup when the REST base URL is unset | The `flexcube.rest.baseUrl` property is optional. SOAP-only deployments can start without a REST base URL. Set the property when you enable REST operations such as loan summary details enrich. |
| Finastra Essence | `gc-finastra-party-connector` | 2.0.1 | Corrected Finastra JOINT deposit co-holder mapping on `GET /parties/{partyId}/accounts` | The Finastra Essence party connector maps each CASA `jointCustomerDetails` and term-deposit `jointHolderNames` entry to its own `parties[]` object, with string `partyId` and `personName.fullName`. Co-holders are no longer collapsed into arrays on a single `parties[1]` item, so the response matches the party-reference schema. |
| Finastra Essence | `gc-finastra-deposit-connector` | 1.0.1 | Corrected Finastra JOINT create-deposit requests to require two parties | When `holderType` is `JOINT`, create deposit schema validation requires at least two `parties` entries and returns HTTP 400 (`minItems`) instead of sending a single-party request to Finastra. CASA create still accepts only `SOLE` and `JOINT` holder types, not `ORGANISATION`. Product identity on create and get deposit by ID uses `product.secondaryProductId` (and optional `description`) instead of `product.productId`. |
## Dependencies
2026.09 has the following dependency updates for Grand Central Connectors:
| Product group | Software component | Version | Title | Description |
| ------------- | ------------------------------ | ------- | ----------------------------------- | ----------- |
| Payments | `gc-obpm-payment-connector` | 2.2.0 | Payment order API updated to v2.2.0 | |
| Temenos | `gc-temenos-payment-connector` | 2.2.0 | Payment order API updated to v2.2.0 | |