Business Readiness Requirements
Requirements to complete before going live with PayTo
If you are integrating with the PayTo API, the following operational requirements should be completed as part of your go-live readiness. We recommend considering these early in your implementation journey.
The below items are required in order to go-live with PayTo:
Note: Technical requirements such as connectivity and key test cases are not listed here.
Privacy Consent Policy Update
Customers need to be able to demonstrate how end-customers privacy consent will be collected and stored before they use PayTo and confirm that their Privacy Policy is aligned to the Privacy Act.
Data & Cyber Security controls
Customers need to confirm that appropriate data and cyber security controls are in place. This can be supported by a certification report (e.g. ISO27001) or equivalent evidence.
More details can be provided by our Integration Team.
Operational Support Process
Customers need to demonstrate they have the operational capability to support PayTo and their end customers using it once live.
More details can be provided by our Integration Team.
PayTo Brand & CX Guidelines
Customers must supply their PayTo customer experience flows for review and approval before go-live. Refer to this guide for more details.
In particular, the below requirements must be met:
The trade mark symbol '®' must be applied with the first or most prominent mention of PayTo and PayID in body copy and in superscript format
End-customers Terms & Conditions
The End-customers T&Cs for PayTo must be included either in your general T&Cs or as part of your end-customer onboarding to PayTo flow.
T&Cs can be provided by our Integration Team.
PayTo is a registered trade mark of NPP Australia Ltd ABN 68 601 428 737.