Reference

What this pestoto FAQ covers

Our FAQ page gives you the shortest route to the answers people ask first: account steps, DANA/OVO/GoPay/QRIS checks, and the support path if you need a hand.

DANAOVOGoPayQRIS

Browse lobby Read FAQ

How this FAQ page works

This page is built for fast reading. We keep the answers grouped by topic, so you can jump to account questions, wallet timing, or the next contact step without hunting through the lobby. The wording stays plain for Indonesian readers and keeps DANA, OVO, GoPay, and QRIS in full so the names match what you see in your app. When a question

touches access or eligibility, we say it depends on local law and is available only where local law permits. That is the standard we use on phone and desktop.

DANA
OVO
GoPay
QRIS

QUICK PATHS

Which FAQ paths matter first

Each card below points you to a different kind of answer: where the FAQ sits, how local rails are named, and what we say when access is subject…

Updated today

LOBBY

Where the FAQ sits

We place the main answers near the account path, so you can move from the page into the lobby without losing the thread. The question order stays short and readable on mobile.

WALLET

Local rail wording

When an answer mentions DANA, OVO, GoPay, or QRIS, we keep the wording exact and point to the same fields you see in your wallet app before you send anything.

RULES

Access and eligibility

If the question is about who can join or what applies, we state that it depends on local law and is available only where local law permits. No vague wording.

AT A GLANCE

How the FAQ is structured

local rails named in answers

support routes linked from the page

law line for access and eligibility

device paths we mention

REACH US

Where you can reach us

If the FAQ does not fully answer your case, we give you a clear next step instead of making you search around.

Live chat Open chat from the page when you want the quickest reply. We use the same FAQ queue, so the team sees your question in the order you sent it during 10:00-22:00 WIB.

WhatsApp Send the short version there when a wallet screen or account step needs a screenshot. Keep the question in one message and we will tie it back to the same FAQ item.

Email Use email for longer cases, especially when you want to keep a written trail. Include your account name and the page topic so we can answer without extra back-and-forth.

CLEAR SIGNALS

What keeps the answers clear

We write the answers the same way every time: direct first, then the condition, then the next action.

Direct answer first

We start with the point you asked for, then add the step that matters. That way you do not read three lines before finding the part that helps.

Local names kept

DANA, OVO, GoPay, and QRIS stay in their exact names so you can match the FAQ text to what you see in your wallet app.

Same step order

When a question needs a process, we keep the sequence stable across the page. You know what comes first, what comes next, and what to check before you move on.

Law-based wording

If a topic depends on access or eligibility, we say it depends on local law and is available only where local law permits. No side statements, no loose phrasing.

Device-aware text

We mention when a page works better on phone or desktop, so you can choose the screen that makes the answer easiest to read and avoid extra tapping.

Clear handoff

If the FAQ stops short, we point you to chat, WhatsApp, or email with the same case details already laid out. That saves you from repeating the question.

ANSWER FLOW

How answer styles differ

Different questions need different amounts of detail, so we keep the pattern steady. Short account answers stay short, wallet questions name the rail, access questions carry the local-law line, and support questions…

Account

We tell you which step comes first, so you can open the account path, check the detail, and move on without guessing.

Wallet

Questions about DANA, OVO, GoPay, or QRIS keep the rail name visible and name the field you should confirm before you send anything.

Access

If the question is about who can join, we answer with the local-law line and keep the wording narrow.

Device

For phone or desktop, we say which screen is easier for the step, then note any tap or click that changes.

Support

When the answer needs a person, we send you to chat, WhatsApp, or email with the same case summary.

Timing

If a detail depends on processing time, we state the usual order and the point where you should wait for a reply.

Edge case

When your case is unusual, we name the part that needs checking instead of writing a vague answer.

VISIBLE MARKS

What you can spot here

These are the visible markers that make the page feel direct. We keep the answer order steady, show the local-law line where it matters, and keep the copy…

Short question blocks Each answer block stays tight so you can scan the…

Law line visible When access or eligibility appears, we place the local-law wording…

Same order everywhere The page keeps the same question flow on phone and…

Plain account steps If a question needs action, we show the step in…

Chat handoff cue Where the FAQ cannot finish the job, we show the…

Indonesia context The wording stays aimed at Indonesia, with familiar local names…

Questions people ask first

This last set covers the most searched FAQ prompts: what the page answers, how to find the right line fast, where to go when a case needs a person, and how local law affects access. We keep each answer short enough to read on mobile and clear enough to compare on desktop.

It covers the questions people ask first: account steps, wallet wording, support channels, device behavior, and the local-law line for access. We keep the answers short so you can find the next action fast.

Start with the section that matches your question, then read the first sentence of the answer. We put the direct point first, so you do not need to read the whole paragraph before you know where to go.

Yes. When a question needs wallet context, we name DANA, OVO, GoPay, and QRIS in full and keep the wording matched to the names you see in your app.

We say it depends on local law and is available only where local law permits. That line appears in the answer itself, so you do not need to guess how it applies.

Yes. The page is written for mobile first, with short blocks and the same order on desktop when you want a wider screen. That makes scanning faster on a small display.

Use live chat, WhatsApp, or email with the same case details. We keep the handoff simple, so you can send the topic once and get a direct reply from the right path.