A payment form builder that charges the right amount every time
A payment form collects answers and a card in one submission, so an order, a booking, or a donation is finished in a single step. Google Forms cannot do this natively at all. Where the others differ is what tier it sits on, whose payment processor it runs through, and whether anyone takes a cut on top of the processor's fee.
The short version
Every payment form runs on a real payment processor — usually Stripe or PayPal — so the first question is whose account it settles into and who takes a percentage. On Zunoform you connect your own Stripe or PayPal keys and the money goes to you with no platform cut; payments are a Pro feature at $14.99/mo. Tally includes Stripe payments free, which is the most generous offer in the category. Typeform puts payments on a $91/mo tier. Google Forms has no native payment capability on any plan.
How a payment form actually works
Three things have to happen in order. The form works out what to charge, the respondent authorises that amount with a card or a PayPal account, and the submission is recorded against the payment. If any of the three is loose, you get the classic failure modes: orders with no payment attached, payments with no order attached, or an amount that doesn't match what the form displayed.
The amount is where most of the risk sits. If the price is calculated in the browser and sent to the server as a number, then the number is a suggestion — anyone who can open developer tools can change it. The correct design computes the price on the server from the form definition, never trusting what the client claims. On Zunoform, when an amount is driven per-option by an earlier answer, the total is recomputed server-side at checkout and then re-verified again at submission, so the price is decided by your form, not by the browser.
The second question is fees. A form builder that processes payments through its own merchant account can take a percentage on top of Stripe's — sometimes several percent, which compounds badly at volume. Connecting your own processor keys avoids that entirely: the processor charges its standard rate and the form builder charges its subscription, and nothing scales with your revenue.
Where payments sit across the tools
Verified August 2026 from published pricing. This is the most expensively gated feature in the category.
| Question | Elsewhere | Zunoform |
|---|---|---|
| What does taking payments cost? | Typeform: a $91/mo tier. Tally: free with Stripe. Jotform: available on paid plans. Google Forms: not possible natively | Pro, $14.99/mo |
| Who takes a percentage? | Depends on whether the tool uses its own merchant account or yours | Nobody but your processor — no platform cut |
| Whose Stripe account does it settle into? | Varies by tool; check before you launch | Yours — your own Stripe or PayPal keys |
| Can the price depend on an earlier answer? | Frequently fixed-price only, or a paid add-on | Yes — price by answer, per option |
| Is the amount safe from tampering? | Browser-side totals are common and are editable by the respondent | Recomputed server-side at checkout and re-verified at submission |
| Can the same form book a time and take a deposit? | Typically two tools and two links; Calendly puts payments on Standard $10/seat/mo and screening questions on Teams $16/seat/mo | One form — scheduler question plus payment question |
Four payment form patterns
Nearly every payment form is one of these. Identifying which one you're building saves a lot of rework.
Fixed price
One product, one amount, no variation — a workshop seat, a single-tier membership, a flat consultation fee. The simplest thing that works, and where you should start. If you find yourself building a fixed-price form per product variant, that's the signal to move to price-by-answer instead.
Price by answer
The amount is driven by an earlier question: ticket type, quantity tier, service level, add-ons. One form covers the whole catalogue instead of one form per SKU. The essential detail is that the total is derived on the server from your definition, so a respondent selecting the expensive option and editing the page still gets charged the expensive option.
Pay what you want
Donations, pay-what-you-can pricing, tips. The respondent enters the amount. Design-wise, suggested amounts massively outperform an empty box — most people take one of the presented options, and the presence of a higher tier raises the average even when few choose it. Keep an other field for the people who want to give more than your top suggestion.
Deposit plus booking
Take a slot and a partial payment in the same submission — consultations, classes, service appointments. This is the pattern that usually spans two tools: a scheduler for the time and a payment link for the money, with a drop-off between them. Here the scheduler is a native question type, so the booking and the deposit are one form. Availability comes from real free/busy on the connected Google or Outlook calendar, and double-booking is prevented by a unique database constraint rather than by hoping.
Before you take the first real payment
Run through this with a live card and a small amount. Every item here has cost somebody a refund.
- Test with a real transaction, not just the processor's test mode — key mix-ups only show up live
- Confirm the amount charged matches the amount displayed, including for the branch you built last
- Check the currency is what you meant, on every option
- Decide what happens when payment fails midway — does the response still record?
- Know where refunds happen (your processor's dashboard) and who on your team can issue one
- Check whether you need to collect tax or VAT, and whether the amount you show is inclusive
- Put a real description on the charge so it's recognisable on a card statement and doesn't get disputed
- Confirm the receipt path — respondents who don't get one email you instead
- Never collect raw card details in a text field; the payment question exists so the card never touches your form data
Payment form templates
Publishing a payment question requires a paid plan; building and previewing one doesn't.
A complete order flow: product picker, shipping, and card payment priced by selection.
Giving tiers, an optional dedication, and secure card payment.
Pick tickets, pay in the same form — prices add up automatically.
Bulk pallet ordering for retail buyers with delivery details and payment.
Questions people ask
Can Google Forms accept payments?
No, not natively, on any plan. The usual workarounds are linking out to a separate payment page after submission, or wiring an add-on — both of which split the transaction across two steps and lose people in between. If the form has to take money, Google Forms is the wrong tool.
Does Zunoform take a cut of payments?
No. Payments run through your own Stripe or PayPal keys, so funds settle into your account and your processor charges its standard rate. Zunoform charges the Pro subscription at $14.99/mo and takes no percentage of what you collect.
What's the cheapest way to take payments through a form?
As of August 2026, Tally — Stripe payments are included on its free plan with unlimited responses, which nothing else matches. Zunoform is $14.99/mo on Pro with no platform cut and adds price-by-answer plus a native scheduler. Typeform's payment tier is $91/mo. Pick based on whether you need what the paid tiers add.
Can the price change depending on what someone selects?
Yes. An amount can be driven per option by an earlier question, so one form handles a whole range of prices. The total is recomputed on the server at checkout and re-verified at submission, so what gets charged always comes from your form definition rather than from the browser.
Can I take a deposit and book an appointment in the same form?
Yes — the scheduler and payment questions can sit in the same form, so someone picks a slot and pays in one submission. Availability is drawn from real free/busy on your connected Google or Outlook calendar, and a unique database constraint makes double-booking impossible rather than unlikely.
Keep reading
Better forms.
Better data.
Build your first form in under 60 seconds. Free forever for personal use, no credit card required.