Once your configuration is correct, the GET Initialization step is the starting point in the conversation and also allows you to determine at what point you are in the flow (conversation) and what are the next availabe actions.
In this example conversation, we are setting up an e-mandate where the authorization method is SMS:
- We have confirmed in the previous step that the configuration is correct.
- The response to the GET
/conversations/initwill indicate that the next available step (as indicated in the
Note: This service may be called at any point and will always indicate where you are in the flow and what are the next possible steps.
Move to the next step of the conversation: Sign
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).