Reference

Terms & Conditions for mpo700 Accounts

mpo700 Terms & Conditions explain how you open, use and protect your account before you enter Live Blackjack Diamond, Crash Fast Lift or other lobby areas.

Account accessWallet conditionsLocal-law wordingSupport path
mpo700 Terms & Conditions for mpo700 Accounts
HELP WITH TERMS

Where Account Questions Go

A clear support route helps when a Terms & Conditions question affects your account or wallet status.

Account access If a phone check prevents access, use the support path shown beside the login and state which step stopped. We can explain the applicable Terms & Conditions and identify whether the account needs a fresh verification step before you return to the lobby.
Wallet status For DANA, OVO, GoPay or QRIS questions, send the payment rail, account identifier and receipt reference through the account support route. We use those details to locate the transaction status without asking you to disclose your wallet password or security code.
Rule changes When you need clarification about a changed clause, contact us through the support channel attached to your account and name the section. We can explain the effective wording, the relevant date and any action required before you continue using the account.
ACCOUNT SAFEGUARDS

How We Apply These Conditions

Our Terms & Conditions work alongside practical account controls rather than sitting apart from daily use.

Account data

We use account details to create access, complete phone verification and connect a transaction to the right account. Keep your phone number current, because a mismatch can delay access checks under these Terms & Conditions.

Cookies

Cookies can retain your session and selected page settings on the device you use. Your browser controls whether they remain, and clearing them may require you to sign in again before opening the lobby.

Security steps

You are responsible for keeping login details private and signing out on shared devices. We may pause an account check when activity, device changes or payment details do not match the account record.

Transaction records

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account request can require its receipt reference and account match. We retain the records needed to trace a status and apply the current Terms & Conditions.

Retention requests

If you ask how long an account or transaction record is kept, contact us through the signed-in support route. We will identify the record and explain the applicable retention handling without asking for your password.

Change requests

To request a correction to your name, phone detail or account record, send the request from your account and describe the field that needs attention. We may ask for a matching verification step before applying a change.

Terms & Conditions Questions Answered

These Terms & Conditions answers cover the account decisions you are most likely to make before opening the lobby. We keep the wording practical: what acceptance means, how payment references are handled, why verification may appear, how access is determined and where a correction request should go. If your situation is not listed, use the account support path with the relevant clause or transaction reference.

They are the rules for creating and using your mpo700 account, including phone verification, wallet instructions, security duties, transaction checks, access restrictions and support requests. You should read the current Terms & Conditions before opening the lobby or sending a payment request.

No. Acceptance confirms that you understand the conditions, but you still need to complete the account path and phone verification before account access. Enter accurate details and follow the prompts shown on your device rather than using another person’s account.

Those local rails may appear for eligible accounts, subject to the current cashier instructions and local-law wording. Use the wallet or QRIS reference shown for your request, keep the receipt, and contact support if the status does not match your account.

Phone verification helps us connect the account to the contact detail entered during the account path and supports security checks. If the code or phone detail fails, use the signed-in support route; never send your one-time code or password in a message.

They apply to account creation, login, lobby access, payment requests, security checks and contact with support. Eligibility depends on local law, so a location or account status may affect access. We do not treat these terms as permission where local law does not allow access.

Contact us from the account support route and name the detail that needs correction, such as a phone number or account name. We may request a matching verification step before changing the record, and you should keep using the existing detail until we confirm the update.

Use the support channel shown in your account and identify the clause or effective date you are asking about. We can explain the current wording and any action it requires. If the change affects access, the local-law condition still applies.