Transactions represent asset movements, such as ACH payments, wire transfers, or card purchases. Track transaction statuses and events through these endpoints.
Endpoints:
- GET List Transactions: GET /transactions
- GET Get a single Transaction: GET /transactions/{uid}
- PUT Approve or deny a Transaction: PUT /transactions/{uid}/authorize
- GET List Transaction Events: GET /transaction_events
- GET Get a single Transaction Event: GET /transaction_events/{uid}
- GET List Synthetic Line Items: GET /synthetic_line_items
- GET Get a single Synthetic Line Item: GET /synthetic_line_items/{uid}
- GET List Custodial Line Items: GET /custodial_line_items
- GET Get a single Custodial Line Item: GET /custodial_line_items/{uid}
Transactions are created based on how you instruct Newline to move assets (a Transfer) or how assets are moved or spent outside your application (ATM withdrawals, debit card purchases, wire transfers, etc…). The Transaction contains the amount, origin, and destination of assets. Newline categorizes Transactions into types to assist in their classification and representation.
Transactions fall into many categories, including debit card purchases, direct deposits, interest, and fees. This endpoint can retrieve a list of Transactions or track the status of an ongoing Transaction.
Transaction Events are created as a result of a Transaction. They capture the steps required to complete the Transaction. These can be used to view the progress of an in-flight Transaction or see the history of a completed Transaction.
Line Items are created for each Transaction Event. They catalog the individual credits and debits associated with the accounts involved in the Transaction.