Vortex Release Version (May 24, 2026)

• Enhanced Legacy Checkout return processing to ensure network messages (0100/0110 and 1100/1110) are consistently sent for all card brands and card entry modes, including EMV return transactions on Ingenico terminals. This update resolves an issue where certain Visa return transactions, primarily on TSYS integrations, were not generating the required network messages.

• Enhanced 3DS acquirer data mapping across Visa, Mastercard, American Express, and Discover to ensure merchant and acquirer details are correctly passed through Vortex and Stripe during authentication requests. This update adds network-specific merchant schema support and improved acquirer detail handling so merchant names are consistently displayed to cardholders during 3DS challenge flows, including payment and vaulting authentication scenarios.

• Implemented Mastercard Account Name Verification support for non-financial authorization transactions by adding DE 108 request and response mapping for receiver and account owner name validation data. This enhancement enables sending account owner first, middle, and last name details in 0100 authorization requests and returning issuer validation responses, match results, and account owner information from 0110 responses through the API for merchant consumption.

• Added Mastercard Account Name Verification support for non-financial authorization transactions by mapping account owner name fields into DE 108 validation request subelements and transmitting the required data validation indicators for receiver and recipient verification. Enhanced API responses to return Mastercard name validation results and account owner information from DE 108 response subelements, enabling merchants to receive detailed account name match outcomes and issuer-provided account ownership data for compliance and verification workflows.

• Resolved duplicate message key collisions between legacy settlement rails and Vortex processing by updating legacy-generated message keys to append DC identifier 0 for unique aggregation handling. This fix eliminates duplicate authorization response processing that caused ACS VISA ISO8583 deserialization errors and prevents related authorization failures without impacting existing authorization or settlement workflows.

• Enhanced the settlement bot to improve resiliency during settlement file generation by adding S3 client timeout configurations to prevent hung processes caused by potential network issues during S3 uploads. Additional logging was also implemented to improve troubleshooting and visibility into long-running or overlapping cron executions that could previously result in delayed or missing settlement files.

• Updated Omaha settlement processing to correctly persist the platform value as Omaha on new SETTLEMENT_FILE records instead of defaulting to north for Fiserv Omaha banks. This fix also aligns settlement generation behavior with Omaha-specific processing expectations to reduce unnecessary empty settlement files generated by the recurring cron schedule.

• Enhanced multi-capture payment processing to support prorated surcharge handling by ensuring the appropriate surcharge amount is sent to Stripe with each partial capture request. This update applies to both initial and subsequent partial captures, improving surcharge accuracy across multi-capture transaction flows.

Impact

These updates improve transaction processing reliability across Legacy Checkout, settlement, and multi-capture payment workflows while enhancing network compliance and interoperability for Mastercard Account Name Verification and 3DS authentication flows. They also strengthen system resiliency through improved settlement handling, reduce authorization processing conflicts caused by duplicate message keys, and ensure accurate surcharge and settlement data handling across supported processors and payment integrations.