Reference

Open bursa33 FAQ for quick answers

We built this FAQ so you can find account steps, device checks, and support paths without hunting through long pages.

Search by topicMobile friendlyLocal law appliesSupport in one place

Browse the FAQ flow before you ask

This page is set up for fast scanning: search a topic, tap a category, and read the answer without losing your place. We keep the FAQ focused on real account questions, from opening a profile to checking browser behaviour and support handoff, so you do not have to sort through generic copy. When a question touches wallet flow, we point to the

local rails we support in Indonesia: DANA, OVO, GoPay, and QRIS. The same layout works on phone and desktop, and every eligibility step still follows local law where it applies.

DANA
OVO
GoPay
QRIS

WHAT STANDS OUT

Explore what the FAQ keeps visible

Each card points to a different part of the FAQ, so you can move from search to wallet context to policy without reading a long block.

SEARCH FIRST

Jump straight to the right answer

The search box at the top helps you find account, device, or support answers fast, and…

LOCAL RAILS

Wallet questions stay local

When a FAQ answer mentions funding, we name the Indonesia rails you expect: DANA, OVO, GoPay…

POLICY CHECK

Eligibility stays factual

If access or account use depends on region, we say so plainly and keep it tied…

PAGE STRUCTURE

Switch to the FAQ structure at a glance

FAQ areas on this page

help routes named here

local rails referenced

device views covered

HELP CHANNELS

Open support when the FAQ needs help

If the FAQ answer does not settle the issue, these channels give you a direct path to a person. We use live chat for the fastest turn, Telegram for short follow-up, and email for cases that need screenshots or a longer thread. The same contact paths are shown on the page so you can move from reading to asking without searching again.

Team online

Live chat

Use live chat when you want the fastest handoff from a FAQ answer to the next step. The chat panel shows when the desk is open, and we use it to point you to the exact section you need.

Telegram is useful when you already know the topic but need a shorter follow-up. Send the question title, and we can reply with the matching FAQ path or the next account step to check.

Email

Email works well for longer cases, especially when you need to paste screenshots or a login detail. We keep the thread tied to the FAQ topic so you do not repeat the same context.

EDITORIAL SIGNALS

Browse the trust signals behind each answer

These trust signals explain how we write the FAQ, not how we market the site. Each answer is kept short, the topic labels stay consistent, and device-specific steps are separated from general…

Plain answers

We keep each response short and direct, so the step, the condition, and the next action sit together in one place. That makes the FAQ easier to read when you are checking account, device, or support details.

Searchable topics

Each item is grouped by what you would actually ask, such as access, browser behaviour, or where to send a support message. The labels stay the same on desktop and mobile, which keeps the page easy to scan.

Device parity

The same wording appears on phone and desktop, but the layout adapts to the screen you are using. You can open one answer at a time on mobile, then compare longer entries on a wider display.

Local law line

When a question depends on region, we say that directly instead of blurring the answer. Access and eligibility steps are only shown where local law permits, which keeps the FAQ factual.

Account separation

Public answers stay separate from account-specific checks, so you can read the general help first and then move into support only when you need private details. That separation avoids extra back-and-forth.

Human handoff

If the FAQ stops at a point where your case needs a closer look, live chat, Telegram, or email can take over. We keep the wording and the handoff path connected so you do not start from zero.

Switch between FAQ paths with less friction

This comparison section shows how the FAQ changes with the way you read it.

Search first

Use search when you know a keyword like login, browser, or QRIS. It gets you to the exact answer faster than opening every section one by one.

Browse categories

Browse when you only know the topic, not the wording. The categories group similar questions together, which helps you compare account help, support, and eligibility without guessing the right search term.

Mobile layout

On mobile, each answer opens in a narrow stack, so you can read one question, close it, and move on. That works well when you are checking a step while on the move.

Desktop layout

On desktop, the wider view makes longer FAQ entries easier to compare side by side. It is better when you want to read a support path, then jump back to an earlier answer.

General help

General help covers the same answer for everyone, while account-specific topics stay out of the public page. That keeps the FAQ clean and reduces confusion when a question needs private details.

Support handoff

The FAQ gives the first answer; support gives the next action. If you need screenshots, a login check, or a regional case, we move you to the channel that fits the question.

Local law

Some answers are the same across regions, but access and eligibility can change where local law differs. We say that plainly so you know which steps apply before you go further.

VISIBLE PIECES

Explore the FAQ details we keep visible

These visible pieces make the page feel easy to use without turning it into a long article.

Search box The first thing you see is a search box for…

Category chips We use short category chips for account, device, support, and…

Accordion rows Each answer opens in a single row, which lets you…

Support strip A help strip near the bottom points you to live…

Device labels We label answers that change by device, such as phone…

Local-law footer The footer reminder keeps the wording tied to local law…

Open the common FAQ questions

If you are reading the FAQ for the first time, these are the questions we see most often. They focus on how to find an answer, when support should take over, and where local law changes the step, so you can use the page without guessing. The wording stays simple on purpose, because a FAQ should be quick to scan and easy to return to later.

Use the search box first, then open the matching category. If your question is about login, browser behaviour, or support, the answer usually sits in one of those sections, so you do not need to read everything.

Yes. The mobile layout keeps each answer in a stacked card, so you can open one item, read it, and close it without losing your place. The same content also fits desktop cleanly.

No account is needed for general FAQ pages. If your question is private, such as profile changes or a login check, open your account first and then use support for the next step.

We cover account access, device behaviour, support channels, local-law eligibility, and the local rails named on this page. If a topic needs a private check, we move it out of the public answers.

Send the exact question title through live chat or Telegram, and we will point you to the matching answer. If screenshots or account details are needed, email keeps the thread tidy.

Some entries stay the same, but access and eligibility can change when local law differs. We say that directly, and we only show the steps that apply where local law permits.