Note. Going-live date: October 20, 2026.
Payment Terminals - Payment App
Payment app version: 4.8.0
Note. We strongly recommend upgrading to the latest version of the app as soon as it becomes available. Each new version includes bug fixes and performance improvements that resolve known issues and ensure a more stable experience.
🚀 New features
Apple VAS support for loyalty cards
Payment terminals can now read loyalty identifiers stored in Apple Wallet using Apple Value Added Services (VAS), and send the loyalty ID to the ECR. Both pure and co-branded loyalty cards stored in Apple Wallet are supported.
Note. To enable this feature, please contact your account manager.
Flexible receipt printing in standalone mode
Merchants can now configure receipt printing more precisely in standalone mode. Separate behaviors can be defined for cardholder and merchant receipts, and for successful and failed transactions, using either "Always print" or "Ask operator". The receipt layout remains unchanged.
Note. For more details, see Configure receipt printing options.
🌟 Improvements
Chinese language for the payment app
Chinese is now available as a user language for the payment app on payment terminals.
Backward-compatible display messages for ECR integrations
The payment app now adapts the format of the display messages sent to the ECR based on the cash register software information received at login. Older ECR driver versions keep receiving the legacy format, while compatible integrations benefit from the updated format.
🔧 Fixes
- Resolved an issue where a transaction approved online could be declined offline when the acquirer's authorization response included a message to print.
- Automatic reconciliation is no longer scheduled twice when a closure finishes at the exact scheduled time, which prevents duplicate empty reconciliation receipts.
- ECR display messages now carry their specific reference ID again instead of "0", and their texts remain translated.
- In ECR and App2App integrations, the payment app now waits for the reconciliation receipt to finish printing before returning control, so subsequent reconciliation requests from the cash register are no longer rejected with a BUSY status.
- The back button has been removed from the tip screen in integrated mode, which prevents the tip selection from being blocked.
Payment Terminals - Master App
Master app version: 1.3.9.5
Note. We strongly recommend upgrading to the latest version of the app as soon as it becomes available. Each new version includes bug fixes and performance improvements that resolve known issues and ensure a more stable experience.
🌟 Improvements
More detailed logs for HTTP cash register integrations
Each POST and GET request exchanged with the cash register over HTTP is now logged with its endpoint name and response code, and the full response is logged before it is sent to the cash register. This makes integration issues easier to investigate.
🔧 Fixes
- In HTTP cash register integrations, the Master app no longer stays busy for 60 seconds after a Diagnosis request. Card acquisition requests are now accepted as soon as the Diagnosis response is sent.
Tap to Pay on Android
Android app version: 2.2.0
Note. We strongly recommend upgrading to the latest version of the app as soon as it becomes available. Each new version includes bug fixes and performance improvements that resolve known issues and ensure a more stable experience.
🚀 New features
Hungarian support for Tap to Pay on Android
Tap to Pay on Android is now available in Hungarian.
Direct access to customer support
When the app encounters a blocking error that users cannot solve on their own, customer support details are now available directly from the login page.
Note. For more details, see Support team details.
🌟 Improvements
Cancellation during SSO login
Users can now cancel the login flow when signing in with SSO.
🔧 Fixes
Improved Czech localization
CSV transaction report exports now display Czech characters correctly, and Czech translations in the logout flow have been corrected.
Improved app stability
Several issues that could cause the app to crash, including at startup, have been fixed. The display order of in-app pop-ups has been corrected, and the app now retries automatically in some timeout cases.
Tap to Pay on iOS
iOS app version: 1.2.0
Note. We strongly recommend upgrading to the latest version of the app as soon as it becomes available. Each new version includes bug fixes and performance improvements that resolve known issues and ensure a more stable experience.
🚀 New features
Liquid Glass design
Tap to Pay on iOS now adopts Apple's latest design language, Liquid Glass, with a cleaner and more fluid interface, updated buttons, menus and transitions, and a more polished user experience.
🌟 Improvements
Clearer message for unsupported card brands
When a card brand is not supported, the payment is now declined with a clear, localized message for the user: Payment brand not supported on this terminal.
Enhanced monitoring
The iOS SDK is now covered by our monitoring tools, improving security and our ability to detect and respond to incidents.
🔧 Fixes
Date and time consistency
Resolved an issue where transactions could be declined in some time zones (such as GMT+2) due to a date mismatch between the device and the authorization request. Dates are now converted to the same time zone.
Market Pay Hub
🚀 New features
Tips and donations configuration
Merchants and distributors can now configure tips and donations directly from the Hub when onboarding and managing stores and solutions.
- Donations: for accounts where donations are enabled, an "Enable donations" toggle is available when creating or managing a solution. Users select the beneficiary store from the list of eligible stores, and the beneficiary is shown in the solution details panel. The toggle is hidden when no eligible store is visible within the user's perimeter.
- Tips: in the store details panel, users can choose to receive tips on a separate bank account and provide the dedicated IBAN, BIC and bank document. Once activated, this option is read-only.
🌟 Improvements
Harmonized legal representative and UBO information
Legal representative information is now collected with the same fields in all countries: fiscal code, document type, and document issue and expiry dates. An identity document is now required for every ultimate beneficial owner (UBO) holding more than 25%.
Error message on transaction events
A new "Error message" field explains why a transaction failed. It is available in the Event list view (Manage columns > System data), in the transaction details panel and page, and in exported files.
Additional payment method fields
The solution details panel now displays payment method-specific fields: Merchant ID, PayPal email, Floa client ID, OP Online A2A merchant ID and industry code, and Plussa Money merchant ID with its options (eligible amount, loyalty, money). Toggle-type options can also be set in the solution creation and management forms.
More details on solutions and stores
- Online Payments solutions: Shop name and Merchant URL are now shown in the solution details panel.
- Store details panel: Company source ID and Store source ID are now shown when available. Tap to Pay SDK users need these IDs to initialize the SDK.
- Tap to Pay solution creation: for accounts without SSO, user details are now mandatory, so the first app user is always created together with the solution.
Special characters support
Company names, store names, usernames and addresses now accept UTF-8 characters, such as diacritics or apostrophes. Email addresses remain ASCII-only. Company names with apostrophes are now displayed correctly in incomplete-KYB email subjects.
🔧 Fixes
- Users of very large accounts can now log in and work normally: the Hub now loads only the account-level information it needs at login.
- On the Dashboard in Reporting mode, company and store filters are now applied and figures update to the selected scope.
- When the refundable amount of a transaction cannot be retrieved from the payment gateway, the issue is now reported with a clear message instead of a generic server error.
- Authorization and capture processors are now displayed correctly in the solution details.
- On the Submissions page, the "Add contract" action now depends on the account's digital signature setting, whatever filters are applied.
- Users with the required permission can now edit and save company banking details in Perimeter without being logged out.
- Store IBANs are now displayed in the store details panel once added.
- When adding a solution right after creating a store, or when managing a solution, the relevant store is now pre-selected.
- All pricing policies of a solution are now displayed in the manage solution form.
- Solutions with all pricing rates set to zero can now be opened in the manage solution form.
- Changes to signing responsibles made from Manage pricing are now saved and shown when the form is reopened.
- The Accounts perimeter view no longer displays the same country twice.
- Group accounts now only list the countries assigned to them.
- For Merchant Admin users, company and store filters in Perimeter > Solutions are now populated with the companies and stores within their perimeter.
Related to