How to Collect Payments with Google Forms (2026)
How to Collect Payments with Google Forms (2026)
Can Google Forms Collect Payments?
No — Google Forms cannot collect payments by itself, because it was never built to process transactions. There is no payment question type, no native Stripe/PayPal/Square integration, no checkout step, and no calculation field to multiply quantity by price. Every “Google Forms payment” method is really a way of attaching payment beside the form, not inside it.
That framing matters, because it explains why all three approaches below feel a little bolted-on: you’re using Google Forms for what it’s good at — collecting names, choices, and quantities for free, with a link anyone can open — and handing the actual money to something built to handle money. This works well for small, occasional collection. It works less well the moment you need real order math or a seamless branded checkout. Let’s start with the one rule you can’t bend, then the three methods in order of effort.
⚠️ Never Put Card Numbers in a Google Form
The single hard rule of this entire topic: never collect a credit card number in a Google Forms text question. Google Forms is not PCI DSS compliant — the security standard that governs how card data must be handled — so a card number typed into a form lands in your response spreadsheet as plain text, unprotected and outside every safeguard the payment industry requires. It’s both against the rules and a real risk to you and the person paying.
The safe pattern, used by every legitimate method below, is simple: Google Forms collects only non-sensitive data (name, email, which item, how many), and a processor-hosted checkout page — Stripe, PayPal, or Square — takes the card details on its own secure, compliant infrastructure. You never touch card data, and neither does your spreadsheet.
Method 1 — Link to a Payment Page After Submit (Free)
The simplest free method is to send people to a payment page after they submit, by pasting a checkout link into the form’s confirmation message. You create a shareable checkout URL in your processor — Stripe Payment Links and PayPal both generate one with no code — and then point your form at it.
- In Stripe (or PayPal), create a payment link for the amount you’re collecting.
- In your Google Form, open Settings.
- Go to the Presentation section.
- Paste your payment link into the confirmation message shown after submitting (something like “Thanks! Complete your payment here: …”).
- Save, and test the flow once yourself end to end.
This is free beyond the processor’s own transaction fee, and it suits low-frequency, fixed-amount, trusted-audience situations — a club fee, a small fundraiser, a friend-group order. The honest costs: the form submits whether or not the person pays, so a submission is not proof of payment; you can’t verify who actually paid without cross-checking your Stripe/PayPal dashboard; reconciliation is manual; and the amount is fixed — the link charges one price, since the form can’t do order math. If you’re still building the form itself, our how to create a Google Form on iPhone guide covers that part first.
Method 2 — A Payment QR Code in the Form (In-Person)
For in-person situations, a payment QR code inside the form is often the fastest path. You add an image of a peer-to-peer payment code — PayPal, Venmo, Cash App, or a regional wallet — to the form or its confirmation screen, and people scan to pay from the same phone. It shines at a table, a stall, or an event where everyone’s already in the room and using the same wallet.
The trade-offs are the same as Method 1, only looser: the form still can’t tell who paid, there’s no automatic reconciliation, and the amount is whatever the code is set to. Treat it as a convenience for face-to-face collection, not a system of record. If you want to generate and place a scannable code on a form from your phone, our Google Forms QR code on iPhone guide covers making the code itself.
Method 3 — A Workspace Add-On (Closest to Real)
A Workspace add-on is the closest Google Forms gets to real integrated payment, because it connects an actual processor and ties payment to the response. Tools like Payable Forms and PayQ install from the Google Workspace Marketplace, connect to Stripe, PayPal, or Square, read the fields that determine the amount, and — crucially — write the paid/unpaid status back to your Google Sheet next to each response.
- Install a payment add-on (for example, Payable Forms) from the Google Workspace Marketplace.
- Open the add-on’s Configure panel and connect your Stripe, PayPal, or Square account.
- Map the form fields that set the amount (so it can total a variable order).
- Publish; respondents are routed to the add-on’s hosted checkout after submitting.
- Watch payment status flow back into your linked Google Sheet.
Setup is generally done in a desktop browser, even though the finished form works fine on a phone. The honest costs: checkout happens on the add-on’s domain, not your own, so the branding breaks for a moment; the add-on has its own fees on top of the processor’s, usually a limited free tier then a low monthly subscription; and you take on a dependency — if the add-on lapses or you stop paying, the payment flow stops with it. In exchange you get the two things the free methods can’t offer: variable pricing (real order totals) and payment verification written back to Sheets.
The Real Costs (Fees Stack Up)
Before you pick a method, price it out — because payment fees stack, and the total is easy to underestimate. There are up to two layers: the processor’s per-transaction fee, and (for Method 3) the add-on’s own charge.
| Cost layer | Typical rate (check current pricing) |
|---|---|
| Stripe (processor) | ~2.9% + $0.30 per transaction |
| PayPal (processor) | ~3.49% + $0.49 per transaction |
| Payment add-on | Limited free tier, then a low monthly fee |
| Google Forms itself | Free |
So a link-out or QR method costs only the processor’s cut, while an add-on adds a second layer on top. Rates change, so confirm the current numbers with each provider before you set your prices — and if margins are thin, build the fee into what you charge.
Comparison — Three Ways to Take Money
Side by side, the three methods trade simplicity for capability in a clear line: the easier it is to set up, the less it verifies and totals for you.
| Factor | Link-out (Method 1) | QR code (Method 2) | Add-on (Method 3) |
|---|---|---|---|
| Cost | Processor fee only | Processor fee only | Processor fee + add-on |
| Verifies payment? | ❌ No — manual | ❌ No — manual | ✅ Yes — status to Sheet |
| Variable pricing | ❌ Fixed amount | ❌ Fixed amount | ✅ Totals an order |
| Branded checkout | Processor page | Wallet app | ❌ Add-on’s domain |
| Set up where | Phone or desktop | Phone or desktop | Mostly desktop |
| Best for | Occasional fixed fee | In-person events | Regular, variable orders |
Notice there’s no column where Google Forms handles the money itself — every method hands payment to something else. That’s the honest shape of “payments with Google Forms”: collection in the form, checkout outside it.
When You Should Use a Different Tool
If collecting money is a regular, core part of what you do, a purpose-built tool is genuinely the better choice — and we’ll say that even though it points away from Google Forms. The workarounds here are glue; they shine for occasional, fixed-amount collection where Google Forms’ free reach and familiarity win. They strain when you need variable pricing, branded checkout on your own domain, automatic receipts, or inventory — anything that makes payment a routine, order-shaped operation.
The honest dividing line: use Google Forms + a workaround for the light cases — an event fee, a one-off order run, a donation drive. Reach for a dedicated form-and-payment platform with native checkout once payment becomes something you do every week. Matching the tool to the frequency saves you the reconciliation headache and the stacked fees.
Managing Payment Forms from Your iPhone
To be clear about what our own app does and doesn’t do: Forms for Google Drive (by Pipiform) does not process payments. It’s an iOS app for building and managing Google Forms — it doesn’t add a checkout, take cards, or replace any of the three methods above. Payment isn’t our battlefield, and we won’t pretend it is.
What it can do is help you run the forms around a payment flow from an iPhone: create and edit the registration or order form itself (our how to create a Google Form on iPhone guide covers the basics), review responses on the go, and export them for reconciliation — pairing naturally with our convert Google Forms responses to PDF guide when you need a clean record to match against your Stripe or PayPal dashboard. The payment itself still lives with your processor or add-on; the app just makes the form side of it pleasant on a phone.
Summary
Google Forms can’t collect payments natively — no payment field, no processor integration, no order-totaling, and a firm rule that card numbers must never go in a form because Forms isn’t PCI compliant. Three workarounds cover the real cases: link out to a Stripe or PayPal checkout in the confirmation message (free, but no verification and fixed amounts), a QR code for in-person events (fast and loose), or a Workspace add-on like Payable Forms that connects a real processor, totals variable orders, and writes payment status back to Sheets (the closest to real, at the cost of off-domain checkout and its own fees). Price in the stacked fees, keep all card data on the processor’s side, and if taking money becomes routine, a purpose-built tool is the honest upgrade. Google Forms is a fine, free way to collect the form; just let something built for money be the cashier.
Frequently Asked Questions
Can Google Forms collect payments?
Not on its own. Google Forms has no payment field, no built-in Stripe or PayPal integration, no checkout flow, and no calculation field to total an order — it was never designed to handle transactions. What people do instead is bolt payment onto the form from the outside: link out to a Stripe or PayPal checkout after submission, drop a payment QR code into the form, or install a Workspace add-on that connects a real payment processor and writes the payment status back to Google Sheets. Each works, but each is a workaround glued beside the form rather than a feature built into it, and each has trade-offs worth understanding first.
Can I add a credit card field to a Google Form?
No — and you must not try to. Google Forms is not PCI DSS compliant, so collecting a credit card number in a plain text question is both against the rules and genuinely unsafe: those numbers would sit in your response sheet in plain text, unencrypted for card data and outside any payment-industry safeguards. This is the one mistake in this whole topic that can actually get you into trouble. The correct approach is to never let card data touch your form at all — send respondents to a processor-hosted checkout (Stripe, PayPal, Square) that is built to handle card numbers securely, and let Google Forms collect only names, choices, and quantities.
How do I add a Stripe or PayPal link to a Google Form?
Create a payment link in your processor first — Stripe Payment Links and PayPal both let you generate a shareable checkout URL with no code. Then, in your form, open Settings, go to the Presentation section, and paste the link into the confirmation message respondents see after submitting (you can also put it in the form description). When someone finishes the form, they see 'Thanks — complete your payment here' with your link. It's the simplest, free method, and it works from an iPhone; just know the form still records a submission whether or not the person actually pays.
Can I verify who actually paid?
Only with an add-on, not with the free link-out method. When you simply paste a payment link into the confirmation message, the form submission and the payment are two disconnected events — Google Forms records that someone submitted, but has no idea whether they clicked through and paid, so you're left reconciling the form responses against your Stripe or PayPal dashboard by hand. A Workspace payment add-on closes that gap: because checkout runs through the add-on, it can write a paid/unpaid status back to your Google Sheet next to each response, so you can see at a glance who has actually paid.
Can Google Forms calculate an order total?
Not natively. Google Forms has no calculation or formula field, so it cannot multiply a quantity by a unit price or sum a cart to show an order total — a real limitation for anything order-shaped. You can work around it with fixed-price choices (for example, separate options priced $10, $20, $30) so respondents pick the amount directly, but the form itself never does math. If you need true variable pricing — quantity times price, tiered options, add-ons that sum — a payment add-on can read the selected fields and calculate the amount at checkout, which is one of the main reasons people graduate from the link-out method to an add-on.
What does a payment add-on cost?
Two layers stack up, so budget for both. First, the payment processor's own fee on every transaction — roughly 2.9% + $0.30 for Stripe and about 3.49% + $0.49 for PayPal at the time of writing (always check current rates). Second, the add-on's own pricing: tools like Payable Forms and PayQ typically offer a limited free tier (a handful of transactions a month) and then a low monthly subscription for unlimited use. So a $20 payment can carry a processor fee plus count against your add-on plan. For occasional collection the free tiers may cover you; for steady volume, factor the subscription into your pricing.
Is it safe to take payments through Google Forms?
It's safe when the money is handled by a real payment processor, and unsafe when it isn't. The safe pattern is to keep all card data off the form entirely: Google Forms collects names and choices, and a processor-hosted checkout page (Stripe, PayPal, Square) handles the actual card details behind its own PCI-compliant security. That's exactly how the link-out and add-on methods work. The unsafe pattern is putting a card-number field directly in the form — never do that, because Forms isn't built or certified to hold card data. Handled correctly, collecting payment alongside a Google Form is perfectly safe; the danger is only in trying to make the form itself the cashier.
Should I use a different tool for payments?
If payments are a regular part of your work, honestly, yes — even though that's not the answer that benefits us. Google Forms plus a workaround is a good fit for occasional, fixed-amount collection: an event fee, a small order run, a donation drive. But if you're taking payments routinely and need variable pricing, branded checkout on your own domain, automatic receipts, or inventory, a dedicated form-and-payment platform with native checkout will save you the reconciliation and the glue. Use Google Forms for the light, infrequent cases where its free reach and familiarity win; reach for a purpose-built tool when collecting money becomes a core, repeated task.