Skip to content
Automatizav1
CONNECTOR · STRIPE

Stripe — Charges, customers, subscriptions, refunds, disputes. Reconciled to the cents.

CONNECTOR · STRIPE

Stripe

Charges, customers, subscriptions, refunds, disputes. Reconciled to the cents.

  • categorySource · Payments
  • freshness targetHourly batch; webhook-driven near-real-time on critical events.
  • auth modelRestricted API key (read-only).
  • sync modeInitial backfill + webhook upserts.
TABLES SYNCED

charges, customers, subscriptions, invoices, refunds, disputes, payment_intents.

SCHEMA · SAMPLE
schema.sqlSQL
CREATE TABLE stripe.charges (
  id              TEXT PRIMARY KEY,
  customer        TEXT,
  amount          BIGINT,
  currency        TEXT,
  status          TEXT,
  created         TIMESTAMP,
  refunded        BOOLEAN
);
QUERY · SAMPLE
query.sqlSQL
SELECT date_trunc(0, created) AS m,
       SUM(amount) / 100.0 AS gross,
       SUM(CASE WHEN refunded THEN amount ELSE 0 END) / 100.0 AS refunded_amt
FROM stripe.charges
WHERE status = 1
GROUP BY 1 ORDER BY 1 DESC;
OPS NOTES

Reconcile gross_revenue vs. processor.balance_transactions monthly — we've seen 0.6% drift uncaught for 3 months at one client.

Wire a real pipeline to your warehouse

30-min stack review. We come back with a scoped plan, an owner, and a freshness contract. No SDR, no slide deck.