Charge for registration
Updated October 8, 2026
Require a one-time payment before a visitor is registered.
What it’s for
A paid page turns payment into the last gate before sign-up: nothing is created in Livestorm and no registrant is recorded until Stripe confirms the charge. Useful for paid masterclasses, workshops and training sessions.
The money goes to your OWN Stripe account (direct charges): you are the merchant of record, you own receipts, refunds and disputes, and Livestorm takes no cut.
Paid registration needs a connected Stripe account. Open Settings → Integrations and check that the Stripe row reads “Connected”.
Then open your page in the builder, on step 4 · Settings. The Payment group sits below the access rules.
Turn on “Paid registration”. Until a Stripe account is connected and able to take card payments, the card stays greyed out with a link to Integrations.
Enter the price and its currency, then optionally a line-item label. It is what buyers see on the Stripe checkout and receipt. Leave it empty to fall back to the event title.
A €49 ticket labelled “Masterclass ticket”, ready to publish. To give some visitors a lower price, click “Add code” under the price. Enter the code, then a percentage or a fixed amount off: the window shows what visitors will pay. A use limit and start and end dates are optional.
A saved code works at once, without publishing again. The list shows how many times each code was used and whether it is active, with a switch to turn it off, and a menu to edit it, share a link that applies it, or delete it.
Good to know
- The minimum price is 0.50 in the selected currency (EUR, USD or GBP).
- The price is snapshotted by the server when a visitor submits, so it cannot be tampered with from the browser, and changing it later never re-prices a sign-up already in progress.
- Someone who is already registered is not charged again: the form recognizes their email and skips checkout.
- On a multi-session page, one payment registers every session the visitor picked.
- Visitors enter a promo code on the page before paying, and the button shows the new price. A shared link opens the page with its code already applied. Capitals do not matter, and a code works on its own page only.
- Stripe charges the reduced price. With a 100% code, the visitor registers without paying.
- A code cannot leave less than Stripe’s minimum charge (0.50 in EUR or USD, 0.30 in GBP) unless it takes 100% off. If you lower the price later, visitors with that code pay the minimum.
- A fixed amount off is in the page’s currency. If you change the currency, the code stops applying until you edit it and enter the amount again.
- A visitor on the Stripe checkout holds one use of the code for up to an hour, and gives it back by leaving without paying. When a code has no uses left, the next visitor is told before paying. A payment you refund in full in Stripe gives its use back too, and the person stays registered.
- Once someone has used a code, you can turn it off but not delete it. Turning a code off or deleting it does not affect a visitor already on the Stripe checkout: they pay the price they were shown.
- The Registrants tab shows what each person paid and the code they used, in the Paid column. The export adds Amount paid and Promo code.
- Promo codes apply on the page itself. In a hub’s registration window, visitors pay the full price.
- Refunds and disputes happen in your own Stripe dashboard, not in Livestorm.
- If a payment succeeds but the event platform then refuses the registration for a cause on its side (a broken connection, an outage), the visitor is kept in the Failed view of the Registrants tab with a “Paid” tag, and retried. See “Recover registrations the event platform refused”.
- A charged visitor whose registration cannot be completed at all is listed at the top of the Registrants tab (its Approved view), under “paid but not registered”, with “Refund in Stripe”.
- Disconnecting Stripe stops paid pages from taking payments until you reconnect.
Related articles
- Control access and privacyPassword-protect the page, set its visibility, redirect after registration, and cap sign-ups or close them at a set date.
- Create and revoke API keysIssue workspace keys to call the pages API from your own code. Revoke them when you no longer need them.
- Set how long registrant data is keptChoose a retention window for the personal data collected through your pages, or have your pages keep none at all.
Still need help?
Ask AI for a docs-grounded answer, or talk to our team.
Was this article helpful?