- About Hevo
- Hevo Features
- Hevo System Architecture
- Core Concepts
- Free Trials
- Regulatory Compliance
- Hevo Support
- General FAQs
- Getting Started
- Creating an Account in Hevo
- Connection Options
- Familiarizing with the UI
- Creating your First Pipeline
- Data Loss Prevention and Recovery
- Data Ingestion
- Types of Data Synchronization
- Ingestion Modes and Query Modes for Database Sources
- Ingestion and Loading Frequency
- Ingestion Frequency and Data Synchronization
- Data Ingestion Statuses
- Deferred Data Ingestion
- Handling of Primary Keys
- Handling of Updates
- Handling of Deletes
- Hevo-generated Metadata
- Data Loading
- Loading Data in a Database Destination
- Loading Data to a Data Warehouse
- Optimizing Data Loading for a Destination Warehouse
- Manually Triggering the Loading of Events
- Scheduling Data Load for a Destination
- Loading Events in Batches
- Data Loading Statuses
- Data Spike Alerts
- Name Sanitization
- Table and Column Name Compression
- Parsing Nested JSON Fields in Events
- Data Flow in a Pipeline
- Familiarizing with the Pipelines UI
Working with Pipelines
- Best Practices for Creating Database Pipelines
- Creating a Pipeline
- Connectivity Check for RDBMS Sources
- Scheduling a Pipeline
- Modifying a Pipeline
- Prioritizing a Pipeline
- Viewing Pipeline Progress
- Pausing and Deleting a Pipeline
- Log-based Pipelines
- Troubleshooting Data Replication Errors
- Managing Objects in Pipelines
Python Code-Based Transformations
- Supported Python Modules and Functions
Transformation Methods in the Event Class
- Create an Event
- Retrieve the Event Name
- Rename an Event
- Retrieve the Properties of an Event
- Modify the Properties for an Event
- Fetch the Primary Keys of an Event
- Modify the Primary Keys of an Event
- Fetch the Data Type of a Field
- Check if the Field is a String
- Check if the Field is a Number
- Check if the Field is Boolean
- Check if the Field is a Date
- Check if the Field is a Time Value
- Check if the Field is a Timestamp
- Convert date string to required format
- Convert date to required format
- Convert datetime string to required format
- Convert epoch time to a date
- Convert epoch time to a datetime
- Convert epoch to required format
- Convert epoch to a time
- Get time difference
- Parse date string to date
- Parse date string to datetime format
- Parse date string to time
- Examples of Python Code-based Transformations
Drag and Drop Transformations
- Special Keywords
Transformation Blocks and Properties
- Add a Field
- Change Datetime Field Values
- Change Field Values
- Drop Events
- Drop Fields
- Find & Replace
- Flatten JSON
- Format Date to String
- Format Number to String
- Hash Fields
- Mask Fields
- Modify Text Casing
- Parse Date from String
- Parse JSON from String
- Parse Number from String
- Rename Events
- Rename Fields
- Round-off Decimal Fields
- Split Fields
- Examples of Drag and Drop Transformations
- Effect of Transformations on the Destination Table Structure
- Transformation Reference
- Transformation FAQs
- Python Code-Based Transformations
- Using Schema Mapper
- Mapping Statuses
- Auto Mapping Event Types
- Manually Mapping Event Types
- Modifying Schema Mapping for Event Types
- Schema Mapper Actions
- Fixing Unmapped Fields
- Resolving Incompatible Schema Mappings
- Resizing String Columns in the Destination
- Schema Mapper Compatibility Table
- Limits on the Number of Destination Columns
- File Log
- Troubleshooting Failed Events in a Pipeline
- Mismatch in Events Count in Source and Destination
- Activity Log
- Does creation of Pipeline incur cost?
- Why are my new Pipelines in trial?
- Can multiple Sources connect to one Destination?
- What happens if I re-create a deleted Pipeline?
- Why is there a delay in my Pipeline?
- Can I delete skipped objects in a Pipeline?
- Can I change the Destination post-Pipeline creation?
- How does changing the query mode affect data ingestion?
- Why is my billable Events high with Delta Timestamp mode?
- Can I drop multiple Destination tables in a Pipeline at once?
- How does Run Now affect scheduled ingestion frequency?
- Will pausing some objects increase the ingestion speed?
- Can I sort Event Types listed in the Schema Mapper?
- How do I include new tables in the Pipeline?
- Can I see the historical load progress?
- Why is my Historical Load Progress still at 0%?
- Why is historical data not getting ingested?
- How do I restart the historical load for all the objects?
- How do I set a field as a primary key?
- How can I load only filtered Events to the Destination?
- How do I ensure that records are loaded only once?
- Why do the Source and the Destination events count differ?
- Events Usage
- Free Sources
Databases and File Systems
- Data Warehouses
- Connecting to a Local Database
- Amazon DocumentDB
- Amazon DynamoDB
- Generic MongoDB
- MongoDB Atlas
- Support for Multiple Data Types for the _id Field
- Example - Merge Collections Feature
Errors During Pipeline Creation
- Error 1001 - Incorrect credentials
- Error 1005 - Connection timeout
- Error 1006 - Invalid database hostname
- Error 1007 - SSH connection failed
- Error 1008 - Database unreachable
- Error 1011 - Insufficient access
- Error 1028 - Primary/Master host needed for OpLog
- Error 1029 - Version not supported for Change Streams
- SSL 1009 - SSL Connection Failure
- Troubleshooting MongoDB Change Streams Connection
- Troubleshooting MongoDB OpLog Connection
- Errors During Pipeline Creation
- Amazon RDS SQL Server
- Azure SQL Server
- Google Cloud SQL Server
- Generic SQL Server
- Troubleshooting SQL Server
- SQL Server FAQs
- Amazon Aurora MySQL
- Amazon RDS MySQL
- Azure MySQL
- Google Cloud MySQL
- Generic MySQL
- MariaDB MySQL
Errors During Pipeline Creation
- Error 1003 - Connection to host failed
- Error 1006 - Connection to host failed
- Error 1007 - SSH connection failed
- Error 1011 - Access denied
- Error 1012 - Replication access denied
- Error 1017 - Connection to host failed
- Error 1026 - Failed to connect to database
- Error 1027 - Unsupported BinLog format
- Failed to determine binlog filename/position
- Schema 'xyz' is not tracked via bin logs
- Errors Post-Pipeline Creation
- Errors During Pipeline Creation
- MySQL FAQs
- Amazon Aurora PostgreSQL
- Amazon RDS PostgreSQL
- Azure PostgreSQL
- Google Cloud PostgreSQL
- Generic PostgreSQL
- Heroku PostgreSQL
Errors during Pipeline creation
- Error 1003 - Authentication failure
- Error 1006 - Connection settings errors
- Error 1011 - Access role issue for logical replication
- Error 1012 - Access role issue for logical replication
- Error 1014 - Database does not exist
- Error 1017 - Connection settings errors
- Error 1023 - No pg_hba.conf entry
- Error 1024 - Number of requested standby connections
- Errors Post-Pipeline Creation
- Errors during Pipeline creation
- PostgreSQL FAQs
- Troubleshooting Database Sources
- Amazon S3
- Azure Blob Storage
- FTP / SFTP
- Google Cloud Storage (GCS)
- Google Drive
- Google Sheets
- Android SDK
- Writing JSONPath Expressions
REST API FAQs
- Why does my REST API token keep changing?
- Can I use a bearer authorization token for authentication?
- Does Hevo’s REST API support API chaining?
- What is the maximum payload size returned by a REST API?
- How do I split an Event into multiple Event Types?
- How do I split multiple values in a key into separate Events?
- Jira Cloud
- Finance & Accounting Analytics
- Apple Search Ads
- Facebook Ads
- Facebook Page Insights
- Firebase Analytics
- Google Campaign Manager
- Google Ads
- Google Analytics
- Google Analytics 4
- Google Analytics 360
- Google Play Console
- Google Search Console
- Instagram Business
- LinkedIn Ads
- Microsoft Advertising
- Pinterest Ads
- SendGrid Webhook
- Salesforce Marketing Cloud
- Snapchat Ads
- TikTok Ads
- Twitter Ads
- YouTube Analytics
- Product Analytics
Sales & Support Analytics
- Help Scout
- Hub Planner
- Toggl Track
- From how far back can the Pipeline ingest data?
- Can I connect to a Source not listed in Hevo?
- Can I connect a local database as a Source?
- How can I push data to Hevo API?
- How do I connect a CSV file as a Source?
- Why are my selected Source objects not visible in the Schema Mapper?
- How can I transfer Excel files using Hevo?
- How does the Merge Table feature work?
- Familiarizing with the Destinations UI
- Amazon Aurora MySQL
- SQL Server
- Connecting to a Local Database
- Limitations of using MySQL as a Destination
- Structure of Data in the Amazon Redshift Data Warehouse
- Loading Data to an Amazon Redshift Data Warehouse
- Troubleshooting Amazon Redshift Destination
- Amazon Redshift FAQs
- Azure Synapse Analytics
- Clustering in BigQuery
- Partitioning in BigQuery
- Loading Data to a Google BigQuery Data Warehouse
- Near Real-time Data Loading using Streaming
- Troubleshooting Google BigQuery
- Google BigQuery FAQs
- Hevo Managed Google BigQuery
- Structure of Data in the Snowflake Data Warehouse
- Loading Data to a Snowflake Data Warehouse
- Troubleshooting Snowflake
- Snowflake FAQs
- Amazon Redshift
- Can I move data between SaaS applications using Hevo?
- Can I change the primary key in my Destination table?
- How do I change the data type of table columns?
- Can I change the Destination table name after creating the Pipeline?
- How can I change or delete the Destination table prefix?
- How do I resolve duplicate records in the Destination table?
- How do I enable or disable deduplication of records?
- Why does my Destination have deleted Source records?
- How do I filter deleted Events from the Destination?
- Does a data load regenerate deleted Hevo metadata columns?
- Can I load data to a specific Destination table?
- How do I filter out specific fields before loading data?
- How do I sort the data in the Destination?
- dbt™ Models
- Familiarizing with the Models UI
- Types of Models
- Key Features
- Working with SQL Models
- Previewing a Model
- Viewing the Query History
- Legacy Models
- Models FAQs
- Account Management
- Personal Settings
- Team Settings
- Pricing Plans
- Time-based Events Buffer
- Setting up Pricing Plans, Billing, and Payments
- On-Demand Purchases
- Billing Alerts
- Viewing Billing History
- Billing Notifications
- Can I try Hevo for free?
- Can I get a plan apart from the Starter plan?
- Are free trial Events charged once I purchase a plan?
- For how long can I stay on the Free plan?
- How can I upgrade my plan?
- Is there a discount for non-profit organizations?
- Can I seek a refund of my payment?
- Do ingested Events count towards billing?
- Will Pipeline get paused if I exceed the Events quota?
- Will the initial load of data be free?
- Does the Hevo plan support multiple Destinations?
- Do rows loaded through Models count in my usage?
- Is Hevo subscription environment-specific?
- Can I pause billing if I have no active Pipelines?
- Can you explain the pricing plans in Hevo?
- Where do I get invoices for payments?
- Account Suspension and Restoration
- Account Management FAQs
- Activate Concepts
- Familiarizing with the Activate UI
- Working with Activate
- Activate Warehouses
- Activate Targets
- Release Notes
- Release Version 2.13
- Release Version 2.12
- Release Version 2.11
- Release Version 2.10
- Release Version 2.09
- Release Version 2.08
- Release Version 2.07
- Release Version 2.06
- Release Version 2.05
- Release Version 2.04
- Release Version 2.03
- Release Version 2.02
- Release Version 2.01
- Release Version 2.00
- Release Version 1.99
- Release Version 1.98
- Release Version 1.97
- Release Version 1.96
- Release Version 1.95
- Release Version 1.93 & 1.94
- Release Version 1.92
- Release Version 1.91
- Release Version 1.90
- Release Version 1.89
- Release Version 1.88
- Release Version 1.87
- Release Version 1.86
- Release Version 1.84 & 1.85
- Release Version 1.83
- Release Version 1.82
- Release Version 1.81
- Release Version 1.80 (Jan-24-2022)
- Release Version 1.79 (Jan-03-2022)
- Release Version 1.78 (Dec-20-2021)
- Release Version 1.77 (Dec-06-2021)
- Release Version 1.76 (Nov-22-2021)
- Release Version 1.75 (Nov-09-2021)
- Release Version 1.74 (Oct-25-2021)
- Release Version 1.73 (Oct-04-2021)
- Release Version 1.72 (Sep-20-2021)
- Release Version 1.71 (Sep-09-2021)
- Release Version 1.70 (Aug-23-2021)
- Release Version 1.69 (Aug-09-2021)
- Release Version 1.68 (Jul-26-2021)
- Release Version 1.67 (Jul-12-2021)
- Release Version 1.66 (Jun-28-2021)
- Release Version 1.65 (Jun-14-2021)
- Release Version 1.64 (Jun-01-2021)
- Release Version 1.63 (May-19-2021)
- Release Version 1.62 (May-05-2021)
- Release Version 1.61 (Apr-20-2021)
- Release Version 1.60 (Apr-06-2021)
- Release Version 1.59 (Mar-23-2021)
- Release Version 1.58 (Mar-09-2021)
- Release Version 1.57 (Feb-22-2021)
- Release Version 1.56 (Feb-09-2021)
- Release Version 1.55 (Jan-25-2021)
- Release Version 1.54 (Jan-12-2021)
- Release Version 1.53 (Dec-22-2020)
- Release Version 1.52 (Dec-03-2020)
- Release Version 1.51 (Nov-10-2020)
- Release Version 1.50 (Oct-19-2020)
- Release Version 1.49 (Sep-28-2020)
- Release Version 1.48 (Sep-01-2020)
- Release Version 1.47 (Aug-06-2020)
- Release Version 1.46 (Jul-21-2020)
- Release Version 1.45 (Jul-02-2020)
- Release Version 1.44 (Jun-11-2020)
- Release Version 1.43 (May-15-2020)
- Release Version 1.42 (Apr-30-2020)
- Release Version 1.41 (Apr-2020)
- Release Version 1.40 (Mar-2020)
- Release Version 1.39 (Feb-2020)
- Release Version 1.38 (Jan-2020)
- Upcoming Features
Stripe is a payment gateway that facilitates payments (in person or online) by transferring money between a merchant account and a payment processor. It can be incorporated into websites and mobile applications and provides technical, fraud prevention and banking infrastructure to facilitate online payments.
For creating Pipelines using this Source, Hevo provides you a fully managed BigQuery data warehouse as a possible Destination. This option remains available till the time you set up your first BigQuery Destination irrespective of any other Destinations that you may have. With the managed warehouse, you are only charged the cost that Hevo incurs for your project in Google BigQuery. The invoice is generated at the end of each month and payment is recovered as per the payment instrument you have set up. You can now create your Pipeline and directly start analyzing your Source data. Read Hevo Managed Google BigQuery.
An active Stripe account with either Administrator or Developer role. Read Teams and user roles.
You are assigned the Team Administrator, Team Collaborator, or Pipeline Administrator role in Hevo to create the Pipeline.
Either a Restricted API Key or a Secret Key, which allows Hevo to read your Stripe data. Read Obtaining the API Key.
Obtaining the API Key
You may obtain a Restricted API Key or a Standard Secret API Key and share it with Hevo. The restricted API key allows you to select specific objects to give Hevo access to, whereas the standard secret key allows Hevo to access all objects without any restriction. If you have an Administrator or Developer role, your API keys are always available in the Stripe Dashboard. Read Stripe’s documentation on API keys.
Do one of the following:
Create a restricted API Key:
Log in to the Developer Dashboard.
Disable the Viewing test data option if it is enabled, to view live data.
In the API keys page, under the Restricted keys section, click Create restricted key.
Specify a unique name for this API Key. For example, Stripe connector for Hevo.
Under the PERMISSIONS column, select the Read permission corresponding to the following resource types:
All core resources
All Billing resources
All Checkout resources
All Orders resources
All Connect resources
All Issuing resources
All webhook resources
All Reporting resources
Scroll to the bottom of the page, and click Create key. You will be redirected to the API keys page.
Under the Restricted Keys section, click Reveal live key corresponding to the name of the API key that you just created, and copy it. This key is required while setting up a Pipeline in Hevo.
View the standard secret key:
Log in to the Developer Dashboard.
Disable the Viewing test data option if it is enabled, to view live data.
In the API keys page, under the Standard keys section, click Reveal live key, and copy it. This key is required while setting up a Pipeline in Hevo.
Configuring Stripe as a Source
Perform the following steps to configure Stripe as a Source in Hevo:
Click PIPELINES in the Navigation Bar.
Click + CREATE in the Pipeline List View page.
In the Select Source Type page, select Stripe.
In the Configure Your Stripe Source page, specify the following:
Pipeline Name: A unique name for your Pipeline, not exceeding 255 characters.
API Key: The API key that you obtained from your Stripe account.
Historical Sync Duration: The duration for which the existing data in the Source must be ingested. Default duration: 3 Months.
Note: If you select All Available Data, Hevo ingests all the data available in your Stripe account since January 01, 2010.
Click TEST & CONTINUE.
Proceed to configuring the data ingestion and setting up the Destination.
After you have specified the Stripe Source connection settings, as mentioned in the Configuring Stripe as a Source section above, select the objects to be ingested in the Select the Objects you want to replicate page, and click CONTINUE.
All the objects for ingestion are selected by default. You can deselect the objects you do not want to ingest. Hevo displays a warning if your Stripe restricted API key does not have the required permissions for the objects. All such objects can be found at the bottom of the objects list. Hevo displays the specific permission required for ingesting data when you hover over the warning icon.
To grant permissions in Stripe to ingest these objects, do the following:
Note: You need to have the Admin or Developer role in Stripe to view the API keys in your account.
Provide a different API key
To do this:
Click EDIT API KEY.
In the Configure your Stripe Source page, provide a different API key from your Stripe account that has the required permissions to access the objects.
Click TEST & CONTINUE.
Edit the existing API key in Stripe: You can edit your restricted API key in Stripe to provide the required permissions for Hevo to access the selected objects. After editing the API key, in the Select the Objects you want to replicate page, click REFRESH to see the updated list of objects that Hevo has access to. Read Stripe FAQs for steps to edit you existing API key.
In case you continue without providing the required permissions, the objects are not ingested and Hevo displays the PERMISSION DENIED message for these objects in the Pipeline Overview page.
|Default Pipeline Frequency||Minimum Pipeline Frequency||Maximum Pipeline Frequency||Custom Frequency Range (Hrs)|
|30 Mins||15 Mins||24 Hrs||1-24|
Note: The custom frequency must be set in hours, as an integer value. For example, 1, 2, 3 but not 1.5 or 1.75.
Historical Data: In the first run of the Pipeline, Hevo ingests historical data for all the objects using the Recent Data First approach. This enables you to have quicker access to your most recent data.
- For Pipelines created before Release 1.80: Hevo ingests historical data on the basis of the offset selected at the time of creating the Pipeline. Default duration: All available data.
- For Pipelines created after Release 1.80: You can select the historical sync duration at the time of creating the Pipeline. Default duration: 3 Months.
Note: The time taken to fetch the historical data depends on the number of days selected at the time of creating the Pipeline. Hevo defaults this period to 30 days. If required, you may customize it to any number or even select the starting date of your Stripe account.
Incremental Data: Once the historical load is complete, all new and updated records are synchronized with your Destination as per the Pipeline frequency. Hevo also fetches the Events object from Stripe, which tracks the updates and deletes made in the last 30 days, in order to sync the related Events with your Destination.
Updated and Deleted Objects
Hevo replicates the updated and deleted records using the Stripe
events object. For the deleted records, Hevo sets the
is_row_deleted column to True and the
deleted_timestamp column to the timestamp when the record was deleted in Stripe, in the ingested data and the Destination.
Hevo identifies the
updated and the
deleted records from the Stripe
events object and replicates that information for the following objects:
|Object Name||Event Type Tracked|
|Early Fraud Warning||
Note: As Hevo also replicates the deleted data now, you might see more Events in your Destination than in the Source.
Schema and Primary Keys
Hevo uses the following schema to upload the records in the Destination:
The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:
|Account||Contains all the properties of a Stripe account, such as its current email address and whether the account is enabled to make live charges.|
|Application Fee||Contains the transaction fee amount collected on top of a charge made for a user.|
|Application Fee Refund||Contains the reference to the application fee collected from the user and the portion of it to be refunded in case of a transfer reversal.|
|Authorization||Contains the information that must be approved for any purchase to be completed successfully from an issued card.|
|Balance transaction||Contains the details of funds moving through an account. It is created for every in-flow and out-flow of funds to and from your Stripe account. Read Balance transaction types.|
|Bank Account||Contains information of the bank accounts connected to the payment methods of the customers object.|
|Capability||Contains the details of the capabilities associated with a connected account. The level of information required for an account is determined by its capabilities.|
|Card||Contains details such as cardholder, and the month and year of expiry of the physical or virtual cards that are issued to the cardholders.|
|Cardholder||Contains information such as the name, email, and phone number of the individual or business entity who issues a card.|
|Charge||Contains the details of a charge made on a credit or a debit card. You can retrieve and refund individual charges as well as list all charges. They are identified by a unique, random ID.|
|Credit Note||Contains the adjusted or refunded amount to be added to an already finalized invoice instead of recreating the invoice.|
|Credit Note line item||Contains the individual adjustments or refunds that you are adding to a credit note associated with an invoice.|
|Customer||Contains the details of a customer, such as the name, email, default payment method and delinquency status.|
|Customer Balance Transaction||Contains the amount by which a customer’s account balance needs to be incremented or decremented.|
|Customer Tax IDs||Contains details of the tax ID(s) of a customer.|
|Coupon||Contains the information about a percent-off or amount-off discount you might want to apply to a customer. It can be applied to invoices or orders.|
|Discount||Contains the information such as the beginning and ending of the discount and the coupon object. It represents the actual application of a coupon to a particular customer.|
|Disputes||Contains details of customer disputes about charges they do not recognise, suspect may be fraud.|
|Dispute Balance Transaction||Contains the mapping between each dispute and transaction entities.
It is a custom table generated by Hevo to maintain data sanity.
|Early Fraud Warning||Contains details about early fraud warnings sent by the card issuer to Stripe for a transaction.|
|Events||Contains the details about the events generated by your Stripe account.|
|Fee Detail||Contains the detailed breakdown of fees paid for each transaction present in the balance transaction table.|
|File Link||Contains a URL that you can use to retrieve the contents of a file without any authentication.|
|Invoice||Contains the statements of amounts owed by a customer. Invoices are either generated one-off or periodically from a subscription.|
|Invoice Item||Contains the details about the charges or credits made to the customer’s credit cards.|
|Invoice Line Item||Contains the details of an invoice, such as amount, currency, period and proration. It is stored inside the invoice object.|
|Issue Disputes||Contains the details of the disputes raised by the customers to recover money for transactions completed using the Issuing API.|
|Mandates||Contains the details of the permissions given by the customer to debit their payment method.|
|Orders||Contains details of the customer’s purchases, such as products and quantities, order status, payment information, and billing and shipping information.|
|Payment Intent||Contains the guide for the process of collecting a payment from your customer during a particular session.
Read How intents work to know more about the payment flow followed at Stripe.
|Payment Link||Contains the URLs of pages that customers use to make payments.|
|Payment Method||Contains the details of the payment method that a customer has used on one or more payment intent(s) along with details. Supported Payment Methods are Card (card/wallet), FPX, and ideal.|
|Payment Method Details||Contains the detailed data for each payment method that is created on your Stripe Account, will be individually stored in your destination to maintain data sanity.
|Payout||Contains the details of the received funds from Stripe. It is created when you initiate a payout to either a bank account or debit card of a connected Stripe account.|
|Person||Contains the details of the person linked to a Stripe account.|
|Plan (pricing)||Contains the details such as the base price, currency and billing cycle for recurring purchases of products. It helps you track the pricing.|
|Price||Contains the details such as the unit cost, currency, and billing cycle for recurring and one-time purchases of the different products you offer to your customers. For example, a standard or premium version of your service.|
|Product||Contains a list of all offers for the product. Each product can have multiple tiers of pricing plans.|
|Promotion Code||Contains a customer-redeemable code that can be used to create single or multiple codes for a coupon.|
|Quote||Contains the details of the quotation document provided to the customer for certain products or services. A quote is a document that contains a fixed price of a product.|
|Refund||Contains the details of a charge that is to be refunded due to a dispute, return, or failure to deliver a service.|
|Review||Contains human-added information to supplement automated fraud detection cases.|
|Sessions||Contains the details of the customer’s session when they pay for one-time purchases or subscriptions.|
|Setup Attempts||Contains the details of the attempts at setting up a payment method by the customers.|
|Setup Intent||Contains the guide for the process of saving a customer’s payment credentials for future payments.|
|Shipping Rates||Contains the details of the shipping rates applied to products being delivered to the customers.|
|Source||Contains the details of a customer’s payment methods that can be used with the Stripe API.|
|Subscription||Contains the details of a recurring charge for a customer. Each subscription has multiple line items.|
|Subscription Item||Contains line item data for each subscription. Each line item is associated with a plan.|
|Subscription Schedule||Contains the attributes required to manage the lifecycle of customers’ subscriptions by predefining existing changes.|
|Tax Code||Contains the details of the tax codes used to classify the goods and services for tax purposes.|
|Tax Rate||Contains the details of the tax rates applied to the invoices, subscriptions, and checkout sessions to collect tax.|
|Tokens||Contains the details of the tokens used by Stripe to collect sensitive customer information such as bank accounts and credit cards.|
|Top-Up||Contains the amount by which customers wish to top up their Stripe account balance.|
|Transaction||Contains details of funds entering or leaving a Stripe account. A transaction object is created whenever an issued card is used for making a purchase or a refund.|
|Transfer||Contains the details to move funds between Stripe accounts such as amount, destination and so on. It is used when you need to directly move a fund from your customer to the seller who’s offering the service through your platform.|
|Transfer Reversal||Contains the amount that is to be deducted from the seller’s account (who originally received it via a successful transfer) and added back to your platform.|
|Usage Record||Contains a report of a customer’s usage and other metrics that are sent to Stripe.|
|Value||Contains the details of the values in a value list, for example, an email ID. Value lists group values together so that they can be referenced in rules. For example, a value list containing email addresses can be referenced for the rule that blocks any payment with the email address on this list.|
|Value List Item||Contains the details of the items that can be added to a Stripe Radar value list that is used for fraud prevention.|
|Verification Report||Contains the details of the data of your users while collecting and verifying their identities.|
|Verification Sessions||Contains the details of the processes you need to follow for collecting and verifying the identities of your users, and the verified data after the verification is complete.|
Read the detailed Hevo documentation for the following related topics:
Stripe informs the user of a change in an object in their account through an event. For example, when a charge succeeds, it creates a charge.succeeded event. Stripe maintains a record of all the events that it created for the past 30 days in an Events object. Hevo refers to this Events object while replicating the data to the Destination to make sure all the deletes and updates are duly accounted for.
Make sure to select Stripe’s Events object while creating your Pipeline, else, Hevo will not be able to capture any updates. To enable Hevo to capture deletes for your Pipeline, you need to contact Hevo Support.
Pausing a Pipeline for more than 30 days can lead to a loss of data, as the
eventsobject tracks updates and deletes of the past 30 days only.
- For new and existing Pipelines, Hevo replicates only the data that has been deleted after Release 1.86.
Refer to the following table for the list of key updates made to this page:
|Date||Release||Description of Change|
|Feb-20-2023||NA||Updated section, Configuring Stripe as a Source to update the information about historical sync duration.|
|Dec-07-2022||1.99||- Updated section, Updated and Deleted Objects to add new objects in the list for which Hevo supports replication of updated and deleted records.
- Updated section, Data Replication to reorganize the content for better understanding and coherence.
|Sep-21-2022||1.98||Updated sections, Schema and Primary Keys, and Data Model to add information about the new Stripe objects supported by Hevo.|
|Aug-24-2022||1.96||Added section, Object Selection.|
|Jul-27-2022||NA||- Renamed section, Creating the API Key to Obtaining the API Key.
- Updated section, Obtaining the API Key to include information about standard and restricted API keys.
|Apr-11-2022||1.86||- Updated the Data Replication and Source Considerations sections to add information about how Hevo handles deletes in Stripe objects.|
|Mar-07-2022||1.83||Added information about reverse historical load in the Data Replication section.|
|Jan-24-2022||1.80||Added information about configurable historical sync duration in the Data Replication section.|
|Jan-03-2022||1.79||Added objects to section, Data Model.|
|Oct-25-2021||NA||Added the Pipeline frequency information in the Data Replication section.|
|Aug-23-2021||1.70||Added the section, Source Considerations.|