Vortex Release (May 10, 2026)

Release notes - May 10 2026

May 10

Vortex Release Version (May 10, 2026)

  • Updated logging for WebSocket connection errors by elevating crypto-related error logs to level 50 while retaining level 40 logging, improving visibility and monitoring of critical connection issues.
  • Fixed an issue with Vortex TSYS DF256 settlement files where the Product Code was missing from PURC2 records for MXM recurring payments by leveraging existing CEDP logic to generate default values such as ITEM1 and ITEM2. This ensures required data is populated correctly, improving transaction qualification and settlement accuracy.
  • Enhanced .NET Checkout logging by capturing Vortex API request and response payloads with proper sanitization of sensitive data, enabling secure debugging and cross-system traceability. Logs are now structured and readable, supporting improved monitoring, reconciliation, and issue diagnosis in production environments.
  • Fixed an issue with Discover 3DS transactions where the Authentication Type value was not being populated in Field 122, ensuring “02 = ProtectBuy” is now correctly sent in positions 1–2 of the Additional Authentication Data for proper network compliance.
  • Updated the settlement bot to use bank-level locking instead of job-level locking, preventing overlapping executions from blocking all settlement processing. This ensures that only the actively processing bank is locked while others continue on schedule, improving reliability, reducing delays, and eliminating the need for manual intervention during settlement windows.
  • Added idempotency handling for terminal payment webhooks to detect and ignore duplicate events, ensuring each event is processed only once and preventing duplicate transactions or side effects.
  • Updated the card.complete flow to preserve invoice data from the secondary transaction during L2/L3 partial captures for Priority processor transactions, ensuring compliance with Stripe requirements. When secondary invoice data is not provided, the system falls back to the original invoice data, maintaining accuracy and consistency.

Impact

These updates improve visibility into WebSocket and Checkout transaction processing through enhanced logging and structured diagnostics, strengthen settlement reliability and concurrency handling, and ensure compliance with processor and network requirements across Discover 3DS and Stripe L2/L3 flows. They also enhance webhook resiliency through idempotency protections and improve settlement accuracy for recurring payments by ensuring required Product Code values are consistently populated.

Back

Did this page help you?
Priority Technology Holdings Logo