All Docs
FeaturesagentOS Direct DebitUpdated March 13, 2026

Public Mandate Form — Multi-Step Flow

Public Mandate Form — Multi-Step Flow

Introduced in v1.0.21

The mandate form is the tenant-facing entry point for setting up a Direct Debit. It is accessed via a unique, token-based URL and requires no authentication. Letting agents generate and send this link to tenants; the tenant completes the form to register their mandate.

Accessing the Form

The form is served at:

/mandate/[token]

Each token is unique to a specific mandate invitation. Tokens are generated server-side when an agent sends a DD mandate invite. Accessing an invalid or expired token returns an appropriate error state.

Form Steps

The form is split into sequential steps. Steps are completed in order; tenants cannot skip ahead. Progress is saved to the database after each step.

Step 1 — Personal Information

Collects the tenant's identity and contact details:

  • Full name
  • Date of birth
  • Address (including postcode)
  • Email address
  • Phone number

Step 2 — DD Guarantee T&Cs

Displays the full Direct Debit Guarantee text as required by BACS rules. The tenant must tick an explicit acceptance checkbox before proceeding. The form cannot advance without this acceptance being recorded.

Step 3 — Payment Details

Shows the agreed payment schedule in a read-only summary:

  • Amount — the collection amount in GBP
  • Frequency — e.g. monthly, weekly
  • Collection date — the date funds will leave the tenant's account
  • Receipt date — the date funds are expected to arrive, calculated using the BACS working day calculator

The date pair gives the tenant clear visibility of both the debit date and the settlement date, accounting for UK bank holidays and BACS processing days.

Step 4 — Bank Details

Captures the tenant's bank account information:

  • Sort code — validated in real time
  • Account number — validated in real time
  • Account holder name

Real-time validation checks format and (where available) account reachability before allowing the tenant to proceed.

Step 5 — Video Verification

The tenant records a short video using their device camera, directly in the browser. The recording is stored against the mandate as a fraud-protection artefact. The tenant should state their name, the payment amount, and the purpose/property.

Step 6 — ID Verification

An identity check is performed via a third-party provider, presented as either a redirect or an embedded widget depending on provider configuration. The mandate proceeds only once the ID check returns a result.

Step 7 — Right to Rent (property mandates only)

This step is conditionally included for property mandates only. It captures the Right to Rent check required for applicable UK tenancies. Non-property mandates skip this step entirely.

Step 8 — Confirmation & Submit

A final read-only summary of all entered information. The tenant reviews and confirms before submitting. On submission, the mandate is registered with the Direct Debit provider via AUDDIS/BACS.

Draft State Persistence

Form state is written to the database at the completion of each step. If the tenant closes their browser or loses connectivity, they can return to the same /mandate/[token] URL and resume from their last completed step. No data entry is lost on page reload.

Mandate Variants

VariantRight to Rent step included?
Property mandate✅ Yes (Step 7)
Non-property mandate❌ No (skipped)

The form detects the mandate type from the token and adjusts the step sequence automatically.

Related