> ## 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.10

> Grand Central Unified APIs release notes, version 2026.10.

## Features

The following feature updates are available in 2026.10 for Grand Central Unified APIs:

| Product group | Software component | Version | Title | Description |
| - | - | - | - | - |
| Activity | `grandcentral-activity-api` | 1.2.3 | Added pagination and custom fields to activity responses | Activity list and search responses include pagination metadata and optional custom fields. Shared query options support page-number and cursor-based pagination. |
| Payment | `grandcentral-batch-payment-api` | 1.0.2 | Added a 422 error response to batch cancellation | The batch cancellation API documents the applicable validation errors with an HTTP 422 response. |
| Investment Portfolio | `grandcentral-investment-portfolio-analysis-api` | 0.1.1 | Removed in v0.1.1: duplicate currency from performance positions | **Removed** the `currency` field from the `performancePosition` schema. **Replaced by** the `assetCurrency` field. |
| Loan | `grandcentral-loan-api` | 1.5.1 | Added custom fields across loan API schemas | Loan operation roots and nested loan, product, repayment, settlement, and payment entity schemas support project-specific `customFields`. |
| Loan | `grandcentral-loan-api` | 1.5.1 | Removed in v1.5.1: `customFields` from the bulk card-linkage request | **Removed** `customFields` from `cardLinkageBulkRequest`. **Replaced by** `customFields` on each `cardLinkageRequest`. Callers that sent custom fields on the bulk request send them on the individual linkage item instead. |
| Market Order | `grandcentral-market-order-api` | 0.4.0 | Added currency to market order options | Each order option can include a three-letter ISO 4217 currency code. |
| Party Lifecycle Management | `grandcentral-party-lifecycle-api` | 1.9.3 | Added identity verification routing and client launch fields | The API adds `userData.customerRelationship` for new-to-bank and existing-to-bank routing, and `clientLaunchUrl` for vendor-agnostic web client handoff. |
| Party Lifecycle Management | `grandcentral-party-lifecycle-api` | 1.9.3 | Removed in v1.9.3: legacy identity verification result fields | **Removed** `sessionId`, `applicantId`, `customerUserId`, and `applicantData` from workflow result responses. **Replaced by** `workflowRunId`, `partyInformation`, and `partyIdentification`. The workflow result and callback payloads align with the identity verification event data contract. |
| Payment | `grandcentral-payment-order-api` | 2.6.1 | Added payer and payer account management APIs | The payment order API supports registering, retrieving, searching, updating, and deleting payers and payer accounts. An optional `userId` identifies the user for applicable retrieval and deletion operations. |
| Payment | `grandcentral-payment-order-api` | 2.6.1 | Removed in v2.6.1: `addressLine` from payment order addresses | **Removed** the `addressLine` field from the `Address` schema. **Replaced by** the `addressLines` field. |
| Activity | `grandcentral-activity-event` | 1.0.0 | Added the activity event specification | The activity event specification is included in the Grand Central API BOM for the first time in v2026.10. |
| Activity | `grandcentral-batch-activity-event` | 1.0.0 | Added the batch activity event specification | The batch activity event specification is included in the Grand Central API BOM for the first time in v2026.10. |
| Payment | `grandcentral-batch-payment-event` | 1.0.0 | Added the batch payment event specification | The batch payment event specification is included in the Grand Central API BOM for the first time in v2026.10. |
| Card Case | `grandcentral-card-case-event` | 1.0.0 | Added the card case event specification | The card case event specification is included in the Grand Central API BOM for the first time in v2026.10. |
| Card | `grandcentral-card-transaction-event` | 1.1.0 | Added the card transaction event specification | The card transaction event specification is included in the Grand Central API BOM for the first time in v2026.10. |
| Correspondence | `grandcentral-correspondence-event` | 0.0.1 | Added the correspondence event specification | The correspondence event specification is included in the Grand Central API BOM for the first time in v2026.10. |
| Deposit | `grandcentral-deposit-event` | 1.1.0 | Added the deposit event specification | The deposit event specification is included in the Grand Central API BOM for the first time in v2026.10. |
| Employee Data Management | `grandcentral-employee-data-management-event` | 0.1.1 | Added the employee data management event specification | The employee data management event specification is included in the Grand Central API BOM for the first time in v2026.10. |
| Investment Portfolio | `grandcentral-investment-portfolio-analysis-event` | 1.0.0 | Added the investment portfolio analysis event specification | The investment portfolio analysis event specification is included in the Grand Central API BOM for the first time in v2026.10. |
| Message | `grandcentral-message-event` | 0.1.0 | Added the message event specification | The message event specification is included in the Grand Central API BOM for the first time in v2026.10. |
| Party Lifecycle Management | `grandcentral-party-lifecycle-event` | 0.1.0 | Added the party lifecycle event specification | The party lifecycle event specification is included in the Grand Central API BOM for the first time in v2026.10. |
| Party Reference | `grandcentral-party-reference-event` | 1.2.0 | Added the party reference event specification | The party reference event specification is included in the Grand Central API BOM for the first time in v2026.10. |
| Party Relationship Management | `grandcentral-party-relationship-management-event` | 0.3.1 | Added the party relationship management event specification | The party relationship management event specification is included in the Grand Central API BOM for the first time in v2026.10. |
| Payment | `grandcentral-payment-event` | 1.1.0 | Added the payment event specification | The payment event specification is included in the Grand Central API BOM for the first time in v2026.10. |
| Position Keeping | `grandcentral-position-keeping-event` | 0.1.0 | Added the position keeping event specification | The position keeping event specification is included in the Grand Central API BOM for the first time in v2026.10. |
| Transaction | `grandcentral-transaction-event` | 0.1.0 | Added the transaction event specification | The transaction event specification is included in the Grand Central API BOM for the first time in v2026.10. |
| Foreign Exchange | `grandcentral-foreign-exchange-api` | 1.3.6 | Added the foreign exchange API specification | The foreign exchange API is included in the Grand Central API BOM for the first time in v2026.10. |
| Card Case | `grandcentral-card-case-api` | 0.1.2 | Added the card case API specification | The card case API is included in the Grand Central API BOM for the first time in v2026.10. |
| Document Directory | `grandcentral-document-directory-api` | 0.1.0 | Added the document directory API specification | The document directory API is included in the Grand Central API BOM for the first time in v2026.10. |
| Investment Portfolio | `grandcentral-investment-portfolio-planning-api` | 0.1.1 | Added the investment portfolio planning API specification | The investment portfolio planning API is included in the Grand Central API BOM for the first time in v2026.10. |

## Fixes

2026.10 contains the following bug fixes for Grand Central Unified APIs:

| Product group | Software component | Version | Title | Description |
| - | - | - | - | - |
| Payment | `grandcentral-payment-order-api` | 2.6.1 | Changed payer updates to return `204 No Content` | `PUT /payer/{directory}/registration/{registrationId}` returns an empty HTTP `204 No Content` response. The previous response was HTTP `200` with a payer registration body. Retrieve the updated payer separately if your integration needs the entity. |