Stripe is an online payment processing platform.
Featureslink
| Feature Name | Supported | Notes |
|---|---|---|
| Capture deletes | check | BANK_ACCOUNT, CARD, COUPON, CUSTOMER, INVOICE, INVOICE_ITEM, PERSON, PLAN, PRODUCT, and SKU tables. |
| Custom data | ||
| Data blocking | check | Column level and table level |
| Column hashing | check | |
| Re-sync | check | Table level |
| History | check | ORDER, SUBSCRIPTION, and SUBSCRIPTION_ITEM tables. |
| API configurable | check | |
| Priority-first sync | ||
| Private networking | ||
| Fivetran data models | check | Get the models: source / transform |
Setup guidelink
Follow our step-by-step Stripe setup guide to connect Stripe with your destination using Fivetran connectors.
Schema informationlink
This schema applies to all Stripe connections created after March 25, 2019.
To zoom, open the ERD in a new window.Schema noteslink
The CARD table does not include credit card number or CVV code data. Instead, the fingerprint column contains Stripe-provided hashes that uniquely identify each card number. You can use this column to check if two customers who’ve signed up are using the same card number.
Connected Accountslink
Fivetran support syncing Connected Accounts for the following endpoints:
- Events
- Charges
- Payouts
- Balance Transaction
- Apple Domain
- Refunds
- Disputes
- Payment Intent
- Issuing Card
- Issuing Dispute
In the connector setup form, set the Sync Connected Accounts toggle to ON.
We populate the connected_account_id column for the supported tables.
NOTE: If you enable this feature during a sync, we re-sync the tables.
Syncing empty tables and columnslink
Fivetran can sync empty tables and columns for your Stripe connector.
We create a table in the destination even if we can’t retrieve the source table data from Stripe. For more information, see our Features documentation.