Release notes

• The terminal screen now shows an animation while starting up.
• Store-and-forward offline payments now support authorization adjustment.

• You will be able to restart the payment terminal from the menu Settings > Power.

• We fixed the issue where it was not possible to board S1U2 terminals using the ethernet connection.
• We fixed the issue where the cellular modem rebooted every 20 minutes on S1F2 terminals with Android 9. This had caused a connectivity gap during which payments failed.

• You can now accept NFC wallet payments on your Android app without having to switch to the Adyen UI.

• Dynamic Currency Conversion (DCC) is now available for contactless and NFC wallet payments.

• It is now possible to configure manual key entry (MKE) for Store-and-forward payments.

• We fixed the issue where in some cases payments with Interac cards failed.

• We fixed the issue that reset the card selection when activating accessibility on the present card screen.

• When an auto-launch application crashes on payment terminals that are in kiosk mode, the app will now relaunch automatically.

• The cellular modem reboots every 20 minutes on S1F2 terminals with Android 9, which causes the terminal to be without cellular connectivity for up to two minutes. Payments made during this connectivity gap fail.

• We fixed the issue where installer notifications on the terminal did not align with the selected display notification settings in the Customer Area.

• The cellular modem reboots every 20 minutes on S1F2 terminals with Android 9, which causes the terminal to be without cellular connectivity for up to two minutes. Payments made during this connectivity gap fail.

• When surcharge applies for Simphony transactions in New Zealand and Australia, the OPI response now returns the surcharge amount in the fieldCCSurchargeAmount.
• It is now possible to perform referenced refunds on Oracle Opera transactions in Brazil and Mexico. Contact our Support Team to enable this feature.

• The instrument selection screen that replaces the present card screen is now generally available. It was previously only available in pilot mode.

• It is now possible to specify payment cards, for which the shopper can bypass the PIN entry on the terminal screen.

• We fixed the issue where the payment terminal did not automatically select Interac on co-badged cards in Canada. Instead, the terminal had asked the shopper to select a payment method.

• MIFARE Classic card payments fail and return the error Read EMV chip failed.

• The cellular modem reboots every 20 minutes on S1F2 terminals with Android 9, which causes the terminal to be without cellular connectivity for up to two minutes. Payments made during this connectivity gap fail.

• We fixed the issue where the result of a barcode scan did not output uppercase spelling when it should.

• The cellular modem reboots every 20 minutes on S1F2 terminals with Android 9, which causes the terminal to be without cellular connectivity for up to two minutes. Payments made during this connectivity gap fail.

• You can now enable Adyen's Auto Rescue mechanism to automatically retry failed store-and-forward payments to increase authorization rates.
• When a shopper presents a co-badged card, they can select the new Card option button on the terminal screen to select their preferred payment method.

• v1.109.8
  We fixed the issue where in some cases it was not possible to cancel Pay-at-table transactions.
• v1.109.10
  We fixed the issue where, when using Oracle Opera, a pre-auth transaction failed when it was followed by the transaction type Sales Complete.
• v1.109.10
  We fixed the issue where MOTO could not be disabled.
• v1.109.10
  We fixed the issue where it was impossible to make a recurring MOTO CVC payment.
• v1.109.10
  We fixed the issue where in some cases loyalty card payments were processed as regular payments.
• v1.109.11
  We fixed the issue where in some cases transactions with Interac cards failed. In the payments overview page, these failed payments were listed as Unknown card with refusal reason Declined offline.
• v1.109.12
  We fixed the issue where the payment terminal did not automatically select Interac on co-badged cards in Canada. Instead the terminal asked the shopper to select a payment method.

• Shoppers can now perform all gift card actions on standalone payment terminals.
• For Mifare Ultralight AES cards, you can now specify the ultralightAESKeyId in the NFCData field to access different parts of the card's data.

• v1.109.8
  We fixed the issue where updating the terminal firmware software from the terminal menu did not work.

• On Android terminals with a built-in barcode scanner, like S1E2L, you can now specify a prefix to be added to the scanned barcode content.
• When you press the barcode scanner button on Android terminals with a built-in barcode scanner, the barcode content can now be sent as simulated keyboard events.
• You can now upload logos and videos to show on the screen of the SFO1 payment terminal during steps of the shopper interaction.
• You can now customize virtual receipts on the SFO1 payment terminal.

• v1.109.7
  We fixed the issue where the user interface elements of some merchant apps were not rendering correctly.
• v1.109.8
  We fixed the issue where the result of a barcode scan did not output uppercase spelling when it should.

• v1.109.12
  We fixed the issue where S1F2 payment terminals with a third-party SIM card in the second SIM slot requested network connection with the incorrect Access Point Name (APN).
• v1.109.12
  We fixed the issue where the cellular modem rebooted every 20 minutes on S1F2 terminals with Android 9, which caused the terminal to be without cellular connectivity for up to two minutes. Payments made during this connectivity gap failed.
• v1.109.12
  We fixed the issue where in some cases contactless Girocard transactions failed on S1E, S1E2L, S1F2L, and S1U2 payment terminals.
• v1.109.12
  We fixed the issue where on AMS1 payment terminals the Scan QR button disappears from the instrument selection screen when the co-badged cards compliance feature was turned on. This occurred on terminals that had their language set to German, Italian, or French.

• The cellular modem reboots every 20 minutes on S1F2 terminals with Android 9, which causes the terminal to be without cellular connectivity for up to two minutes. Payments made during this connectivity gap fail.

• You can now reassign payment terminals from one store to another using the same one-time boarding password.
• We added the option to reassign a payment terminal to another store from the Settings menu of the terminal under Configuration > Reassign device.

• You can now check the Access Point Name (APN) in the terminal menu settings under Network > Cellular.

• We fixed the issue where the tipping screen showed the predefined tipping options as the percentage as well as the amount.

• This version is not stable for Android payment terminals. The user interface elements of some merchant apps are not rendering correctly.
• The cellular modem reboots every 20 minutes on S1F2 terminals with Android 9, which causes the terminal to be without cellular connectivity for up to two minutes. Payments made during this connectivity gap fail.

• In Japan, the payment response now includes installments information. Before, installments information were only included in additionalData.
• You can now configure the Adyen Giving feature in your Customer Area under Giving > Campaigns to use a single tap or double tap flow. Shoppers can now choose to donate a fixed amount or to round-up the amount of their original purchase.
• We introduced a new instrument selection screen to adhere to co-badged cards compliance in pilot mode. When this feature is enabled, it replaces the present card screen.

• We fixed the issue where Store and Forward transactions that were created on a software version lower than version 1.103 could not be processed after updating to a later software version. The stored transactions were discarded after 2 months.

• You can now reassign payment terminals from one store to another using the same one-time boarding password.
• We added the option to reassign a payment terminal to another store from the Settings menu of the terminal under Configuration > Reassign device.
• When using accessibility mode, Android payment terminals now provide audio feedback about how many PIN digits have been entered.

• We fixed the issue where a diagnostics call to an Android terminal did not return the correct IP address of the terminal.
• We fixed the issue where there was no endMaintenance event notification to inform about a finished maintenance call on S1U2 and S1F2L payment terminals.

• The Support for S1E and S1EL payment terminals ends with this software version. If you need help selecting alternative terminal models, contact your Adyen Account Manager.

• The tipping screen shows the predefined tipping options as the percentage as well as the amount. This issue will addressed in the upcoming version.

• In Estonia, you can now accept the shoppers' national ID cards as a loyalty card on non-Android payment terminals.

• v1.107.7
  To stay compliant with Greek tax regulations, we have enabled an integration with licensed e-invoicing systems that connect to the Greek Ministry of Finance.

• v1.107.7
  To stay compliant with Greek tax regulation, we have enabled an integration with licensed e-invoicing systems that connect to the Greek Ministry of Finance.

• Store and Forward transactions that were created on a software version lower than version 1.103 cannot be processed when updating to a later software version. The stored transactions will be discarded after 2 months.

• We fixed the issue where Adyen Giving donations could not be captured after the donation were processed.

• For gift card transactions, you can now use Manual Key Entry as an automatic fallback when swiping a card fails.

• Store and Forward transactions that were created on a software version lower than version 1.103 cannot be processed when updating to a later software version. The stored transactions will be discarded after 2 months.
• Adyen Giving donations cannot be captured after processing the donation.

• In Estonia, you can now use Android payment terminals to accept the national ID cards of the shoppers as loyalty cards.

• When using terminals in Kiosk mode, the lock task mode that hides the Android navigation bar is no longer enabled by default.

• When pre-authorizing a payment, you can now configure your terminal to automatically block specific types of payment cards, for example prepaid cards.

• v1.105.10
  We fixed the issue where recurring payments failed when using MKE as the entry method.
• v1.105.10
  We fixed the issue where in Japan VISA cards not issued in Japan showed on the payment terminal screen as payment options.
• v1.105.11
  We fixed the issue where Store and Forward transactions that were created on a software version lower than version 1.103 could not be processed after updating to a later software version. The stored transactions were discarded after 2 months.
• v1.105.12
  When putting cards in the penalty box, we fixed the issue where the incorrect card AID was banned.

• We fixed the issue where S1E2L and AMS1 payment terminals got stuck in a boot loop when their battery charge level was 5 percent or lower.
• v1.105.8
  We fixed the issue where Android payment terminals got stuck on the start-up screen when failing to update to a later software version.
• v1.105.8
  We fixed the issue where the buttons on the terminal screen used to select a credit or debit card option showed incorrect text.
• v1.105.10
  We fixed the issue where in some cases the time to start up a payment terminal took longer than expected after a configuration update.

• When a payment terminal gets stuck during start up, the terminal screen now shows an error message and a Retry button.
• When boarding a payment terminal with a one-time password fails, the terminal screen now shows the Settings button.
• You can now use Apple VAS payment flows for contactless and NFC wallet payments on Android terminals.
• Android terminals on Android 10 now support WebView version 123.0.6312.0.
• The status bar of test payment terminals now show a test icon.

• v1.105.8
  We fixed the issue where refunding or cancelling certain OPI transactions failed when they included manual key entry, tipping, or tax-free shopping flows.
• v1.105.10
  We fixed the issue where funds were not received from the shopper’s payment card when the transaction was initiated by OPI Retail or Oracle Simphony and the receipt was in Chinese language. This also caused the payment terminal to crash.

• v1.105.8
  On P400 Plus payment terminal, we fixed the issue where the touchscreen was not responding when trying to tip.
• v1.105.8
  We fixed the issue where the terminal screen turned off when a payment request was sent.
• v1.105.9
  We fixed the issue where users could access the Transactions menu without a passcode.

• When boarding with a one-time password, the payment terminal now tries to download the configuration for a limited amount of time. After the set limit, the terminal stops making call to Adyen and prompts your user to press Retry on the terminal screen.

• Store and Forward transactions that were created on a software version lower than version 1.103 cannot be processed when updating to a later software version. The stored transactions will be discarded after 2 months.

• For Pay at table, in your Customer Area you can now select either the Table number or Check number to retrieve the customer's bill on the payment terminal screens.

• Refunding or cancelling OPI transactions might fail when they include manual key entry, tipping, or tax-free shopping flows.

• S1E2L and AMS1 payment terminals get stuck in a boot loop when their battery charge level is five percent or lower.

• We fixed the issue where the transaction data could be accessed from the terminal menu without entering the Transactions passcode. You can manage your passcodes in the Customer Area or by using API calls.

• You can now exclude products and charges from the total amount that are not eligible for tipping. The terminal screen then shows the amount that the shopper can choose to tip on separately from the total amount.

• Store and Forward transactions that were created on a software version lower than version 1.103 cannot be processed when updating to a later software version. The stored transactions will be discarded after 2 months.

• In the terminal settings menu, we have fixed the issue where toggling DHCP on and off removed all previously stored IP addresses.

• From the menu of S1U2 and S1E2L payment terminals, you can now manage the performance of your Android apps. You can, for example, force quit an unresponsive app, or clear the cache and storage of an app.

• S1E2L and AMS1 payment terminals get stuck in a boot loop when their battery charge level is five percent or lower.

• Refunding or cancelling OPI transactions might fail when they include manual key entry, tipping, or tax-free shopping flows.

• We have removed classic libraries. If you need support, contact your Adyen Account Manager.

• You can now make a request to the /terminals endpoint to get the restartLocalTime which is when your payment terminals are set to reboot during the restart hour.

• On Android terminals that have a built-in barcode scanner, like S1E2L, you can now specify the type of separator for the scanned barcode content. You can pass the content of each scanned barcode in a new line, or specify the character to use a separator.

• For Mail Order/Telephone Order (MOTO) payments it is no longer possible to skip providing the shopper's information such as the postal code.

• S1E2L and AMS1 payment terminals get stuck in a boot loop when their battery charge level is five percent or lower.

• When overriding the preconfigured tipping options, we changed the structure of the Operation JSON object passed in the SaleToPOIData.

• Support for classic library integration ends with this software version. If you are still using the classic library integration, we recommend that you use the LTS version 1.100. If you need support, contact your Adyen Account Manager.

• The signatures of the receipts of transactions are only partially visible on the Payment details page in your Customer Area. In some cases, the receipt of a transaction is missing.
• S1E2L and AMS1 payment terminals get stuck in a boot loop when their battery charge level is five percent or lower.

• v1.100.7
  We fixed the issue where the gift card load reversal failed, when the load request was completed on a different terminal.

• This version supports an outdated format of the feature that lets you override the existing tipping options by specifying them in the payment request. A new format will be introduced in an upcoming release.

• v1.100.10
  We fixed the issue where Android terminal failed to start the payments app properly after reboot.
• v1.100.8
  We fixed the issue where terminals got stuck after being reassigned during the boarding process.
• v1.100.7
  We fixed the issue where in some cases the payment terminal made multiple authorisation calls on a single transaction and blocked the shopper’s card.

• v1.100.7
  We fixed the issue where the customer signature was only partially visible on the Payment details page in your Customer Area.

• v1.100.7
  We fixed the issue where in some cases the transaction receipt was missing on the Payment details page in your Customer Area.
• v1.100.7
  We fixed the issue where the button to view the last known Totals report was missing from the payment terminal menu after the Totals were reset at the reset hour.

• S1E2L and AMS1 payment terminals get stuck in a boot loop when their battery charge level is five percent or lower.

• v1.100.10
  We fixed the issue where the terminal screen turned off when a payment request is sent.
• v1.100.7
  We fixed the issue where in some cases the payment terminal randomly showed a black screen.

• v1.100.7
  We fixed the issue where, after using a standalone merchant reference and canceling the transaction on the amount input screen, the same reference was used automatically for the next transaction.

• On Android terminals that have a built-in barcode scanner, you can now activate the barcode scanner by pressing the side button. A successful scan enters the content of the barcode directly into the input box in your app.

• The signatures of the receipts of transactions are only partially visible on the Payment details page in your Customer Area. In some cases, the receipt of a transaction is missing.
• S1E2L and AMS1 payment terminals get stuck in a boot loop when their battery charge level is five percent or lower.

• You can now use Adyen payment terminals to read cards that are not compliant with PCI DSS, such as employee benefit cards.

• The receipts of transactions on the Payment details page in your Customer Area have no signature. In some cases, the receipt of a transaction is missing.
• S1E2L and AMS1 payment terminals get stuck in a boot loop when their battery charge level is five percent or lower.

• In Japan, when a transaction fails, the payment terminal now presents the shoppers with an instruction on how to resolve the failed transaction.

• We fixed the issue where the printed receipt showed “NULL” in the receipt header when you did not populate Header line 1 and Header line 2 under Customer Area > Terminal Settings > Receipts.
• We fixed the issue where contactless EFTPOS transactions fail on AMS1 payment terminals if PIN entry is required.

• The function button on the back of the S1U2, which is needed to access the device settings, is unresponsive.
• The receipts of transactions on the Payment details page in your Customer Area have no signature. In some cases, the receipt of a transaction is missing.
• S1E2L and AMS1 payment terminals get stuck in a boot loop when their battery charge level is five percent or lower.

• For contact payments surcharges are not applied which means that the surcharge fee is not transferred to the shopper.

• In the US, all payment terminals can now accept EMV Quick Chip transactions. This allows shoppers to insert and remove their EMV chip cards at checkout while the scanning of the goods is still in process.

• When updating to this version, the terminal files migration can get interrupted by another process. The payment terminal then shows a Transaction interrupted error message. On unattended payment terminals the Cancel button must be pressed to close this message.

• You no longer have to contact Support to update UX300 and UX410 payment terminals to the latest software version.

• UX400 payment terminals refuse transactions after updating to software version 1.95.5.

• We have introduced the S1U2 payment terminal to our terminal range.

• The receipts of transactions on the Payment details page in your Customer Area have no signature. In some cases, the receipt of a transaction is missing.
• S1E2L payment terminals get stuck in a boot loop when their battery charge level is five percent or lower.

• We fixed the issue where the timestamp on items in the transaction history shows UTC time instead of the actual time.

• In a local integration, you can now configure terminals to notify you when their IP address changes. The terminal sends a webhook to the endpoint that you choose with the ID and the new IP address of the terminal.

• You can now use a one-time password (OTP) to get the unique ID of a terminal to assign it to the correct store.

• v1.94.10
  We have fixed the issue where transactions continued to be processed as Store and Forward payments even after the payment terminal had re-connected to the network.

• When updating to this version, the terminal files migration can get interrupted by another process. The payment terminal then shows a Transaction interrupted error message. On unattended payment terminals the Cancel button must be pressed to close this message.

• When pre-authorising a payment, you can now configure your terminals to automatically detect if a payment method does not support authorization adjustment. The terminal then presents the customer with an option to choose a payment method that supports authorization adjustment.

We have fixed the issue where UX300 terminals lost network connection after the nightly reboot.

• You can now split a landscape display of a payment terminal, such as the M400, to show two display requests.

• You can now use a kiosk mode on payment terminals to:
  • Make an Android app that you uploaded to Adyen the default app on the terminal.
  • Hide the Android navigation buttons from the home screen.
  • Hide the Settings and Transactions menus buttons from the home screen.

• The receipts of transactions on the Payment details page in your Customer Area have no signature. In some cases, the receipt of a transaction is missing.
• The timestamp on items in the transaction history is two hours ahead of the actual time.
• The printed receipt shows “NULL” in the receipt header when you do not populate Header line 1 and Header line 2 under Customer Area > Terminal Settings > Receipts.
• S1F2 payment terminals lose connection to the Wi-Fi network after a software update, or after an update of the logo on the terminal screen.
• S1E2L payment terminals get stuck in a boot loop when their battery charge level is five percent or lower.

• When collecting shopper input on a terminal, you can now mask the input data on the terminal screen.
• You can now use a third-party SIM card in addition to the pre-installed Adyen SIM card in AMS1, S1U2, S1F2L, and S1EL2 payment terminals.

• When applying surcharges:
  • We enabled rounding up the payment amount up to three decimals instead of two.
  • The payment response now includes the surcharge amount in the TotalFeesAmount field.

• EMV offline transactions get discarded after three days without internet connection.
• The payment terminal’s approved screen shows longer than expected.
• Transactions continue to be processed as Store and Forward payments even after the payment terminal has re-connected to the network.
• When updating to this version, the terminal files migration can get interrupted by another process. The payment terminal then shows a Transaction interrupted error message. On unattended payment terminals the Cancel button must be pressed to close this message.

• You will now get notified when Anti-removal switches (ARS) are triggered on UX300 and UX400 payment terminals.

• We no longer support managed engagement.

• Merchant app installation fails on S1E and S1EL payment terminals.
• S1F2 payment terminals lose connection to the Wi-Fi network after a software update, or after an update of the logo on the terminal screen.

• We fixed the issue where the timestamp on items in the transaction history shows UTC time instead of the actual time.

• If there is a communication or technical issue, you can now get the ServiceID of the in-progress payment or card acquisition request. You can then use that ServiceID to cancel that in-progress request.

• If you want to tokenize a card, you can no longer include both the old and the new tokenization parameters in your payment request.

• We now support accepting payment surcharges on Android payment terminals.

• The timestamp on items in the transaction history show UTC time instead of the actual time.

• We fixed the issue where the first transaction after the installation of a merchant app failed.
• We fixed the issue where contact chip transactions were declined when using surcharge.
• v1.91.18
  We fixed the issue where you could not update or retrieve Wi-Fi or SIM card information for S1F2 and S1F2L payment terminals.
• v1.91.20
  We fixed the issue where S1F2 payment terminals lost connection to the Wi-Fi network after a software update, or after an update of the logo on the terminal screen.

• We fixed the issue on UX300 payment terminals where the screen showed an error message instead of the result of card acquisition.
• v1.91.18
  We fixed an issue that slowed down the performance of the terminals.

• We fixed the issue where transactions were declined when using magnetic stripe on eftpos cards.
• v1.91.18
  We fixed the issue where offline Store and Forward transactions were rejected after three days without internet connection.
• v1.91.20
  We fixed the issue where transactions were still processed as Store and Forward payments even after the payment terminal had re-connected to the network.
• v1.91.20
  We fixed the issue where EMV offline transactions were discarded after three days without internet connection.
• v1.91.20
  We fixed the issue where transactions canceled before presenting the card were showing in the Customer Area under Payments.
• v1.91.20
  We fixed the issue where in some scenarios the payment terminal’s approved screen showed longer than expected.
• v1.91.21
  We fixed the issue where the terminal files migration could get interrupted by another process when updating to this version. The payment terminal then showed a Transaction interrupted error message. On unattended payment terminals, the Cancel button had to be pressed to close this message.
• v1.91.21
  We fixed the issue where, in some cases, a transaction could not be canceled by pressing Cancel on the terminal screen.

• We fixed the issue where certain Visa payment cards in Canada and the US were rejected because they were identified as SVS gift cards.

• Starting with this version, all payment terminals are automatically upgraded to the new menu structure.

• We fixed the issue on UX410 payment terminals where using contactless magstripe cards failed the card acquisition and stopped the terminal from transacting until the next reboot.

• We fixed the issue where the totals fail to reset when you log out of your terminal.

• This version is not available for V400m terminals.

• Payment terminals updating from v1.75 will first update to v1.86 before updating to the later versions.

• You can no longer include HTML tags in the body of input requests.

• This version is not available for AMS1, S1F2, and S1F2L terminals.

• You cannot update or retrieve Wi-Fi or SIM card information for S1F2 and S1F2L payment terminals.

• Contact chip transactions are declined when using surcharge.

• You can now split the screen of a landscape payment terminal to show an input and a display request at the same time.

• The screen of the e285p payment terminal no longer keeps turning on and off when connected to Wi-Fi.

• We fixed the issue of Pay at table button not showing on the screen of payment terminals that use the old menu structure.

• You can no longer include HTML tags in the body of input requests.

• Payment terminals updating from v1.75 and earlier versions will first update to v1.86 before updating to this version.

• This version is not available for V400m and payment terminals that are on a manual update strategy.

• We fixed the issue where canceling the payment request during PIN entry made the payment terminal unresponsive.

• Contact chip transactions are declined when using surcharge.

• In Canada and the US, certain Visa payment cards are rejected because they are identified as SVS gift cards.

• We fixed the issue where HTML tags showed on the terminal screen during display requests.

• We fixed the issue where the payment terminal was not able to send the current status of the ongoing Adyen Giving transaction.

• We fixed the issue where HTML tags showed on the terminal screen during display requests.

• When connected to Wi-Fi, the screen of e285p payment terminal keeps turning on and off.

• The Pay at table button does not show on the screen of payment terminals that use the old menu structure.
  If you are using Pay at table, with either Terminal API or OPI integration, consider enabling the new menu structure or updating to v1.89.

• Canceling the payment request during PIN entry makes the payment terminal unresponsive. The terminal needs to be restarted to transact again.

• Contact chip transactions are declined when using surcharge.

• In Canada and the US, certain Visa payment cards are rejected because they are identified as SVS gift cards.

• We fixed the issue where sending the Abort Request without the MessageCategory field made the terminal reboot.

• We fixed the issue where additional characters were passed as part of the scanned barcode data in the additonalData of the Terminal API response.

• For Pay at table, you can now select in your Customer Area to show or hide the notification button on the payment terminal screen.
  When the notification button is hidden, you start a transaction by selecting the Confirm key
  on the keypad.

• For Pay at table, you can now select in your Customer Area to show or hide the Pay@Table button on the payment terminal screen.
  When the Pay@Table button is hidden, you start a transaction by selecting the Confirm key
  on the keypad.

• When connected to Wi-Fi, the screen of e285p payment terminal keeps turning on and off.

• The Pay at table button does not show on the screen of payment terminals that use the old menu structure.
  If you are using Pay at table, with either Terminal API or OPI integration, consider enabling the new menu structure or updating to v1.89.

• Canceling the payment request during PIN entry makes the payment terminal unresponsive. The terminal needs to be restarted to transact again.

• Contact chip transactions are declined when using surcharge.

• In Canada and the US, certain Visa payment cards are rejected because they are identified as SVS gift cards.

• When using the new menu structure, you now have to enter the Transactions passcode to make referenced refund from the Transaction History.

• When connected to Wi-Fi, the screen of e285p payment terminal keeps turning on and off.

• The Pay at table button does not show on the screen of payment terminals that use the old menu structure.
  If you are using Pay at table, with either Terminal API or OPI integration, consider enabling the new menu structure or updating to v1.89.

• You can now allow a third party to interact with your customers on your payment terminals without integrating with your POS system. A third party can send non-payment requests, like input and display requests, and receive notifications from your terminals. Using third-party interactions, the third party is able to gather feedback on your service or engage customers in your loyalty program.

• You can now add a flag to your payment request to hide the pre-authorized amount on the payment terminal screen.

• You can now use the same card tokenization system for point of sale as for ecommerce. This allows you to create a recurring contract for:
  • One-off transactions where a shopper can either store their payment details or pay in your website or app later.
  • Transactions that occur on a fixed schedule for a fixed or variable amount.
  • Transactions that occur on a non-fixed schedule and/or have variable amounts.

• Canceling the payment request during PIN entry makes the payment terminal unresponsive. The terminal needs to be restarted to transact again.

• In Canada and the US, certain Visa payment cards are rejected because they are identified as SVS gift cards.

• For Pay at Table, payment terminals now support refunds initiated from Oracle Symphony.

• We rearranged the menu options on the terminal, and changed the way you access the menus to align it with Android payment terminals.

• For V400m with Bluetooth base station, we improved the way you connect the payment terminal with your wired network using the base station. You now only need to dock the terminal into the base station and select Pair now.

• When connected to Wi-Fi, the screen of e285p payment terminal keeps turning on and off.

• Canceling the payment request during PIN entry makes the payment terminal unresponsive. The terminal needs to be restarted to transact again.

• We fixed the issue where Interac transactions were declined when certain fields were sent without a value.

• In Canada and the US, certain Visa payment cards are rejected because they are identified as SVS gift cards.
• For Interac and EFTPOS payments, the account type is in some cases automatically set to credit and the account type selection screen does not show. The account type selection screen also doesn’t show in cases in which the payment terminal cannot detect the payment card brands Interac and EFTPOS.

• With Pay-at-table payments, the options to pay the amount in total, split equally, or split unequally are presented on the same screen. While paying, you can now see how many splits there are left.

• With Pay-at-table payments, the options to pay the amount in total, split equally, or split unequally are presented on the same screen. While paying, you can now see how many splits there are left.

• When connected to Wi-Fi, the screen of e285p payment terminal keeps turning on and off.

• Interac transactions are declined when certain fields in the request are sent without a value.
• In Canada and the US, certain Visa payment cards are rejected because they are identified as SVS gift cards.
• For Interac and EFTPOS payments, the account type is in some cases automatically set to credit and the account type selection screen does not show. The account type selection screen also doesn’t show in cases in which the payment terminal cannot detect the payment card brands Interac and EFTPOS.

• For Mifare DESFire cards, you can now use our Android payment terminals to send read or write requests.

• We now support sending the secondary security code (SSC) data in the activation and load requests for Stored Value Solutions (SVS) gift cards.

• We fixed the format of the timestamps sent in the Terminal API notifications.

• To prevent declined card-not-present transactions, like MOTO, the payment request now includes the network transaction reference and the reason for the payment.

• On an S1E Barcode payment terminal, you can now activate the barcode-scanning camera by sending a Terminal API request.

• When connected to Wi-Fi, the screen of e285p payment terminal keeps turning on and off.

• Interac transactions are declined when certain fields in the request are sent without a value.
• In Canada and the US, certain Visa payment cards are rejected because they are identified as SVS gift cards.
• For Interac and EFTPOS payments, the account type is in some cases automatically set to credit and the account type selection screen does not show. The account type selection screen also doesn’t show in cases in which the payment terminal cannot detect the payment card brands Interac and EFTPOS.

• When sending read or write requests to Mifare cards, you can now create a session that spans multiple read/write requests to make them a single user interaction.

• You can now do a diagnostics of the payment terminal's hardware components like the chip card reader, swipe reader, and NFC antenna.

• You can now send a request to Android payment terminals to specifically get the unique identifier (UID) of Mifare cards.

• We extended the maximum character length of the Device Slogan on the terminal.

• The Device Slogan variable now correctly shows the serial number of the terminal.

• When tipping from a terminal, Swedish users no longer get multiple No tip buttons when entering low amounts.

• Making a card acquisition request before a refund no longer fails when the payment terminals is offline.

• When connected to Wi-Fi, the screen of e285p payment terminal keeps turning on and off.

• Interac transactions are declined when certain fields in the request are sent without a value.
• For Interac and EFTPOS payments, the account type is in some cases automatically set to credit and the account type selection screen does not show. The account type selection screen also doesn’t show in cases in which the payment terminal cannot detect the payment card brands Interac and EFTPOS.

• When sending read or write requests to Mifare cards, the response now returns the unique identifier (UID) of the card even if the request fails.

• You can now send a request to Mifare cards to specifically get the unique identifier (UID) of the card.

• On payment terminals, the virtual receipt now automatically scrolls to the bottom of the receipt. You can then use the scroll to go back and view each item.

• We fixed the issue where captures failed for payments made by scanning the barcode on SVS and ValueLink gift cards.

• Under Transactions > Totals, you can now view and print the last known Totals report even if you already reset the totals.

• On standalone payment terminals, we now support refunds for Mail Order/Telephone Order (MOTO) payments.

• When tipping on a terminal, shoppers now get a warning if the tip is higher than the predefined percentage. They can then choose to continue or adjust the tip.

• When connected to Wi-Fi, the screen of e285p payment terminal keeps turning on and off.

• Interac transactions are declined when certain fields in the request are sent without a value.
• For Interac and EFTPOS payments, the account type is in some cases automatically set to credit and the account type selection screen does not show. The account type selection screen also doesn’t show in cases in which the payment terminal cannot detect the payment card brands Interac and EFTPOS.

• You can now initiate payments from your Oracle Retail Xstore POS app for the following QR code wallet apps: Affirm, Pix (Brazil only), Swish, Twint, and Zip.

• To prevent fraud when making refunds on standalone payment terminals, you can set up a 6 digit passcode to protect access to the Refund option in the special payments menu.

• On your terminal, you can run a Local communications TLS test to check the TLS version, cipher, and URL used in your local communications integration.

• On Android terminals, you can now Run connection tests from Settings > Diagnostics menu.

• For Mifare Ultralight and Mifare Ultralight C cards, you can now use our payment terminals to do a single read or write action.

• You can now adjust the volume of your payment terminals. To enable this, contact our Support Team.

• In the Device info menu of your payment terminal, you can do a long-press to copy the values of the Serial number and Merchant account fields. You can then paste the values, for example, when setting up your POS app.

• If a terminal is malfunctioning, you can send us a diagnostic report from the Hardware diagnostics menu. This includes logs from the terminal that help us improve our software.

• On terminals that use the French language, in the Totals menu we now show the number of transactions for every transaction type.

• On terminals that use the Swedish language, we fixed the issue where the currency symbol next to the amount showed incorrectly.

• Captures fail for payments made by scanning the barcode on SVS and ValueLink gift cards. The payment is then automatically refunded after three days to the shopper's gift card.

• When making a Pay-at-table payment, payment terminals no longer get stuck in the middle of input requests.

• Captures fail for payments made by scanning the barcode on SVS and ValueLink gift cards. The payment is then automatically refunded after three days to the shopper's gift card.

• When making a Pay-at-table payment, payment terminals no longer get stuck in the middle of input requests.

• If a terminal is malfunctioning, you can now send us a diagnostic report from the Hardware diagnostics menu. This includes logs from the terminal that help us improve our software.

• Shoppers in the US can now select between debit or credit options when paying on a terminal.

• This version is not compatible with the following payment terminals: UX300 and UX410.

• For Mifare Classic cards, you can now use our payment terminals to do a single read or write action.

• The Settings menu on Android terminals now shows installed certificates as well as installed apps.

• We now support the following features for standalone Android terminals:
  • Mail Order/Telephone Order (MOTO)
  • Manually enter payments (MKE)
  • Payment with cashback
  • Bypass PIN entry
  • Bypass AID PRIO

• You can now see the Wi-Fi MAC address of the Android terminal in the Customer Area, under Settings > Connectivity > Wi-Fi.

• The Device Info menu on Android terminals now shows the details of the network it is connected to, specific for the type of network, Wi-Fi or cellular.

• Android terminals can now support multiple CA certificates for Enterprise EAP-TLS and Enterprise EAP-PEAP Wi-Fi profiles.

• When the IP address of the terminal changes, it is now updated in the Customer Area.

• You can now select the Hidden SSID flag to allow Android terminals to connect to networks with hidden SSID. You can enable it in the Customer Area under Terminal settings > Connectivity > Wi-Fi profiles, or using Management API.

• On Android terminals, on the Transactions > Totals screen, the referenced refunds no longer show zero for the total amount.

• WeChat Pay no longer shows as the payment method for transactions made with a Maestro card.

• When tipping on a terminal, shoppers now get a warning if the tip is higher that the predefined percentage. They can then choose to continue or adjust the tip.

• Terminal API now supports sending secondary security code (SSC) data in the payment request for Stored Value Solutions (SVS) gift cards. Previously, customers had to enter the security code on the terminal.

• You can now send a GetRating input request to show the rating screen asking the customer to select a value between 0 and 9 without needing to confirm the choice.

• Captures fail for payments made by scanning the barcode on SVS and ValueLink gift cards. The payment is then automatically refunded after three days to the shopper's gift card.

• This version is not compatible with Android payment terminals.

• We now support the printing of receipts in a layout specific to the Japanese market.

• You can now let Japanese shoppers choose on a terminal whether to pay the whole amount or split it into installments.

• When making the CardAcquisition request, the response no longer includes the warning that the SaleToPOIData field is not supported.

• When making a Pay-at-table payment with the Pay in cash option disabled, the payment terminal no longer gets stuck in the payment menu if you cancel the transaction.

• You can now send the following display requests on Android terminals:
  • Show an image on the terminal
  • Show a QR code on the terminal

• You can now present shoppers with an option to donate to a charity after they pay on a terminal.

• In the Customer Area, you can now add variables in the Device slogan field to automatically show the terminal serial number, store ID, or IP address on the screen of the terminal.

• When printing on a terminal, we fixed the scaling issue for images that are wider than 384 pixels.

• We fixed the issue where the language on the terminal failed to change to Norwegian after being selected in the Customer Area.

• For gift cards that require a signature, you can now ask for a signature either on the terminal screen or on the receipt.

• Manual Key Entry now supports entering card numbers of up to 24 digits, instead of 20.

• For declined meal voucher transactions, we now print the remaining balance on the receipt, even if the balance is 0.

• When transaction conditions in the payment request limit the accepted payment methods to card schemes, the icon to select a QR code payment method no longer shows for that transaction.

• You can now show a waiting screen on the terminal after display requests and payment requests. Previously, you could only show the waiting screen after input requests.

• Sending a full referenced refund request more than once now results in an error message that the transaction has already been reversed.

• We fixed an issue where terminals showed a black screen after an input request.

• The PSP reference we return for your requests now includes letters as well as numbers.

• For Oracle Simphony, we now pass the card alias to identify cards used in pre-authorizations and sale purchases. This enables issuing multiple checks/orders for the same table.

• For cloud integrations, we now have a mechanism where the terminal retries sending Terminal API requests and Terminal API event and display notifications after losing the WebSocket connection.

• You can now send the following input requests on Android terminals:
  • Multiple choice—multiple answers: lets you ask the shopper a question and allow them to select more than one answer.
  • Phone number: lets you ask the shopper to enter their phone number.
  • Rating: lets you ask the shopper or your staff to enter a numerical value from 0 to 10.

• We can now configure your Android terminals to hide decimal numbers for currencies that do not use minor units, or if it is customary to show round numbers.

• New payment method: Atome. For this QR code wallet we support the merchant-presented payment flows (initiated from the terminal, or from the POS system).

• On the merchant receipt, you can now print the name of the cardholder. This lets you minimize the risk of fraud by verifying that it matches the name of the shopper. To enable this, contact our Support Team.
• We improved the overall payment processing time by optimizing the generation of the receipt data.

• On the M400 terminal, we fixed the misalignment of the Admin menu icons.
• Terminals no longer crash if you send an empty DisplayOutput field in a display request. You now get an error message with a description of the issue.

• You can now use an InputRequest to ask the shopper or your staff to enter text, like an email address of the shopper.

• With QR code payments, we now show the logo of the used payment method below the QR code.
• In the GetDigit input request, you can now leave the DefaultInputString field empty.
• On the S1E, the navigation bar layout has been changed to be the same as on S1F2.

• The Device info QR code now includes the MAC address of the terminal.

• With Manual Key Entry transactions, we ensured that the amount is shown from the start throughout the flow. Also, when entering the card number, 16 digits will fit the screen.

• Standard webhooks now include the following fields for point-of-sale payments:

  • RecurringDetailReference
  • PaymentAccountReference
  • tokenTxVariant

• For Pay at Table, we improved the employee authentication flow:

  • If employees usually authenticate by swiping their employee card but do not have their card available, they can select the Cancel key to switch to entering their reference number. To switch back to swiping, they need to select the Cancel key again.
  • Employee numbers starting with one or more zeros are supported.

• For Pay at Table, when an itemized receipt is configured but no data is sent, the terminal will show "No data" and the total payment amount instead of a zero amount.

• The cloud icon on the display, which represents the WebSocket connection, is now more reliable. Previously the icon sometimes continued to show when there was no WebSocket connection anymore.

• Pressing and holding the Cancel key works as expected again: Battery-powered terminals turn off, and tethered terminals remain turned on.

• Surcharge didn't work for contactless transactions when single tap was configured.

• You can now use the terminal to get input from the shopper:
  • Ask for numeric input
  • Ask to select a single answer from a list
  • Ask for confirmation

• The support for cashback is extended to Mastercard and Visa transactions.

• You can now make an AdminRequest to create a session that spans multiple requests. The first implementation that we support, is to show a "waiting" screen on the terminal between requests. You can use this waiting screen in flows like Pay at Table to make it clear that the POS system is not unresponsive, it is just busy doing something that takes a bit of time.

• The tender options to override settings configured for NFC wallet passes should now be passed in SaleToPOIData instead of SaleToAcquirerData. The reason for this change is that the acquirer doesn't need to be aware this type of tender options. The following tender options are affected:

  • VASModeVASAndPayment
  • VASModeVASOrPayment
  • VASModeVASOnly
  • VASModePaymentOnly

  Other tender options still need to be passed in SaleToAcquirerData.

• We now interpret TransType 08 as a Reopen Closed Check operation. This means the capture is reversed, and the authorization is kept open so that you can capture a new amount against that authorization.

• The terminal keeps a list of devices that it connected to through Bluetooth pairing. When the list is full, the terminal won't connect when you try to pair it to a new device. When this happens we now show a message to explain the situation, and a hint to remove one of the other devices from the list.

• Fixed various rare issues with cellular connectivity.

• Terminals on software version 1.70.6 became unresponsive after a donation and continued to show the Donated screen.

• Reassigning a terminal to a different store caused the terminal to go into service mode.

• Bluetooth turned off automatically when a paired device was unpaired.

• We now support card acquisition on Android terminals.

• The terminal sometimes showed a prompt to select a launcher app.

• Added an input request that lets you ask the shopper to provide their signature on the terminal. This is similar to the Terminal API GetSignature input request.

• Added an input request that lets you ask the shopper to provide numeric input on the terminal. This is similar to the Terminal API GetDigit input request.

• This release includes a patch for a vulnerability in the Verifone NFC driver on UX payment terminals.

• You can now set a beep volume specifically for when the shopper leaves their card in the payment terminal, for example in a self-service kiosk.

• It is now possible to set the Wi-Fi frequency band that the terminal uses. Possible values are 2.4 GHz, 5.0 GHz, and Automatic. This enables you to resolve a situation where a network is not listed because the terminal is on a different frequency band. Contact our Support Team to enable this for you.

• The process for manually updating the base station is now smoother.
  When you update the terminal software and then place the terminal on the base station, the terminal prompts you to update the base station. The next time you place the terminal in the base station, the terminal will know you have updated the base station, and will no longer prompt again for an update.

• Renewal of the terminal certificate is now faster.
  When a terminal asks our backend for a new signed certificate, we temporarily reduce the maintenance interval to ensure the terminal receives the new certificate almost as soon as it is ready. The terminal will then reboot immediately, to load the new certificate.

• We made some changes in the power management, to prevent intermittent blinking of the terminal.

• We fixed an issue where the Wi-Fi driver sometimes crashed and caused 'failed to go online' errors.

• Added support for printing a logo on the receipt. You can upload the logo in your Customer Area > In-person payments > Terminal settings > Receipts.

• The Totals report that is available on the terminal now includes the terminal serial number.

• We restyled the button to start a refund in a standalone solution. For three seconds, Refund will show next to the icon.
  

• The magstripe reader failed to read Givex gift cards.

• After trying a contactless transaction, shoppers often had to fall back to a contact transaction.

• The terminal sometimes shows a prompt to select a launcher app. This will be solved in the next release. In the meantime, when this prompt appears: Select Adyen and confirm with Always.

• Partial referenced refunds are now added to the referenced refunds total in the Totals report.

• The QR code payment screen is now consistent across terminal models.

• When the magnetic stripe reader is used, eftpos now requires authentication with the PIN. Other payment methods may follow suit. For this reason, we introduced a setting that triggers the terminal to ask for the PIN when a card is swiped. Ask our Support Team to configure this for you.

• The new GetAmount input request lets the shopper enter an amount with decimals. The terminal shows the currency and a placeholder amount.

• For the multiple choice—multiple answers input request the MinLength and MaxLength parameters are now enforced. These let you manage the number of options the shopper can select.

• The gift card number is now shown in PaymentInstrumentData.CardData.SensitiveCardData.PAN. For existing integrations, we continue to show the gift card number in StoredValueAccountID.StoredValueID as well.

• You can now configure Pay at table so that your staff can authenticate by swiping their employee card.

• You can now create recurring details for a shopper while offline, through Store and Forward. You'd use this for loyalty use cases or later recurring payments. A requirement is that Store and Forward is enabled for payments that normally require a PIN as CVM.

• The terminal now shows the new logo for the QR code wallet Affirm.

• If you are using surcharge it is now possible to skip the screen that asks the shopper to agree with the surcharge.

• Printed receipts didn't include details specific for Oney payments.

• You can now use airplane mode to quickly turn all network connections off and on. When enabled, this option is included in the Settings > Network menu.

• We added support for tipping by asking for a total amount.

• The diagnosis response for an S1F2 payment terminal now includes the PrinterStatus.

• Fixed an issue where authorization rates showed a drop between midnight and 2:00 AM.

• By adding some fields, you can use the GetMenuEntry input request to let the shopper select multiple options from a menu, instead of only one option.

• We support V400m terminals with a German keypad. German keypads have a different letter mapping. For example, to get the letter Q you'd press the 7 key three times. On a standard keypad, you'd press the 1 key two times.

• Because some certificates were about to expire, we have updated the Mozilla Certificate Authority tree used to authenticate incoming TLS requests.

• For cloud integrations, we have improved the mechanism used by the terminal to reconnect if it loses the WebSocket connection.

• V400m Bluetooth base stations now reboot every night and after every software update. This improves operational stability.

• UX410 terminals sometimes got stuck when a card acquisition request was made.

• When an in-progress transaction was interrupted, this sometimes caused a boot loop.

• We now show the correct message after a Bluetooth PAN or tethering connection is established, and correctly show the Bluetooth status of the terminal after unpairing a Bluetooth device.

• A printed Totals report now includes the From and To dates of the reporting period.

• When using a white background image, the names of the Adyen menus on the home screen were not clearly visible.

• To prevent unnecessary declined payments, we brought the ecommerce concept of the penalty box to point of sale.
  When a payment network connection is unavailable, we put the payment method in our platform's penalty box. Ecommerce payments are then routed through other connections until the problem is resolved. Previously, the payment terminal was unaware of the penalty box and would try using the unavailable payment method regardless. Now, we inform the terminal. It will then try offline processing, or with co-badged cards the terminal will route the payment to another payment method. For example, the terminal skips a local payment method that is temporarily unavailable and uses a global card scheme instead.

• For Synchrony private label credit cards and co-badged credit cards, we support account number lookup and card signup.

• We improved the design for tipping screens, to standardize the screens across terminal models and flows. There is no functional change.

• We now provide better feedback in the payment response when an unsupported gift card is presented for a payment.

• The card acquisition response for a contactless Interac card returned the card type incorrectly.

• We fixed an issue where the payment response didn't contain the masked PAN and the BIN for cards with a short PAN (less than 15 digits).

• We broadened the scope of the release testing for OPI integrations.

• Android terminals support WebView version 91.0.4472.88.

• You can customize after how many minutes of inactivity the terminal goes to sleep mode. Contact our Support Team to configure this for you.

• We updated Settings > Config and Settings > Device info > Software:
  • When you select these options, the terminal immediately checks for available updates and shows the actions you can take.
  • The terminal also shows suggestions about what you can do when an action didn't succeed.
  • When you remove the configuration, you'll first see a warning and afterwards you can board the terminal again.

• New feature: Surcharge. The terminal will add a percentage or fixed amount (or both) to the transaction amount and show a screen for the shopper to accept or decline. Contact our Support Team to configure this for you.

• We support some additional Nets gift cards.

• After logging in with a TotalsGroupID, a GetTotals request with that same TotalsGroupID didn't return the totals for the session with that totals group ID.

• After a transaction failed because the payment method wasn't supported, the terminal didn't accept a new payment request.

• When swiping a gift card after a card acquisition request, the giftcardTrack1 and giftcardTrack2 parameters were missing from the additional response.

• With the new GetRating input request you can use the payment terminal to conduct NPS surveys.

• For gift card transactions we now return the unmasked PAN of the gift card, provided your account is set up to add this to the response.

• Referenced refunds were correctly processed on our platform, but the RRN field in the response contained too many characters, causing the POS system to treat the transaction as failed.

• We improved the French text on some screens.

• We improved the screen that lets the shopper provide their signature on the display, and the screen that lets you check if the signatures match.

• The donations flow now shows two new screens:

  • Donated after completing the donation payment (instead of Approved).
  • Take your card (instead of Thank you, take your card) if the shopper declines to donate and they dipped their card.

• When a remote Wi-Fi profile was added while the terminal was connected to a local Wi-Fi network, the connection status in the Network > Wi-Fi menu wasn't always clear.
  We now make sure the connected network is listed first and has a green dot next to the signal strength icon .
  If other networks listed under Saved networks are in range, they are shown with a signal strength icon .

• We fixed some UI bugs on M400 and e280 terminals. For example, the wrong background color for a screen or an icon, or a white line showing at the bottom of a screen.

• You can now show a device slogan on the terminal display. For example, to visually identify the terminal. You can specify the text in your Customer Area on the Settings page for the specific terminal, under Customization.

• We improved the Settings > Apps menu. When you open this menu, the terminal checks for and downloads any updates to your apps. You can then close the menu; you do not have to wait for the download to finish.

• You can now print a shopper or merchant receipt from the Transactions menu by selecting the transaction and then the document icon.

• We fixed a bug in the support of remote Wi-Fi profiles.

• The Totals report on the terminal no longer shows Giving donations mixed with regular payments.

• When you use direct tipping after card entry, our Support Team can now enable single tap. This ensures that for a contactless payment shoppers do not need to tap their card again after specifying a tip.

• In some scenarios issues occurred when the terminal tried to reconnect to WebSockets.

• You can send temporary shopping pass data in a payment request. For this you can use the CardData object in PaymentRequest.PaymentData.PaymentInstrumentData.

• When using terminals with P2PE encryption a diagnosis request returns the version number of the software, the vault, the SRED, the AppManager, and the Open Protocol used on the terminal.

• Making a display request to show a QR code on the terminal is now supported on all Engage terminals.

• Fixed an issue that approved an unreferenced refund to a QR code wallet in the merchant-presented flows.

• In the tax-free shopping flow we automatically send an input request to the terminal asking the shopper for their consent to share card details with the TFS provider. If the shopper declines, we automatically update the taxfree.indicator flag in the subsequent payment request to false.

• We improved the performance of cellular communications for some specific scenarios.

• e280: After switching to sleep mode, the terminal didn't wake up when the user pressed the power button.

• e280: Volume settings reverted to the maximum after switching the terminal off and on again.

• e285: With automatic network selection for cellular connectivity, the terminal tries to use the strongest connection that the terminal model supports. On e285 terminals this is 3G, but is was shown on the terminal display as 4G.

• When a static IP address was configured, DHCP remained shown as enabled on the Device info screen.

• You can change the screen brightness on the terminal.

• In Adyen > Totals, you can reset the totals report. On the S1F2 you can also print the totals report.

• On the S1F2 you can select a transaction under Adyen > Transactions and then print the shopper and merchant receipts.

• When boarding a terminal, users can now search for their store.

• DCC receipts were non-compliant because our company name appeared as Adyen instead of Adyen N.V.

• We returned the issuer country/region as a code of three digits instead three letters.