CONNECTOR · STRIPE

Stripe — Charges, customers, subscriptions, refunds, disputes. Reconciliado ao centavo.

CONNECTOR · STRIPE

Stripe

Charges, customers, subscriptions, refunds, disputes. Reconciliado ao centavo.

categoriaOrigem · Pagamentos
alvo de frescorHourly batch; webhook near-real-time em eventos críticos.
modelo de authRestricted API key (read-only).
modo de syncBackfill inicial + upserts via webhook.

TABELAS SINCRONIZADAS

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

SCHEMA · EXEMPLO

schema.sqlSQL

CREATE TABLE stripe.charges (
  id              TEXT PRIMARY KEY,
  customer        TEXT,
  amount          BIGINT,
  currency        TEXT,
  status          TEXT,
  created         TIMESTAMP,
  refunded        BOOLEAN
);

QUERY · EXEMPLO

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

Reconciliar gross_revenue vs. processor.balance_transactions mensalmente — já vimos drift de 0,6% passar 3 meses sem detecção.

RELATED · CONNECTORS

Origem · Tracking de eventos

Segment

Conecte um pipeline real ao seu warehouse

Revisão de stack de 30 min. Voltamos com escopo, owner e contrato de frescor. Sem SDR, sem deck.

Agendar revisão de 30 min Abrir o playground