Identified - Treasury Prime's partner for the production and mailing of physical debit cards has notified us that they are experiencing a delay. They are pausing new shipping today to allow the completion of all existing orders of Mastercard branded cards over the weekend, then completing a migration in their production process, and then will resume standard shipping. We will work with them to identify impacted cards and update as appropriate. Current card status can be in the Fulfillment status field on the card object.
Sep 11, 2026 - 20:44 UTC
Resolved -
No additional communication issues have been observed after the change was put into place.
Sep 10, 21:23 UTC
Identified -
Our bank partner made a change to mitigate the issue and we are seeing improved communication in all channels. We continue to monitor processing.
Sep 10, 19:48 UTC
Investigating -
Treasury Prime is currently triaging an issue with our connection to the core and SFTP process for a specific bank partner, Bangor Savings Bank. The communication issue will impact our ability to return core data and complete book transfers between core accounts. It will also impact payment flows dependent on book processing such as ACH origination, incoming ACH processing, and wire processing. We are currently investigating and will work to resolve as soon as possible.
Sep 10, 19:42 UTC
Resolved -
No further incidents have been observed since the fix was deployed.
Sep 9, 19:08 UTC
Monitoring -
A fix was deployed to the production environment and we are seeing a reduction in the issue. We continue to monitor.
Sep 9, 17:12 UTC
Identified -
Treasury Prime is seeing an increase in timeouts on card authorizations; the issue is being triaged and we are working on a deployment to resolve the issue.
Sep 9, 16:01 UTC
Resolved -
Search is functioning as expected at this time
Sep 4, 15:56 UTC
Monitoring -
Data is being backfilled in search and we are monitoring behaviors.
Sep 3, 18:14 UTC
Identified -
Treasury Prime is aware that some searches in the console are not returning data as expected. The most common case is returning the associated account when searching a person. The underlying data is intact, but is not returning via search. We are working to resolve the issue.
Sep 2, 20:00 UTC
