PayConexDecryptxShieldConexTECS
Release Notes
Request SandboxContact Us
Back to All

PayConex - 10.20.2026

about 9 hours ago by Ryan Cox

In this release, we’ve focused on Mastercard compliance for RapidConnect, Checkout Component refinements, and a set of processor, settlement, and UI fixes informed by merchant and partner feedback. Below is a summary of the key updates included in this release.

Key Updates and Enhancements

Mastercard TLID support for RapidConnect

PayConex now captures the Mastercard Transaction Link Identifier (TLID) from RapidConnect authorization responses and carries it into clearing. This supports Mastercard’s TLID mandate for RapidConnect merchants.

Account administrator control for External Transaction ID handling

Account administrators can now configure how PayConex handles duplicate external transaction ID values at the account level:

  • Reject Duplicate IDs (default)
  • Replay Original Response
  • Replay Approvals; Retry Failures

This gives integrators more control over idempotent request handling while keeping blocking mode as the default.

Custom reports — flexible field selection

Custom reports no longer require a fixed set of mandatory fields. Merchants can build simplified reports with only the columns they need (for example, transaction_id and transaction_amount), while recommended defaults remain pre-selected when creating a new report.

Custom report CSV output also now respects the report’s selected fields for RSAPI-related columns—enabling a field for RSAPI no longer forces that field into every custom report export.

Contactless CVM / CDCVM reporting

Cardholder verification method (CVM), including CDCVM, is now reported more accurately for contactless transactions across card brands.

TSYS device/POS profile assignment (QSAPI)

For TSYS transactions submitted through QSAPI, PayConex more reliably assigns the appropriate device and POS profile based on transaction characteristics, improving routing accuracy and compliance with TSYS requirements.

Bug Fixes

Checkout Component

  • Reusable payment methods visibility. Reusable card or ACH tokens are no longer shown when the related payment method is not included in the active Checkout Component allowedPaymentMethods configuration.

PayConex Hosted Card Inputs

  • Credit card field entry in PayConex UI. Fixed several card-entry issues across PayConex, Hosted Payment Forms, and eToken flows, including cursor/spacing behavior when editing card numbers, spaces being stripped on blur in some browsers, alphabetic characters accepted in expiry/CVV on Android Chrome, and paste via keyboard shortcut in Safari.

Processors and settlement

  • Elavon mobile wallet values. Elavon Google Pay and Apple Pay transactions now post the correct mobile wallet type and account entry mode values required by Elavon.
  • Elavon STORE / device-store exceptions. Resolved processing exceptions that could occur on certain Elavon STORE and device-store transactions.
  • Special characters in customer names. Improved handling for transactions with special characters in customer name fields that could fail to batch or block reissue with “Could not find reference transaction.”
  • PTS minimal sale/refund. Fixed failures on minimal Sale and Refund requests for PTS accounts.
  • Vantiv / FIS daily batch reconciliation. Corrected daily batch reconciliation scope and settlement-mode diagnostics so terminals opted out of unattended settlement are not incorrectly included, and force-close metadata is recorded more accurately.
  • EPIC partial approvals. Partial approval responses returned through the EPIC Proxy now include the approved amount (e_amount) in addition to the partial-approval indicator.

Security, boarding, and ShieldConex

  • Account boarding email preservation. When boarding a PayConex account, a caller-supplied email is now preserved when Salesforce does not provide a business email, preventing boarding failures caused by a missing email field.
  • ShieldConex error handling. Improved error handling when ShieldConex responses include missing or invalid fields, avoiding secondary exceptions during account/token processing.

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