Get wallet transaction details
GET/v1/transactions/:id
Retrieves detailed information about a specific wallet transaction.
Request
Path Parameters
The ID of the transaction to retrieve
Responses
- 200
- 400
- 403
- 404
Wallet transaction retrieved successfully.
- application/json
- Schema
- Example (from schema)
Schema
data
object
Unique identifier for this transaction
ID of the card transaction that created this wallet transaction
ID of the parent card transaction container (for grouping)
ID of the bank transaction that created this wallet transaction
ID of the parent bank transaction container (for grouping)
ID of the crypto transaction that created this wallet transaction
ID of the parent crypto transaction container (for grouping)
ID of the wallet this transaction affects
Possible values: [USER_REQUESTED, CRYPTO_WITHDRAWAL_INITIATED, CRYPTO_WITHDRAWAL_SUCCESS, CRYPTO_WITHDRAWAL_FAILURE, CRYPTO_DEPOSIT_INITIATED, CRYPTO_DEPOSIT_SUCCESS, CRYPTO_DEPOSIT_FAILURE, BANK_WITHDRAWAL_INITIATED, BANK_WITHDRAWAL_SUCCESS, BANK_WITHDRAWAL_FAILURE, BANK_DEPOSIT_INITIATED, BANK_DEPOSIT_SUCCESS, BANK_DEPOSIT_FAILURE, COLLATERAL_LOCK_SUCCESS, COLLATERAL_LOCK_FAILURE, COLLATERAL_LOCK, USER_TRADE, TRADE_REVENUE_SETTLEMENT, TRADE_ASSET_CREATION, TRADE_FEE_SETTLEMENT, FEE_ADJUSTMENT, CREDIT_LINE_PAYMENT, LP_SETTLEMENT_ACCOUNT_TRANSFER, WITHDRAWAL_FEE_REVENUE, TRADE_ORDER, TRADE_ORDER_RESERVE_SOURCE_ASSET, TRADE_ORDER_RESERVED_TO_CF_BALANCE, TRADE_ORDER_TRANSFER_EXISTING_TARGET_ASSET, TRADE_ORDER_CREDIT_TARGET_ASSET, TRADE_ORDER_DEBIT_SOURCE_ASSET, TRADE_ORDER_CREDIT_SOURCE_ASSET, TRADE_ORDER_FEE_SETTLEMENT, TRADE_ORDER_REVENUE_SETTLEMENT, VIRTUAL_INTERNAL_TRANSFER, MEMBERSHIP_COMMITMENT, DEBIT_CARD_HOLD, DEBIT_CARD_CAPTURE, DEBIT_CARD_REFUND, CLIENT_FEE_REVENUE_SHARE, CLIENT_FEE_CHARGE]
Purpose of the transaction (e.g., DEBIT_CARD_HOLD, BANK_DEPOSIT_SUCCESS)
Possible values: [CREDIT, DEBIT]
Operation type (CREDIT or DEBIT)
Possible values: [AVAILABLE, PENDING, RESERVED, COMMITTED, FEE_REVENUE, CF_BALANCE, TRADE_FEE, SPREAD_REVENUE, LOCKED]
Balance type affected (AVAILABLE, RESERVED, PENDING, COMMITTED)
Transaction amount
Asset code (e.g., USD, BTC)
Possible values: [PENDING, COMPLETED, FAILED, CANCELLED, PROCESSED]
Transaction status
When the transaction was created
{
"traceId": "string",
"message": "string",
"data": {
"id": "550e8400-e29b-41d4-a716-446655440000",
"cardTransactionId": "550e8400-e29b-41d4-a716-446655440001",
"parentCardTransactionId": "550e8400-e29b-41d4-a716-446655440002",
"bankTransactionId": "550e8400-e29b-41d4-a716-446655440003",
"parentBankTransactionId": "550e8400-e29b-41d4-a716-446655440004",
"cryptoTransactionId": "550e8400-e29b-41d4-a716-446655440005",
"parentCryptoTransactionId": "550e8400-e29b-41d4-a716-446655440006",
"walletId": "550e8400-e29b-41d4-a716-446655440007",
"purpose": "DEBIT_CARD_HOLD",
"operation": "DEBIT",
"balanceType": "AVAILABLE",
"amount": "50.00",
"asset": "USD",
"status": "COMPLETED",
"createdAt": "2026-01-15T14:30:00Z"
}
}
Invalid request payload. This can happen if required fields are missing or have invalid formats.
- application/json
- Schema
- Example (from schema)
Schema
{
"traceId": "string",
"message": "string"
}
The API key is invalid or the client does not have sufficient permissions.
- application/json
- Schema
- Example (from schema)
Schema
{
"traceId": "string",
"message": "string"
}
One of the specified resources was not found. Does not apply for empty result set.
- application/json
- Schema
- Example (from schema)
Schema
{
"traceId": "string",
"message": "string"
}