Stripe + Go Fig

Accounting

Connect Stripe to Go Fig for complete payment data visibility and revenue analytics.

Stripe processes your payments, but the real insight comes from joining payments, payouts, refunds, and fees to your accounting ledger and CRM. Go Fig pulls Stripe's full balance-transaction grain into the Financial Intelligence Graph, so revenue recognition, MRR roll, and payout reconciliation happen against the same canonical numbers your accountant trusts.

Connect Stripe See All Integrations

Key facts

Auth: Restricted API key, optional Connect
Grain: Balance-transaction (most granular)
Multi-account: Connect platforms supported
Subscription data: Full Billing object coverage
Sync cadence: Webhook-driven, near real time

SOC 2 Type II · All integrations

What you can do with Stripe data in Go Fig

Revenue Recognition

Roll Stripe charges, refunds, and credit notes into ASC 606 schedules joined to your accounting ledger.

Subscription Analytics

Track MRR, churn, expansion, and net retention with the Subscription, Invoice, and Customer objects ingested at full grain.

Payout Reconciliation

Match Stripe payouts to bank deposits and the underlying balance transactions, automating one of finance's slowest weekly tasks.

Data available from Stripe

Go Fig extracts and normalizes the following data from your Stripe account:

Payments

Refunds

Disputes

Subscriptions

Invoices

Customers

Products

Prices

Payouts

Balance transactions

Fees

Transfers

How to connect Stripe

Generate a restricted API key

In your Stripe dashboard, go to Developers, API keys, Create restricted key. Grant read access to Charges, Customers, Subscriptions, Invoices, Payouts, Balance Transactions, and any other resources you want exposed. Keep write permissions disabled. Store the key in Go Fig's connector setup.

Configure webhook events

Add a webhook endpoint pointing to Go Fig and subscribe to charge, invoice, subscription, and payout events. The signing secret authenticates inbound events. This drives near-real-time updates rather than waiting for the next polling cycle and is how MRR dashboards stay current intra-day.

Connect multi-account or Stripe Connect platforms

If you operate a Stripe Connect platform or have multiple accounts (test, live, region-specific), authorize each one. Each connected account lands in its own partition with its own balance, so platform-level reporting and per-merchant reporting both work without join gymnastics.

Map balance transactions to your chart of accounts

Stripe's balance-transaction grain captures every fee, refund, dispute, transfer, and reserve adjustment. Go Fig pre-suggests a mapping from each balance-transaction type to GL accounts in QuickBooks, NetSuite, Xero, or Sage, then lets your accountant lock the mapping for revenue recognition and payout journal automation.

Authentication: Restricted API key with read-only scopes on the resources you choose to expose. Webhook signing secret is configured for event-driven sync. For Stripe Connect platforms, OAuth flow is used per connected account so each merchant's data lands in its own partition.

Common Questions About Stripe Integration

What's the grain of data Go Fig pulls from Stripe?

Balance-transaction grain, which is the most granular level Stripe exposes. Every charge, refund, fee, dispute reserve, transfer, and adjustment is pulled as its own row with the linked source object (charge, invoice, subscription) attached. This is what makes payout reconciliation possible: every dollar in a Stripe payout traces back to the underlying transactions that produced it.

Does Go Fig support Stripe Connect platforms with many connected accounts?

Yes. Each connected account is authorized via OAuth and lands in its own partition. Platform-level views aggregate across accounts with the connected account ID preserved as a dimension, so per-merchant payout schedules, fee economics, and revenue can be reported either platform-wide or per merchant. Application fees and transfers between accounts are tracked separately so platform take rate is queryable.

How does Go Fig handle Stripe rate limits?

Stripe enforces 100 read and 100 write requests per second in live mode (25 each in test). Go Fig drives steady-state sync via webhooks, so polling load is minimal. Backfills use parallel pagination tuned to stay under the read ceiling. The connector dashboard surfaces your current request rate so administrators can confirm we are not interfering with checkout or subscription operations.

Are MRR, churn, and expansion calculated from Stripe data?

Yes. Subscription, Invoice, and Customer objects are ingested with status changes preserved, so MRR roll, gross churn, expansion, contraction, and net retention can be calculated using the same logic Stripe's own dashboard uses, plus any custom segmentation you add (plan tier, geography, channel). Because the data lives in the graph alongside your CRM and accounting ledger, those metrics tie back to booked revenue and CAC.

How are refunds, disputes, and reserve adjustments handled?

Each is its own balance-transaction row with the linked charge, dispute, or transfer. Refunds reduce gross revenue in the period they occur (with the option to apply ASC 606 timing in a flow). Disputes are tracked through their lifecycle (warning_needs_response, won, lost) and the reserve adjustment that funds them is visible. This means payout reconciliation never has unexplained variance from these adjustments.