> For the complete documentation index, see [llms.txt](https://docs.xyb.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyb.co/platform-release-notes/xyb-platform-2.0-release-notes/xyb-platform-2.6-release-notes.md). # XYB Platform 2.6 Release notes #### 1. Open Banking **Connect External Accounts and Move Money Between Them** This release introduces open banking on the platform, allowing customers to connect their accounts at other banks and move money between them. * **Link external accounts:** Customers can link an external bank account and see aggregated balances and transactions alongside their XYB accounts. * **Top up and pay from elsewhere:** Top up from a linked bank, or initiate a payment funded from an account held elsewhere. * **Full consent journey:** Granting, viewing, and revoking access is covered end to end, with a connected-apps view so customers can see exactly which third parties hold access and withdraw it at any time. * **XYB as a provider:** The platform also now serves as a provider, exposing XYB-held accounts and payments to authorised third parties, with a bank picker, provider directory, and institution catalogue included. #### 2. Identity Verification **A Provider-Agnostic Verification Engine with Back-Office Visibility** Identity verification becomes a first-class, provider-agnostic capability with back-office visibility. * **Multiple providers, one interface:** A new identity verification engine supports multiple verification providers behind a single interface, with runtime failover between them if one is unavailable. * **Back-office visibility:** Operators gain a verifications view on the entity record, showing verification history and evidence. * **Policy integration:** Verification outcomes now feed policy decisions directly, so a journey can require a verified identity before proceeding. #### 3. Enterprise Identity: Ping Identity **PingOne as a Login and MFA Provider** Ping Identity (PingOne) is now supported as both a primary login provider and a multi-factor authentication provider. * **Direct authentication:** Banks using PingOne can authenticate customers directly against it. * **MFA and step-up:** Enrol and activate MFA devices, and issue standalone step-up challenges. * **Authorisation delegation:** Delegate authorisation decisions to PingOne Authorize, and use PingOne Verify as an identity verification provider. * **Configurable per entity:** Provider selection is configurable per entity, so different customer populations can use different identity providers on the same platform. #### 4. OAuth 2.0 and OpenID Connect **A Standards-Compliant Authorisation Server** A standards-compliant authorisation server is now part of the platform. * **Full OAuth/OIDC support:** The platform issues and manages OAuth 2.0 grants with OpenID Connect support, including pushed authorisation requests, private key JWT client authentication, the client credentials grant, a UserInfo endpoint, and token revocation to RFC 7009. * **Scoped and configurable:** Grants are bound to the resource server they were issued for, and token lifetimes are configurable per product. * **Fully audited:** The full grant lifecycle is audited. #### 5. Multi-Ledger Support **Run More Than One Ledger, with Full Control Over Routing** Banks can now run more than one ledger behind the platform and control which ledger each product and payment uses. * **Multi-ledger account creation:** Accounts can be created across multiple configured ledgers with all-or-nothing completion. * **Configurable targets:** Ledger targets can be set per product and per payment, with an allow-list controlling which ledgers a given payment may reach. * **Traceable end to end:** Payments carry the product version and ledger target from submission through execution, and per-ledger activity is separately observable. #### 6. Reconciliation: Scheduling and Resolution **From Manual Runs to Scheduled, Self-Service Reconciliation** Reconciliation moves from manual runs to scheduled, self-service operation with a guided resolution flow. * **Scheduled runs:** Reconciliations can now be scheduled on a configured cadence, with runs that wait for their data rather than failing, and clear reporting of waiting, started, and missed windows. * **Guided resolution:** Exception resolution is driven by a catalogue of resolution modes with typed, pre-filled fields drawn from the row being resolved. * **Approval-aware:** Resolutions that require four-eye approval link directly to the pending approval. * **Configurable and recoverable:** Reconciliation profiles can be configured per business customer, a failed run set can be re-run as a fresh run, and every reconciliation carries a queryable audit trail. #### 7. Device Binding **Link, Manage, and Revoke Customer Devices** Customers' devices can now be linked to their identity, managed, and revoked. * **Secure linking:** Device linking uses an SMS verification ceremony, with a configurable limit on linked devices per customer. * **Linked at onboarding:** A customer's first device is linked automatically during onboarding. * **Operator management:** Operators can search and manage devices across customers from the console, and revoking a device immediately ends its sessions. * **Full audit trail:** Every link and revoke leaves a durable record. #### 8. Payments: ACH, Wire and Live Balances **More Transparency and Broader Rail Coverage** Payment operations gain more transparency and better rail coverage. * **Upfront timing information:** Customers can see ACH and wire cutoff times and same-day handling before they submit, choose a payment tier, and see the settlement batch a payment falls into. * **Broader ACH support:** WEB debit origination is now supported on ACH. * **Flexible wire addressing:** Wire beneficiary addresses can be supplied in structured or unstructured format. * **Live balances:** Account balances can now be retrieved live from the banking provider, with ledger, available, and float balances mapped and validated against the platform ledger. #### 9. Improvements and Fixes * **More reliable approval enforcement**, including fixes where payee creation bypassed a configured approval policy and where assessment-policy thresholds were not applied. * **A clearer payment audit trail**, showing the approver rather than the payment creator on approval events, and payment method on payments awaiting approval. * **Numerous console display fixes**, covering overlapping table columns, clipped detail tables, unscrollable filters, and names shown as raw references instead of readable values. * **Fixed a range of issues** across payments, treasury, cards, reconciliation, terms and conditions, and the console, including FedWire payment failures, card search filters, enquiry search, statement scheduling, and payment history search. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.xyb.co/platform-release-notes/xyb-platform-2.0-release-notes/xyb-platform-2.6-release-notes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.