Welcome

Welcome to Zepto's PayTo API - we're happy to have you aboard. These guides aim to give you a view into what's coming and enable your teams to start forming your payment flows around our PayTo solution.

As well as delivering our scalable, best-in-class PayTo solution, we've become the NPPA's first Connected Institution. Meaning that, we've connected to the global SWIFT network and built out our own banking-grade infrastructure that connects directly to the NPPA’’s Basic Infrastructure (NPP).

---

PayTo

PayTo (formally known as the Mandated Payments Service or MPS) is the biggest shake-up in account-to-account payments in Australian history. To date, the only way to pull funds from a bank account has been to perform a direct debit via the antiquated BECS system. This system essentially passes batch payment files between Tier 1 banks, 6 times a day, Monday to Friday, takes a break at the weekends, hates working public holidays, and makes it a real pain to receive funds given a payment takes 2 days to clear - and even then, can still, sometimes fail.

Enter the NPPA's PayTo 🚀!!

👍

Additional resources about PayTo:

• https://www.zepto.com.au/payto/
• https://payto.com.au/
• https://nppa.com.au/wp-content/uploads/2021/12/PayTo-Service-Overview-Nov-2021-2.0.pdf

---

PayTo Availability

PayTo continues to be rolled out across the industry, with a significant number of accounts already online. For greater clarity on PayTo availability across specific accounts, please check with the respective financial institutions that are offering these services.

---

PayTo Concepts

Whether you are new to Zepto or are already using our highly composable API for your payment flows, we've learned a lot over the years and have made a few tactical decisions around our PayTo APIs to enable all our platforms to scale safely.

Asynchronous Operations

Our API is designed to be asynchronous to maintain consistently fast response times:

• Invalid requests:
  • Invalid schema will be rejected immediately (400 Bad Request)
  • Failed field validations will be rejected immediately (422 Unprocessable Entity) with relevant error messages
• Valid requests:
  • receive 201 Created with a ref id that can be used to track the resource

Synchronous Notifications

There are two ways to determine the outcome of your request. Depending on your integration, you can choose your preferred method:

1. Webhooks: Each outcome will fire a webhook to notify your application in real-time of the result
2. Polling: In the event an outcome needs to be checked out-of-band, the resource may be queried directly

Alternatively, combine both webhooks and polling to meet your notification needs.

Idempotency

Include your own unique 64-character payment id to enforce idempotent behaviour throughout the application.

This id is required when requesting a new:

• PayTo Agreement
• PayTo Payment