Quick answers about your rakatoto account, our lobby, and the DANA, OVO, GoPay and QRIS flows you'll use day to day. We've grouped the questions we hear most...
This FAQ page is a single scrollable reference for the questions you've asked us most. We've kept the answers short, written in plain en-ID English, and grouped by topic so you don't dig through menus. If a question touches a payment rail, we name it directly — DANA, OVO, GoPay or QRIS — so you know which flow applies. If your question
isn't answered here, jump to the support section near the bottom and we'll route you to a human on our team.
Three FAQ clusters cover most of what you'll ask us in your first week. Skim the cards, then jump to the matching question further down.
If your question isn't on this FAQ page, these are the three paths to a real answer.
Open chat from the lobby header any time. Our team handles FAQ overflow first — anything not covered here goes straight to a live agent for a same-session reply.
Send the full context to our inbox and we'll write back with a documented answer. Useful when your question needs screenshots or a DANA, OVO, GoPay or QRIS reference attached.
A longer-form companion to this FAQ. Search by keyword, browse by category, and bookmark the articles you reference most when setting up your account.
How we keep FAQ answers accurate and current as the lobby and payment flows evolve.
Every FAQ answer is drafted by the rakatoto team that built the feature it covers — not copied from a generic template. If a flow changes, the FAQ gets edited the same week.
FAQ entries carry quiet revision dates so our support team knows when an answer was last verified against the current lobby and payment behaviour you'd see today.
Payment FAQ answers are checked against DANA, OVO, GoPay and QRIS rail behaviour before publishing, so what you read here matches what the screen actually does.
We write FAQ answers in en-ID English a first-time reader can follow. No jargon walls, no legalese unless the question genuinely demands a precise policy quote.
Where an FAQ answer touches our terms or a payment policy, we link to the source document so you can read the full clause instead of trusting a summary.
Every FAQ entry has a thumbs control. Negative feedback routes to the editor who owns that topic, and the answer gets rewritten — usually within a few days.
Why this FAQ reads differently from the generic help pages you'll find elsewhere.
Six things that shape how this FAQ feels to read and use — beyond the answers themselves.