Changelog

Added

Recipients will now return associated attachments

All /recipients response objects will return a recipient's associated attachments as an ephemeral pre-signed url as well as the corresponding taxFormType, fileName, and uploaded dateTime info if available.

Added

Internal Transfers API now available

We've added a new endpoint /transfer that allows you to programmatically move money between your accounts. This endpoint requires a SendMoney write scope. Check out the docs here:

Added

Users API now avaliable

We’ve expanded the Mercury API with two new /api/v1/users endpoints that make it easier to retrieve user information for your organization.

Added

Get Transaction by Id

Retrieve a single transaction without an accountId path parameter with our new GET endpoint /transactions/:transactionId

Added

Events API now available

The new Events API provides visibility into changes to your Mercury resources through a pull-based event log. Query and replay historical changes to your transactions for backfills, reconciliation, and audit trails. The API uses a pull-based model where you query for events on-demand. This enables reliable event replay and backfill scenarios. The API currently supports the Transaction resource type. Additional resource types (Accounts, Cards, etc.) will be added in future updates. If you're interested in events for other resource types, please reach out to [email protected].

Added

Invoicing API now available

The new Invoicing API simplifies managing invoices and customers by allowing seamless integration with Mercury invoicing into your existing systems. Note that it's only available to Mercury users on a subscription plan. Visit https://mercury.com/pricing to upgrade!

Tracking Number now available on Transaction response

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.

New details for Treasury transactions

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.