> 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.md).

# XYB Platform 2.0 Release Notes

**Release date:** March 20, 2026

### New Features

* **Risk Engine dashboard:** A new interface for reviewing and managing risk checks, giving you visibility into how transactions are being screened.
* **Admin dashboard:** A new overview dashboard with at-a-glance stats, tables, and cards summarizing key account activity.
* **Cash positions and balances view:** See a consolidated view of your cash positions and account balances directly in the platform.
* **Payee (beneficiary) management:** Create, edit, approve/reject, and block or unblock payees, with full support for all required beneficiary details.
* **Payment initiation and approval workflow:** Initiate payments, route them for approval, and approve or reject them, with four-eye (dual-control) approval support built in.
* **Change request approvals:** A new change request list and detail view lets designated approvers review and approve/reject pending changes.
* **User groups and roles & permissions screen** — Organize users into groups and manage granular roles and permissions from a dedicated screen.
* **Commercial Portal login and shell:** A new, separately branded login experience and application shell for the commercial portal, including support for users with access to multiple accounts.
* **Card management:** Initial card management tools, including card replacement, cancellation, activation, and PIN view requests.
* **Session timeout warning:** You'll now be warned before your session times out due to inactivity.
* **Payment activity audit trail:** A detailed payment view now shows the full audit trail for a given payment.

### Improvements

* Clarified which policies currently apply to an entity in the Entity policy view.
* Deactivated employees can no longer be selected as policy approvers.
* Improved visibility of approvals for managers when a request was initiated by a specialist.
* User invite and edit screens now reflect accurate, up-to-date information.
* General visual polish across the console: sidebar, tables, spacing, borders, focus states, and empty-state messaging.
* Roles displayed in business selection now show all of a user's actual roles, not just one.
* Users can now be assigned multiple roles at once.
* Added a "Feature disabled" message in place of a generic "Not found" error for features that aren't yet available to you.

### Bug Fixes

* Fixed charts in the console showing outdated data when switching between them.
* Fixed rejected payments incorrectly staying in "in processing" status on the Activity screen.
* Fixed an issue where the payment initiation form was not visible in the web app.
* Fixed errors thrown on the Accounts page when a statement was missing.
* Fixed missing localizations for beneficiary dynamic fields.
* Fixed an "unknown component" error that could appear in beneficiary policy setup.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.xyb.co/platform-release-notes/xyb-platform-2.0-release-notes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.