BOTLOBBIES.ORG
Payments

What should I do if payment completed but activation is still being checked?

Return to the existing purchase and let the site verify its Stripe confirmation. A payment success screen alone does not complete every account-linking and bot-activation step, so check the existing transaction before paying again.

Payment confirmation and service access

The service checks the Stripe session or subscription against the purchase it has recorded. A paid plan needs confirmed payment conditions; a card-based trial needs its own verified zero-today subscription and payment-method conditions. The website also needs to associate the activated bot with the correct web account. A return from Stripe can therefore be followed by a verification or account-access screen. Do not treat a short delay on that screen as proof that the payment failed, or as proof that the bot is already assigned to the account you expected.

Follow the purchase you already started

Use the return link and the website's existing payment or renewal controls for that same purchase. If you have an account, make sure you sign in to the intended one; if the confirmed activation offers registration, complete that step. Keep any visible purchase or payment reference. Repeatedly starting independent checkouts can make the situation harder to understand and is not a reliable way to force activation. A temporary verification error should lead to checking the existing state rather than assuming that another charge is necessary.

When to ask for help

If payment and access remain inconsistent, contact support with the approximate time, the plan, the amount and currency, the relevant receipt or purchase reference and the exact visible error. State whether Stripe reported success and whether you reached the website account step. Share those details privately, leaving out full card numbers, passwords and authorization tokens. The team can investigate the specific purchase; there is no published guarantee that every activation finishes in a fixed number of seconds, and an error message by itself does not establish the cause.