PayTo Mandate

Before a customer can have payments debited through PayTo, it is essential that the customer has authorised/approved the PayTo mandate through their banking app. Without this authorisation from the customer's end, the customer set up for direct debits using PayTo will be unsuccessful.

When a customer signs up to a merchant and wishes to use PayTo for their direct debits, Ezypay will send a request to our banking partner, so that they can create a mandate for the specific customer to use PayTo services.

Once our banking partner has created the mandate, they will send this to the customer's banking institution to inform them that one of their customer has requested to use the PayTo service.

The customer's banking institution will then send a notification to the customer's banking app, advising them that their mandate has been created and they will need to authorise/approve the mandate in order for direct debits to take place.

Once the customer has authorised the mandate, the customer's banking institution will inform our banking partner, who will then inform Ezypay that the mandate has been approved by the customer and debits can commence.

📘

NOTE:

All notifications are near real time. Once the customer has authorised the mandate, payments can be made via PayTo immediately.

PayTo Mandate Scenarios

Customer Scenario

Actions Performed by Customer

Mandate Status Outcome

Customer signs up to a merchant and wishes to use PayTo.

PayTo mandate has been created.

Customer receives notification to approve the PayTo mandate via their banking app.

Customer approves mandate immediately.

Active

Customer signs up to a merchant and wishes to use PayTo.

PayTo mandate has been created.

Customer receives notification to approve the PayTo mandate via their banking app.

After 2 days, the customer still hasn't approved the PayTo Mandate

Customer approves mandate within 5 days of the PayTo mandate being created.

Active

Customer signs up to a merchant and wishes to use PayTo.

PayTo mandate has been created.

Customer receives notification to approve the PayTo mandate via their banking app.

After 5 days, the customer still hasn't approved the PayTo Mandate.

The customer still hasn't approved the PayTo Mandate in time and it has been over 5 days since the PayTo mandate has been created.

The mandate times out and can no longer be approved.

Cancelled

Customer signs up to a merchant and wishes to use PayTo.

PayTo mandate has been created.

Customer receives notification to approve the PayTo mandate via their banking app.

Customer declines mandate

Cancelled

Customer has been using PayTo but cancels the PayTo mandate via their banking app

Merchant receives notification that the customer has cancelled their PayTo mandate.

Cancelled

Customer has been using PayTo but suspends the PayTo mandate via their banking app

Merchant receives notification that the customer has suspended their PayTo mandate.

Suspsended

Different Mandate Statuses: What they Mean

As the mandate is being created or has already been approved, the status of the mandate could change. Listed in the table below are the different mandate statues, what they mean. and what

Mandate Status

Actions Triggering this status

Related Webhooks

Created

Account Holder enters PayID/Bank Details on the Hosted Payment Page

Or

Merchant enters bank details into Partner Platform on behalf of the customer

payment_method_linked

Activated

Mandate has been approved by the account holder

payment_method_valid

Cancelled

-Account holder declines ‘Created’ mandate
-Account holder cancels ‘Active’ mandate
-Account holder does not approve mandate within timeout window
-Payment Initiator (Ezypay) ‘recalls’ the mandate

payment_method_invalid

Suspended

-Paused by Initiator (Ezypay)
-Paused by Account Holder
-Paused by Account Holders Financial Institution

payment_method_invalid


Did this page help you?