Vortex Release (June 7, 2026)
Release notes - June 7 2026
Vortex Release Version (June 7, 2026)
-
Updated Stripe chargeback notification processing to use the correct configuration source for dispute notification URLs and aligned default environment settings with UAT configuration. This enhancement ensures chargeback disputes are routed correctly and merchants consistently receive chargeback email notifications when dispute events occur.
-
Added support for the Priority Managed Fee Program (PMFP) across MX Merchant, MX Connect, and Checkout workflows. Merchants can now enable PMFP during onboarding and product configuration, apply Priority Processing Fees to eligible credit card transactions, display fee disclosures and transaction details throughout the payment lifecycle, and ensure fee configuration data is consistently stored, transmitted, and reflected across transaction processing, reporting, batch management, receipts, and Passport integrations.
-
Resolved an issue in the ACS Stripe integration where
response.totalAmountcould return incorrect values for adjustment transactions and payments processed through the token processor. Authorization, sale, and adjustment transactions now consistently return a total amount that matches the requested transaction amount while maintaining existing payment processing behavior. -
Fixed an issue affecting Omaha Vortex Visa EMV settlement transactions where Card Sequence Numbers in TapTrans Chip 1 Addenda records were not padded with the required leading zeros, resulting in network reject code V0873 ("Card Sequence Number Is Not Numeric"). Settlement processing now formats Card Sequence Numbers as three-digit numeric values, ensuring successful EMV settlement file acceptance.
-
Resolved an issue affecting recently migrated FD Omaha Vortex merchants processing American Express EMV transactions where settlement records could be rejected due to a missing value in the Chip 3 Addenda record. The required field is now consistently populated, ensuring settlement files meet processor requirements and settle successfully.
-
Fixed an Omaha Vortex settlement issue that caused Discover transactions to be rejected due to unsupported Cardholder ID Method values in Auth Addenda records. Settlement processing now enforces valid network-supported values, applies PIN validation requirements where appropriate, and maintains existing behavior for mail order, telephone order, e-commerce, unattended terminal, and signature-based transaction scenarios.
Impact
These updates improve settlement processing reliability across Visa, American Express, and Discover transaction flows while ensuring compliance with network and processor requirements. They also enhance chargeback notification delivery, strengthen Stripe transaction response accuracy, and expand Priority Managed Fee Program support across onboarding, payment processing, reporting, and receipt experiences. Together, these enhancements improve operational consistency, merchant visibility, and transaction processing accuracy across the Vortex platform.
Updated 5 months ago