Reference

Terms & Conditions For Wallet Access

raja5d Terms & Conditions explain how you open, use and maintain your account while accessing casino rooms, sports markets and local wallet routes.

Account stepsWallet checksDevice accessPolicy contact
raja5d Terms & Conditions For Wallet Access
POLICY HELP

Where Policy Help Starts

A clear contact route matters when a Terms & Conditions question affects your account or wallet status. Use the support path connected to your account and include the registered phone detail, transaction reference and the exact clause you want us to clarify. We can then separate an access question from a payment-status question without asking you to repeat the whole account history.

Team online

Account wording

Ask us to explain a registration, phone verification or login condition through the account contact path. Include your registered phone detail so we can connect the question to the correct account record.

Wallet status

For DANA, OVO, GoPay, QRIS or bank transfer questions, send the payment reference and displayed status. We use those details to check whether the entry is pending, matched or needs another account step.

Clause request

When a rule is unclear, name the Terms & Conditions section and describe the action you planned to take. Our support route can point you to the applicable wording and tell you what account detail is needed.

RECORD PRACTICES

How We Handle Account Records

We handle policy requests through the account details needed to identify the right record and answer the right Terms & Conditions question.

Account data

We use the registration name, phone detail and account identifier to match your request with the correct Terms & Conditions record. Accurate details help us avoid discussing another account when several devices share a connection.

Phone verification

A phone check may be required before account access or after a material account change. Keep the registered number available and do not send its private code through a support message.

Device changes

A new phone, browser reset or unusual sign-in can lead to an additional account check. This condition helps us connect access requests to the account holder before wallet activity continues.

Cookies and storage

Cookies or browser storage can preserve login state, language choice and page settings. Clearing them may require you to repeat the login path or phone verification step described in these Terms & Conditions.

Record retention

We retain account, payment-reference and contact records for the operational period needed to administer conditions, resolve disputes and meet applicable legal requests. The retained record can include your support conversation.

Change requests

To ask for a correction, deletion or explanation, use the account contact route and identify the record involved. We may request account details before acting, and the result depends on local law.

Questions About Terms & Conditions

These Terms & Conditions answers focus on the account decisions you are most likely to make before opening the raja5d lobby. We cover eligibility wording, wallet records, device access, data requests and the contact route, with each answer tied to an action you can take. Where a condition changes because of location or legal requirements, access depends on local law.

They cover account opening, phone verification, login security, wallet references, device access, policy changes, data handling and contact requests. They also explain how conditions apply when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

Account access depends on local law and is available where local law permits. You must provide accurate account details and complete the phone verification step requested before access. Check the current Terms & Conditions for the location and account conditions that apply to you.

Phone verification links the sign-in attempt to the account detail you supplied during registration. We may request it before access or after a device change, wallet discrepancy or account update. Keep private verification codes out of support messages and enter them only in the account flow.

Yes. The conditions cover how DANA, OVO, GoPay and QRIS entries are matched to your account, including a displayed pending status. Bank transfer and virtual account references may also need to match before an account balance is updated.

A new phone, browser reset or changed device signal can trigger an additional account check under the Terms & Conditions. Use the registered login path and complete any requested phone verification. Contact the support route if the account detail no longer matches your device.

Send a request through the account contact route and state whether you want a correction, deletion or explanation. Include the relevant account identifier, but never send your password. We verify the request before changing a record, and the outcome depends on local law.

Name the Terms & Conditions section in your account contact request and describe the action you are considering. Add a payment reference when the question concerns DANA, OVO, GoPay, QRIS or a bank transfer. We will direct you to the applicable wording.