Transaction Types

• DEPOSIT: Fiat or crypto deposit
• WITHDRAWAL: Fiat or crypto withdrawal
• CONVERSION: Asset conversion (buy/sell/convert)
• AUTO_CONVERSION: Auto-conversion rule execution
• TRANSFER: Internal transfer between customers

TRANSFER Response
For TRANSFER transactions:

• Sender sees a TRANSFER transaction with transaction_action: TRANSFER
• Receiver also sees the transfer in their transaction history
• Cross-entity transfers are supported

AUTO_CONVERSION Response
For AUTO_CONVERSION transactions, the response includes a sub_transactions array containing individual transaction steps, ordered as:

1. DEPOSIT - Initial fiat/crypto deposit
2. CONVERSION - Asset conversion (if applicable)
3. WITHDRAWAL - Final fiat/crypto withdrawal (if applicable)

Note:
For SWIFT withdrawals, UETR is populated in the reference field.

Pagination
Two query parameter formats are supported:

• Flat format (recommended): ?page=1&size=10
• Nested format: ?pagination=page=1&size=10

Receiving virtual account

For an attributed fiat deposit, receiving_virtual_account contains virtual_account_id, nickname, and external_id. Use the VA ID as the durable reconciliation key. The nickname and external reference reflect current VA metadata, so a rename can change the label shown on an older transaction. Unset metadata is returned as an empty string.

The field is null when no VA association is available, including transactions that are not attributed fiat deposits. This does not indicate a failed payment. For an auto-conversion flow, inspect the deposit sub-transaction. Archived VAs retain their historical transaction association.

A deposit webhook carries transaction_id; query the transaction to obtain this VA object. See Virtual Accounts.