Build a form that takes payments

Taking payments is on the free plan here. Charging someone is not a premium feature. For an order form it is the whole point of the form.

Add a Payment question, connect your Stripe account, and the card fields appear on the form itself. No redirect to a separate checkout, no second tool, no plugin.

The money goes straight to you

You connect your own Stripe account, and charges land in it directly. Payouts follow your normal Stripe schedule, refunds happen in your Stripe dashboard, and disputes are between you and Stripe exactly as they would be otherwise.

Nextforms takes no commission. You pay Stripe’s standard processing fees and nothing else: no percentage, no per-submission fee, on any plan. It is worth checking that against anything else you are considering: a platform fee on top of Stripe’s own is easy to miss on a pricing page and compounds quietly on every order.

A fixed price, or a total the form works out

A fixed amount covers the simple cases: a ticket, a deposit, a registration fee.

More often the amount depends on what someone chose: quantity, options, a size, a delivery method. Nextforms calculates the total from the answers and charges that. The respondent sees the figure update as they fill the form, so nobody is surprised at the card field.

The price is worked out on the server, from the answers actually submitted. The browser never decides what to charge. That distinction matters: a total computed in the page can be edited by anyone willing to open developer tools.

One-off or recurring

Charge once, or set the Payment question to a subscription and bill monthly or yearly. A membership signup, a recurring donation, and a one-time order all use the same question type.

What happens after the payment

The submission is a submission like any other, so the workflow engine picks it up: email the customer a receipt from your own address, push the order to Google Sheets, post it to Slack, or send it anywhere else with a webhook. All free, all without a separate automation tool in the middle.

Payment status is stored with the response, so a paid submission is distinguishable from an abandoned one when you read your results or export to XLSX.

Good for

Order forms, event tickets, deposits and booking fees, registration fees, donations, membership signups, and any request form where the work is only worth starting once someone has paid.