PayTo

Operated by

Australian Payments Plus

Runs on

New Payments Platform

Direction

Payee-initiated, outgoing only

Withdrawals

Not a payout rail

A PayTo agreement is not a payment

PayTo runs on the New Payments Platform, the same rails behind PayID, and is operated by Australian Payments Plus. It does a different job from PayID, and the vocabulary matters because the cashier will not explain it. What you create when you use PayTo is a payment agreement, also called a mandate. It is not stored on the payee's server. It lives in a central register the banking system maintains, the Mandate Management Service, and your bank reads it from there.

That is the point of the service. PayTo is the modern replacement for direct debit, and under direct debit you hand a business your BSB and account number and trust its filing. Under PayTo you hand over nothing. You approve a standing instruction that the banking infrastructure holds and that your bank enforces against every request made under it.

An agreement carries a fixed set of parameters: the payee's registered name, the account to be debited, addressed either by PayID or by BSB and account number, a maximum amount, a frequency or schedule, a start date and sometimes an end date. A debit request that falls outside those parameters cannot succeed under that agreement. The whole list of agreements you have granted sits in one screen in your banking app, usually labelled PayTo or payment agreements, and you can pause, amend or cancel any of them from there without contacting the payee at all. Against a card left on file with an offshore merchant, that is a genuine structural improvement, not a marketing point.

Sponsored partners · Display order is not an independent ranking.

#1 SPONSORED PARTNER

200 free spins on selected slots

WinCrown free-spin offer. Check the eligible slots, qualifying deposit and full promotion conditions.

• 200 free spins · eligible slots apply
• Check spin value, expiry and wagering
• Read withdrawal and verification rules

9,827

Partner-reported reviews Not independently verified

No independent score.

View current offer Visit WinCrown

18+ · Offer conditions

18+ only. Availability depends on your location and eligibility. Any promotion is subject to the operator's live terms, including wagering, eligible games, maximum bets, expiry and cashout limits where applicable. Deposit and withdrawal methods, processing times and limits are set by the operator and its payment providers and are not guaranteed here. Offshore operator; not licensed to offer online casino services in Australia. Gambling involves financial risk.
Checked: 2026-10-05. 18+. Gambling involves financial risk.

#2 SPONSORED PARTNER

+250% welcome bonus

Safe Casino welcome offer. Check the qualifying deposit, bonus cap, wagering and eligibility before accepting.

• Welcome bonus +250%
• Read the wagering basis and game weighting
• Check maximum bet, expiry and cashout limits

7,833

Partner-reported reviews Not independently verified

No independent score.

View current offer Visit Safe Casino

18+ · Offer conditions

18+ only. Availability depends on your location and eligibility. Any promotion is subject to the operator's live terms, including wagering, eligible games, maximum bets, expiry and cashout limits where applicable. Deposit and withdrawal methods, processing times and limits are set by the operator and its payment providers and are not guaranteed here. Offshore operator; not licensed to offer online casino services in Australia. Gambling involves financial risk.
Checked: 2026-10-05. 18+. Gambling involves financial risk.

Pull, not push — and what that costs you

PayID is a push rail. You open your banking app, choose the amount, read the recipient name and confirm. Nothing leaves without you starting it. PayTo is a pull rail. The payee initiates each request and your bank honours it if it fits the agreement. Banks describe the service plainly as being for outgoing payments; it is not built to receive funds.

The first consequence is in your favour. A PayID casino deposit requires you to copy an identifier and a reference code from a live cashier page into a banking app, and that transcription step is where deposits go missing. A stale saved payee, a reference typed without the final digit, an identifier the operator's processor rotated last week. Under an agreement none of that happens, because you are not addressing a payment. The operator requests, your bank checks the request against terms you already approved, and the funds move or the request fails cleanly.

The second consequence is the one no cashier mentions. A mandate service has no mechanism for sending money to the account holder. There is no payer-initiated payout, no reverse request, nothing. So PayTo cannot be your withdrawal method, and any page describing PayTo withdrawals is describing something else at the back end and has not looked closely. This is not a limitation of a particular operator; it is what the rail is.

The approval screen: five fields that decide your exposure

The agreement request arrives inside your authenticated banking app. That is not a convenience of a particular bank, it is how the service works, and it gives you a reliable test. If a cashier page, an email or a chat message asks you to approve a PayTo agreement on a page that is not your bank's own app or internet banking, that is not PayTo and you should close it.

Five fields on that approval screen are worth reading before you tap anything. The payee's registered name comes first, and it is less diagnostic here than people expect. The name shown will often be a payment processor's registered trading name rather than the brand on the casino website, because offshore operators sit behind processors. A mismatch is therefore normal on this rail, which means the name check that makes PayID safer carries much less weight on PayTo. If you cannot explain the name in front of you, decline it rather than guessing.

The maximum amount per payment is the field that actually governs your exposure, and the figure pre-filled on the screen is the payee's suggestion, not a requirement. Set it to what you intend a single deposit to be. Next, read the frequency. An agreement described as ad hoc or as-authorised permits a request at any time up to the maximum, with no monthly ceiling implied anywhere; a fixed recurring agreement permits one request per stated period. Those are very different grants and they look similar on screen.

Then check which account will be debited. Put an agreement on an account you keep a deliberate balance in rather than the one your pay lands in, because the pull arrives when the payee sends it, not when you are watching. Finally, the end date. An agreement with no end date persists until you cancel it, and an uncancelled mandate will outlive your interest in the site that requested it. Both Safe Casino and WinCrown publish their current deposit routes on their own cashier pages; whether an NPP agreement is on offer at either of them is something to read on the live page, not here.

The deposit choice that sets your payout route

Because PayTo cannot pay you, a PayTo deposit quietly chooses your payout route for you, and it does so before you have won anything. Operators generally return funds by the route the money arrived on, up to the deposited amount. On a pull-only rail, that route does not exist as a return path, so the operator falls back to whatever its withdrawal tab offers for bank payments, normally an ordinary transfer to a nominated account, measured in business days rather than seconds.

The practical instruction is therefore to read the withdrawal tab before approving the agreement, not the deposit tab. Three things to establish there: which route a bank-funded balance is paid out by, whether that route needs its own verification step, and whether the operator treats an NPP agreement as bank transfer for the purpose of its closed-loop rule or as its own category with its own conditions.

The failure this prevents is common and badly timed. A player funds an account by agreement because it was the fastest option on the screen, plays, wins, requests a payout, and only then discovers the payout route requires proof of a nominated bank account in a matching name that was never supplied. Days get added at the exact moment the money matters. The fix is procedural and costs nothing: supply the nominated-account proof on the day you create the agreement, while nothing is pending and nobody is waiting on you. Where the waiting actually sits between a withdrawal request and money arriving is broken down on the payout speed page; the agreement only ever touches the deposit side.

When a debit fails, and how to tell which cause

A failed debit under an agreement produces a vague error at the cashier and a precise reason at your bank. Learn to read the second rather than retrying the first.

A request outside the agreement terms is rejected by the bank, not by the cashier. If the cashier attempts more than the ceiling you set, the request dies at your bank, and retrying at the cashier cannot change an answer your bank has already given. The repair is to amend the agreement in your banking app. Put the attempted amount and timing from the cashier's history next to the terms in your agreement list and the mismatch usually names itself. Insufficient funds at the moment the request arrives produces a failure that looks identical from the cashier's side. On an ad hoc agreement the request can arrive immediately after you click, which is fine, but on a scheduled one it arrives when the payee sends it, which may not be a moment you chose. The two causes are distinguishable only from the bank end.

A paused agreement is the one that confuses people, because pause is not symmetrical. Either party can apply it, and only the party that applied it can lift it. If the payee or its processor paused yours, the resume control in your app is inert and support is the only route back. That asymmetry is the reason to prefer pausing when you intend to return — say, while you are away for a fortnight — and cancelling when you do not, since a cancelled mandate cannot be revived, only replaced by a new request you approve again.

Account eligibility is worth checking before any of this. Not every account type at every bank is enabled to hold agreements, and that list is on your bank's PayTo page rather than anywhere a cashier can tell you. An account you can send a PayID payment from is not necessarily an account that can carry a mandate. And never approve a second agreement because the first one failed. Two live mandates against one account is a configuration you will forget you created.

Three ceilings, three places to read them

Three independent ceilings apply to every debit, they are read in three different places, and a request fails against whichever is lowest without telling you which.

The agreement maximum is the first, and it is in your banking app's agreement list. Your bank's own payment limits are the second: a rail-level cap on NPP payments that applies regardless of what any agreement says, found on your bank's limits screen and often adjustable there. The operator's cashier minimum and maximum per method is the third, published on its cashier page, and it has no relationship to either of the other two. A deposit sitting comfortably under your agreement maximum can still be refused for being under an operator minimum.

On fees, check each layer instead of assuming the round trip is free. Australian banks commonly do not charge for NPP payments, but that is your bank's fee schedule to confirm and not something a cashier page can state on its behalf. The cost that actually bites is currency conversion, and it applies when the casino balance is not denominated in Australian dollars. It is charged at the operator's rate, in both directions, and it is the largest real expense of running an AUD-native rail into a non-AUD account. Where that rate is disclosed at all, it is on the terms page rather than the cashier.

One detail that is easy to misread: a maximum on an ad hoc agreement is a limit per payment, not per month. Unless the frequency field constrains it, nothing in the agreement caps how many payments can be requested.

The most revocable rail, and the least deliberate one

A standing authorisation and a gambling spending control pull in opposite directions, and it is worth deciding which way that balance falls for you before you approve one.

The protective side is real and specific to this rail. Every authorisation you have granted appears in one list, with the payee named, the ceiling you set stated next to it, and a cancel button that works without the payee's cooperation. Neither a card on file nor a crypto wallet offers anything comparable. For someone reviewing their own spending, that list is a better record than a bank statement, because a statement shows what was taken while the agreement list shows the ceiling you were willing to grant.

The risk is the loss of friction. A PayID deposit forces four small deliberate acts: open the app, enter the amount, read the name, confirm. Those frictions do more work than most people credit, and a mandate replaces all of them with a single tap at the cashier. If your pattern is to top up again after a losing run on the pokies, the standing authorisation has removed the step at which that decision used to be interrupted.

A gambling block in your banking app interacts with a mandate in a way worth asking about directly, because this rail splits one decision into two moments. There is the approval, where you grant the agreement, and then every later pull, which happens without you. A block could in principle be evaluated at either, at both, or at neither, and which of those your bank does is not something a cashier page or this one can tell you. So the question to put to your bank is specific: does your gambling block screen the approval of a payment agreement, does it screen each debit raised under one, or does it only cover card spend. What a block is actually looking at is covered on the bank blocks page; the point here is that an approval you gave weeks ago is not re-presented for your judgement each time it is used.

Cancelling the mandate yourself remains the one control over this rail that needs nobody else's permission — not the payee's, not its processor's, not your bank's. If depositing has begun to feel compulsory rather than chosen, cancel the agreement first, because it is the step that removes the mechanism rather than only the intention, and the self-exclusion page sets out what the national register does and does not reach.

Whether to use it, and what this page could not verify

The decision rule is short. An agreement is worth creating if you deposit repeatedly at one place, you want a hard per-payment ceiling that the site cannot override, and you would rather hold the controls in your bank than in a merchant's account settings. It is the wrong choice if you deposit occasionally, because the mandate outlives the reason you created it; if the manual pause before each deposit is doing useful work for you; or if you have not yet checked what route a bank-funded balance is paid out by.

What this page could not verify is worth stating plainly. No operator is named here as supporting PayTo for deposits. Mandate support across the offshore market is thin and processor-dependent, and a list published on this page would be wrong within weeks while continuing to look authoritative. The cashier page is the only current source, and its withdrawal tab matters more than its deposit tab. Bank eligibility, limits and fees belong to your own bank to state and not to any review site.

Which casinos carry the rail at all is a question about operators rather than about the rail, and it is answered where operators are compared rather than here. What this page should leave you with is narrower and more useful: the ability to read an agreement screen and know exactly what you are granting before you approve it.

Read next