Customer visibility
The customer can review the business, amount and terms presented in the banking experience.
Authorised bank-payment agreements
PayTo for Australian businesses
PayTo is a digital bank-payment method in which a customer reviews and authorises an agreement through participating online banking. ShaBaas Pay can help eligible businesses present and manage supported PayTo collection workflows, including payment status and reconciliation information. Customer, bank, provider and product support determine which agreement types and lifecycle actions are available.
Understand the agreement
What is a PayTo agreement?
A PayTo agreement sets out the terms under which a business may request eligible payments from a customer’s nominated bank account. The customer reviews the details and authorises or declines the agreement through participating online banking. Agreement approval is not the same as a completed payment.
Approved collection
After an agreement reaches a usable status, the business can initiate an eligible payment under the approved terms.
Operational status
Agreement and payment status can support customer communication, exception handling and reconciliation.
Agreement to payment
How PayTo works through ShaBaas Pay
Create the request
The business creates or presents a PayTo agreement with the terms supported by the selected flow.
Customer reviews
The customer receives the agreement in participating online banking and authorises or declines it.
Agreement becomes usable
The agreement reaches a supported status before the business requests an eligible payment.
Track and reconcile
Status, webhooks and reporting support payment follow-up, exceptions and reconciliation where configured.
Agreement design
Which PayTo arrangements may fit?
One-off or ad hoc
Useful where the customer authorises a defined collection or a business needs an approved arrangement for an occasional payment.
Regular payments
May suit memberships, subscriptions, education, professional services or invoice instalments where the supported terms fit.
Fixed, variable or capped terms
Describe only the amount and schedule structures enabled by the configured product and current documentation.
Lifecycle management
Pending, active, amended, paused, cancelled, expired or declined states require a defined operational response.
Customer-controlled, business-requested and provider-dependent actions can differ. Confirm the current implementation before promising a particular amendment, pause or cancellation path.
Operate the payment flow
What should a business plan for?
Initiation and status
Initiate only when the agreement and payment conditions are satisfied. A pending, rejected or timed-out state needs follow-up.
Changes and cancellation
Amount, frequency, payment date, bank-account changes and new-agreement requirements may follow different rules.
Customer and bank coverage
Not every bank, account or flow supports PayTo. Customer authorisation is required and alternatives may be practical.
Reconciliation
Connect agreement references, payment status, transaction data and receipts to the client’s accounting or ledger workflow.
Business fit
Where PayTo may be useful
- Memberships and approved recurring collections
- Education and service businesses
- Professional-service invoice instalments
- Variable approved billing
- Platforms and SaaS workflows
- Businesses that want digital customer authorisation
PayTo compared with other methods
PayID generally supports customer-initiated one-off payments, while PayTo uses a customer-authorised agreement for eligible future requests. Payment links and hosted checkout can present one or more methods in a customer journey. The right combination depends on payer reach, collection pattern and operational support.
Frequently asked questions
Questions about PayTo
What is a PayTo agreement?
A PayTo agreement is a digital arrangement that a customer reviews and authorises through participating online banking so a business can request eligible payments under the approved terms.
Does the customer approve PayTo in their banking app?
The customer reviews and authorises the agreement through participating online banking. The exact banking experience depends on the customer’s financial institution.
Can PayTo support one-off and recurring payments?
Depending on the configured method, PayTo can support approved one-off, ad hoc or regular payment arrangements. Availability depends on the customer, bank and provider-supported flow.
Can a customer pause or cancel an agreement?
Some lifecycle actions may be customer-controlled or business-requested, but the available path depends on the agreement status, bank and current product implementation.
Can a business change an agreement?
A business may be able to request supported changes or create a new agreement where required. Confirm the current rules for amount, frequency, date and bank-account changes.
Does agreement approval mean the payment has completed?
No. Agreement approval makes an arrangement usable; payment initiation and payment completion are separate events with their own status and possible exceptions.
What happens when a bank does not support the PayTo flow?
The business should use another supported payment method or customer journey where practical and explain the availability limitation before relying on PayTo.
How does PayTo support reconciliation?
Agreement references, payment status, transaction information, webhooks and receipts can support matching and exception handling where those data are available in the configured workflow.
Related resources
Review PayTo in context
Assess PayTo against the collection pattern
Bring the payment schedule, customer journey, bank coverage and reconciliation requirements for a fit discussion.