PayID deposits, mapped the way a payments desk would map them

Registering a PayID before you deposit

Every PayID deposit starts with a registration step that has nothing to do with any pokies site. You register an identifier, a mobile number, an email address, or an ABN if you operate as a sole trader, against your own bank account inside your banking app. That registration takes a few minutes and is entirely under your bank's control; no gambling site is involved in creating it, and none should ever ask you to register a new PayID specifically for their platform.

Once registered, that identifier works everywhere PayID is accepted, splitting a bill, paying a tradesperson, or depositing to a site. It is not a gambling account and carries no record of what it has been used for beyond your own bank's transaction history.

Choosing the right identifier

A mobile number is the most common choice because it is easy to type correctly under pressure and easy to recognise if you ever need to check which identifier you used. An email address works identically but is more prone to typing errors on a phone keyboard. Whichever you choose, use one you control long-term; if you later lose access to the number or inbox, you may need to re-register before your next deposit will work.

The deposit flow, step by step

The mechanics are consistent across sites that accept PayID, even though branding differs. First, you select PayID as your deposit method, and the site displays a PayID for you to pay, almost always belonging to a payment processor rather than the operator directly, along with a unique reference code. Second, you open your banking app, enter that PayID, and your app resolves it to a registered name, which you check against what the site displayed. Third, you enter the amount and the reference code, then confirm the payment. Fourth, the transfer settles over the NPP and the site attempts to match the incoming payment to your account using the reference code, crediting your balance once matched.

The only step in that sequence you control for safety is the second one, checking the resolved name. Everything after that point is automated on both sides.

How fast a deposit actually settles

The transfer portion is genuinely fast. NPP payments typically settle in under a minute, 24 hours a day, seven days a week, which is the structural reason PayID replaced slower transfer methods for this use case. That speed comes from the payment network itself, not from any particular site's systems, so it does not vary much between different operators.

What does vary is the matching step after settlement. A site with good reference-matching automation credits your balance within seconds of the transfer clearing. A site relying on manual matching during a busy period can take several minutes longer, even though the underlying transfer settled just as quickly either way.

Why deposit speed says nothing about withdrawal speed

It is tempting to assume a fast deposit predicts a fast withdrawal, but the two are governed by different processes. Deposits move through the NPP with no identity check beyond what your own bank already performed when you opened your account. Withdrawals, by contrast, typically require the site's own verification process before a first payout, which is a separate bottleneck entirely and covered in full on the fast withdrawals page.

A worked timing example

Take a player depositing $85. They select PayID, and the site displays a processor's PayID plus a reference code such as "REF-8842." The player opens their banking app, enters the PayID, and sees a registered name appear, matching what the site showed. They enter $85, add the reference code, and confirm. The transfer itself clears in roughly 15 to 35 seconds. The site's system then checks incoming NPP payments against open reference codes, a process that typically takes another 5 to 90 seconds depending on how the matching is automated. In total, from opening the banking app to seeing an $85 credited balance, the whole sequence usually finishes in under two and a half minutes.

If the reference code is entered incorrectly, this same $85 payment can instead sit unmatched for hours until a staff member manually reconciles it, which is why the reference code matters as much as the amount itself.

Deposit limits: minimums, maximums and daily caps

Two separate sets of limits apply to any PayID deposit, and they are easy to conflate. Your own bank sets a daily cumulative cap on outgoing NPP transfers, a limit that exists for fraud control and applies across all your PayID payments combined, not just gambling-related ones. Separately, the site itself sets its own minimum and maximum deposit amounts per transaction, which have nothing to do with your bank and can change without notice.

A typical pattern seen across sites that publish their limits is a minimum deposit somewhere in the $10 to $20 range and a per-transaction maximum in the low thousands, though neither figure is standardised anywhere and both are set entirely at the site's discretion.

Why limits differ so much between sites

Because there is no Australian licence covering these sites, there is no regulator setting a floor or ceiling on deposit limits the way there might be for a licensed product. Each site sets limits based on its own processor's risk appetite and its own commercial preference, which is why the same player can encounter a $20 minimum on one site and a $50 minimum on another with no consistent logic connecting the two.

Fees: who charges what, and why

Sending or receiving a PayID payment is typically free at the banking end; Australian banks generally do not charge customers to use PayID for standard transfers. Deposits specifically are almost always free as well, since the site benefits from making it as easy as possible for money to arrive. Where fees appear, they tend to show up on withdrawals rather than deposits, charged by the processor rather than your bank.

Because no Australian regulator oversees these processor fees, there is no cap on what could theoretically be charged, and terms can change between visits to the same site without much notice. Reading a site's own published fee schedule before depositing is the only real safeguard available.

When a deposit fails: declines and troubleshooting

A PayID deposit can fail for reasons that have nothing to do with the site. Your own bank may decline the transaction outright if you have a gambling block switched on, or if its automated risk systems flag the receiving processor's merchant category. Separately, some banks apply daily transfer caps that a large deposit can simply exceed, producing a decline unrelated to gambling at all.

The first troubleshooting step is checking your own banking app for a decline reason before assuming the site's system is at fault. If the app shows the payment as sent and settled but the site never credits it, the more likely cause is a reference-matching failure, which the site's support can usually resolve once you provide proof of payment.

What a declined deposit looks like in your banking app

A bank-side decline typically appears immediately, within seconds of confirming the payment, rather than after a delay, and the transaction will not show as pending or settled anywhere in your account history. That immediacy is a useful signal: a payment that shows as sent and settled but never arrives at the site is a matching problem, not a decline, and needs a different fix.

The payee name-check: what it protects

Before you confirm any PayID payment, your banking app shows the name registered against that identifier. This step exists purely to catch a mistyped identifier or an outright scam attempt before your money leaves your account, and it is a genuine anti-fraud feature built into the NPP by design.

It is not, however, any kind of endorsement of the site or processor you are paying. The name-check confirms that the PayID resolves to the name the site told you to expect, nothing about whether that processor is trustworthy, licensed, or the same one you paid last time. Treating the name-check as a safety signal about the site itself is a common misreading of what the feature does.

Common deposit mistakes worth avoiding

The most frequent deposit mistake is mistyping or omitting the reference code, which sends the payment through correctly but leaves it unmatched at the site's end, sometimes for hours. A second common mistake is registering a PayID against a shared or work email rather than a personal one, which complicates tracing a payment later if a dispute arises. A third is depositing an amount larger than the site's stated maximum, which can result in the transfer settling at your bank while the site simply refuses to credit the excess.

The most common deposit mistake

By far the most avoidable error is skipping the payee name-check entirely, confirming a payment on autopilot without glancing at the resolved name. Because PayID transfers settle as final within roughly a minute, catching an error before confirming is a far more reliable safeguard than trying to fix it afterward.

Where deposits fit into the bigger picture

A fast, low-friction deposit is only one part of the picture, and read it alongside the other pieces before assuming a site is safe to use regularly. The fast withdrawals page covers the verification steps and timing on the way back out, which is where most of the genuine friction sits. The legality page explains why a smooth PayID deposit says nothing about a site's licensing status. And the safe and responsible play page covers deposit limits and bank blocks as safeguards, not just as payment mechanics.

A quick checklist before your next deposit

Confirm the resolved payee name matches what the site displayed, double-check the reference code before sending, and note the amount and date somewhere outside the site itself. None of these steps add meaningful time to the process, and together they prevent almost every common deposit problem covered on this page.

Frequently asked questions