Choose between trying a password reset and contacting support before making another login attempt. If you are sure the account details are yours and there is no unfamiliar activity, use the site’s normal reset process; if you see a security warning, changed account details or a transaction you do not recognise, stop and document the issue first.
For a New Zealand player, the useful question is not simply whether the page opens, but where the process fails: before verification, after a code is sent, or when the account loads. Start from the official site you normally use, such as the Rewards Casino Login page, and record the date, time and exact message. Do not follow login links in unexpected emails or messages.
Define the login problem precisely
Separate an access problem from a restriction or payment issue. A wrong-password message, a verification code that never arrives, a blank page and an account notice are different problems, and each needs different evidence. Note the last time you successfully signed in and whether anything changed afterwards, such as a new device, email address, phone number, browser setting or network.
Also record what you were trying to do. Were you signing in, completing identity checks, viewing a bonus, or opening the cashier? A promotion or balance that is not visible after login may be an account or offer question rather than a password fault. Keeping these facts separate helps support staff investigate without repeated guesses.
Likely causes of a failed sign-in
- Typing or saved-password error: Autofill can enter an old password, add a space, or use a different email address from the one registered.
- Verification delay: An email may be filtered, a text may arrive late, or an expired code may have been entered. Check the inbox, junk folder and the correct phone number, then request a fresh code only through the site.
- Browser or connection issue: Out-of-date software, blocked cookies, a private browsing setting or an unstable connection can interrupt a login. A maintenance notice may also explain a temporary failure.
- Account review or security lock: Several unsuccessful attempts, a new device, incomplete identity details or an account notice may require the operator to confirm information. Do not create another account to get around a restriction.
- Different account details: A mismatch between the registered name, email, phone number or payment information can prevent verification or access to account features.
Diagnostic checks and evidence to retain
Make one careful check at a time. Confirm the spelling of the registered email, check the device’s date and time settings, and use a current browser. If you test another browser or connection, record what changed. Avoid repeated password guesses: they can trigger additional security checks and make the timeline harder to explain.
Keep a small evidence file before clearing browser data or reinstalling an app. Screenshots should show the full error and, where possible, the address bar and time, but hide passwords, one-time codes, full card numbers and other sensitive details. Save the original error wording rather than paraphrasing it. If the page contains personal information, crop or cover it before sharing.
| Evidence | What to capture |
|---|---|
| Login attempt | Date and time in New Zealand, device, browser or app version, and the step where it failed. |
| Terms and notices | The relevant account, identity-check or bonus terms as displayed, including the offer name, conditions and expiry date. |
| Messages | Error text, support case number, and copies of emails or notices with their dates and sender details. |
| Transactions | Relevant NZD amount, date, payment method, status and transaction reference from the account or your bank record. |
| Account details | The email or phone number used, last successful access and any recent change you made. Never send a password or verification code. |
For a payment-related concern, distinguish a pending bank authorisation from a completed debit. Keep the bank’s transaction reference and the operator’s receipt or transaction ID, and compare the amount and date. Do not send an unredacted statement unless support explains why it is needed and provides a suitable secure channel.
Next action and when to escalate
If there is no sign of unauthorised access, use the official password-reset or verification route once, then wait for the stated delivery period. If access returns, check the account email, contact details, balance and transaction history. Save any changed terms or account notices relevant to the issue. If you cannot regain access, contact the operator through contact details reached independently from the site, and include a concise timeline, error screenshot and relevant references.
Ask support to confirm the specific reason for the block, what evidence is required, how to submit it securely, and the expected response time. If the issue concerns an offer, quote its exact name and ask which eligibility or wagering condition applies; do not rely on a banner alone. Keep copies of your request and every reply, and note when you followed up.
Escalate when the stated response time has passed, the explanation does not address your evidence, or a transaction remains unexplained. Use the operator’s formal complaints process and retain its outcome. If you suspect account compromise, secure your email and payment accounts as well, contact your bank about any unrecognised debit, and do not share codes with anyone claiming they can restore access. In 2026, the safest record is a clear sequence of events, exact terms and verifiable transaction details—not repeated login attempts.