DonatePay Settings
People ask this as
- how do I connect DonatePay
- where do I get the DonatePay API token
- the token field is empty after I saved it
- the badge says Disabled
- the badge says New token required
What this page is
Connections → Monetization → DonatePay is where DonatePay is given an API token so donations reach the app. Two things live here: the Accept donations switch and the token itself.
How to set it up
- Open Connections → Monetization and press Connect DonatePay on the card. On an already connected card the same page opens with Configure. The arrow in the top left, Back, returns to the list.
- The page is headed DonatePay Settings, with "Configure DonatePay integration to receive donation notifications." under it.
- The top row is Accept donations, subtitled DonatePay, with a badge and a switch. The switch acts the moment you flip it — it is not waiting for the save button. With it off the badge reads Disabled and nothing is received.
- Press Open the DonatePay API page. It opens donatepay.ru in your ordinary browser. The hint says what to expect: "DonatePay issues the token on its own API page — it opens only after you sign in."
- Copy the token from that page and paste it into API Access Token. The field hides what you type; while it is empty it prompts "Enter API Token (available in DonatePay panel)".
- Press Save Settings in the top right corner. It reports back on itself — Saving…, then Saved, or Error if the token was not stored. After a successful save the page closes itself and returns to the list of services.
- Saving with the field empty and no token stored yet is refused with "Please enter your API token."
- Reopen the page to check. The token field is empty on purpose — a stored token is never shown back to you. That it exists is said by the prompt inside the field: "Token saved — leave empty to keep it". Leaving the field empty and pressing Save Settings keeps the stored token untouched; to replace it, type the new one over.
- The badge beside the switch tells you where the connection stands: Not connected (no token yet), Disabled (the switch is off), Connecting…, New token required, Connection error, or Connected as {username}. It refreshes by itself every few seconds while the page is open.
- New token required means the stored token no longer works. Get a fresh one on the DonatePay API page and save it over the old one.
What it cannot do
- The token cannot be read back out of the app — the field shows nothing, and there is no reveal control.
- There is no browser sign-in here: the token is copied by hand. The button only opens the DonatePay page, it does not fetch anything.
- The account name is not typed in. It arrives with the connection, and until then the badge shows the connected state with no name after it — the card in the list explains this as "Account name appears after the first donation".
- The switch only governs whether DonatePay is accepted. It is not the module's on/off in the catalog, and it does not disconnect anything else.
- Disconnecting and Remove connection (the bin icon) are on the DonatePay card under Connections → Monetization, not on this page.
- No donations, amounts or history are displayed here — this page is only about access.