• Confirm that the address is the one you intended to visit and that the connection is secure.
• Look for a consistent page layout, clear navigation and wording that matches the service you meant to access.
• Avoid signing in through unsolicited messages, unexpected pop-ups or links copied from an unknown source.
• If the page redirects unexpectedly, pause and return to a trusted starting point rather than continuing automatically.

Before submitting details, check that the sign-in fields are clearly labelled and that you understand what action the button will take. Use a unique password where possible and keep it private. Do not share passwords, recovery codes or one-time passcodes with another person or place them in a verification message.

If a verification prompt appears, read it carefully before responding. Do not assume that any particular document or data is required or expected. Instead, consult the current official requirements and use only a verified submission channel. If the instructions are unclear, stop and seek clarification through an independently trusted support route rather than replying to an unverified request.

A normal entry into a verified payment form is different from sending sensitive information through a message or file. Never send card images, CVV or CVC codes, PINs, one-time passcodes, passwords or recovery codes in KYC files, screenshots, email, chat or support requests. Enter sensitive details only where the verified form clearly calls for them, and leave the page if the request seems unrelated to the action you selected.

Readers can note what they were trying to do, which page they used and what question remains unresolved. Avoid recording secret credentials. If a request conflicts with the current official guidance, do not guess or proceed under pressure. Recheck the channel independently and look for a clear explanation before taking further action.

This checklist is a practical starting point, not a confirmation that a particular page, request or process is genuine. Current instructions should always take priority, and readers can pause whenever the sign-in or verification path is unclear.