Reference

rans303 Terms & Conditions Before Access

rans303 Terms & Conditions set the rules for opening an account, using the lobby and requesting account or wallet actions.

Account rulesWallet conditionsAccess by local lawPolicy contact
rans303 rans303 Terms & Conditions Before Access
POLICY HELP

Where To Ask About These Terms

A clear contact path helps you resolve a Terms & Conditions question before an account action is taken. Start with the support contact displayed on our site and include your account phone number, the relevant policy heading and a short description of the issue. For a wallet question, name the rail shown in your receipt, such as DANA or QRIS; for a bank request, identify BCA, BRI, Mandiri or BNI where it is shown. We use those details to locate the correct account record without asking you to send a password.

Team online

Account wording

Ask about account opening, phone verification, duplicate details or access conditions through the support contact shown on our site. We can point you to the relevant Terms & Conditions section and explain which account step must be completed before access continues.

Wallet wording

For a DANA, OVO, GoPay or QRIS query, send the receipt reference and the status displayed beside the transaction. Our support path can help distinguish a pending wallet record from a policy restriction without requesting your account password.

Policy request

If you need a correction, clarification or copy of a policy record, state the request clearly in the available contact form or chat route. Include the policy heading and your registered phone detail so we can match the request safely.

ACCOUNT SAFEGUARDS

How We Apply These Conditions

The policy works alongside practical account controls rather than replacing them. We use your account details to identify the account holder, check phone verification and connect a transaction to the correct wallet…

Account data

We use the details you submit for account administration, phone verification, policy requests and transaction matching. Review your entries before sending them, and contact us when a phone number or account detail no longer reflects your current information.

Cookies

Cookies can preserve a session and help the account page behave consistently when you move between login, the lobby and the cashier path. Browser controls let you remove stored cookies, although clearing them may require you to authenticate again.

Login security

Never share your password or verification code with another person. If you notice an unfamiliar session or cannot complete the account step, stop using the account and contact us through the support path shown on the site.

Wallet matching

A payment record must be connected to the account and rail shown during the transaction. Keep the receipt for DANA, OVO, GoPay, QRIS, bank transfer or virtual account requests so a status question can be checked against the correct entry.

Record retention

We retain account, policy and transaction records for the period needed to administer the account, address disputes and meet applicable obligations. If you ask how a record is handled, identify the account detail or transaction reference rather than sending a password.

Policy changes

When Terms & Conditions change, we can publish revised wording on the policy page or show a notice during account access. Read the current text before continuing, and contact us if a change affects an account or payment request you have already started.

Terms & Conditions Search Answers

These Terms & Conditions questions cover the account decisions people commonly make before using rans303. We keep the answers tied to account access, policy wording and transaction conditions rather than describing unrelated lobby features. If your situation involves a specific DANA, QRIS, bank transfer or phone-verification record, use the policy contact path with the reference visible in your account.

They set the conditions for requesting an account, completing phone verification, accessing available areas and submitting wallet or bank requests. They also explain account accuracy, security checks, policy changes and circumstances where access depends on local law. Read the current wording before continuing from the account form.

Yes. Account access and eligibility depends on local law and your location. You must check that access is permitted where you are before using the account. If the location or policy position is unclear, contact us before submitting account details or starting a transaction.

You must provide accurate account details and complete the phone verification step when requested. Keep your verification information private and do not create conflicting account records. If a detail is wrong, contact support with the registered phone detail so the correction can be handled through the account process.

DANA and QRIS requests remain subject to the account status, receipt details and conditions shown during the transaction. Keep the payment reference and check the status beside the request. A wallet record may need matching account information before a balance or withdrawal action can proceed.

Yes, send a clear correction request through the support contact shown on our site. State which account detail is incorrect and include the registered phone number or relevant reference. We may need an account check before changing information, and you should never include your password or verification code.

Cookies may keep a signed-in session or remember a browser preference while you move through account pages. You control cookies in your browser settings, but clearing them can end the session and require another login. The policy section explains how cookies relate to account use and access.

Use the support route displayed on the site and identify the policy heading, account phone detail and any receipt reference connected with the issue. For BCA, BRI, Mandiri or BNI requests, include the transaction rail shown in the record. Do not send your password or verification code.