API Reference

Enrich transactions

post
https://api.moneyhub.co.uk/caas/v1/transactions/enrich

Requires the caas:transactions:write scope. Upload transactions to be enriched by Moneyhub's Data Enrichment Engine

Body Params
string
length between 8 and 36

Unique identifier for the customer/user.

string
required
length between 8 and 36

Unique identifier for the account.

string
required
length between 8 and 36

Unique identifier for the transaction.

string
enum
required

The account type. Permitted values as follows: 'cash' - current accounts; 'card' - credit cards; 'savings' - savings accounts; 'investment' - investment accounts; 'loan' - loan accounts; 'mortgage' - mortgage accounts; 'pension' - pension accounts

Allowed:
string

The transaction code. Permitted values as follows: 'DEB' - general debit card transaction; 'CR' - general bank credit; 'TFR' - general transfer to/from; ')))' - contactless purchase; 'DD' - direct debit; 'SO' - standing order; 'BGC' - bank giro credit; 'ATM' - cash withdrawal; 'CHQ' - cheque; 'CHG' - bank charge. For credit card transactions or if unsure for a transaction set to the empty string. Although we do accept more codes; please supply us a list of the transaction codes you'd like to use and we'll either let you know if they are supported or how you can map onto our transaction codes.

date-time
required

The date and time of the transaction in ISO 8601 format.

string
enum
required

The status of the transaction: e.g. pending, posted (booked)

Allowed:
string
required

The transaction description which is commonly a combination of the merchant name and merchant location.

number
required

The transaction amount in major units of the currency.

string
Defaults to GBP

The currency of the transaction e.g. GBP, EUR. Defaults to GBP

string
length ≤ 4

MCC code for the merchant's primary activities. A maximum 4 digit string which we will left pad with 0s to make 4 digits if necessary.

boolean

Indicates if the cardholder was present when the transaction occurred. Note that, online purchases are considered card holder not present. Only card holder present transactions are eligible for geotagging. Commonly derived from the POS entry mode: e.g. '07' is contactless chip read so card present. Do not specify or set to true if unknown/unsure; the engine uses this field as part of the estimation of a more accurate card present flag.

meta
object

Optional object containing additional data about the transaction. This can be used to store additional information about the transaction.

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Updated 6 months ago

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
*/*

Updated 6 months ago