The Hosted Payment Pages (HPP) integration is deprecated. This means we are:
- No longer developing the HPP integration.
- Not accepting new HPP integrations.
We will announce the end-of-life plan around October 2021.
If you already have a live HPP integration, we will contact you to discuss your options for migrating to our newest integration. From the moment we announce the end-of-life plan, you will have approximately 12 months to migrate.
Benefits of migrating
Get the latest features
We are no longer developing the HPP integration. Our developers are working on the newest integration which has:
We are building new features, making security improvements, and optimizing performance. For example, HPP does not support Apple Pay, Amazon Pay, and the native 3D Secure 2 flow, which are all available on the newest integration.
With weekly release cycles for the Checkout API, you immediately get access to new payment methods, new features, and fixes.
Higher conversion rate
Our data shows Drop-in and Components integrations have better conversion rates than HPP. Merchants who switched to Drop-in and Components have seen a conversion increase between 3.6% and 15%.
The redirect to the hosted payment page causes lower conversion rates for HPP integrations. Shoppers sometimes perceive the redirect as unreliable, making them abandon the checkout process.
Drop-in and Components have an embedded checkout flow, which means the payment form is part of your website. This is perceived as more trustworthy, leading to an increase in conversion rate.
Higher authorization rate
The HPP payment form does not have built-in validation for input fields. The validation happens after the payment details are submitted, leading to a declined transaction if there is any invalid information.
Drop-in and Components have built-in validation for the payment form. This means the shopper gets instant feedback and can fix the input if needed. The shopper can only submit the payment if all validations pass, eliminating declined transactions caused by shopper error.
For example, Drop-in and Components validation includes checking if the:
- Card number is valid.
- Card brand the shopper wants to pay with is a card brand you accept.
- The required address fields are filled in, based on country requirements.
Improved support and monitoring
An HPP integration is harder to troubleshoot, so resolving issues takes longer than for Drop-in or Components.
Improved monitoring for the Checkout API allows our support team to more easily reproduce and investigate issues. The architecture of Drop-in and Components also makes troubleshooting easier which together allow our support team to resolve issues faster.