Stripe

Stripe is a payment processing platform that allows merchants of all types to accept credit cards and integrate almost any type of payment processing into a third-party application using its robust Application Programming Interfaces (APIs). Replicating Stripe data to your warehouse lets you analyze revenue, payouts, refunds, disputes, customers, invoices and subscriptions alongside your other business data.

Setup Instructions

Follow the setup steps guide for configuring your Stripe connection to enable data to flow into your destination via DLH.

Supported Features

Here are key features supported for this connector.

If you have any questions about these supported features please reach out to our Customer Support team.

Details on Sync Processing

• Created date filter: every table is read with a created date filter. The first synchronization reads from the Historical Start Date, or up to 2 years back when none is set. Later runs read only what was created since the previous run, with a lookback to cover any clock drift between runs.
• Edits after creation: an object edited after it was created (for example a charge disputed later, or an invoice paid later) is not re-read by this filter alone. A periodic historical re-sync picks those up.
• Deleted rows: a manual re-sync of a top level table reads its complete current set, and rows missing from that pull are marked as deleted in the target. Child tables (read per parent record) and ACCOUNT and PAYMENT_LINK are not part of this.
• Child tables: tables such as line items, persons and bank accounts are read once for each parent record that was read.
• Always read whole: ACCOUNT and PAYMENT_LINK have no created date filter and are read whole on every run.
• Issuing: AUTHORIZATION, CARDHOLDER, CARD, TRANSACTION and ISSUING_DISPUTE (Stripe Issuing data) are unchecked by default since most Stripe customers only process payments and do not issue cards. Check them in the schema editor if you do.
• Rate limits: requests are paced well within Stripe's live mode limits, and rate limited responses are retried after the wait time Stripe returns.
• Read only: DLH.io never writes to Stripe.

Issue Handling

If any issues occur with the connection simply return to the sources page in DLH.io, edit the source details and click the Save & Test button to confirm connectivity. If any issues persist please contact our support team via the DLH.io Support Portal.

Replicated Entities

The following entities are replicated by default to your Target Connection. These are the table names you will see in your Target Connection. If you believe any entities/tables are missing please open a ticket with Customer Support:

Account and money movement

Account, payouts, transfers, top-ups, balance transactions and application fees.

• ACCOUNT
• PERSON
• BANK_ACCOUNT
• PAYOUT
• TRANSFER
• TRANSFER_REVERSAL
• TOPUP
• BALANCE_TRANSACTION
• FEE
• APPLICATION_FEE
• APPLICATION_FEE_REFUND

Charges and disputes

Charges, refunds, disputes and fraud signals.

• CHARGE
• REFUND
• DISPUTE
• DISPUTE_BALANCE_TRANSACTION
• EARLY_FRAUD_WARNING
• REVIEW

Customers

Customers and their balance, discounts, sources and payment methods.

• CUSTOMER
• CUSTOMER_BALANCE_TRANSACTION
• CUSTOMER_DISCOUNT
• SOURCE
• PAYMENT_METHOD

Invoicing

Invoices, credit notes, coupons and tax rates.

• INVOICE
• INVOICE_LINE_ITEM
• INVOICE_ITEM
• CREDIT_NOTE
• CREDIT_NOTE_LINE_ITEM
• COUPON
• TAX_RATE
• TAX_RATE_INVOICE_ITEM_MAPPING

Subscriptions and catalog

Subscriptions, prices, products and plans.

• SUBSCRIPTION
• SUBSCRIPTION_ITEM
• SUBSCRIPTION_SCHEDULE
• TAX_RATE_SUBSCRIPTION_MAPPING
• PRICE
• PRODUCT
• PLAN
• TIER
• USAGE_RECORD

Payments

Payment intents, setup intents, files, checkout sessions and payment links.

• PAYMENT_INTENT
• SETUP_INTENT
• FILE
• FILE_LINK
• CHECKOUT_SESSION
• PAYMENT_LINK

Issuing

Stripe Issuing data. Unchecked by default; check these in the schema editor if you issue cards.

• AUTHORIZATION
• CARDHOLDER
• CARD
• TRANSACTION
• ISSUING_DISPUTE

Schema Details (ER Diagram)

This entity relationship diagram (ERD) provides you with information about what entities/tables DLH provides for you out-of-the-box and how they are related to one another.

View Interactive ERD