> ## Documentation Index
> Fetch the complete documentation index at: https://grandcentral.backbase.io/llms.txt
> Use this file to discover all available pages before exploring further.
# 2026.04
> Grand Central Connectors release notes, version 2026.04.
## Features
The following feature updates are available in 2026.04 for Grand Central Connectors:
| Product group | Software component | Version | Title | Description |
| --------------------- | --------------------------------------------- | ------- | ------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| FIS Cardbase | `gc-fis-device-administration-connector` | 1.0.35 | Improved name-field handling on the FIS Device Administration Connector | The `createCard` request validates maximum lengths for `personName.firstName` (10), `personName.familyName` (15), and the new `customFields.fullName` (26) at the schema level. Card-name embossing (`cbCrdNmeLne1`) is driven by `customFields.fullName` instead of being derived by concatenating first and last name, so channels have full control over what is printed on the card and silently truncated values at FIS are prevented. |
| Payments | `gc-backbase-ebp-payment-order-connector` | 1.1.0 | Added support for retrieving scheduled payments and standing orders by account | You can retrieve a list of standing orders and future scheduled payments for a specific account. This enables account-level visibility into recurring and upcoming payment activity. |
| Payments | `gc-obpm-direct-debit-mandate-connector` | 1.2.0 | Enabled environment-driven configuration for the OBPM Direct Debit Mandate Connector | The OBPM Direct Debit Mandate Connector externalizes all OBPM connection values (`obpm.baseUrl`, `obpm.source`, `obpm.ubsComp`, `obpm.userId`, `obpm.branch`) and introduces a new `obpm.hostCode` property, all with Helm-compatible placeholder syntax. The previously hardcoded `WBY_WELL HOST_CODE` is supplied at runtime as an exchange-scoped `$hostCode` parameter to the `get-direct-debit-mandate` and `terminate-direct-debit-mandate` request XSLTs, so you can deploy the connector to multiple OBPM environments without rebuilding. |
| EBP Servicing Consent | `gc-backbase-ebp-servicing-consent-connector` | 1.5.0 | Added scheme and type filters to the delete consent feature | You can filter by scheme (Open Banking UK or Berlin Group EU) and consent type (account, payment, or balance check) when deleting consents. This provides flexibility to use the same connector across different regulatory frameworks and consent categories. |
| Payments | `gc-obpm-payment-connector` | 1.7.0 | Added contact sync with create and update payee support | The OBPM Payment Connector syncs beneficiaries to OBPM when they are created or updated. The `createPayee` route validates requests, transforms them into the OBPM `BeneficiarySyncRequest` XML format, and publishes them asynchronously to a configured WebLogic JMS queue, returning an immediate 201 acknowledgment. The `updatePayee` route follows the same pattern for existing beneficiaries, completing the payee lifecycle. The connector aligns with the GC Payment Order API contract 1.4.8 to pick up the payee-service schemas, and introduces a runtime dependency on `flexcube-connector-sdk` 0.1.70 for the `JmsWebLogicQueueReceiver` utility that implements the JMS publishing flow. |
## Fixes
2026.04 contains the following bug fixes for Grand Central Connectors:
| Product group | Software component | Version | Title | Description |
| ------------- | -------------------------------------------- | ------- | ---------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Salt Edge | `gc-saltedge-servicing-consent-ob-connector` | 1.5.0 | Fixed schedule object to align with the payment API | The schedule object mapping aligns with the payment API, covering a wider range of frequency use cases supported by the EBP. |
| Saltedge | `gc-saltedge-servicing-consent-bg-connector` | 1.5.0 | Fixed mapping for the patch consent feature | |
| Payments | `gc-obpm-payment-connector` | 1.7.0 | Standardized response structure for date and time fields in payment services | The connector returns `valueDate` (single payments), `acceptanceDate` (recurring payments), and bank-calendar holidays as ISO-8601 date-time strings (`YYYY-MM-DDT00:00:00Z`). When the underlying OBPM source field (`ActivationDate`, `BOOK_DATE`, or holiday date) is absent, the connector omits the field from the response rather than returning an empty or placeholder string. |