Why our help center starts with the awkward questions

Most help centers are built like sales pages in disguise. The first questions are the flattering ones: "How fast is delivery?", "Is it secure?", "Why choose us?". The questions customers actually type into a search box late at night, "Why was my card declined?", "Do I get my fees back?", "Can I phone someone?", sit further down, if they are there at all.

We tried to reverse that. A help center is the only page a customer reads when something has already gone wrong, so it should answer the question they are afraid to ask. This note explains how ours is organized and why the uncomfortable answers are deliberately easy to find.

Organized by situation, not by department

Our help center is divided into eight topics, each named for the situation you are in rather than for an internal team:

1. Getting in: signing up, the confirmation email, the authenticator every account carries.
2. The order: what happens between your brief and a working card.
3. Paying for it: the two payment routes and the details that make a transfer easy to match.
4. The price: two numbers, held while you pay.
5. Your card: seeing details, spending, frozen and declined.
6. Money back: which balances return and how.
7. Staying safe: how accounts are protected and what we will never ask for.
8. Talking to us: where to write and what to include.

Each topic has a one-line summary, so you can tell from the list where your question lives.

The awkward questions we answer

Within those topics, we made a point of including the questions that make us look less convenient:

• "Why can't I skip the authenticator step?" Because a password alone is too easy to steal, and the accounts hold card details.
• "Why does a human look at my payment?" Because a script would issue cards against payments that never landed.
• "What gets an order turned down?" With the reasons listed.
• "I picked the wrong network." With an honest answer: funds sent over a network our address does not use may be gone for good.
• "If I ask for a refund, do the fees come back too?" No, and the answer says why.
• "Why is a small leftover balance not refundable?" With the rule and the reason.
• "Which shops will take the card?" With the admission that we cannot promise every shop will.
• "Can I phone you?" No, and why that is deliberate.

None of these answers sells anything. All of them prevent a worse conversation later.

Why the honest "no" helps

A clear "no" in the help center is better than a vague "maybe" that becomes a "no" in a support ticket. The customer who reads "the fees are not refunded" before paying can decide not to pay. The customer who discovers it afterward feels misled, with some justification.

This is the same principle behind publishing the fee rule and the refund policy before checkout: a disappointing answer, given early, is a form of respect.

Writing for a worried reader

Help answers are written for someone who may be anxious. That shapes the style:

• the answer comes first, then the explanation;
• sentences are short and use the same words as the interface;
• every answer ends with a next step where there is one: open a ticket from the order, check spam, wait for confirmations;
• we say who acts: you, us, the network or a merchant.

We described how we choose those interface words in how we name things.

Testing the desk

A help center tells you what a business says. Support tells you what it does. We encourage readers to test both, as we suggested in test the support desk before you trust the seller: ask a question before you order and see whether a person answers it properly.

What we leave out

There is no "Why choose us?" question, no list of advantages and no comparison with competitors. Those belong to marketing, and the help center is not marketing. We also avoid answers that promise outcomes we do not control, such as delivery times at the blockchain level or acceptance at a particular merchant.

Keeping it current

Answers go stale when the product changes. When we change a fee, a limit or a process, the help answer changes with it, and placeholders in the answers pull the current figures from the same settings the checkout uses. That way the help center and the order page cannot disagree about the price.

Why this is a design decision

It would have been easy to treat the help center as an afterthought. We treated it as part of the product, because for many customers it is the first page they read carefully. Like our decision to show no star ratings, it reflects one idea: the most persuasive thing a service can do is answer hard questions in public.

How an answer is built

Most answers in the help center follow the same small structure. The question is written the way a customer would ask it, sometimes as a statement of the problem: "I picked the wrong network." The first sentence answers it directly, even when the answer is no. The next sentences explain why, briefly. The last sentence, where there is one, says what to do next and where.

That structure makes answers easy to scan and hard to dodge. An answer that begins with background and reaches the point in the fourth sentence has usually been written to soften bad news. Putting the answer first removes that option, for us as much as for the reader.

Questions in the customer's words

We write the questions themselves in ordinary language, the way they arrive in tickets: "The confirmation email hasn't arrived.", "My phone is gone, and my authenticator with it." A help center written in the company's vocabulary forces customers to translate their problem before they can find the answer. Written in theirs, the right question is recognizable at a glance, even by someone who is stressed and skimming.

Questions people ask

Why is there no phone support?

Written support lets us look properly at your account and keeps a record for both sides. It also makes fake "support calls" easy to spot.

What if my question is not in the help center?

Open a ticket or email us. If the question comes up often, it will be added.

Are the figures in the help center up to date?

Yes. They come from the same settings the order page uses.