September 9, 2026

​

✨ New Features

​

Virtual Accounts

1. New Endpoint: POST /v3/customers/{customer_id}/virtual-accounts Create Virtual Account issues a virtual account for a customer and now lets you choose the banking partner that receives the fiat deposit.
   • source.bank — required. Accepts SSB and PORTAGE. The banks available to you depend on your configuration, and not every bank supports every source rail.
   • The create response now returns deposit_instructions, destination, and bank. customer_id and created_at are no longer returned on create.
2. New Endpoint: GET /v3/customers/{customer_id}/virtual-accounts List Virtual Accounts returns a paginated list of every virtual account belonging to a customer.
3. New Endpoint: GET /v3/customers/{customer_id}/virtual-accounts/{va_id} Get Virtual Account Details returns the full record for a single virtual account, including the deposit instructions the customer funds it with and the crypto destination the deposits settle to. There is no earlier equivalent for this endpoint.

​

Beneficiaries

1. New Field: intermediary_routing_number Create Beneficiary accepts receiver_meta_data.intermediary_routing_number, the routing number of an intermediary bank when a payout has to be routed through one before it reaches the beneficiary bank. This field is required for SWIFT payouts.

​

🛠️ Improvements

​

Beneficiaries

1. Request Examples Split by Rail The bank beneficiary example on Create Beneficiary has been replaced with two examples: a local rail example using bank_account.scheme LOCAL with a FEDWIRE routing number, and an international rail example using bank_account.scheme SWIFT with a SWIFT BIC. Both examples now use the ETHEREUM rail for deposit_instruction and refund_instruction.
2. USD ACH Payouts Coming Soon USD ACH payouts are not yet available. This is now stated on Create Beneficiary.

​

Supported Currencies and Rails

1. EURC Removed From Currency Enums EURC is no longer accepted and has been removed from the currency enums on the following endpoints. USDC and USDT are unaffected.
   • Create Beneficiary — deposit_instruction.currency, refund_instruction.currency, and the external crypto wallet token list
   • Create Virtual Account — destination.currency
   • Create Customer Wallets — currency
2. FEDNOW and SEPA Removed From Virtual Account Source Rails source.rail on Create Virtual Account now accepts ACH, SWIFT, FEDWIRE, and SPEI. FEDNOW and SEPA have been removed.
3. Capabilities Response Examples Updated The response examples on Get Customer Capabilities no longer include EURC tokens, the FEDNOW on-ramp rail, or SEPA off-ramp routes.

​

🗑️ Deprecations and Removals

1. Endpoints Deprecated and Removed After the September 1, 2026 Deprecation Date

   Resource	Removed endpoint	Replacement
   Create individual customer	POST /v1/customers/individual	POST /v2/customers/individual — reference
   Attach individual documents	POST /v1/customers/individual/attach	POST /v2/customers/{customer_id}/individual/attach — reference
   Get customer details	GET /v1/customers/{customer_id}	GET /v2/customers/{customer_id} — reference
   Create beneficiary	POST /v2/beneficiaries	POST /v3/beneficiaries — reference
   Create virtual account	POST /v2/customers/{customer_id}/virtual-accounts	POST /v3/customers/{customer_id}/virtual-accounts — reference
   List virtual accounts	GET /v2/customers/{customer_id}/virtual-accounts	GET /v3/customers/{customer_id}/virtual-accounts — reference
   Fetch transaction details	GET /v1/transactions/{transaction_id}	GET /v2/transactions/{transaction_id} — reference

   PATCH /v1/customers/{customer_id} — Patch Customer RFI is unaffected and remains available.
2. V1 Virtual Account Webhooks Deprecated The virtual_account.created and virtual_account.status events are deprecated and no longer documented. Subscribe to the .v2 events instead, which carry the same fields plus rfi and developer_fee_fixed.

   Deprecated event	Replacement
   virtual_account.created	virtual_account.created.v2 — reference
   virtual_account.status	virtual_account.status.v2 — reference

   Both event names have been removed from the type enum on the webhook event envelope. The status values differ between the two versions: the deprecated events returned ACTIVE, INACTIVE, and SUSPENDED, while the .v2 events return PROCESSING, IN_COMPLIANCE, REQUEST_FOR_INFORMATION, ACTIVE, INACTIVE, and DECLINED. All other webhook events are unaffected.