The tables below list the range of statuses and events that apply to a Direct Debit mandate, along with the corresponding description of when that status/event applies.
Mandate Statuses
| MANDATE STATUS | DESCRIPTION |
|---|---|
|
Pending Customer Approval |
The mandate has not yet been signed by the second signatory |
|
Pending submission |
The mandate is currently being processed in GoCardless. Please note that SEPA, Becs, Becs NZ, PAD and ACH 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 |
|
Suspended by Payer |
The mandate has been suspended by the payer |
|
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 |
|
Expired |
The mandate has expired due to no payments being submitted for collection. For customers who do not use our Merchant Name on Payer Bank Statements add-on feature, hence using the GoCardless shared SUN, their mandates will expire after 5 years of no activity. For customers using our Merchant Name on Payer Bank Statements add-on feature, 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 it's cancelled prior to submission). |
|
Blocked |
The mandate has been blocked as it matched against either our own fraud information or an entry in a block list provided by you. This mandate cannot be unblocked and no payments can be created against it. If you still wish to collect payments from the customer on your block list you will need to remove their details from any blocks you have created and ask them to set up a new mandate. |
|
Consumed |
The mandate has been consumed and cannot be reused (note that this only applies to schemes that are per-payment authorised) |
Mandate Events
| MANDATE EVENT | DESCRIPTION |
|---|---|
|
Created |
The mandate has been created in GoCardless |
|
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 |
|
Active |
The mandate has been successfully set up by the customer’s bank. You can now collect Direct Debit payments against this mandate |
|
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 |
|
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 |
|
Transferred |
The mandate has been transferred to a different bank account |
|
Expired |
The mandate has expired due to no payments being submitted for collection. For customers who do not use our Merchant Name on Payer Bank Statements add-on feature, hence using the GoCardless shared SUN, their mandates will expire after 5 years of no activity. For customers using our Merchant Name on Payer Bank Statements add-on feature, 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 it's cancelled prior to submission). |
|
Submitted |
The mandate has been submitted to the customer's bank to set up against their bank account |
|
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 |
|
Consumed |
The mandate has been consumed and cannot be reused (note that this only applies to schemes that are per-payment authorised) |
|
Blocked |
The mandate has been blocked as it matched against either our own fraud information or an entry in a block list provided by you. This mandate cannot be unblocked and no payments can be created against it. If you still wish to collect payments from the customer on your block list you will need to remove their details from any blocks you have created and ask them to set up a new mandate. |