Simple pricing
Use flat-fee Pay by Bank pricing with no percentage-based ShaBaas Pay transaction fee. Review current fees and limits before activation.
View current pricing →Real-time bank payments for Australian businesses
Accept PayTo payments with simple flat-fee pricing
Give customers a secure way to authorise payments through participating online banking. ShaBaas Pay helps eligible businesses create and manage supported PayTo agreements, track payment status and simplify reconciliation—without percentage-based ShaBaas Pay transaction fees.
- Pay-as-you-go pricing
- No monthly fee or lock-in contract
- Account creation takes only a few minutes
Built for business payments
A clearer way to collect authorised bank payments
Real-time status
Track agreement and payment status to support customer follow-up, exception handling and reconciliation.
Get started online
Create your ShaBaas Pay workspace, test the payment journey and complete onboarding when you are ready to accept live payments.
Create your account →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.
Customer visibility
The customer can review the business, amount and terms presented in the banking experience.
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
Use the amount and schedule structures enabled for your integration. Confirm fixed, variable or capped terms before offering them to customers.
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.
PayTo for Australian small businesses
ShaBaas Pay offers PayTo for eligible Australian businesses and software platforms. Customers authorise an agreement in participating online banking before a business requests payments under its approved terms. Successful standard Pay by Bank payments cost AUD $0.29 incl. GST below $100, or AUD $0.99 incl. GST from $100 to $1,000 inclusive. The standard maximum is AUD $1,000 per transaction; additional limits may apply.
| Topic | ShaBaas Pay offering |
|---|---|
| Eligibility | Live payments require business onboarding and applicable identity and business checks. The payer needs an eligible account at a participating financial institution. |
| Access | Use supported dashboard payment journeys or integrate through the payment APIs. |
| Collections | One-off and recurring arrangements depend on the agreement terms and enabled integration. Confirm the required amount and frequency during setup. |
| Fees and limits | Current Pay by Bank fees and the $1,000 standard transaction limit apply; card and wallet fees are separate. |
| Confirmation | Agreement approval, successful collection and payout to the merchant bank account are separate events. |
How can a business collect recurring bank payments?
Use a customer-authorised PayTo agreement with the amount and frequency enabled for your integration. An authorised agreement permits eligible requests; it does not guarantee that each payment will succeed.
Agree the terms
For example, a service business can discuss a $60 monthly collection. This is an illustrative use case: confirm that the schedule and amount are enabled before offering it to customers.
Obtain authorisation
The customer reviews the payment terms in participating online banking.
Request and check each payment
Collect only under the usable agreement and approved terms. Track the payment result separately from agreement status.
Handle changes and failures
Review pending or failed collections before retrying. A paused or cancelled agreement requires follow-up before further collection. Confirm supported amendments or whether a new agreement is needed.
Available schedules, variable-amount rules and automated scheduling depend on the integration. Discuss these with ShaBaas Pay before activation.
PayTo, PayID, direct debit and cards compared
Australian small businesses can offer bank payments alongside cards. ShaBaas Pay supports PayTo, PayID and BECS direct debit in enabled business flows, with cards and digital wallets available through approved partners where activated.
| Method | Who authorises or initiates? | Recurring use and timing | Matching and costs |
|---|---|---|---|
| PayTo | Customer authorises an agreement in participating online banking; the business requests eligible collections. | Approved one-off or recurring terms. Generally real-time processing, subject to bank and operational checks. | Agreement and payment references support matching. See Pay by Bank fees. |
| PayID | Customer sends a payment to the displayed PayID using online banking. | Customer initiates each payment; a PayID is not a recurring debit authority. Generally real time, subject to bank checks. | Match payment references and status to the invoice. See Business PayID. |
| BECS direct debit | Customer provides a debit authority; the business submits collections. | Recurring collections in supported flows; batch and business-day processing. Rejections or returns require follow-up. | Match collections and later returns. Confirm the enabled flow and applicable fees before activation. |
| Cards and wallets | Customer uses card or wallet authorisation. | One-off or recurring use depends on the activated card product. Processing and payout timing vary. | Separate card and wallet fees are confirmed before activation. |
PayTo customer controls and status notifications differ from BECS direct debit. Existing debit authorities do not establish that a PayTo agreement is authorised: confirm migration requirements, customer consent and bank coverage before moving collections. Read the direct debit comparison and PayID comparison.
PayTo and PayID APIs for Australian platforms
ShaBaas Pay provides PayTo agreement and payment-initiation APIs, and PayID collection and status workflows for approved integrations. Start with the developer gateway and REST API reference for authentication, operations, webhooks and status handling.
Create an account at Sign up to explore the staging workspace. Sandbox testing and live merchant activation are separate. Review agreement error codes and payment error codes. Confirm duplicate protection and timeout handling for each endpoint before retrying a payment.
Split payouts for approved merchant workflows
ShaBaas Pay offers split-payment functionality for approved business use cases. Payout recipients must be eligible merchants that have completed the required business and identity checks; payouts to consumers are not supported.
Illustrative collection example: two customers pay $50 and $30 towards an $80 merchant bill. Both collections must be confirmed before treating the full $80 as collected. Collection and merchant bank payout are separate steps. This example describes collection aggregation, rather than a promise of a particular multi-recipient payout arrangement.
Discuss your platform workflow to confirm recipient eligibility, allocation rules, the supported funding source, fees and payout timing before integration.
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.
Does ShaBaas Pay support PayTo for small businesses?
Yes. Eligible Australian businesses can use supported PayTo payment journeys or APIs after onboarding. Customers authorise agreements through participating online banking. Successful standard Pay by Bank payments cost AUD $0.29 incl. GST below $100, or AUD $0.99 incl. GST from $100 to $1,000 inclusive. The standard maximum is AUD $1,000 per transaction; additional limits may apply.
What is the difference between PayTo and PayID for merchants?
PayTo lets a business request eligible payments under a customer-authorised agreement. PayID lets the customer initiate a bank payment to an identifier. PayID does not itself authorise recurring debits.
Can ShaBaas Pay split payouts to consumers?
No. Split-payment functionality is for approved business use cases with eligible, verified merchant recipients. Confirm allocation rules, funding sources, fees and payout timing with ShaBaas Pay.
Related resources
Review PayTo in context
Start with a test workspace
Ready to offer PayTo to your customers?
Create your account to explore the payment journey. Complete business onboarding when you are ready to activate live payments.