Transforming external transactions

The best way to upload transaction data to Flinks is to include a list of ‘already transformed’ transactions within the JSON body of your request to /Attributes/Upload. Ideally, once you receive data from an external source, you will store that response/data on your servers and subsequently ensure that it is converted into an acceptable JSON format to include within the body of your request. Flinks expects your transformed ‘transactions’ object to include at least a TransactionDate, Description, Debit, and Credit fields (Balance is required, but can be included as either a running balance or by using one of the Balance options). Please see the template below for further information on what is required.

Template For Transactions

    	"Transactions": [
        {
            "TransactionDate": "2021/01/22",
                "Description": "payroll - flinks technologies",
                "Debit": "100.00",
                "Credit": null,
                "Balance": "900.00"
            },
            {
                "TransactionDate": "2021/01/21",
                "Description": "purchase newegg - rtx 3090",
                "Debit": "100.00",
                "Credit": null,
                "Balance": "1000.00"
            },
            {
                "TransactionDate": "2021/01/21",
                "Description": "nsf fee random",
                "Debit": "10.00",
                "Credit": null,
                "Balance": "1110.00"
            }
        ]
    }

Field Breakdown

NAME	FORMAT	DESCRIPTION	REQUIRED?
TransactionDate	YYYY/MM/DD	Date the transaction occurred.	Yes
Description	String	Description of the transaction.	Yes
Debit	Numeric, two decimal points maximum	If it is a purchase or outflow, the amount of the transaction. If it is not a debit, this field should be `null` or left empty.	Yes
Credit	Numeric, two decimal points maximum	If it is a deposit or inflow, the amount of the transaction. If it is not a credit, this field should be `null` or left empty.	Yes
Balance	Numeric, two decimal points maximum	The running balance after the transaction has been posted. Although this is not directly required, one of `Balance`, `MostRecentBalance`, or `OldestBalance` must be provided.	Yes (or use `MostRecentBalance` or `OldestBalance` if a running balance per transaction is not available)

Note on transaction order

Flinks will assume that the order of the transactions is either ascending or descending. Please ensure that this format is followed. If there are irregularities (transactions out of order), inconsistent results may be returned.

Optional Parameters

Fraud Verification

⌘I

API Reference

Auth

Connect

Enrich

Outbound

Pay

Upload

Utilities

Field Breakdown

​Field Breakdown

Field Breakdown