At this point in the conversation we are ready for the user to sign the electronic mandate.
- As an initial step, call
GET /conversations/signto retrieve the mandate details (the details as provided in the Prepare E-Mandate request).
- Render the E-Mandate signup page.
- When the end user clicks the Proceed button on the signup page, use
POST/conversations/signto move the e-mandate to the next conversation step. Note that
mobileNumberare mandatory in the request.
As the authorisation method in this example is
SMS_PASSWORD, The user will receive an SMS message with a 4-digit code to the mobile number specified. The user will need to submit this code when prompted (in the next conversation step). Note that this OTP is not returned in the API.
Move to the next stage in the conversation: Confirmation
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 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).