Four Stripe facts that decide your columns
| Stripe fact | What it means for the sheet |
|---|---|
| Amounts come in cents | Divide by 100; JPY is already whole |
| A refund leaves the payment unchanged | Log refunds as their own negative rows |
| Fees are not on the payment | Look them up, or reconcile from payouts |
| Events can arrive twice, out of order | Keep the ID; skip IDs you have |
Stripe retries failed deliveries for up to 3 days and does not promise order, which is why the ID check matters.
The columns to keep
| Column | From Stripe | Note |
|---|---|---|
| Payment ID | Payment intent or charge ID | Your duplicate check |
| Date | Created time | Sent in UTC; convert or say so |
| Customer | Name or email | Guest checkouts may have only email |
| Amount | Amount divided by 100 | Format as currency |
| Currency | Currency code | Never sum USD with EUR |
| Description | Description or product | Often empty; use the invoice number |
| Type | Payment or Refund | One SUMIF gives net of refunds |
How to log Stripe payments in Google Sheets
Step 1: Make the sheet first
Create the tab with the header row above, ID first, and freeze it. Tools map fields to the headers they find, so name them before you connect anything.
Step 2: Trigger on successful payments only
Use the "payment succeeded" event, not "payment intent created", which fires before the money moves. In viaSocket's catalog the Stripe trigger is "When a payment succeeds".
Do this step in 50agents
Set up an automation: every new Stripe payment is added as a row to my Google Sheet with the customer, amount and date
Build itCaptain reads one real payment from your Stripe account to plan the fields, tests the steps on it, and adds rows to your own sheet without waiting for approval. See the ready-made version.
Step 3: Check the ID before adding
Look the payment ID up in the sheet. If it is there, stop. This one step removes every duplicate from retries.
Step 4: Convert, then add the row
Divide the amount by 100 (unless the currency has no decimals), convert the time, and add the row.
Watch out. Check the first row against the Stripe Dashboard. An amount 100 times too big means the division step was skipped.
Step 5: Add a second automation for refunds
Trigger on refunds and add a row with Type Refund and a negative amount, so totals stay true without editing old rows.
Step 6: Backfill the past once
Export earlier payments from the Stripe Dashboard as CSV, paste them under the same headers, and let the automation carry on from the day it goes live.
What can go wrong
The same payment twice
A retried event added a second row. Look the ID up before adding, every time.
Refunds missing from the totals
Only payments were logged. Add the refund automation, and total with a SUMIF on Type, or sum the signed amounts.
Test payments mixed with real ones
The automation was connected to test mode while you set it up. Delete those rows, and check the connection is the live account.
The sheet stops accepting rows
Google's API allows 300 writes a minute per project and 60 per user, and a busy sale can hit that. Spread a backfill out, and keep one tab per year.
Questions people ask
Why is my Stripe amount 100 times too large in Google Sheets?
Stripe sends amounts in the smallest currency unit, so $25.00 arrives as 2500. Divide by 100, except for zero-decimal currencies such as JPY.
How do I include Stripe fees?
Fees are on the balance transaction, not the payment. Either add a step that fetches it, or reconcile fees monthly from your payout report, which is simpler and matches your bank.
Can I log old payments too?
Yes, once: export them from the Stripe Dashboard as CSV and paste them under the same headers. The automation only sees payments from the moment it goes live.
How do I keep test payments out of the sheet?
Connect the live Stripe account for the real sheet, and use a separate test sheet while you build. Test payments mixed into totals are hard to find later.
Can I log payments in more than one currency?
Yes. Keep a Currency column and never sum USD with EUR. Total each currency on its own, or convert in a separate column with the rate you used.
What if the sheet gets too big?
Google Sheets holds up to 20 million cells. Long before that it gets slow, so move each year's rows to an archive tab and keep the live tab short.