The password I had written down no longer worked. After two failed attempts I stopped trying and opened the saved contact. The first message stated only that the login was rejected and asked for the next step. No account number or extra details were included yet.
The reply arrived in under fifteen minutes and requested the registered mobile number. I sent it. A temporary code followed. I entered the code,.Matchexch9 set a new password, and confirmed the login worked. The entire chain stayed inside the same conversation and finished in less than half an hour.
What the temporary code required
The code remained valid for a short window. I typed it as soon as it arrived and avoided any delay. Once the new password was accepted I logged out and back in once more to be certain. Both attempts succeeded. That second confirmation removed the remaining doubt.
A deliberate pause before any deposit
Even after the login worked I left the balance at zero for the rest of the day. Previous recoveries on other platforms had sometimes shown strange behaviour in the first few hours. Waiting until the next evening felt more comfortable. When I finally moved a small amount the balance updated normally and a test settlement cleared without extra steps.
Reactions when I described the recovery
I wrote one line in the group about the password reset. Three people answered that they had used the same contact for similar issues. One said the code arrived faster late at night. Another simply noted that the conversation stayed on the password and nothing else. The comments remained short and free of extra advice.
One permanent change after the incident
I now keep the current password on a piece of paper at home rather than in any digital note. The paper sits in a drawer and is updated whenever the password changes. The method is old fashioned but it removes the risk of losing access when the phone itself becomes the problem.
Regaining the account required only a clear message and a short wait. The contact responded to the actual problem without introducing new requests. Once the login was stable the page returned to its usual quiet state until the next match required it.