> ## Documentation Index
> Fetch the complete documentation index at: https://docs.treasuryprime.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Product Updates

> New releases and improvements

<Update label="July 3, 2026" tags={["console","bug-fix","documentation"]}>
  #### Console

  * **Notification Center: scrolling and display fixes for users with 50+ notifications** (beta users only)
    * The Notification Center tray now supports infinite scrolling, so users with more than 50 notifications can access their full history. Previously, the Unread tab went blank once 50 notifications accumulated, the badge was stuck at 99+, and All/Read tabs showed the same first 50 items. All four symptoms are now resolved.
  * **Multi-select for ACHs flagged for review**
    * Banks can now select multiple ACH items in table views using checkboxes. This supports the NACHA 2026 risk monitoring workflow, allowing bankers to review and act on multiple flagged ACHs at once rather than one at a time.
  * **Green Dot transactions now searchable in the Console**
    * Green Dot cash deposit transactions are now indexed in Console search results. Banks and fintechs can search for Green Dot deposits alongside other transaction types, making it easier to locate and investigate cash deposit activity.
  * **Business applications now visible to owning banks**
    * Fixed an issue where business applications submitted by fintechs were not visible to the owning bank in Console search results. Banks can now find and review business applications associated with their programs.
  * **Close open accounts from the Console**
    * Bank users can now close an open account directly from the Console. The close-account action is available to banker-role users on the account detail page.
  * **FBO creation now validates on-core account numbers**
    * When creating an FBO in the Console, the system now validates that the entered account number exists on-core before proceeding — the same validation already in place for the "Link Account" flow. This prevents errors from typos or invalid account numbers during FBO setup.

  #### Bug Fixes

  * **Changing user roles in the Console no longer errors**
    * Fixed a bug where changing a user's role (e.g., viewer to admin) in the Console resulted in a SyntaxError and the role was not updated. Role changes now apply correctly.

  #### Documentation

  * **Manual hold ID prefix corrected**
    * Fixed the API documentation examples for manual holds to use the correct `mhold_` ID prefix instead of the incorrect `hold_` prefix. This aligns the documentation with actual API responses.

  #### Reminder

  * **Bank holiday: Independence Day — Saturday, July 4, 2026**
    * Treasury Prime and our bank partners will be closed on Saturday, July 4, 2026 in accordance with Standard Federal Reserve Bank Holidays. ACH and wire transfers will not clear on that day and may take an additional business day to process.
</Update>

<Update label="June 26, 2026" tags={["console","prime banking","api","bug-fix"]}>
  #### Console

  * **Businesses now appear in Console search results**
    * Banks and fintechs can now search for businesses directly in the Console search bar. Business records are indexed alongside accounts and persons, making it easier to locate businesses without navigating through accounts first.
  * **Card controls now display correctly on card detail pages**
    * Fixed an issue where card controls (merchant category restrictions) set via the API were not displayed in the Console. The card detail page now correctly shows active card controls.

  #### Prime Banking

  * **Address autocomplete and verification improvements**
    * Prime Banking counterparty forms now include address autocomplete, reducing data entry errors and speeding up the process.

  #### API

  * **Wire fields now accept longer values for ISO 20022 compliance**
    * Several wire fields now accept longer character strings to align with ISO 20022 standards: `purpose` expands to 35 characters, `name_on_account` and counterparty bank name expands to 140 characters, and `city` and `state` fields expand to 35 characters. For banks still on legacy Fedwire formats, values are automatically truncated to the required lengths. No action is needed from existing integrations.

  #### Bug Fixes

  * **Deleting a user in the Console now works correctly**
    * Fixed a bug where clicking "Delete User" in the Console did not perform the action.
  * **Person application search results now visible to bankers**
    * Fixed a bug where person application search results were not visible to bank users in the Console. Search results now correctly display for both bank and fintech users.
</Update>

<Update label="June 12, 2026" tags={["console","api"]}>
  #### Console

  * **Flagged ACH Review: Console & Banker Tools**
    * Console now includes a **Flagged ACH (Needs Review)** tab under **Payments > ACH** for reviewing originated debit ACHs that meet your bank's flagging threshold. Treasury Prime flags originated debit ACHs at or above a configurable amount (default **\$10,000**) as part of our risk-based fraud-monitoring program supporting NACHA's 2026 Rule amendments. Flagged ACHs continue to process flagging does not block payments. Bankers can mark flagged ACHs as reviewed individually; once reviewed, an ACH no longer appears in the Needs Review tab.
    * Configure the threshold per program or account under **Programs > Limits > ACH Limits** using the **ACH Flag Review Threshold** field.
    * [Learn more →](https://docs.treasuryprime.com/docs/flagged-ach)
  * **Person and business contact details: mailing address now optional**
    * Banks and fintechs can update a person's or business's phone, email, or physical address in the Console without being forced to also fill in a mailing address. Foreign phone numbers now render correctly on detail pages, and several smaller display and edit bugs on person/business detail views have been resolved.
  * **Business name shown on accounts with an unknown primary person**
    * When an account has a business attached but the primary person is unknown, the Console now displays the business name with the correct label instead of "Unknown." This removes a long-standing source of confusion in account views.
  * **Card products now display in the Console**
    * Fixed an issue where card products visible visible via the API did not appear on the Console card products view for affected banks. Card products are now listed correctly.

  #### API

  * **Smoother wire counterparty creation: address fields are now optional**
    * Creating a wire counterparty no longer requires a zip code, and the remaining address fields (city, state) are automatically populated from the Federal Reserve routing-number table when they can be looked up. This matches typical industry requirements (city + state, not zip) and reduces friction when adding new counterparties via the API.
</Update>

<Update label="May 29, 2026" tags={["console","api","bug-fix","security"]}>
  #### Console

  * **Publicly traded entity option on business applications**
    * Banks and fintechs can now flag a business as a publicly traded entity when creating or editing a business application. This supports banks with different KYB requirements for publicly traded companies, removing the need for manual workarounds to capture this information.
  * **Green Dot transaction minimum is now configurable in Console**
    * Banks can now set the minimum transaction amount for Green Dot cash deposits directly in the Console. Previously, adjusting this threshold required a support request. This gives banks self-service control over their Green Dot deposit floor.
</Update>

<Update label="May 22, 2026" tags={["console","api","bug-fix"]}>
  #### Console

  * **NBC Snapshot dashboard now available**
    * Banks can now view a Negative Balance Cure (NBC) Snapshot page in the Console that surfaces key data at a glance: an overview of negative-balance accounts, a historical balance chart with date-range selection, the top 5 negative-balance accounts, and related loss-reserve book transfers. Filtered views now include a banner indicating active filters, so bankers always know which data they're looking at.

  #### API

  * **Update account address via API**
    * Fintechs and banks can now update the mailing address on an account record via the API. Previously, changing an account address required contacting support. This update supports address fields on the account object and works alongside the existing Console-based address editing

  #### Bug Fixes

  * **Console crash on Customer Summary scroll resolved**
    * Fixed a crash that occurred when scrolling over the "Customer Summary" section on account detail pages.
</Update>

<Update label="May 15, 2026" tags={["console","api","documentation","bug-fix","security"]}>
  #### Console

  * **Person's list and detail pages are now available**
    * Banks and fintechs can now browse and view person records directly in the Console through the account details page under the customer details tab.  The person detail surfaces key information — identity data, linked accounts in one place, reducing the need to navigate between multiple screens.
  * **Digital wallet tokens tab on Card details**
    * The Card detail page in the Console now includes a tab showing all digital wallet tokens associated with that card. This gives banks and fintechs visibility into tokenized card provisioning (e.g., Apple Pay, Google Pay).
  * **Improved beneficial ownership display**
    * The Console now provides a clearer, more detailed view of beneficial ownership information for business accounts. This makes it easier for banks to review ownership structures and verify compliance data. This is found on the account details page.

  #### API

  * **Card external\_id is now returned on GET requests**
    * Card GET responses now include the `external_id` field. Fintechs that set an external identifier when creating a card can now retrieve it on subsequent reads, making it easier to correlate card records with external systems.

  #### Bug Fixes

  * **Person name patch now works correctly**
    * Fixed an issue where updating person name fields via the API could fail under certain conditions. Name patches now apply reliably.
  * **Notification Center (Beta users only)**
    * **Duplicate changelog update notifications fixed**
      * Fixed an issue where Console users received duplicate notifications when the platform changelog was updated. Users now receive a single notification per update.
    * **Transaction limit notification wording improved**
      * Improved the wording and formatting of transaction-level limit notifications in the Console to make them clearer and easier to act on.

  #### Documentation

  * **Trace ID documentation expanded**
    * Updated the developer documentation to clarify that Trace IDs are used across multiple payment types — not just card events. This makes it easier for developers to use Trace IDs when debugging payments across ACH, wires, and other channels.
  * **Minimum age setting is now documented**
    * Added documentation for the configurable minimum age validation setting on person applications. Banks with specific age requirements can reference this documentation when configuring their programs.
</Update>

<Update label="May 12, 2026" tags={["api"]} rss={{ title:"Account name now included in List Accounts response" }}>
  #### API

  * **`name` field now returned by List Accounts**
    * The `GET /account` endpoint response now includes the `name` field for each account, matching the data already returned by [Fetch an Account](/reference/get_account-id) and the account update endpoints.
</Update>

<Update label="May 8, 2026" tags={["console","api","bug-fix","security"]}>
  #### Console

  * **Update person names directly in the Console**
    * Banks and fintechs can now edit person names — first, middle, and last — directly from the person detail page in the Console. Previously, updating a name required submitting a support ticket. This self-service capability is available to both bank and fintech users with the appropriate permissions.
  * **Reverse a mistakenly returned incoming ACH**
    * Banks can now reverse an incoming ACH that was mistakenly marked as returned, moving it back to done status directly from the Console. Previously, correcting a returned ACH required submitting a support ticket. The reversal creates a compensating transaction to restore funds and updates the ACH status accordingly. This feature works for items in both `returned` and `return_pending` states.
  * **Webhook history is now visible on payment detail pages**
    * Fintech users can now see a new section on most payment detail pages showing webhook sends for that object. This gives fintechs direct visibility into which webhooks were triggered, when they were sent, and their delivery status — making it easier to debug integration issues and confirm that events were received without needing to check separate logs or contact support.
  * **Notification Center: re-enabled notifications now fire correctly (Beta users only)**
    * Fixed a bug where disabling a Console notification type and then re-enabling it would not resume notifications.

  #### API

  * **Update person name via API**
    * Fintechs can now update the name fields on a person record via the API. Previously, name changes required submitting a support ticket. This update supports the same fields available in the Console (first, middle, and last name).

  #### Other Improvements

  * **API reference documentation navigation fixed**
    * Fixed broken navigation on the API reference documentation page at docs.treasuryprime.com. Previously, clicking on sections such as Accounts did not load the expected content. Navigation now works correctly across all reference sections.
</Update>

<Update label="May 5, 2026" tags={["api","docs"]} rss={{ title:"New filterable fields on Account Applications" }}>
  #### API & Documentation

  * **Filter Account Applications by applicant ID**
    * The `business_application_id` and `primary_person_application_id` fields on the [Account Application](/reference/account-application) object are now filterable. You can use them as query parameters when listing Account Applications to quickly find every application tied to a specific Business Application or primary Person Application — useful when reconciling related applications or building dashboards that group applications by applicant.
    * Example: `GET /apply?primary_person_application_id=apsn_01d5w6yaa6vt` returns every Account Application referencing that Person Application. The same pattern works for `business_application_id` on business account flows.
    * No changes were made to request or response shapes — only the filter capability is new. See the [Account Application reference](/docs/account-opening) for the full list of filterable fields.
</Update>

<Update label="May 1, 2026" tags={["console","api","security","prime-data","bug-fix"]}>
  #### Console

  * **Flexible ACH return filing option**
    * When returning an incoming ACH in the Console, bankers can now choose whether or not to include the return on the outgoing ACH file. Previously, returning an incoming ACH automatically placed it on the file, which caused issues when the bank had already processed the return on the core side same-day — the return would go out twice. Bankers can now mark an ACH as returned and return funds without generating a duplicate file entry. This was a top support request and eliminates a common manual run-queue workflow.

  #### Prime Data

  * **Duplicate records removed from ledger transaction stream**
    * Fixed an issue in the `int_ledger_transaction_stream` model where duplicate records could appear for the same `transaction_id` due to differences in `network_message_status`. The model now correctly deduplicates these records, ensuring that queries against ledger transaction data return one row per transaction. If you use this table in reporting or reconciliation workflows, you may notice row counts decrease slightly as the duplicates are removed.
</Update>

<Update label="April 28, 2026" tags={["api"]}>
  #### API

  * **New filters on List Account Applications**
    * The [List Account Applications](/reference/account-application) endpoint now supports filtering by `business_application_id` and `primary_person_application_id`. This makes it easier to look up the account applications associated with a given business or primary applicant without having to scan results client-side. Both fields are now also marked as filterable on the Account Application resource.
      ```bash theme={null}
      GET /apply/account_application?business_application_id=abus_01dcrqkr3yhw
      GET /apply/account_application?primary_person_application_id=apsn_01d5w6yaa6vt
      ```
</Update>

<Update label="April 27, 2026" tags={["console","api","security","prime-data","bug-fix"]}>
  #### Console

  * **ACH window configuration times displayed consistently**
    * Updated the Console to display ACH processing window times in a consistent format across all configuration settings. Previously, ACH window times were displayed differently from other time-based configs, which could cause confusion when reviewing or editing schedules. All time-based configuration fields now render in the same wall-clock format with timezone.
</Update>

<Update label="April 24, 2026" tags={["api"]}>
  #### API & Payments

  * **Filter accounts by status on List Accounts**
    * The [List Accounts](/reference/get_account) endpoint (`GET /account`) now accepts a `status` query parameter, allowing you to retrieve only accounts in a specific state (`open`, `close_pending`, or `closed`). The `status` field is also now returned on each account object in the response, removing the need to fetch each account individually to determine its state. This simplifies workflows like auditing closed accounts, monitoring accounts pending closure, or reporting on active account inventory.
</Update>

<Update label="April 22, 2026" tags={["prime-data","data"]}>
  #### Prime Data & Data Updates

  * **ACH trace number now in Prime Data**
    * The `trace_number` field on ACH records is now available in Prime Data. This field was previously exposed in the API only; it can now be queried directly from the data warehouse alongside other ACH fields, making it available for reporting, reconciliation, and analytics workflows without going through the API.
  * **`DW_UPDATED_TS` added to `assoc_txn_backing_book` table**
    * The `assoc_txn_backing_book` table — used to align ledger transactions to core transactions during reconciliation — now includes the `DW_UPDATED_TS` column. This brings it in line with the ledger transaction table and allows banks and fintechs running recon jobs to filter on last-update timestamp when investigating variances or building incremental queries.
  * **`account.status` field populated**
    * We've updated the `status` column on the `account` table so that values are now consistently populated. Previously, a subset of records had `null` status values even when the underlying account was active in the core. These records now reflect the correct status, sourced from the corresponding `ledger_account` record.
    * If you query or report on `account.status`, you may notice that records which previously returned `null` now return a populated status value (e.g., `open`). No schema changes were made — this is a data backfill only.
</Update>

<Update label="April 20, 2026" tags={["console","api","payments","bug-fix"]}>
  #### Console & Banker Tools

  * **Payment limit notifications - available to Beta users ONLY**
    * Beta users can now receive notifications when payments trigger established velocity limits. New notification types are available for ACH, wire, check deposit, issued check, and FedNow velocity limit events. These alerts apply to org-level limits, helping banks stay informed when a program approaches or exceeds configured thresholds — without generating noise from account-level limit hits. Notification preferences can be managed from the new Notifications page in the Console.

  #### API & Payments

  * **Webhook queueing for reliable delivery**
    * Webhooks are now processed through a queueing system, improving delivery reliability during high-traffic periods. This reduces the chance of dropped or delayed webhook notifications for events like transaction status changes and account updates.

  #### Bug Fixes

  * **Check deposit status changes now restricted to pending review**
    * Check deposit status decisions and amount changes can now only be made when the check is in `pending_review` status. This prevents accidental modifications to checks that have already been approved or rejected, improving data integrity for check deposit workflows.
  * **Account linking error resolved**
    * Fixed an error that could occur during account linking operations, which in some cases prevented accounts from being properly linked to their parent entities.
  * **Business account creation in Sandbox fixed**
    * Resolved issues where business account products in the Sandbox environment had incorrect workflows, which could prevent successful business account creation during integration testing. Sandbox business account flows now match production behavior.
  * **Green Dot deposit recovery**
    * Green Dot cash deposits that were incorrectly voided by providers can now be restored and committed, ensuring affected customers receive their funds. Added monitoring to proactively detect potentially problematic voided deposits.
</Update>

<Update label="April 10, 2026" tags={["api","console","payments","performance","docs"]}>
  #### API & Payments

  * **ACH trace numbers now available in the API**
    * Trace numbers for originated ACH items are now accessible through the API. Fintechs can use the new `trace_number` field on ACH endpoints to help their customers track originated ACH payments without needing to contact the bank directly.

  #### Console & Banker Tools

  * **Changelog notifications in Console for BETA users**
    * The Console now includes a notification bell that alerts users when new changelog entries are published (for select users). Clicking the notification opens a drawer with recent updates, and each notification links directly to the relevant changelog entry. When there are no new notifications, clicking the docs icon navigates to the documentation homepage as before.
  * **Account details: closed date now displayed**
    * The account details page in the Console now shows the `closed_date` for accounts that have been closed. This gives bankers immediate visibility into when an account was closed without needing to look it up separately.
  * **Account application processing fix**
    * Resolved an issue where mismatched product names between internal configuration tables could cause errors during account application processing. Product name references are now kept consistent, preventing application workflows from being blocked.
</Update>

<Update label="April 3, 2026" tags={["console","api","payments"]}>
  #### Console & Banker Tools

  * **Transaction table now sortable by amount**
    * The account transactions table in the Console can now be sorted by amount, making it easier for bankers to locate specific transactions or identify high-value activity at a glance.
  * **New transaction filters: type and payment source**
    * Bankers can now filter the account transactions table by transaction type (charge, deposit, hold, payment, reversal, etc.) and by payment source (ACH, wire, book, card, check). These filters make it faster to narrow down specific transaction activity without exporting data.

  #### Payments & Processing

  * **ACH ledger processing reliability improvement**
    * Improved the ACH process so that it allows overlapping ACH ledger processing runs, which could produce serialization errors. The system now ensures that concurrent processing windows do not conflict, resulting in smoother and more reliable ACH batch processing.
</Update>

<Update label="March 13, 2026" tags={["console","api","payments","prime-data","docs"]} rss={{ title:"FBO Table in Prime Data, Payment Hub Wire API Updates, ACH Documentation Fix, and Console Improvements" }}>
  ### **<u>Console Enhancements</u>**

  * **Marketplace Link Display Fixed**
    * A bug causing the Marketplace link in the Console navigation to not appear for some users has been resolved. A logic error in the navigation rendering was corrected to ensure the Marketplace link displays as expected.
  * **Timezone Context Added to Card Settlement Window Config**
    * Card settlement window configurations now include a `timezone_id` field, providing bankers with explicit timezone context when viewing or managing settlement windows in the Console. Previously, settlement window times were displayed without a timezone reference, which could cause ambiguity for banks in non-Eastern timezones.

  ### **<u>Payments</u>**

  * **1099-INT Correction Processing Fix**
    * Resolved an issue where certain 1099-INT correction submissions were being rejected by the tax filing provider with an error indicating no change in value, even when the corrected data differed from the original filing. Affected corrections will now process successfully.

  ### **<u>Documentation</u>**

  * **Originating ACH Guide: Lifecycle Diagrams Corrected**
    * The lifecycle diagrams in the [Originating ACH guide](https://docs.treasuryprime.com/docs/ach#lifecycle-of-an-originated-ach-credit) were incorrectly showing the flow for incoming ACH rather than originated ACH. The correct diagrams are now in place for both originated credit and debit flows.

  ### **<u>Prime Data</u>**

  * **Entitlement Table Now Available in Prime Data**
    * The `entitlement` table has been added to both the bank and fintech Prime Data marts. Banks and fintechs with Prime Data enabled can now query entitlement data directly, giving data teams visibility into which features and capabilities are enabled for their programs.
  * **FBO Table Now Available + New Green Dot and FedNow Columns**
    * The `fbo` (For Benefit Of) table has been added to both the bank and fintech Prime Data marts. Additionally, new columns for Green Dot and FedNow data have been added to the relevant mart tables. Banks and fintechs with Prime Data enabled can now query FBO account data directly and benefit from expanded transaction context for Green Dot cash deposits and FedNow transfers.
</Update>

<Update label="March 6, 2026" tags={["console","api","payments","prime-data"]} rss={{ title:"Dark Mode, Payment Config APIs, Green Dot Bug Fixes, and More" }}>
  ### **<u>Console Enhancements</u>**

  * **Dark Mode Now Available**
    * The Treasury Prime Console now supports dark mode. Users can toggle between light and dark themes based on their preference. This applies across all Console views for both bankers and fintechs.
  * **Incoming Wire Configuration Now Visible in Bank Console**
    * Bankers can now view incoming wire configuration settings directly in the Bank Menu alongside other payment configurations. Previously, this information required manually locating the configuration outside of the standard bank settings view.

  ### **<u>API Updates</u>**

  * **ACH NOC Documentation Updated: Latest Change Only**
    * API documentation for the `noc_change_code` and `noc_corrected_data` fields on ACH objects has been updated to clarify that only the most recent Notice of Change is reflected. If a new NOC is received for an ACH, it will overwrite the previous values in both fields.

  ### **<u>Payment Processing</u>**

  * **Green Dot: Rejected Deposits Now Correctly Reflect Voided Status**
    * When Treasury Prime rejects an incoming Green Dot cash deposit (for example, due to a program limit being exceeded), the deposit now correctly moves to a `voided` status and includes a reject reason. Previously, these deposits were moved to an `expired` status, which was unintuitive and made it difficult to understand why a deposit had not completed.
  * **Green Dot: Daily Limit Calculation Fixed for Non-Business Days**
    * A bug in how daily deposit limits were calculated on weekends and holidays has been resolved. Previously, Monday's limit window incorrectly included Saturday and Sunday transactions. Now, each business day only counts transactions from that day, while weekend and holiday activity looks back to the prior business day's midnight cutoff.

  ### **<u>Prime Data</u>**

  * **FBO Table Now Available in Prime Data**
    * The `fbo` table is now available in Prime Data for both bank and fintech data marts. This table provides visibility into FBO (For Benefit Of) account structures, enabling bank and fintech data teams to query and reconcile FBO account relationships directly from their Prime Data connection. Additional new columns for Green Dot and FedNow are also included in this update.

  ***

  ### **<u>⚠️ Deprecation Notice</u>**

  * **`GET /search` Endpoint Being Removed — Action Required by March 20, 2026**
    * The `/search` endpoint is being deprecated and will be permanently removed on **March 20, 2026**. This endpoint was previously documented in the API reference but is no longer supported going forward.
    * **What to do:** If your integration uses `GET /search`, please migrate to the relevant resource-specific endpoints (e.g., `GET /account`, `GET /person`, etc.) before the removal date.
    * If you have questions or need assistance migrating, please contact your Treasury Prime support team.
</Update>

<Update label="February 27, 2026" tags={["console","api","payments","prime-data"]} rss={{ title:"Account Number Reservation, ACH NOC Exposure, Console Limit Visibility, and Prime Data Enhancements" }}>
  ### **<u>Console Enhancements</u>**

  * **Fintech Program Limits Now Visible in Console**
    * Fintech users can now view their transaction and program limits directly in the Console. Previously, limits were not surfaced in the fintech-facing view, requiring them to reach out to their bank partner for that information. Limits are now displayed in the Console so fintechs always have visibility into their current thresholds.
  * **ACH Returns Now Sortable by Return Date**
    * The ACH Returns view in the Console can now be sorted by the date the return was received, in addition to the original submission date. Since ACH returns can arrive anywhere from a few days to 60 days after the original transaction, bankers previously had to scroll through pages of historical entries to find recent returns. Sorting by return date makes it significantly easier to identify and act on newly returned items.

  ### **<u>API Updates</u>**

  * **ACH Notice of Change (NOC) Data Now Exposed via API**
    * Two new fields — `noc_change_code` and `noc_corrected_data` — are now available on ACH objects via the `GET /ach`, `GET /ach/:id`, `GET /bank/ach`, and `GET /bank/ach/:id` endpoints. When a receiving bank sends a Notice of Change on an originated ACH (indicating that account or routing information should be updated), this data will now be returned directly in the API response. This gives fintechs and banks programmatic access to NOC details without needing to rely on manual notification workflows.
  * **Account Number Reservation Endpoint**
    * A new account number reservation endpoint is now available, allowing programs to reserve a specific account number before creating an account. This supports use cases where an account number must be known ahead of time — for example, pre-assigning an account number as part of an onboarding flow before the account is formally opened. The endpoint is gated behind an entitlement, and reserved numbers are validated against the program's configured prefix at the time of account creation.

  ### **<u>Prime Data</u>**

  * **ACH NOC Fields Added to Prime Data**
    * The two new ACH Notice of Change fields (`noc_change_code` and `noc_corrected_data`) are now available in Prime Data for banks and fintechs. When an ACH Notice of Change is received, these fields will be populated and accessible via Snowflake, enabling downstream reporting and account maintenance workflows.
  * **FedNow: External Reject Reason Now Available in Bank Data Tables**
    * The `external_reject_reason` field has been added to the FedNow tables in bank Snowflake reader accounts. This field surfaces the reason code when a FedNow payment is rejected externally, giving bank data teams better visibility into rejected payment details for reconciliation and reporting purposes.
  * **Green Dot Cash Deposit Transmission Data Now Visible in Prime Data**
    * The `greendot_incoming_transmission` table is now accessible to banks and fintechs via Prime Data. This table tracks ACH transmissions expected from Green Dot as part of the cash deposit funds flow, providing visibility into deposit transmission activity and status.
  * **Check and Check Issued Tables: Additional Fields Added**
    * Several fields previously available in Sigma have been added to the `checks` and `check_issued` tables in Prime Data for improved parity. New fields on `check_issued` include: `error`, `delivery_method`, `signatory_name`, and `signatory_id`. New fields on `checks` include: `return_data`, `amount_discrepancy_detected`, `risk_rating_description`, `ocr_amount`, `ocr_account`, and `ocr_routing_number`. These additions give bank data teams more complete check data for investigations and reconciliation.
</Update>

<Update label="February 20, 2026" tags={["fixes","api","docs"]} rss={{ title:"FedNow Improvements, ACH Validation, and Prime Data Enhancements" }}>
  ### **<u>FedNow Improvements</u>**

  * **FedNow Limit Calculation Fix**
    * Rejected FedNow payments are no longer counted against transaction limits. Previously, if a FedNow payment was rejected by the receiving bank, it was still included in the daily limit calculation, which could prevent subsequent legitimate payments from processing. Limits now only reflect payments that were successfully processed.
  * **FedNow Reject Reason Now Available**
    * The FedNow payment object now includes a `reject_reason` field that provides detailed error information when a payment is rejected by the receiving institution. This gives fintechs better visibility into why a FedNow payment failed, enabling more informative error handling and end-user messaging.

  ### **<u>Documentation</u>**

  * **Green Dot Locations API: Updated Field Requirements**
    * Updated the Green Dot cash deposit locations API documentation to clarify required fields. The `ip_address` field is now marked as required, and either `lat`/`long` coordinates or a `zip_code` must be provided when searching for deposit locations. These changes ensure developers have accurate integration guidance.

  ### **<u>Data & Reporting</u>**

  * **Prime Data: Improved Person Role Consolidation**
    * Improved how person roles are recorded in Prime Data. Previously, when a person had multiple associations with the same account, their roles could be reflected inconsistently. The updated logic now properly consolidates these role entries under the same account ensuring more accurate person-level data in downstream reporting and compliance datasets.
  * **Prime Data: Sole Proprietorship Application Fix**
    * Fixed a data quality issue in Prime Data where sole proprietorship account applications were being duplicated across both the person and company application tables. Applications with an ownership type of "personal" are now correctly categorized in a single table, eliminating double-counting in compliance and reporting queries.
  * **Prime Data: Snowflake Reader Account Expansion**
    * Additional bank partners have been onboarded to Snowflake Reader Accounts as part of the ongoing Prime Data V1 deprecation migration. Banks transitioning from the legacy RDS-based data feed now have access to faster, more frequent data refreshes through Snowflake. As a reminder, V1 will no longer be updated after **February 28, 2026**.
</Update>

<Update label="February 13, 2026" tags={["console","fixes","api","deprecations","docs"]} rss={{ title:"Console Enhancement, Search Endpoint Deprecation, and Sandbox Simulation Fixes" }}>
  ### **<u>Console Enhancements</u>**

  * **Retry Button for Failed Book Transfers**
    * Bank users can now retry failed book transfers directly from the Console. When a book transfer has an `Error` status, a retry button is available on the detail page, eliminating the need to contact support to re-process the transfer. Once a retry succeeds, the button is automatically disabled.
  * **Banker Viewers Can Now See Limits**
    * The Banker Viewer role can now view limits in the Console. Previously, only Banker Admin users could see limits, which prevented compliance and operations team members from accessing this information without elevated permissions.

  ### **<u>API Updates</u>**

  * **Deprecation: Search Endpoint Being Removed**
    * The `GET /search` endpoint is being deprecated and will be turned off on **March 6, 2026**. If your integration currently uses this endpoint, please migrate to the appropriate resource-specific list or filter endpoints. Documentation for the search endpoint has been removed. If you have questions about migration, please reach out to support.

  ### **<u>Documentation</u>**

  * **Wire Simulation Docs: Fixed Invalid JSON Example**
    * Corrected an invalid trailing comma in the JSON request example for the incoming wire simulation endpoint in the API documentation. Developers copying the example directly will no longer encounter parsing errors.
  * **Simulation Docs: Corrected URLs to Sandbox**
    * Fixed two simulation example requests in the API documentation that incorrectly pointed to the production URL instead of the sandbox URL. Developers following the docs will now be directed to the correct sandbox endpoint.
  * **Changelog Now Supports RSS Feed**
    * The Treasury Prime changelog now generates a proper RSS feed, allowing customers to subscribe and receive automatic notifications when new updates are published.

  ### **<u>Data & Reporting</u>**

  * **Prime Data: Duplicate Record Cleanup in Company Person Data**
    * For customers using Prime Data, approximately 500 duplicate records have been removed from the company person dataset. Previously, certain account applications with multiple entries for the same person could generate duplicate rows. Records are now consolidated to one per unique person and company. Incomplete applications that previously resulted in null ID values now display a valid identifier. This improves data accuracy for compliance and reporting workflows.
</Update>

<Update label="February 6, 2026" tags={["console","api","docs"]} rss={{ title:"Console Enhancements, Green Dot API Updates, and Documentation Improvements" }}>
  ### **<u>Console Enhancements</u>**

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

  ### **<u>Green Dot Cash Deposits</u>**

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

  ### **<u>Documentation</u>**

  * **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.
</Update>

<Update label="February 4, 2026" tags={["fixes","api"]} rss={{ title:"FedNow ID Now Populated in Ledger Transactions" }}>
  ### **<u>Data & Reporting</u>**

  * **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.
</Update>

<Update label="February 4, 2026" tags={["announcements","deprecations"]} rss={{ title:"Prime Data: Migration to Snowflake (V1 Deprecation)" }}>
  ### **<u>Prime Data: Migration to Snowflake (V1 Deprecation)</u>**

  We're completing our migration of Prime Data to Snowflake, delivering faster and more reliable data access for all customers.

  **What's changing:**

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

  **What this means for you:**

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

  **Why we're making this change:**

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

  **Need help migrating?** Contact your Relationship Manager
</Update>

<Update label="January 23, 2026" tags={["console","features","fixes"]} rss={{ title:"Console Enhancements and FedNow Search Support" }}>
  ### **<u>Console Enhancements</u>**

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

  ### **<u>FedNow Improvements</u>**

  * **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`

  ### **<u>Wire Transfers</u>**

  * **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.
</Update>

<Update label="January 16, 2026" tags={["console","features","api"]} rss={{ title:"Card and Account Management Console Updates" }}>
  ### **<u>Console Enhancements</u>**

  * **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.*
</Update>

<Update label="January 9, 2026" tags={["console","fixes","api"]} rss={{ title:"Console Transaction and Analytics Fixes" }}>
  ### **<u>Console Enhancements</u>**

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

  ### <u>API Updates</u>

  * **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.
</Update>

<Update label="December 19, 2025" tags={["features","api"]} rss={{ title:"FedNow Simulations and Tax Document Improvements" }}>
  ### <u>Console Enhancements</u>

  **Human-Readable Transaction Descriptions Now Displayed**\
  The bank Console now displays the `human_readable_description` field for transactions, providing a clearer context for FedNow and other payment types directly in the transaction details view.

  **Treasury Prime AI Marketplace Now Accessible from Console**\
  Bank Admin users can now access the Treasury Prime AI Marketplace directly from the Console. The Marketplace provides a streamlined way to discover and connect with vetted fintech partners seeking banking relationships.

  **Console Search Results Restored**\
  Fixed an issue where searching for specific IDs (accounts, ACH, books, etc.) in the Console was not returning results.

  ### <u>FedNow </u>

  **FedNow: Security Context Now Optional**\
  The `security_context` field is no longer required when sending FedNow payments. This aligns with updated FedNow network requirements and simplifies the payment initiation process.

  **FedNow Simulations Now Available**\
  Fintechs can now test FedNow integrations in the sandbox environment. Incoming payment simulations allow you to trigger test payments to your accounts, similar to how incoming ACH simulations work today. This enables end-to-end testing of your FedNow workflows before going live.

  ### <u>Prime Cash (powered by Green Dot Network)</u>

  **Green Dot Cash Deposit Simulations Now Available**\
  Fintechs can now test Green Dot cash deposit integrations in the sandbox environment. Simulations allow you to trigger test cash deposits to your accounts, enabling end-to-end testing of your cash deposit workflows before going live.

  ### Tax Document Filing (1099-INT)

  <Info>
    Please refer to our new documentation on [Creating and Filling a 1099-INT](https://docs.treasuryprime.com/docs/creating-and-filing-a-1099-int)
  </Info>

  **Tax Documents: Error Field Now Exposed**\
  The tax document API response now includes an `error` field, providing visibility into any issues that occurred during 1099-INT processing or filing.

  **Tax Documents: TIN Matching Can Be Skipped**\
  A new `skip_tin_verification` flag is available when creating tax documents, allowing users to bypass TIN matching if they have already verified recipient information through other means.
</Update>

<Update label="December 19, 2025" tags={["announcements","api"]} rss={{ title:"1099-INT Vendor Transition to TaxBandits" }}>
  **What's new with 1099-INTs at Treasury Prime?**

  Treasury Prime has transitioned to a new vendor partner, TaxBandits, and enhanced our 1099-INT generation endpoint, making it easier for you to manage the 1099-INT creation and filing process, leveraging our API. For full details, please see our updated [<u>1099-INT guide</u>](https://docs.treasuryprime.com/docs/creating-and-filing-a-1099-int)

  **What are the 1099 filing deadlines, and what does your organization need to know to be prepared?**

  If your organization uses the Treasury Prime ledger and disburses interest to customers, you may be required to provide your customers with 1099-INTs for the previous calendar year. Customers who are obligated to provide 1099s must do so by **February 2, 2026**. Treasury Prime supports 1099-INTs generation, but we will require your action to ensure accuracy and distribution to your end users.

  **ACTION REQUIRED**

  Please verify the following information about your organization with your Treasury Prime account manager before you begin generating 1099-INTs with our API. It will not be possible to generate 1099-INTs via Treasury Prime until we have received this information.

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

  **Pricing**

  The costs associated with generating forms 1099-INT via Treasury Prime for the 2025 tax year for your organization are as follows. You need to confer with your bank partner and/or your Treasury Prime Relationship Manager to determine whether you need to execute an amendment to your existing contract to account for the costs of this product.  To the extent you need to execute an amendment, it is your responsibility to work with Treasury Prime to ensure that an amendment is executed no later than January 5th, 2026.

  * 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)

  **In summary**

  To generate these forms accurately and ensure your customers receive them on time, please adhere to the following steps:

  * 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 [<u>here</u>](https://docs.treasuryprime.com/reference/patch_transaction-id).
  * You will be able to reference our updated [<u>1099-INT documentation</u>](https://docs.treasuryprime.com/docs/creating-and-filing-a-1099-int) 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.
</Update>

<Update label="December 15, 2025" tags={["announcements"]} rss={{ title:"Banking Holiday and Support Availability Notice" }}>
  This is a friendly reminder that our bank partners will be closed for Christmas Day on Thursday, December 25th, 2025, and New Year's Day on Thursday, January 1, 2026, in accordance with the Standard Federal Reserve Bank Holidays.

  Treasury Prime offices will be closed for the winter holiday for the entire week starting Thursday, December 25, 2025, until Thursday, Jan 1, 2026.

  **How will this impact your payments?**

  Since transfers do not clear on bank holidays (Dec. 25 and Jan. 1), ACH and Wire transfers may clear a day slower than expected. In addition, prior to Treasury Prime offices closing for the winter break, we plan to freeze work on new features and bug fixes to lower the risk of deploying bugs, regressions, or other issues within our system.

  Soft Freeze (Dec. 17 - Dec. 19)

  * Bug fixes allowed, but no new feature deployment.

  Hard Freeze (Dec. 22 - Jan. 3)

  * No code deployments, exceptions for critical issues.

  **How will this impact support availability?**

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

  **Questions?** Feel free to reach out to our support team at [**<u>help@treasuryprime.com</u>**](mailto:help@treasuryprime.com).
</Update>

<Update label="December 12, 2025" tags={["console","features","api"]} rss={{ title:"FedNow Console Tab and Enhanced Data Access" }}>
  ### <u>Console Enhancements</u>

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

  ### <u>Search Improvements</u>

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

  ### <u>API Updates</u>

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

  ### <u>Bug Fixes</u>

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

  **Check Deposit Error Messages Improved**

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

  ### <u>Prime Data</u>

  * **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.
</Update>

<Update label="December 5, 2025" tags={["features","console","api"]} rss={{ title:"FedNow Search and Book Transfer Performance" }}>
  ### Payments & Transfers

  **FedNow Search Support**

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

  **Improved Book Transfer Performance**

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

  ### Console & Search

  **Console Search Improvements**

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

  **Account Transaction Sorting**

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

  **Prime Analytics Access**

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

  ### Cards

  **Mastercard Tap to Add Card**

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

  **Digital Wallet Token Updates**

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

  **OCT Transaction Handling**

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

  ### Documentation

  **Reserve Account Documentation**

  * Updated API documentation to clarify that only ledger accounts can be linked as reserve accounts.
</Update>

<Update label="November 21, 2025" tags={["console","fixes"]} rss={{ title:"Console Search and Permission Fixes" }}>
  ### **<u>Improvements & Bug Fixes</u>**

  **Search Improvements**

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

  **Console Enhancements**

  * **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_type`field to the incoming ACH table display in the Console, providing better visibility into ACH transaction processing details.
</Update>

<Update label="November 14, 2025" tags={["features","announcements","fixes"]} rss={{ title:"Prime Cash Launch via Green Dot Partnership" }}>
  ### <u>✨ New Feature Alert</u>

  **Feature Spotlight: Prime Cash (Powered by Green Dot) – Expanding Financial Access Through Cash Funding**

  Treasury Prime has partnered with **Green Dot®** to launch **Prime Cash (Powered by Green Dot)**, a game-changing solution that lets your customers instantly fund their accounts with cash at more than 90,000 retail locations nationwide, including Walmart, CVS, and 7-Eleven. With funds typically available within minutes, Prime Cash delivers a fast, secure, and frictionless funding experience for both individuals and businesses. More than a convenience, Prime Cash represents a strategic opportunity for financial institutions. By meeting customers where they are, whether they prefer cash or need alternative funding options, banks and fintechs can build deeper trust, strengthen engagement, and broaden financial inclusion. Embedding Prime Cash directly into your app allows institutions to drive deposits, expand reach, and empower more customers to participate in the digital economy.

  **Ready to get started?** Contact your Bank Partner or Treasury Prime Relationship Manager to confirm availability and begin implementation today.

  [API Documentation](https://docs.treasuryprime.com/reference/greendot)

  ### <u>Improvements & Bug Fixes</u>

  **Digital Wallets**

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

  **Documentation**

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

  ### <u>Prime Data</u>

  **Incoming Wire Error Tracking Enhancement**

  * 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.
</Update>

<Update label="November 7, 2025" tags={["fixes","api"]} rss={{ title:"Digital Wallets and Payment Processing Fixes" }}>
  ### <u>Improvements & Bug Fixes</u>

  **Cards & Digital Wallets**

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

  **Account Holds**

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

  **Sandbox Performance**

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

  **Database Performance**

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

  **Error Handling**

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

  ### <u>Bank & Payment Processing</u>

  **Wire Transfers**

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

  **ACH Processing**

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

  **FedNow Payments**

  * **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.
</Update>

<Update label="October 31, 2025" tags={["fixes","api","console"]} rss={{ title:"Wire Processing and Console Navigation Improvements" }}>
  ### 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
</Update>

<Update label="October 28, 2025" tags={["console","features","fixes"]} rss={{ title:"Check Return and Documentation Navigation Updates" }}>
  ### 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](http://docs.treasuryprime.com)) and Core Direct ([direct.treasuryprime.com](http://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
</Update>

<Update label="October 17, 2025" tags={["api","console","fixes"]} rss={{ title:"Check Deposits and Wire Transfer Enhancements" }}>
  ### API Enhancements

  **Check Deposits**

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

  ### Console Improvements

  **Feature History Display**

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

  **Wire Transfers**

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

  **User Management**

  * Fixed an issue where banker administrators were unable to invite users with the "Banker Account Reviewer" role.

  **Check Management**

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

  **Payment Processing & Reliability**

  * 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

  **API Guides**

  * 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.
</Update>

<Update label="October 10, 2025" tags={["console","fixes"]} rss={{ title:"OpenSearch Testing and Card Transaction Visibility" }}>
  ### **New Features & Enhancements**

  **Banking Infrastructure**

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

  **Console & User Interface**

  * 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

  **Technical Infrastructure**

  * Code cleanup: Resolved database schema issues including default values and constraint validations
</Update>

<Update label="October 3, 2025" tags={["features","console","api"]} rss={{ title:"Cards Performance and Internal Transfers" }}>
  ### **New Features & Enhancements**

  **Card & Digital Wallet Services**

  * **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

  **Prime Banking**

  * **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

  **Payment Processing & ACH**

  * **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)

  **Statements & Reporting**

  * **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

  **Platform & Infrastructure**

  * **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

  **Documentation Updates**

  * **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
</Update>

<Update label="September 26, 2025" tags={["api","fixes"]} rss={{ title:"FedNow and Card Product Enhancements" }}>
  ### New Features & Enhancements

  **API & Error Handling**

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

  **Card Products & Digital Wallets**

  * **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

  **Payment Processing**

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

  **Check Processing**

  * **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.
</Update>

<Update label="September 19, 2025" tags={["fixes","console","api"]} rss={{ title:"Platform Improvements and ACH Processing" }}>
  ### 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.
</Update>

<Update label="August 28, 2025" tags={["announcements","deprecations"]} rss={{ title:"1099 Provider Transition Notice" }}>
  * 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.
</Update>

<Update label="August 28, 2025" tags={["features"]} rss={{ title:"Sandbox Features Auto-Enabled" }}>
  Automatically enabled key sandbox features out of the box to streamline developer onboarding and testing workflows.

  **What's Changing**

  * \*\*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

  **Benefits**

  * **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
</Update>

<Update label="August 27, 2025" tags={["features","api"]} rss={{ title:"Enhanced ACH Descriptions with Company Field" }}>
  <Info>
    ***Scheduled change for September 3rd, 2025***
  </Info>

  Enhanced incoming ACH transaction descriptions to include the company description field alongside existing company name information for better transaction identification.

  **What's Changing**

  * 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]

  **Benefits**

  * 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
</Update>

<Update label="August 25, 2025" tags={["features","api"]} rss={{ title:"Timezone Configuration for Statements" }}>
  Added support for configuring a timezone in statement settings.

  * **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).
</Update>

<Update label="August 21, 2025" tags={["fixes"]} rss={{ title:"Improved RDC Check Release Descriptions" }}>
  * **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.
</Update>

<Update label="August 13, 2025" tags={["fixes"]} rss={{ title:"Check Deposit Status Logic Update" }}>
  * **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.
</Update>

<Update label="August 8, 2025" tags={["features"]} rss={{ title:"Valid Routing Number for Sandbox Environment" }}>
  Updated the sandbox environment to use a valid routing number instead of placeholder zeros 0's to improve testing capabilities for integration partners.

  **What's Changing**

  * Changed the routing number format in sandbox from "000000000" to "051883043" for all sandbox accounts

  **Benefits**

  * Enables partners to test end-to-end workflows without manual overrides
  * Eliminates validation errors during sandbox testing
</Update>

<Update label="July 11, 2025" tags={["fixes","console"]} rss={{ title:"Fixed Person and Business Title Display" }}>
  Fixed UI display issue in the Overview Page where company names were incorrectly appearing in place of person names. The system now correctly displays the person's name (e.g., "Josh E Johnson") in the Person field instead of duplicating the business name (e.g., "Example LLC"). This fix ensures proper distinction between business and personal account information.⁠⁠
</Update>

<Update label="July 11, 2025" tags={["features","announcements"]} rss={{ title:"Fedwire ISO 20022 Migration Readiness" }}>
  We're ready! Treasury Prime is fully prepared for the Federal Reserve Financial Services' (FRFS) upcoming ISO 20022 implementation for the Fedwire Funds Service, scheduled for **Monday, July 14, 2025**.

  In alignment with FRFS's single-day implementation strategy, we have completed all necessary updates to support the transition from the legacy FAIM format to the new ISO 20022 messaging standard. All proprietary FAIM messages will be sunset and replaced by ISO 20022-compliant messages as of the implementation date.

  Customers and partners can expect continued support and seamless Fedwire Funds Service operations following this change.

  🔗 [Learn more about the ISO 20022 implementation on FRFS](https://www.frbservices.org/resources/financial-services/wires/iso-20022-implementation-center)
</Update>

<Update label="July 7, 2025" tags={["announcements","console"]} rss={{ title:"Sandbox Console Matches Production" }}>
  As of today, our Sandbox experience matches our production experience! The legacy sandbox app (developer dashboard and bank console) now redirects to [https://app.sandbox.treasuryprime.com](https://app.sandbox.treasuryprime.com). Note: You can use the same email and password as before.
</Update>

<Update label="May 15, 2025" tags={["features","console"]} rss={{ title:"Bank Admins Can Close Accounts in Console" }}>
  We've added a new capability to the Console that allows **bank admins** to close accounts that are in the `close_pending` status.

  * **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

  This enhancement streamlines the account closure process and gives banks more control over finalizing account lifecycle actions.

  Please refer to our [Closing an Account](https://docs.treasuryprime.com/docs/closing-an-account#activity-on-a-closed-account) documentaion for more details
</Update>

<Update label="May 14, 2025" tags={["features","console"]} rss={{ title:"Features Visibility and Toggles Added" }}>
  Starting **on Monday**, 5/12/2025, we released a small but powerful change in your Console.

  We've introduced a new **features** section that clearly shows **which features are enabled** for your fintechs/programs. You'll also be able to **toggle features that are currently on to off** directly from this view, giving you more control and visibility.

  At this time, you will **NOT** be able to toggle features that are currently "off" to "on", this functionality will be available in future rollouts. If you are interested in adding more features, please reach out to your Relationship Manager

  In addition, no action is needed on your part, and this update will appear automatically in your Console.

  <img src="https://mintcdn.com/treasuryprime/gHGxfRvS5k4Gnce7/images/image(12).png?fit=max&auto=format&n=gHGxfRvS5k4Gnce7&q=85&s=7a609d18abf7ad221d2d5f6bb3d36b0e" alt="Features Visibility" width="674" height="720" data-path="images/image(12).png" />

  If you have any questions or run into issues, our support team is here to help. Please feel free to reach out to our customer support team at [help@treasuryprime.com](mailto:help@treasuryprime.com) or through the [Customer Support Platform](http://click.treasuryprime.com/MjUzLVdRQi04MjgAAAGTjwEF_PrWJ-kj7N-hZYT1vooR1-4pOOXWQli3bsttRrpAlJUaQzkX4VtvvYkkjVJFzdD5fnc=). We are here to assist you every step of the way.
</Update>

<Update label="May 7, 2025" tags={["deprecations","api"]} rss={{ title:"Deprecating Product Field in Account Applications" }}>
  On June 1st, 2025, we will be removing support for the `product` field in account applications. This field has been deprecated since November 2021.

  ## 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

  Replace the `product` field with `account_product_id` in your API calls. For example:

  ```text theme={null}
   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"
           }'
  ```

  You can retrieve your available account product IDs using:

  ```text theme={null}
  curl -u $API_KEY_ID:$API_SECRET_KEY <https://api.treasuryprime.com/account_product> \\
      -H 'Content-Type: application/json'
  ```

  ## Documentation

  For more details, please refer to our documentation on [opening an account](https://docs.treasuryprime.com/docs/opening-an-account#4-select-an-account-product) and the [account application API reference](https://docs.treasuryprime.com/reference/account-application).
</Update>

<Update label="April 25, 2025" tags={["fixes"]} rss={{ title:"Statement Generation Performance Improvement" }}>
  * Statements will not be generated for accounts closed at least 90 days ago. This will improve statement generation time.
</Update>

<Update label="March 19, 2025" tags={["features","console"]} rss={{ title:"Incoming Bank Files View in Console" }}>
  * 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.
</Update>

<Update label="March 18, 2025" tags={["features","fixes"]} rss={{ title:"IntraFi Configuration and Interest Rates" }}>
  ### 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
</Update>

<Update label="February 14, 2025" tags={["features","console"]} rss={{ title:"Card Pages Added to Console" }}>
  We've enhanced our console experience by introducing Card List and Card Detail Pages, providing better visibility and management of issued cards.
</Update>

<Update label="February 11, 2025" tags={["fixes","features"]} rss={{ title:"Webhook Delivery and Check Error Improvements" }}>
  ### Improved Webhook Delivery for Incoming ACH Updates

  We have resolved an issue where some customers were not receiving updated webhooks for incoming ACH transactions. As of today, all incoming ACH update events will now correctly trigger webhook notifications. Previously, while the initial create webhook was successfully sent, subsequent update notifications—such as those indicating a return—were not being delivered.

  ### Improved Error Messaging for Issued Checks

  We've enhanced our API response for issued checks to provide better visibility into error statuses. Now, the API will explicitly indicate when the issue is related to velocity limits, similar to how ACH returns provide actionable retry guidance.

  ### Support for Other Delivery Methods

  Within the field delivery\_method The below options will be available.

  * USPS\_FIRST\_CLASS
  * OVERNIGHT
  * TWO\_DAY
  * USPS\_CERTIFIED

  <Info>
    USPS is the default selection if not specified otherwise
  </Info>

  The above options are not available for all orgs. Please reach out to your bank partner and/or RM for more details
</Update>

<Update label="February 11, 2025" tags={["features"]} rss={{ title:"Signatory Name for Printed Checks" }}>
  We've added the signatory name to the issued checks table, ensuring that customers who print their own checks have all the necessary information. Previously, this data was generated but not stored, making it inaccessible for those needing to print checks independently.

  What's New?

  * 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.
</Update>

<Update label="January 28, 2025" tags={["features"]} rss={{ title:"Additional Check Status and Invoice Details" }}>
  ### Additional Check Deposit Status added to the documentation

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

  <Info>
    This status is only available at certain banks
  </Info>

  ### 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\\
</Update>

<Update label="January 27, 2025" tags={["features"]} rss={{ title:"Enhanced Shipping Methods for Issued Checks" }}>
  A new field has been added:delivery\_method. Which will allow orgs and users to pick a shipping method.

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

  <Info>
    The PRINT option provides check data only; customers must handle check image generation for printing. This endpoint remains provider-agnostic for seamless integration.
  </Info>
</Update>

<Update label="January 20, 2025" tags={["fixes","console"]} rss={{ title:"Search Filtering Added to Console" }}>
  Users will now see a filter in the search bar upon entering 3 characters or more. This will enable users to quickly find specific data in the console search engine like filtering for accounts, ACHs, Wires, and more.

  <Info>
    This is automatically enabled for all organizations using "The Console"
  </Info>
</Update>

<Update label="January 17, 2025" tags={["announcements","console"]} rss={{ title:"New Console Launch Announcement" }}>
  Some of you may have noticed a new banner announcing our new console in your old console/dashboard. Please see that message below

  <Warning>
    #### The New Console is Live!

    We will be removing access to this application on January 15, 2025. Please contact support if you have questions or concerns.

    Try It Now
  </Warning>
</Update>

<Update label="December 18, 2024" tags={["features","api"]} rss={{ title:"Enhanced 1099-INTs On-Demand Generation" }}>
  Now, customers/fintechs can use the endpoint `POST /account/:account_id/tax_document ****` to generate 1099s on demand

  * 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).

  If a change is needed for the tax document, customers/fintechs can use the `PATCH /account/:account_id/tax_document/:id` to make the necessary update

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

  Additional endpoints `DELETE /account/:account_id/tax_document/:id` and `GET /account/:account_id/tax_document/:id` are available for use.

  For `DELETE /account/:account_id/tax_document/:id`

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

  For GET `/account/:account_id/tax_document/:id`

  * Similarly, we've added a `GET /account/:account_id/tax_document` endpoint that returns the 1099s generated for an account.
</Update>

<Update label="December 4, 2024" tags={["features","api"]} rss={{ title:"Enhanced Statement Generation Endpoint" }}>
  Now, customers can use the endpoint `POST /account/:account_id/statement` to generate on-demand statements.

  * 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.
</Update>

<Update label="October 25, 2024" tags={["fixes","api"]} rss={{ title:"Account Endpoint Daily Balances Update" }}>
  Now the `/Account` endpoint can provide a list of Daily Balances along with the average balance
</Update>

<Update label="October 9, 2024" tags={["features"]} rss={{ title:"Split Balanced ACH Return File" }}>
  <Info>
    This feature is ONLY for Banks with a FIS core
  </Info>

  We can now generate two files when processing returns:

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

  Restrictions

  * This feature is ONLY for Banks with a FIS core

  How to Enable

  * For this to be enabled at a Bank, reach out to your Relationship Manager or Treasury Prime Support
</Update>

<Update label="September 30, 2024" tags={["announcements","console"]} rss={{ title:"Introducing The Console and New Features" }}>
  ### Introducing "The Console" (click here for more details)

  We have a new and Improved Console!! Replacing our Production Bank Console and Developer Dashboard, and providing a host of new features. Only a few of our orgs have access to "The Console" as we eagerly get ready to roll this out. If you are interested in a Demo, please reach out to your Relationship Manager.

  Check out the new features such as:

  ### Return Incoming ACH

  \* **Description:** Easily return incoming ACH transfers directly from "The Console" when in Done status.

  \* **How to Enable:**

  \* 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

  \* **Description:** Via the Book Transfer tab, you can create a book transfer to transfer funds

  \* **How to Enable:**

  \* 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

  \* **Description:** In "The Console", you have a dedicated view for Incoming ACHs only in real-time.

  \* **How to Enable:**

  \* This is automatically enabled for all orgs using "The Console"

  ### Originated ACHs marked as return

  \* **Description:** As a Bank, via "The Console", a user will be able to mark originated ACH items as returned

  \* **How to Enable:**

  \* This is automatically enabled for all Banks using "The Console"

  ### Incoming Wire View

  \* **Description:** In "The Console", you have a dedicated view for Incoming ACHs only

  \* **How to Enable:**

  \* This is automatically enabled for all orgs using "The Console"

  ### Ability to Void Wire

  \* **Description:**

  \* 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.

  \* **NOTE:** For some banks that support sending Treasury Prime notifications about wires being rejected, the process of voiding an outgoing wire is already automated.

  \* **How to Enable:**

  \* This is automatically enabled for all Banks using "The Console"

  ### Ability to Void Wire w/ Fees

  \* Description:

  \* 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.

  \* **NOTE:** For some banks that support sending Treasury Prime notifications about wires being rejected, the process of voiding an outgoing wire is already automated.

  \* **How to Enable:**

  \* This is automatically enabled for all Banks using "The Console"

  ### Check Deposits/RDC

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

  \* How to Enable:

  \* This is automatically enabled for all orgs with Check Deposits enabled and using "The Console"

  ### FBO Table View

  \* **Description:** In one view, a new view shows the FBO and the associated on-core accounts linked to it.

  \* **How to Enable:**

  \* For Banks, this is automatically enabled in The Console
</Update>

<Update label="September 17, 2024" tags={["fixes","console"]} rss={{ title:"Voiding Outgoing Wires with 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.

  <Info>
    For some banks that support sending Treasury Prime notifications about wires being rejected, the process of voiding an outgoing wire is already automated.
  </Info>
</Update>

<Update label="September 16, 2024" tags={["features","console"]} rss={{ title:"Voiding and Returning Wires Capabilities" }}>
  ### 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.

  <Info>
    For some banks that support sending Treasury Prime notifications about wires being rejected, the process of voiding an outgoing wire is already automated.
  </Info>

  ### 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.
</Update>

<Update label="September 12, 2024" tags={["features"]} rss={{ title:"Originated ACH Email Notifications" }}>
  * Banks can now receive email notifications regarding originated ACH files.
  * Email Structure

  ```text theme={null}
  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
  ```
</Update>

<Update label="September 12, 2024" tags={["fixes","api"]} rss={{ title:"Update to List Account Endpoint" }}>
  * 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.
</Update>

<Update label="September 11, 2024" tags={["features","api"]} rss={{ title:"Addenda Record for WEB SEC Code ACH" }}>
  * Addenda Record can be added for WEB SEC code
  * See our updated API Reference Documentation
</Update>

<Update label="September 4, 2024" tags={["features","console","announcements"]} rss={{ title:"Console Launch with Multiple Features" }}>
  We have a new and Improved Console!! Replacing our Production Bank Console and Developer Dashboard and providing a host of new features. Only a few of our orgs have access to "The Console" as we eagerly get ready to roll this out. If you are interested in a Demo, please reach out to your Relationship Manager. Check out the new features such as:

  ### Return Incoming ACH

  Description

  * Easily return incoming ACH transfers directly from "The Console" when in Done status.

  How to Enable

  * 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

  Description

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

  How to Enable

  * 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

  Description

  * In "The Console", you have a dedicated view for Incoming ACHs only in real-time.

  How to Enable

  * This is automatically enabled for all orgs using "The Console"

  ### Originated ACHs marked as return

  Description

  * As a Bank, via "The Console", a user will be able to mark originated ACH items as returned

  How to Enable

  * This is automatically enabled for all Banks using "The Console"

  ### Incoming Wire View

  Description

  * In "The Console", you have a dedicated view for Incoming ACHs only

  How to Enable

  * This is automatically enabled for all orgs using "The Console"

  ### Ability to Void Wire

  Description

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

  <Info>
    For some banks that support sending Treasury Prime notifications about wires being rejected, the process of voiding an outgoing wire is already automated.
  </Info>

  How to Enable

  * This is automatically enabled for all Banks using "The Console"

  ### Ability to Void Wire w/ Fees

  Description

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

  <Info>
    For some banks that support sending Treasury Prime notifications about wires being rejected, the process of voiding an outgoing wire is already automated.
  </Info>

  How to Enable

  * This is automatically enabled for all Banks using "The Console"

  ### Check Deposits/RDC

  Description

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

  How to Enable

  * This is automatically enabled for all orgs with Check Deposits enabled and using "The Console"

  ### FBO Table View

  Description

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

  How to Enable

  * For Banks, this is automatically enabled in The Console
</Update>

<Update label="August 15, 2024" tags={["fixes","api"]} rss={{ title:"Update Account Endpoint Address Support" }}>
  * 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.
</Update>

<Update label="August 2, 2024" tags={["features","api"]} rss={{ title:"Smart Webhook Retries" }}>
  Description

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

  How To Enable

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

  Documentation

  * See our new updated Webhook API Reference
</Update>

<Update label="August 1, 2024" tags={["features","fixes"]} rss={{ title:"Early Posting for Incoming ACH Credits" }}>
  #### Early Posting for Incoming ACH Credits

  Description

  * 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

  Restrictions

  * 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

  Description

  * Old Status: pending
  * New Status: pending\_review
  * pending\_review will now indicate checks awaiting approval.
</Update>

<Update label="July 30, 2024" tags={["features","console"]} rss={{ title:"Returning and Voiding Wires via Console" }}>
  ### Returning/Voiding Wires Capabilities

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

  <Info>
    For some banks that support sending Treasury Prime notifications about wires being rejected, the process of voiding an outgoing wire is already automated.
  </Info>

  **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 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.
</Update>

<Update label="July 29, 2024" tags={["fixes","api"]} rss={{ title:"International ID Numbers and Check Status" }}>
  ### 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.
</Update>

<Update label="June 21, 2024" tags={["announcements"]} rss={{ title:"New Documentation Page Launch" }}>
  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.
</Update>

<Update label="June 7, 2024" tags={["fixes","api"]} rss={{ title:"RDC API and Account Closure Updates" }}>
  ### 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.
</Update>

<Update label="June 7, 2024" tags={["features","api"]} rss={{ title:"Returning Incoming ACH and Invoice Numbers" }}>
  ### 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.

  ### 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
</Update>

<Update label="April 17, 2024" tags={["fixes"]} rss={{ title:"Prime Data JSON Format Fix" }}>
  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.
</Update>

<Update label="February 21, 2024" tags={["fixes"]} rss={{ title:"Various Platform Fixes" }}>
  * 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.

  <Info>
    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.
  </Info>

  * 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.
</Update>

<Update label="January 22, 2024" tags={["fixes","features"]} rss={{ title:"Statements and ARC SEC Code Support" }}>
  ### 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.
</Update>

<Update label="January 8, 2024" tags={["fixes","features"]} rss={{ title:"Statements, 1099-INT, and KYC Updates" }}>
  ### 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.

  <Info>
    Please note that this change is backwards-incompatible.
  </Info>

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

  <Info>
    Third-party KYC evaluation submission is currently only available to certain organizations.
  </Info>

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