PayConexDecryptxShieldConexTECS Platform
Release Notes
Request SandboxContact Us
Back to All

PayConex - 12.09.2025

about 1 month ago by Ryan Cox

In this release, we’ve introduced updates and enhancements across the PayConex platform—focused on Mastercard compliance, settlement throughput and clarity, and a set of fixes informed by customer support/merchant feedback. Below is a summary of what’s included.

Key Updates and Enhancements

Apple Pay browser support expanded

  • Apple Pay will now appear as an option on hosted payment forms (where configured) for customers using supported non-Safari web browsers, reflecting Apple’s updated browser support for Apple Pay. This allows more end users to complete payments with Apple Pay without switching browsers.

Mastercard compliance updates

  • TSYS – service‑location coordinates. You can now provide latitude/longitude for service locations in TSYS settings to meet Mastercard requirements. Values must be entered as <latitude>,<longitude> (example: 61.21630,-149.89500).

Mastercard TLID for TSYS. PayConex captures the Transaction Link Identifier (TLID) from authorization responses and carries it into clearing to support Mastercard’s mandate.

  • MPG ID on auth requests. PayConex now includes the Mastercard Merchant Payment Gateway ID (MPG ID) on Mastercard authorizations for Fiserv Omaha and RapidConnect, helping reduce declines tied to missing gateway identifiers.

Chase Paymentech Settlement Improvements

We’ve updated how settlement files are created and reported to make processing smoother and more efficient:

  • Higher settlement capacity: Files now use a transaction-based limit, allowing more volume to settle without manual steps.
  • Smoother processing: When a file reaches its limit, PayConex automatically starts a new one in the same run so settlements aren’t delayed.
  • Clearer reporting: Batch reports and logs now show the batch cutoff time for better visibility into which transactions were included.

Security & access controls

  • Duplicate HMAC header defense. V4 API endpoints now reject requests with duplicate HMAC authorization headers.
  • Account deactivation guardrails. When an account is deactivated, associated API access is blocked until reactivation.
  • Password‑reset hardening. Improved validation and rate limiting to reduce abuse.

Bug Fixes

Transaction Processing & Integrations

  • FIS (Express): Corrected ECI values for recurring e-commerce transactions.

  • Fiserv Device Transactions:

    • Ensures the correct refund type tag is sent for RapidConnect Retail accounts.
    • Fixed “Not Entitled” errors in certain device transaction scenarios.

  • Chase Paymentech Transactions:

    • Corrected source account ID handling to prevent settlement errors.
    • Resolved intermittent errors on partial and full refunds of settled transactions.

  • Reissues:

    • Restored missing first_name values on impacted reissued transactions.
    • Grouped reissues now process as expected.

  • Device model handling: Reader name variations (e.g., iDynamo5 vs. iDynamo 5) are now recognized as the same device.

Webhooks & Notifications

  • Webhook logging: Failed webhook deliveries now store the status, HTTP code, and response body for better visibility.

  • Account Updater:

    • Fixed webhook URLs that included the wrong account ID.
    • Resolved issues with re-triggering and sending batch webhooks.

Account Updater Improvements

  • Disabled invalid schedule rows missing required token references.
  • Removed unexpected characters (such as tabs) from tokenization input.
  • last_reissue values now update correctly.

ACH & Reporting

  • ACH declines: action_date now reflects when decline records are ingested, aligning RSAPI and email reporting.

UI & User Experience

  • Login: Prevents authentication attempts using usernames with leading or trailing spaces.
  • 2FA: Fixed intermittent issues causing the 2FA pages to load without styling.
  • Receipts: Customer receipt emails now consistently reflect edits made in Tools → Receipt Email.

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