# Transactions
Transactions are a read-only representation of banking operations on a Wallet.
Best practice – Use the Operations feature
If you are using Treezor Connect , the Operations endpoint supersedes this one.
# Key attributes
Attribute | Type | Description |
---|---|---|
transactionId | integer | The unique identifier of the transaction. |
createdDate | string | The date and time at which the transaction was created. |
valueDate | string | The date on which the payment was applied. |
executionDate | string | The date on which the transaction was executed. |
transactionType | string | The type of the transaction. See Transaction Types list. |
name | string | The name of the transaction. |
foreignId | integer | |
walletDebitBalance | string | The balance of the debited Wallet (if any). |
walletCreditBalance | string | The balance of the credited Wallet (if any). |
walletDebitId | integer | The unique identifier of the debited Wallet (if any). |
walletCreditId | integer | The unique identifier of the credited Wallet (if any). |
amount | string | The amount of the transaction. |
currency | string | The currency of the transaction (format: ISO-4217). |
# Transaction Types (transactionType
)
Below the list of possible values for the transactionType
attribute.
1
– Payin2
– Payout3
– Transfer5
– Payin Refund10
– Card Transaction11
– Payout Refund13
– Payin Acquiring14
– Payin Refund Acquiring12
– Card Transaction Payout15
– SCTR Inst16
– Card Transaction payin
# Structure
# Retrieving transactions
The following example searchs for Transactions per userId
and amount
.
Returns an array of Transaction objects.
# Retrieving a single transaction
Returns the corresponding Transaction object.
# Endpoints
Endpoint | Description | Scope |
---|---|---|
/v1/transactions | Search for transactions | read_write |
/v1/transactions/{transactionId} | Retrieve a transaction | read_write |
← IBAN Account Details →