Vortex Release Version (September 1, 2025)

• Updated the Vortex Global reference number to use a 12-digit alphanumeric value instead of the Stripe payment intent ID. A new globalId property has been added under the payment meta field to store the original Stripe payment intent ID. Changes were implemented across the Stripe ACS, Stripe Integration, Broker, and Consumer Checkout services.
• Added support for Account Verification transactions (transactionType == accountVerification with totalAmount == 0) in Global payments. The broker now allows zero-amount verification requests, while ACS Stripe integrates with the Stripe Setup Intents API to validate payment methods.
• Enabled Mail Order / Telephone Order (MOTO) support by sending the MOTO flag from the broker to ACS Stripe. ACS Stripe now validates response.authorization.moto = true for MOTO transactions.
• Fixed an issue where terminal payments for global merchants were incorrectly assigned a batch ID in the MXM database. A new IsGlobalPayment property bypasses batch assignment when true, ensuring Stripe transactions remain batchless.
• Enhanced Checkout L3 data logic to randomize product descriptions when none are provided, ensuring greater variability and compliance with interchange optimization standards.
• Fixed an issue in MX Connect where merchants with multiple processors (e.g., Fiserv North, TSYS) could not edit or save funding accounts due to validation errors. Banking tab updates now save successfully.
• Corrected a boarding issue where debit-side FSCs were incorrectly aligned under DDA #2 instead of DDA #1, which impacted Daily Fee billing in Merchant Manager. Newly boarded accounts now align correctly.
• Enhanced MXC merchant boarding so that Priority Payroll underwriting status automatically syncs with Acquiring when boarded together. Payroll inherits the full underwriting status set, reducing manual intervention and delays.
• Fixed an issue where Interlink Adjustment of Return transactions in Checkout did not include the correct network message. Network requests now populate 0220 with accurate DE2 and DE3 field values.
• Corrected handling of Amex adjustments in VTX where response codes 400 (Reversal Accepted) or 900 were incorrectly marked as Declined. These now appear as Approved in the Vortex Payments Report.
• Added support in VTX for storing Visa Commercial Choice (VCC) Agreement IDs from Field 111 Dataset ID 02 Tag C0 in the 0110 response message. IDs are now saved in the database for use during clearing.
• Implemented VTX settlement support for the Visa Commercial Choice Program by mapping the Agreement ID across all supported processors (Fiserv North, Fiserv Omaha, TSYS, TC-57), ensuring compliance with Visa specifications.
• Added Checkout support for capturing Visa Commercial Choice Agreement IDs in Field 111 Dataset ID 02 Tag C0 on the 0110 response. Values are now stored for use in downstream clearing.
• Implemented Checkout settlement support for Visa Commercial Choice by mapping Agreement IDs into capture/settlement files for Fiserv Omaha and TSYS, ensuring compliance with Visa settlement specifications.

Impact

This release improves accuracy, compliance, and operational efficiency across Vortex systems. Merchants gain expanded support for verification and MOTO transactions, fewer boarding and funding errors, and more reliable reporting. Visa Commercial Choice compliance is ensured across both Checkout and VTX, strengthening downstream settlement processes. Amex and Interlink adjustments now reflect correct statuses and network data, while enhancements to randomize product descriptions improve interchange optimization. Overall, the updates increase transparency, reduce errors, and align Vortex with evolving payment network standards.