For Partners/Merchants who would like to use the Account Access & E-Mandate setup flow, using their own User Interface, this section describes the APIs required.
In order to launch the Open Banking Account Access and E-Mandate signup flow, in SELF_HOSTED
mode, you must call various APIs, as outlined below.
We highly recommend that you use Postman to test our APIs on the Sandbox environment. See the Postman Overview section for more on this. |
Create & Sign the Mandate/DDI
The following services may be used to complete the E-Mandate signing step:
Service | Endpoint | Description |
Prepare E-Mandate | POST /emandates | This request returns a unique token used to render the E-Mandate screen. The Token encapsulates:
|
Initialise Conversation (Optional) | GET /conversations/init | Call this service to see the next available steps in the conversation.
This is an optional step. |
Retrieve E-Mandate Details (Optional) | GET /conversations/sign | Use this service to retrieve the E-Mandate details to be rendered for the payer to sign.
This is an optional step. |
Sign Mandate | POST /conversations/sign | Call this service to sign the Mandate. This step is required. Certain response elements should be stored for use later.
|
Retrieve E-Mandate (Optional) | GET /conversations/document | After the E-Mandate is signed the PSU may receive a Mandate PDF via E-Mail. If you want to download the PDF for your records use this service.
This step is optional |
Retrieve Mandate (Optional) | GET /schemes/{schemeId}/mandates/{mandateId} | Use this service to retrieve the mandate details after it has been signed.
This step is optional |