PayTo payments: agreements and checkout
Assess PayTo for customer account payments. Follow agreement authorisation and collection checks, including pauses, cancellation and failed payments.
- Published
- Last updated
PayTo lets a customer authorise a business to collect payments from an eligible bank account under agreed terms. The customer approves the agreement in their online banking. Your store then needs a separate payment result before treating an order as paid.
For a retailer, PayTo acceptance means connecting an access provider to checkout and keeping agreement status separate from payment status. An active agreement permits collection within its terms. It doesn’t establish that a particular collection succeeded.
What PayTo authorises
A PayTo agreement records the customer’s permission for account payments, including their purpose, amount rules and frequency. It can cover one purchase, payments requested as needed or recurring collections.
The customer nominates an eligible account using a PayID or their BSB and account number. A PayID addresses an account. The PayTo agreement supplies permission to collect from it. Participating banks and eligible account types determine availability.
A one-off agreement can authorise payment for a single order. An ad hoc arrangement supports collections when needed within its terms. A recurring arrangement sets terms for repeat payments. Each collection still needs its own outcome.
Australian Payments Plus’ PayTo FAQs explain how customers review and manage these agreements. Keep the customer’s purchase contract separate from the agreement used to pay it.
Choose an access provider and set up the agreement
Retailers access PayTo through a sponsoring financial institution or payment service provider. Australian Payments Plus’ access provider directory lists organisations that can support this route.
Choose a provider that supports your store’s payment workflow and collection use case. Complete its merchant onboarding, confirm its commercial terms and establish the required integration. Customer account eligibility remains a separate check.
Zepto is one documented provider example. Its integration guide assigns requirements through merchant risk classification during onboarding. Higher-risk merchants must also integrate its counterparty records and complete a compliance and solutions review. An account with API access alone doesn’t establish approval for every use case.
The following illustrative flow follows Zepto’s documentation:
- Collect the payer’s name and nominated account details through your approved checkout flow. Record the purchase purpose and agreed payment terms, including applicable limits and validity.
- Resolve a PayID through the provider’s required alias-resolution step when the customer uses one. Create the agreement with a unique identifier and the required payer and merchant details.
- Ask the customer to open their bank’s app or online banking. They review the business name and payment terms, then authorise or decline the request there.
- Receive the agreement notification in your store integration. Save the agreement identifier and current status against the customer or order. Start collection only after the agreement becomes active.
Zepto’s agreement guide distinguishes a created agreement awaiting authorisation from an active agreement. A declined or expired request leaves the order awaiting payment. Show the customer a way to retry agreement setup or choose another accepted payment method.
Confirm the payment before fulfilment
Request a collection under the active agreement, then match the payment’s final result to the order. A successful request submission means processing has started. It doesn’t authorise your warehouse to release the goods.
Zepto documents separate notifications for agreement changes and payment outcomes. Its payment lifecycle includes created and submitted states, followed by settled or failed. A delayed result can become pending or require investigation. Keep the order unpaid while its collection result remains unresolved.
Keep the identifiers separate
Store the agreement identifier for the permission that supports collection. Keep the payment identifier for this individual attempt and the order or invoice reference used for reconciliation. Also retain the notification identifier so receiving the same event twice doesn’t trigger fulfilment twice.
For example, a fictional $180 order has an authorised agreement and one collection request. The store saves both identifiers against order RET-204. An agreement activation updates permission only. The matching settled payment result marks RET-204 paid, and reconciliation matches its amount and reference to the receiving record.
Incorrect handling marks RET-204 paid as soon as the agreement activates. Correct handling waits for its collection to settle.
Check duplicates and failures
Zepto documents unique request identifiers for idempotency, which prevents a repeated request from creating another collection. Keep the identifier stable when recovering the same request. Query the existing payment after a lost response before starting a fresh attempt.
Before launch, test a repeated request and a repeated notification. Confirm that one intended collection creates one paid-order transition and one fulfilment action. Also test a declined agreement and a failed payment: the customer sees an unpaid order with a recovery option, while staff see the relevant status.
A failed-payment notification supplies the reason and whether the payment is retryable. Use the provider’s supported retry route and limits after addressing that reason. A pending payment needs investigation before another collection or alternative payment risks charging the customer twice.
Australian Payments Plus’ business guidance describes success and failure notifications and warns that security checks can hold some payments. Treat the confirmed result as the release condition.
Handle paused or cancelled agreements
Customers can pause, resume or cancel PayTo agreements through their online banking. Your integration must receive these agreement changes and stop attempting collections that the current status doesn’t permit.
Pausing or cancelling stops future collection through that agreement. It doesn’t refund a payment already made or end the underlying purchase contract. Process an agreed refund through your provider’s refund procedure and retain its separate outcome.
Zepto’s modification guide treats a pause as reversible and cancellation as final. Resume a suspended agreement through its supported process and confirm its active status before collecting again. A cancelled agreement needs a new agreement and authorisation if the customer still wants to pay by PayTo.
Changes to collection amounts or frequency require the supported amendment process and customer authorisation. Some fields cannot be amended and require a replacement agreement. Keep the existing terms until the required amendment approval arrives.
When collection cannot proceed, offer another payment method your store accepts. First resolve any pending collection and reconcile the order, so the alternative payment covers an outstanding balance rather than duplicating a payment already received.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.