CONNECTOR · STRIPE

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

CONNECTOR · STRIPE

Stripe

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

categoríaOrigen · Pagos
target de frescuraHourly batch; webhook near-real-time en eventos críticos.
modelo de authRestricted API key (read-only).
modo de syncBackfill inicial + upserts vía webhook.

TABLAS SINCRONIZADAS

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

SCHEMA · MUESTRA

schema.sqlSQL

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

QUERY · MUESTRA

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 vs. balance_transactions mensualmente — vimos drift de 0,6% pasar 3 meses sin detección.

RELATED · CONNECTORS

Origen · Tracking de eventos

Segment

Conectá un pipeline real a tu warehouse

Revisión de stack de 30 min. Volvemos con scope, owner y contrato de frescura. Sin SDR, sin slide deck.

Agendar revisión de 30 min Abrir el playground