Where a payer is accessing an E-Mandate link e.g. from an email, the user will be prompted to provide the last 4 digits of the IBAN.
The Verify API includes:
- GET to retrieve mandate details.
- POST to push the conversation to the next step (once the payer provide the last 4 digits of his/her IBAN).
| You must have first retrieved the E-Mandate token via the Prepare Mandate before you can call these APIs. |
When working with our APIs, please use the Sandbox URI when testing and the Live URI when you move to Production.
LIVE https://api.nuapay.com SANDBOX https://sandbox.nuapay.com/
If you haven't done so already and would like to do some testing, please Request Sandbox Access
Important: Endpoints and Webhooks may be extended from time to time and any changes we make will follow our Versioning and Backward Compatibility rules. This means that the code that you write today must be designed to be robust enough to handle any future changes (where a new object is added to (or removed from) a specific API response, for example).
GET /conversation/verify
POST prepare/{emailToken}
Note that if you are not using a UI-based flow (for example if your user has received an email with a link to the E-Mandate signup), you will need to use the following service to move to the Verify step of the conversation: