|
ENHANCEMENT
|
Refactored the ACS Stripe payment integration to pass the countryCode parameter directly to functions instead of storing it in the shared resources singleton, preventing race conditions when identifying the platform account and handling payment currencies. |
|
ENHANCEMENT
|
Added a configurable flag for ACSS debit notification webhooks in non-production environments. When enabled, the webhook returns HTTP 200 to Stripe even if notification processing fails in MX Connect, preventing automatic retries and allowing multiple non-production environments to share a single Vortex environment. |
Read more about this release →
|
ENHANCEMENT
|
Updated SMS reserve funding configuration to ensure reserve amounts are transferred to the designated internal reserve account while the remaining batch funds are deposited into the merchant’s account. Reserve transactions are also reflected in the ACH Funding Reports in MX Connect and MX Merchant, as well as SMS reserve reporting. |
|
ENHANCEMENT
|
Updated Mastercard single-message authorization processing to support Device Type values 35, 36, and 37, along with future values in the 38–99 range. Vortex now passes the Device Type from EMV Tag 9F6E into DE 48, Subelement 23, Subfield 1, while preserving the original chip data in DE 55 and maintaining existing device type handling and fallback behavior. The changes apply to 0100 and 0120 messages, with 0400 messages excluded and dual-message authorization behavior unchanged. |
|
ENHANCEMENT
|
Updated Mastercard settlement processing to persist the Device Type received during authorization and pass it through to the applicable TSYS and Fiserv North settlement fields. Fiserv Omaha uses the persisted value when available and retains its existing fallback behavior otherwise. Valid two-digit values are preserved without restricting them to a predefined list, while safe defaults are used for invalid values. Non-Mastercard processing remains unchanged. |
|
ENHANCEMENT
|
Updated CP transaction responses for Authorization, Sale, Interac Sale, and Interac Refund to include network decline codes, response messages, and network advice details received through Stripe. Approved transactions now consistently return code 0, response code 00, and the approved network status, while declined transactions include the available network response code, mapped message, advice code, and seller message to improve transaction troubleshooting and decline visibility. |
|
BUG FIX
|
Corrected the Mastercard Account Name Inquiry message format by updating DE 108 subelement IDs to use the required two-digit format while preserving existing length fields and subfield encoding. Updated serialization and parsing tests to match the Mastercard specification and re-enabled the functionality following certification validation, preventing format-related declines. |
Read more about this release →
|
WHAT'S NEW
|
Updated Discover processing to support Apple Pay 3DS transactions by passing the wallet cryptogram through DE122 DS03 and allowing valid transactions to proceed. Wallet transactions without a required cryptogram are handled appropriately, while DE55 and DE61 processing has been updated to align with Discover R26.2 requirements. |
|
WHAT'S NEW
|
Updated AMEX wallet payment processing to support Apple Pay and other payment-token transactions when an ECI is not supplied by the wallet. For AMEX wallet payments, the ECI now defaults to 20 when missing or blank, while supplied ECI values continue to be preserved and persisted for settlement processing. |
|
ENHANCEMENT
|
Updated chargeback funding processing to use the dispute ID as the funding transaction identifier when a batch ID is not available, allowing SMS PIN-debit chargebacks to proceed through ACH funding while preventing duplicate transactions during reprocessing. Existing SMS funding behavior remains unchanged, and invalid funding lines without a batch ID or dispute ID are rejected instead of creating transactions with undefined identifiers. |
|
ENHANCEMENT
|
Enhanced funding processing to support multiple S3 source directories through configurable directory metadata, allowing SMS chargeback disbursement files to be detected and processed independently alongside existing SMS funding files. SMS chargeback funding now selects the merchant’s Billing/fees or Funding/deposits account based on the Use Deposits Account For Chargebacks setting. |
|
ENHANCEMENT
|
Updated dispute funding files to use the funding/chargeback prefix and .csv extension so they can be processed by the funding bot. Dispute records now include a unique 15-character ACH external ID that distinguishes chargebacks from settlement transactions while preserving the correct debit or credit amount. |
|
ENHANCEMENT
|
Updated ACS Stripe responses to include network decline and advice codes, along with corresponding messages and seller information for declined transactions. Approved transactions now consistently return standardized approval codes, messages, and network status information across account verification, authorization, adjustment, refund, reversal, sale, sale completion, and token transactions. |
|
WHAT'S NEW
|
Added email notifications for ACSS debit transactions. When an ACSS debit enters processing, the merchant receives an email with the transaction amount, currency, and last four digits of the account. |
Read more about this release →
|
ENHANCEMENT
|
Expanded EBT card recognition in the payment broker by incorporating 36 new EBT BIN ranges into network detection workflows. Valid EBT cards now correctly resolve to Visa network processing without triggering unrecognized card errors, while existing network detection rules and non-EBT card classifications remain unchanged. |
|
ENHANCEMENT
|
Updated payment processing and integration services to record transaction entry modes as CP, CNP, or Interac on global payments. The new Transaction Method field in payment responses enables the VTX Card Payments report to accurately reflect entry methods in alignment with the Transaction Activity report. |
|
BUG FIX
|
Resolved an issue in the Checkout-to-Vortex processing flow where EBT Balance Inquiry requests for food stamps and cash benefits were incorrectly routed as dual-message account verifications. EBT Balance Inquiry requests are now routed as Single Message System (SMS) transactions, enabling accurate network-level processing without affecting standard EBT purchase flows. |
|
BUG FIX
|
Updated the Stripe chargeback webhook workflow to assign fee currency codes based on the underlying payment intent currency instead of the platform account default. Fee currency records now consistently match the transaction currency across chargeback events. |
|
BUG FIX
|
Enhanced card-present processing in the Stripe integration to support alphanumeric network decline codes for terminal transaction declines. Decline codes are now accurately mapped and stored in payment responses and database records, providing consistent error handling and response code reporting. |
|
BUG FIX
|
Updated the ACS Stripe integration to ensure authorization responses reflect the cumulative updated total amount following incremental adjustments. When secondary adjustments are approved for card-not-present authorizations, response records now return the final total balance instead of the individual adjustment value. |
Read more about this release →
|
ENHANCEMENT
|
Updated settlement reference generation to use a persistent global counter across application lifecycles, ensuring unique reference identifiers for concurrent or overlapping settlement batches and preventing batch reference collisions. |
|
BUG FIX
|
Resolved host service crashes caused by unhandled Redis network timeout errors by adding a default error handler to the persistence monitoring component while preserving active batch flush rejection handling. |
Read more about this release →
|
WHAT'S NEW
|
Enhanced the Suspend Funds workflow to support SMS funds, allowing authorized Risk and Ops users to configure percentage-based SMS fund suspensions for defined date ranges. Suspension rules are saved against the merchant account, logged with the SMS fund source, and enforce the required validation and authorization rules. |
|
WHAT'S NEW
|
Introduced the new MX VTX Reserve API as the central hub for Priority reserve logic. The service includes standard API configuration, documentation, health and version endpoints, and deployment support across environments. |
|
ENHANCEMENT
|
Enhanced SMS fund processing to automatically divert the configured percentage of a merchant's SMS funds to a designated internal reserve account while an SMS suspension rule is active. Reserve and suspended SMS fund balances are updated automatically, with funds returning to normal merchant settlement when the rule is inactive or expired. |
|
ENHANCEMENT
|
Enhanced the Vortex-to-MXC payment flow to support reserve payments, allowing SMS reserve payment transactions to be recorded in MXC. Funding transaction records now flow from Vortex to MXC, providing visibility into reserve payments for reporting and reconciliation. |
|
ENHANCEMENT
|
Enhanced the MXC Suspended Funds UI with a consolidated Total Reserve Funds view that combines processor reserve funds and SMS suspended funds. Risk and Ops users can now view total reserve exposure along with a breakdown of individual processor and SMS balances. |
|
ENHANCEMENT
|
Enhanced the Suspended Funds SMS workflow to allow Risk users to initiate partial or full fund releases directly from the MXC UI. Releases now create a tracking case, reduce the displayed suspended balance, and record release details for PayOps processing and reconciliation. |
|
ENHANCEMENT
|
Enhanced reserve audit logging to track changes to Priority reserves alongside existing TSYS reserve information. The audit log now combines reserve activity while preserving existing sorting, filtering, and formatting behavior. |
|
ENHANCEMENT
|
Updated Vortex settlement file generation to use the client-provided Destination Country Code when available, preventing incorrect defaults to 840 (USA) for international transactions. The country code now aligns with the destination postal code and defaults to 840 only when no valid country code is provided. The update applies consistently across TSYS, Fiserv North, and Fiserv Omaha settlement formats. |
|
ENHANCEMENT
|
Enhanced BIN lookup and routing logic to evaluate the most specific available BIN match in descending order of specificity (9-digit, 8-digit, 6-digit, then 4-digit). Eligible PINLESS debit transactions are now correctly identified for SMS routing, including cases where less-specific BIN metadata is unavailable. Checkout and Vortex routing now correctly set the SMS flag so eligible transactions are submitted as 0200 rather than 0100. |
|
ENHANCEMENT
|
Enhanced Stripe payment method update handling to verify that a payment method exists in the internal MXM vault before processing Vault and Forward requests. Requests are now executed only when the payment method is mapped to an internal token, with appropriate logging when no matching token is found. |
|
BUG FIX
|
Updated refund and void processing to ensure the original Sale Completion transaction's refundedAmount reflects only active, non-voided refund amounts. Full and partial refund voids, refund adjustments, and out-of-order or repeated voids are now handled correctly without allowing refundedAmount to become negative. |
Read more about this release →
|
WHAT'S NEW
|
Added support for automatically vaulting payment methods for Card Present transactions processed with the setup_future_usage option, allowing successfully vaulted payment methods to be reused for future payments. |
|
ENHANCEMENT
|
Updated the payment broker to load non-production BIN ranges based on a configuration setting instead of the environment name, ensuring test BIN ranges are loaded consistently across all non-production environments. |
|
ENHANCEMENT
|
Enhanced payment method synchronization to automatically retrieve and synchronize updated payment details to the vault when payment method update events are received. |
|
ENHANCEMENT
|
Enhanced payment request logging with structured, searchable log data and centralized payload sanitization to improve observability while protecting sensitive payment information. |
|
ENHANCEMENT
|
Updated SMS Settled reporting to calculate totals and summary values using settlement amounts instead of transaction amounts, improving consistency with Clearing reports and the accuracy of financial reporting. |
|
ENHANCEMENT
|
Enhanced funding file processing to support SMS settlement and funding files across all supported merchant processors, with successfully processed files automatically moved to the completed directory. |
|
BUG FIX
|
Updated refund tracking to automatically adjust the original transaction's refunded amount when a refund is voided, ensuring accurate totals for full and partial refund reversals while preventing negative refunded amounts. |
Read more about this release →
|
ENHANCEMENT
|
Enhanced payment request logging to use structured, searchable log data instead of serialized text, improving observability while introducing centralized payload sanitization to protect sensitive payment information without reducing diagnostic visibility. |
|
ENHANCEMENT
|
Updated SMS Settled reporting to calculate totals and summary values using settlement amounts instead of transaction amounts, ensuring consistency between Settled and Clearing reports while improving batch reporting, billing accuracy, and financial reporting. |
|
ENHANCEMENT
|
Enhanced funding file processing to support SMS settlement and funding files across all supported merchant processors. Successfully processed files are now automatically moved to the completed directory, improving the reliability and consistency of the funding workflow. |
|
ENHANCEMENT
|
Updated refund tracking to automatically adjust the original transaction's refunded amount when a refund is voided, ensuring refunded totals remain accurate for both full and partial refund reversals while preventing refunded amounts from becoming negative. |
Read more about this release →
|
ENHANCEMENT
|
Removed an obsolete processor configuration from the settlement workflow to prevent it from being included in settlement processing. This update reduces unnecessary processing and eliminates related settlement log entries. |
|
ENHANCEMENT
|
Removed the unused VTX Batch Report publishing process to eliminate unnecessary background processing and reduce system messaging overhead while preserving the underlying batch report data for future use. |
|
ENHANCEMENT
|
Enhanced configuration management to support loading application settings from Kubernetes ConfigMaps with automatic fallback to local configuration values when needed. This simplifies environment configuration while maintaining compatibility with existing deployments and ensuring services continue operating when local configuration is unavailable. |
|
ENHANCEMENT
|
Enhanced Redis connectivity to support both TLS-enabled and non-TLS environments through configuration-based settings. This enables seamless compatibility across cloud and on-premises deployments without requiring code changes. |
|
ENHANCEMENT
|
Updated SMS Settled reporting to calculate totals and summary values using settlement amounts instead of transaction amounts. This ensures consistency between Settled and Clearing reports while improving the accuracy of batch totals, transaction summaries, billing, and reporting. |
Read more about this release →
|
ENHANCEMENT
|
Resolved an issue that prevented certain single-message payment transactions from being included in settlement processing due to a missing platform registration. Eligible transactions are now correctly included in settlement file generation and funding workflows. |
|
ENHANCEMENT
|
Enhanced database reliability by expanding retry handling for transient MySQL connection failures during data persistence operations, improving resilience against temporary connectivity issues and reducing the risk of incomplete data affecting downstream processing and settlement workflows. |
|
ENHANCEMENT
|
Enhanced card-present payment processing by adding support for forwarding card data through the Stripe Forward API during terminal transactions, improving the availability of card-related transaction details across integrated payment workflows while maintaining existing processing behavior. |
Read more about this release →
|
WHAT'S NEW
|
Implemented support for the Stripe Forward API, including a new callback endpoint to receive forwarded card data responses. This feature enables end-to-end forwarding workflows by allowing requests to be sent and processed through callback responses containing tokenized card information. |
|
ENHANCEMENT
|
Updated Stripe authorization capture processing to account for payment methods that do not support multi-capture. The system now omits the final capture flag when capturing authorizations for unsupported card types, ensuring sale completion requests process successfully without capture-related errors. |
|
ENHANCEMENT
|
Updated settlement file generation to correctly populate the Point of Sale Terminal Operating Environment field for American Express transactions using authorization message data. This enhancement improves network data consistency by ensuring terminal environment values are accurately carried forward into settlement records and align with card-brand specifications. |
|
BUG FIX
|
Resolved an issue where EMV chip data captured during authorization was not consistently carried forward to related sale completion transactions. Sale completions now inherit required EMV data from the original authorization when not explicitly provided, ensuring Chip Addenda records are generated correctly in settlement files and supporting accurate settlement processing across card brands and processors. |
Read more about this release →
|
WHAT'S NEW
|
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 maintain consistent fee configuration data across processing, reporting, batch management, receipts, and Passport integrations. |
|
ENHANCEMENT
|
Updated Stripe chargeback notification processing to use the correct configuration source for dispute notification URLs and aligned default environment settings with UAT configuration, ensuring chargeback disputes are routed correctly and merchants consistently receive chargeback email notifications. |
|
BUG FIX
|
Resolved an issue in the ACS Stripe integration where response.totalAmount could return incorrect values for adjustment transactions and payments processed through the token processor. Authorization, sale, and adjustment transactions now consistently return the correct transaction amount. |
|
BUG FIX
|
Fixed an issue affecting Omaha Vortex Visa EMV settlement transactions where Card Sequence Numbers in TapTrans Chip 1 Addenda records were not padded with required leading zeros, causing settlement file rejections. Card Sequence Numbers are now consistently formatted as three-digit numeric values. |
|
BUG FIX
|
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 to support successful settlement processing. |
|
BUG FIX
|
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 while preserving existing transaction processing behavior. |
Read more about this release →
|
ENHANCEMENT
|
Enhanced Legacy Checkout return processing to ensure required network messages (0100/0110 and 1100/1110) are consistently generated for all card brands and card entry modes, including EMV return transactions on Ingenico terminals and TSYS integrations. |
|
ENHANCEMENT
|
Enhanced 3DS acquirer data mapping across Visa, Mastercard, American Express, and Discover to improve merchant and acquirer detail handling during authentication requests, ensuring merchant names display consistently during payment and vaulting challenge flows. |
|
WHAT'S NEW
|
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, including issuer validation responses and account ownership details. |
|
WHAT'S NEW
|
Added enhanced Mastercard Account Name Verification support by mapping account owner validation fields into DE 108 request subelements and returning detailed issuer-provided account name match results and ownership information through API responses. |
|
BUG FIX
|
Resolved duplicate message key collisions between legacy settlement rails and Vortex processing by appending a DC identifier to legacy-generated message keys, eliminating duplicate authorization response handling and related ACS VISA ISO8583 deserialization errors. |
|
ENHANCEMENT
|
Enhanced settlement bot resiliency by adding S3 client timeout configurations and expanded logging to prevent hung settlement generation processes and improve troubleshooting visibility for long-running or overlapping cron executions. |
|
BUG FIX
|
Updated Omaha settlement processing to correctly persist Omaha platform values on SETTLEMENT_FILE records and reduce unnecessary empty settlement file generation for Fiserv Omaha banks. |
|
ENHANCEMENT
|
Enhanced multi-capture payment processing to support prorated surcharge handling by ensuring accurate surcharge amounts are transmitted to Stripe during initial and subsequent partial capture requests. |
Read more about this release →
|
WHAT'S NEW
|
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. |
|
ENHANCEMENT
|
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. |
|
ENHANCEMENT
|
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. |
|
ENHANCEMENT
|
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. |
|
ENHANCEMENT
|
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. |
|
BUG FIX
|
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. |
|
BUG FIX
|
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. |
Read more about this release →
|
ENHANCEMENT
|
Enhanced Apple Pay error logging to include response codes and messages for failed requests, ensuring detailed response data is captured in logs and improving visibility for troubleshooting transaction failures. |
|
ENHANCEMENT
|
Aligned AMEX POS data mapping by ensuring Field 22 authorization values are correctly propagated to settlement records across supported processors, including proper positional mapping for Fiserv Omaha, resolving inconsistencies and ensuring accurate transaction processing. |
|
ENHANCEMENT
|
Aligned Mastercard ACS service configuration with other card networks to ensure consistent routing to correct aggregator environments across non-production setups, enabling uniform traffic routing to QA and UAT simulators. |
|
ENHANCEMENT
|
Enhanced Checkout responses for account verification transactions by mapping network-level cardholder name verification results into the risk object, ensuring account name response and match indicators are accurately populated based on issuer responses. |
|
ENHANCEMENT
|
Introduced feature flags in ACS Stripe to control L2 and L3 processing, enabling dynamic inclusion of request data and enforcement of arithmetic validation on line items through configuration without requiring deployment. |
|
ENHANCEMENT
|
Created a design document outlining the implementation of Stripe Vault and Forward API within Vortex, defining integration approach, data flow, and key considerations for securely retrieving and forwarding card data. |
|
ENHANCEMENT
|
Added support for EMV request data in ACS Stripe behind a feature flag, enabling ingestion and parsing of device, swipe, and EMV payloads into TLV format with extraction of relevant tags and fallback behavior for card-not-present transactions when disabled. |
Read more about this release →
|
WHAT'S NEW
|
Updated ACH processing to support MXC tenants with multiple credential sets, introducing routing logic that selects credentials based on NACHA ID while maintaining backward compatibility through fallback to tenant-level credentials. |
|
ENHANCEMENT
|
Enhanced Stripe payment intent metadata by automatically populating the taxAmount field using prioritized sources and converting all values into smallest currency units to ensure consistent and accurate tax data representation. |
|
ENHANCEMENT
|
Improved Stripe integration by normalizing customer country codes into ISO 3166 Alpha-2 format during payment intent creation, preventing processing errors and ensuring compliance with address validation requirements. |
|
ENHANCEMENT
|
Updated chargeback fee handling to dynamically retrieve values while enforcing a minimum threshold, ensuring consistent fee application when configured values are missing or below the required baseline. |
Read more about this release →
|
ENHANCEMENT
|
Enhanced settlement file generation by introducing surcharge addenda records for applicable card brands, ensuring accurate calculations, correct formatting, and proper placement without impacting other processing. |
|
BUG FIX
|
Improved SMS void and reversal handling by validating issuer responses before approval, ensuring declined void attempts retain the original transaction. |
|
ENHANCEMENT
|
Enforced single-capture behavior for SMS PIN debit transactions by preventing multi-capture and partial capture across APIs. |
|
ENHANCEMENT
|
Restricted unsupported transaction adjustments across systems, returning a standardized not allowed response when attempted. |
|
BUG FIX
|
Corrected American Express addenda handling to properly reflect card-not-present transactions in settlement files. |
|
BUG FIX
|
Fixed MasterCard refund processing to correctly populate addenda indicators when additional records are present. |
|
BUG FIX
|
Resolved settlement data issues by correcting POS input mode mapping and fixing date offset errors. |
|
BUG FIX
|
Updated MasterCard purchase record formatting to correctly populate default values in accordance with specification requirements. |
|
ENHANCEMENT
|
Enhanced settlement file support for updated specifications by expanding field lengths and adjusting positions while maintaining validation compliance. |
|
BUG FIX
|
Corrected Point of Sale addenda values to ensure accurate handling of transaction indicators and card presence data. |
|
ENHANCEMENT
|
Updated routing configuration values to align with defined routing priorities. |
|
BUG FIX
|
Ensured tax-exempt data is correctly included in transaction payloads when provided. |
|
BUG FIX
|
Fixed missing discount indicators and amounts in purchase card addenda records. |
|
BUG FIX
|
Resolved multiple sale completion issues to ensure accurate authorization usage, addenda generation, and data sequencing. |
|
BUG FIX
|
Fixed missing addenda records in sale completions to ensure correct transaction linkage data. |
|
WHAT'S NEW
|
Added automated chargeback notification emails for Canadian merchants with localized language support and defined response deadlines. |
Read more about this release →
|
WHAT'S NEW
|
Added support for enriching Canadian Visa and Mastercard transactions processed through Stripe with Level 2 and Level 3 data such as tax amount, quantity, product code, and product description to enable evaluation of potential interchange savings. Transactions without enrichment continue to qualify at Level 1 while Interac and Amex processing remain unchanged. |
|
ENHANCEMENT
|
Added new APIs to the eos-payment-api-cutoff service to allow on-demand triggering of bot-funding, bot-ach, and bot-dispute jobs. This improves testing efficiency by removing the need to wait for scheduled job execution and aligns with existing job control patterns used across Vortex services. |
|
BUG FIX
|
Fixed an issue where SaleCompletion transactions could intermittently fail validation because the system attempted to verify the original authorization before it was persisted in the database. The payment broker now checks Redis cache when the transaction is not yet available in the database, preventing false authorization code mismatch errors. |
|
BUG FIX
|
Fixed a settlement issue where the Cardholder Activated Terminal indicator for Mastercard ecommerce transactions was not correctly populated, which could result in network rejects. The system now assigns the correct indicator value based on device type and transaction context. |
|
BUG FIX
|
Resolved multiple issues in the Point of Sale Addenda Record for Vortex Omaha settlement files to ensure values align with TapTrans specifications and authorization data. The final authorization code field now uses a default value and several Discover-specific fields are mapped correctly. |
|
BUG FIX
|
Corrected serialization of Discover Chip Addenda fields in Vortex Omaha settlement files so values such as Card Sequence Number, Terminal Country Code, Terminal Capability, CVM Results, Application Version Number, Application Identifier, and Interface Device Serial Number are populated correctly. |
|
BUG FIX
|
Fixed mapping issues in the Discover Auth Addenda Record so that settlement file values correctly reflect the original authorization data including identification method, MOTO indicator, and service development code. |
|
BUG FIX
|
Corrected an issue where Discover transactions populated spaces in the CPS IC1 Addenda Record instead of required values. The system now sends the correct electronic commerce indicator for tokenized transactions and defaults to 00 when no token is present. |
|
BUG FIX
|
Resolved an issue where the Terminal Verification Results value from EMV Tag 95 was missing from settlement file Chip Addenda records. The indicator that signals additional addenda records was also corrected to align with legacy system behavior. |
Read more about this release →
|
WHAT'S NEW
|
Chargeback webhook processing now supports multiple Stripe platform accounts, enabling accurate dispute handling across regions. When a dispute is created, the system reverses the original transfer or transfers and generates a country-specific dispute fee transfer of 15 USD for USA merchants or 15 CAD for Canadian merchants to ensure proper fund reconciliation. |
|
ENHANCEMENT
|
Updated SMS PIN debit funding for merchants funded via Passport with TSYS to route funds to the merchant’s Passport routable account instead of a generic processor funding account, ensuring accurate settlement and preventing funds from remaining in intermediary accounts. |
|
ENHANCEMENT
|
Updated Visa network message logic to include DE 48.11 only for secondary transactions when the original network is Interlink, preventing invalid field rejections for other Visa debit networks during voids, returns, and adjustments. |
|
ENHANCEMENT
|
Enhanced the Visa SMS funding CSV file sent to ach.com by populating the Individual ID field with the merchant’s Card Acceptor ID, improving ACH reject mapping, supporting UAR retrieval indexing requirements, and correcting funding bot logic for SMS funding scenarios. |
Read more about this release →
|
ENHANCEMENT
|
Improved ACH settlement logging to clearly indicate when files are successfully sent to ACH.com, including batch IDs, totals, external file IDs, and additional metadata for full traceability and clearer incident diagnosis. |
|
ENHANCEMENT
|
Added post-lock validation to SMS settlement file processing to verify data integrity, financial totals, and originating instance before funding proceeds. Validation failures now halt processing, log full context for auditability, and mark control files as failed without impacting other files. |
|
ENHANCEMENT
|
Updated dispute processing to write Visa chargeback-related debit and credit files to S3 in alignment with the current ACH funding flow, ensuring automated merchant debits and credits continue without file team coordination. |
|
ENHANCEMENT
|
Updated clearing and settled reports to source amounts from settlement data rather than initial transaction data, removing $0 entries and correctly displaying refunds. |
|
ENHANCEMENT
|
Backfilled historical transaction records to restore missing Card Type values, ensuring consistent reporting and filtering across historical and current data. |
|
ENHANCEMENT
|
Added support for recurring and credentials-on-file payments with Stripe, including proper handling of on-session and off-session transactions, multicapture, sale completion, and surcharging for compliant recurring processing. |
|
ENHANCEMENT
|
Updated MasterCard TapTrans file generation in both Vortex and Legacy Checkout to align with the latest layout specifications by relocating the Merchant Country of Origin field to the correct positions. |
|
ENHANCEMENT
|
Enhanced Visa SMS funding files by updating the Individual ID field to use the merchant Card Acceptor ID, improving ACH reject mapping and UAR retrieval accuracy. |
|
ENHANCEMENT
|
Restricted access to the incomplete VTX Batch Report in reporting to prevent users from viewing data that cannot yet accurately aggregate across multiple indexes. |
|
BUG FIX
|
Updated Visa SMS effective date logic to always select a valid business day, preventing weekend dates and excluding US Federal Reserve Bank holidays while allowing non-federal holidays. |
|
BUG FIX
|
Resolved EMV Chip Addenda serialization issues for offline sale completions by correctly splitting Issuer Application Data and properly encoding the Visa Interface Device Serial Number, ensuring valid 6K Chip Addenda records and successful settlement validation. |
|
BUG FIX
|
Updated SMS PIN debit funding for Passport merchants to route funds to the correct routable Passport account instead of the generic processor funding account, ensuring proper settlement. |
|
BUG FIX
|
Corrected Mastercard CAT Indicator logic in settlement files to prevent rejects and ensure alignment between authorization and settlement data for eCommerce, wallet, and unattended transactions. |
|
BUG FIX
|
Updated Visa network messaging to conditionally include DE 48.11 only for applicable secondary transactions, preventing invalid field rejections during processing. |
|
BUG FIX
|
Corrected SMS void handling logic to finalize voids only after confirmed Visa approval, preventing incorrect $0 adjustments and reconciliation discrepancies across checkout, settlement, and reporting. |
Read more about this release →
|
WHAT'S NEW
|
Stripe payment processing now supports multiple Stripe Platform accounts, automatically routing transactions based on merchant country to ensure correct processing for Canadian, U.S., and Puerto Rico merchants and support future regional expansion.
|
|
ENHANCEMENT
|
SMS settlement processing now generates and stores control metadata directly on settlement CSV files using S3 object metadata, improving auditing, validation, and downstream processing visibility without impacting settlement success.
|
|
ENHANCEMENT
|
Distributed locking has been added to SMS funding processing to prevent duplicate settlement file handling across multiple instances, ensuring only one process handles a file at a time while allowing safe recovery and reprocessing after failures.
|
Read more about this release →
***
|
WHAT'S NEW
|
Expanded multi-currency and international payment support across Vortex by enhancing country code handling, enabling broader ISO currency usage, and improving consistency for global and Priority processor payment flows.
|
|
ENHANCEMENT
|
Updated chargeback processing for Canada-connected accounts to apply a consistent fixed CAD fee during dispute events, ensuring accurate fee application, correct reversal of payment intent transfers, and proper platform fee creation.
|
|
ENHANCEMENT
|
Improved country code validation and propagation throughout the card payment flow by supporting ISO Alpha-2, Alpha-3, and Numeric formats, enforcing required merchant address data for Priority processor payments, and normalizing country codes for Stripe metadata.
|
|
ENHANCEMENT
|
Refactored Stripe payment processing by moving payment model to payment intent conversion into the ACS Stripe service, improving separation of concerns while preserving all existing Global Payment functionality.
|
|
ENHANCEMENT
|
Enabled environment-specific configuration for Apple Pay Discover, allowing Discover transactions in the QA-AUS certification environment while maintaining existing behavior in other QA environments.
|
|
ENHANCEMENT
|
Improved the 3DS challenge experience by ensuring the correct transaction-specific merchant name is displayed during authentication and OTP delivery, replacing the default aggregator name for greater clarity.
|
Read more about this release →
***
