From Stripe to SQL Server: managed, scheduled, no code.
Creating a pipeline that sends data from Stripe to SQL Server databases takes only a few minutes with Kondado. And the whole integration from Stripe to SQL Server is managed and executed by our platform. With Kondado, you can focus on extracting value from Stripe data and combining it with other data in your SQL Server database
Kondado connects your Stripe account to SQL Server and replicates payments, subscriptions, invoices, customers and balance data on a schedule you define. You authorize the Stripe data source once, point Kondado at your SQL Server instance, then choose which of the 51 available pipelines you want to load. From that moment, Kondado reads the selected Stripe endpoints and writes the records into your SQL Server database, so your team queries payment data with the T-SQL skills it already has.
Kondado replicates Stripe data to SQL Server across 51 pipelines and 1,971 fields, covering charges, payment intents, subscriptions, invoices, refunds, disputes, payouts, balance transactions, products, prices, coupons and events. Updates run on a configurable schedule, from every 5 minutes to daily, and each pipeline writes into its own destination table in SQL Server that you can join with internal revenue, CRM or ERP data.
Once your Stripe records land in SQL Server, you can build the reporting your finance and product teams actually need. The Charges and Payment intents pipelines give you transaction-level detail for revenue reconciliation, while the Subscriptions pipeline supports MRR, churn and renewal analysis joined against your own customer records. Add the Balance transactions and Payouts pipelines to close the loop between what customers paid and what reached your bank account. Analysts can blend this data with internal order, CRM or ERP tables and publish the results to Power BI or Looker Studio.
Try out all the features for free for 14 days
Replicated to SQL Server
Stripe data available for SQL Server
Tables Kondado writes into your SQL Server, on a schedule you control.
51
available pipelines
1971
extractable fields
SQL Server
Destination
Available integrations
Subscription schedules
Registry of subscription schedules, with id, customer, subscription, status, creation, cancellation, completion and release dates, current phase, billing mode, default settings, end behavior, and live-mode flag.
Early fraud warnings
Record of early fraud warnings, with id, actionable flag, related charge and PaymentIntent, creation timestamp, fraud type, and live/test mode.
Tax rates
Tax rate record with identifier, active status, country, state and jurisdiction, display name, percentage and effective percentage, flat amount and currency, inclusive flag, rate type and tax type, creation timestamp, and live mode.
Subscriptions
Subscription record with identifier, customer, status, collection method, currency, billing cycle and anchor, creation, start, cancellation and end dates, fee amounts and percentages, discounts, thresholds, invoice and trial settings, plus schedule and pending updates.
Subscriptions - Details - Subscription items
Subscription items, with id, associated subscription and price, quantity, billing and trial periods, usage thresholds, and price attributes such as currency, unit amount, recurring interval, and usage type.
Customers
Stripe customer records, with identifier, name/business, email, address, balance and currency, invoice settings, tax data, shipping, discount, cash balance, and creation timestamp.
Customers - Details - Tax IDs
Registry of each customer's tax IDs (CNPJ, CPF, VAT, etc.), with country, type, value, verification status, creation timestamp, and customer, account, and owner references.
Customers - Details - Payment methods
Payment methods linked to customers, with identifiers, billing details, card details (brand, expiry, last four digits, checks), bank accounts, and digital wallets.
Each row is a customer credit balance transaction, with id, customer_id, amount, ending_balance, currency, type, created, description, livemode, and related IDs for checkout_session, credit_note, customer, customer_account, and invoice.
Charges
Stripe charge records with id, amount, captured and refunded amounts, currency, creation date, status, paid/captured/refunded/disputed flags, customer, PaymentIntent, payment method, balance transaction, risk outcome, and billing/shipping details.
Billing credit grants
Registry of billing credit grants issued to customers for consumption-based billing, with id, customer/account, monetary amount and currency, type, category, priority, price scope, effective/expiration/void timestamps, live/test mode, and creation/update timestamps.
Connected accounts (Connect)
Registry of connected accounts (Connect), with identifier, business profile (name, MCC, type, estimated annual and monthly revenue, estimated worker count), support details, and payment capability statuses.
Disputes
Stripe dispute records, with id, disputed amount, currency, related charge and PaymentIntent, reason, status, creation and evidence due dates, plus evidence and eligibility details.
Coupons
Registry of discount coupons, with identifier, name, amount or percentage off, currency, duration and duration in months, redemption limits and count, redemption deadline, validity status, livemode flag, and creation timestamp.
Promotion codes
Registry of promotion codes customers enter to apply a coupon, with identifier, code, active status, customer, expiration, redemption limits and count, promotion type, and minimum-amount and first-transaction restrictions.
Events
Record of Stripe account events, with id, account, API version, context, creation time, livemode, pending webhooks, request details, event type, and the affected object's id and type.
Invoices
Registry of invoices, with identifier, customer, currency, amounts due/paid/remaining, creation and due dates, collection method, billing reason, and automatic tax status.
Invoices - Details - Invoice line items
Each row represents a Stripe invoice line item, with invoice, subscription, and parent identifiers, plus amount, subtotal, currency, quantity/quantity_decimal, period_start/period_end, description, discountable, livemode, parent_type, and pricing details (price, product, pricing_type).
Entitlement features
Registry of features that can be granted to customers by product, with unique identifier, active status, live-mode flag, lookup key, and name.
Setup intents
Each row records a SetupIntent, with id, customer, status, usage, created, payment_method, cancellation_reason, last_setup_error fields, automatic_payment_methods, mandate, latest_attempt, and livemode.
Payment intents
Payment intent records, with id, amount and amount received, currency, status, creation date, customer, payment method, capture and confirmation method, cancellation reason, latest charge, and transfer data.
Invoice items
Record of an invoice item, with id, amount and currency, linked customer and invoice, date, description, quantity, discount and proration flags, period, and pricing/subscription details.
Payment links
Registry of payment links, with identifier, active status, URL, currency, post-purchase behavior, tax, invoice, PaymentIntent, subscription, application fee, transfer amount, and session restriction settings.
Payment links - Details - Line items
Line items of payment links, with payment_link_id, id, quantity, description, currency, discount, subtotal, tax and total amounts, plus price data (id, type, billing scheme, recurring interval and unit amount) and adjustable quantity limits.
Radar value lists
Each row represents a Radar value list, with id, alias, name, item type, creator, creation timestamp, and live mode indicator.
Radar value lists - Details - Items
Item in a Radar value list, with its own and parent list identifiers, value, creation timestamp, creator, and live-mode indicator.
Billing meters
Registration of usage billing meters for consumption-based billing, with id, display_name, event_name, default_aggregation_formula, customer_mapping_type, event_time_window, status, livemode, and creation, update, and deactivation timestamps.
Credit notes
Credit notes issued or voided, with identifier, customer, invoice, status, reason, currency, amounts (subtotal, total, tax, shipping and payment amounts), creation/effective/void dates, and PDF link.
Credit notes - Details - Line items
Each row represents a credit note line item, with credit note and item IDs, amount, description, discount amount, linked invoice line item, livemode flag, quantity, type, and unit amounts.
Quotes
Record of quotes with id, status, customer, invoice and subscription, currency, subtotal/total amounts and computed recurring and upfront totals, discount, shipping and tax details, creation/expiration/status-transition dates, and invoice and subscription settings.
Quotes - Details - Line items
Each row represents a quote line item, with quote_id and id, description, quantity, currency, discount, subtotal, tax, and total amounts, plus price details (id, type, unit amount, recurrence, product) and adjustable quantity limits.
Invoice payments
Payments applied to invoices, with id, related invoice, paid and requested amounts, currency, status, payment type and originating payment references, default flag, livemode, and creation, payment, and cancellation timestamps.
Plans
Registry of recurring price plans, with id, active status, amount and currency, billing scheme, interval and interval count, product, nickname, tiers mode, usage type, trial days, meter, usage transformation, creation timestamp, and live/test mode.
Prices
Registry of product prices (one-time or recurring), with id, active status, currency, unit amount, billing scheme, recurring interval, associated product, and tier and tax settings.
Products
Stripe catalog product record, with identifier, name, description, active status, default price, package dimensions, tax code, unit label, URL, and creation and update timestamps.
Top-ups
Record of each balance top-up, with id, amount and currency, status, creation time, balance transaction, payment method, initiator, failure code/message, expected availability date, description, statement descriptor, source ID, and transfer group.
Refunds
Each row represents a Stripe refund, with id, amount, currency, status, reason, creation date, links to charge, customer, and PaymentIntent, plus balance transaction, destination, failure/pending, and presentment details.
Payouts
Each row is a payout, with id, amount, currency, status, creation and arrival dates, method, destination, balance transaction, failure code/message, and reversal references.
Payouts - Details - Payout transactions
Each row is a balance transaction linked to a payout, with identifier, gross amount, fee, net amount, currency, status, type, reporting category, availability and creation dates, source, and exchange rate.
Radar reviews
Each row represents a Radar review, with its identifier, associated charge and PaymentIntent, open/closed status and reasons, creation timestamp, IP and location data, session details, and live-mode flag.
Current balance
Current Stripe account balance per balance type and currency, with amount, portions from cards, bank accounts, and FPX, production/test mode flag, and read timestamp.
Checkout sessions
Checkout sessions, with unique id, creation and expiration timestamps, currency, subtotal and total amounts, customer, invoice, and PaymentIntent references, plus address, tax, branding, and consent data.
Checkout sessions - Details - Line items
Line items of a checkout session, with session and item identifiers, quantity, description, currency, discount, subtotal, tax and total amounts, plus price details such as product, type, recurrence, tax behavior and unit amount.
Identity verification sessions
Each row represents an identity verification session, with id, client_reference_id, created, status, type, livemode, document/email/phone and matching options, provided details, latest error, redaction_status, related customer/person, verification_flow, and verified outputs (address, date of birth, email, name, ID number, phone, and sex).
Shipping rates
Each row represents a shipping rate, with id, active status, creation time, display name, delivery estimate minimum/maximum unit and value, fixed amount and currency, livemode, tax behavior, tax code, and calculation type.
Application fees
Each row represents a Stripe application fee, with its identifier, account, application, related charge and balance transaction, amount and amount refunded, currency, creation time, fee source, live mode, and full-refund indicator.
Terminal readers
Registry of terminal readers, with id, label, serial number, device type and software version, IP address, location, network status, last seen, livemode, and action details such as type, status, API errors, refund, display, print, and processing configurations.
Terminal locations
Registry of physical locations for Stripe Terminal readers, with id, address (including kana/kanji variants), display name, configuration override, phone, and live-mode flag.
Balance transactions
Each row is a Stripe balance transaction, with id, gross amount, fee, net impact, currency, exchange rate, creation and availability dates, balance type, reporting category, source, status, and transaction type.
Transfers
Stripe transfer record with identifier, amount and reversed amount, balance transaction, creation timestamp, currency, description, destination account, destination payment, live mode, reversal status, source charge, source type, and transfer group.
Transfers - Details - Reversals
Transfer reversals, with id, reversed transfer, amount, currency, creation timestamp, balance transaction, and linked source/destination payment refunds.
Sync data automatically — no code, no manual exports.
1
Connect Stripe on Kondado
Authorize your Stripe account as a data source inside Kondado and confirm which account you want to replicate. The connection takes a few minutes and requires no code.
2
Configure your SQL Server destination
Enter your SQL Server host, database, port and user credentials, then test the connection so Kondado can write to the target schema. You can point to an existing database or a dedicated reporting one.
3
Select pipelines and set the schedule
Choose the Stripe pipelines you need, such as Charges, Subscriptions or Balance transactions, and set the update schedule from every 5 minutes to daily. Save the configuration and Kondado begins loading data into SQL Server.
Try out all the features for free for 14 days
Hundreds of data-driven companies trust Kondado
Why Kondado?
Focus on extracting value from your data and leave the rest to us
Answers about sending Stripe data to SQL Server automatically
How does Kondado move Stripe data into SQL Server?▼
You connect Stripe as a data source, enter your SQL Server connection details, and select the pipelines you need. Kondado then reads those Stripe endpoints on your configured schedule and writes the records into your database. No code is required on your side, and you can adjust the pipeline selection whenever your reporting needs change.
Which Stripe pipelines can I replicate to SQL Server?▼
There are 51 pipelines and 1,971 fields available, spanning charges, payment intents, refunds, disputes, subscriptions, subscription items, invoices, invoice line items, customers, tax IDs, products, prices, coupons, promotion codes, payouts, balance transactions, checkout sessions and account events. You can start with a handful of pipelines and add more as new questions come up.
How often does the Stripe to SQL Server update run?▼
You choose the update schedule for each pipeline, from every 5 minutes to hourly, daily or another interval that fits your workflow. Faster schedules suit operational monitoring such as failed payments and dispute alerts, while daily runs are usually enough for financial close and cohort reporting.
What does the Stripe data look like inside SQL Server?▼
Each pipeline arrives as its own destination table with columns mapped to the Stripe fields, including identifiers, amounts, currencies, timestamps and statuses. Nested objects such as invoice line items or customer payment methods come through as separate pipelines, so you can join them on shared IDs like customer, invoice or charge.
Can I combine Stripe data with other sources in SQL Server?▼
Yes. Stripe records can be joined with internal order, CRM or ERP data already in SQL Server, and you can also send the combined result to Google Sheets for quick review or model it further in BigQuery. Many teams keep a curated reporting schema that mixes payment data with cost and customer tables.
Do I need to know SQL to set up Kondado with Stripe?▼
No. Setup happens in the Kondado interface: you pick the data source, enter your SQL Server connection details and choose pipelines. Writing queries only becomes relevant afterwards, when your analysts explore the data and build custom dashboards.
What Stripe metrics can I calculate once the data is in SQL Server?▼
You can build MRR and churn from the Subscriptions pipeline, net revenue and refund rates from Charges, Refunds and Balance transactions, dispute ratios from Disputes, and payout reconciliation from Payouts. Because the data lives in your own database, you can join it with internal cost and customer data and publish custom dashboards in Power BI.