Sign in is a partner flow, not an rs9 form
rs9 does not collect credentials. PLAY NOW routes to the verified partner sign-in. The flow is five steps with two-factor recommended. below documents what happens at each step so the reader is not surprised by a prompt.
Partner sign-in, named at each step
Open the verified partner route
PLAY NOW on rs9 routes to the partner sign-in on gogotofly.
Enter registered mobile or email
The identifier is the one used at partner account creation.
Enter password
A strong password at creation. rs9 does not see it.
Two-factor prompt
OTP to the registered mobile. Recommended on first sign-in.
Land on the lobby
The partner lobby opens with the active contests and the wallet.
What the partner checks
Something you know
Password. Set at partner account creation. Use a password manager.
Something you have
OTP to the registered mobile. SMS is the partner default.
Something you are
Face match at KYC. Reused at high-value transactions in some flows.
Two recovery paths
Forgot password
Use the Forgot password link on the partner sign-in. OTP to the registered mobile, then set a new password. The flow is partner-side only.
Lost mobile access
Open an in-app ticket from a second device if available, or escalate via the partner help center on /customer-care/.
Five questions after the walk-through
Does rs9 see my partner password?
Is two-factor mandatory?
What if the OTP does not arrive?
Can I sign in on two devices?
How do I close my partner account?
Five steps on the partner, three factors after
Step one: open the partner app or the partner web player. Step two: enter the partner-side credentials (mobile number or email). Step three: enter the partner-side password. Step four: complete the in-app captcha. Step five: confirm the partner-side welcome screen. The five steps run inside the partner platform. rs9 never sees the credentials.
After the five steps, the partner flow exposes three optional factors: an SMS OTP sent to the registered mobile, an email OTP sent to the registered email, and a partner-side biometric prompt on supported devices. The three factors are independent. The reader can enable any combination. rs9 does not host any of the three factors.
Four recovery paths when the partner credentials fail
Path one: forgot password. The partner flow sends a reset link to the registered email. The link expires in a partner-published window. Path two: forgot mobile number. The partner flow asks for the registered email and sends an OTP to that email. Path three: account locked. The partner flow asks for the KYC documents on file before unlocking. Path four: suspected unauthorised access. The partner flow freezes the account immediately and asks the reader to verify identity via the in-app ticket matrix.
Why the partner login flow respects the state eligibility gate
The partner login flow applies the state eligibility gate at every sign-in. If the reader's state is restricted, the partner flow blocks sign-in. If the reader has moved states, the partner flow asks the reader to update the profile and re-confirm eligibility. The state gate runs server-side on the partner platform; rs9 does not see the gate decision.
The partner login flow also exposes a device-fingerprint check. If the reader signs in from a new device, the partner flow asks for an additional factor (SMS OTP or email OTP). The reader can enable biometric prompt on supported devices for a faster subsequent sign-in.