PayConexDecryptxShieldConexTECS
Release Notes
Request SandboxContact Us
Back to All

PayConex - 08.13.2026

about 2 hours ago by Ryan Cox

In this release, we’ve focused on Checkout Component payment method improvements, stronger card-data validation, Chase Paymentech settlement flexibility, and a set of processor, receipt, and UI fixes informed by merchant and integrator feedback. Below is a summary of the key updates included in this release.

Key Updates and Enhancements

Checkout Component — saved ACH payment methods

Merchants can now load a customer’s previously saved ACH payment token into the Checkout Component alongside saved cards. Customers can select a stored bank account from their Saved Payment Methods list, confirm the account details, and complete checkout without re-entering ACH information.

Card expiration validation

PayConex now validates card expiration dates earlier in the tokenization and transaction processing workflow. Invalid expiration values—such as non-numeric data, unsupported formats, or invalid months—are rejected early across affected card-entry flows, reducing failures later in tokenization, 3-D Secure initialization, or sale/auth processing.

Chase Paymentech settlement method flexibility

Chase Paymentech accounts with auto-settlement enabled can now select API or FILE settlement independently of the preferred settlement time. API settlement is supported at any auto-settlement hour, so merchants can keep their existing end-of-business schedules while PayConex routes settlement through the correct method.

Transaction source recognition

Transactions submitted by the nopCommerce Plugin are now recognized as a valid transaction source in PayConex. Transaction history and details display nopCommerce Plugin instead of unspecified, making it easier to identify where those payments originated.

Bug Fixes

Checkout and payment APIs

  • Expired reusable cards in Checkout. Selecting an expired reusable card in the Checkout UI again prompts for updated card information (such as a new expiry date) instead of skipping ahead in the flow.
  • Unicode / emoji characters in V4 requests. Fixed a server error that could occur when certain V4 payment fields (including extTransactionId) contained emoji or other Unicode characters.
  • Click to Pay with empty Address Line 2. Using a Click to Pay token in a transaction no longer fails with an internal server error when billing Address Line 2 is empty or null.

Processors and settlement

  • Missing batch dates after successful batching. Fixed an issue where some successfully batched transactions were missing a batch date in PayConex, which could affect UI display, reporting, and reconciliation.
  • FIS batch settlement totals. Corrected batch total and transaction count reconciliation for FIS settlements so voids, refunds, credits, and related transaction types are handled consistently when closing batches.
  • PTS settlement matching. Improved PTS settlement acknowledgement matching by amount and related fields, reducing settlement failures caused by amount-format and matching issues.
  • PTS long EMV TLV data. Device transactions on PTS with TLV data longer than 999 characters now process correctly instead of failing.
  • Elavon device-store transactions. Resolved an exception that could occur when running Elavon device-store transactions.

Receipts and PayConex UI

  • Blank email receipts. Fixed an issue where certain accounts could send email receipts with a blank body, so recipients again see expected transaction receipt details.
  • Session timeout on processor settings. Corrected the session timeout / 2FA dialog behavior when accessing processor settings after a timed-out UI session.

We appreciate your feedback and continued support. If you encounter any issues or have questions regarding this release, please contact our customer service team at [email protected].