Reference

Terms & Conditions for Your dki4d Account

dki4d Terms & Conditions set the rules for opening an account, using the lobby, and connecting DANA, OVO, GoPay or QRIS.

Account stepsWallet recordsLocal-law access
dki4d Terms & Conditions for Your dki4d Account
POLICY CONTACT

Three Ways to Ask About Policy

A clear contact route helps when a Terms & Conditions question affects your account or wallet status. We ask you to begin from the account help link beside the login area, then include your registered phone number and the relevant payment reference. This lets us locate the right record without asking you to send a full password. If you are checking a rule before opening an account, quote the section heading and we will point you to the applicable wording.

Team online

Account access

Use the account help route when phone verification does not match your details or a Terms & Conditions step prevents access. Include your registered number, device type and the policy heading involved so we can check the account path without requesting your password.

Wallet status

For a DANA, OVO, GoPay or QRIS record, send the payment reference shown on your receipt and the account phone number. We compare those details with the wallet status connected to your account and explain which policy condition affects the next step.

Policy wording

If a clause is unclear, contact us through the policy link beside the cashier path and name the exact heading. We can clarify how the rule applies to your account, device session or bank transfer record without changing the published Terms & Conditions.

ACCOUNT CONTROLS

Six Controls Behind Account Policy

We apply the Terms & Conditions through account records rather than vague promises. The same policy path covers phone verification, payment references, device sessions, cookie choices, account security and requests to change…

Data handling

We use the details needed to operate your account and check a payment record, such as your registered phone number and transaction reference. The Terms & Conditions describe why those details are collected and how they support account and wallet checks.

Cookie choices

Cookies can preserve the policy page state, login session and selected account settings on your device. Our Terms & Conditions explain their role, so you can check the relevant browser controls before continuing from mobile or desktop.

Account security

Keep your phone access, password and verification details private. If a session looks unfamiliar, stop using it and contact us through the account route named in the policy. We use the account record to identify the correct security question.

Record retention

Payment references, account actions and policy-related messages may be retained for the period stated in the Terms & Conditions. This helps us trace a QRIS receipt, virtual account entry or bank transfer when a status needs review.

Change requests

You can ask us to correct account details through the contact route beside login. Include the field that needs changing and the registered phone number; we may request an account check before applying an amendment to the stored record.

Policy owner

Questions about these Terms & Conditions go to our account support route, not to a payment wallet provider. Name the clause, account step or wallet reference involved, and we will direct the request to the team handling policy matters.

Questions About dki4d Terms & Conditions

These Terms & Conditions answers focus on the account decisions you may need to make before using dki4d. We cover local-law access, verification, wallet records, cookies, data changes and the contact path. If your question concerns a clause not listed here, use the policy contact route and quote the heading shown on this page.

They cover account opening, phone verification, account security, wallet references, device sessions, cookies, record retention and policy contact steps. They also explain that access or eligibility depends on local law and that where local law permits, the displayed account path still applies.

You may follow the account path where local law permits and complete the phone verification shown before access. Keep your details accurate and use only your own account information. If eligibility is unclear, contact us before connecting DANA, OVO, GoPay or QRIS.

We match the registered phone number with the payment reference and status supplied at the account step. For QRIS, DANA, OVO, GoPay, bank transfer or virtual account records, keep the receipt available so we can identify the correct transaction.

Do not create a second account to bypass the check. Use the account help route beside login and provide your registered phone number, device type and the relevant Terms & Conditions heading. We can then identify whether the issue concerns your details or the access rule.

Cookies can keep a policy page state, login session or account setting on your browser. The Terms & Conditions describe that use, while your browser controls manage cookie choices. Check those settings if the policy page behaves differently on mobile and desktop.

Yes. Contact us through the policy route and state which detail is incorrect, such as a phone number or account field. Include the registered number and be ready for an account check. We record the request and apply changes according to the stated policy.

Start with the contact link beside the login or cashier path and quote the exact clause heading. Include only the account and payment details needed to locate the issue. We will clarify the Terms & Conditions that apply to your request and explain the next step.