Reference

Open the Terms Before Account Access

Clear account rules make the montigo 88 Terms & Conditions easier to use before you open an account.

Account eligibilityWallet recordsGame access rulesSupport requests
montigo 88 Open the Terms Before Account Access
POLICY HELP PATH

Check Policy Help Through Your Account

Questions about the Terms & Conditions should reach us through the account support route shown on the site, so we can connect your request with the correct account record.

Account policy request Use the support path displayed after login when a clause is unclear or you want a policy decision checked. Tell us which Terms & Conditions section you mean, and we can respond against the account details already held rather than asking you to repeat sensitive credentials.
Wallet record question For a DANA, OVO, GoPay or QRIS record, provide the transaction reference, date and displayed status. Our team can compare those details with the account ledger and explain whether the request is pending, rejected or needs another verification step under the Terms & Conditions.
Access or eligibility concern If access changes after a sign-in or device check, contact us through the account support route and describe the screen you see. Eligibility depends on local law, so we will explain the applicable policy position without asking you to bypass a location or verification control.
ACCOUNT DATA CARE

Protect Your Account and Policy Requests

Our Terms & Conditions explain how account details, transaction evidence and policy requests are handled while you use the service.

Data used for verification

We may use your registered phone details and account records to confirm that a policy request comes from the correct account holder. When a wallet status needs checking, transaction references help us compare the request without requesting your password or private security code.

Cookie choices

Cookies may help keep a signed-in session working and remember essential page settings. Your browser controls their storage, but removing required cookies can interrupt the account path or make a Terms & Conditions page load differently on your device.

Login protection

You are responsible for keeping login details private and for checking the device after access. We may ask for phone verification before account access or when a request changes account information, because the Terms & Conditions link actions to the verified account.

Record retention

Account, payment and support records may be retained for the period needed to resolve disputes, confirm transaction history and apply the current Terms & Conditions. A request to remove or correct data can be sent through the support route shown in your account.

Correction requests

If your name, phone detail or account record is inaccurate, tell us which field needs attention and why. We may request a matching account step before making a change, particularly when the detail is connected to DANA, QRIS or a withdrawal request.

Policy contact record

Keep the reference from your support conversation so we can follow the same case through later replies. When you ask about Withdraw Troubleshoot or another policy outcome, include the relevant date and account status instead of opening duplicate requests.

Find Answers About Terms & Conditions

These answers address the policy questions we hear before account creation and after a transaction status changes. They are a practical starting point, while the full Terms & Conditions remain the controlling wording for your account. Read the relevant clause carefully, then use the support path if your circumstances do not match an example.

They cover account creation, phone verification, login responsibilities, permitted access, game records, wallet transactions, withdrawals, data handling and policy changes. The same Terms & Conditions apply whether you use a mobile browser or desktop, and eligibility depends on local law.

Yes, we may require phone verification before account access or before changing important account details. This step links the request to your account record. Keep your registered phone available, and contact support if the verification screen does not match your details.

DANA and QRIS transactions must show details that match the account record and the reference supplied at checkout. If a status is unclear, send the date, reference and receipt through support. We may pause a request while those details are checked.

The policy recognises OVO, GoPay, bank transfer and virtual account records when those options are shown for your account. You must follow the displayed steps and submit matching details. Availability still depends on local law and the payment route presented.

A withdrawal request may be held while we compare the account name, destination details and transaction history. Do not create duplicate requests or share a password. Use the Withdraw Troubleshoot support path with the displayed reference so we can explain the next policy step.

Yes. Send a correction request through the account support route, identify the field and explain the change. We may ask for phone verification or matching account evidence before updating information connected to login, DANA, QRIS or another transaction record.

Use the support contact path shown after login and quote the relevant section, account reference and date. We can review the request against the current policy wording. If access is restricted, we will state that the outcome depends on local law where applicable.