Last updated: June 14, 2026
If you are searching for how to create a payment form, you are not really asking how to arrange input fields.
You want to collect participation fees. You want to receive ticket payments. But building a payment system from scratch is hard, dedicated event platforms feel expensive, and ideally you would handle the whole thing as an extension of a registration form, without building a website.
That is the real question behind a payment form search.
Paid seminars, paid workshops, small-group classes, community membership fees, pre-orders for physical goods -- they all share one trait: you receive money at the same moment someone signs up. A free form is done once it collects a name and an email address. The moment money is involved, you also have to think about collecting the fee, confirming that payment went through, receipts, and how cancellations are handled.
This guide defines what a payment form is, compares building payment yourself, using an event platform, and adding payment to a form. Then it walks through how to build a form in FORMLOVA that collects paid-event fees without a website -- the steps, the fees, the required plan, and how to manage payment status before and after the transaction.
The field design and capacity work for the registration itself live in the Event Registration Form Guide. This article focuses on the part where you add payment on top of that.
Quick Answer: Choose a Payment Form by Who Owns the Audience
There are three broad ways to build a payment form.
Which one is right is decided not by feature count, but by where the center of gravity for your audience and your money sits.
| Method | Best when | Watch out for |
|---|---|---|
| Build payment yourself (implement Stripe directly) | You want a custom booking or sales system on your own site | Requires development and maintenance. Overkill for a single form |
| Event platform (ticketing service) | You want a public event listing or marketplace to bring you an audience | Fees tend to run higher. Hard to embed in your own context |
| Add payment to a form | You take signups from your own LP or social posts and want signup and payment in one flow | Less audience reach than a platform. Assumes you promote it yourself |
If you need a full-featured sales system on your own site, implement payment directly. That assumes development, so it is not the method to choose for a single form.
If, instead, you want to rely on an event platform's audience reach itself, a dedicated ticketing service fits. The fees tend to run a little higher, though, and it can be hard to embed it in your own email copy and brand context.
And for people who can already promote through their own landing page, social accounts, or email, the third option -- adding payment to a form -- is the lightest choice. Signup and payment complete in a single form, and response management continues exactly as before.
FORMLOVA is the third option.
You take signups the same way you always do, and you add fee collection only when you are running a paid event. There is no need to set up a separate site.
What Makes a Payment Form Different From a Regular Registration Form
A free registration form and a payment form look similar.
Both collect fields like name, email address, which event you are attending, and an agreement checkbox.
The difference is whether money moves after submission.
With a free registration form, the registration is complete the instant the submit button is pressed. After that you send a confirmation email and guide the person to the event day. That is all.
With a payment form, one extra step comes after submission. The attendee enters their card details, and their place is only confirmed once payment is complete. On the operations side, you pick up new work that a free form never had: confirming that payment cleared, handling receipts, processing refunds for cancellations, and dealing with people whose payment never completed.
In other words, a payment form requires you to manage "a signup arrived" and "money was received" as two separate things.
Blur the two, and you end up sending a confirmed-attendance email to someone who has not paid yet, or letting an unpaid provisional signup occupy a seat when the event is already full.
The most important thing in payment-form design is not adding more fields.
It is holding the state separately before and after payment.
A FORMLOVA Payment Form Is "Registration Form + Stripe Connect"
When you collect paid-event fees in FORMLOVA, it uses a mechanism called Stripe Connect Express.
Rather than FORMLOVA holding the participation fees, the amount the attendee pays goes into the organizer's own payout account. FORMLOVA only receives the platform fee on that transaction.
Put into words, the flow is this:
An attendee signs up through the form
The attendee pays the fee by card
The amount paid goes into the organizer's payout account
FORMLOVA receives the platform fee
Payment is confirmed and the place is secured
All the organizer has to do is register a payout account once at the start. The Stripe Connect account registration is a one-time step; you do not have to set it up again every time you create a paid form.
And it is not a design that asks everyone for account registration up front. You use free forms as usual, and the moment you say you want to run a paid event, the guidance for registering a payout account appears in chat. So you can start using FORMLOVA for free and turn on payment only when you actually need it.
The non-payment part of the form is exactly the same as a regular registration form. Collecting names and email addresses, sending a confirmation email, and managing attendees in the response list -- none of that changes. It helps to think of payment as a single layer that sits on top.
How Much Is the Fee -- The 4.6% Breakdown
When choosing a payment form, the fee is the most important deciding factor.
FORMLOVA's paid-event fee is 4.6% of the transaction amount.
That 4.6% has a breakdown.
| Component | Rate | What it covers |
|---|---|---|
| Stripe base cost | 3.6% | Stripe's standard Japan rate, passed through as-is |
| FORMLOVA platform fee | 1.0% | Platform operating cost |
| Total | 4.6% | Deducted from the attendee's payment amount |
The reassuring thing to know here is that the 3.6% is not FORMLOVA's cut -- it is the actual cost charged by Stripe (the payment processor). As long as you accept credit card payments, this kind of processing fee occurs with any service. The only amount FORMLOVA adds on top is 1.0%.
This 4.6% level is on par with event ticketing platforms. Typically, a representative event platform charges a few percent of the sale plus a fixed per-ticket cost of roughly several tens to about a hundred yen. FORMLOVA is a flat 4.6% with no fixed cost, so the burden is especially easy to predict on lower-priced tickets.
For the record, the fee is calculated per transaction, and because of rounding, at least 1 yen is always deducted as the fee. Just keep in mind that the fee never drops to exactly 0 yen even on a small ticket -- that is enough.
Because exact fee rates and conditions can change, the surest way to confirm a final amount is to check FORMLOVA's pricing page and Stripe's official information.
Can You Build a Payment Form for Free -- How the Plans Work
People searching for a free payment form care most about whether they can start without spending money.
Let me draw the line precisely.
In FORMLOVA, form creation, response collection, response search, status management, and CSV/Excel export are available on the Free plan (0 JPY/month). In other words, you can build registration forms for free events and free seminars without spending anything.
On the other hand, the paid-event feature that receives participation fees (Stripe Connect) is a Premium plan (980 JPY/month) feature.
To organize it:
| What you want to do | Plan needed |
|---|---|
| Build a registration form for a free event | Free (0 JPY/month) |
| Set up auto-reply emails and reminders | Standard (480 JPY/month) or higher |
| Build a paid event that receives fees | Premium (980 JPY/month) |
So no, it is not the case that a payment form is completely free to build. The part that collects fees is a Premium feature. That said, the 980 JPY/month subscription is usually a level that the revenue from a single event covers comfortably.
The practical way to start is this: build the registration form for free first and confirm the signup flow. When the time comes to actually run a paid event, upgrade to Premium and turn on payment. You can design and verify the form for free before you ever start paying.
You can see the full difference between Free, Standard, and Premium on the pricing page.
Manage Payment Status Separately Before and After Payment
The place where mistakes happen most on a payment form is payment-status management.
To repeat: "a signup arrived" and "money was received" are two different things.
In FORMLOVA, payment status is tied to the responses on a paid form. In the response list, responses with incomplete payment are visually distinguished with a light gray background, so you can tell paid attendees apart at a glance.
In operations, it is easier to keep things organized if you separate states like these:
Registering (not paid yet)
Payment complete
Payment incomplete
Cancelled
Refund under review
Drawing this distinction reduces the risk of mistakenly telling an unpaid person "your place is confirmed." It also lets you build the day-of check-in list from paid attendees only.
There is also a mechanism so that a provisional signup left unpaid does not occupy a seat in your capacity indefinitely. In FORMLOVA, a provisional signup that passes a set time (24 hours) without completing payment is automatically treated as expired. This prevents the "added to cart but never paid" problem of someone holding a seat forever.
With a payment form, it only becomes a real operation once you include this kind of payment-status management. The point that you are not done the moment you publish the form matters even more than it does for a free form.
For capacity and waitlist design itself, the rules are the same whether or not payment is involved. See the capacity section of the Event Registration Form Guide for details.
How to Build a Payment Form in FORMLOVA
In FORMLOVA, you can draft a payment form from chat using an MCP-compatible client such as ChatGPT or Claude. You do not need to learn a dedicated admin screen for the payment setup either -- you can do it in conversation.
Your first request does not need to be long. For example, ask like this:
Create a registration form for a paid seminar with a 3,000 yen fee.
Fields: full name, email, company, receipt name,
agreement to the cancellation policy, and consent to how personal data is used.
I want to receive the fee by credit card.
If you have not registered a payout account yet, the guidance for account registration (Stripe Connect) appears here. Follow it once, and from then on your paid forms can receive fees directly.
If your tickets come in several types, add this:
Add ticket types.
General 5,000 yen, early bird 3,500 yen, student 2,000 yen.
To set up the post-payment messaging too, ask for the confirmation email:
When payment is complete, send a confirmation email that includes
the ticket details, how receipts are handled, the cancellation deadline,
and a contact address.
Once the draft is ready, do not publish right away. Confirm the following:
- The fee amount and ticket types are correct.
- The receipt name and the cancellation-policy agreement are included.
- The post-payment confirmation email states the receipt and the cancellation deadline.
- You can view the state separately before and after payment.
- The purpose of personal-data use is shown inside the form.
- You confirmed the email and response list with a test submission or a small test payment.
The trick here is not to treat the payment setup as too special. In FORMLOVA, fee collection is set up conversationally in the same flow as a normal form field. The hard part is not building a payment system -- it is deciding what to communicate before and after payment.
Publishing a Payment Form Without a Website
For people searching for a payment form without a website, what matters is how it looks after publishing.
Every form you build in FORMLOVA gets a public URL. Just share that URL on social media, by email, or in a message, and the person who receives it can complete everything from signup to payment on that page. There is no need to prepare a separate company site or landing page.
In short, it fits people like these:
You want to run a paid class or event as an individual
You do not have the time or budget to build a landing page
You want to promote directly to your social followers or newsletter readers
You want to finish signup and payment with a single link
For example, if you want to sell tickets as an individual, you can start accepting signups just by pasting the form URL into your profile or a post, without setting up a dedicated event site. The fees you receive go into the organizer's own payout account, and FORMLOVA takes only its fee.
On the flip side, the convenience of not having a site means it assumes you handle promotion yourself. It is not a mechanism where new attendees flow in from the service's own listing pages, the way an event platform works. The lighter the setup, the more it favors people who already have a way to promote.
If you want to rely on audience reach itself, a dedicated ticketing platform can be the better fit. This trade-off is the same one covered at the start of this article.
What to Watch For Around Confirmation Emails and Receipts
The confirmation email for a paid event should be written more carefully than for a free one.
Right after paying, attendees feel more anxious than they do for a free signup. Did the payment really go through? Will I get a receipt? If something comes up, will I be refunded? When the confirmation email answers these questions in advance, inquiries go down.
Include the following in the payment-complete confirmation email:
That payment is complete
The ticket details (type, amount)
How receipts are handled (issuing method, recipient name)
The cancellation deadline and refund conditions
The day-of details (date, venue or URL)
A contact address
The biggest difference from a free event here is how cancellations and refunds are handled. For a free event, "no problem if you do not show up" is enough, but for a paid one, if you do not state "until when refunds are available," individual handling piles up later. Put the cancellation policy in the form's agreement field and write the deadline in the confirmation email too, so both sides are on the same page.
In FORMLOVA, the auto-reply email copy can be customized on Standard and above. Because paid events are a Premium feature, customizing the confirmation email is naturally included. For the thinking behind auto-reply emails themselves, the Form Auto-Reply Email Examples are also a useful reference.
Pre-Publish Checklist
Before publishing a payment form, confirm the following:
[ ] The fee amount and ticket types are correct
[ ] The Stripe Connect payout account registration is complete
[ ] There is a field asking for the receipt name (if needed)
[ ] There is an agreement field for the cancellation policy
[ ] The purpose of personal-data use is clear before submission
[ ] The post-payment confirmation email includes the receipt and cancellation deadline
[ ] You can view the state before and after payment separately (registering / payment complete / cancelled)
[ ] You understand how an unpaid, abandoned provisional signup is handled
[ ] You can build the day-of check-in list from paid attendees only
[ ] You confirmed the payment, email, and response-list flow with a small test payment
[ ] Signup through payment proceeds smoothly on mobile
The most important one is the second to last: the test payment.
A payment form needs you to go one step further than a free form's test submission and confirm the actual payment flow. Buy one low-priced ticket yourself and watch the whole path: whether the payment-complete email arrives, whether the response list shows it as paid, and whether the receipt handling works as intended. That gives you peace of mind.
And the mobile check is essential too. Paid-event promotion is often opened on a phone from social media or email, and whether someone can move smoothly all the way to the card-entry screen on a phone directly affects your completion rate.
Common Mistakes
The first is treating signup and payment as the same thing.
If you think "the form was submitted = the place is confirmed," you will send a confirmation email to someone who has not paid yet. On a payment form, hold payment-complete as a separate state and base your messaging on it.
The second is publishing without deciding cancellation and refund conditions.
With a paid event, cancellation questions will always come. If you do not write the deadline and refund conditions into the form's agreement field and the confirmation email, you burn out making case-by-case judgments every time.
The third is setting the price without accounting for the fee.
The fee (4.6%) is deducted from the amount the attendee pays. If you do not design the price around the amount left in your hand, you receive less than you expected.
The fourth is leaving unpaid provisional signups alone.
If people who drop off mid-payment keep occupying seats, capacity management breaks down. In FORMLOVA they automatically expire after a set time, but read capacity with that behavior in mind.
The fifth is going live without a test payment.
If you are satisfied with only a free form's test submission, you will discover payment problems in production. Run an actual payment once, even for a small amount.
Get Started With a Payment Form in FORMLOVA
A payment form is often assumed to be the hard work of building a payment system from scratch.
But for individuals and small businesses that already have a way to promote, it is enough to add a single fee-collection layer to a registration form. Without building a site, just by sharing the form URL, everything from signup to payment completes.
In FORMLOVA, you build a registration form for free as usual, and turn on payment (Stripe Connect) from chat the moment you say you want to run a paid event. The fee is 4.6% (of which 3.6% is Stripe's actual processing cost, and only 1.0% is the add-on), with no fixed costs. Fees go into the organizer's own payout account. The paid-event feature is Premium (980 JPY/month).
Start by building the registration form for free. Once the signup flow is settled, going paid is a single line in chat.
The build-out for running the event itself -- field design, capacity, day-of check-in, and reminders -- lives in the Event Registration Form Guide. If you want to set up your whole webinar or seminar operation in order, start from How to Build and Publish a Webinar Registration Form in FORMLOVA to get a map from creation through post-publish operations.
FAQ
Can I build a payment form for free?
The registration form itself can be built on the Free plan (0 JPY/month), but the paid-event feature that receives fees is Premium (980 JPY/month). The practical approach is to build the form for free first and upgrade when you actually run a paid event.
How much is the fee?
It is 4.6% of the transaction amount. The breakdown is Stripe's actual processing cost of 3.6% (Japan's standard rate, passed through as-is) plus FORMLOVA's 1.0% add-on. There are no fixed costs. Confirm exact amounts on the pricing page and Stripe's official information.
Where do the fees I collect go?
The amount the attendee pays goes into the organizer's own payout account (Stripe Connect). Rather than FORMLOVA holding it, the mechanism only takes the fee. Account registration is a one-time step at the start.
Can I publish a payment form without a website?
Yes. Every form you build in FORMLOVA gets a public URL, so just sharing that link on social media or by email lets the recipient complete everything from signup to payment. No company site or landing page is needed. It does assume you handle promotion yourself, though.
Can individuals use it for ticket sales?
Yes. Even for an individual's class or event, you can collect fees by pasting the form URL into your profile or a post. There is no need to set up a dedicated event site. It is safest to state cancellation and refund conditions in the form's agreement field and the confirmation email.
What happens to people who have not completed payment?
In the response list they are distinguished as payment-incomplete with a light gray background, so you can tell them apart from paid attendees. A provisional signup that passes a set time (24 hours) without completing payment is automatically treated as expired and no longer occupies a seat in your capacity.
Summary -- Build a Payment Form by Separating Before and After Payment
A payment form is not finished by adding a payment button to your input fields.
How much is the fee? Is the price set with the fee accounted for? How do you confirm that payment is complete? How do you communicate receipt and cancellation conditions? How do you handle unpaid provisional signups?
Only once you have decided all of this does a payment form become a real operation.
And for people who already have a way to promote, adding a single fee-collection layer to a registration form is a far lighter choice than setting up a dedicated payment system or event site.
In FORMLOVA, you build a registration form for free and turn on payment from chat only when you run a paid event. The fee is 4.6%, with no fixed costs, and fees go into the organizer's account. No site is required -- accepting signups starts just by sharing the form URL.
Start by building the registration form for free. Going paid is just a single request when you are ready.
Related Articles
- Event Registration Form Guide
- How to Build and Publish a Webinar Registration Form in FORMLOVA
- Registration Form Guide
- Webinar Registration Form Guide
- Form Auto-Reply Email Examples
- Form Services Comparison Guide
Disclosure and Verification
This guide is a practical reference for organizers who want to collect participation fees for paid events or ticket sales through a form. I work on FORMLOVA. The fee rates, supported plans, and payment mechanism are based on FORMLOVA's specs and pricing page, confirmed as of June 14, 2026. Because fee rates and pricing can change, confirm final amounts on the pricing page and Stripe's official information. Make decisions involving payments, accounting, and legal matters according to your own situation.
