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:

• transaction_action: TRANSFER
• amount / asset: Transfer amount and asset
• No transaction fee (transfers are fee-free)
• Both sender and receiver can query their respective transaction records

AUTO_CONVERSION Response
For AUTO_CONVERSION transactions, the response includes:

• Main transaction metadata (ID, status, source/destination assets)
• sub_transactions array with individual steps:
• transaction_id: Sub-transaction ID
• transaction_action: DEPOSIT | CONVERSION | WITHDRAWAL
• status: Current status of the sub-transaction
• source.amount / source.asset: Source amount and asset
• destination.amount / destination.asset: Destination amount and asset (for conversion)
• created_at: Timestamp

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

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.