Payments Platform 2026.3.3

Production Release: August 24, 2026

What's New

Administrator Applications

Line-Level Refunds in Payments Administration

Payments Administration now supports refunding individual line items within a Chase- or Fiserv-processed payment — for example, refunding a single tax penalty line rather than an entire assessment — when a transaction has more than one distinct charge type. The refund dialog displays an expandable breakdown of line items for eligible transactions, with each line showing its own remaining refundable amount after accounting for any prior partial refunds.

(CHOUT-3735)

Itemized Fee Breakout on the Payment Method Page

Tyler Payments now displays the itemized fee breakout (Convenience Fee, Service Fee, Technology Fee) on the payment method selection page for portals with fee breakout enabled, consistent with the itemized breakdown already shown on the pre-payment summary and post-payment receipt. Previously, this page showed only a single combined "Processing Fee" line, creating a brief inconsistency between the summary and receipt screens surrounding it.

(CHOUT-3948)

Cleaner Payment Method Selection When Switching Back to Pay Now

Switching the payment schedule back to "now" now presents a clean payment-method choice instead of keeping a previously made selection.

(CHOUT-3812)

Anonymous Cart Persistence Across Domains

Shoppers who have not signed in now keep their cart as they move between your Tyler payment applications, so items added in one place are still waiting for them when they reach checkout on a related site — no more starting over or landing on an empty cart. The cart also stays private to the shopper's own session and can no longer be read by other scripts running in the browser. If your organization uses the .NET Framework Checkout SDK (tp-checkout-api-net-sdk), your development team needs to make a small update before carts will carry over this way — see the SDK's updated documentation for details.

(CHOUT-3899, CHOUT-3901, CHOUT-3902, CHOUT-3903, CHOUT-3904)

PayPal and Venmo Support Through Braintree

Redirect Checkout's PayPal and Venmo sessions through Embedded Checkout now always use Braintree as the payment processor, replacing the previously hard-coded PayPal Managed Path. This is a backend routing change with no visible impact on the PayPal or Venmo payment experience, and it has been validated end to end.

(CHOUT-3852, CHOUT-3909)

Complete Reporting Data with Automatic Parity Checks and Replay

Payments Reporting now confirms on its own that every transaction message sent from the payment engine has arrived. A check runs every 30 minutes, identifies any messages that are missing from reporting data, and replays them automatically so your reports show the complete picture. Replays draw from the replication copy first and fall back to the source payment system when that copy does not have the data, and in-flight replays finish before the same records are requested again. Missing transactions are filled in without a manual request.

(PPR-1314, PPR-1315, PPR-1316)

Time Zone Support in Order History Searches and Exports

Order History searches and exports now return dates in the time zone you request, so results line up with your local business day instead of requiring conversion. The requested time zone applies consistently to dates in nested fields and to the filter criteria you search on, and requests that do not specify a time zone default to UTC.

(PPR-1457)

Groundwork for Order Exports

Order History now retains the detail that upcoming order exports will deliver, including each order's merchant and service descriptions, gross revenue, cost of sale, profit/loss, payment instrument type, masked account number, and customer name, along with a record for every line item. This information is organized into month-based indexes with expanded storage capacity so the full order and item export history remains available.

(PPR-1461, PPR-1476)

Faster Reports and Merchant Hierarchy Filtering

Report queries now run against a dedicated read-only copy of the payments reporting database, so running reports no longer competes with incoming payment data and results return more consistently. Payments Reporting also keeps its own copy of the merchant hierarchy and its merchant, service, and portal codes, so a report filtered on a parent merchant resolves every merchant and service beneath it in a single lookup and reads only the data it needs.

(PPR-1337, PPR-1447)

Individually Attributable Database Access

Access to the payments reporting database now uses individual named accounts scoped to read-only or read-write permissions rather than shared administrator credentials, and supports IAM-based database sign-in in every environment alongside existing credentials. Every session is attributable to a single person, strengthening auditability of the data behind your reports.

(PPR-1338)

End-to-End Validation of Reporting Changes Before Release

Payments Reporting generates synthetic payment activity in a test-only environment and runs it through the full reporting pipeline, so changes are verified end to end before release without using production data.

(PPR-1477)

Hierarchy-Based Access and Permissions

Access permissions are now determined by a user's position within your organization's hierarchy, so the access granted at a parent level applies consistently to everything beneath it. Permission checks across the hierarchy are also faster and more reliable, so users see the correct access to entities and their related records right away — including immediately after your hierarchy or a user's permissions are updated. The result is more predictable, dependable control over what each user can view and do in Merchant Services.

(MERCH-2029, MERCH-2031)

A Single Source for Organization and Entity Hierarchy

Applications across the platform now retrieve organization and entity hierarchy information from a single shared source. This keeps the entities you see consistent from one application to the next and ensures changes to your organization's structure are reflected right away, without the delays or mismatches that could previously occur. Merchant account and hierarchy details are also handled more consistently wherever you work with them, improving reliability and performance and laying the groundwork for future enhancements to merchant management.

(MERCH-2030, MERCH-2034)

Permission Management for Payments Administration

Payments Administration now includes dedicated permission management support. This groundwork enables more precise control over what each user can access and do within the application, helping organizations align access with staff responsibilities and keeping sensitive payment functions limited to the right people as the capability rolls out.

(MERCH-2053, MERCH-2056)

Multi-Environment Support

Payments Administration now identifies your workspace directly from the environment you are working in. If your organization uses more than one environment, you automatically see the correct workspace and its data when you sign in, without needing to select or switch it manually. Platform Administration also supports multiple environments, so you can work across separate environments — such as testing and production — without a separate setup for each, making it easier to validate configuration changes safely before applying them to live operations.

(MERCH-1962, MERCH-2076)

Configurable Homepage Tiles in Platform Administration

Feature flags now control the visibility of homepage tiles in Platform Administration, so tiles can be turned on or off for your organization without requiring a software update. This gives you a homepage that shows only the tools relevant to your team and allows new functionality to be introduced gradually as it becomes available.

(MERCH-1977)

Mark Returns and Chargebacks as Reverse Returned

Transactions with a type of Return or Chargeback can now be marked as reverse returned, giving you a clear way to record when previously returned or disputed funds have come back. The action is available for both default and SKU-based processor configurations, so transaction statuses stay accurate without manual workarounds or offline tracking.

(MERCH-1992)

Resolve or Pend Net Disbursement Exceptions

Merchant Services now includes the latest options for handling net disbursement exceptions, so you can resolve an exception or place it in a pending state directly from the exception itself. This gives you a clearer path to clear out exceptions that are ready to be closed while setting aside the ones that still need review, without leaving items in limbo.

(MERCH-2002)

Blocking and Unblocking Payment Accounts

Merchant Services now uses the latest updates for blocking and unblocking a payment account, keeping this capability aligned with current platform behavior. Administrators can continue to block a payment account to stop further activity on it and unblock it when activity should resume, with more consistent and reliable results.

(MERCH-2003)

Pinned Headers and Filters in PayOps Admin Lists

The page header and filter controls now stay in view while you scroll through Product Support and Key Management lists in PayOps Admin, so you no longer lose sight of your search and filter selections while reviewing long lists. Scrolling also happens across the full page rather than inside a smaller inner panel, making it easier to move through large sets of records and confirm which filters are applied at any point.

(MERCH-2015, MERCH-2020)

Refreshed Navigation, Dashboards, and Terminology

The Payments Platform navigation portal has been updated, making it easier to find and move between the applications and tools available to you. The Payments Implementation Admin dashboard now features updated Tyler branding for a consistent, modern look that matches the rest of the Payments Platform, and the PayOps dashboard uses clearer, more consistent wording:

• Menu item labels — including "Manage users," "Advanced operations," "Orders and reports," "Manage encryption keys," and "Change logs" — now follow consistent capitalization.
• The merchant management description now reads "Manage merchants, services, processors, banking, and related settings."
• The omnibar entry for this area is now labeled "Payment Operations Admin" to more clearly identify it.

(MERCH-2026, MERCH-2040, MERCH-2060)

Stronger Security Scanning and Platform Maintenance

We've added automated security scanning to the development process for Merchant Services administrative applications. Code is now continuously checked for potential vulnerabilities and exposed credentials before it reaches you, helping us identify and resolve security concerns earlier and keep your payment data better protected. We've also made behind-the-scenes maintenance updates to internal development documentation — this doesn't change any functionality you'll see in the product, but it helps our teams build and deliver future improvements more consistently.

(MERCH-1961, MERCH-2072)

ROAM Parity for Tandem Devices

Tandem devices now support the same payment capabilities in Tyler Payment Processing that were previously available only with ROAM devices. Staff get a consistent payment experience no matter which device they use, and offices moving to Tandem hardware can do so without giving up existing functionality.

(POS-3480)

Payer Applications

Form Batch Export

Form batch export is now available in Payments Enterprise Portal. A new configuration page in the global portal lets you set up and manage batch export of forms, so you can pull form submissions out in bulk instead of retrieving them one at a time.

(TEBPP-12907)

Risk Threshold Presets in Payment Settings

Payments Enterprise Portal now supports the standard "Default," "Elevated," and "High" risk threshold presets used across other Tyler Payments products, so administrators can apply a consistent level of payment security protection without configuring numeric values by hand. The selected preset is applied at the payment settings level and is honored by every form that uses those settings, with the "Default" level applied automatically when no preset has been chosen.

(TEBPP-13113)

Blocked Payment Method Support

Payments Enterprise Portal now recognizes blocked payment methods. When a payer attempts to pay with a tender that has been blocked, the portal identifies it and prevents the payment from moving forward, so payers get clear feedback up front instead of encountering an unexplained failure later in the process.

(TEBPP-13359)

Performance, Batch Integration, and Fuzzy Search Improvements

This release includes performance and usability enhancements across the portal: overall system performance has been improved for faster page loads and quicker response times, batch integration is more reliable and efficient when processing batched transactions, and new fuzzy search lets you find records even when your search terms are only a partial or approximate match. Bill search and checkout also provide clearer insight into how system resources are used while each request is processed, making it easier to pinpoint and address slowdowns in these frequently used areas.

(TEBPP-13260, TEBPP-13351)

Performance Metrics for Payments Administration

Payments Administration now tracks performance metrics as you work in the application, giving Tyler visibility into how quickly pages and actions respond. This insight helps identify slow areas so responsiveness improvements can be prioritized and delivered in future releases.

(TEBPP-13102)

Dashboard and Bill Search Administration Modernization

The Payments Enterprise Portal dashboard now runs on the latest supported version of its underlying application framework, with a modernized layout that displays more consistently across different screen sizes and browser window widths — so cards and content align predictably whether you are working on a desktop monitor, laptop, or tablet. Pages load faster and the dashboard sits on a currently supported foundation for improved long-term stability and security. The Bill Search administration screens have also been updated to the latest version of our shared user interface framework, bringing refreshed components, improved accessibility, and better consistency with the rest of the portal. No changes are required on your part, and existing features continue to work as before.

(TEBPP-10642, TEBPP-13310, TEBPP-13358)

Automated Dependency and Security Scanning

Payments Enterprise Portal now uses automated dependency monitoring to continuously check the third-party components it relies on for known security vulnerabilities and outdated versions. Known vulnerabilities are identified and flagged as soon as they are published, so updates can be reviewed and applied promptly. This strengthens the ongoing security of the portal and helps keep the platform current with the latest security fixes, with no change to how you use the application.

(TEBPP-13306, TEBPP-13309)

Antivirus Engine Updates

The ClamAV antivirus engine used by the portal's file scanning and update services has been upgraded to the latest releases, keeping uploaded file scanning current with the newest virus detection capabilities.

(TEBPP-13294, TEBPP-13375)

Improved Platform Monitoring and Resilience

Monitoring behind Payments Enterprise Portal has been enhanced so system activity is tracked with greater consistency and detail, giving our teams clearer visibility into performance and health across the application. Health monitoring has also been improved so the platform can more accurately detect and report the status of its services, helping the system respond faster and shift traffic away from an unhealthy region during a service disruption. Together these changes support more reliable uptime, smoother recovery, and quicker resolution of issues.

(TEBPP-12046, TEBPP-13274)

Expanded Automated Test Coverage

Automated testing coverage has been expanded across the portal, including a broader set of checks for the NIC configuration, consistent internal identifiers for banner and page custom content areas, coverage for the Tyler Content Manager Form Services integration, and coverage for configuring payment notification recipients on forms. Each release now runs through more automated validation before it reaches customers, helping catch display and functional issues earlier and supporting more consistent, reliable behavior in the portal.

(TEBPP-9359, TEBPP-9729, TEBPP-13279, TEBPP-13290)

Fixed Issues

Jira issue #	Detailed description	What changed	Expected results
CHOUT-3873	In Embedded Checkout, the payment amount sent for Google Pay, Apple Pay, PayPal, and Venmo omitted the applicable convenience or service fee. Separately, the configured eCheck (ACH) amount counted the base payment amount twice.	Resolved an issue in Tyler Payments' Embedded Checkout integration where the payment amount sent to Embedded Checkout for Google Pay, Apple Pay, PayPal, and Venmo omitted the applicable convenience or service fee, which could cause a $0 payment with a fee to fail to load and could undercharge the displayed amount for non-zero payments. Also resolved an issue where the configured eCheck (ACH) amount was calculated with the base payment amount counted twice, which did not affect the amount actually charged but produced an incorrect configured amount and a recurring log warning.	All Embedded Checkout payment methods compute the fee-inclusive total consistently, $0 payments with a fee load correctly, and the configured eCheck amount is accurate.
CHOUT-3875	In Payments Administration, tender-type dropdowns displayed each configured option twice immediately after a new payment settings record was created and saved.	Resolved an issue in Payments Administration where, immediately after creating and saving a new payment settings record, the tender-type dropdowns (Credit Card, eCheck, Apple Pay, Voucher, PayPal, Google Pay, Venmo) would display each configured option twice. Reopening the record or refreshing the page was unaffected.	Tender-type dropdowns display each option once the first time a new settings record is saved, without needing to reopen or refresh the page.
CHOUT-3885	On the global portal view in Payments Administration, the Voucher option in the transactions list payment-method filter did not update when switching between portals.	Resolved an issue in Payments Administration where, on the global portal view, the Voucher option in the transactions list payment-method filter retained the previous portal's setting until a full page reload. An unrelated order-metadata display setting with the same underlying cause was also corrected.	Switching portals refreshes the Voucher filter option and the order-metadata display setting without requiring a page reload.
CHOUT-3927	In PIG Admin, global portal users could not apply a tenant using the tenant selector in the sidenav.	Resolved an issue in PIG Admin where selecting a tenant from the sidenav dropdown had no effect — the tenant was not applied, data lists remained unfiltered, and the page continued to display "Please select a tenant."	Global portal users can select, switch, and clear tenants as expected, with all tabs correctly filtered to the selected tenant.
CHOUT-3833	A browser console error occurred when loading the Auto pay tab of the Recurring activity view in Payments Administration.	Internal reliability improvements.	The Auto pay tab of the Recurring activity view loads without console errors.
CHOUT-3877	Feature flag lookups on the global portal with no tenant selected were evaluated against an empty portal identifier.	Internal fix — no customer-facing change.	Feature flags evaluate correctly on the global portal when no tenant is selected.
PPR-985	Canceling the Edit Columns drawer in Custom Reports did not reliably discard the changes made there, and the display total badge used an inconsistent color.	Canceling the Edit Columns drawer in Custom Reports discards all changes made there — column selections, reordering, restored defaults, and field settings like display totals and date ranges revert to their last saved state, and the display total badge now appears in blue.	After canceling the Edit Columns drawer, the report matches its last saved state with no column, ordering, or field-setting changes applied, and display total badges render in blue.
PPR-1241	Syncing a transaction that was not external could remove documents belonging to external transactions.	Syncing a non-external transaction no longer deletes external transaction documents; those documents are removed only when the sync targets an external transaction and its ID is missing.	Syncing a non-external transaction leaves external transaction documents intact. Documents are deleted only when the sync targets an external transaction whose ID is missing.
PPR-1432	In Payment Operations Admin, the order item section showed an Order Total of 0.00 instead of the actual amount, so it did not match the order section.	Payment Operations Admin shows the actual Order Total on the order item section for all payment types, including Apple Pay, credit card, ACH, and paper payments, instead of 0.00.	The order item section displays the actual Order Total for every payment type — Apple Pay, credit card, ACH, and paper payments — matching the value shown in the order section.
MERCH-1115	The Product Support tile listed portals that the signed-in user was not authorized to manage, including portals where the user was not a Corporate Admin.	The Product Support tile now respects your administrative access. When you open Product Support, the portal selector lists only the portals where you are a Corporate Admin, so you no longer see portals you are not authorized to manage.	Opening Product Support shows only the portals where you hold Corporate Admin access, making it faster to find the right portal and preventing confusion when selecting one.
MERCH-2008	The merchant hierarchy did not refresh after a new merchant was added, so the new merchant did not appear until the page was reloaded.	The merchant hierarchy now updates automatically as soon as you add a new merchant.	A newly created merchant appears in the correct place in the hierarchy right away, without reloading the page or navigating away and back.
MERCH-2085	In PayOps Admin, the selected location could be lost during sign-in, requiring users to reselect it before continuing their work.	Logging in to PayOps Admin now keeps your selected location in place.	After signing in, your previously selected location is still applied, so you can pick up right where you left off without reselecting it.
TEBPP-13094	In bill search, the autopay toggle appeared active even when autopay was not enabled on the associated payment setting.	The autopay toggle in bill search now reflects whether autopay is actually enabled for the associated payment setting, rather than appearing active regardless of that setting.	Users see accurate autopay status at a glance and can trust the toggle before making changes.
TEBPP-13344	In checkout, printing an already-paid voucher produced the voucher document instead of a payment receipt.	Vouchers that have already been paid now produce a payment receipt when printed, instead of reprinting the voucher document.	Printing a paid voucher returns the correct confirmation of payment for your records without needing to look it up separately.
TEBPP-13346	Accounts appeared to allow payment even when a block was placed on the only available payment method.	When an account's only available payment method is blocked, the payment is now correctly treated as fully blocked, and payers are no longer shown options that appear to let them continue when no usable payment method exists.	Payers receive clear, accurate messaging up front instead of encountering a failure later in the process. Accounts that still have another eligible payment method continue to work as before, including the existing credit card maximum messaging and the option to update the payment amount.