All Transaction responses now return an optional trackingNumber: A unique identifier assigned by payment networks to trace transactions (e.g., RTP reference ID, ACH trace number, wire IMAD/OMAD). The field will be null if nonexistent.
We added a new detials object for each transaction to the response of the /treasury/:id/transactions endpoint. This new value includes the already existing security but also adds additional details like the id of the account for deposits and withdrawals, descriptions for several actions and trade and sweep directionality details.
Added a new parameter order for the /treasury/:id/transactions endpoint to control de order in which data is retrieved
The /api/v1/transactions API serves as a top level list view for all transactions within your Mercury organization. List, filter, paginate, and search transactions from all your Mercury accounts in a single endpoint. See the documentation here.
Added email and paymentMethod to details.creditCardInfo for credit card transactions on the endpoints:
GET requests to /account/:id/transactions can now be filtered by mercuryCategory and categoryId query parameters.
Retrieve information about a Send Money Request via our new GET /request-send-money/:requestId endpoint. Checkout the response schema here: https://docs.mercury.com/reference/request-send-money#/
You can now fetch Mercury Treasury transactions using the new endpoint GET /treasury/:id/transactions. Use the account ID from the UI or from the GET /accounts endpoint.
Fetch and update transaction categories.
GET requests to /account/:id/transactions can now be filtered by a requestId query parameter.
