Vortex Release Version (May 12, 2025)

Updated the MasterCard Account Updater (R625 file) to format Merchant IDs as 15-digit, right-justified, zero-padded values, resolving prior rejections caused by shorter IDs.
Enhanced the GET /checkout/v3/payment endpoint to return an InProgress status for active payments queried via replayId, replacing inaccurate Declined responses.
Updated validation in Checkout to accept brokered payments with swipe data containing empty or asterisked Track 1 cardholder names, improving compatibility with valid formats.
Applied Visa Level 2 and 3 data corrections for TSYS D256 in Checkout, including accurate tax indicators, validated line item totals, corrected VAT fields, and improved postal code formatting.
Implemented Visa Level 2 and 3 validation enhancements in VTX to align with compliance standards, covering tax logic, line item validation, and disabling VAT unless explicitly provided.
Added support for MasterCard Transaction Lifecycle Linking in VTX by handling TLID in DE105 SE001 across all transaction stages, with serialization, propagation, and visibility in MXC.
Introduced default case handling for undefined or missing fields in network responses, improving data robustness across PPS and EOS-Payment-API-ACS systems.
Resolved an issue where network messages were not displayed in the MXM Merchant Payments Report; message details now appear correctly in MXConnect.
Enabled automatic Redis connection retries in Vortex if a connection is not present during command execution, enhancing reliability and fault tolerance.
Fixed decoding issues for binary fields in ISO8583 messages by updating logic to display HEX strings instead of ASCII/EBCDIC in both UI and API responses.
Removed the hard dependency on Redis from eos-payment-api-bank, allowing the service to start and operate even if Redis is unavailable.

Impact

These improvements significantly enhance platform stability, data transparency, and compliance with card network requirements. Merchants and partners benefit from accurate reporting, fewer integration errors, and improved visibility into payment lifecycles. Users querying transactions now receive real-time, reliable status updates, while internal systems remain resilient even when dependent services like Redis experience outages. Compliance with Visa and MasterCard standards ensures smoother processing and fewer rejections, which in turn strengthens trust and operational efficiency across the ecosystem.