Account & Payment Security
Practical checks for sign-in, recipient IDs and payment-provider pages.
Checked 3 October 2026Your recipient ID is not your game login.
The seven product forms request the configured account ID and, where needed, a server. They do not request a game password or game OTP. If a message asks you to send those secrets for a normal recipient-ID top-up, stop and verify the request through the service’s published contact route.
Sign into the order service carefully
Use a unique password for your order account. Login and password-reset requests go to the Veegame order service over HTTPS. This frontend keeps the returned session token in this browser tab’s session storage and does not save your password.
Email checkout does not ask for a password. If an account is created through checkout, use the email reset flow to set or recover a unique password for later access. No generated password is assumed or displayed here.
A reset code belongs only in the reset form for the action you initiated. Do not share it in a support chat. On a shared device, sign out after checking your order.
Check the payment destination
Payment entry takes place on a provider page. Review the destination, merchant information, charge currency and final amount before authorising payment. A familiar logo alone does not verify the page.
This storefront validates payment redirects against the configured provider domains. If a link cannot be verified, it leaves the created order available for review instead of following an unknown destination.
Device checks
Some methods require Fingerprint Pro. The existing service also uses a browser identifier for other methods. These are payment-risk identifiers; they are not publisher authorisation or a guarantee that an account top-up is safe in every circumstance.
If a required device check fails, checkout asks you to retry or choose another method. It does not silently bypass the required check.
Read the privacy noticeKeep useful evidence without oversharing
Support may need the order reference, recipient, payment record and balance history. Crop unrelated personal details and never include passwords, OTPs or full card numbers.
Find the published support route