Handling ZAR Mandates pre-transaction
You can validate if a Mandate is already in place for a specific ZAR::Bank
transaction using the validation endpoint (please refer to /transactions/validate in our API documentation for further details).
If the mandate doesn’t exist, we will trigger a new process on your behalf.
Validate API request example
Validate API response examples
Mandate already signed (HTTP 200
)
Mandate in progress (HTTP 422
)
Note: On production, the recipient of a ZAR transaction will receive an email with instructions and a link that they can open to fill and sign the mandate. Once they sign the mandate, you can proceed to create the transaction using the same details used in the validate api call.
On sandbox, no emails are sent. You can reach out to our support team to sign the mandate on your behalf thus enabling you to create a transaction with a valid signed mandate.
Mandate failed to initiate (HTTP 422
)
Warning: Getting a successful validate response before instructing a transaction might be a requirement depending on your configurations in AZA.