Legacy docs ↗App sign in ↗
improved

June 21st, 2024

15 days ago by Shayla Gibson
  • Introducing our New Documentation Page!! Designed to enhance your experience and provide easier access to comprehensive resources. Here’s what you can expect:
    • Streamlined Navigation: Find information quickly with improved organization and search functionality.
    • Enhanced Content: Updated guides, API references, and tutorials to help you integrate seamlessly.
    • Interactive Examples: Explore code snippets and practical use cases directly within the documentation.
    • Feedback Integration: Share your thoughts and suggestions to help us improve further.
added

June 7th, 2024

29 days ago by Shayla Gibson
  • Returning Incoming ACH
    • Treasury Prime created a way for banks and fintech customers to return an incoming ACH. We have built a new PATCH endpoint that would require a status of returned to be specified as well as a return_code. The rollout of this feature will be applied to both business and consumer accounts in an open status. Returns will be restricted to incoming ACHs with an effective date within the last 1 business day. Any incoming ACH sent outside of that window will not be returned. Both fintech and bank users will have the option to provide a description though if one is not, Treasury Prime will use the default. For fintech users, this will effectively indicate the incoming ACH was not authorized or recognized by the customer.
      • For this to be enabled at a Bank, reach out to your Relationship Manager
      • For this to be enabled at a Fintech, your corresponding Bank will need to provide approval. Please reach out to your Relationship Manager
    • Check out our Documentation
  • Invoice Account Numbers
    • Treasury Prime can now allow customers to allocate an account number and assign it to an existing ledger account via our /invoice_account_number endpoint. Treasury Prime will generate an account number using the prefix of the FBO connected to the provided ledger account ID.
    • Incoming ACHs and wires received for the invoice account number will be posted to the associated ledger account. These payments will be posted to the ledger account just as if they were a payment to the account number on the ledger account.
    • The account number for the ACH/wire will continue to be surfaced on the /incoming_ach and /incoming_wire endpoints which will allow customers to make the connection to the invoice account number.
    • How to enable this
      • For this to be enabled at a Bank, reach out to your Relationship Manager
      • For this to be enabled at a Fintech, your corresponding Bank will need to provide approval. Please reach out to your Relationship Manager
    • Check out our Documentation
improved

June 7th, 2024

29 days ago by Shayla Gibson
  • Updates to RDC API responses
    • We have implemented a change in the API response to include the parsed-out RDC (Remote Deposit Capture) fields on the checks table. This means that when you make a request to the API, you will receive additional information related to RDC fields directly in the response.
  • Updates to Account Closure Checks funds flow
    • Previously, when a stop payment was placed on an account closure check, the funds were transferred from the settlement account to the FBO account, and subsequently, the funds were reinstated in the customer's ledger account. However, under the new process, account closure check funds will no longer be reallocated to the customer's ledger account. Instead, these funds will remain in the settlement account.
    • Additionally, any checks in the status of pending or sent and were issued from the customer's ledger account before it was closed will have a stop payment placed on them
  • Updates to Prime Data
    • The amount of data type was previously stored as numeric(38,9), indicating a precision of 38 digits with 9 decimal places. We've adjusted the amount of data type to numeric(38,2), providing a precision of 38 digits with 2 decimal places, which is more suitable for our requirements and helps optimize storage space.
improved

April 17th 2024

2 months ago by Shayla Gibson
  • April Updates to Prime Data
    • Previously, in 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.
improved

February 21, 2024

5 months ago by Shayla Gibson
  • 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 APY and footnote parameters are now required when creating a statement config object, as it is required to be included in statements per Reg DD.
    • Note: even if the APY is 0.0%, customers still need to input it in the config field for it to appear on the statement. To learn more about our virtual ledger statements feature, visit our API Reference page.
  • 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.