The Mandate object
Description
Mangopay relies on the Mandate object to authorize direct debits to be collected from a user’s bank account on behalf of platforms.
The direct debit scheme of the Mandate is determined automatically by the Typeof the Bank Account: IBAN for the SEPA scheme and GB for the Bacs scheme.
Once created, the Mandate’s RedirectURL hosts a form that the user must confirm to authorize payments.
Attributes
The scheme of the mandate, which is available once the mandate is submitted. The value can be one of the following:
- BACS – Covers payments in the UK, in GBP only.
- SEPA – Covers payments in the EU.
The unique identifier of the bank account.
Warning: The Bank Account Type must be IBAN for the SEPA scheme and GB for the Bacs scheme.
The banking reference for the Mandate.
Allowed values: One of the supported languages in the ISO 639-1 format: DE, EN, FR, NL
Default value: FR
The language in which the Bancontact payment page is to be displayed.
The URL at which the mandate document can be downloaded.
Max. length: 255 characters
The URL to which the user is returned after the payment, whether the transaction is successful or not.
The URL to which to redirect the user to complete the payment.
Caution: This variable URL is specific to each payment. You must rely on the returned URL in full (host, path, and queries) and not hardcode any part of it.
The unique identifier of the object.
The date and time at which the object was created.
Returned values: CREATED, SUBMITTED, ACTIVE, FAILED, EXPIRED
The status of the mandate:
CREATED– The mandate has been generated but not yet confirmed.SUBMITTED– The mandate has been confirmed and sent to the user’s bank, and can be used to request a direct debit pay-in.ACTIVE– The mandate has been accepted by the user’s bank or successfully used to process a direct debit direct pay-in. Further pay-ins can be requested.FAILED– The mandate has been canceled or otherwise failed, and can no longer be used for payments.EXPIRED– No payment has been made against the mandate in the last 24 months. It can no longer be used for payments.
The unique identifier of the user the card belongs to.
Returned values: WEB
The execution type of the mandate.
Custom data that can be added to this object.
In the case of the Card Registration, this parameter can be used to facilitate the link between the User object and its equivalent on your platform for instance. This value will be inherited by the Card object Tag parameter and will not be editable.
The code indicating the result of the operation. This information is mostly used to handle errors or for filtering purposes.
The explanation of the result code.