Last updated: October 15, 2026
To create a payment form, separate the free intake draft from the paid configuration that collects money. FORMLOVA card payments require Premium and Stripe Connect. Account onboarding, paid mode and price are configured in the dashboard. Common MCP does not return paid purchase URLs, QR codes or embeds; one chat request does not start selling tickets.
Choose the right approach
| Approach | Suitable work | Responsibility |
|---|---|---|
| Custom payment implementation | A bespoke sales/booking system | Development, maintenance and payment exceptions |
| Event platform | Combined discovery and ticket sales | Publication, monthly/fixed/per-transaction fees |
| Registration form plus payment | Your own LP/social audience | Acquisition and reconciling intake/payment/communication |
FORMLOVA connects intake with card payment. It is not a complete replacement for product inventory, arbitrary carts, assigned seating or fulfilment systems.
Draft the intake and decision points before payment
This is a proposed trial, not an operation or result measured for this rewrite. Use a private test draft first.
We plan a paid seminar. First create a normal private draft with name, email, participation goal and necessary consent. Ask for event time, people per response, planned price and cancellation terms; list unknowns. Do not set price, enable paid mode, onboard an account, publish or send. Show preview and the pre/post-payment checklist.
Before proceeding, check:
- Are received, paid and confirmed separated?
- Are response count, participants and capacity distinct?
- Can mobile/desktop check fields, consent and completion copy, with dashboard payment setup clearly separate?
Design the intake free before collecting fees
Free supports a normal draft and preview. Card payments require Premium; custom confirmation mail requires Standard or above. Free registration does not enable payment.
Register, verify your email, connect a supported AI client, and paste the proposed request above. Check the saved draft before publishing. AI-client account and usage requirements apply separately.
This existing conceptual diagram shows the draft-checking stage; it is not a screenshot or measurement of this article’s proposed test.
Plans and fees
| Stage | Requirement |
|---|---|
| Normal creation/collection/search/status/CSV and Excel | Free |
| Custom replies/reminders | Standard or above, from JPY 1,480/month |
| Paid card form | Premium, JPY 3,980/month plus transaction fees |
These are current tax-included new-contract prices; check any grandfathered terms separately.
The transaction rate is 4.6%, based on 3.6% Stripe processing plus 1.0% platform fee, with rounding and a minimum JPY 1 fee. There is no separate fixed per-transaction FORMLOVA fee, but Premium subscription is additional. Stripe Japan pricing lists 3.6% per successful card charge, with separate conditions such as currency conversion. Do not assume every possible cost is always 4.6% alone.
Do not equate two ticket sales with recovering every event cost. Include transaction charges, delivery/venue costs and cancellation/refund conditions in your own event calculation.
Configure paid mode in the dashboard
- Review the normal private draft, completion text and consent.
- Confirm Premium eligibility.
- Open paid events/Stripe Connect from the dashboard plan area and complete onboarding.
- Configure and verify paid mode, price and connection status for the target form in the dashboard.
- Verify the purchase path using supported Web publishing controls.
- If conducting a payment test, reconcile intake, payment result, confirmation, receipt and refund handling separately.
Public MCP creation/update does not accept paid flags or prices. Managing/previewing an existing paid form is separate from a purchase link. Web payments remain available, while common MCP suppresses purchase URLs, QR codes, iframe and related indirect paths.
Separate intake, payment and handling state
Dashboard payment labels are unpaid, paid and expired. Stored registration is not payment. Cancellation/refund decisions and actual execution need separate records; changing response status does not charge or refund a card.
Response handling uses new / in_progress / resolved / spam. Put confirmed attendance or refund waiting in retained tags/notes or an external ledger. Multiple people per response means response count is not seat count.
Unpaid responses are logically removed after the specified 24-hour expiry. This does not guarantee arbitrary inventory or multi-person seat-return logic. Paid forms accept cards only, not asynchronous bank-transfer or convenience-store methods.
Confirmation, receipts and cancellation
We have received your registration record.
Participation confirmation depends on verification of payment.
Please check the event time, joining instructions, preparation and contact route.
For changes, cancellation or refunds, follow the stated policy and contact route.
Adapt this example to the real process. Separate unpaid from paid messages and verify who issues receipts and how they are obtained. Custom replies require Standard or above; Premium still has outgoing-mail and unsubscribe conditions.
Free owner response notification is a six-hour digest outside outgoing-mail quota. It is distinct from participant email or payment notifications.
Pre-publish checks and first step
Check amount/currency, transaction/fixed/monthly costs, card-only checkout, account readiness, capacity/party size, unpaid/expired records, event instructions, receipts, cancellations/refunds and storage. Preview submission does not test a real payment. Basic CSV/Excel contains form fields and submission time, not guaranteed payment/handling-status columns.
Start with the normal draft above to make receipt versus confirmation clear. Move to dashboard payment setup and Premium only when ready to collect fees.
Related Guides and References
- Event Registration Form Guide
- Order Form Guide
- Form Auto-Reply Email Examples
- How to Build and Publish a Webinar Registration Form in FORMLOVA
- Registration Form Guide
- Webinar Registration Form Guide
- Form Services Comparison Guide
- How to Create Forms -- Use-Case Templates and Post-Publish Operations
Disclosure and Verification
This guide is written by FORMLOVA's developer. Prices, MCP/dashboard boundaries, payment states and card-only support were checked against current specification/code on October 15, 2026. Stripe's standard rate was rechecked on its official page. The proposed request is not a new payment or send result.
