PayConexDecryptxShieldConexTECS Platform
Release Notes
Request SandboxContact Us
Back to All

PayConex - 12.08.2025

11 days 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

Mastercard compliance updates

  • TSYS – service‑location coordinates. You can now provide latitude/longitude for service locations in TSYS settings to meet Mastercard requirements and avoid funding issues. 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

  • Updated batch limits. The legacy batch cap has been replaced with a transaction‑based threshold so more volume can be settled per file without manual intervention.
  • Automatic rollover within the same run. When a file reaches its transaction limit, PayConex now starts a new file automatically in the same job so remaining batches don’t wait for the next cron.
  • Cutoff time in reports. Batch reports and logs now display the batch cutoff time, making it clear 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) recurring payments: Corrected ECI mapping for recurring e‑commerce transactions.
  • Fiserv Device Transactions:
    • Ensures the refund type tag is present for transactions on RapidConnect Retail accounts.
    • Resolved “Not Entitled” errors for certain device transaction scenarios on Fiserv.
  • Chase Paymentech (groups): Fixed an issue where group transactions on newer architecture didn’t pass the correct source account_id value, leading to settlement errors.
  • Reissues:
    • Restored the missing first_name on some reissued transactions after September 2025.
    • Ensured grouped reissues are picked up correctly.
  • Device model normalization: Variants like iDynamo5 vs. iDynamo 5 are now treated as the same reader type, so correct terminal capability codes are sent.

Webhooks & notifications

  • Webhook logging: Non‑2xx deliveries are now persisted with failure status, HTTP code, and response body for better audit-ability.
  • Account Updater webhooks:
    • Fixed webhook URLs that included an incorrect account ID.
    • Corrected issues when re‑triggering Account Updater webhooks.
    • Addressed scenarios where batch webhooks weren’t sent or logged.

Account Updater

  • Disabled invalid schedule records (e.g., enabled rows lacking a token reference).
  • Strips unexpected characters (e.g., tab characters) from tokenization input.
  • last_reissue on the transaction table now updates properly.

ACH & reporting

  • ACH decline timing: The action_date now reflects when decline records are ingested, so RSAPI queries and email notifications align on the same day.
  • Chase refunds: Fixed intermittent processing errors on partial/full refunds of settled transactions.

UI & user experience

  • Login validation: Prevents login attempts with leading/trailing spaces in usernames that could trigger errors.
  • 2FA styling: Resolved an issue where the 2FA page could intermittently render without styling.
  • Customized receipts: Customer receipt email content now reliably reflects edits saved under 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].