Payment Application Release Notes
Version: 2.0.15.25
Release Date: 2026-09-07
Customer Impact Statement
- Transaction receipts now include a Surcharge field, displayed as 0 by default. When the surcharge feature is enabled and applicable, the calculated surcharge amount is displayed instead.
- Provides cardholders using BankAxept co-badged cards with a clear and consistent choice of payment scheme without requiring merchant intervention.
- Provides clearer payment information and an improved user experience during amount approval.
- Provides a cleaner and more consistent user interface across the Payment Application.
Features
Surcharge Calculation for Purchase Transactions
- Added support for surcharge calculation on purchase transactions. Once the terminal identifies the card through BIN lookup and confirms the transaction as a purchase, it determines whether a surcharge applies and calculates the applicable surcharge amount. (ID: 51236).
Improvements
Consumer Choice for BankAxept Co-Badged Cards
- Improved Consumer Choice handling for BankAxept co-badged cards. Cardholders are automatically presented with the available payment schemes with equal prominence and can select their preferred scheme directly on the terminal. (ID: 53990).
Improved Local Handling of Offline Refund Declines
- Improved the handling of refund transactions that receive an AAC (offline decline) decision from the EMV process. Such refund transactions are now declined locally, consistent with the existing behavior for purchase transactions. This ensures that offline refund transactions are treated as locally denied transactions, preventing them from being processed further when the EMV decision indicates a decline. (ID: 50218).
Updated Amount Approval Screen Design
- Updated the Amount Approval screen to display the card name and improved the OK button appearance for better visibility and consistency. (ID: 54458).
Removed Blue Wave Background from Application Screens
- Removed the blue wave background elements from application screens to provide a cleaner and more consistent visual design. (ID: 54458)
Improved Transaction Completion When ECR Connection Is Unavailable
- Improved transaction completion handling when the ECR connection is unavailable or unresponsive. The ECR TCP connection timeout is now handled correctly, and event log processing has been moved to occur after the transaction returns to the idle state. This prevents the PA from remaining on the Approved screen for an extended period and ensures a smoother transition after successful transactions. (ID: 53737).
Fixes
Prevent Application Hangs During AppX Response Processing
- Fixed an issue where the application could become unresponsive while processing an AppX response. The affected operation has been moved from the main thread to a background thread, preventing it from blocking the application and improving overall responsiveness during AppX response processing. (ID: 50217).
Prevented Duplicate Beeps During SCA Card Reinsertion
- Fixed an issue where the terminal could produce two consecutive beeps during an SCA (Strong Customer Authentication) scenario when the user was prompted to insert the card again. The terminal now provides a single audible notification when the card reinsertion prompt is displayed, ensuring a clearer and more consistent user experience. (ID: 51181).
Aligned BAX Offline Transaction Processing with Specification
- Fixed BAX offline transaction handling to comply with the BAX Offline Specification. This includes improved offline transaction identification and correction of the EMV data sent for offline-approved transactions to ensure the correct TC (Transaction Certificate) result is reflected. (ID: 51998).
Prevented Transaction Loop During Contactless Refunds
- Fixed an issue where the terminal could enter a transaction loop when an unexpected G8 (PIN Request) response was received from the card issuer during a contactless refund. The terminal now handles this response correctly and prevents repeated transaction processing, ensuring the refund flow completes without entering a loop. (ID: 52008).
Prompt for Card Insertion During SCA Transactions
- Fixed an issue in the SCA transaction flow where the terminal did not prompt the customer to insert the card when required. The terminal now correctly displays the “Insert Card” prompt during applicable SCA scenarios, ensuring the transaction follows the expected card-present flow. (ID: 52042).
Corrected EMV Cryptogram in Swedbank Approval Advice and Clearing Messages
- Fixed an issue where the EMV cryptogram included in Swedbank HISO Approval Advice and Clearing messages could be incorrectly reported as an ARQC instead of the expected TC (Transaction Certificate) for successfully completed transactions. The EMV data is now populated correctly according to the transaction flow and second GENERATE AC result. (ID: 52051).
Fixed EPP Time Synchronization During Host Logon
- Fixed an issue where the EPP firmware time was not updated during Host Logon when the terminal and gateway used different time zones. The EPP time is now synchronized correctly with the gateway time and time zone, ensuring accurate time information for transaction processing and preventing potential ARQC validation failures that could result in transaction declines. (ID: 52130).
Improved GetLastTransaction Handling for Invalid Merchant Data
- Fixed an issue where GetLastTransaction could fail when merchant data contained invalid XML characters. The operation now handles such data correctly, ensuring the last transaction information can be retrieved without errors. (ID: 52596).
Prevented Missed Reversals During Transaction Abort
- Fixed a timing issue where a reversal could be missed when an abort request was received during transaction processing. In specific card-inserted scenarios, the transaction state could transition to WaitForCardRemoval before the authorization completed, causing the system to miss the host communication event indicating that the transaction should be declined and reversed. The transaction flow has been updated to ensure the required reversal is handled correctly when an abort is received. (ID: 53969).
Known Issues in This Release
- None
Written by: Chami Muthukumarana. | Reviewed by: Chamika Dimantha |