The core functionality of Ntropy API is the enrichment of transactions. Each transaction is understood by our system and a structured response is returned containing all the extracted information. The API supports both enrichment synchronously up to 4000 transactions and asynchronously up to 24960 transactions in the same batch.
Input Transaction Object
The enrichment process requires a list of transaction objects as input and outputs a list of enriched transaction objects (in the same order) containing additional structured information. The input transaction object contains the following fields:
|Description text of the transaction. Has a maximum length of 1024 characters.
|Direction of the flow of money from the perspective of the account holder. Possible values are incoming and outgoing.
|Amount of the transaction. Should always be a positive number. Use
entry_type to represent the direction of the flow of money.
|Currency of the transaction in ISO-4217 format. See supported options.
|Date when the transaction was made in ISO-8601 format, i.e. YYYY-MM-DD.
|Unique identifier of the transaction in your system.
|(optional) - The country where the transaction was made in ISO-3166-2 format. See supported options.
|(optional) - Unique identifier of the account holder in your system.
|(optional) - Type of the account holder. Possible values are consumer, business, freelance.
In the transaction model, the
amount attribute must always be positive, as the direction of the flow of money is represented only by the
From the point of view of the account holder, if a transaction represents money leaving the account it should have an
entry_type value of
outgoing (debit), and if a transaction represents money entering an account it should have an
entry_type value of
Multiple transactions submitted with the same
transaction_id will be considered the same transaction, where the most recent will replace previous submissions.
While providing account holder information is optional, it is needed for labeling. If neither account_holder_id nor account_holder_type are provided, labeling will be disabled. Check the Account Holder section for more information regarding this. There are other transaction attributes that are not required; however, they should be submitted if known to increase the quality of the results.
Enriched Output Transaction Object
The enriched transactions that are returned by the API will contain the set of fields described below.
|Label from our live hierarchy, depending on the type of account holder (consumer, business).
|Higher level category that groups together related labels
|Indicates whether a transaction is a one-time transfer, e.g. purchasing a mattress (one-off), regularly repeats with personalized pricing, e.g. utilities, mortgage (recurring), regularly repeats with fixed pricing (subscription).
|If a transaction is recurrent, this is a RecurrenceGroup object with fields described below, (null if transaction is not recurrent).
|Location of the transaction (if a location is present) as a formatted string.
|Location of the transaction (if a location is present) as a structured object.
|string, url format
|Logo of the merchant (if a merchant is present).
|Normalized merchant name (if a merchant is present).
|Unique merchant identifier (if a merchant is present).
|Name of the person in the transaction text (if a person is present).
|Unique transaction identifier.
|Website of the merchant (if a merchant is present).
|Predicted MCC codes, usually containing a single value. Can be multiple values if the merchant can operate with multiple MCCs (if a merchant is present).
|List of objects containing the properties id, name, website and logo corresponding to all the intermediary merchants of the transaction (i.e., the payment processor)
Most of the output fields listed above can be enabled / disabled for your specific API key, and if disabled they won't be returned by the API. You can check your MSA for details. You can also reach out to Ntropy Support at firstname.lastname@example.org for more information regarding returned fields.
More details on consumer labels can be found here.
In the enriched transaction some fields may be null if it was not possible (or does not make sense in the context of the request) to determine its value. For example: merchant, merchant_id, logo, website and mcc will be set to null if a merchant is not detected in a transaction. There are also fields that must be enabled for an account per request through any support communication channel.