Release Notes

• April Updates to Prime Data
  • Previously, in the Prime Data, certain fields containing JSON data weren't stored in the proper JSON format, which made it difficult to access and interpret structured data. Instead, they were stored as character varying, meaning the data in the database stored strings of characters of variable lengths.

‍

• We have improved the way transaction descriptions are displayed on Plaid Exchange. Previously, end users found the transaction descriptions to be unclear. With this update, each transaction will include the beneficiary’s name, the financial institution’s name, and the last 4 digits of the counterparty’s account number.
• We have developed the capability to support interest-bearing Enhanced FDIC sweep accounts. If you would like to learn more about how to take advantage of interest-bearing sweep accounts with Treasury Prime, please contact your Account Manager.
• We have fixed a bug that was previously displaying the OMAD output date in the Bank Console with the wrong format. This issue has now been resolved, and the dates are displayed in the MM/DD format.
• The <mono>apy<mono> and <mono>footnote<mono> parameters are now required when creating a statement config object, as it is required to include in statements per Reg DD.
• We have improved the way APY is displayed on statements. It now reads “Annual Percentage Yield Earned” which aligns better with Reg DD.
• Check deposits are now searchable in the Developer Dashboard and Bank Console.

• We have made several improvements to our Statements feature for ledger customers.
• We now support the ARC SEC code for incoming ACH payments.
• We have built the ability for banks and fintechs to manage Enhanced FDIC Insurance for foreign entities without US-TINs with one of our partner sweep networks. If you are interested in learning more about this specific use case please reach out to your Treasury Prime Account Manager.

• We have made improvements to our Statements feature for ledger customers. In transaction descriptions, we have replaced "ACH Credit" with "ACH Withdrawal" and "ACH Debit" with "ACH Deposit" to clearly indicate the direction of the transaction. "ACH Withdrawal" signifies that money came out of the account, while "ACH Deposit" signifies that money was put into the account. Please note that this change is backwards-incompatible.
• We have improved our 1099-INT generation feature. Ledger customers now have the ability to create and file corrected 1099s if the initial 1099-INT filing contained incorrect information. This can be done by posting to the same endpoint. To learn more about 1099-INT generation and corrections, please visit our API Reference page.
• We have added new parameters (<mono>provider<mono>,<mono>provider_full<mono>, and <mono>provider_result<mono>) to our KYC endpoint. These parameters are used to define the name of the third-party KYC provider for person or business applications. Please note that third-party KYC evaluation submission is currently only available to certain organizations. To confirm its availability for your organization, please contact your Treasury Prime Account Manager. For more information, please visit our KYC API Reference page.

• We have implemented authentication for the Card Auth Loop endpoint in order to improve security. For more information on these new parameters, visit our API Reference page.
• We have added a dynamic <mono>originator_name<mono> field to the ACH object that enables you to customize the originator name on individual ACH payments.
• We removed all hardcoded language from statements, including the required Reg E disclosures. You will need to work with your partner bank to align on what specific language should be included on the statements.

We have made enhancements to our Cards feature. Treasury Prime customers enrolled in a Cards program can now:

• Simulate requests to credit funds for OCT transactions. Learn more about Card Simulations here.
• Retrieve the shipping service used to mail the card. To learn more about this parameter, see the fulfillment sub-object in our Cards API reference page.

‍

• The latest round of improvements to our Statements feature for ledger customers is now live. These changes will be applied to statements generated on 12/02/2023 for the November 2023 period.
• Users of the Developer Dashboard and Bank Console can now view and manage Network Transfers directly from the user interface.

• We have made several improvements to our Statements feature. These changes will take effect for statements generated on 11/02/2023 for the October 2023 period.
• We have improved our card simulations feature. Treasury Prime customers can now simulate refund authorization events. For more details on refund authorization events, please refer to our Card Simulations page.
• We have added date range filters to tables in the Developer Dashboard and Bank Console. Users of these tools can now filter payments and accounts by their created dates, in addition to the other available filter types.

‍

• We have made improvements to our Cards program endpoints. Treasury Prime's customers can now:
• ~Retrieve the tracking number for a specific card. You can utilize the <mono>tracking_number<mono> field in the Card Fulfillment object. It is important to note that this field is only accessible for shipping methods that offer tracking numbers. Please be aware that USPS Standard, which is the most frequently used shipping method, does not provide a tracking number.
• ~Utilize the <mono>reissue_pan_from_card_id<mono> field to re-issue a card with the same PAN and PIN, but with a new CVV and expiration date.
• To learn more about the latest Cards enhancements at Treasury Prime, please visit our Card API Reference and our Issuing a Card API guide.

• We have enhanced our Digital Wallet Token endpoint by providing additional parameters such as device, network, token data, and more. For more information about these improvements, please visit our Digital Wallet Token API Reference page.
• Users of the Developer Dashboard and Bank Console now have the ability to export transactions in CSV format from the transactions tab of an account page. This allows download of all transactions within the currently visible page of results.
• We have fixed a bug that was preventing Bank Console users from searching for ledger accounts using the <mono>name<mono>, <mono>account_id<mono>, or <mono>account_number<mono> fields. Bank Console users can now use the search feature to find accounts based on these fields.
• We have improved the Source filter in the Bank Console to also display organizations that are no longer active at the bank. This enhancement aims to facilitate the filtering of historical account applications.
• We have made improvements to the Wire pages in the Developer Dashboard and Bank Console to display IMAD and/or OMAD data when they are available on the relevant payment.

• We have created an API reference page for Digital Wallet Token (DWT) simulations. These simulations are designed to replicate the process of provisioning a card to a digital wallet. To learn more about DWT simulations, visit this page.
• If you're a customer of the Treasury Prime ledger, you may currently receive two webhook events - <mono>transaction.create<mono> and <mono>account.update<mono> - for every new transaction on your account. However, during times of peak activity involving a single account, we’ve found that the resulting flood of <mono>account.update<mono> events is counterproductive to our customers, and negatively impacts our system’s performance and stability. Moving forward, we will now coalesce multiple <mono>account.update<mono> events into a single event, at regular intervals (on the order of one minute). The coalesced events will be identical to the <mono>account.update<mono> events you’re already receiving; you will simply see fewer of them. This will greatly improve our ability to handle peak traffic, resulting in a more stable and reliable system.

• We are introducing a new read-only endpoint called <mono>incoming_ach<mono>. This endpoint provides descriptive details about incoming ACH transfers for customers who use the Treasury Prime ledger. For more information on this endpoint, please refer to our Incoming ACH API reference page.
• Users of the Developer Dashboard can now create, manage, and manually trigger webhooks directly from the dashboard. Please note, however, that this does not include logging of sent webhooks. For more information about webhooks, please visit our Webhooks API Reference page.

• We have added a new <mono>extended_timestamp_precise<mono> field to the Transaction Object. This field represents the timestamp of the transaction in ISO 8601 format with subsecond precision ("YYYY-MM-DDThh:mm:ss.SSS[SSS]Z"). The precision could be millisecond or microsecond, depending on the source data. This field has limited availability and is always in UTC. To learn more about transactions, please visit our Transaction API reference page.

• We have enhanced our Digital Wallet Token suite by adding new endpoints that allow for easier management of digital wallets. For more information on digital wallets, visit our improved Digital Wallet Tokens page.
• Our Card page in the API Reference has been updated to include information about the <mono>creation_options<mono> parameter. This parameter is an object that defines additional fields for card customization during creation, such as personalized text in cards.
• We have updated our Cards Simulations page in the API Reference to include our new force capture simulation.
• We have made improvements to the check issuing testing feature in our sandbox environment. Additionally, we have added a page to the API Reference section to reflect these changes. To learn more about check issuing testing, please visit our Check Issuing Testing page.
• We have improved our wire and ACH velocity limit calculations to provide organizations with precise visibility into their threshold velocity limits.
• Our new Enhanced FDIC Insurance endpoint is now live. To learn more about enabling this feature for your organization, visit our Enhanced FDIC Insurance page.
• We have made usability improvements to payment tables in the Developer Dashboard and Bank Console for ACH, Wire, and Book Transfers. Now, you can more clearly see the originator and counterparty details for each payment without the need to click into the payment detail page.
• The Source filter in the Bank Console has been updated to support filtering the list of developer orgs by typing. This allows for quicker filtering for banks with many live fintech programs.
• Our Fintech Fraud Best Practices guide is now public and available for everyone. To access the guide, along with other resources from our Compliance Toolkit, please visit this link.
• We have made improvements to the Webhooks page in our API Reference. The page now provides a complete list of available webhooks, along with descriptions and helpful resources. For additional information about webhooks, please visit this page.

• We have improved our API Reference documentation to show that the <mono>person_id<mono> and <mono>last_4<mono> parameters on the Card Object are <mono>filterable<mono>. To learn more about the Card Object, click here.

• We have made several improvements to our API documentation:
• ~An effective way to reduce the risk of fraud is to inform cardholders when someone attempts to add their card to a digital wallet. For further information, please refer to our newly published Digital Wallet Notifications guide.
• ~We have improved the Statements page in our API Reference by providing instructions on how to retrieve statements in PDF format.

• We have updated our documentation to include card authorization and capture events, which were previously not documented. To view all available card events on Treasury Prime, click here.
• We have added the ability to filter search results by data type in both the Developer Dashboard and Bank Console.
• We have made improvements to the user experience of the Developer Dashboard and Bank Console:
• ~Table rows can now be opened in new browser tabs easily by using command+click for Mac users, and control+click for Windows users. This applies to all list views of applications, accounts, and payments.
• ~We have fixed a bug that prevented viewing the full transaction description on account pages when the value was too long. Now, transaction summaries will display in full, regardless of the string length.
• ~Users of the Developer Dashboard can now view and copy the <mono>userdata<mono> field on account, application, and payment pages.
• ~Users of the Developer Dashboard and Bank Console can now hover over the routing numbers of external financial institutions to see more details about the bank in a popover.

• We have fixed a bug that previously resulted in a vague error message when a required field was missing from account applications. With this fix, the error message now specifies which required field is missing. For more information on Person and Business Applications, please click here.
• Starting in June, monthly statements will be generated for all open accounts, regardless of recent activity. Previously, statements were only produced for accounts with activity, such as transactions, during the given month. This change was made to comply with Reg E 1005.9b, and may have billing and technical implications for fintech customers. Billing implications will be reflected in invoices starting with the June 2023 invoice. To learn more, please contact your CSM or reach out to us.
• The Bank Console and Developer Dashboard now display full timestamps for all activity. Relative datetime values have been replaced with the full <mono>MM/DD/YYYY, HH:MM XM<mono> format. This update aims to provide more clarity to workflows that require a clear understanding of event timing.

‍

• Treasury Prime now offers daily and monthly intervals for card control limits. Previously, customers with Marqeta card programs could only set hourly rolling intervals for spend and withdrawal limits on card controls. With this new feature, Treasury Prime customers can now set limits based on daily and monthly intervals.
• We have made several improvements to the Developer Dashboard and Bank Console:
• ~Issued checks are now searchable.
• ~Account detail pages now prominently display the name of the business or primary account holder on the account. This title space previously displayed the type of account and the last four digits of the account number.
• ~We’ve fixed a bug that displayed an empty Account Products table to some bank partners. Account Products should now be visible to all users of the Developer Dashboard, and many bank partners, with the remaining access to be rolled out the coming weeks.

• We have fixed a bug that previously prevented customers from filtering transactions by Incoming Wire ID. This issue is now resolved, and customers can filter transactions using the <mono>incoming_wire_id<mono> parameter. For more information on filtering, please refer to this link.
• Tags are now visible on the Overview tab of the Accounts page on the Developer Dashboard and Bank Console. Account tags are also search-indexed and can be used to find accounts through the search interface, though the individual tags do not yet appear in the inline search result UI.
• Account applicants are now searchable in the Developer Dashboard. Indexed fields include business and personal applicants’ names, IDs, TINs, and other identifying details.
• We fixed a bug in the Developer Dashboard and Bank Console that prevented users from filtering ACH transactions in a <mono>canceled<mono> status. This issue has been resolved, and filtering should function as expected.
• We have fixed a bug in the Bank Console that prevented full use of nav bar on mobile devices.

• Enhanced card controls for Marqeta card programs. These controls allow you to configure the restrictions and capabilities of associated card and card product objects. For example, you can now restrict the use of a debit card for a specific merchant.

• Originating international USD wires from a domestic US account to an overseas beneficiary using is now available via the Treasury Prime API.

• Output Messaging Accountability Data (OMAD) is now exposed on outgoing wire confirmations originated at Third Coast Bank and FirstBank. Customers will now see the <mono>omad<mono> field in the Wire Transfer Object, which includes the date, sender, sequence number, date and time, and the processing Fed location ID.
• ~OMAD is only exposed at these two banks (Third Coast Bank and FirstBank) because they include OMAD in the outgoing wire confirmation file. If other banks start to include OMAD in the outgoing wire confirmation file, it can be exposed as well.

• Outgoing wire confirmation files for wires originated at BankProv are now being processed. As a result, Input Messaging Accountability Data (IMAD) will be available to these users. Previously, we did not parse these wire confirmations at BankProv, but this has since been corrected. Customers will now see the <mono>imad<mono> field on the Wire Transfer Object, which includes the date, sender, and sequence number.

• ACH pages in the Developer Dashboard and Bank Console now include the <mono>scheduled_settlement<mono> field. This field is a timestamp that indicates the approximate time a debit ACH hold will be released, and the debit ACH will be considered settled. This feature is only available on ACH originated from Treasury Prime ledger accounts.
• We’ve made several minor improvements to search in the Developer Dashboard & Bank Console:
• ~Search results can now be opened in a new tab. Mac users can use ⌘+click, and Windows users can use Ctrl+click to open one or multiple results in new browser tabs without navigating away from your current page.
• A Developer Dashboard bug has been fixed that prevented users from navigating to Dashboard pages from links in other applications. This should now allow linking to any dashboard page from internal tooling or other resources for users who are signed in and have the necessary permissions to view the destination.
• A Bank Console bug has been fixed that prevented Admin users from updating Developer Org API permissions. This should now be working as expected.