Code of conduct

Flint Help is a record of how Flint works in practice: what broke, what fixed it, and what Flint should build next. Ask in the open when you can, so the next person finds the answer instead of asking again.

Post the endpoint you called, the request id, what you expected, and what came back. Without those, the first replies you get are questions back at you.

Reply to the person, not to the mistake. Disagree with an answer as much as you like. Do not go after whoever wrote it.

Card numbers, API keys, bank details, and other people's personal data do not belong in a thread. Flint rejects a post that contains them and tells you which line to fix. When the answer needs those details, ask Flint privately instead.

Two unrelated problems get two threads. A thread that answers one question is the one that turns up when someone searches for it.

Accept the reply that fixed your problem. It moves to the top of the thread, and accepted answers are how members earn the Helper badge.

Flint moves a thread private when answering it needs your account, your payouts, or your billing. After that only the people on the thread can open it.

Report a post from its menu and say what is wrong with it. A moderator reads every report. They can dismiss it, remove the post, lock the thread, or suspend the author.

Send security vulnerabilities to security@withflintpay.com. Never open a public thread about one.