Virtual Terminal release notes

📝 Release Notes: VT Level 2 and Level 3 Improvements and help guide

Deployment Date: February 26, 2026

Priority: P1 (Critical for Merchant Qualification)

Jira Tickets:

🚀 Executive Summary

This release focuses on improving data quality and mathematical accuracy for Level 3 (L3) transactions in the Virtual Terminal (VT). By relabeling confusing UI elements and automating line-item calculations, we are resolving systemic qualification failures where local taxes were being misreported as VAT. Additionally, we have fixed a critical bug that was incorrectly scaling unit costs during batch extraction and updated the 'Commercial Card Acceptance Transaction Guide' to provide merchants with current procedural guidance.

🛠 Key Functional Changes

1. UI Relabelling & Qualification Triage [OO-2708]

Confusing labels that previously led to misreporting have been updated to ensure merchants qualify for L3 rates:

Renamed Tax Fields: Labels in "Level 2 and 3 Settings" and "L3 Line Item Records" have been changed from generic "Tax Rate/Amount" to "Local Tax Rate" and "Local Tax Amount"

Field Security: To prevent manual errors, "Line Item Total" and "Local Tax Rate" are now greyed out/read-only.

2. Automated L3 Calculations [OO-2708]

The line-item page now features real-time automation to maintain mathematical integrity:

Standard Formula: Line Item Total is now strictly calculated as (Quantity * Unit Cost) - Discount.
Dynamic Tax Sync: Updating the Local Tax Amount will now automatically recalculate the Local Tax Rate.
System Configuration Priority: If a merchant updates Quantity or Unit Price, the tax amount will automatically recalculate using the default rate from system settings.
Zero tax rate in System Configuration : if there is no default tax rate, and merchant change tax amount, tax rate is changed accordingly then merchant update quantity/unit cost/ discount again, tax rate is changed as tax amount still didn’t change.

3. Bug Fix: Unit Cost Reporting Accuracy [OO-2780]

A critical "Medium" severity bug identified in the development environment has been resolved:

The Issue: Previously, a unit cost of 1.00 entered in the VT was being recorded as 0.01 in the visa_settlement_line_items table.

The Resolution: Corrected the code logic in the TridentBatchExtractor and BatchExtractionEvent flows to ensure unit cost values are passed accurately to settlement tables.

📖 Merchant Guidance & Support Update

Update the "Commercial Card Acceptance Transaction Guide" [OO-2712]

The legacy guideline (dated 2018) has been replaced with the updated "Commercial Card Acceptance_January_2026.pdf".

📺 Demo recording of above changes

Demo Video (2026-02-20 21:05 GMT+7)

✅ Test cases covered and test results :

OO-2708 : https://merchante.atlassian.net/wiki/spaces/SE/pages/5257134081

OO-2780 : https://merchante.atlassian.net/wiki/spaces/SE/pages/5269061645

OO-2712 : https://merchante.atlassian.net/wiki/spaces/SE/pages/5221548041