Product Updates

​

Console Enhancements

• Banker Viewer Role: Read-Only Access to Program Details
  • The Banker Viewer role now has read-only access to view Program keys, limits, and features in the Console. This allows compliance team members and other users who need visibility into program controls without requiring full Banker Admin privileges.
• Updated Disabled Feature Messaging
  • When a feature is not enabled for a bank program, the Console now directs users to contact their Relationship Manager.
• SSN Search
  • Bank users can now search for accounts by Social Security Number in the Console. This feature allows searching by the last 4 digits combined with a name.
• Bug Fix: Banker Viewer Settings Page
  • Fixed an issue where the settings/features page was showing a “Server error occurred” screen for Banker Viewer users. The page now loads correctly.

​

Green Dot Cash Deposits

• Green Dot Locations API: Read-Only Key Support
  • The Green Dot locations endpoint now supports read-only API keys, allowing fintechs to retrieve cash deposit location information without requiring write permissions. This is useful for displaying deposit locations to end users in mobile apps and web interfaces.

​

Documentation

• Updated BYO KYC Documentation
  • Improved the Bring Your Own KYC documentation to be more provider-agnostic. The /apply/kyc endpoint documentation now uses generic field names instead of specific provider references, reducing confusion for fintechs using non-Alloy KYC providers.

​

Data & Reporting

• FedNow ID Now Populated in Ledger Transactions
  • The fednow_id field in ledger transaction data is now populated for FedNow-related transactions. Previously, this field existed but was not consistently populated. With this update, 304 historical records (dating back to April 2025) will have the fednow_id value populated, and all new FedNow transactions will include this identifier going forward.
  • For customers using the RDS Prime data instance (Prime Data v1), the fednow_id attribute will be populated in new data going forward. Historical records in RDS will not be backfilled.
  • This enhancement improves transaction traceability by allowing customers to link ledger transactions directly to their corresponding FedNow payment objects.

​

Prime Data: Migration to Snowflake (V1 Deprecation)

• Prime Data V1 (the legacy RDS-based data feed) will no longer be updated after February 28, 2026, and will be fully discontinued on April 7, 2026.

• If you’re already accessing data via Snowflake—either through a Reader Account or Data Share—no action is needed. If you’re still using the legacy V1 feed, please transition to Snowflake before February 28.

• Snowflake provides more frequent data refreshes (up to 10x daily vs. 6x for V1), eliminates the data synchronization delays inherent in the legacy pipeline, and ensures you’re always working from the single source of truth.

​

Console Enhancements

• Card Status Banners
  • The Console now displays visual status banners on card detail pages for cards that are Terminated or Suspended. This follows the same pattern as account lock banners, providing immediate visibility into card status when reviewing card details.
• Persistent Page Size Preferences
  • Users can now set their preferred rows-per-page in Console tables, and this preference will persist across sessions. Each user’s selection is saved individually, so team members can customize their own viewing experience without affecting others.
• Bug Fix: Account Details Page
  • Fixed an issue where the account details pages were returning 404 errors in certain scenarios. The Console now properly loads these detail views.

​

FedNow Improvements

• FedNow Search Support
  • FedNow transactions are now included in Console search results. When searching for a FedNow ID, the Console will return the FedNow object as well as any related book transfers, consistent with how other payment types behave in search.
• Enhanced FedNow Details Display
  • The FedNow object detail page in Console now displays additional fields, including Error information and Related FedNow IDs, even when the data is null

​

Wire Transfers

• Financial Institution Transfer Wire Support
  • Added support for parsing incoming ISO 20022 financial institution transfer wires (PACS.009 message type). This extends the existing customer credit transfer (PACS.008) support to handle bank-to-bank transfer messages.

​

Console Enhancements

• Cards Now Visible on Account Detail Page
  • Bankers can now see all associated cards directly from an account’s detail page, including card status (active, terminated) and type (physical/virtual). This eliminates the need to navigate to the Cards section separately when handling account closures or disputes.
• Source/Program Column Added to Accounts Table
  • The Accounts table now displays a Source (Program) column, allowing bankers to quickly identify which fintech opened each account. This supports fraud detection and daily account oversight without needing to filter accounts one-by-one.
• Account Information Now Visible on Cards Table
  • The Cards table now displays linked account information in a dedicated column, matching the format used in the Accounts table. This makes it easier to identify which account a card is associated with without navigating away from the Cards view.
• FedNow Enhancements in Console
  • FedNow transactions are now searchable via the Console’s global search, and the FedNow detail page now displays the error and related_fednow_ids fields for improved transaction tracking and troubleshooting.
• Card Events Search & Transaction Linking Improvements
  • Card Network Messages are now searchable in the Console with dedicated icons and filters. Additionally, card events are now properly linked to their associated transactions, making it easier to trace card activity to account movements.
• Team Management: Delete User Functionality
  • Administrators can now delete users directly from the Console’s Team Management section, with a confirmation modal to prevent accidental deletions.

​

Prime Banking

• Counterparty Account Type Corrections Now Supported
  • Counterparty records can now be corrected when account types (checking vs. savings) are misconfigured, reducing repeated NOC (Notification of Change) triggers for ACH transactions.

​

Data & Reporting

• Prime Data: Pulse Settlement Book ID Now Available
  • The pulse_settlement_book_id field is now available in Prime Data card transaction tables for bank users. This creates parity in direct querying and reporting on card settlement activity through Sigma between Pulse and Mastercard network transactions.
    • Available for banks with Prime Data and Pulse card processing enabled.

​

Console Enhancements

• Card Transaction ID Now Copyable for Dispute Processing
  • The card transaction identifier (ttx_id) and merchant name are now easily copyable from the Console, improving the workflow for submitting card disputes. Previously, these values could not be copied from the transaction details view.
• Prime Analytics Reports Directory Restored
  • Fixed an issue where the menu bar for accessing the reports directory in Prime Analytics was not displaying. Users can now access their custom reports and templates as expected.
• Account Product Creation Access Fixed
  • Resolved a permissions issue that was preventing users from creating account products in certain bank environments.

​

API Updates

• Check Deposit Return Reason Now Documented
  • The return_reason field is now documented in the Check Deposit API reference. When a check deposit is marked as returned, this field provides visibility into the reason for the return.
• Business Name Now Editable via API
  The business name field on ledger business accounts can now be updated via the API. Previously, only the address field was editable after account creation.

​

Console Enhancements

​

FedNow

​

Prime Cash (powered by Green Dot Network)

​

Tax Document Filing (1099-INT)

• Legal name of your organization
• Address of your organization in the US
• Phone number of your organization
• TIN (Taxpayer Identification Number) of your organization

• 1099 filing: $2 per filing (includes state and Federal)
• Corrected 1099 filings (if needed): $2 per filing. (A corrected filing is one which needs to be amended subsequent to filing through the API)
• $250 platform fee (charged once yearly in February)

• Ensure you’ve provided the information under the ‘Action Required’ heading above to your account manager prior to using our API to create 1099-INTs.
• Make sure all relevant transactions for 2025 are correctly categorized as “interest”. You can do this by setting the “category” field on the transaction object to “interest”. See our documentation here.
• You will be able to reference our updated 1099-INT documentation to understand how to generate, verify, and file 1099-INT forms.
• Disburse the forms to your end users by February 2, 2026.
• Note: Treasury Prime cannot provide advice on a customer’s tax liability. If you have any questions, it is recommended that you consult a tax professional.

• Bug fixes allowed, but no new feature deployment.

• No code deployments, exceptions for critical issues.

• There will be limited support available to customers through 12/25 - 1/2.
• 12/26 - 12/31 Support will be available between 9 AM EST - 6 PM EST (closed Saturday/Sunday).
• Any emails/cases/requests sent after 6 PM will be addressed the following working day.
  • E.g. - If you send an email/case/ticket/request at 6:30 PM EST on 12/26, it will be addressed/acknowledged on 12/29.
  • E.g. - If you send an email/case/ticket/request at 6:30 PM EST on 12/31, it will be addressed/acknowledged on 1/2.
  • Email/case/ticket/request sent after 5:00 PM EST are not guaranteed to be answered before 6 PM and may be addressed/acknowledged the following working day.

​

Console Enhancements

• FedNow Payments Tab Now Available
  • A new FedNow payments tab is now accessible in the Console, providing visibility into both incoming and outgoing FedNow instant payments. Users can view payment details, status, and related transaction information directly from the Console interface.
• FedNow Transaction Details Enhanced
  • The FedNow details page now displays additional data fields, including Payment ID, Error information, and Related FedNow IDs—making it easier to track and troubleshoot instant payment transactions.
• Card Events Details Page
  • A new details page for card events is now available, allowing users to click through from the card events list to view comprehensive information about each card event.
• Card Product Column and Filter Added to Cards List
  • The Cards list view now includes a Card Product Name column and filter, making it easier to identify which card products your cards are associated with and filter your card inventory accordingly.
• FBO Page Shows Settlement Account Balances and Account Numbers
  • The FBO management page now displays cached settlement account balances and uses account numbers instead of account IDs for improved readability.
• Read-Only Entitlements View for Fintechs
  • Fintech users can now access a read-only view of their entitlements in the Console settings menu, providing transparency into enabled features without requiring bank-level access.
• Business Name Editing Now Available in Console
  • Users can now edit ledger business names directly from the Console, in addition to the existing address editing capability—reducing the need to contact support for routine updates.

​

Search Improvements

• FedNow Transactions Now Searchable
  • FedNow transactions are now indexed and searchable in the Console. Users can search by FedNow ID and filter search results by the FedNow object type.
• Card Network Messages Added to Search
  • Card network messages are now included in search results, enabling users to quickly locate card transaction details across their programs.
• Incoming ACH Filter Added to Search
  • You can now filter search results specifically for incoming ACH transactions, making it easier to locate inbound ACH items.
• Search Experience Fixes
  • Several search improvements have been deployed: partial ID searches now work correctly, object-type filters properly limit results to the selected type, and search result linking now navigates to the correct detail pages for cards and FedNow transactions.

​

API Updates

• Ledger Business Name Editable via API
  • The API now supports editing the business name on ledger records, in addition to the existing address editing capability.
• Filter Cards by Card Product
  • A new backend filter allows retrieving cards by card product ID, enabling more efficient card inventory management through the API.
• IntraFi Customer ID Now Exposed in Deposit Sweep Response
  • The Fetch Deposit Sweep API response now includes customer ID and associated email address information for IntraFi enrollments, allowing programs to provide their customers with the credentials needed for IntraFi portal access without contacting support.

​

Bug Fixes

• Reporting Tab Loading Issue Resolved
  • Fixed an issue where the Reporting Overview page failed to load with an “Embed URL is missing ‘:nonce’” error for some users. The embedded reporting interface now loads correctly.
• Program Accounts Tab Navigation Fixed
  • Resolved an issue where clicking on accounts in the Program page’s Accounts tab resulted in a 404 error. Account detail links now navigate correctly.

• Fixed an issue where failed check deposits were incorrectly tagged as “Endorsement Missing” even when the failure was due to unrelated causes (such as image quality or MICR readability issues). Error messages now more accurately reflect the actual issue.

​

Prime Data

• Outgoing Bank File Data Now Available in PrimeData
  • The outgoing_bank_file table is now included in PrimeData, giving banks direct access to outgoing file transmission records through their Snowflake data shares. This data can be used for reconciliation, audit trails, and operational reporting on files sent to payment networks and processors.

​

Payments & Transfers

• FedNow transactions are now indexed in the Console search, allowing you to find FedNow payments alongside ACH, wires, and other payment types.

• Optimized the creation of book transfers by reducing database operations, resulting in faster processing times and improved reliability during high-volume periods.

​

Console & Search

• Fixed an issue where Console search was returning overly broad results. Searches now require exact string matches for more precise results.
• Partial ID searches now work correctly when searching for transactions and other objects.

• Transaction lists for core accounts now display in reverse chronological order (newest first), matching the standard behavior across other payment rails and account views.

• Resolved an issue preventing bank users from accessing the Prime Analytics copilot feature through the Console.

​

Cards

• Verified compatibility with Mastercard’s new “Tap to Add Card” feature, which allows cardholders to add physical cards to Apple and Google wallets by tapping them against their device. No action is required from banks or fintechs to enable this feature.

• Fixed an issue where Digital Wallet Tokens were not properly updating when cards were removed from mobile wallets.

• Improved handling of Original Credit Transfer (OCT) webhooks to correctly process declined transactions, preventing erroneous credits from being posted.

​

Documentation

• Updated API documentation to clarify that only ledger accounts can be linked as reserve accounts.

​

Improvements & Bug Fixes

• Fixed: Account number search in Console
  • Resolved an issue where searching by customer-facing account numbers was not returning results in the new OpenSearch implementation. The search now properly locates accounts by account number, person ID, and EIN.

• Fixed: Account link permissions for non-admin bankers
  • Non-admin banker users can now properly access account details from the programs page without encountering permission errors.
• Improved: Contact details display
  • Added date of birth display to the customer contact details section in the Console, providing bankers with easier access to customer information without needing to run API reports.
• Improved: Check status actions
  • Removed the stop payment option for pending checks in the Console, as pending checks can only be cancelled. This prevents confusion and ensures users take the correct action.
• Improved: Wire transfer details access
  • Restored the ability to view network transfer wire details in the Console, fixing a 404 error that was preventing bankers from accessing detailed information about balancing wires.
• Improved: Incoming ACH visibility
  • Added the exception_typefield to the incoming ACH table display in the Console, providing better visibility into ACH transaction processing details.

​

✨ New Feature Alert

​

Improvements & Bug Fixes

• Fixed: Google Wallet device ID mismatch
  • Resolved an issue where Google Wallet device IDs were not matching between requests and responses, and improved digital wallet token update handling when cards are removed from wallets.

• Fixed: Check deposit testing documentation link
  • Restored navigation access to the Check Deposit Testing documentation page that was not accessible from the main documentation menu.

​

Prime Data

• We’ve added enhanced error reporting for incoming wire transfers to provide better visibility into transaction issues.
• What’s new:
  • Added an error attribute to incoming wire transaction records that captures detailed error information when wires fail to process or encounter issues
  • This field is now available in analytics and reporting tables, making it easier to diagnose and resolve wire processing problems
• Where to find it: The error field is available in the incoming_wire data tables in Prime Data and analytics reporting systems.

​

Improvements & Bug Fixes

• Fixed: Digital wallet tokens staying active after card reactivation
• We resolved an issue where digital wallet tokens (Apple Pay, Google Pay, etc.) were being automatically suspended when cards were reactivated. The system now correctly maintains the token state during card lifecycle changes.

• Fixed: Serialization errors when creating manual holds
• We resolved 409 errors that were occurring during manual hold creation. The system now handles concurrent hold requests more reliably, preventing transaction conflicts.

• Fixed: Reduced 502 errors in sandbox environment
• We addressed a performance issue that was causing intermittent 502 errors in our sandbox environment, improving reliability for development and testing.

• Improved: Faster bank card data retrieval
• We optimized database queries for card operations, resulting in faster response times when retrieving card information.

• Improved: Better NSF (insufficient funds) detection
• Added support for an additional NSF error code (8115) from our banking partners improving transaction failure detection and reporting.

​

Bank & Payment Processing

• Fixed: Processing of non-standard ISO20022 wire formats
• We improved our wire processing system to handle improperly formatted ISO20022 files from certain bank vendors, ensuring wire transfers continue to process correctly even when files don’t fully conform to standard formatting.

• Fixed: IAT (International ACH Transaction) return processing
• We corrected an issue in our ACH processing library that prevented proper formatting of IAT return files. The system now correctly handles international ACH return transactions.

• Fixed: Error handling for specific payment scenarios
• We improved error handling for FedNow payments to prevent incorrect error states when payments are successfully processed by the bank but experience webhook communication issues.

​

Check Deposits & RDC

• Improved handling of ISO 20022 wire files that lack proper XML root nodes, ensuring more reliable processing of incoming wire data
• Added missing check serial numbers to X9 files for better check tracking and reconciliation

​

ACH Processing

• Fixed processing of International ACH Transaction (IAT) returns to ensure proper formatting and handling

​

FedNow

• Improved handling of FedNow payment errors to prevent duplicate transactions and ensure accurate payment status tracking
• Enhanced reliability for FedNow payment processing with better error state management

​

Console Improvements

• Added missing contact details in marketplace applications
• Improved navigation and display of network transfer details
• Enhanced user authentication and login experience

​

API & Documentation

• Updated OpenAPI specifications with latest endpoint documentation
• Improved error responses and validation messages across various endpoints
• Implemented automation to keep API documentation up-to-date with recent changes

​

Console Self-Service Enhancements

• Check Deposit Return with Reason Tracking
  • This feature enables bank operations teams to return check deposits directly through the Console with documented return reasons.

​

API & Developer Experience

• FedNow API Key Permission Fix
  • Resolved an issue where newly generated API keys for organizations with FedNow enabled were not automatically inheriting the FedNow permission. API keys now correctly include FedNow permissions when generated for FedNow-enabled organizations, ensuring developers have immediate access to FedNow functionality without manual permission adjustments.

​

Infrastructure Improvements

• Improved Statement Accuracy - Corrected statement descriptions for incoming ACH transactions to provide clearer, more accurate transaction descriptions for end customers.

​

Bug Fixes & Performance

• Card Listing Pagination Fix
  • Corrected a pagination bug in the Console’s card management view where navigation controls were incorrectly disabled even when additional cards existed beyond the initial page. Users can now properly navigate through all cards using pagination buttons.

​

Documentation

• Unified Documentation Navigation
  • We’ve improved the documentation experience by consolidating navigation between our Virtual Ledger and Core Direct documentation. While the two product lines maintain separate documentation content, they now share a unified navigation structure, making it easier to discover and switch between Virtual Ledger (docs.treasuryprime.com) and Core Direct (direct.treasuryprime.com) resources.
    • What Changed:
      • The combined navigation menu allows seamless switching between Virtual Ledger and Core Direct docs
      • Improved discoverability of product-specific guides, API references, and resources
      • Maintained separate, dedicated documentation for each product line while reducing navigation complexity

​

API Enhancements

• Added return reason field to the check deposit return API, providing more detailed information when check deposits are returned.

​

Console Improvements

• Fixed an issue where the history view in the Features area displayed “Unknown User” for certain actions. The Console now shows the user’s email address when the name is unavailable.

• Enhanced Console to display new status types for international wire transfers, improving visibility into the wire lifecycle.

• Fixed an issue where banker administrators were unable to invite users with the “Banker Account Reviewer” role.

• Resolved a bug where attempting to view a non-existent check ID would cause the page to fail. The Console now properly displays an error message.

• Book Transfer Duplicate Prevention Implemented idempotent operations across all on-core book transfer methods to prevent duplicate transactions during retry scenarios. This enhancement improves reliability and reduces the risk of duplicate funds movements, particularly during network interruptions or timeout scenarios.
• ACH Signature Enhancement Introduced an improved signature mechanism (signature_v3) for incoming ACH transactions. This new signature incorporates additional fields, including company description, file ID, and batch number, to provide better deduplication and transaction matching capabilities.
• Incoming Wire Error Tracking Added an error description field to incoming wire records, providing long-term storage of failure reasons directly in the database. This enhancement improves troubleshooting capabilities and provides better audit trails for failed incoming wire transactions.
• Bill Pay Processing Resolved a response parsing issue with FIS Bill Pay transactions that was preventing proper decoding of gzip and zlib compressed responses. This fix ensures reliable bill payment processing.

​

Documentation

• Updated simulation endpoint documentation to include guidance on firewall configuration requirements for receiving webhook callbacks.
• Revised FedNow guide to reflect current compliance and operational requirements.
• Updated KYC guide with improved guidance on compliance procedures.

​

New Features & Enhancements

• Search functionality improvements: Completed comprehensive testing of OpenSearch implementation, preparing for production rollout

• Card transaction visibility: Added card event display in the payments section, enabling bankers to view transaction history
• Check deposit permissions: Fixed read-only access for banker viewer roles to view check deposit information

• Code cleanup: Resolved database schema issues including default values and constraint validations

​

New Features & Enhancements

• Card Management Performance - Significantly improved cards page loading speed by optimizing data loading patterns and reducing initial page load times
  • What Changed: Deferred person data loading to per-row instead of loading all data upfront
  • Benefits: Faster initial page load, especially for organizations with many cards
• Digital Wallet Token Management - Resolved issues with digital wallet tokens becoming suspended after card reactivation, improving user experience for mobile payments
• Google Wallet Integration - Fixed device ID mismatch and digital wallet token update issues for improved Google Wallet functionality

• Internal Account Transfers - Added book transfer capability for end users with multiple accounts, enabling self-service transfers between their own accounts.
  • Use Case: 401(k) clients can now move funds between pre-tax, after-tax, and Roth accounts
  • Benefits: Automated internal transfers without manual intervention

• Plaid Integration Fix - Resolved 500 errors when creating counterparties with Plaid processor tokens in sandbox environment.
  • What Was Fixed: Improved error handling and logging for bad Plaid tokens
  • Impact: Users can now receive proper error messages instead of internal server errors
• FedNow Error Handling - Enhanced FedNow transaction processing with proper NSF (insufficient funds) error messaging for better customer experience
  • What Changed: FedNow NSF failures now display “Insufficient funds” or “Not enough funds: balance < amount”
• Zero-Dollar ACH Optimization - Eliminated unnecessary book transfer creation for $0 incoming ACH transactions (typically pre-notifications)

• Authorized Representative Support on Account Statements - Enhanced statement capabilities to display authorized users (such as representative payees) on customer account statements, supporting ABLE accounts and government benefit requirements.
  • What’s New: Statements can now show both the primary account owner and an authorized representative with proper designations
  • Format: {authorized_user}, Representative Payee for {owner}
  • Benefits: Meets compliance requirements for government deposits (SSI/SSA) and ABLE account programs
  • Configuration: New display_authorized_user statement configuration option available

• Response Header Logging - Added external response header storage for better tracking and debugging of core banking system interactions
• Horizon CC Book Transfer Tracking - Improved book transfer UUID storage for Horizon CC core to enhance troubleshooting capabilities

• FedNow API Documentation Update - Added missing “blocked” status to FedNow payment API documentation.
• Idempotency Key Documentation - Clarified idempotency key retention policy in API documentation.
  • What’s Documented: Idempotency keys are retained for 7 days

​

New Features & Enhancements

• Missing OpenAPI Status Added: Added missing ‘blocked’ status to FedNow OpenAPI specifications to ensure complete API documentation coverage.
• Improved NSF Error Handling for FedNow: Added proper insufficient funds error messaging to FedNow transactions, providing clearer feedback when transactions fail due to insufficient account balance.

• Digital Wallet Token Reactivation Fix: Resolved issue where digital wallet tokens were incorrectly suspended after card reactivation, improving the card management experience.
• Card Product Validation Enhancement: Added validation to prevent entering invalid HH:MM as a rollover time in card product configurations, preventing downstream authorization simulation errors.

​

Fixes & Improvements

• Idempotency Documentation Update: Clarified 7-day retention period for idempotency keys in API documentation.

• Check Processing Fixes: Resolved various check deposit processing edge cases and improved error handling.

​

Documentation Updates

• FedNow Guide Overhaul: Comprehensive update to FedNow documentation with enhanced send transaction details and status flow explanations.

​

Platform Improvements

• Enhanced Webhook support
  • Fixed an issue preventing the creation of invoice account number webhooks in sandbox environments. Developers can now successfully create invoice_account_number.create and invoice_account_number.update webhooks without encountering validation errors.
• Console Display Accuracy
  • Corrected timestamp display issues in the console where incoming wires were showing incorrect “received at” and “updated at” times, ensuring accurate transaction timing information for banking operations.
• Enhanced Card Management
  • Improved card search functionality in the console, allowing banking staff to efficiently locate and manage card records through the administrative interface.

​

Operations

• ACH Processing Enhancement
  • Added support for the DNE (Death Notification Entry) SEC code in NACHA processing, ensuring comprehensive handling of all standard ACH transaction types and preventing processing failures.
• Statement Customization
  • Improved statement disclosure management, allowing banks to customize standard disclosures that appear on customer statements for better brand alignment and regulatory compliance.

​

Security & Compliance

• Enhanced Access Controls
  • Restored proper read-only access to check deposits for Banker Viewer roles in the console, ensuring appropriate permission levels for different user types while maintaining security protocols.
• API Key Management
  • Added reactivation functionality for API keys in the console, providing banks and fintechs with better control over key lifecycle management while maintaining security best practices.

​

Console Interface Improvements

• Console Interface Improvements
  • Optimized transaction list table spacing in the console for better readability, ensuring Payment IDs and dates are fully visible without truncation.

• Treasury Prime is in the process of switching 1099 providers and will no longer be using Abound.
• Portions of the 1099 documentation have been temporarily removed while updated provider details are being added.
• Some documentation pages may appear blank during this transition.

• **Inbound ACH Manual Returns: **Now enabled by default in all sandbox environments
• Manual Holds: Account hold functionality is automatically available for testing
• Invoice Account Numbers: Custom account numbering features are ready to use immediately

• Zero Configuration: Developers can start testing advanced features without setup requests
• Complete Testing: End-to-end workflow validation, including hold management and ACH returns
• Faster Integration: Reduced time from sandbox creation to full feature testing

• Incoming ACH transaction descriptions now include the ACH “Company Description” field
• Updated format: INCOMING ACH CREDIT [Company Name] [Company Description] [Sequence Number][ccd]
• Example: INCOMING ACH CREDIT FINTECHABC PAYOUT [999000000000999][ccd]

• Clearer Transaction Purpose: Company descriptions often contain payout details, invoice references, or transaction purposes
• Better Reconciliation: Recipients can more easily identify what specific payment or service the ACH represents
• Enhanced User Experience: More descriptive transaction details in bank consoles and customer statements
• Improved Support: Reduces customer inquiries about unclear ACH transaction purposes

• Before: Dates in statements always defaulted to UTC, which could cause misleading dates near midnight boundaries.
• Now: Fintechs can configure their local timezone for statement generation.
• Additional Details:
  • New timezone field introduced in statement configuration (defaults to UTC for backward compatibility).

• Before: Ledger entries displayed as "Release hold ttx_id" and posting descriptions used "chk_id funds released".
• Now:
  • Posting description updated to use “posted” instead of “released.”
  • Hold release description updated to "Release hold for chk_id", making reconciliation clearer for customers.

• Before: All new check deposits were created with pending_review a status.
• Now: New check deposits are created with pending status.
• Additional logic: Deposits will transition to pending_review only after submission to CheckAlt, and if CheckAlt returns a pending status.

• Changed the routing number format in sandbox from “000000000” to “051883043” for all sandbox accounts

• Enables partners to test end-to-end workflows without manual overrides
• Eliminates validation errors during sandbox testing

• Who can use it? Bank admins only
• When does it apply? The account must first be moved to close_pending by the fintech
• Where is it? Accessible directly in the account details view in the Console
• What is Different?
  • Previously when a fintech moved an account to close_pending it would automatically close in 30 days w/o activity. After this enhancement this will no longer happen.
  • When the fintech flips and account to close_pending , they will need to reach out to the bank partner to close the account via the console

​

What’s Changing

• The product field will be completely removed from the account application API
• Applications using the deprecated field will receive an HTTP 400 status code
• Clients must use account_product_id instead

​

Required Action

 curl -u $API_KEY_ID:$API_SECRET_KEY <https://api.treasuryprime.com/apply/account_application> \\
     -H 'Content-Type: application/json' \\
     -d '{
           "person_applications": [
             {
               "id": "apsn_example",
               "roles": ["owner", "signer"]
             }
           ],
           "primary_person_application_id": "apsn_example",
-          "product": "personal_checking"
+          "account_product_id": "apt_yourProductId"
         }'

curl -u $API_KEY_ID:$API_SECRET_KEY <https://api.treasuryprime.com/account_product> \\
    -H 'Content-Type: application/json'

​

Documentation

• Statements will not be generated for accounts closed at least 90 days ago. This will improve statement generation time.

• Added new functionality allowing banks to view incoming bank files directly in the Console
• This will provide greater transparency and reduce the need to request file updates manually.
• Banks can access this under the Console’s “File Management” section for easy navigation.

​

Account Enrollment Type Configuration

• Added ability to configure IntraFi enrollment type (reciprocal vs one-way sell)
• Settings apply per bank-fintech combination
• Can be applied to new enrollments and retroactively to all accounts

​

Account-Specific Interest Rates

• Implemented account-level interest rate settings for IntraFi enrollments:
• Available via API (fintech) and Console (bank)
• Account-specific rates override org-level program rates
• Default rate of 0% if no rates are specified

​

Improved Webhook Delivery for Incoming ACH Updates

​

Improved Error Messaging for Issued Checks

​

Support for Other Delivery Methods

• USPS_FIRST_CLASS
• OVERNIGHT
• TWO_DAY
• USPS_CERTIFIED

• Signatory Name Field: Now stored on the checks table for easy retrieval.
• Read-Only API Access: The signatory name is now exposed as a read-only field in the API, allowing users to access it without modification.

​

Additional Check Deposit Status added to the documentation

• Declined Check could not be processed for collection by the bank

​

Additional Key Points about Invoice Account Numbers

• Dashboard Display: Additional account numbers appear in an “Additional Account Numbers” field on the account detail page
• Payment Types: Supports both incoming ACHs (debit/credit) and incoming wires
• Transaction Appearance: Transactions appear like normal payments, with the account number matching the invoice account number in incoming ACH/wire objects
• Account Nature: These are not separate accounts, but rather additional account numbers linked to an existing ledger account
• Bank Controls: Banks can only control whether organizations can create invoice accounts using the invoice_account_allowed flag. There are no limits on payment size or number of account numbers
• Lifecycle: Can remain active indefinitely and can be disabled/re-enabled as needed\

• USPS is the default selection if not specified otherwise
• PRINT (New option)

• Customers/Fintechs can generate a 1099 via this endpoint as long as a 1099 doesn’t already exist for the account.
• If a 1099 does exist for the account, customers/fintech can either delete the existing 1099 via the PATCH or DELETE endpoint (if the 1099 has not yet been filed).
• They can also create a corrected 1099 using the is_correction flag (if the 1099 has already been filed).

• The PATCH endpoint would allow users to update the status of the 1099 under certain conditions.
• If the status of the 1099 is ready_for_filing the user could PATCH the status to filing to trigger filing of the 1099.
• We would trigger the filing of the 1099 and return the entry in filing status.
• We’ll update the status to filed once the filing is completed.

• If the 1099’s status is pending or ready_for_filing, we’d use this endpoint to allow deletion of the 1099.
• At this time, the 3rd party provider doesn’t allow changes to unfilled 1099s; instead, customers/fintechs will need to delete the 1099s they want to change and create a new one.
• When this endpoint is used, we’ll delete the associated 1099 and set the status to deleted.

• Similarly, we’ve added a GET /account/:account_id/tax_document endpoint that returns the 1099s generated for an account.

• When used, Treasury Prime generates a statement and provides a URL link for configuration to be filled out.
• The endpoint does not use a statement_config, instead, it requires all parameters that will be used when generating the statement to be supplied with the request.
• Parameters that are required for a statement_config are also required when generating statements via this endpoint.
• Automatic monthly statements (bulk on the 2nd of the month) will remain available for those not using this feature.

• An unbalanced return file
• A new ON US ACH origination file that instructs internal transfers to fund the return.

• This feature is ONLY for Banks with a FIS core

• For this to be enabled at a Bank, reach out to your Relationship Manager or Treasury Prime Support

​

Introducing “The Console” (click here for more details)

​

Return Incoming ACH

​

Create Book Transfers

​

Incoming ACH view

​

Originated ACHs marked as return

​

Incoming Wire View

​

Ability to Void Wire

​

Ability to Void Wire w/ Fees

​

Check Deposits/RDC

​

FBO Table View

• As a Bank, via our new Bank Console, they will be able to return an Incoming wire via a new button “Void Wire Transaction” and apply any associated fees
• The bank can view all Outgoing/Originated wires in the new Bank Console.
• From there, a bank can select the wire in question and use the “Void Wire Transaction” button.
• When the action is triggered (Selecting Void Wire Transaction), a pop-up will appear with the bank representative will be able to provide the reason and a fee (if applicable).
• When the action is triggered/completed, funds are moved from the outgoing wire settlement account to the FBO.
• A corresponding transaction is created for the return of funds in the ledger and an additional ledger transaction is created to represent the deduction of the fees from the ledger account.

​

Voiding Outgoing Wires

• As a Bank, via our NEW Bank Console, they will be able to return an Incoming wire via a new button “Void Wire Transaction”
• If a wire is created, processed by our system, and sent out to the receiving bank where it’s then unable to be processed (for example, due to sanctions against the intended recipient or the recipient’s country), the bank will be able to mark the wire as voided and provide a reason why it’s been voided.
• The bank can view all Outgoing/Originated wires in the new Bank Console.
• From there, a bank can select the wire in question and use the “Void Wire Transaction” button.
• When the action is triggered (Selecting Void Wire Transaction), a pop-up will appear with the bank representative will be able to provide the reason.
• When the action is triggered/completed, funds are moved from the outgoing wire settlement account to the FBO.
• A corresponding transaction is created for the return of funds in the ledger.

​

Returning Incoming Wires

• As a Bank, via our new Bank Console, they will be able to return an Incoming wire via a new button “Return Incoming Wire”.
• When an incoming wire is received and is unable to process.
• The Bank can leverage the “Return Incoming Wire” button to return the wire.
• A few example reasons as to why an Incoming wire will need to be returned are as follows:
  • We receive an incoming wire with an invalid account number
  • A wire was sent to a closed account
  • Instances of detected fraud
• The bank can view all Incoming wires in done status from the new Bank Console.
• From there, a bank can select the wire in question and use the Return Incoming Wireoption.
• This will mark the wire as returned. In this scenario, Treasury Prime will not move funds.
• Since the money is still in the inbound wire settlement account, it is up to the bank to move the funds out and return them to the originating bank.

• Banks can now receive email notifications regarding originated ACH files.
• Email Structure

Subject: Treasury Prime ACH File Sent: [filename] ([Bank Name])
Body:
  (Earliest) Effective date
  Total debits $
  Total credits $
  Number of debits
  Number of credits
  Destination path + filename

• Only ledger and operating accounts will be retrieved using the [Get Account] endpoint.
• Settlement accounts & FBO accounts will no longer be included in the results.
• This change ensures streamlined access to relevant accounts for transactions and reporting.

• Addenda Record can be added for WEB SEC code
• See our updated API Reference Documentation

​

Return Incoming ACH

• Easily return incoming ACH transfers directly from “The Console” when in Done status.

• For Banks, this is automatically enabled in The Console
• For this to be enabled at a Fintech/Program, your corresponding Bank will need to provide approval.
• Please reach out to your Relationship Manager or Treasury Prime Support

​

Create Book Transfers

• Via the Book Transfer tab, you can create a book transfer to transfer funds

• For Banks, this is automatically enabled in The Console
• For this to be enabled at a Fintech/Program, your corresponding Bank will need to provide approval.
• Please reach out to your Relationship Manager or Treasury Prime Support

​

Incoming ACH view

• In “The Console”, you have a dedicated view for Incoming ACHs only in real-time.

• This is automatically enabled for all orgs using “The Console”

​

Originated ACHs marked as return

• As a Bank, via “The Console”, a user will be able to mark originated ACH items as returned

• This is automatically enabled for all Banks using “The Console”

​

Incoming Wire View

• In “The Console”, you have a dedicated view for Incoming ACHs only

• This is automatically enabled for all orgs using “The Console”

​

Ability to Void Wire

• As a Bank, via “The Console”, they will be able to return an Incoming wire via a new button “Void Wire Transaction”
• The bank can view all Outgoing/Originated wires in “The Console”.
• From there, a bank can select the wire in question and use the “Void Wire Transaction” button.
• When the action is triggered (Selecting Void Wire Transaction), a pop-up will appear with the bank representative will be able to provide the reason (if applicable).
• When the action is triggered/completed, funds are moved from the outgoing wire settlement account to the FBO.
• A corresponding transaction is created for the return of funds in the ledger.

• This is automatically enabled for all Banks using “The Console”

​

Ability to Void Wire w/ Fees

• As a Bank, via our new Bank Console, they will be able to return an Incoming wire via a new button “Void Wire Transaction” and apply any associated fees
• The bank can view all Outgoing/Originated wires in the new Bank Console, From there, a bank can select the wire in question and use the “Void Wire Transaction” button. When the action is triggered (Selecting Void Wire Transaction), a pop-up will appear with the bank representative will be able to provide the reason and a fee (if applicable). When the action is triggered/completed, funds are moved from the outgoing wire settlement account to the FBO. A corresponding transaction is created for the return of funds in the ledger and an additional ledger transaction is created to represent the deduction of the fees from the ledger account.

• This is automatically enabled for all Banks using “The Console”

​

Check Deposits/RDC

• A new check deposit tab in The Console.
• You will be able to see all checks deposited via Remote Deposit

• This is automatically enabled for all orgs with Check Deposits enabled and using “The Console”

​

FBO Table View

• In one view, a new view shows the FBO and the associated on-core accounts linked to it.

• For Banks, this is automatically enabled in The Console

• Update to the [Update An Account] Endpoint
• Effective Date: 8/15/2024
• Previously the [Update An Account] endpoint only updated information such as account status, tags, and other arbitrary user data.
• NOW, the [Update An Account] endpoint will allow the mailing and physical addresses of the associated account to be updated
• If applicable, the updated address information will be sent to the partner Marqeta.

• We have implemented an automatic retry logic for webhook messages that receive non-200 HTTP responses.
• After 10 retries the system will stop retrying

• For this to be enabled at a Fintech, Please reach out to your Relationship Manager or Treasury Prime Support.

• See our new updated Webhook API Reference

​

Early Posting for Incoming ACH Credits

• Treasury Prime can support early payroll funds.
• Most payroll ACH instructions are generally sent well in advance of the effective date to make sure the funds are available.
• For example, ACH credit instructions received on the 25th with an effective date of the 27th can be made available sooner for end users.
• For this to be enabled at a Bank, reach out to your Relationship Manager or Treasury Prime Support
• For this to be enabled at a Fintech, your corresponding Bank will need to provide approval.
• Please reach out to your Relationship Manager or Treasury Prime Support

• This is only available for credits; debits cannot be originated early through NACHA.
• NACHA limits credits to at most two business days in the future.
• The bank must fund the early credits

​

Check Deposit Status Conversion

• Old Status: pending
• New Status: pending_review
• pending_review will now indicate checks awaiting approval.

​

Returning/Voiding Wires Capabilities

• As a Bank, via our new Bank Console, they will be able to return an Incoming wire via a new button “Void Wire Transaction”
• If a wire is created, processed by our system, and sent out to the receiving bank where it’s then unable to be processed (for example, due to sanctions against the intended recipient or the recipient’s country), the bank will be able to mark the wire as voided and provide a reason why it’s been voided.
• The bank can view all Outgoing/Originated wires in the new Bank Console, From there, a bank can select the wire in question and use the “Void Wire Transaction” button. When the action is triggered (Selecting Void Wire Transaction), a pop-up will appear with the bank representative will be able to provide the reason. When the action is triggered/completed, funds are moved from the outgoing wire settlement account to the FBO. A corresponding transaction is created for the return of funds in the ledger.

• As a Bank, via our new Bank Console, they will be able to return an Incoming wire via a new button “Return Incoming Wire”.
• When an incoming wire is received and is unable to process. The Bank can leverage the “Return Incoming Wire” button to return the wire.
• A few example reasons as to why an Incoming wire will need to be returned are as follows:
  • We receive an incoming wire with an invalid account number
  • A wire was sent to a closed account
  • Instances of detected fraud
• The bank can view all Incoming wires in thedone status from the new Bank Console.
• From there, a bank can select the wire in question and use the Return Incoming Wireoption.
• This will mark the wire as returned. In this scenario, Treasury Prime will not move funds.
• Since the money is still in the inbound wire settlement account, it is up to the bank to move the funds out and return them to the originating bank.

​

International ID Numbers

• In the case an International EIN or any other ID is needed, it can be populated using these two fields identification_number & identification_number_type (these fields are optional).
• If you are partnered with Alloy and/or Unit21, data within these fields will be passed to Alloy and Unit21.
• It’s important to note that Treasury Prime will NOT validate the information in this field.
• Added optional field on person and business applications identification_number to collect international tax numbers
  • Store it as text
  • 30-character limit
• Added optional field on person and business applications identification_number_type to collect the type of identification number
  • Store it as text
  • Enforce a 30-character limit via the controller

​

Check Deposit Status Conversion

• Old Status: pending
• New Status: pending_review
• pending_review will now indicate checks awaiting approval.

• 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.

​

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.

​

Returning Incoming ACH

• 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.

​

Invoice Account Numbers

• 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

• 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.

• 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.

​

Statements

• We have made several improvements to our Statements feature for ledger customers
  • We have improved the way transaction descriptions are displayed on ledger statements.
  • 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.
  • This change will be implemented starting from the statement period of January 2024, which will be generated on February 2, 2024.
  • We have fixed a bug that used to cause the state field in ledger statements’ to show null for accounts with international addresses.

​

Support For ARC SEC Code For Incoming ACH

• We now support the ARC SEC code for incoming ACH payments.

​

Manage Enhanced FDIC Insurance For Foreign Entities Without US-TINs

• 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.

​

Statements

• 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.

​

1099-INT Generation Feature

• 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.

​

KYC Endpoints

• We have added new parameters (provider,provider_full, and provider_result) to our KYC endpoint.
• These parameters are used to define the name of the third-party KYC provider for person or business applications.

• To confirm its availability for your organization, please contact your Treasury Prime Account Manager.
• For more information, please visit our KYC API Reference page.