Google Forms cannot take payments — here's what does work
No. Google Forms has no payment question type and no built-in checkout, and paying for Workspace does not add one. Every method that looks like it works is a workaround that moves the money somewhere other than the form — an add-on, an external checkout link, or a QR code and good faith. All three are usable, and two of them are free.
The short answer
There is no payment field in Google Forms, on the free version or on paid Workspace. You can attach a payment to the process, but the transaction always happens outside the form, which means the response and the payment are two separate records you match up by hand afterwards.
The three workarounds, in the order most people should try them
Pick based on how much the amount varies and how much reconciliation you are willing to do. If your price is fixed and your volume is low, the free option is genuinely fine.
1. A payment link in the confirmation message (free, five minutes)
Create a Stripe Payment Link or a PayPal button, then paste the URL into the form's confirmation message and into the final section. The respondent submits the form, sees the message, and clicks through to pay. Nothing to install, no add-on subscription, and you keep your processor's normal fees. The catch is that clicking is optional — the form counts as complete whether or not they pay.
2. A Google Workspace Marketplace add-on
Several Marketplace add-ons bolt a payment step onto Forms, usually by connecting a Stripe account and emailing the respondent a payment request when the form is submitted. It automates the chase. Two things to check before you install: the add-on almost always carries its own monthly subscription on top of processor fees, and it asks for permission to read your form responses. Read the requested scopes, because you are handing a third party your submission data.
3. A QR code or bank details, reconciled manually
For a school fundraiser, a club subscription, or a bake sale, putting a payment QR code or bank details in the last section and matching payments to responses once a week is not embarrassing — it is often the fastest thing that works. It stops scaling the moment you have more than a couple of dozen orders or more than one price.
What the workaround actually costs you
The real expense is not money, it is reconciliation. After a week you have a Google Sheet that says somebody ordered and a Stripe dashboard that says somebody paid, joined only by whatever name or email address the person typed on each side — usually not identically. Every refund, cancellation, and "did this one go through?" question turns into a manual lookup across two systems.
Drop-off is the second cost. Submitting a form and paying for something become two decisions instead of one, with a page load in between. You will collect orders that never turn into payments, and you will not be able to tell the difference between a person who intended to pay later and a person who changed their mind.
Variable amounts are where it breaks completely. A payment link is a fixed price. If the amount depends on what the person picked — three items instead of one, a large instead of a small, an add-on ticket — you need either a separate link for every possible combination or a manual invoice per order. There is nothing inside Google Forms that can add up selections and produce a total, because Forms has no calculation engine.
And nothing can make payment a condition of submitting. Forms submits when the respondent presses submit. Whatever happens after that is out of the form's hands.
If you're staying on Google Forms, set it up this way
This is the version of the link workaround that causes the fewest problems later. It takes about ten minutes.
Capture everything before the handoff
Put every question — items, quantity, delivery details, contact — before the payment step, and turn on "Collect email addresses" in settings. If the person never clicks through to pay, you still have a complete order and a way to chase it. Never rely on the payment page to collect information you need.
Use one link per price point, not one link plus instructions
Resist the temptation to use a single open-amount link with a note asking the buyer to type the right figure. Create a separate Payment Link per price, name each one after the option it belongs to, and branch to the matching section so each respondent sees only their link. The name comes through on the processor side, which is how you will tell orders apart.
Give yourself a matching key
Show a short reference in the confirmation message — even something as basic as "quote your email address in the payment note" — and ask for it on the payment side. Stripe Payment Links and PayPal both let you collect a note or a custom field. Matching on a key you chose is far less painful than matching on names a month later.
Ordering and paying in one step
This is the difference between a payment link bolted onto a form and a payment question inside one.
| What you need | Google Forms plus a link | Zunoform payment field |
|---|---|---|
| Where the money moves | On another site, after the form is submitted | Inside the form, before it is submitted |
| Amount that depends on the answers | One link per price combination, or a manual invoice | Price by answer — a price mapped to each option of an earlier question |
| Proof of payment on the response | Matched by hand across two systems | Stored with the response itself |
| Protection against a tampered amount | Not applicable — the link is whatever you set | Recomputed server-side at checkout and re-verified at submission |
| Who takes a cut | Your processor, plus the add-on's subscription if you use one | Your own Stripe or PayPal keys, no platform cut |
Zunoform payment fields are on the Pro plan at $14.99/month. Building and previewing one is free; publishing it needs Pro.
Forms that need to charge
Each of these is a form where splitting the order from the payment hurts most.
A complete order flow: product picker, shipping, and card payment priced by selection.
Pick tickets, pay in the same form — prices add up automatically.
Giving tiers, an optional dedication, and secure card payment.
Menu with live per-item pricing, delivery or pickup, and card payment.
Questions people ask
Is there a free way to accept payments through a Google Form?
Yes, if you count an outbound link. A Stripe Payment Link or PayPal button pasted into the confirmation message costs nothing beyond your processor's normal fees. It is not a payment field — the respondent pays on another page, after submitting — but it works and it is free.
Do Google Forms payment add-ons cost money?
Usually yes. Most Marketplace add-ons that add a payment step charge their own monthly subscription on top of your processor's fees. They also request permission to read your form responses, so check the requested scopes before installing one.
Can Google Forms calculate a total based on what someone picked?
No. Forms has no calculation or arithmetic feature, so it cannot add up selected options into an amount. You would export to Sheets and calculate there after the fact, which does not help you charge the right amount at the time of ordering.
Does paid Google Workspace add payment collection to Forms?
No. Paying for Workspace adds essentially nothing that is specific to Forms. Payments, branding removal, and custom domains are all absent on every tier, verified against Google's product and support documentation on 2026-08-13.
Can I require payment before the form is submitted?
Not with Google Forms. Submission and payment are separate events and the form has no way to check whether the second one happened. A form builder with a native payment question can hold the submission until the charge succeeds.
Keep reading
Better forms.
Better data.
Build your first form in under 60 seconds. Free forever for personal use, no credit card required.