Payments Platform 2026.3.4

Production Release: August 27, 2026

What's New

Administrator Applications

Historical Data Load

Historical order data has been fully reprocessed across the Order History search indexes and flat reporting tables, with each month verified complete before the next month loads, ensuring reporting data is accurate and complete.

(PPR-1190)

Order Exports

PayOps Admin users can now export orders directly from the Orders page as Order Detail, Order Item Detail, or Order Summary. Exports can be downloaded or emailed in CSV, text, Excel, PDF, or Word format, and automatically reflect the current filters, search terms, and active tab on the Orders page.

(PPR-1462, PPR-1463, PPR-1475)

Reporting Engine Enhancements

Reports now read from new flat reporting tables for improved accuracy and performance, with corrected Net Revenue cost-of-sale calculations and disbursement reporting now based on effective date. Report data is also scoped by portal, merchant, or service selection, so users only see data for the merchants and services they have access to.

(PPR-1497, PPR-1498, PPR-1499)

Scheduled Payments Effective Date

Scheduled ACH payments now capture and expose their effective settlement date in payment reporting data and the Order History search index, giving visibility into when a scheduled payment will settle.

(PPR-1503)

Checkout Frontend Modernization: Angular 21 and Forge 3.0

Redirect Checkout has been upgraded from Angular 11 to Angular 21, migrated from Forge 1.0 through Forge 3.0, and moved off the deprecated @angular/flex-layout library onto native CSS Flexbox. This is a frontend framework modernization with no intended change to checkout behavior or appearance — full end-to-end regression testing (desktop and mobile, all iframe providers, all payment modes, all major settings/feature flags) confirmed no regressions.

(CHOUT-2598, CHOUT-2601, CHOUT-2602, CHOUT-2603, CHOUT-2604, CHOUT-3664, CHOUT-3807, CHOUT-3808)

Consistent Confirmation Numbers for Chase Batch Closing

We tested end to end to confirm that the confirmation number a payer sees after a card payment stays exactly the same after batch closing. Previously, the reference number could change once a payment moved from authorized to captured during batch close, making it harder to match a payer's confirmation number to records in Chase. Now that number stays consistent from authorization through capture, refunds, and reporting, so support agents and payers can rely on it to match transactions in both TP Admin and Chase without ambiguity.

(CHOUT-3845)

Anonymous Cart Merging on Cross-Application Handoff

Anonymous shoppers no longer lose items previously added when arriving from another application.

(CHOUT-3905)

Phone Payments Respect Billing System Payment Method Restrictions

Phone (IVR) payments now respect payment-method restrictions set by the billing system, so callers are only offered the payment methods allowed for their bill.

(CHOUT-3955)

Automated Security Scanning for Payment Operations Admin and Platform Admin

We've strengthened security monitoring for Payment Operations Admin and Platform Admin by setting up automated vulnerability scanning. Both applications now undergo regular automated security scans to proactively detect and address potential vulnerabilities, helping ensure a safer experience.

(MERCH-1813, MERCH-1960)

Order Action Buttons in Platform Admin

Platform Admin users can now view and manage refunds, returns, and cancellations directly from order details, with actions shown only when they're actually available.

• Cancel, Refund, and Return buttons now appear only when an order is eligible for that action, so users no longer have to guess whether an action will succeed.
• Refund and Return buttons are automatically hidden once an order has been fully refunded or returned.
• Button visibility now respects each user's role (Admin, Operator, or Viewer), ensuring Viewer-role users cannot see or access these actions.
• Improved keyboard navigation, screen reader support, and readability at higher zoom levels for order action buttons.

(MERCH-1847)

Pinned Headers and Filters Across User Management Lists

User Management lists now stay easy to navigate no matter how far you scroll.

• On the Users, Role permissions, and Audit report lists (Payment Operations) and the Users and Groups lists (Payments Implementation), the header and filter row stay pinned in place as you scroll through results, so you can adjust filters or get your bearings without scrolling back to the top.
• The paginator and rows-per-page control stay fully visible and usable at every page size.

(MERCH-2019)

View Redirect Checkout Batches and Batch Details

Internal Tyler implementation users can now view a list of Redirect Checkout payments batches for a workspace directly in the Payments Implementation Admin, making it easier to confirm a batch exists, check whether it's still open, and locate a specific batch to investigate.

• A new Batches page lists batch ID, close date, status, and amount for the workspace in context, covering online and IVR Redirect Checkout payments.
• Batches can be searched by payments batch ID, source system batch ID, or amount, and all columns can be sorted, with the list sorted by close date (most recent first) by default.
• Selecting a batch opens its detail page, and returning to the list restores your previous position, page size, sort, and search.
• Clear messaging is shown when a search has no matches, when a workspace has no batches, or if the list fails to load, with an easy way to retry or clear the search.
• The batch details view shows the Batch ID, close date, status, and amount, matching what's shown on the Batches list.
• A Source batches section lists every source system batch included in the payments batch, along with each one's own identifier, originating source system, and status, which may differ from the payments batch status.
• If a payments batch has no source batches, a clear message is shown instead of leaving the section empty.
• If batch details or source batch information can't be loaded, an error message with a retry option is shown instead of blank or placeholder data.

(MERCH-2035, MERCH-2036)

Users Tab in Payments Administration

The Users tab now shows exactly who has access to Payments Administration for a workspace and what role each person holds, so admins can review access at a glance without being able to change anything from this view.

• Each user's name, email, and role chip(s) are listed based on the groups that grant them access — users with no group access simply don't appear.
• Adding a new user or assigning groups links out to the appropriate admin tools rather than being handled on this read-only tab.
• Helpful messaging is shown when a filter has no matches, when no groups have granted access yet, or if the list fails to load (with a way to retry).
• The list supports sorting, pagination, and remains accessible via keyboard and screen reader.

This release also lays the groundwork for a new, group-based way of managing user permissions, making it easier to control who can access what without having to configure access for each person individually.

(MERCH-2045, MERCH-2052)

TPE Admin Username for User Syncing

When adding a new user, Payment Operations Admins can now enter that person's Tyler Payment Processing Admin username directly, ensuring the system matches the correct account even when the username doesn't match their email address.

• The "Add a new user" dialog now includes a required "TPE Admin username" field alongside the Email field.
• This username is used going forward for account verification and keeping user roles and merchant assignments in sync.
• The Edit User page displays the username for reference (read-only).
• If the entered username doesn't match a TPE Admin account, an error is shown and the user won't be created.

(MERCH-2055)

Merchant Hierarchy Filter in Platform Admin Orders Search

You can now filter the Orders list by merchant hierarchy in the Advanced search panel on Payments Platform Admin.

• Expand and select from a tree of merchants and services, choosing multiple entries at once, then apply the filter to narrow the Orders list to just those results.
• The tree only shows the merchants and services you have access to, so you always see a view scoped to your permissions.
• A filter chip shows how many merchant hierarchy nodes you've selected; click the chip to review or adjust your selection, or click its X to clear it.
• If the merchant hierarchy fails to load, you'll see a clear error message and can still use the rest of the advanced search filters without losing your other selections.

(MERCH-2087)

Updated Page Headers in Payments Implementation Admin

We've updated the page headers you see after selecting a tile from your Payments Implementation Admin dashboard so they match the tile's new name, keeping the app consistent from start to finish.

• Selecting Assign merchants now opens a page titled "Assign merchants" (previously "Merchant scope")
• Selecting Configure checkout now opens a page titled "Configure checkout" (previously "Checkout settings")
• Selecting Connect systems now opens a page titled "Connect systems" (previously "Systems integrations")
• Selecting Payment workspace settings now opens a page titled "Payment workspace settings" (previously "Reconciliation portal setup")
• Selecting Review orders and reports now opens a page titled "Review orders and reports" (previously "Orders and reports")

(MERCH-2091)

Descriptive Browser Tab Titles in Payments Administration

Browser tabs and screen readers now show which page you're on in Payments Administration, making it easier to navigate when you have multiple tabs open or are using assistive technology.

• Each page—Home, Users, Groups, and individual group detail pages—now displays its own title, such as "Home - Payments Platform Administration" or "Disbursements - Payments Platform Administration," instead of the same generic title everywhere.

(MERCH-2095)

Accessibility Improvements for the Groups Table

Screen readers can now identify every column in the Groups table, including the ones without filter controls, so no headers are left blank or unannounced while navigating.

• The Members and actions column filter headers now announce that no filter is available for that column, instead of being silently skipped.

(MERCH-2097)

Default Sort Order for the Users Audit Report

The Users audit report in Payment Operations Admin now sorts by newest activity first when you open it, so you can see recent entries right away without re-sorting. Your sort choice is remembered as you navigate away, return, or clear filters, and you can still click any column header to sort differently at any time.

(MERCH-2108)

Payer Applications

Improved Automated Test Reliability

We're continuing work to keep our automated Payments Enterprise Portal test suite reliable and accurate, addressing tests that were failing due to outdated payment history data as well as tests failing for unrelated reasons, so we can improve the overall reliability of our quality checks.

(TEBPP-9004, TEBPP-9040)

WalkMe Configuration Option

We've made it possible to disable WalkMe pop-ups and tooltips on a per-portal basis across our administrator applications, so users no longer have to dismiss unwanted guided-tour prompts when visiting a page.

(TEBPP-9175)

Batch Integration Admin Framework Upgrade

Batch Integration Admin has been upgraded to the latest version of our underlying design framework, keeping the application secure and consistent with the rest of the platform. All existing functionality works the same as before.

(TEBPP-10645)

Disaster Recovery Protections for Notifications and Imports

We've strengthened protection against data loss during disaster recovery failover. Billing account notifications sent to external systems, and items processed through Open Accounts Receivable's Full Replacement import, are now safely tracked and retried until confirmed — and any notification that's delayed too long is automatically resent — so no data is lost and your systems stay in sync even during a failover.

(TEBPP-12050, TEBPP-12051, TEBPP-12091)

Disaster Recovery Improvements for Search Infrastructure

We've made disaster recovery more reliable by automating a key step in the failover process for our search infrastructure, including a new automated workflow that stops replication on the failover search instance during a disaster recovery event.

(TEBPP-13386)

Updated Local Development Database Backups

We've refreshed the sample databases provided for local development so they stay in sync with the latest database migrations, ensuring your local environment matches production behavior. Restoring from the provided backups now correctly applies all subsequent migrations, and updated dumps are available for all databases, including Billsearch.

(TEBPP-12100)

Configurable Bill Presentation Options

You can now declare whether an external system supplies bill PDFs or structured bill detail data, and configure how each integration service presents bills to payers — as a PDF from your billing system, as a bill rendered from your data, or with basic bill values only. Only one presentation option can be active at a time, and each is available only when the connected integration supports it; existing integration services keep their current behavior after this update.

(TEBPP-13002, TEBPP-13343)

Feature Flag Cleanup: Batch Export

Batch export functionality is now permanently enabled and works consistently every time.

(TEBPP-12909)

Fixed Feature Flag Evaluation on Global Portal

We fixed an issue where feature flags could incorrectly appear disabled when accessed from the global portal without a tenant selected. Bill Search Admin and Batch Integration Admin now correctly evaluate the flag's default setting in this scenario, instead of always treating it as off.

(TEBPP-13352)

Permission-Based Visibility for Payments Administration

Payments Administration now respects your access permissions, so you only see options you're actually allowed to use. If you don't have access to Payments Administration, the Transaction history and Reconciliation tiles no longer appear in the Quick Actions grid, and the Payments Administration section of the sidebar is disabled — with no brief flash of options you don't have access to.

(TEBPP-13373)

Antivirus Engine Update

Updated our ClamAV virus scanning engine in both the scanner and updater components to version 1.4.6.

(TEBPP-13375)

Automated Unit Testing in Build Pipeline

We've strengthened our automated testing process to help catch bugs earlier and improve overall reliability. Unit tests for select internal tools are now automatically run and verified with every build, so any issues are caught before they can affect your experience.

(TEBPP-13380)

Fixed Issues

Jira issue #	Detailed description	What changed	Expected results
PPR-1466	Reporting data sync could report success even when a batch of transaction data failed to save to the reporting database, causing reports to silently miss transactions.	Reporting data sync now returns an error instead of a success response when a batch of transaction data fails to save to the reporting database, so the sync retries the batch rather than dropping it.	A failed batch write is retried and results in a non-success response, so reporting data is no longer silently missing transactions.
PAYSD-23928	The Checkout API's PaymentReconciliationDetails endpoint returned error responses (400 and 404) as plain text instead of the structured error format documented for the endpoint, which could cause deserialization failures for integrators such as Records Management.	Both the 400 and 404 response paths now return a structured error object consistent with the endpoint's published API specification, and the OpenAPI/SDK documentation reflects the change.	A paymentId that hasn't reconciled or doesn't exist returns 404 with a JSON ApiError object ({message, isError, requestId}), not a bare string. BadRequest scenarios return 400 with the same shape. Fully reconciled payments still return 200 with the unchanged ReconciliationDetailResponse body.
PAYSD-24474	Some payments with an unconfirmed processing outcome could be shown as Declined even though they had processed successfully, prompting payers to attempt duplicate payments.	Payments whose gateway response outcome can't be confirmed are now recorded as a Communication Error with a Processor Timeout status instead of Declined.	An unreadable or absent gateway response is recorded as Processor Timeout, not Declined. The payer sees messaging that the charge may take a day to appear, with no retry option and no receipt email. A payment with both a declined and an unconfirmed transaction reports the unconfirmed outcome, not Declined. Genuine processor declines are unaffected.
TEBPP-13322	The paperless billing enrollment dialog incorrectly flagged an existing masked/hidden email address as invalid even when it hadn't been changed.	Existing masked email addresses no longer trigger validation errors unless they are actually edited. If you do update a saved email address, it will still be checked to make sure it's in a valid format.	A hidden/masked email address that has not been changed does not fail validation. An email that has been saved and is modified is validated for proper format.
TEBPP-13348	CheckFreePay voucher emails rendered a literal {paymentItemHeader} placeholder above the item list, and the voucher payment receipt email included an incomplete sentence claiming the payment would appear on a card or bank statement.	The voucher-creation email now correctly displays the "Description / Amount" header instead of a placeholder, and the voucher capture receipt email no longer includes the incorrect account-statement sentence, since voucher payments don't work that way.	The voucher-creation email contains no literal placeholder text. The voucher capture receipt email contains no account-statement sentence or "ending in" fragment. Card and eCheck receipt emails are unaffected and still read "…for your {brand} ending in {lastFour}."
MERCH-2099	Filtering by "Today's date" on Orders and Reports could return records from the wrong day when a user's time zone preference didn't match the system time zone.	Filters that used "Today's date" on Orders and Reports could return records from the wrong day if your user time zone preference didn't match your computer's system time zone, sometimes including yesterday's records even though the filter chip showed "Today's date." Date filtering now correctly accounts for your time zone so results are consistent no matter where you're located.	Filters generate results based on the user's time zone and convert to UTC before querying TPE. Filter results are correct, and a "Today's date" filter returns the same records regardless of the timezone of the machine running the query.
MERCH-2122	Certain feature flag checks could return an incorrect default value instead of properly evaluating the flag, which could cause features to behave unexpectedly.	We fixed an issue where certain feature flag checks could return an incorrect default value instead of properly evaluating the flag, which could cause features to behave unexpectedly. Feature flags are now evaluated correctly and consistently across all scenarios.	The Harness FME UI reports traffic for enablePaymentsMaintenanceModeCheck, and no "FME returned 'control'" logs are generated after visiting PayOps.