Naming Convention Updates — Rebranding, Remote Bank Accounts & Recipient Fields

Rebranded "Unblock" / "DTR" references → "Bakkt"

All references to the legacy "Unblock" and "DTR" brand names have been updated to Bakkt across the API and documentation.

Session header

Before	After
`unblock-session-id`	`bakkt-session-id`

The old unblock-session-id header is still accepted but deprecated and will be removed in a future release. Please migrate to bakkt-session-id.

Bank account paths

Internal ("Unblock") bank account endpoints have been renamed:

Before	After
`/user/bank-account/unblock`	`/user/bank-account/bakkt`
`/user/bank-account/unblock/{account_uuid}`	`/user/bank-account/bakkt/{account_uuid}`
`/user/bank-account/unblock/{account_uuid}/statement`	`/user/bank-account/bakkt/{account_uuid}/statement`
`/corporate/{id}/bank-account/unblock`	`/corporate/{id}/bank-account/bakkt`
`/corporate/{id}/bank-account/unblock/{account_uuid}`	`/corporate/{id}/bank-account/bakkt/{account_uuid}`
`/corporate/{id}/bank-account/unblock/{account_uuid}/statement`	`/corporate/{id}/bank-account/bakkt/{account_uuid}/statement`

All guide code examples and prose now reference the new /bakkt paths.

Renamed "Destination Bank Account" → "Remote Bank Account"

All API endpoint summaries and documentation now use remote bank account instead of "destination bank account". The tag name has also changed from Destination Accounts to Remote Bank Accounts.

This applies to all 8 user and corporate remote bank account endpoints (create, get all, get by UUID, delete).

Renamed `beneficiary_` request fields → `recipient_`

All beneficiary_* fields in request bodies and query parameters have been renamed. The API now accepts the new field names; the previous names are no longer accepted.

Field mapping

Before	After
`beneficiary_type`	`recipient_type`
`beneficiary_first_name`	`recipient_first_name`
`beneficiary_last_name`	`recipient_last_name`
`beneficiary_address`	`recipient_address`
`beneficiary_phone_number`	`recipient_phone_number`
`beneficiary_bank_address`	`recipient_bank_address`
`beneficiary_address_line`	`recipient_address_line`
`beneficiary_country`	`recipient_country`
`beneficiary_state`	`recipient_state`
`beneficiary_postal_code`	`recipient_postal_code`
`beneficiary_city`	`recipient_city`
`main_beneficiary`	`main_recipient`
`beneficiary_uuid` (in payout simulation)	`recipient_uuid`

Affected endpoints

User remote bank accounts:

Method	Path	Changed fields
POST	`/user/bank-account/remote`	`main_recipient`, `recipient_type`, and currency-specific `recipient_address`, `recipient_phone_number`, `recipient_bank_address`, `recipient_first_name`, `recipient_last_name`, `recipient_address_line`, `recipient_country`, `recipient_state`, `recipient_postal_code`, `recipient_city` in `account_details`
GET	`/user/bank-account/remote`	`recipient_type` query parameter
PUT	`/user/bank-account/remote/main`	`main_recipient` in request body
DELETE	`/user/bank-account/remote/{account_uuid}`	— (no renamed fields, uses path param)

Corporate remote bank accounts:

Method	Path	Changed fields
POST	`/corporate/{id}/bank-account/remote`	Same body fields as user POST above
GET	`/corporate/{id}/bank-account/remote`	`recipient_type` query parameter
PUT	`/corporate/{id}/bank-account/remote/main`	`main_recipient` in request body
DELETE	`/corporate/{id}/bank-account/remote/{account_uuid}`	— (no renamed fields)

Payout simulation (sandbox only, not in public API spec):

Method	Path	Changed fields
POST	`/user/wallet/{chain}/simulate-payout`	`recipient_uuid` in request body
POST	`/corporate/{id}/wallet/{chain}/simulate-payout`	`recipient_uuid` in request body

Note: Response fields such as beneficiaryUuid that originate from the underlying platform remain unchanged.

Updated guide documentation

All guide pages now use the updated terminology. Code examples use createRemoteBankAccount instead of addDestinationAccount / addBeneficiary, and prose references reflect the new naming.