The GET Conversation settings allows you to verify your E-Mandate configuration and to see the next available steps in your current conversation
Before calling any of the conversation APIs, you must first make a request to Prepare Emandate and retrieve an E-Mandate token. This token must be provided in your HTTP Token header.

In this conversation example, we are assuming that:

  • You are creating an e-mandate and will issue an OTP to the payer.
  • The payer will lose that code (for example, the user deletes the SMS or email message in error)
  • The payer has requested that a new code is issued.

In this example, we will assume that the authentication method is set to EMAIL. Note that the conversation steps outlined here are also applicable where the authorization type is configured as SMS_PASSWORD

To begin:

  • Confirm that you have been properly configured for this authentication method.
  • Generate a GET request to /conversations/settings
  • Confirm in the response that authorization is EMAIL_PASSWORD.

Move to the next stage in the conversation: Signing