How to Send Stripe Payments to Google Sheets (Free CSV, Apps Script Webhook or Zapier)

Quick answer: The fastest method is Stripe's CSV export (Method 1). For automatic rows, use the free Apps Script webhook (Method 2) or Zapier (Method 3). Free? Yes for Methods 1 and 2. Time: about 2 minutes for the export, about 20 minutes for the webhook.

Stripe lets you export payments to a CSV file from the Dashboard, and that file opens in Google Sheets. To log each new payment as it happens, Stripe can push an event to a web address, and a short Google script can turn that event into a row. Zapier's Free plan includes 100 tasks per month as of 13 October 2026.

What do you need before you start?

You need three things:

• A Stripe account with at least one payment, ideally made through Stripe Checkout.
• A Google account with a blank Google Sheet.
• Permission to create API keys and webhooks in Stripe. If you are not the account owner, ask the owner.

Try everything in Stripe's test mode (called a sandbox in the Dashboard) first. Stripe says live and test mode use different keys and different webhook signing secrets, so repeat the setup for live mode when you are done.

How do you export Stripe payments to Google Sheets? (Method 1: CSV, free)

Open the Transactions page in the Stripe Dashboard, filter the list, click Export, then import the downloaded CSV into Google Sheets. Stripe's support page describes this flow. It is manual, but it needs no code and no keys.

1. Sign in to the Stripe Dashboard and open the Transactions page.
2. Filter by date range, payment method or payment type (for example successful or refunded).
3. Click Export.
4. Pick your settings and the columns you want, then confirm. A CSV file downloads to your device.
5. Open your Google Sheet and click File > Import.
6. Click Upload, drop in the CSV, and choose Append to current sheet or Replace current sheet.
7. Click Import data.

For accounting, Stripe recommends its Balance Summary Report instead of a payments export, saying it "functions similarly to a bank statement". Use the payments export when you want one row per payment.

How do you log every new Stripe payment in Google Sheets automatically? (Method 2: Apps Script webhook, free)

Create a Google Apps Script web app, give Stripe its URL as a webhook endpoint, and have the script add one row per paid Checkout Session. This works for payments made through Stripe Checkout. Stripe says that when someone pays, Checkout creates a checkout.session.completed event.

One design choice matters here. Stripe recommends checking each webhook with the Stripe-Signature header and the raw request body. Google's web apps page documents the request object as having parameters, a query string and post data, with no header field. So this script does not trust the incoming message. It reads only the session ID from it, then asks Stripe directly for the real session. A fake request can then add at most a row for a genuine, paid session.

Part A: Make a restricted Stripe key

1. In the Stripe Dashboard, open the API keys page and click Create restricted key.
2. Enter a Key name, such as "Sheets logger".
3. Set the permission for Checkout Sessions to Read, and leave everything else on None. Verify this step: the exact resource label in your Dashboard may differ.
4. Click Create key and complete the two-factor check.
5. Copy the key. Stripe says a restricted key starts with rk_live_ or rk_test_ and you cannot retrieve it later.

Part B: Add the script

1. Open your Google Sheet and name the first tab Payments.
2. In row 1, type these headers: Session ID, Created (UTC), Amount, Currency, Email, Status.
3. Click Extensions > Apps Script.
4. Delete the sample code and paste the script below.
5. Click the Project Settings gear, then Script Properties, then Add script property. Name it STRIPE_KEY and paste your restricted key as the value.

// Stripe -> Google Sheets. Paste into Extensions > Apps Script.
// Stripe key lives in Script Properties as STRIPE_KEY (never in the code).

const SHEET_NAME = 'Payments';

function doPost(e) {
  try {
    const event = JSON.parse(e.postData.contents);
    const okTypes = [
      'checkout.session.completed',
      'checkout.session.async_payment_succeeded'
    ];
    if (okTypes.indexOf(event.type) === -1) {
      return reply('ignored');
    }

    // Do not trust the payload. Ask Stripe for the real session.
    const sessionId = event.data.object.id;
    const session = fetchSession(sessionId);
    if (session.payment_status !== 'paid') {
      return reply('not paid yet');
    }

    const sheet = SpreadsheetApp.getActiveSpreadsheet().getSheetByName(SHEET_NAME);
    if (alreadyLogged(sheet, session.id)) {
      return reply('duplicate');
    }

    const email = (session.customer_details && session.customer_details.email)
      || session.customer_email || '';
    sheet.appendRow([
      session.id,
      new Date(session.created * 1000).toISOString(),
      session.amount_total / 100,   // check: this assumes a currency with 2 decimals
      (session.currency || '').toUpperCase(),
      email,
      session.payment_status
    ]);
    return reply('ok');
  } catch (err) {
    console.error(err);
    return reply('error');
  }
}

function fetchSession(id) {
  const key = PropertiesService.getScriptProperties().getProperty('STRIPE_KEY');
  const res = UrlFetchApp.fetch('https://api.stripe.com/v1/checkout/sessions/' + id, {
    headers: { Authorization: 'Bearer ' + key },
    muteHttpExceptions: true
  });
  if (res.getResponseCode() !== 200) {
    throw new Error('Stripe returned ' + res.getResponseCode() + ': ' + res.getContentText());
  }
  return JSON.parse(res.getContentText());
}

function alreadyLogged(sheet, sessionId) {
  const last = sheet.getLastRow();
  if (last < 2) return false;
  const ids = sheet.getRange(2, 1, last - 1, 1).getValues().flat();
  return ids.indexOf(sessionId) !== -1;
}

function reply(text) {
  return ContentService.createTextOutput(text);
}

The amount_total field is an integer in the Checkout Session object; Stripe's example shows 2198 with currency usd. Dividing by 100 gives dollars and cents for two-decimal currencies. Check your own currency before trusting the totals.

Part C: Publish it as a web app

1. In the Apps Script editor, click Deploy > New deployment.
2. Next to "Select type", click the gear and choose Web app.
3. Set Execute as to Me. Google describes this as the script always running as the owner.
4. Under who has access, choose the option that lets anyone reach the URL without signing in. Verify this step: Google's page does not list the option names, and your Workspace admin may block public access.
5. Click Deploy, approve the permission prompts, and copy the Web app URL.

Use the /exec URL. Google says the /dev URL only works for people with edit access and always runs the latest saved code.

Part D: Point Stripe at the script

1. Open the Webhooks tab in Workbench (dashboard.stripe.com/webhooks).
2. Click Create an event destination.
3. Select Your account.
4. Choose the Snapshot payload format (not Thin), because the script reads the session ID from the event's data.object.
5. Select the events checkout.session.completed and checkout.session.async_payment_succeeded, then click Continue.
6. Choose Webhook endpoint as the destination type and click Continue.
7. Paste your Apps Script URL as the Endpoint URL and finish.
8. Make a test payment in test mode, then check the Payments tab.

The signing secret (starts with whsec_) is not needed by this script. Stripe's webhook docs say the secret is used for signature checks.

How do you connect Stripe to Google Sheets with Zapier? (Method 3: no code)

Create a Zap with the Stripe trigger New Payment and the Google Sheets action Create Spreadsheet Row. Zapier lists New Payment as "Triggers when a new payment is completed" and Create Spreadsheet Row as "Create a new row in a specific spreadsheet".

1. In Zapier, click Create > Zap.
2. For the trigger, choose Stripe, then the event New Payment, and connect your Stripe account.
3. For the action, choose Google Sheets, then the event Create Spreadsheet Row.
4. Select your spreadsheet and worksheet.
5. Map Stripe fields (amount, currency, customer email, ID) to your sheet columns.
6. Test, then turn the Zap on.

Zapier also lists Checkout Session Completed, New Charge, Failed Payment and New Refund as Stripe triggers, which is useful if you want refunds logged on a second tab.

Which method should you choose?

Pick the CSV export for one-off reports, the Apps Script webhook for free live logging, and Zapier if you want no code and can live with its limits. Prices are as of 13 October 2026.

What's free and what costs money?

Stripe's export and webhooks have no extra fee listed on the pages used here, and Apps Script is part of your Google account. Zapier is the only paid piece, as of 13 October 2026:

• Free: 100 tasks per month, unlimited Zaps, two-step Zaps (one trigger, one action), 15-minute polling. Zapier says premium apps are paid-only.
• Professional (750 tasks): $19.99 per month billed annually, or $29.99 billed monthly.
• Trial: 14 days of Professional for new accounts, no card required.

Triggers do not count as tasks; each row written to Sheets does.

What can go wrong, and how do you fix it?

1. Rows appear twice. Stripe says the same event can arrive more than once and live-mode retries run for up to three days. The script's alreadyLogged check prevents repeats. If you changed the sheet layout, keep Session IDs in column A.
2. Nothing arrives. In Workbench, open your endpoint and check Event deliveries (Delivered, Pending or Failed). Also confirm you published a new version after editing code, and that you used the /exec URL.
3. Stripe shows deliveries as Failed. Stripe says your endpoint must return a 2xx quickly and that 3xx redirects count as failures. If Failed shows even though rows appear, rely on the duplicate check, or switch to Zapier.
4. "Stripe returned 401" in the logs. The key is wrong or missing. Re-check the STRIPE_KEY script property, and remember test and live keys are separate.
5. "Stripe returned 403 or a permissions error". Stripe says a missing permission returns an error that explains which permission to add. Edit the restricted key and re-save.
6. Amounts look 100 times too big. You are seeing the raw integer. Keep the / 100 for two-decimal currencies.
7. Delayed payments are missing. Methods like ACH send a later checkout.session.async_payment_succeeded event. Make sure that event is selected in Stripe.

Is this allowed?

Yes, with care about customer data. Payment rows contain customer emails, so limit sheet sharing to people who need it and never paste a full secret key into a cell. Stripe's docs advise using restricted keys as drop-in replacements for secret keys, which keeps access narrow. If you plan to email these customers from the sheet, see how to send emails from Google Sheets automatically and check your local marketing-email rules first.

What's still unclear?

• Header checks. Google's documentation does not describe request headers in doPost, which is why this script re-fetches the session instead of verifying Stripe-Signature. If Google adds header access, signature checks would be stronger.
• Delivery status. Whether Stripe marks Apps Script deliveries as Failed in your account depends on the response your deployment sends back. Check your own Event deliveries tab after a test.
• Scope. The script handles Checkout Sessions only. Payments from Payment Links, invoices or subscriptions renewals use other events, and the script does not log them.

Looking for similar logging jobs? See how to connect Gmail to Google Sheets with Apps Script and how to get Google Sheets alerts on WhatsApp to be notified of each new payment row.

Last checked: 13 October 2026.