DonatePay Settings

Comes with strAImer: this module is installed together with the app, so there is nothing to download. It is listed under Module Catalog → Built-in.

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

1. 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.
2. The page is headed DonatePay Settings, with "Configure DonatePay integration to receive donation notifications." under it.
3. 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.
4. 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."
5. 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)".
6. 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.
7. Saving with the field empty and no token stored yet is refused with "Please enter your API token."
8. 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.
9. 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.
10. 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.

A refusal is not taken as final at once. If DonatePay has accepted this token before, a refusal is answered with a pause and another try: 5 seconds, then 10, 20 and so on, up to five minutes. The badge shows Connection error from the third refusal in a row, and New token required only after refusals have gone on for ten minutes without a single accepted answer (two minutes right after a start or a save). Even then the token is tried again every five minutes, and the badge turns back by itself once DonatePay accepts it. A token that DonatePay has never accepted asks for a replacement at once.

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. The app asks DonatePay for it as soon as the token is accepted, so it shows up with the connection and no donation is needed. If DonatePay does not give a name out, the badge and the card read DonatePay User instead.
• 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.