Internet Paperless Direct Debit

The Internet Paperless Direct Debit (IPDD) service provides a secure, BACS‑compliant flow for creating Direct Debit Instructions (DDIs) online — without requiring paper mandates or custom UI development. The service validates customer data in real time, ensures the correct presentation of mandated text, and submits DDIs via PayPoint’s accredited gateway.

Developers can integrate using either a hosted redirect flow or a modern embedded component, with support for prefilled customer and schedule data, flexible orchestration, and real-time validation.

How IPDD Works

IPDD is a hosted orchestration layer that abstracts all Direct Debit mandate creation logic. When a customer enters their details, IPDD performs:

Real‑time validation

  • Payer Name Verification

  • Bank Modulus Validation

  • EISCD Sort Code lookup

  • Schedule, interval, and amount validation

  • Compliance verification (SUN display, DDI guarantee, mandated layouts)

Secure mandate creation

Once validated, IPDD automatically generates and submits the Direct Debit Instruction (DDI) to BACS via PayPoint’s accredited service.

Regulatory compliance out‑of‑the‑box

IPDD ensures:

  • The Direct Debit Guarantee is displayed correctly

  • The Service User Number (SUN) and bank details are presented in the required format

  • Pages meet accessibility and regulatory display requirements

  • No customer information bypasses compliance controls

Hosted Redirect Integration

This is the fastest way to integrate IPDD. Redirect customers to:

https://{clientname}.directdebits.paypoint.com/

Customers enter all required details directly on the hosted page.

If you want to pre-populate schedule, customer, or instruction metadata, POST to the orchestration endpoint:

https://{clientname}.directdebits.paypoint.com/Orchestration/Post

HTML Form Example

<form method="post" action="https://{clientname}.directdebits.paypoint.com/Orchestration/Post">
  <input type="hidden" name="orchestration_type" value="IPDD" />
  <input type="hidden" id="instructionReference" name="DirectDebit_DDInstruction" value="" />
  <input type="hidden" id="customerAccountId" name="DirectDebit_CustomerAccountId" value="" />
  <input type="hidden" id="startDate" name="Schedule_StartDate" value="" />
  <input type="hidden" id="endDate" name="Schedule_EndDate" value="" />
  <input type="hidden" id="amount" name="Schedule_Amount" value="" />
  <input type="hidden" id="intervalUnit" name="Schedule_IntervalUnit" value="" />
  <input type="hidden" id="interval" name="Schedule_Interval" value="" />
  <input type="hidden" name="AdHoc" value="false" />
<button type="submit">Setup a Direct Debit</button>
</form>

Field Descriptions

  • DirectDebit_DDInstruction - string - Your unique reference to help you identity an instruction.

  • DirectDebit_CustomerAccountId - Your Id for your customer, for Vend clients 19 digits, else Alphanumeric, max 50

  • Schedule_StartDate - string - the first working day after the instruction has been approved by BACS, this is normally at least 5 working days.

  • Schedule_EndDate - string - not mandated, but can be provided if a fixed length contract.

  • Schedule_Amount - decimal - the fixed amount to be table, must be above 0 and not exceed your BACS Item Limit.

  • Schedule_IntervalUnit - weekly/monthly

  • Schedule_Interval - integer - the number of interval units, i.e. 12 monthly is annually.

  • AdHoc - true/false - When set to true, no schedule is required (client collects variable payments manually)

BACK TO TOP   ⇧

Embedded Component Integration

The embedded flow allows you to render all Direct Debit pages inside your site, without iframes, while still being fully hosted and compliant.

Step 1 - Add the IPDD component script

Include the following into the <head> of the HTML page:

<script>
    const scriptSrc = "https://jolly-field-0aa415003.6.azurestaticapps.net/web-component.js?v=" + new Date().getTime();
    const script = document.createElement('script');
    script.src = scriptSrc;
    document.head.appendChild(script);
</script>

Step 2 - Insert the orchestration component

Place this tag into the <body> of the HTML page where you want the IPDD form to be rendered:

<ipdd-orchestration-form 
         InstructionReference="InstructionRef"
         CustomerAccountID="AccountId"
         ScheduleStartDate="2025-06-26"
         ScheduleEndDate="2026-06-26"
         ScheduleAmount="100.23"
         ScheduleIntervalUnit="Week"
         ScheduleInterval="1"
         AdHoc="false"
         publishablekey="{Provided by PayPoint}">
</ipdd-orchestration-form>

How the component works

When the browser loads the script:

  1. The <ipdd-orchestration-form> tag is detected.

  2. The component is replaced with the hosted IPDD workflow.

  3. All validation and compliance logic runs inside PayPoint’s platform.

  4. On submission, a Direct Debit Instruction is created and submitted to BACS.

This approach provides a native‑feeling, zero‑maintenance UX for Direct Debit onboarding.

If embedding the IPDD component:

Customers must have access to:

  • A support phone number, or

  • A live chat option

This ensures compliance with BACS customer‑service obligations during mandate creation.

Return URLs

After the customer has completed the creation of their Direct Debit Instruction, a response page is display containing Finish button. The client can configure this button to include a return URL that redirects the customer back to the client's website. The URL is appended with the status of the instruction, the instruction id and the customer account id. The client can provide their account manager different return URLs, if the creation of the Direct Debit Instruction was successful or was a failure.

BACK TO TOP   ⇧