The Storage Transaction Object in Detail
{
"insights_transaction_id": ?String,
"reference": ?String,
"bank_references": ? {
"unstructured": ?String,
"structured": ?String,
"end_to_end": ?String
},
"amount" : ?Amount,
"booking_date": ?Date,
"value_date": ?Date,
"state": ?Enum<'PROCESSED', 'PENDING', 'CANCELED', 'FAILED'>,
"type": ?Enum<'CREDIT', 'DEBIT'>,
"method": ?Enum<'TRANSFER', 'DIRECT_DEBIT', 'INSTANT', 'UNKNOWN'>,
"bank_transaction_code": ? {
"code": ?String,
"sub_code": ?String,
"description": ?String
},
"counter_party": ?{
"iban": ?String,
"account_number": ?String,
"bic": ?String,
"bank_code": ?String,
"holder_name": ?String,
"holder_address": ?{
"country": ?String
}
},
"category_ids": ?Array<String>,
"category_tag_ids": ?Array<String>,
"labels": ?{
<label_key>: String
}
}
The identifier for this transaction that is a string of up to 128 characters.
Endpoint specific infos:
- create-transactions: If this value is not provided it will be generated.
- update/replace-transactions: This value is required to identify the transaction that should be updated/replaced.
Some banks offer a subset of the transactions reference in different fields. Those fields are given in the BankReference object.
The unstructured reference that was really returned from the bank without any modifications.
This value can be used for reconciliation and transaction matching.
The amount of the transaction. If this property is not set the default is XXX
(as defined in ISO 4217).
The date on which the transaction was booked.
If this property and the value_date
is not set it will be set to today.
The date on which the transaction was valued by the bank (usually in accounting).
If this property and the booking_date
is not set it will be set to today.
The state of the transaction. If this property is not set the default is PROCESSED
.
PROCESSED
- The transaction was processedPENDING
- The transaction is still pending and not yet processedCANCELED
- The transactions was canceledFAILED
- The transaction was not processed
The type of this transacton.
DEBIT
- Funds were withdrawn from the accountCREDIT
- Funds were applied to the account
Must be set if an amount is set.
The type property indicates which transaction method was used.
Possible values are:
TRANSFER
- ADEBIT
transaction that was initiated by the consumerDIRECT_DEBIT
- ADEBIT
transactionINSTANT
- AnINSTANT
transactionUNKNOWN
- A transaction that could not be classified
The Bank Transaction Code as provided by the bank. This information allows the customer to correctly report a transaction, which will help to - for example - perform reconciliation operations.
The values of this object are not normalized and the meaning and format could differ per PSD2-framework or even per bank. For more information, visit the related PSD2-API documentation of the specific banks. Some banks (e.g. Berlin-Group PSD2) follow the ISO-20022 Standard.
Specifies the business area of the underlying transaction.
There is no guarantee that the code
-field follows the ISO-20022 Standard.
Specifies the sub-product family within a specific family.
There is no guarantee that the sub_code
-field follows the ISO-20022 Standard.
A textual description of the bank_transaction_code
.
The other party involved in the transaction. Can be empty for some transactions.
The country of the counter party account holder.
Any amount of labels consisting of key-value pairs can be set on a transaction. Keys have a minimum length of 1 and maximum length of 128. Values have a minimum length of 0 and maximum length of 1024.
Endpoint specific infos:
- update-transactions: add new keys and overwrites existing keys
Skips the transaction categorization of Account Insights and sets this specific list of categories. A list of valid category ids can be retrieved with the category-list endpoint.
Skips the transaction categorization of Account Insights and sets this specific list of category tags. This endpoint is only available to clients who use their own specific categories. See category-list for more information.