Update Mandates RESTful API
Edit me

API Details

You may need to make updates to mandates at various points. Where a payer informs you that address details or an account has changed, for example, it is important to update this data so that Direct Debit payments will continue to be processed as normal.

You may need to re-send the mandate for signature depending on the update that is being made to the mandate. We would recommend that a mandate is approved by your payer if any of the following key mandate fields are modified:

  • The Unique Mandate Reference (the SEPA Mandate ID)
  • Payer account data
Usage You can update mandates in Pending and Active status
Method PUT
URI /schemes/{CS_ID}/mandates/{MANDATE_ID}

The mandateInfo.resendMandateForSignature argument allows you to control if your payer should re-sign the updated mandate:

DEFAULT the mandate is updated from Active to Pending if a key mandate field (see above) is modified .
SEND the mandate is always updated from Active to Pending for any mandate update.
DO_NOT_SEND the mandate remains in Active status regardless of the modification to the mandate.

A successful request will return a 200 OK response code.

The following is the complete list of possible status codes, which may be returned in the response:

Status Code Description
200 OK - The request completed successfully.
201 Created - A new resource has been created successfully. The resource is appended to the response.
400 Bad Request - The request was malformed. The response body will include an error providing further information.
401 Unauthorized - Your API key is wrong.
403 Forbidden - The client has provided a valid Authentication header, but it does not have permission to access this resource.
404 Not Found - The requested resource did not exist.
405 Method Not Allowed - When a HTTP method is being requested that isn’t allowed.
410 Gone - The API requested has been removed from our servers.
412 Precondition Failed - Certain unmet conditions must be fulfilled before the request to be processed e.g. timestamp is too old.
415 Unsupported Media Type - If incorrect content type was provided as part of the request (e.g. other than “application/json”).
422 Unprocessable Entity - Used for validation errors. More details will be provided in response body.
500 Internal Server Error - We had a problem with our server. Try again later and if the problem persists contact the Nuapay application support team.
501 Not Implemented - When the endpoint is not implemented yet.
503 Service Unavailable - We’re temporarially offline for maintanance. Please try again later.

Note: For a more detailed view of this API see the: API Reference