Integrate using payment pages
Accept payments using customizable payment page prepared by Unzer.
Payment Page v1 will be deprecated soon.
- If you have an existing integration, go to the Migration guide for more details.
- If you are integrating for the first time, follow the specific guide for hosted, embedded, or link pay to learn more about the next steps.
The payment page is a ready-made webpage that allows you to offer your customers a variety of payment methods without implementing each one of them separately. This makes it one of the quickest ways to integrate.
With a payment page, the data of your customer is secure and forms are carefully designed and optimized, displayed correctly in all major browsers. You don’t need to update your code when there’s a new browser version—Unzer takes care of that.
The payment page is customizable, enabling you to add your own branding, matching corporate style, or personal preferences.
Comparison of Embedded and Hosted Payment Page
There are two types of payment pages: Embedded Payment Page (EPP) and Hosted Payment Page (HPP). The EPP displays payment options directly in your online shop using a website overlay, while HPP shows them on an external webpage hosted by Unzer.
The following table compares the EPP and HPP:
| Feature | Embedded Payment Page (EPP) | Hosted Payment Page (HPP) | LinkPay |
|---|---|---|---|
| Appearance of the page | Appears as if hosted on your site | Leaving your shop | Leaving your shop |
| Customization options | More customizable UI, allowing merchants to tailor the overlay. | Limited customization options for the payment page. | Customizable link with defined validity. |
| Payment Link | No unique URL; integrated directly into the site. | Unique URL created for each transaction. | Common URL that can be reused, with an expiration date. |
| Use Cases | Suitable for seamless checkout experiences. | Ideal for standard e-commerce transactions. | Best for invoice payments or donations. |
| Setup Complexity | More complex due to the need for overlay integration. | Generally simpler to set up, as it requires less customization. | Requires API calls to generate payment links. |
| Customer experience | After selecting the Pay button, the customer can see the payment page open as an overlay on the current website. | After selecting the Pay button, the customer is redirected to the payment page hosted by Unzer. The customer sees your company branding, but on Unzer’s URL. | After selecting the Pay button, a link and a QR code are created that the customer can use to make the payment. |
| Examples (select the image to enlarge it) |  |  |  |