How to Collect Payments with Google Forms for Free

Google Forms is one of the most widely used form tools in the world — and for good reason. It’s free, easy to use, and integrates seamlessly with the rest of Google Workspace. But if you’ve ever tried to collect payments directly through Google Forms, you’ve probably run into a frustrating reality: Google Forms doesn’t support payments natively.

That means no credit card fields, no checkout page, and no built-in way to confirm that someone has actually paid. For small businesses handling event registrations, service bookings, or product orders, this is a real bottleneck.

The good news? There are a few free workarounds — and one significantly better alternative. In this guide, we’ll walk through three ways to collect payments with Google Forms for free, along with their limitations, so you can decide what’s right for your business.

Why Google Forms Doesn’t Support Payments Out of the Box

Google Forms was built for data collection — surveys, quizzes, and registrations. It was never designed as a payment tool. More critically, Google Forms is not PCI DSS compliant — it lacks the security controls required to safely handle credit card data directly.

This is a hard technical limitation, not a missing feature that’s “coming soon”. Any payment solution with Google Forms requires connecting a third-party tool.

⚠️ Never add credit card fields to a Google Form. It might seem like a shortcut to add fields asking for a card number, expiry date, or CVV — but this violates PCI DSS requirements and puts your customers at serious risk. Google Forms does not encrypt field data at the level required for payment card information, and collecting it this way exposes both your customers and your business to liability. Payment data must flow through a certified payment processor, not a form field.

Method 1: Add a Payment Link to Your Confirmation Message

Best for: Simple, fixed-price transactions with a small, trusted audience.

The easiest free workaround is to include a payment link in the confirmation message that appears after someone submits your form.

Steps:

1. Open your Google Form and switch to the Settings tab.

   

2. Expand the Presentation tab.

3. In the Confirmation message field, click Edit, and paste in a payment link (e.g., a PayPal.me link, Stripe payment link, or Venmo handle).

   

   Example confirmation message:
   “Thank you for registering! Please complete your payment of $50 here: [your payment link]. Your spot will be confirmed once payment is received.”

4. Click Save.

Limitations:

• No way to verify who has paid — you’ll need to manually reconcile responses and payments.

• Respondents can submit the form without ever paying.

• Fixed pricing only — you can’t automatically calculate totals based on form selections.

What manual reconciliation actually looks like: If 100 people register for an event and 30 pay, you have two completely separate records — Google Sheets with your form responses, and your PayPal or Stripe dashboard with payment records. There’s no shared transaction ID linking them. You’re matching by name or email, and names frequently appear differently across both systems (“Jon Smith” vs “Jonathan Smith”). For anything above a dozen responses, this quickly becomes error-prone work.

Method 2: Embed a QR Code Inside the Form

Best for: In-person or community events where respondents are likely to use the same P2P payment app.

Instead of a link after submission, you can embed a QR code directly inside your form so respondents can scan and pay mid-form or at the end.

Steps:

1. Generate a QR code for your payment platform (PayPal, Venmo, Cash App, Zelle). Most platforms provide this in your account settings.

2. Open your Google Form and click the image icon (Add Image) on a question.

   

3. Upload your QR code image.

4. Add instructions asking respondents to scan and pay before submitting.

Limitations:

• Many P2P payment apps (Venmo, Cash App, Zelle) require the app to be installed for QR scanning to work — not all customers will have it.

• Still no automatic confirmation that payment has been made.

• Not suitable for professional or branded client-facing workflows.

Refunds and disputes: If a customer requests a refund, you’re processing it manually in the payment app while separately looking up their original form submission. Because the form and the payment are in two different systems with no shared transaction ID, matching them takes extra effort — especially at higher volumes.

Method 3: Use a Google Workspace Add-On

Best for: Businesses that want to stay within Google Forms and need automatic payment calculation.

Google Workspace Marketplace offers add-ons like PayForm that add a payment layer on top of Google Forms. Depending on the add-on, they can calculate a total from your form answers and redirect respondents to a third-party checkout page.

Steps:

1. Find an Add-on: Go to ⋮ > Get add-ons and search for a tool like PayForm.

   

2. Install the Plugin: Grant the necessary permissions to access your form data.

3. Setup: Click the puzzle icon (🧩) to configure your new payment add-on.

   

4. Configure Pricing: Add prices to your form questions by including a currency symbol (e.g., “$50”). Then, go to the plugin settings to link your form to a payment gateway like Stripe or PayPal.

Limitations:

1. Add-ons can be unstable and may require re-authorization periodically.

2. Limited customization — the checkout page is hosted by the add-on, not your brand.

3. No built-in document generation, e-signatures, or multi-step form logic.

4. Pricing tiers can add up quickly as your volume grows.

5. These add-ons are third-party products, not Google’s — if a developer stops maintaining one, your payment flow may break without warning.

The Limitations of All Google Forms Payment Methods

All three methods above share a fundamental problem: they’re workarounds, not integrated solutions. While they work for occasional use, they often lead to manual reconciliation errors or a disjointed customer experience.

If your business needs a more streamlined approach, PlatoForms is designed to bridge the gap. It’s a professional form builder that turns complex documents and data collection into a seamless workflow — with payment processing built directly into the core experience.

Here’s what you’re giving up when using workarounds versus a native platform:

A Better Way: Collect Payments Natively with PlatoForms

If your business collects payments regularly — for client onboarding, service agreements, event registrations, or product orders — the workarounds above will cost you more time than they save in money.

PlatoForms supports three payment providers natively. Each form uses one provider — once you add a payment field, the others are disabled, which keeps the checkout clean and avoids conflicts. All three support fixed and dynamic pricing. PlatoForms does not charge any additional transaction fees.

Stripe — cards, Apple Pay, Google Pay

Stripe is the most flexible option. Drag the Stripe Payment widget onto your form, connect your Stripe account, and choose between a fixed amount or a dynamic amount pulled from a form field. Stripe supports credit and debit cards, and once you register your form domain in the Stripe Dashboard, Apple Pay and Google Pay appear automatically for supported browsers and devices.

Stripe also has full Test Mode — connect a separate test account in the widget settings, and all preview-mode submissions use test card numbers with no real charges. This lets you verify the full payment flow before going live.

For dynamic pricing, switch to Amount from a form field, point the widget at a hidden field, and drive that field’s value with form logic. Add {{pricing}} to the widget label and the amount updates live as the respondent fills in the form.

Best for: Card-first businesses, subscriptions, businesses that need Apple Pay and Google Pay, or anyone who wants sandbox testing before launch. See the Stripe integration guide for full setup.

PayPal — PayPal, cards, Pay Later

The PayPal Payment widget renders PayPal’s Smart Payment Buttons directly inside your form — PayPal checkout, credit/debit card, and Pay Later options all in one field, with no redirect. Customers who don’t have a PayPal account can still pay by card.

PayPal provides free Sandbox accounts for testing. Connect a sandbox account in the widget’s test slot, and all preview submissions run through PayPal’s test environment — a mock buyer and merchant, no real money involved.

Best for: Businesses where customers expect PayPal as a checkout option, or where Pay Later options can improve conversion for higher-value services.

Square — embedded field or checkout redirect

Square offers two modes. The Square Payment field keeps the respondent on your form throughout — they enter card details inline, no redirect. The Square Checkout integration redirects the respondent to a Square-hosted page after submission and automatically sends them a receipt email.

One important limitation: Square supports live payments only — there’s no sandbox or test mode. Any test submission charges a real card. If you need to verify the flow, charge a small amount and refund it from your Square Dashboard.

Watch: setting up the Square Payment field in PlatoForms — fixed pricing, variable pricing, and viewing the transaction ID in submissions.

Best for: Businesses that already use Square for in-person transactions and want their online and in-person payments consolidated in one Square account. See the Square integration guide for full setup.

All three providers support the same dynamic pricing mechanism — PayPal and Square have the same Fixed Amount / Amount from a form field toggle in their widget settings. Not sure which provider to use? See Stripe vs. Square vs. PayPal for a side-by-side comparison.

Which Method Should You Choose?

• Occasional, low-volume payments from a trusted audience → The confirmation message link is fast and free.
• In-person events with a community group → The QR code method works fine.
• Regular payments, card-first customers, or anyone who needs Apple Pay/Google Pay → PlatoForms with Stripe.
• Customers who expect PayPal, or higher-value services where Pay Later matters → PlatoForms with PayPal.
• Businesses already running Square at a physical location → PlatoForms with Square.

Google Forms is a great tool for what it was built to do. Payment collection just isn’t one of those things — and the workarounds reflect that. If payments are a core part of how your business operates, you deserve a tool built to handle them natively.

Once payments are live, you can set up logic-based email routing to automatically notify the right team or send custom receipts based on what was ordered. Need to collect a signed waiver or consent form alongside payment? See how to combine waivers and payments in a single form.

Start a free 15-day trial with PlatoForms — full features, no credit card required.

Already using Google Forms? You don’t have to start from scratch — import your existing form into PlatoForms and add native payment support in minutes.