Login, Verification and Payment Safety Checklist

Account access, identity checks and payment settings can involve sensitive information. Before signing in or submitting anything, readers can use this checklist to confirm that they are viewing current information and using an appropriate channel.

Check the login page

Readers should navigate through a trusted starting point rather than relying on an unexpected message or advertisement. Before entering account details, check the domain carefully, confirm that the connection is secure and look for unusual spelling, redirects or page elements.

If a login attempt produces an unexpected prompt, stop and consult the current official guidance. Passwords, one-time codes, PINs and recovery codes should not be shared through email, chat, screenshots or verification files. Additional sign-in protection can be enabled when it is available through the verified account settings.

Review current verification guidance

Verification procedures can change, so readers should consult the current official requirements before preparing a submission. The instructions should explain what process applies, where it begins and which verified submission channel should be used.

Do not assume that a particular file or piece of information is required. Only provide information requested through the current verified process, and review the submission screen before continuing. Card images, CVV or CVC values, PINs, one-time codes, passwords and recovery codes should never be included in verification files, screenshots, email, chat or support messages.

The Fair Go account verification guide can be used as a starting point for a reader’s own checks, while current official requirements should remain the deciding reference.

Compare payment settings carefully

Before selecting a payment option, readers can verify which methods are currently supported, whether account details must match, what limits or conditions apply, and how any charges are displayed. Sensitive payment information should be entered only into a verified payment form intended for that purpose.

Readers should pause if payment instructions arrive through an unexpected channel or request information that is not normally entered into the verified form. Any uncertainty can be addressed by consulting the current official payment guidance through a trusted access route.

Check operator and account information

Readers can look for clear, current information about who provides the service, applicable terms, privacy handling and available support channels. These details should be compared across the relevant official pages rather than inferred from a page title, search result or promotional statement.

Before proceeding, confirm that:

• the domain and connection appear correct;
• the login route was reached through a trusted path;
• verification instructions are current and use a verified channel;
• no secret access credentials are being requested in messages or files;
• payment conditions are displayed before confirmation;
• privacy and account terms are available for review.

If any detail is unclear or inconsistent, readers can stop and seek clarification through a verified support route before entering information or authorising a transaction.