Payments

Paddle's script did not load within 20 seconds, which a content or script blocker usually causes. Allow Paddle's form on this page, or turn the blocker off for it, and reload. Nothing has been charged and no card was added.

Paddle has the card and has not finished saving it. Do not add it again: it appears under Payment method within a minute or two.

The card page checks with Cloud before it draws anything, each time it opens or reloads. When that check cannot confirm the card yet, often no more than a dropped connection, it reads "Reload this page in a minute." and adds that if you entered a card, it appears on the billing page once Paddle confirms it. Reload once more: a card that was entered is on file within a minute or two.

Paddle refused to show the form for this checkout, so nothing was saved. Go back to Billing and press Add a card or Change card again. If it happens again, contact support.

The page was opened without starting a checkout from Billing, or the checkout has been used or has expired after an hour. Start again from Billing.

The organization has a card on file, so Payment method offers Change card instead of Add a card. Use it to replace the card.

The page adds "It was started from the billing of another of your organizations, and only that organization can keep its card. Switch back to it to finish, or add a card to this one from its own billing." The console moved to another organization, in this tab or another, after Add a card was pressed. Switch back to the organization you started from at the top of the sidebar and press Add a card on its billing again. If Paddle had already taken the card, the page reads instead "Paddle has the card, for the organization this checkout was started in, which is not the one the console is in now. Switch back to that organization to see it on its billing."

Paddle says why in its form, where you can try the same card again or another. A card your bank asks you to confirm is saved only once you confirm it.

Paddle took the payment and has not confirmed it yet. Do not pay again. The statement reads Paid as soon as Paddle confirms.

Check Statements on Billing first: a month that reads Paid needs nothing more. If it still reads Payment failed, press Pay now again, and if this message comes back, contact support.

The page names the month and adds "Nothing is owed for it. Its document is on the billing page." Nothing to do. A month that is not owed yet reads "Nothing is owed for November 2026 yet" instead, and one billed by invoice says to pay it from the invoice's link.

The page adds "This address does not name a month of this organization. A month of another of your organizations is paid from its own billing, which lists every month and what is owed." The link is old, or the month belongs to another of your organizations: switch to that one and press Pay now on its billing.

This is an invoice's payment link. The page adds "A link stops working once its invoice is paid or cancelled, or the link is replaced. If you have not paid, reply to the email the invoice came with to ask for a new link." Check Statements first: a statement that reads Paid needs nothing more, and one that reads Overdue is normally given a new link under Pay now within the hour. If it is not yet, reply to the email the invoice came with to ask for one.

Cloud checks a paid or voided invoice against the invoicing service the next time you open billing, not the instant you pay it. Open Billing again: once the statement reads Paid, new paid work is accepted. If it still reads Overdue after a few minutes, contact support.

Cloud starts the services about a minute after the last cause clears, and emails you "Paid services in Kopi Tiga are starting again" once they are all back. Check that every cause has cleared: each month on Statements reads Paid, or for the limit, the next month has begun or the limit was raised. An invoice paid through its link counts once Cloud has read it, which it does the next time you open Billing. A service you had stopped yourself before the stop stays stopped. If they are still stopped a few minutes after every cause has cleared, contact support.

That is how the stop works. Your free application and free database are never stopped for billing, in whichever organization they run, and nothing on them is refused for it.

An organization billed by card needs a card on file while it runs paid services, not only when a month closes. Cloud emailed you the date when it first found paid services running there with none: "Add a card to Kopi Tiga by 13 December 2026 at 12:00 UTC, or its paid services stop". Add a card under Payment method and the services start again. If you no longer want them, delete them: the stop clears once no paid service is left.

Paying before the archive date keeps everything; paying after it restores nothing. The services were deleted when they were archived, and Cloud does not rebuild them. Their final backups stay on the Archived tab of Storage until the date in the email: download them and create the services again. Contact support for help rebuilding one.

Cloud starts archiving within the hour after the date, one final backup at a time, and deletes a service only once every final backup of it has finished. If a final backup fails, the service stays, stopped, and Cloud tries again a day later. Until a service is deleted, clearing the stop still keeps it: pay the month or add a card, and it starts again with the rest.

An application with no volume, a Redis database, a compose stack and a service that never ran have nothing Cloud backs up, so they were deleted with no final backup. The email at archiving says which. Every other archived service has a final backup of its database, or one of each volume the application had.

A final backup reads this instead of Download until Cloud has verified its stored file, usually within the hour after the backup. Open the Archived tab again later. Once the date the backups are kept until has passed, nothing can be downloaded: Cloud deletes them.