PayTo Agreements (or Mandates)
With PayTo the customer will need to authorise the PayTo agreement before any invoices can be processed. The below information is important for all integrators to understand before integrating with PayTo.
-
Before a customer can have payments debited through PayTo, it is essential that the customer has authorised/approved the PayTo agreement 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 PayTo agreement for the specific customer to use PayTo services.
-
Once our banking partner has created the PayTo agreement, they will send this to the customer's banking institution to inform them that one of their customers' 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 PayTo agreement has been created and they will need to authorise/approve the PayTo agreement in order for direct debits to take place.
-
Once the customer has authorised the PayTo agreement, the customer's banking institution will inform our banking partner, who will then inform Ezypay that the PayTo agreement has been approved by the customer and debits can commence.
NOTE:
All notifications are near real time. Once the customer has authorised the PayTo agreement, payments can be made via PayTo immediately.
Mandates is the (API) technical term for PayTo Agreements is what merchants and customers will know this as.
PayTo Agreement Scenarios
| Customer Scenario | Mandate Status is | Actions Performed by Customer | Mandate Status Changes to | Integrator/Merchant Action Required |
|---|---|---|---|---|
| Customer signs up to a merchant and wishes to use PayTo. PayTo agreement has been created. Customer receives notification to approve the PayTo agreement via their banking app. | Created | Customer approves agreement immediately. | Activated | Merchant can now set up payment schedules for the customer. |
| Customer signs up to a merchant and wishes to use PayTo. PayTo agreement has been created. Customer receives notification to approve the PayTo agreement via their banking app. After 2 days, the customer still hasn't approved the PayTo agreement. | Created | Customer approves agreement within 5 days of the PayTo agreement being created. | Activated | Merchant can now set up payment schedules for the customer. |
| Customer signs up to a merchant and wishes to use PayTo. PayTo agreement has been created. Customer receives notification to approve the PayTo agreement via their banking app. After 5 days, the customer still hasn't approved the PayTo agreement. | Created | The customer still hasn't approved the PayTo agreement in time and it has been over 5 days since the PayTo agreement has been created. The mandate times out and can no longer be approved. | Cancelled | Merchant would need to contact the customer and if the customer still wants to use PayTo. A PayTo agreement needs to be sent to the customer for approval again or they can arrange other payment method options for the customer. No payments can be set up until the customer has approved the PayTo agreement. |
| Customer signs up to a merchant and wishes to use PayTo. PayTo agreement has been created. Customer receives notification to approve the PayTo agreement via their banking app. | Created | Customer declines agreement. | Cancelled | Merchant would need to contact the customer and if the customer still wants to use PayTo. A PayTo agreement needs to be sent to the customer for approval again or they can arrange other payment method options for the customer. No payments can be set up until the customer has approved the PayTo agreement. |
| Customer has been using PayTo but cancels the PayTo agreement via their banking app. | Activated | Merchant receives notification that the customer has cancelled their PayTo agreement. | Cancelled | Merchant will need to contact customer. No further payments will be debited from the customer's account until, a new PayTo agreement has been approved, or a new payment method has been updated. |
| Customer has been using PayTo but suspends the PayTo agreement via their banking app. | Activated | Merchant receives notification that the customer has suspended their PayTo agreement. | Suspsended | Merchant will need to contact customer. No further payments will be debited from the customer's account until, the PayTo agreement has been reactivated, or a new payment method has been updated. |
Updated 3 months ago