Lovable: How to Subscribe (AI App Builder / Full-Stack Generation)
A practical Lovable subscription checklist: choose the right workspace, compare current plans, understand credits, and investigate a failed payment without guessing its cause.
1. Choose the workspace before choosing the plan
Begin with the project you actually want to finish. Write down its purpose, who will use it, and who should control the subscription. For a personal prototype, that might be you; for a client project, agree on ownership and the payer before anyone enters payment details. Keep that agreement in your own project notes so a future handover does not depend on someone remembering a chat conversation. Lovable's pricing FAQ (https://lovable.dev/pricing) says each plan belongs to a workspace and its members share credits. That makes the workspace name a useful item on your purchase checklist. Before confirming, compare the workspace you are viewing with the one recorded for the project. If you cannot establish which workspace the offer applies to, stop at the review screen and ask Lovable to clarify. A higher tier is not a substitute for resolving that uncertainty.
2. Compare the offer shown to your account
Use the official pricing page (https://lovable.dev/pricing) for the current plan comparison. This guide deliberately leaves subscription prices and allowances to that page. When comparing offers, capture the currency, billing interval, total due now, and the features you need. Put monthly and annual offers on separate lines in your notes; do not compare a monthly equivalent with an upfront total as though they were the same cash commitment. Prepare a short requirement list before looking at larger tiers. For example: a working registration flow, a private test project, collaboration with a colleague, or a particular deployment requirement. Ask which requirement justifies the proposed upgrade. If the answer is only that you might need it later, consider testing the current setup first. The useful comparison is the offer against your defined task, with uncertain requirements marked for confirmation rather than treated as included.
3. Separate development work from running the app
Lovable's credit documentation (https://docs.lovable.dev/introduction/credits-and-usage) describes credit usage across building, Cloud and AI features in deployed apps. It directs you to Workspace settings → Plans & credit usage to inspect the balance and usage. Use that view as the starting point for your own record, and read the current documentation when interpreting the categories shown to your workspace. For planning, keep two lists: work needed to produce the app, and activity expected after people start using it. The first might include revising a form and testing error states. The second might include people uploading files or using an AI feature. These are planning examples, not a claim about the price of any particular operation. Estimate each separately, then compare your estimates with observed usage. A completed visual prototype alone is not enough evidence to decide what you should spend on operating the finished project.
No overseas card needed: cocodot's OpenAI-compatible API — switch your base_url to call the models on sale.
Top up via Alipay / WeChat Pay (RMB), USDT / USDC · billed per token · switch your base_url to connect
4. Make a purchase record you can reconcile
Before paying, prepare a compact purchase record: account email, workspace name, selected offer, billing interval, total displayed, and the time you reviewed it. Keep sensitive payment details out of shared notes. After checkout, add the receipt reference and the status you see in the account. This record gives you something concrete to compare when the payment screen and the project screen appear to disagree. For Pro and Business bought on lovable.dev, the official billing guide (https://docs.lovable.dev/introduction/invoices-and-billing) directs owners and admins to Workspace settings → Plans & credit usage → Manage → Invoices & payments for payment-method management. Use the guide that matches your actual purchase channel; do not assume every purchase follows the web route. Review the final summary again after changing a payment method. If you are unsure whether a previous purchase completed, resolve its status before submitting another one.
5. Investigate a declined payment without guessing
Ask your card issuer and the merchant to confirm the reason for the decline. A missing entry in your bank app does not show where the request was stopped, and a decline at another merchant does not by itself identify the cause. For your own checklist, record the exact error text, attempted amount, currency, time and workspace. Check whether the payment details are complete, whether the card balance covers the displayed purchase, and whether any requested verification remains unfinished. These checks collect information; they do not prove which party refused the transaction. Send the merchant a concise description with sensitive card details removed, and ask the issuer what information it can confirm about the attempt. If considering a cocodot card, Lovable acceptance is unverified here. Begin with a small purchase if you decide to test it. This card is not tied to a personal address, and cocodot does not provide or assign any address. On the checkout page, enter the address you actually use as your billing address, fill in every field, and keep using the same one with the same merchant.
6. Check paid-but-missing access before buying again
The Lovable billing guide (https://docs.lovable.dev/introduction/invoices-and-billing) says to check subscription status in Plans & credit usage when payment has completed but the plan has not appeared, and to contact support if the plan still has not changed. That is a specific official route for a paid-but-missing-plan question. It is not evidence that every missing-credit problem has the same cause. For a missing-credit question, prepare a before-and-after comparison: workspace, balance observed, offer purchased, receipt reference, and time checked. Keep your observations separate from your interpretation. Write 'the receipt shows a purchase, and this workspace shows this balance' rather than declaring that the payment provider lost the credits. Ask support to reconcile the purchase with that workspace. This also gives another person a clear way to investigate without needing access to your card or a long account of every button you tried.
7. Measure a representative task before adding credits
Choose a small task with an observable finish: a form that validates required fields, a page that stays readable on a phone, or a search that handles an empty result. Record the starting usage, describe the task, inspect the result, and record the ending usage. Include the revisions needed to meet your acceptance criteria. Treat this as a planning experiment, not a promise that repeating the prompt will always consume the same amount. Keep a simple task ledger with columns for the request, result, corrections, and observed usage. Mark changes caused by an unclear brief separately from changes caused by a new requirement. That distinction helps you improve the next request without claiming that longer prompts automatically save credits. Lovable's top-up documentation (https://docs.lovable.dev/introduction/credit-top-ups) describes one-time credit purchases and automatic top-ups for Pro and Business. Read its current eligibility and controls before choosing either, and decide who should authorize additional purchases.
8. Set a review point before committing further
Decide in advance when you will review the subscription: after the prototype passes its acceptance checks, before inviting a wider audience, or before the next purchase you are considering. At that review, compare the original scope with the working result and the usage you recorded. Check unfinished requirements and ask whether they still justify continuing with the same tool and offer. For cancellation, credit expiry, refunds and plan changes, consult the current Lovable credit documentation (https://docs.lovable.dev/introduction/credits-and-usage) and billing guide rather than assuming a policy from another AI service applies. Keep a dated copy of the terms relevant to your decision. If your next step involves editing the project in another tool, verify the actual handover requirements before depending on it; the separate AI coding tools guide (/hub/ai-coding-tools) can help frame that comparison. A subscription decision should follow the project evidence you have collected, including unresolved questions.
What to verify before paying for Lovable
| Decision | Evidence to collect | Your next step |
|---|---|---|
| Which workspace? | Workspace name and intended project | Confirm the purchase is for the workspace you intend to fund |
| Which offer? | Current checkout total and billing interval | Compare the same interval and currency |
| What will use credits? | Build tasks and expected live-app activity | Write separate estimates for development and ongoing operation |
| Payment failed? | Exact error, time and payment status | Ask the issuer and merchant to confirm the cause |
| Paid but no upgrade? | Receipt and current subscription status | Reconcile those records before making another purchase |
| Considering a virtual card? | Merchant eligibility and actual checkout result | Test a small purchase; acceptance is unverified here |