Comparison
PayID vs PayTo: Comparing Australian Account-to-Account Rails
A detailed analysis of PayID and PayTo on Australia's New Payments Platform (NPP)—exploring authorisation mechanics, recurring support, customer journey, and operational fit for merchants.
Executive summary: Push vs. pull real-time bank payments
Both PayID and PayTo are built on Australia's real-time New Payments Platform (NPP), but they serve fundamentally different collection functions:
- PayID (customer-initiated): The customer initiates a payment through participating online banking using an identifier linked to an eligible account. It can suit one-off invoices and ad hoc requests, subject to bank review and payment timing.
- PayTo (Merchant-Pulled / Mandated): The merchant creates a digital payment agreement (mandate) that the customer authorises inside their banking app. Once approved, the merchant can pull scheduled recurring fees, variable retainer payments, or 1-click checkout payments in real time.
Side-by-side feature comparison
Swipe horizontally to compare all columns.
| Feature / Dimension | PayID (Push Payment) | PayTo (Pull Agreement) |
|---|---|---|
| Payment Direction | Pushed by customer from mobile banking | Pulled by merchant via pre-approved mandate |
| Authorisation Model | Per-transaction customer approval | One-time agreement setup in banking app |
| Recurring & Subscription Support | Manual (Requires customer to send each time) | Automated (Supports fixed & variable schedules) |
| Settlement Speed | Typically quick where supported; timing and fund availability can vary | Near real-time messaging where supported; payment completion can vary |
| Reconciliation & Matching | Requires matching reference numbers | Agreement and transaction references can support matching where available |
| Merchant Fee Model (ShaBaas Pay) | $0.29 (<$100) / $0.99 ($100–$1000) incl. GST | $0.29 (<$100) / $0.99 ($100–$1000) incl. GST |
| Dishonour / Failed Payment Fees | Confirm failed-payment, return and fee handling with the provider | Confirm failed-payment, return and fee handling with the provider |
When to choose PayID vs PayTo
Choose PayID when:
- Collecting one-off payments or single invoice settlements.
- You want a simple, zero-friction payment link without setting up a recurring mandate.
- Customers prefer logging into their own bank app to hit "Send".
- Receiving ad-hoc deposits or initial project payments.
Choose PayTo when:
- Collecting recurring subscriptions, monthly retainers, or membership dues.
- You need 1-click checkout for returning web or app customers.
- You want to eliminate credit card expiry churn and 1.5%–2.9% interchange fees.
- Replacing traditional paper BECS direct debit with real-time settlement.
Frequently asked questions
Can a customer pause or cancel a PayTo agreement?
Yes. Customers have visibility and control over their PayTo agreements directly inside their participating Australian banking app. If a customer pauses or cancels an agreement, ShaBaas Pay immediately receives a real-time status notification so your system can update their account status.
Do customers need a special app to pay via PayID or PayTo?
No separate ShaBaas Pay app is required. Customers use their existing Australian online or mobile banking app (such as CommBank, NAB, ANZ, Westpac, Macquarie, etc.) to approve PayID transfers or authorise PayTo agreements.
Implement PayID and PayTo in one unified checkout
ShaBaas Pay offers pre-built hosted checkout, payment links, and REST APIs so you can accept both PayID and PayTo seamlessly.