Live / App
Sign in with the email address on your mv22 account and we open the signed-in home, where your wallet, the game lobby and the published help routes sit together. The form runs one step at a time — email entered, sending, confirmation — so you always know where you are.
Setting up an account with us happens in one sitting at the form, and the fields are the ones you would expect: your email address or phone number, a password you choose, and the basic details that keep the account wallet in your own name. Submit the form and a confirmation step appears before the signed-in home loads. Coming back later is simpler — the login form asks only for the details you set. Inside, the lobby navigation sits along the header, the wallet and its transaction record sit in the account menu, and any verification step that applies to your account is listed there with the exact details we ask you for. We do not push those steps through a phone call you did not ask for. If something on the screen is unclear, the support route published on this page is where you raise it, and our reply reaches the contact details registered on your account.
The form asks for your contact details and a password you choose, then shows a confirmation step before the signed-in home opens. Close the tab halfway through and the same screen waits for you when you come back, with the fields you already filled.
Money moves through the account wallet tied to the details you registered. Each deposit and withdrawal appears in the transaction record beside your balance, so you can match a payment to the day you made it without asking anyone. That record is yours to read at any time.
The signed-in area shows the session you are using and the control to sign out of that device. If you open the account on a second phone or computer, close the first session so the list stays readable and the account stays yours.
Questions about the account flow have a written route: the support page published on this site, or the help entry inside your account menu. Write from the contact details on the account and we can see which account you mean, and answer there.
Deposits and withdrawals live inside the signed-in account, so the wallet only opens after your login is confirmed. Once you are in, the payment page lists the rails we have configured for accounts in Bangladesh: bKash, Nagad, Rocket, Upay and Bank Transfer, each with the number or reference field it needs. Add funds and the entry appears in your transaction record next to the wallet balance, dated and matched to your account. That record is the part worth watching — it is the same list our support team reads when you ask about a payment, which is why we ask you to sign in before you open a query. If a rail you expected is not showing in your wallet view, tell us through the support route linked below and we will check the configuration on your account. Nothing about a payment is settled on this page; the wallet you see after sign-in is the record that counts.
bKash is the rail most accounts in Bangladesh reach for first. Sign in, open the wallet, and you will see the bKash field with the number tied to your account. Add the amount, confirm the entry, and it lands in your transaction record.
Nagad sits beside bKash on the wallet page. The flow is the same: you are signed in, the field shows the account details we hold, and each entry you send is dated in your record. If a field looks wrong, hold off and ask us before you send anything.
Rocket works the same way from the wallet, and the reference each payment carries is the one that shows in your record. Keep that reference when you contact us about a payment — it saves a long back-and-forth. The wallet field never asks for your login password.
Upay is one of the rails we have configured for accounts in Bangladesh. Because it sits inside the signed-in wallet, you will only see it after your login is confirmed, alongside the reference field the payment needs and the running list of entries you have made.
Bank Transfer is the rail account holders reach for when they want a bank record of the payment. The wallet shows the details to send to and the reference to attach, and the entry appears in your transaction list with the date you set it up.
Most sign-ins that fail trace back to something small: a contact detail that changed, a password typed on an old device, or an address opened from a saved bookmark. Before you fill the form, look at the browser bar. Every account page we run sits on mv22, so a quick read of the address is the first check you can make. Next, the phone number or email you registered with — if that number has changed hands or the mailbox is closed, sort it out with us before you try again. Third, your password: pick one you have not reused elsewhere and keep it off a shared handset. Fourth, your identity details, which should read as they do on the documents you can produce. Four checks, roughly two minutes, then the form takes over. Nothing about a sign-in needs a call from us to you first, and if any one of those four looks wrong, write to us before you try again.
Look at the browser bar before you fill anything in. The account page for this brand sits on mv22, and a bookmark saved months ago can point somewhere else. Typing the address yourself is a small habit worth keeping. It takes a second.
Confirmation steps and account messages go to the contact you registered. If that number has changed hands or that mailbox is closed, sort it out with us first, because a sign-in you cannot confirm is a sign-in you cannot finish. Keep both details to hand before you start.
Use a password you have not reused on a wallet, a mailbox or a social account. Keep it off shared handsets. If you have typed it in front of someone, raise it with us through the published help route rather than changing it and hoping the session closes.
The name and details on the account should read exactly as they do on the documents you can produce if we ask. A mismatch between the two is the one thing no login screen can resolve, and it is far easier to sort out before you add funds.
If the login form will not take your details, work through the account interface before you try again from a different device. Open the support route published on this page and send the contact details registered on your account — that is how we know the request is yours. From there, follow the steps the screen shows you; where a step needs a document or another confirmation, it is listed in the account menu with the exact wording we ask for. Do not send account details to anyone who contacts you first, whatever they claim to be. When you are back in, open your session list and sign out of any device you no longer use, then read the wallet record for entries you did not make. If one appears, tell us straight away through the same support route. A returning account is normally a short job for you and a careful one for us.
Try the form once more with the email or phone number you registered, typed by hand rather than pasted from an old message. If it still refuses, close the tab and move to the published help route instead of opening five more attempts.
Open the support page linked from this site and write from the contact details on the account. Tell us the email or phone you registered and what the login screen says. We match the request to the account before anything else happens.
Where the account menu lists a step for your situation, it carries the exact wording we ask for — the document, the detail, the confirmation. Read it to the end before you send anything, and never send account details to a message that reached you first.
When you are back in, open the session list and close any device you no longer use. Then read the wallet record for entries you did not make. If one is there, tell us through the same route straight away.
Account help follows the routes we publish, and nothing else. Start on the support page linked from this site: it carries the account questions we handle — a form that will not take your details, a confirmation you never saw, a session you want closed, or a record that looks wrong. Write from the contact details registered on your account, because that is how the request gets matched to the right wallet. If you are already signed in, the account menu carries the same help entry, which is useful when the question is about the session right in front of you. Our terms and privacy pages are published too, so questions about how account and payment records are kept have a written answer you can read before you write to us. We do not run any channel that is not listed on this site. Pick the route that fits the question and keep it in one place.
The support page linked from this site is the route for login questions: a form that will not accept your details, a confirmation that never arrived, or a session you want closed. Write from the contact details on your account so we can match the request.
Inside the signed-in area the account menu carries the help entry and the contact details we publish. Open it while you are still signed in where you can — the account you are asking about is right there, and we can answer about the session in front of you.
Our terms and privacy pages are published on this site and set out how account and payment records are handled, and what we hold about you. When your question is about those records rather than a sign-in problem, start there before you write to us.
Evidence on a login page comes down to four things you can check yourself, and none of them need a phone call. First, the address: every account page we run sits on mv22, so the browser bar is a check you can make in a second. Second, the records inside the account — the session list and the transaction record beside the wallet — which show what has happened in order. Third, the published routes: terms, privacy and support pages that say how account details and payment records are handled. Fourth, the access rules. Availability depends on your local law and eligible regions, and the account is held by one named person, which is why the wallet and its entries stay behind the login. When any of those four looks wrong, write to us through the published route before you act on a message that arrived unasked, and we will confirm what we sent and what we did not.
Every account page we run sits on mv22, and the login form is no exception. Read the address before you type a password, and treat a link from a message you did not ask for as something to check against the browser bar before you use it.
Two things inside your account are worth reading: the session list and the transaction record beside the wallet. Both show what has happened on the account, in order, without a support request — which makes them the quickest way to spot an entry you did not make.
Availability depends on your local law and eligible regions, and that applies to the login page as much as the lobby. We ask for account details at sign-in because the wallet and the records behind it belong to one named account holder, not to a device.
If an email or a call arrives asking for your password or a payment, do not use the contact details inside that message. Open the published help route on this site and ask us directly — that habit keeps more accounts out of trouble than any warning line.
These are the sign-in questions we are asked most, and the answers are the same ones you would get from writing to us — only faster to read. If yours is not here, the support page linked on this site takes it. Most of what goes wrong with a login is a contact detail that changed, a password typed on an old device, or an address opened from a saved bookmark rather than the browser bar. Work through those first, then read on. Every answer below points at something you can see on your own screen, and where a step depends on your account we send you to the account menu rather than guessing for you. Nothing in the account flow needs a phone call from us to you, and we will never ask for your password by message. Read the three that match your situation and skip the rest.
Open the login page and enter the email address or phone number you registered, then the password you set. The form shows a sending step, then a confirmation, then the signed-in home where the lobby, your wallet and the published help routes sit together.
Use the published support route on this page and tell us the phone number or the name held on the account. We match what you send to the account before anything else happens, then reply to the contact details we find there. Send one request rather than several.
You can, and plenty of account holders do. What matters is the session list: it shows the devices currently signed in. Close any session you no longer use, especially after signing in on a phone that is not yours. A clean list is easier to read the next time.
The confirmation tells you the details you entered matched the account we hold. It sits between sending and the signed-in home, so you know the step worked before you touch the wallet. If it never appears, the details did not match. Try once more before you write to us.
In the transaction record beside your wallet balance, inside the signed-in area. Each entry carries a date and a reference, and it is the same list our team reads when you ask about a payment, so the answer rarely needs you to explain anything twice.
Try once more with the contact and password you set, typing them by hand rather than pasting from an old message. If the form still refuses, use the published help route and write from the account's contact details instead of repeating the attempt from several devices.