POS 2026.3.0

Production Release: July 30, 2026

What's New

Administrator Applications

Merchant Reference Support for NIC Device Payments

Now Tyler Payment Processing device payments can pass through a merchant-supplied unique reference so it's included with the order sent to the payment device, making it easier to match transactions on the processor's side. If no reference is supplied, the transaction ID is used automatically, so no behavior changes for existing integrations.

(POS-3075)

Chase Direct and CommerceHub Processing Improvements

Payment processing for ChaseDirect and CommerceHub transactions has been streamlined to improve reliability when service fees are involved, with no change to how payments appear or complete for users. Payment transactions processed through CommerceHub and Chase Direct now include the last four digits of the card in the transaction result, in addition to the existing card details already being provided. Card brand, cardholder name, and masked card number continue to be included as before.

(POS-3225, POS-3322)

Linked Service Fee Transaction Records

Service fee transactions are now linked to their related primary transaction in Taipei's transaction log, making it easier to trace and reconcile fee activity across all supported processors (Chase, Chase Direct, CommerceHub, Monetra, and NIC). Payments without a service fee are unaffected.

(POS-3267)

Automatic Payment Platform Detection for POS Devices

POS devices now automatically detect the payment processing platform they're connected to and route transactions accordingly, with no configuration needed.

• Newer devices are automatically recognized and process payments through the updated platform, while existing devices continue working exactly as before.
• If a device can't be reached or its platform can't be determined, payments continue processing through the existing system with no interruption to service.
• This change is fully backward compatible, so older devices and system versions are unaffected.

(POS-3284)

Increased Chase Worldline Connection Timeout

Devices updating with Chase host settings now get more time to establish a connection, reducing the chance of timeout errors in the field. Existing merchants will automatically receive the updated timeout on their next merchant update, with no action needed.

(POS-3324)

Chase Direct Service Fee Reliability Improvements

Chase Direct card transactions that include a service fee now complete correctly instead of failing with errors or unexpected prompts, including fixes for rejected payments, incorrectly reported failures, and an unnecessary cardholder prompt to approve the service fee amount. Additionally, when a service-fee payment fails to switch the device to the fee merchant's credentials, the primary transaction is now automatically canceled instead of proceeding with an incomplete payment, and when a payment fails partway through after the main charge succeeds, the original charge is now automatically canceled so customers are never left with an unexpected hold on their account.

(POS-3372, POS-3373, POS-3409)

Fixed Issues

Jira issue #	Detailed description	What changed	Expected results
POS-3211	NIC device payment timeouts were previously surfaced as a confusing, unhandled error instead of a clear timeout message.	When paying with a NIC device, if the device takes too long to respond, you'll now get a clear timeout message instead of a confusing error, so you know right away that the transaction didn't go through and can retry or try another payment method.	When a NIC device times out during payment processing, the error returned to the caller clearly indicates a timeout occurred; no AggregateException wrapping TaskCanceledException surfaces to callers; non-timeout exceptions from NIC device calls continue to propagate as before.
POS-3261	Chase Direct Lane 3600 devices were incorrectly flagged as signature-capable, triggering an unnecessary signature prompt after successful payments.	Signature capture on Chase Direct Lane 3600 devices has been corrected so cashiers are no longer prompted to capture a signature after a successful payment. Lane 3000 and Link 2500 devices, along with Lane 5000, Lane 7000, and Lane 8000, continue to behave as expected.	A cashier using a Chase Direct Lane 3600 is not prompted for a signature after a successful payment; GetDeviceCapabilities returns SIGNATURE = false for a Lane 3600 device; signature capture continues to work correctly on Lane 5000, Lane 7000, and Lane 8000 devices.