Charged After Cancelling Lovable? Refund Steps

Why did Lovable charge me after I cancelled?

The most common causes of a charge after cancellation are: the downgrade did not fully process before the renewal date, the cancel confirmation was not received or the step was not completed, or an annual plan renewal fired automatically. Less commonly, a payment method update accidentally reactivated a cancelled subscription.

Lovable's billing runs on Stripe, which processes renewals automatically at the start of each billing cycle. If your cancellation request arrived within the processing window — sometimes as close as 24 hours before renewal — the charge may have already been queued. In these cases, Lovable support can issue a refund even if the technical cancellation arrived a day late.

Before contacting support, confirm that your cancellation actually completed. Go to Settings → Plans & Billing inside Lovable and check whether your plan currently shows as Free. If it still shows as a paid plan, the cancellation may not have processed — in which case complete the downgrade first, then request the refund.

What evidence do I need before contacting support?

Gather three things before reaching out: your cancellation confirmation email with its timestamp, your bank or card statement showing the charge amount and date, and a screenshot of your current Settings → Plans & Billing page. The more clearly you can show the timeline — cancelled on date X, charged on date Y — the faster the support team can process the refund.

1. Find the cancellation confirmation email Lovable sent when you downgraded.
2. Note the exact date and time shown in that email.
3. Find your bank or card statement showing the charge — note the amount, date, and merchant name.
4. Log into Lovable and take a screenshot of Settings → Plans & Billing showing your current plan status.
5. Note your Lovable account email address — support will need it to look up your billing record.

How do I contact Lovable support for a refund?

Lovable support is reached via email at support@lovable.dev or through the in-app help widget. Email is recommended for billing disputes because it creates a written record. Include your account email, the charge amount and date, your cancellation confirmation, and a clear one-sentence statement of what you are requesting.

A clear, factual email resolves faster than a vague complaint. State exactly: the date you cancelled, the amount charged after that date, and that you are requesting a full refund of the post-cancellation charge. Avoid lengthy context — support agents work from the billing record and need the specifics, not the backstory.

Sample email subject: 'Refund request — charged after cancellation on [date]'. In the body, include: your account email, the cancellation date, the charge date and amount, and attach the cancellation confirmation email as evidence. Keep the email under 200 words.

1. Draft an email to support@lovable.dev with subject: 'Refund request — charged [amount] after cancellation on [date]'.
2. In the body: state your account email, cancellation date, charge date, and charge amount.
3. Attach your cancellation confirmation email as evidence.
4. Send the email and keep a copy in your sent folder.
5. Expect an initial response within 1–3 business days.
6. If no response in 5 business days, follow up with a short reply to the same thread.

What does Lovable's refund policy actually cover?

Lovable processes refunds for clear billing errors: charges after a confirmed cancellation, duplicate charges, and charges at incorrect amounts. The policy does not generally cover refunds for dissatisfaction with the product, unused credits within a billing period, or change-of-mind cancellations after a charge has processed for a new billing cycle.

Lovable's terms state that all charges are non-refundable except where required by applicable law or where there is a billing error on their part. A charge after a confirmed cancellation qualifies as a billing error. A charge for a month you signed up for and then decided not to use does not.

If your request falls outside Lovable's standard refund scope, you can also dispute the charge with your bank or card issuer as a last resort. Chargebacks are generally successful for documented billing errors, but they may result in account closure on the merchant's side. Use the support channel first.

What if Lovable support denies my refund request?

If support denies a refund for a charge that occurred after a documented cancellation, escalate via your bank's dispute process. A chargeback for a charge after confirmed cancellation is a strong case — you have a timestamped cancellation confirmation and a later charge date. Document everything before initiating the dispute.

To initiate a bank dispute: contact your card issuer's customer service, explain you were charged after a confirmed cancellation, provide the cancellation date and charge date, and request a chargeback. Most card issuers resolve these within 10–45 business days.

Before using a chargeback, attempt at least two rounds of support contact with Lovable. Banks and card networks expect merchants to have had a fair chance to resolve the dispute. Two unanswered or denied support emails establish that you made a good-faith effort.

How long does a Lovable refund take to arrive?

If Lovable approves a refund, the credit typically processes within 5–10 business days for card refunds. The timeline depends on your card issuer after Lovable initiates the refund — Lovable's action is immediate, but the credit reaching your statement takes additional days. Stripe (Lovable's payment processor) confirms refunds by email.

1. Wait for Lovable support to confirm the refund has been issued — this comes as an email.
2. Allow 5–10 business days for the credit to appear on your card statement.
3. If the credit does not appear after 10 business days, contact your card issuer and quote the refund date.
4. For PayPal charges, refunds process faster — typically 3–5 business days.
5. Keep the refund confirmation email from Lovable support for your records.