POLi Payment Not Working: Causes, Fixes and Refunds

"POLi payment failed" covers a few genuinely different problems that look similar from the outside — a flat decline, a payment that hangs on "processing" indefinitely, or a session that simply times out and dumps you back at checkout. Each has a different likely cause and a different fix. This guide walks through the common causes in roughly the order worth checking, then explains what actually happens to your money when something goes wrong (short version: nothing bad, because POLi never held it to begin with).

Common causes of a failed, declined, or pending POLi payment

1. Your bank declined the transaction

This is the single most common cause, and it has several sub-flavours worth distinguishing:

• Insufficient funds — the most straightforward cause, including situations where available balance looks sufficient but a hold from another pending transaction has reduced what's actually accessible.
• Merchant category blocks — many NZ banks apply heightened scrutiny, or outright blocks, to transactions coded under certain merchant categories, gambling among them. If you're trying to pay a gambling-related merchant, your bank may decline the payment specifically because of how that merchant is categorised, regardless of your balance or limits.
• Fraud or risk-scoring holds — an unusual payment pattern, a brand-new payee, or a larger-than-usual amount can trigger an automatic review or decline even when nothing is actually wrong.
• Limit exceeded — covered in detail in our deposit limits guide, but worth a mention here since a limit breach often presents to the user as an unexplained decline.

2. Session timeout

A POLi session has a limited window to complete — you're taken to your bank's login, asked to authenticate, shown the payment details, and asked to authorise, all within a timed session for security reasons. If you get distracted, need to find a second-factor code, or simply take too long reading the confirmation screen, the session can expire before you finish. The fix here is simple: start the payment again and move through the steps a little more briskly, having your banking credentials and any authentication device ready beforehand.

3. Bank-side maintenance or outage

Your bank's own online banking platform can be down for scheduled maintenance or an unplanned outage at the exact moment you're trying to pay, which will cause the POLi session to fail at the login or authorisation step regardless of anything POLi is doing correctly. Separately, POLi's own platform can occasionally experience planned maintenance windows or incidents.

4. Browser and popup-blocker issues

Because a POLi payment session typically opens your bank's login in a new window or overlay, aggressive popup blockers, strict privacy extensions, or outdated browser settings can prevent that window from opening properly or can interrupt the secure session partway through. Common culprits:

• Popup blockers preventing the bank login window from opening at all
• Ad blockers or privacy extensions interfering with scripts the payment flow depends on
• Cookies disabled, which can break session continuity between the merchant site and your bank's login
• An outdated browser version lacking support for current security protocols

5. Insufficient funds or account restrictions

Beyond a straightforward low balance, some accounts carry restrictions — a savings account not enabled for third-party transfers, an account frozen or flagged pending verification, or a joint account requiring secondary authorisation — any of which can cause a POLi payment to fail at the bank's authorisation step even though the login itself succeeded.

What happens to your money when a POLi payment fails

This is where understanding how POLi actually works pays off. A card payment that fails partway through can sometimes leave a temporary authorisation hold on your account, which is why cards occasionally need an explicit "refund" to release funds back to you. POLi doesn't work that way, because POLi never takes custody of your money in the first place. A POLi transaction only becomes real the moment your bank processes the transfer you've explicitly authorised — up until that point, nothing has left your account, there is no escrow, and there is no intermediate holding state where POLi is "sitting on" your funds.

Practically, this means:

• If the payment fails before authorisation (bank decline, session timeout, browser issue), your money simply stays in your account exactly as it was. Nothing needs to be refunded because nothing was captured.
• If you see a pending entry on your bank statement for a transaction that ultimately failed, that's a temporary bank-side record, not a POLi hold, and it should clear on its own within your bank's normal timeframe for pending entries — usually a few business days at most.
• If the payment did complete successfully but the merchant failed to deliver whatever you were paying for, that's a dispute with the merchant, not a POLi transaction failure, and would need to be resolved directly with them or, where relevant, via your bank's normal payment dispute process.

Step-by-step troubleshooting

1. Check POLi's status page at status.polipay.co.nz for any current incident or maintenance window before doing anything else.
2. Confirm your bank's own banking app or website is working normally — try logging in directly, outside of the POLi flow, to rule out a bank-side outage.
3. Check your account balance and available (not just total) balance, since holds from other pending transactions can reduce what's actually usable.
4. Disable popup blockers and privacy extensions for the merchant's checkout page, or try an incognito/private window with extensions off.
5. Try a different browser if the above doesn't resolve it, to rule out a browser-specific compatibility issue.
6. Move through the payment steps promptly on your next attempt, having any two-factor authentication method ready before you start, to avoid a session timeout.
7. If it still fails, contact your bank directly and ask specifically whether the transaction was declined on their end and why — this is the fastest way to learn whether it's a merchant-category block, a fraud flag, or something else entirely.
8. Avoid repeatedly retrying the exact same payment in quick succession if you've had one clear decline, since repeated attempts can sometimes trigger additional fraud scrutiny.

Related situations worth understanding

If your actual goal was withdrawing money from a casino account rather than depositing, it's worth knowing upfront that POLi cannot process withdrawals at all under any circumstances — see our dedicated explainer on POLi and casino withdrawals for why. And if repeated bank declines on gambling-related payments are the real pattern you're running into, our POLi alternatives guide looks at what other NZ payment methods exist, with the same honest caveats about gambling-specific restrictions applying across the board.

Frequently asked questions