Configure Denmark Direct Debit Type Payment Pages 2.0

Knowledge Center > Billing and Payments > Hosted Payment Pages > Payment Pages 2.0 > Configure Payment Pages 2.0 > Configure Denmark Direct Debit Type Payment Pages 2.0

Configure Denmark Direct Debit Type Payment Pages 2.0

This article describes how to configure Payment Pages 2.0 to accept the Denmark Direct Debit (Betalingsservice) type payments.


  • Before any integration work can begin, the Payment Page form must be set up in Zuora.
  • A GoCardless payment gateway instance has been created in your Zuora tenant. See Setting Up Payment Gateways for more information

Create New Payment Page

To create a Payment Pages 2.0 form:

  1. In Zuora, navigate to Settings > Payments, and click Setup Hosted Pages.
  2. In the Type field, click and select Bank Transfer-Betalingsservice. See Payment Methods to learn more about the payment type.
    If your tenant has both Payment Pages 1.0 and Payment Pages 2.0 enabled, you can see the Hosted Page 1.0 and Hosted Page 2.0 categories.
    You need to have the Bank Transfer tenant permission enabled to create a Payment Page of the bank transfer type.
  3. Click create new hosted page.
  4. 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: Zuora validates this field for you. You will see an error message displayed on HPM iframe if the validation fails. 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 if 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.
  5. In the Security Information area, configure the following information:  
    • Limit the number of submission before CAPTCHA Challenge: Enter a threshold for the number of Payment Page submissions before the CAPTCHA challenge page is displayed on HPM iframe. 
    • Limit the number of submission before blocking Submission: Enter a threshold for the number of Payment Page submissions before Zuora blocks all subsequent requests. 
      For more information, see Configure Advanced Security Checks for Payment Pages 2.0.
  6. In the Payment Gateway area, enter the following information:
    • Payment Gateway: Select the created GoCardless payment gateway instance because Betalingsservice is supported by only the GoCardless payment gateway integration in Zuora. Note that Zuora does not validate this setting. 
  7. In the Page Configuration area, enter the following information.
    HPM configuration for Betalingsservice and Autogiro
    • Page Title: Type a title for the Payment Page form. Select Display to display the Page Tile on this Payment Page form.
    • Page Description: Type a description for the form. Select Display to display the Page Description on this Payment Page form.
    • For each field in the Page Fields section:
      • Label Name: Enter the display label to be shown on this Payment Page.
      • Display: Select to display the field on the Payment Page.
      • Required: Select to make the field a required field.
      • Specifically, the Identity Number field is added for Autogiro. It is a required field and corresponds to the national identity number of Danish customers.
      • If you want to change the default display order of the input fields within a section, such as in the Bank Account Information or Customer Information section, enter the number representing the display order of the field within the section.
      • If you want to change the display order of the sections, in the order field next to the section, enter the number representing the display order of the section on this Payment Page.
    • Submit Button: Type the label to appear on the 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 the parameter, submitEnabled, 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. 
      • Use the variable,  #fieldName, in the error message to include the missing field name. 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.
    • 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 Page 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.

  8. Click generate and save page.

The Preview Payment Pages 2.0 page shows the page as it would be displayed on your website. 

Last modified


This page has no custom tags.


(not set)