Vortex Release Version (February 15, 2026)

• Enhanced ACH settlement logging to clearly indicate when files are successfully sent to ACH.com, even if subsequent batch status updates fail. Logs now include batch IDs, totals, external file IDs, and extended metadata to improve traceability and incident diagnosis.
• Added post-lock pre-processing validation to SMS settlement funding to ensure data integrity, correct financial totals, and valid originating instances before funding proceeds. Validation failures now halt only the affected file, log full audit context, and mark control files as failed without interrupting other processing.
• Updated Visa SMS effective date logic to always select a valid business day, excluding weekends and U.S. Federal Reserve holidays. Same-day funding scenarios now correctly roll forward when necessary, ensuring ACH compliance and accurate effective dates in both ACH.com submissions and persisted funding records.
• Hid the Priority VTX Batch Report in MXC Reporting to prevent access to an incomplete report that cannot yet accurately aggregate data across multiple indexes.
• Updated the dispute bot to write Visa chargeback debit and credit files to Amazon S3 instead of HDFS, aligning with the current ACH processing flow and ensuring resulting entries are correctly included in the MXC ACH report.
• Corrected EMV Chip Addenda serialization for Omaha VTX offline sale completions by properly splitting Issuer Application Data between Chip Addenda Records and encoding the Visa Interface Device Serial Number as an alphanumeric value. These fixes ensure valid 6K Chip Addenda records and successful FD settlement validation.
• Updated clearing and settled reports to source transaction amounts from settlement data rather than original transaction amounts, eliminating $0 entries for voided or declined transactions and ensuring refund values display correctly.
• Backfilled historical transaction records to populate missing Card Type values using existing account data, restoring consistent Card Type visibility and enabling accurate filtering across historical and current reports.
• Added support for recurring payments and vaulted cards using Stripe credentials-on-file for CNP transactions. Integrations now pass customer and payment method identifiers, correctly handle on-session and off-session payments, and enforce proper behavior for multicapture, sale completion, and surcharging.
• Updated SMS PIN debit funding for Passport-funded merchants to route funds to the merchant’s Passport routable account instead of the generic processor funding account, ensuring accurate settlement and preventing funds from remaining in intermediary accounts.
• Updated MasterCard TapTrans settlement file generation in both Vortex and Legacy Checkout to comply with 10/17/2025 specifications by relocating the Merchant Country of Origin field to the correct positions.
• Corrected Mastercard settlement rejects caused by invalid CAT indicators by aligning Cardholder Activated Terminal logic between authorization and settlement processing.
• Updated Visa network message logic to conditionally include DE 48.11 only for eligible secondary transactions when the original network is Interlink, preventing invalid field rejections.
• Enhanced the Visa SMS funding CSV sent to ACH.com by updating the Individual ID field to use the merchant’s Card Acceptor ID, improving ACH reject mapping and alignment with indexing requirements.
• Corrected SMS void and reversal handling logic to validate Visa responses before finalizing voids. Voids now complete only upon successful network confirmation, preventing incorrect $0 adjustments and reconciliation discrepancies across MXM, VTX, and reporting systems.

Impact

These updates strengthen settlement accuracy, ACH compliance, and funding reliability across SMS and Vortex processing. Improvements to logging, validation, file handling, and reporting enhance auditability and operational visibility, while network message corrections and file layout updates ensure continued compliance with Visa and Mastercard specifications. Together, these changes reduce settlement errors, improve reconciliation integrity, and increase overall processing stability without disrupting merchant workflows.