Reference

Terms & Conditions for msg77 Accounts

Our Terms & Conditions set out how you open, use and maintain a msg77 account in Indonesia.

Indonesia account rulesPhone verificationWallet and device terms
msg77 Terms & Conditions for msg77 Accounts
TERMS SUPPORT

Get Help With Account Rules

A clear support path helps you resolve a Terms & Conditions question without guessing which team handles it. Start from the support contact shown in your account area and include the phone number linked to your account, the relevant clause and any payment reference. We can then direct an account, wallet or access question to the right route. If you are in Semarang, the same online contact path applies, and we can explain what evidence is needed before discussing account changes.

Team online

Account access

If phone verification, a login check or a device change affects your Terms & Conditions, contact us through the account support route. Include your registered number and the device path you used so we can identify the access step without asking you to share a password.

Wallet status

For a DANA, OVO, GoPay or QRIS status question, send the payment reference shown in your cashier record. Our support route can explain which Terms & Conditions apply to a pending record, a reversed entry or a mismatch between your wallet name and account details.

Policy questions

When a clause needs clarification, quote the heading or sentence that concerns you and tell us whether it relates to account access, payment verification, cookies or data retention. We will keep the discussion focused on these Terms & Conditions and identify any request that needs additional account checks.

ACCOUNT SAFEGUARDS

How We Apply These Account Terms

Our policy handling follows the account records and settings connected to your use of the service.

Account details

The Terms & Conditions require accurate details so we can connect your phone verification, account history and payment reference. If your phone number or other account detail changes, use the available account path or contact support before attempting another access request.

Cookies and devices

Cookies can preserve session settings and help us recognise the device path used for account access. Our Terms & Conditions explain their role, and your browser controls can affect them. Clearing cookies may require phone verification again before the account area opens.

Payment records

We keep transaction references so a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question can be checked against the account record. A receipt or reference number gives support a practical way to match the request with the correct wallet entry.

Access protection

Do not share your password, verification code or logged-in device with another person. The Terms & Conditions allow us to pause a request when account details do not match, then ask for the account step or verification evidence needed to protect access.

Record retention

Account, payment and support records may remain available for account operation, dispute handling and legal requirements. The retention wording in these Terms & Conditions explains why records are kept; ask support which request path applies if you need a correction or removal assessment.

Policy changes

If these Terms & Conditions change, we will present the revised wording through the site or account path. Check the displayed version before using a payment rail or entering a lobby such as Fish Hunter, especially after a device or account setting change.

Terms & Conditions Questions Answered

You should be able to find a direct answer before opening an account or sending a payment. The questions below focus on the Terms & Conditions that affect account access, personal data, cookies, wallet records and contact requests on msg77. Where a question concerns eligibility or access, the answer depends on local law and the account details supplied during phone verification. If your situation is different, quote the relevant clause to support so we can keep the response specific.

Open the Terms & Conditions page from the site policy links before creating an account. The displayed text explains account creation, phone verification, wallet records, cookies, device access and policy changes. Keep the current wording available when you ask support about a specific account or payment event.

Yes. The Terms & Conditions cover payment records and account checks connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account entries shown in your cashier path. The available rail and any access requirement depend on local law and your account status.

You must provide accurate account details and complete the phone verification step before account access is enabled. If you change devices, clear cookies or request help with a login, we may repeat an account check. We do not ask you to disclose your password or verification code.

Cookies can support session continuity, account settings and device recognition as described in the Terms & Conditions. Browser controls may block or remove them, which can send you back through a login or phone verification step. Support can explain the effect of a cookie setting on your account path.

You can contact us through the support route shown in your account area and identify the data that needs correction. Include your registered phone number and the relevant account step, but never include your password. We assess the request against the Terms & Conditions and applicable legal requirements.

Do not continue the affected account or payment step until you understand the clause. Quote the wording to support and tell us whether it concerns access, data, cookies or a wallet record. We can explain the operational meaning, while eligibility and access remain where local law permits.

Send support the payment reference, date, rail and account phone number for a DANA, OVO, GoPay, QRIS, bank transfer or virtual account dispute. We compare the receipt with the account record, explain the status under the Terms & Conditions and request further evidence only when the check requires it.