The two get used interchangeably, including in vendor material that ought to know better. They share a prefix, a network and an owner, and almost nothing else.
One is an addressing service. The other is a payment initiation framework. A business that has implemented the first has done nothing whatsoever about the problem the second exists to solve, and the gap between those two positions is where a fair amount of avoidable cost sits on a finance team's ledger.
A Sector That Adopted One and Has No Use for the Other
The cleanest way to see the distinction is an industry that took up one comprehensively and ignored the other entirely.
Online wagering deposits are one-off, customer-initiated pushes. Somebody decides to fund an account, does it, and the transaction is complete. There is no recurring billing anywhere in that model, no subscription, no scheduled collection. When credit cards were removed as a funding method for licensed online wagering in June 2024, that volume had to move onto rails that settle rather than authorise, and the category standardised hard on the addressing layer as a result.
Which is why comparisons of playing casino with PayID treat the payment method as a defining product feature rather than a checkout detail, and why PayTo barely registers in that sector at all. The payment shape simply does not call for it.
Most businesses have both shapes. That is the point.
PayID Is an Address
PayID does one job: it maps something memorable to something unmemorable.
Register a mobile number, an email address, an ABN or an organisation identifier against an account, and payers can send to that identifier instead of a BSB and account number. The lookup returns the registered account name, which is displayed before the payer confirms.
The money itself never touches PayID. It travels over the New Payments Platform exactly as it would if the payer had keyed in the account details manually. PayID is a directory sitting in front of the rails, not a rail.
Two commercial consequences follow. Inbound one-off payments get materially easier, which matters for invoicing, refunds and any transaction where a customer is typing details into a form. And the name display materially reduces misdirected payments, because the payer sees who they are actually about to pay before committing.
That is the whole product. Useful, narrow, and finished once implemented.
PayTo Is a Mandate
PayTo does something structurally different: it lets a business initiate a payment against a standing authorisation the customer has already granted.
The customer approves a payment agreement in their banking app, setting out the payee, the amounts and the frequency. The business can then initiate against that agreement, with funds settling in real time. The customer can view, pause, amend or cancel every agreement from the same app.
This is the replacement for direct debit, and it is a considerably better one on almost every axis. PayTo agreements are visible to the customer in a way direct debit requests never were, which cuts disputes. Balance can be checked before initiation, which cuts dishonours. Settlement is immediate rather than sitting in a three-day window during which nothing is certain.
Direction of initiation is the crux. PayID is a customer pushing money to you. PayTo is you pulling money, with permission the customer granted in advance and can withdraw at any point.
Where the Conflation Actually Costs
Three places, and they are not small.
Recurring revenue collection. A business that supports PayID has improved the experience for one-off inbound payments and left its subscription billing exactly where it was, on direct debit or card-on-file. Those are different projects, different integrations, and frequently different vendors.
Interchange on recurring card billing. Subscription revenue collected on cards carries interchange and scheme fees on every cycle. Account-to-account initiation does not. For a business with meaningful recurring revenue, that is a margin line rather than a rounding error, and it recurs monthly.
Failed payment economics. Direct debit dishonours cost money directly and cost more in churn, since a failed collection frequently ends a subscription that would otherwise have continued. Being able to verify funds before initiating changes that arithmetic.
None of which is visible if the two products are filed under one heading in a board paper.
The Migration Nobody Has Priced Properly
There is a deadline attached to all of this.
The legacy direct entry system is being decommissioned by 2030, which means every business currently collecting by direct debit has a migration ahead of it whether or not it has scheduled one. PayTo is the designated destination.
The firms treating that as a compliance exercise will spend money and get nothing back. The ones treating it as a chance to restructure how recurring revenue is collected, with real-time settlement, lower failure rates and no scheme fees, will come out with better working capital and lower cost of collection.
Same deadline, same technical work, very different outcomes depending on whether anybody in the room understood that PayTo was a commercial opportunity rather than an IT obligation.
What to Watch
Three indicators, for anyone assessing Australian consumer-facing businesses.
PayTo adoption rates against the 2030 deadline. Slow uptake in the middle of the decade would suggest the migration is being deferred rather than planned, which usually means a compressed and expensive project later.
Whether card-based subscription billing starts shifting. If businesses with large recurring bases move collection off cards, that shows up in payment processor volumes before it shows up anywhere else.
Vendor positioning. Payment providers describing PayID and PayTo as a single capability are telling you something about their depth. The two require genuinely different integration work, and conflating them in marketing usually reflects conflating them in the roadmap.
The broader point for anyone reading Australian payments coverage is that the technology story here is not really about speed. Real-time settlement was the headline in 2018. What is happening now is a restructuring of how businesses are permitted to collect money at all, and that has considerably more direct effect on cash conversion than the transfer time between two personal accounts ever did.