The HPP integration has reached end-of-life. This means we are:
- No longer developing the HPP integration.
- Not accepting new HPP integrations.
- Preparing to stop accepting transactions using HPP.
The next important dates are:
- 1 July 2022 - No more support provided for HPP.
- 1 October 2022 - No more transactions allowed for HPP.
1. Find out how you're using HPP
If you know that you have an HPP integration or received an email from Adyen about live traffic on HPP, that means the deprecation applies to you. Contact our Support Team if you need help with identifying your HPP traffic.
If you integrated using a plugin or through a partner, find out more about what actions you need to take.
2. Choose a new integration
There are many benefits to migrating from HPP to a newer integration, including higher conversion rates and compliance with the latest industry standards.
Try our interactive guide to get a recommendation for your new integration based on your business needs.
3. Replace your HPP integration
Learn about replacing your HPP integration by watching our webinar on-demand. Request the recording on Adyen Education > HPP to Checkout tab.
Need help to migrate?
Our Support Team can help you find a system integrator.
Build an integration to replace HPP:
When replacing your HPP integration, you do not need to change your:
- Account structure
- Payment method setup
- System messages setup
- Payout settings
- Reporting and reconciliation setup
- Risk profile
4. Submit PCI DSS validation documentation
The complexity of the documentation you need to submit depends on the new integration you choose.
You must submit the PCI DSS validation documentation before going live with your new integration. Contact our Support Team to get the prefilled PCI DSS documentation you need to sign.
If you move your HPP traffic to another Adyen integration for which you are already providing annual validation documentation, then you most likely don't need to submit additional validation documentation.
Exceptions for deprecation
The following integrations are not being deprecated, so you can continue using: