Confirm matches for multiple bank transactions.
This should be used when platforms have pre-existing knowledge of what bank transactions are associated with a financial event such as an invoice payment or a payout. This allows you to match multiple transactions in a single request. Use this endpoint when you already know whichDocumentation Index
Fetch the complete documentation index at: https://docs.layerfi.com/llms.txt
Use this file to discover all available pages before exploring further.
suggested_match_id should be confirmed for each transaction.
match_pairs array of transaction-to-suggested-match pairs. Each item in the array confirms one existing suggested match for one transaction.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Content-Type must be set to application/json.
The UUID of the business to confirm the matches for.
List of transactions with their suggested match.
Matched transactions.
Unique identifier of the bank transaction.
Unique identifier of the business the bank transaction is associated with.
Source of the transaction.
UNIT, PLAID, API, STRIPE, CUSTOM External transaction ID from the source platform (e.g, Plaid transaction ID).
"g4DlKyjXqGH3Kp5XlaWMtwLRrE4Z9AiE8B4Ko"
External account ID from the source platform (e.g, Plaid account ID).
"Aaoy8G7VXZHVeqNoL1GvcmkPdqpLRWi9NArdG"
Timestamp when the transaction was imported.
Date of the transaction.
Direction of the transaction.
CREDIT, DEBIT Transaction amount in cents.
Name of the transaction counterparty.
"WeWork"
Description of the transaction.
"WeWork monthly rent payment"
Name of the bank account.
"Plaid Checking"
The status of the transaction’s categorization in Layer’s systems.
PENDING, READY_FOR_INPUT, CATEGORIZED, SPLIT, LAYER_REVIEW, JOURNALING, MATCHED The category assigned to the transaction. Only populated for transactions that have a finalized category.
The method used to classify the transaction.
SMS, API, LAYER_AUTO, LAYER_MANUAL REVENUE, EXPENSE, EXCLUDE Memo for any text you would like to associate with the bank transaction (for example, to display to end users).
Arbitrary custom metadata in JSON format with a size limit of 1KB.
{
"custom_field": "value",
"any valid json": "below 1kb",
"nested": { "meaning of life": 42, "array": [] }
}Any (typically user-visible) identifier you would like to associate with the bank transaction. Can be used to filter when listing bank transactions.