Use the GET and POST methods to retrieve the manate details and then capture when payers sign.
The Sign Conversation API use:
- GET to retrieve the mandate details initially.
- POST to push the conversation to the next setp.
To present the mandate for signing:
- Use the
GET /conversations/signto retireve the mandate details (i.e. the details provided in Prepare E-Mandate) - 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.
Swagger Reference:
E-Mandates
Note:
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).