Reference

Terms & Conditions For Your aksi99 Account

Our Terms & Conditions set the rules for opening, using and closing your aksi99 account, including identity checks, wallet status and access where local law permits.

Account accessWallet checksPolicy contact
aksi99 Terms & Conditions For Your aksi99 Account
HELP WITH TERMS

Clear Policy Help From The Cashier Path

A clear contact path matters when a clause affects your account, so we connect policy questions with the same account help route used for wallet status checks. Tell us whether your question concerns phone verification, a DANA receipt, a QRIS reference or account closure, and include the relevant account detail without sending your password. We can point you to the applicable Terms & Conditions wording and explain the next step. If you are in Bandung, the same online route applies wherever access is permitted by local law.

Team online

Account help

Use the account help route when you need a clause explained before opening an account or changing your details. Include your registered phone number and the section heading, while keeping your password and one-time codes private. We use that context to direct your question to the right policy path.

Wallet status

For a payment question, send the receipt reference and name the rail involved, such as OVO, GoPay or bank transfer. We check the account record against the payment status and tell you whether the Terms & Conditions require another verification step before the balance can be updated.

Access concern

If login access changes after a device switch, contact us through the support route and describe the device path you used. We can check phone verification, recent account activity and local access wording without asking you to disclose a password or security code.

DATA AND SECURITY

How We Apply These Terms Safely

The policy also describes how we handle the account record behind each request. We use the details needed for registration, phone verification, payment matching and security checks, then retain them only for…

Phone verification

Before account access, we may send a phone verification step to confirm that the registered number belongs to you. The Terms & Conditions allow us to delay access when that check does not match. Update the number through the account path if your contact details change.

Payment matching

A DANA, QRIS or virtual account receipt can be compared with your account details to identify the correct transaction. We do not need your wallet password. If a reference is incomplete or belongs to another account, the policy explains why status confirmation may wait.

Cookie controls

Cookies can preserve a login session and remember device settings, but they do not replace your account credentials. You can clear them in your browser settings; after that, the mobile or desktop path may ask for phone verification again before access continues.

Account security

We may pause access when sign-in behaviour, device changes or account details need checking under the Terms & Conditions. This protects the account record while we ask for the relevant verification. Keep your registered phone available and contact support if the activity was yours.

Data requests

You can contact us to request correction of an inaccurate name, phone number or account detail. State the change clearly and use the registered contact path. We may ask for a verification step before changing data, because the request must come from the account holder.

Retention questions

Ask us which account records remain connected to a payment, security or policy matter and why they are retained. We will use the registered account route to discuss the request. Closing an account does not automatically erase records that must be kept for a stated operational reason.

Terms & Conditions Questions For aksi99

These Terms & Conditions questions cover the account decisions you are most likely to make before registration or while checking a wallet status. We keep the answers tied to the actual account path: phone verification, payment references, cookies, data requests and local access. If your situation is not covered, contact us with the relevant section heading and we will explain the next available step.

They cover account opening, phone verification, accurate registration details, wallet matching, security checks, cookies, data requests and account closure. They also explain when access depends on local law and what may happen if an account detail or payment reference needs clarification.

Access depends on local law. Before opening an account, you must confirm that using the service is permitted where you are located. If a location or eligibility question remains unclear, use the account help route before entering registration details or sending a payment.

Phone verification connects the account to the registered number and helps us check that an access or data-change request comes from you. The Terms & Conditions allow us to delay account access when the number, device activity or submitted details do not match.

We may match a DANA or QRIS reference with your registered account before confirming status. Send the receipt reference through the support route, never a wallet password. A mismatch, duplicate reference or missing detail can require another check under the policy.

Yes. Contact us through the registered account route and identify the name, phone number or other detail that needs correction. We may ask for phone verification before changing it. This protects the account record and ensures the request comes from the account holder.

Closing an account stops normal account use, but some records may remain for a stated payment, security or policy reason. You can ask which records are retained and why. We will handle the request through the registered contact path after confirming your identity.

Use the account help route and include the section heading plus a short description of your question. For wallet matters, add the DANA, GoPay, OVO, QRIS or bank transfer reference. Do not send passwords or one-time codes; we will identify the relevant policy step.