Transaction classification provides insights on the nature of individual transactions of an account. This is enabled by default in the Data API /transactions
endpoint.
It is currently in the beta phase and supports purchase-related (credit/debit card and direct debit category) transactions.
Classification vs. Categorisation
transaction_category
identifies the type of transaction for both account and card transactions. The supported set of categories is consistent across all providers and are mapped according to the information returned by the bank.- Read more about
transaction_category
and the supported categories in our Documentation here.
- Read more about
Transaction classification
returns category information for account transactions. This returns information about the Merchant and the group the transaction is in. These fields are returned subject to availability.
Read more aboutTransaction classification
and the types of categories and subcategories returned here.
More
When calling for /transactions
, you will also see the Transaction type
returned. There are two possible responses:
- CREDIT
Example
{
"results": [
{
"transaction_id": "03c333979b729315545816aaa365c33f",
"timestamp": "2018-03-06T00:00:00",
"description": "GOOGLE PLAY STORE",
"amount": -2.99,
"currency": "GBP",
"transaction_type": "DEBIT",
"transaction_category": "PURCHASE",
"transaction_classification": [
"Entertainment",
"Games"
],
"merchant_name": "Google play",
"running_balance": {
"amount": 1238.60,
"currency": "GBP"
},
"meta": {
"bank_transaction_id": "9882ks-00js",
"provider_transaction_category": "DEB"
}
},
If you need more information
Read our blog post on classification here.
Check out our comprehensive API documentation with more details.
Comments
0 comments
Please sign in to leave a comment.