Home/Documents/Direct Debit Mandate

How to tell if a direct debit mandate is fake

A direct debit mandate is the signed authority that lets a creditor pull money from a bank account. Its fraud comes in two forms: a mandate signed by someone who does not own the account, and one whose amount or creditor was changed after signing. The document is small and mostly boxes, so what carries the evidence is the account number, the signature, and whether the form fields were filled at one sitting.

Last updated:

How direct debit mandate forgeries are made

  • Signature forgery

    An account holder's signature is drawn or pasted onto a mandate they never signed. Identical stroke geometry across documents, or a signature with a different resolution from the form, is a signal.

  • Account swap

    The account number is changed so funds are drawn from a different person. The edited digits stand apart from the printed form, and the account may fail its format check.

  • Limit and frequency edits

    The amount ceiling or the frequency is raised after signing. The changed field's rendering differs from fields filled originally.

  • Creditor replacement

    A mandate for one biller is repurposed for another by changing the creditor block. The identifier and reference formats then fail to match the stated scheme.

What a genuine direct debit mandate contains

A mandate identifies the debtor by name and address, gives the bank and account details (an IBAN, or an account and routing number), and names the creditor with an identifier and a mandate reference. It states the scheme, such as SEPA, ACH, or NACH, whether the mandate is one-off or recurring, the amount or its maximum, and the frequency. The debtor signs with a date and place, and a bank section may be stamped.

Account numbers carry check digits: an IBAN passes a modulus test and many national formats have their own rules, so a mistyped or invented number can fail. The debtor's name should match the account holder, the creditor identifier should follow its scheme's format, and the signature should resemble the debtor's on other documents. Electronic mandates have no wet signature and are judged on their audit trail instead.

Red flags in a direct debit mandate

  • An account number or IBAN that appears only once

    Genuine documents usually repeat an identifier in a header, footer, barcode or reference block. Look for every place the account number or IBAN should appear and check they agree. An edit that updates one and forgets the others is one of the most common mistakes.

  • A signature that looks too clean

    Inspect the signature at high zoom. A real impression has uneven ink, edge variation and some interaction with the paper beneath. A copied one is often uniformly sharp or uniformly soft, with resolution that does not match the text next to it.

  • Numbering that does not follow the sender's sequence

    Genuine senders number documents in order. A reference far outside the sequence, or a repeat of an earlier number, is a prompt to ask questions.

  • A date or period that quietly moved

    Check issue, due and service dates against the period they claim to cover and against the file's own creation date.

  • Bank details that differ from earlier documents

    Compare the payee account against the last genuine document from the same sender. A changed account number is the single most expensive edit on this class.

How to verify a direct debit mandate in 4 steps

  1. 1. Check the fields against each other

    Read account number or IBAN, signature, and creditor and amount together rather than one at a time. Forgers typically change one value and leave the rest of the document describing the original.

  2. 2. Inspect the file metadata

    Open the document properties and look at the producer, creation date, and modification date. A document produced by a consumer PDF editor, or created long after the date printed on its face, is worth a closer look.

  3. 3. Ask for a second document

    Request a corroborating document from the same issuer or an adjacent period. Forgery effort concentrates on one file, so inconsistencies surface as soon as there are two to compare.

  4. 4. Run a forensic check

    Manual review catches obvious edits but not field-level pixel manipulation or synthetic generation. TamperCheck runs 300+ forensic checks on a direct debit mandate and returns a risk score from 0 to 100 within seconds, on published per-document pricing.

What TamperCheck checks on a direct debit mandate

  • Reference and document number checks

    Document, account, and reference numbers are checked for issuer format conformance and against every other place the same value appears on the page.

  • Signature forgery analysis

    Signature regions are assessed for ink consistency and for how the stroke sits on the page, which distinguishes a genuine pen stroke from a pasted image of one.

  • Arithmetic reconciliation

    Stated totals are recomputed from their components, and running or cumulative figures are checked for continuity across periods. A single edited value breaks the chain even when the page still looks right.

  • And many more checks

    The three above are the layers that carry the most weight on a direct debit mandate. Every upload runs the full suite of 300+ checks regardless of document class, spanning file structure and metadata, pixel-level forensics, font and text rendering, optical and print characteristics, provenance signals, AI-generation signatures, and many more checks.

Frequently asked questions

How do billers verify a direct debit mandate?

They validate the account number format, confirm the creditor identifier and reference, and compare the signature with samples on file. Forensic analysis of a scanned or digital mandate tests whether any field was altered after signing.

Can a direct debit mandate signature be forged?

Yes. A signature is a small graphic and can be traced or pasted. What is hard to fake is consistency: the same stroke shape on unrelated documents, or a signature at a different resolution from the printed form, stands out in analysis.

What is the difference between SEPA, ACH, and NACH mandates?

They are regional schemes for authorising debits: SEPA in Europe, ACH in the United States, and NACH in India. Each has its own form fields and identifier formats, which is why a mandate that mixes conventions is suspicious.

Does a direct debit mandate always need a wet signature?

No. Many schemes accept electronic mandates authorised online, in which case the record is a digital consent trail. A paper mandate, however, should carry a real signature and date, and a blank or pasted-looking one is worth flagging.

Which forensic checks matter most for a direct debit mandate?

It starts where forgeries of a direct debit mandate most often break: the mandate reference and creditor identifier, the maximum amount and frequency, and a pasted signature. Pixel, font and metadata checks then run across the rest of a direct debit mandate.

What inconsistency most often exposes a forged copy of a direct debit mandate?

Look for a mismatch between the account holder name and the account number or IBAN. Edits to a direct debit mandate usually change one side and leave the other as issued.

Can I trust the logo and layout of a direct debit mandate?

No. Branding and layout are the easiest things to copy. Put your attention on the fields that carry money and identity on a direct debit mandate: account number or IBAN, signature, and creditor and amount.

How do I catch altered payment details on a direct debit mandate?

Confirm any change out of band using contact details you already hold, and compare account number or IBAN against earlier documents from the same sender. A forensic check on the file shows whether the region around signature was edited.

Is there an API for checking a direct debit mandate?

Yes. Send each direct debit mandate to the REST API as it arrives and route on the JSON verdict: clean files pass straight through, and flagged ones reach a reviewer with account number or IBAN already highlighted if it was changed.

Check a document

Upload a PDF or a photo of direct debit mandate. TamperCheck returns a risk score from 0 to 100 and marks the region that was edited, usually within seconds.

For developers, the API class is direct_debit_mandate. See the API and MCP documentation.

Often checked alongside

All supported document types