The table below lists the range of statuses that can be applied to a Direct Debit mandate, along with the corresponding description of when that status applies.
| Mandate status | Description |
|---|---|
| Created |
The mandate has been created in GoCardless |
|
Pending submission |
The mandate is currently being processed in GoCardless. Please note that SEPA, ACH and BECS NZ mandates are only set up when the first payment is due to be processed |
| Submitted | The mandate has been submitted to the customer's bank to set up against their bank account |
| Active | The mandate has been successfully set up by the customer’s bank. You can now collect Direct Debit payments against this mandate |
| Failed | The mandate could not be set up. Typically this occurs because the specified bank account does not accept Direct Debit payments or is closed |
| Cancelled | The mandate has been cancelled, either by the customer through their bank or by yourself. The mandate can also automatically be cancelled when the customer’s bank account is closed |
| Transferred | The mandate has been transferred to a different bank account |
| Expired |
No payments were submitted for collection against the mandate. For merchants on our standard package, using the GoCardless shared SUN, their mandates will expire after 5 years of no activity. For merchants on our Plus and Pro packages, using their own SUN, their mandates will expire after 24 months of no activity. As a result, it has expired, is inactive, and no further collections can be taken against it. (Please note, creating a payment in GoCardless does not reset the expiry if its cancelled prior to submission). |
| Resubmission requested | A request to resubmit the mandate |
| Reinstated | The mandate has become active again after being cancelled or expiring |
| Replaced | The mandate has been cancelled and replaced by a new mandate |
| Customer approval granted | The mandate required additional approval from the customer (e.g. permission from a second signatory), and that approval has been granted |
| Customer approval skipped | The mandate originally was believed to require additional approval from the customer (e.g. permission from a second signatory), but this was a mistake and secondary approval has been skipped |