Direct Debit

Mandate lifecycle

Follow a Direct Debit mandate from request to collection, cancellation, and recovery

A Direct Debit mandate has a lifecycle: a request to set it up, an authorisation, the bank lodges it, it becomes Active, you collect under it, and eventually it is suspended or cancelled. This page maps each stage to the guides that document it, so you can jump to the stage you are working on.

What you'll learn
  • The stages every mandate moves through
  • Which starting points create a mandate and which collect
  • Where advance notice happens in the lifecycle
  • What changes when a mandate is suspended, cancelled, or fails

The life of a mandate

Direct Debit starting points
  1. Request -- you send a mandate request from a customer record, or the customer chooses Direct Debit on an invoice, checkout, or embed.
  2. Authorise -- the customer completes the hosted mandate page.
  3. Lodge -- the bank accepts the instruction; the mandate becomes Active.
  4. Notice -- the customer receives advance notice of the amount and date.
  5. Collect -- RevKeen submits the collection under the Active mandate.
  6. End or pause -- the mandate is cancelled, suspended, or fails.

Setup and collection are separate jobs. Completing the setup form never takes money by itself.

Stage by stage

StageWhat happensWhere it is documented
Request from a customerMandate setup only, no collectionStart from a customer
Request on an invoiceCollection once mandate Active and notice givenStart from an invoice
Request on checkoutCollection once mandate Active and notice givenStart from checkout
Embedded on your siteMandate capture; collection still needs an amountEmbed
AuthoriseCustomer completes the hosted mandate pageHow Direct Debit works
Become ActiveBank lodges the instructionMandate statuses
Advance noticeCustomer learns the amount and dateEmails and notices
CollectRevKeen submits the collectionHow Direct Debit works
Manage or cancelCustomer views, changes, or cancelsCustomer portal

Statuses in the lifecycle

Mandate statuses

A mandate only collects when it is Active. Awaiting setup, Submitted, Failed, Suspended, and Cancelled all block collections. Expired request means the setup link was not used in time.

If you subscribe to webhooks, wait for mandate.activatedmandate.created is not permission to debit. See Webhook events.

Where advance notice fits

Advance notice sits between the mandate becoming Active and the first collection:

Combined versus separate advance notice

If the amount, date, and frequency are all known at sign-up, the first collection's notice may be combined with the confirmation. Otherwise the customer gets a confirmation first and a separate advance notice later. Any later change to amount, date, or frequency triggers a new notice.

Collection is a separate step

The customer tab never collects. Collection happens only after an Active mandate and advance notice, and only from an invoice, a checkout link, or an eligible subscription renewal:

Mandate setup versus collection

Ending or pausing the lifecycle

The lifecycle can end several ways:

TransitionHow it happensResult
SuspendedOperational or bank pauseCollections pause; can return to Active
CancelledMerchant, customer, or bank ends the authorityNo more collections
FailedBank or bureau rejects the instructionMust be corrected or a new request sent
ReplacedChange of bank completes a new mandateDo not collect on the old one

The customer can cancel a Direct Debit directly with their bank at any time, then tell you so you can agree another way to pay. See Customer portal for how change of bank and cancellation appear in RevKeen.

Choose the guide for where you are now:

Customers can read Set up and manage a Direct Debit for a plain-language explanation of the setup page.

On this page