Most businesses using HubSpot and Stripe have both tools doing important work, but working separately. Sales quotes live in HubSpot. Payment processing happens in Stripe. Revenue data sits in Stripe dashboards. The follow-up sequences are in HubSpot. Connecting the two changes that: payment events trigger workflows, revenue data appears on contact and deal records, and the gap between CRM activity and billing reality closes.
There are two distinct ways to connect HubSpot and Stripe, and confusing them is the most common mistake teams make when setting up the integration. This guide covers both paths clearly, including when to use each, how to set them up, and what data flows where.
Understanding The Two Integration Paths
Path One: Stripe As Payment Processor
The first integration path connects Stripe as the payment processor for HubSpot's Commerce tools. HubSpot's Commerce Hub includes quotes, invoices, payment links, and subscriptions. By default, HubSpot can process payments through HubSpot Payments (available in the US, UK, and Canada). If you are outside those regions, or if you already have a Stripe account you want to keep using, connecting Stripe as the processor lets you use HubSpot's Commerce tools with Stripe handling the actual payment collection.
In this path, HubSpot is the source of truth for the transaction initiation. You create a quote or invoice in HubSpot, the customer pays through a Stripe-powered checkout, and the payment confirmation flows back into HubSpot.
Path Two: Stripe Data Sync
The second integration path uses HubSpot's Data Sync app (available in the HubSpot Marketplace) to synchronise existing Stripe data into HubSpot. This is relevant for businesses that already process payments and manage subscriptions in Stripe and want that data visible in HubSpot without rebuilding their payment infrastructure.
In this path, Stripe is often the source of truth for billing data. Customer records, invoices, products, subscriptions, and payment transactions in Stripe are mapped to corresponding objects in HubSpot and synced on an ongoing basis.
These two paths are not mutually exclusive. Some teams use Stripe as the processor for HubSpot Commerce transactions and also run Data Sync to bring in historical billing data from Stripe. Others use only one path depending on their setup.
HubSpot Payments vs. Stripe Processing
If you are in the US, UK, or Canada and do not have an existing Stripe account, HubSpot Payments is the simpler path. If you are already using Stripe or operate in a region where HubSpot Payments is not available, connecting Stripe as the processor is the right choice.
Prerequisites And Requirements
HubSpot Plan And Permissions
Connecting Stripe as a payment processor requires access to HubSpot's Commerce tools, which are available across plans but with varying feature depth. Payment links are available on most plans. Invoices and quotes with payment collection are available on Starter and above. Subscriptions and more advanced Commerce Hub features require Professional or Enterprise.
Setting up the Stripe Data Sync app requires Operations Hub Starter or above for basic sync, and Operations Hub Professional for custom field mappings beyond the default set.
You need Super Admin or a role with connected apps permissions to install and configure either integration.
Stripe Account Requirements
For the payment processor connection, you need an active Stripe account in good standing. HubSpot connects to one Stripe account per portal. If your business runs multiple Stripe accounts (for different entities or regions), only one can be connected natively at a time.
For the Data Sync path, the same requirement applies: one Stripe account per HubSpot portal in the native sync.
Regional Considerations
Stripe payment processing through HubSpot is available in the countries where Stripe operates, which covers most of North America, Europe, Asia-Pacific, and Latin America. This is broader than HubSpot Payments' current geographic support. If you are outside the US, UK, and Canada, Stripe processing is typically the only native payment option in HubSpot.
How To Connect Stripe As A Payment Processor
Step 1: Access Payment Settings
In HubSpot, go to Settings (gear icon), then Commerce, then Payment Processing. You will see the option to connect a payment processor. If HubSpot Payments is already active, you will need to review whether switching to Stripe processing is appropriate (the migration section below covers this).
Step 2: Select Stripe And Authorise
Click Connect Stripe. HubSpot redirects you to Stripe's OAuth authorisation page. Log in to your Stripe account and authorise HubSpot's access. You will be returned to HubSpot once authorisation is complete.
HubSpot requires read and write access to your Stripe account for the payment processor connection. Review the permissions being requested before authorising.
Step 3: Verify The Connection
After authorisation, HubSpot displays a confirmation that Stripe is connected. Verify the connection by checking that your Stripe account name appears in the payment settings. Run a test transaction using Stripe's test mode before accepting live payments.
Step 4: Configure Payment Methods
In the payment settings, configure which payment methods to accept: cards, ACH direct debit, SEPA, and other methods available in your region through Stripe. The available methods depend on your Stripe account settings and the countries you are collecting payments in.
Step 5: Use Stripe With Commerce Tools
With Stripe connected, you can:
- Payment links: create a payment link in HubSpot that generates a Stripe-powered checkout page
- Quotes: add a payment collection step to a HubSpot quote, processed through Stripe
- Invoices: send HubSpot invoices with a Stripe payment option for the recipient
- Subscriptions: create recurring billing subscriptions in HubSpot, processed through Stripe
Payments collected through these tools are recorded in HubSpot on the associated contact and deal records, giving sales and finance teams visibility without leaving the CRM.
How To Set Up Stripe Data Sync
Step 1: Install The Stripe Data Sync App
In HubSpot, go to the App Marketplace (Marketplace icon in the top navigation). Search for "Stripe Data Sync." Install the official Stripe Data Sync app published by HubSpot. This is a separate app from the Stripe payment processor connection.
During installation, you will be prompted to authorise the connection to your Stripe account via OAuth. Authorise the access and return to HubSpot.
Step 2: Configure Object Mappings
After installation, configure which Stripe objects sync to which HubSpot objects. The default mappings are:
The customer-to-contact sync is bi-directional by default: changes in HubSpot contact properties (name, email, phone) can sync back to Stripe customer records, and changes in Stripe sync to HubSpot. All other objects typically sync one-way from Stripe into HubSpot.
Step 3: Custom Field Mappings
Default field mappings cover the most common data points. For custom fields (a Stripe metadata field you want mapped to a specific HubSpot contact property, for example), Operations Hub Professional is required. In Operations Hub, go to Data Sync, select the Stripe connection, and add custom field mappings to the relevant object sync.
Step 4: Enable Historical Sync
During setup, choose whether to sync historical data from Stripe. For a new integration, syncing 12 months of historical customer and invoice data gives your HubSpot contact records meaningful billing context from day one. For large Stripe accounts, the initial historical sync may take several hours.
What Data Syncs And What Does Not
What Syncs
- Stripe customers sync as HubSpot contacts (matched by email address)
- Stripe invoices sync as invoice records in HubSpot
- Stripe products sync to the HubSpot product library
- Payment transactions sync and are visible on contact timelines
- Subscription status and plan information syncs to contact properties or custom objects
What Does Not Sync Automatically
- Stripe payment method details (card numbers, bank account details) do not sync and should not be stored in a CRM
- Coupon and discount objects are not natively synced in the default mapping
- Complex subscription modifications (mid-cycle upgrades, downgrades with proration) may not map cleanly without custom configuration
- Refund records require verification: check current app documentation for refund sync status as this has changed across versions
Handling Subscriptions
Subscription data is one of the more complex sync scenarios. In the native integration, subscription status (active, past due, cancelled, trialing) and basic plan information sync to HubSpot contact properties or as a custom object depending on your configuration. For SaaS businesses where subscription lifecycle is a primary CRM workflow driver, review the current mapping documentation carefully before relying on subscription data in workflows.
For teams building subscription management workflows in HubSpot, the subscription sync is most reliable when HubSpot's native subscription tool (Commerce Hub) is used for subscription creation, with Stripe as the processor. Syncing externally-created Stripe subscriptions into HubSpot is functional but requires more configuration.
Using The Integration For Revenue Operations
Accepting Payments Via Quotes And Payment Links
Payment links created in HubSpot generate a Stripe-powered checkout URL that can be shared via email, embedded on a page, or included in a quote. The link includes the product, price, and any subscription terms defined in HubSpot. When the customer pays, HubSpot records the payment on the associated deal and contact.
For teams with a Webflow site connected to HubSpot, payment links can be embedded or linked from Webflow pages with form submissions routed to HubSpot contacts. Our guide on the Webflow and HubSpot integration covers how contact data flows from Webflow into HubSpot, which is the foundation for payment link personalisation and post-payment workflow automation.
Automating Follow-Ups On Payment Events
HubSpot workflows can trigger on payment events including payment received, payment failed, subscription created, and subscription cancelled. Common automation patterns:
- Payment received → enrol contact in onboarding sequence, update lifecycle stage to Customer, notify account owner
- Payment failed → trigger a dunning sequence, create a task for the account manager, send a payment retry link
- Subscription cancelled → enrol in win-back sequence, update deal stage, alert customer success team
These automations close the loop between billing events and CRM actions without manual intervention.
Revenue Reporting
With Stripe data synced and payment transactions recorded in HubSpot, revenue reporting becomes available within the CRM. Custom reports can show revenue by contact, by deal, by product, and by time period. For teams running HubSpot services that include Commerce Hub setup and revenue reporting, the Stripe integration is often the first step in building a unified revenue view inside the CRM.
Migration Options
Migrating From Stripe Processing To HubSpot Payments
Teams in the US, UK, or Canada who connected Stripe initially and want to move to HubSpot Payments can migrate. The process involves disconnecting Stripe as the processor, enabling HubSpot Payments, and updating any active payment links or invoice templates.
Active subscriptions created under Stripe processing do not automatically migrate. New subscriptions can be created under HubSpot Payments. Existing Stripe subscriptions typically need to be managed through their natural renewal cycle before migrating, or cancelled and recreated under HubSpot Payments.
Migrating Stripe Subscriptions To HubSpot
For businesses moving from Stripe-native subscription management to HubSpot Commerce subscriptions processed through Stripe, the most reliable approach is:
- Keep existing Stripe subscriptions active until their next renewal
- At renewal, recreate the subscription in HubSpot with Stripe as the processor
- Cancel the original Stripe-native subscription after the HubSpot version is active
Migrating subscriptions mid-cycle requires careful handling of proration and billing dates. Test the process with a small number of subscriptions before migrating at scale.
Best Practices And Common Pitfalls
Choose The Right Path Before Building
Decide whether you need payment processing, data sync, or both before connecting anything. Building on the wrong path creates technical debt that is harder to undo than starting with the right setup.
If your primary goal is accepting payments inside HubSpot: connect Stripe as the payment processor. If your primary goal is seeing Stripe billing data in HubSpot for reporting and workflow purposes: install the Data Sync app. If you need both: start with the processor connection, then add Data Sync.
Test Before Going Live
Use Stripe's test mode for the initial connection. HubSpot's Commerce tools respect Stripe's test mode, so you can run the full payment flow (quote creation, payment link, checkout, confirmation) with test card numbers before processing real payments. Do not skip this step.
Monitor Sync Health
The Data Sync app has a sync health dashboard in HubSpot showing the status of recent sync operations, records that failed to sync, and error messages for failed syncs. Review this dashboard weekly during the first month after setup and monthly thereafter. Sync failures are usually caused by missing required fields in the source record or duplicate matching issues on email address.
One Account Limitation
The native integration supports one Stripe account per HubSpot portal. If your business structure requires multiple Stripe accounts, you will need a custom integration (via Zapier, Make, or direct API) or a third-party sync tool to handle the additional account. Plan your architecture around this limitation before connecting.
Advanced Options And Alternatives
Third-Party Sync Tools
For businesses that need deeper bi-directional sync, MRR and ARR tracking within HubSpot, or connections to multiple Stripe accounts, third-party tools like ClearSync, Stacksync, and Chargebee (for subscription management) extend what the native integration can do. These add cost and a third-party dependency but solve use cases the native integration does not cover.
Custom API Integration
For engineering teams comfortable with APIs, both HubSpot and Stripe have well-documented APIs. A custom integration can map any Stripe object to any HubSpot object, handle complex subscription scenarios, and maintain sync logic tailored to your specific business model. This is the highest-effort option but the most flexible.
Getting Started Checklist
Before connecting HubSpot and Stripe:
- Confirm which integration path you need (payment processor, data sync, or both)
- Confirm your HubSpot plan supports the Commerce features you need
- Confirm your Stripe account is in good standing and in a supported region
- Identify which Stripe account to connect (only one is supported natively)
- Enable Stripe test mode before running any live transactions
- Review default object mappings and identify any custom field mappings needed
- Test the full payment flow (quote or payment link → checkout → confirmation → HubSpot record update) before going live
- Set up payment event workflows (payment received, payment failed, subscription events)
- Schedule a sync health review after the first week of live operation
For teams that want help designing the full commerce and CRM architecture, take a look at our work to see how we connect these systems, or get started with a conversation about your current setup.
FAQs
How Do I Connect Stripe To HubSpot?
Go to Settings, then Commerce, then Payment Processing. Select Stripe and complete the OAuth authorisation with your Stripe account credentials. For data sync, install the Stripe Data Sync app from the HubSpot App Marketplace and authorise the connection separately.
What Is The Difference Between Stripe Payment Processing And Stripe Data Sync In HubSpot?
Stripe payment processing connects Stripe as the payment method for HubSpot's Commerce tools (quotes, invoices, payment links, subscriptions). Stripe Data Sync brings existing Stripe data (customers, invoices, subscriptions, products) into HubSpot through an ongoing synchronisation. They serve different purposes and can be used independently or together.
Does The HubSpot Stripe Integration Sync Both Ways?
For the payment processor connection: no, it is primarily HubSpot-initiated transactions recorded back in HubSpot. For the Data Sync app: customer-to-contact sync is bi-directional by default. Other objects (invoices, products, subscriptions, transactions) sync one-way from Stripe into HubSpot.
Can I Use My Existing Stripe Account With HubSpot?
Yes. Both the payment processor connection and the Data Sync app connect to an existing Stripe account via OAuth. Only one Stripe account can be connected per HubSpot portal natively.
What Data Syncs From Stripe To HubSpot?
Via Data Sync: customers (to contacts), invoices, products, subscriptions, and payment transactions. The exact fields within each object depend on default and custom mappings. Some objects require Operations Hub Professional for custom field mapping beyond the defaults.
Is Stripe Payment Processing Available Globally In HubSpot?
Stripe processing through HubSpot is available in the countries where Stripe operates, which is significantly broader than HubSpot Payments (US, UK, Canada only). Check Stripe's current country availability for the specific payment methods relevant to your customers.
Do I Need A Specific HubSpot Plan For The Stripe Integration?
Basic payment processing is available across most HubSpot plans. Specific Commerce features (subscriptions, full invoice management) require Professional or Enterprise. The Data Sync app requires Operations Hub Starter for default mappings and Operations Hub Professional for custom field mappings.
What Are The Limitations Of The Native Integration?
The native integration supports one Stripe account per portal. Complex subscription modifications (mid-cycle changes, proration) may not sync cleanly. Refund records and coupon objects are not fully synced in default configurations. For multi-account setups or complex subscription management, a third-party tool or custom API integration is required.
A Note On Sources
Feature descriptions, setup steps, and object mapping information in this article reflect HubSpot's and Stripe's published integration capabilities as of mid-2026. Both HubSpot and Stripe update their integration features, object mappings, and regional availability regularly. Verify current setup steps, supported objects, and plan requirements at knowledge.hubspot.com and the HubSpot App Marketplace before configuring your integration.
Sync direction information (bi-directional vs. one-way) reflects the native app's default configuration at the time of writing. Custom field mapping behaviour and sync directions can change with app updates. Review the current Stripe Data Sync app listing in the HubSpot Marketplace for the most current mapping documentation.
HubSpot Payments regional availability (US, UK, Canada) reflects published availability as of mid-2026 and may expand. Verify current regional support at hubspot.com/products/commerce before making platform decisions based on geographic availability.
HubSpot and Stripe are independent platforms. Belt Creative has no commercial relationship with either company. Platform mentions are for informational purposes only and do not constitute an endorsement.