Interested in automatic updating?
Contact the Support Team to find out which update strategy you are following or to switch to automatic updating.
To ensure you benefit from latest features, improvements, and fixes, you need to keep your terminals up-to-date with the latest software release. A new version is released approximately every month, after rigorous testing.
- Update automatically: when the new release is stable, we update your terminals overnight in multiple stages spread over a three-week period. This is the default setting for new accounts.
- Update manually: you request and test the new release yourself. To update terminals to a version, you need to contact us in advance.
Every release goes through rigorous testing:
- Phase 1, robot testing. We have over 40 robots performing test transactions for thousands of test cases on the supported terminal models in different integrations.
- Phase 2, manual checks. For example, we test upgrading and boarding, check all screens, and do many test and live transactions with various card types and card entry modes.
- Phase 3, beta testing. For merchants participating in the beta testing program, we release the latest version to live terminals in multiple countries. This allows us to monitor the transaction performance and the communication with acquirers and issuers.
When all test phases are successful, we consider the release to be stable.
The beta testing program lets us test the latest release in a live environment, monitor the performance of payment terminals, and discover potential issues at an earlier stage. The terminals that are part of the beta testing are updated to the latest version in the first stage of the automatic update process.
Setting up and running the beta testing program requires no extra effort from your side. The whole process is handled by Adyen.
For you, participating in the beta testing program has the following benefits:
- The earliest access to the latest features.
- Testing and bug fixing specific to your industry.
- The highest priority with IPP Support.
- Dedicated monitoring during the beta test.
In rare cases of potential issues related to software updates, to avoid impact on your business operations we have the following strategies in place:
- To ensure business continuity, we try to select the terminals from stores with at least 2 other active terminals.
- If the update fails, the terminals continue to transact using the previous software version.
- In case of unexpected issues, we can pause the update process or revert to a previous release at any time.
In addition to the benefits of the beta testing program, we also have some expectations from you during this stage:
- Report issues diligently. You have priority when reporting issues to POS Support.
- Keep the beta terminals always active.
- Inform your personnel which terminals are part of the beta testing program.
- Instruct your personnel on how to report issues to Adyen.
All of this helps us improve the current version before the official release.
After we test a release version and tag it stable, we update your terminals in several stages and outside business hours.
Automatic updating has the following benefits:
- Faster troubleshooting. The terminal is already on the latest release, so the Support Team immediately starts looking for solutions. There is no trying to fix the issue by updating to the latest release first.
- Compliance with the latest scheme regulations.
- Lower update risk. The improvements from one release to the next are smaller compared to a manual updating process where releases are often skipped.
- Convenience. You don't have to do anything.
- You never miss vital updates.
How it works
Automatic updating is done in four stages:
- Stage 1 - beta testing merchants. We update up to 5% of the payment terminals to the latest beta software version. If any issues are discovered, we fix them before releasing the first stable version in stage 2.
- Stage 2 - all merchants. This is the first stage that includes terminals that are not part of the beta testing program. The process is the following:
- At the start of a work week, after publishing the release notes, we release the first stable version. Unlike stage 1, issues discovered in this stage will not be fixed until the next software version.
- We target terminals that are not the busiest ones but process enough volume for us to monitor the performance. With you, we only select terminals at locations where with back-up terminals.
- We update 5–20% of your terminal fleet. For example, one terminal of each model per country and all test terminals. For stores with a single terminal, we select locations close to your headquarters.
- You can also choose to include only test terminals in stage 2. This gives you about a week to test the release before we update your live terminals in the next stages.
- Stage 3 - all merchants. A week after stage 2, we update another 20–30% of your terminal fleet. For example, one terminal in each store, or all terminals in stores that had a terminal in stage 2.
- Stage 4 - all merchants. A week after stage 3, we update the remaining active terminals including the ones that are not yet boarded.
We never update your terminals on Friday or Saturday nights or during busy periods. When we push a release, the terminal automatically installs the new software after rebooting at the restart hour. The restart hour is configured in your Customer Area, and is usually set to 6:00 AM.
To update successfully, the terminal needs to be turned on and connected to your network for at least one maintenance interval (by default 180 minutes) before the restart hour. If the update fails, the terminal will run as before on the previous software version. We will notice this, and schedule an update for the next night.
In case of unexpected issues, we can pause the update process or revert to a previous release at any time. When you are ready to follow automatic updates again, you can contact the Support Team.
With manual updating you submit an update plan in your Customer Area each time you want to update a number of terminals to a new release. For more information, refer to Manually schedule terminal software updates.
You need to submit a manual update request at least two working days in advance.
Unlike automatic updating, we don't actively monitor terminals that are updated manually. This approach can be suitable for specific integrations, but we would need to determine that in a discussion with you.
To prevent terminals from running on software that is not compliant or that we no longer support, keep your terminals updated to one of the latest three to five releases.
Possibly your terminals are on a manual updating strategy because automatic updating wasn't available when you set up your account. In that case, we recommend switching to automatic updating.