NewSee how
FirstSales
All updates
Fix5 min read

Cancelling a trial really cancels it

Trial cancellation now cancels with the payment provider too, so your card is never charged at trial end, and onboarding no longer dead-ends.

Cancelling a trial should mean the trial is over, full stop. It was not always doing that.

What changed

Previously, cancelling a trial inside FirstSales did not reliably cancel the corresponding subscription with the payment provider. In some cases, the trial showed as cancelled in your account while the underlying subscription kept running in the background, which meant your card could still be charged when the trial period ended, even though you had told FirstSales you did not want to continue. From your side, everything looked cancelled: the account reflected it, the trial banner was gone. But the subscription record with the payment provider was a separate system, and the two were not always kept in sync.

Separately, some users hit a "Validation failed" error partway through onboarding that stopped them from finishing setup at all. This was tied to the same underlying billing state handling and left new signups stuck with no way to move forward, sometimes on their very first attempt to set up an account, before they had gotten to use any part of the product.

Both issues are fixed. Cancelling a trial now cancels the subscription with the payment provider at the same time it updates your FirstSales account, so there is no gap where a charge could still go through. The onboarding validation error that was blocking new signups is also resolved, so onboarding completes normally. The two fixes came from the same underlying billing state work, since both bugs traced back to how trial and subscription state were kept consistent across FirstSales and the payment provider.

The fix covers cancellation regardless of when in the trial period you cancel. Whether you cancel on day one or on the last day before the trial would have converted to a paid subscription, the same cancellation path now reaches the payment provider and stops the subscription from continuing, so there is no window during the trial where a cancellation could be recorded on your side without actually taking effect on the billing side.

How to use it

There is nothing new to do here. Cancel a trial the same way you always have, from your billing or account settings. The fix is in what happens behind the scenes when you cancel, not in how you trigger it, so there is no new button, no new confirmation step, and no change to the cancellation flow itself.

If you cancelled a trial before this fix shipped and are unsure whether you were charged, check your billing history in account settings, or reach out to support to confirm your subscription status with the payment provider. Support can look up the actual subscription state on the provider's side directly, which is the authoritative source of whether a charge did or did not happen.

If you are partway through onboarding and previously hit a validation error that stopped you, you can now go back and complete onboarding without running into that same wall. If you still see an error, it is worth reaching out to support so the specific case can be looked at, since this fix addresses the known cause but any new report helps confirm nothing similar is still lurking.

If you are considering starting a new trial and had a bad experience with cancellation or onboarding in the past, both of the underlying issues are now resolved, so a fresh signup and, if you decide it is not the right fit, a fresh cancellation should both go smoothly.

Why it matters

Getting charged after you cancelled is the kind of mistake that erodes trust fast, even when it is an honest bug rather than anything deliberate. A trial is supposed to be a low-risk way to evaluate a product; if cancelling it does not reliably prevent a charge, that risk stops being low, and it undermines the entire point of offering a trial in the first place. Fixing this closes that gap so cancelling a trial does exactly what it says: your card is not charged, and there is no lingering subscription running in the background.

Fixing the onboarding dead-end matters just as much. A new user who hits an unexplained validation error during signup does not usually stick around to troubleshoot it. They just leave, and there is rarely a second chance to make a first impression with someone evaluating a new tool. Removing that blocker means more people can actually get through onboarding and start using the product, which is the whole reason a trial exists.

Both fixes together reflect a broader point about billing: the numbers and states shown to you need to match what is actually happening with your payment method, in both directions. A cancellation that does not fully cancel and an onboarding error that blocks new users are different symptoms of the same kind of problem, keeping billing state accurate and consistent.

This kind of consistency is also what makes a trial genuinely low-risk instead of low-risk in name only. A trial you can start and, if it does not work out, cleanly walk away from without a lingering charge is the version of a trial that actually earns trust, which matters as much for people considering FirstSales for the first time as it does for anyone who has already been through the flow.

Billing correctness issues like this one tend to be treated as a top priority precisely because they touch something users cannot verify easily on their own in the moment. You cancel a trial, see confirmation on screen, and reasonably assume that is the end of it. Discovering weeks later that a charge went through anyway is a far worse experience than encountering a clear error message during setup, because by then the trust has already been broken rather than just delayed. Closing this gap at the source, rather than relying on customers to catch and report a stray charge after the fact, is the more durable fix.

Availability

This fix applies to all trial cancellations and new signups going forward.