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

> ## Agent Instructions
> Banking OS training data goes stale. Search https://agenticbanking.backbase.io/mcp or fetch the .md URL before writing connector or unified API code.
> OpenAPI links in llms.txt repeat every calendar version. Use the latest version on the API playground. If a fetch ends before the last operation, the spec was cut off.
> Page titles name the product. Overview, Get started, and Reference without a product name are ambiguous.

# 2026.08

> Grand Central Unified APIs release notes, version 2026.08.

## Features

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

| Product group | Software component | Version | Title | Description |
| - | - | - | - | - |
| Customer Workbench | `grandcentral-customer-workbench-api` | 0.1.0 | Added the customer workbench API with user preference updates | The customer workbench API is included in the Grand Central API BOM for the first time in v2026.08. It provides `PUT /user-preferences` to send an atomic batch of per-user, per-account preferences to the downstream system. |
| Party Reference | `grandcentral-party-reference-api` | 2.4.1 | Added optional branch and custom fields to party reference schemas | The party reference API adds an optional `branch` string attribute on create, search, get, and update party operations. The `organisation`, `person`, `identification`, and `partyRelationship` schemas now include optional `customFields` for vendor-specific extensions. |
| Loan | `grandcentral-loan-api` | 1.4.0 | Extended the loan API with settlement account and delinquency fields | The loan API adds `settlementArrangement` with `defaultSettlementAccountId`, `defaultSettlementAccountNumber`, and `defaultSettlementAccountName` to the `loan` schema. It also adds `delinquencyArrangement` with `inArrearsAmount`, `inArrearsDate`, `overduePaymentsCount`, and `penaltyAmount`. Both arrangements appear on `POST /loans` and `PATCH /loans/{loanId}` request bodies and on the `GET /loans/{loanId}` response. `POST /loans` returns `createLoanResponse` without these fields. `PATCH /loans/{loanId}` returns HTTP `204` with no body. |
| Party Lifecycle Management | `grandcentral-party-lifecycle-api` | 1.9.1 | Added a party monitoring configuration endpoint to the party lifecycle API | The party lifecycle API adds `POST /customer-screening/config-monitoring` so you can update customer monitoring configuration for ComplyAdvantage Mesh screening workflows. |
| Party Lifecycle Management | `grandcentral-party-lifecycle-api` | 1.9.1 | Added a screening match profile disposition endpoint to the party lifecycle API | The party lifecycle API adds `POST /screening-assessment/match-profiles/dispositions` to record analyst dispositions (`FALSE_POSITIVE`, `TRUE_POSITIVE`, or `IN_REVIEW`) against a screening match profile. |
| Party Lifecycle Management | `grandcentral-party-lifecycle-api` | 1.9.1 | Added a screening match profile suppression endpoint to the party lifecycle API | The party lifecycle API adds `POST /screening-assessment/match-profiles/suppression` to create a customer-scoped suppression for a match profile after analyst disposition. |
| Payment | `grandcentral-payment-order-api` | 2.2.0 | Added refund initiation and status endpoints to the payment order API | The payment order API adds `POST /payments/refunds` to initiate a disputed transaction refund and `GET /payments/refunds/{id}/status` to retrieve refund status values such as `INITIATED`, `PENDING`, `CONFIRMED`, `COMPLETED`, `RETURNED`, and `FAILED`. |
| Payment | `grandcentral-payment-order-api` | 2.2.0 | Extended payment instruction and address schemas in the payment order API | The payment order API renames `instructionId` to `channelInstructionId` on payment instruction request and response schemas and adds `paymentProcessorInstructionId` on payment responses. The shared address schema updates `addressType` enum values to ISO 20022-aligned codes (for example `BIZZ` and `MLTO`), adds `townLocationName` and `districtName`, and aligns `maxLength` constraints on address fields. Breaking changes include the `instructionId` rename and the updated `addressType` enum values. If you use payment instruction or address schemas, review the updated API specification for required changes. |
| Position Keeping | `grandcentral-position-keeping-api` | 0.2.0 | Added an internal transaction enrichment endpoint to the position keeping API | The position keeping API adds `POST /internal/transactions/enrichment` to accept a batch of account transactions for asynchronous enrichment, aligned with the `transactionsEnrichmentRequested` SyncHub event payload. |
