Configure iDEAL type Payment Pages 2.0

Prerequisites

An Adyen v2.0 gateway instance has been created on your Zuora tenant. For now, iDEAL payment methods are supported only on Adyen v2.0 gateway integrations.

Create an iDEAL type of Payment Page

Before any integration work can begin, set up a Payment Page 2.0 in Zuora:

1. Navigate to Settings > Payments, and click Setup Payment Page and Payment Link.
2. On the Payment Pages tab page, configure the tenant-level settings for the hosted payment page.
3. In the Type dropdown list, select iDEAL.
4. Click create new hosted page.
5. In the Basic Information area, enter the following information:
   • Page Name: Type a name for your Payment Page form. This name is used to identify your form in Zuora. It is different from the title displayed on the form. You specify the form title in the Page Title field in the Page Configuration section.
   • Hosted Domain: Type the domain address from which your Payment Page will be served. This is also the domain where your callback page resides. The value should be in the format: https://www.domain.com. Zuora validates this field for you. You will see an error message displayed on HPM iframe if the validation fails.

     To allow your hosted payment pages and callback pages to reside in the subdomain of the hosted domain, enable the Allow Subdomain Callback for Hosted Pages setting. See Configure Payment Pages 2.0 for details.

     Note that the Overlay Hosted Page mode does not support the Hosted Domain validation.

   • Callback Path: Type the path on which the callback page file resides. Zuora appends this to the Hosted Domain entry to create the full URL to which the callback is sent. Specify a value in the format: /app/callback_file.jsp. You are not required to include a file extension, for example, .jsp or .php. However, the callback path must begin with a forward slash character ( / ).

     The Callback Path is only required when you are using the advanced implementation option, using the inline style form with an external submit button. The Callback Path setting is ignored when you implement the basic setup, i.e., using the overlay form or the inline form with the submit button inside.

6. In the Security Information area, configure the page-level security settings. For detailed information about each option, see Security Measures for Payment Pages 2.0.
7. In the Payment Gateway area, click the Default Payment Gateway field and select an Adyen v2.0 instance. Note that Zuora does not validate this setting. You can override this default gateway in your request by specifying a gateway through the paymentGateway client parameter.
8. In the Page Configuration area, complete the field configuration. Except for the following fields, you do not need to configure any form fields because the card issuer drop-down list is the only field on your hosted payment page and the list will be automatically loaded when your payment page is rendered.
   • Page Title: Enter a title for the Payment Page form. Select Display to display the Page Title on this Payment Page form.
   • Page Description: Enter the description of the form. Select Display to display the Page Description on this Payment Page form.
   • Submit Button: This label is applied only if the button is on the Payment Page form. See Client Parameters for Payment Pages 2.0 for information about the submitEnabled parameter that controls the placement of the submit button.
   • Client-Side Validation: Select Enable client-side validation to check the required fields for values.
     • If the client-side validation is enabled, you can specify a custom error message for missing required fields in the Error Message field.
     • In the Error Message field, use "#fieldName" to include the missing field name in the error message. For example, "Please enter a valid #fieldName to continue."
   • Confirmation Dialog: Select Enable Confirmation Dialog to add a step to display a confirmation dialog in the Payment Page workflow. When this step is enabled, your customers get a chance to confirm the information they entered before submitting the payment method.

     When you select Enable Confirmation Dialog, the template editor appears. Customize the Confirmation Dialog by typing in the desired information in the template editor, such as the page heading, your merchant name, etc. If you want to customize the CSS style of the Confirmation Dialog, add the customized CSS to the CSS field. The default behavior of the Cancel button is closing the confirmation dialog and allowing the end user to edit the account information again. If you want to customize the logic, you can use the onCancelMandatePage event handler in your client code.

     The Retrieve Mandate PDF field only works for bank transfer type of hosted payment pages on GoCardless. Do not select this field to avoid errors.

   • CSS: Enter the custom CSS code for your page. You can review the CSS id and class names by using View Source or Inspect Element in Firefox or Chrome on the preview page of this Payment Pages form. For example, you can customize the style and format of the field label and error message, as well as the error message texts. However, implementing customized JavaScript is not allowed for security reasons.

     Design Payment Pages CSS provides a CSS pack that you can download and use to design the look and formatting of your Payment Pages 2.0 form.

     Ensure that you enter the valid CSS codes in this field. An error will occur if you include HTML tags or other invalid characters.

9. Click generate and save page.

Subsequently, you can preview Payment Pages 2.0 to preview the form that will be displayed on your website. 

What's next

Because iDEAL payment methods on Adyen v2.0 can only be created through the one-time payment flow of Payment Pages 2.0, you must implement a one-time payment flow after you create the iDEAL type of hosted payment page. For details, see Implement one-time payment flows on Adyen v2.0.