Release Notes for Client Bank Account APIs: 20/06/2026

This release introduces Bank Account and Transaction Account APIs for client-owned accounts, along with updated API Guides and API Reference documentation. Client bank accounts can now be created, updated, retrieved, and listed through the new Bank Account API surface, independently of the legacy Account API.

Bank Account API changes:

Client-owned bank accounts are supported through the Bank Account API. See the Bank Accounts API Guide Bank Account for ownership model, workflows, status transitions, and payload examples.

New Client Bank Account API endpoints
Client bank accounts are managed through /bank-accounts instead of the legacy /accounts endpoints:

  • Added Create a Bank Account endpoint Create Client Bank Account — supports client.issuing and client.migration workflows
  • Added Update a Bank Account endpoint Update Bank Account — supports the client.direct workflow for status, alias, attributes, and plug-in service provider deposit information updates
  • Added Get a Client Bank Account endpoint Get Bank Account
  • Added List Bank Accounts endpoint List Bank Accounts

Supported create workflows for client bank accounts:

  • client.issuing — issue a new client bank account with a service provider (explicit or implicit)
  • client.migration — migrate an existing client bank account from a service provider into the IF platform using the migration source identifier in the connect container

Supported update workflow for client bank accounts:

  • client.direct — update client bank account fields such as status, alias, and provider-specific attributes
  • Status updates: Supported client bank account status transitions and lifecycle behaviour are documented in the API Guide, including which transitions are available through the public API, applied automatically by the platform, or performed through the Backoffice API. Client Bank Account Status Updates

Webhooks: Existing bank account lifecycle webhooks also apply to client-owned bank accounts when bank account or connection status changes. Bank Account Webhooks

Transaction Account API changes:

Client-owned transaction accounts linked to client bank accounts are supported through the dedicated Transaction Account API. See the Transaction Accounts API Guide Transaction Account for ownership context, workflows, and payload examples.

Transaction Account API endpoints for client-owned accounts:

Supported create workflows for client transaction accounts:

  • client.integrated-pool-account — create a transaction account linked to a client bank account
  • client.internal-ledger-only-account — create a ledger-only transaction account without a bank account
  • client.sub-account — create a sub-account linked to a main transaction account and client bank account

Supported update workflow for client transaction accounts:

  • direct — update editable fields such as alias and provider-specific attributes

Webhooks: Existing transaction account lifecycle webhooks also apply to client-owned transaction accounts. Transaction Account Webhooks

Important Note for the Legacy Client Account API's:

The legacy Client Account API remains available for backward compatibility when legacy client account API access is enabled for the tenant. New integrations should use the Bank Account API and Transaction Account API instead of the legacy Accounts API.

Documentation updates:

  • Expanded the Bank Accounts API Guide with client-owned bank account ownership model, create/update/get/list examples, status transition diagrams, and webhook payload examples
  • Expanded the Transaction Accounts API Guide with client-owned transaction account examples and workflow descriptions
  • Updated the API Reference with request/response examples for Bank Account and Transaction Account create and update operations