HubSpot Payment Gateway Integration: Every Option Compared (2026)

HubSpot Commerce Hub ships with HubSpot Payments as the default gateway — but it's not the only option. Native integrations with Stripe and GoCardless cover the most common alternatives, the HubSpot App Marketplace has 30+ payment connectors, and multi-PSP orchestrators sit on top of all of them.

The question "what payment gateway should I use with HubSpot" has different answers depending on what you're optimising for: lowest transaction fees, broadest payment method support, international currency coverage, existing PSP relationships, or simplest setup. This guide covers every workable HubSpot payment gateway option in 2026, what each unlocks, and how to pick.

Quick Answer

• Native HubSpot gateways: HubSpot Payments (default), Stripe, GoCardless (in supported regions).

• HubSpot App Marketplace gateway connectors: PayPal, Square, Authorize.Net, Adyen, Worldpay, Braintree, Checkout.com, Mollie, plus 20+ regional / niche providers.

• Multi-PSP orchestrators: Shuttle, Primer, Gr4vy, Spreedly — sit above multiple gateways, route per transaction.

• Cheapest setup: HubSpot Payments (built-in, no configuration).

• Cheapest transaction cost at volume: Direct PSP relationship via a multi-PSP orchestrator (you keep negotiated rates).

• Best for most US/UK SMBs: HubSpot Payments or HubSpot + Stripe native.

• Best for cross-border B2B: Multi-PSP orchestrator with HubSpot integration.

What HubSpot Calls a "Payment Gateway"

HubSpot uses "payment gateway", "payment integration", and "payment processor" somewhat interchangeably — but they're different layers of the stack.

Payment gateway: The piece that captures card details (or other payment method) on the checkout page and securely transmits them to the processor for authorisation. Examples in HubSpot context: Stripe Checkout, HubSpot Payments hosted checkout, PayPal's checkout iframe.

Payment processor / acquirer: The bank-adjacent entity that routes the authorisation to card networks and settles funds. Examples: Stripe (gateway + processor), Adyen (gateway + processor), Worldpay (processor), Chase Merchant Services (acquirer).

Payment orchestrator: Sits above multiple gateways/processors and routes transactions across them. Examples: Shuttle, Spreedly, Primer, Gr4vy.

HubSpot Commerce Hub's "payment integration" is really about the gateway layer — what captures the payment on your behalf. The processor underneath is determined by which gateway you choose. This guide uses "gateway" loosely (matching HubSpot's terminology) but each section is explicit about which layers are involved.

Tier 1: Native HubSpot Gateway Integrations

Three gateways are integrated natively into HubSpot Commerce Hub — meaning HubSpot built and maintains the integration, and the gateway shows up directly in Commerce Hub settings rather than as a third-party app.

HubSpot Payments

The default. HubSpot is the merchant of record, processing transactions through their underlying processor agreement.

• **Rates:** 2.9% + $0.30 (US cards), 1.9% + £0.20 (UK), 0.5% capped at $5 (ACH, US only). See HubSpot Commerce Hub transaction fees for the full breakdown.

• Currencies: USD, GBP, EUR, CAD, AUD only.

• Setup: Zero config — built into Commerce Hub.

• Best for: SMBs in supported markets with simple invoicing needs and low international exposure.

• Worst for: International merchants, high-volume B2B, anyone with an existing PSP relationship.

Stripe (native HubSpot integration)

HubSpot has a deep native Stripe integration that routes Commerce Hub payment links to your Stripe account instead of HubSpot Payments.

• Rates: Your direct Stripe rates (2.9% + $0.30 US standard, often lower with volume). No HubSpot markup.

• Currencies: 135+ via Stripe's coverage.

• Local payment methods: Apple Pay, Google Pay, Klarna, Affirm, iDEAL, Bancontact, SEPA, BACS, and ~40 others depending on region.

• Setup: Connect Stripe in Settings → Commerce → Connected accounts. 5-10 minutes.

• Best for: Teams already on Stripe who want CRM-attached payment links without HubSpot Payments' markup.

• Trade-offs: Single-PSP — you can't route across multiple processors. Stripe-branded checkout by default.

GoCardless (native HubSpot integration, supported regions)

GoCardless handles bank-to-bank direct debit — BACS (UK), SEPA (EU), ACH (US, in beta), PAD (Canada).

• Rates: ~1% of transaction value, capped (varies by region and plan).

• Best for: Recurring B2B billing, subscriptions where customers prefer direct debit over cards, high-value invoices where 1% beats 2.9%.

• Trade-offs: Direct debit takes 3-5 working days to clear (cards are instant). Doesn't replace card acceptance — sits alongside.

Combined native setup

Many HubSpot teams run all three:

• HubSpot Payments for one-off invoices and SMB customers

• Stripe for ecommerce-style checkout with local payment methods

• GoCardless for recurring B2B subscriptions

HubSpot Commerce Hub Pro+ supports multiple connected payment accounts simultaneously, with different gateways selected per workflow or deal type.

Tier 2: HubSpot App Marketplace Gateway Connectors

Beyond the natively integrated gateways, the HubSpot App Marketplace hosts 30+ payment connectors built by gateway providers or third-party developers. Quality varies — read reviews and check the install count before committing.

Strong marketplace connectors:

• PayPal — official PayPal app, handles PayPal Checkout, Venmo (US), PayPal Pay Later.

• Square — for HubSpot users with existing Square POS.

• Authorize.Net — common for US merchants on traditional acquirer relationships.

• Adyen for HubSpot — for enterprise merchants using Adyen as primary processor.

• Worldpay — UK merchant accounts via Worldpay (FIS).

• Braintree — owned by PayPal, often used for marketplace-style platforms.

• Checkout.com — strong for cross-border merchants in EMEA.

• Mollie — European focus, strong local payment method support.

Regional / niche:

• Razorpay (India), MercadoPago (LATAM), Paystack (Africa), iyzico (Turkey), PayMongo (Philippines), PayU (LATAM/India/Africa), and more.

What marketplace connectors typically do:

• Generate payment links from HubSpot triggers

• Embed checkout iframes in HubSpot CMS pages

• Send payment status back to HubSpot via webhook

• Attach payment data to deals/contacts

What they typically don't do:

• Replace HubSpot Payments entirely on the native payment link feature

• Route across multiple gateways (single-PSP only)

• Provide white-label / your-domain checkout

For most HubSpot teams, marketplace connectors are how you add support for a payment method or processor that isn't natively integrated. They sit alongside HubSpot Payments rather than replacing it.

Tier 3: Multi-PSP Orchestrators (Beyond Single-Gateway)

The third pattern: instead of picking one gateway, sit a payment orchestrator above multiple gateways and route each transaction to the best processor for that specific transaction's characteristics (currency, country, card BIN, transaction value).

What an orchestrator does in a HubSpot stack:

• Sits between HubSpot Commerce Hub and 40+ underlying gateways (Stripe, Adyen, Worldpay, Braintree, regional processors)

• HubSpot workflow generates a payment link via the orchestrator's API

• Orchestrator picks the best processor per transaction (lowest fees, best decline rates, local acquiring)

• Customer pays on a white-label checkout (your domain, your branding)

• Webhook returns to HubSpot with full transaction data

Examples of orchestrators with HubSpot integration paths:

• Shuttle — 40+ underlying processors, 210+ countries, white-label, designed for platform-style use cases

• Primer — enterprise focus, strong workflow / no-code routing rules

• Gr4vy — cloud-native orchestration, modern API

• Spreedly — tokenisation-first orchestrator, common with subscription businesses

When orchestrators make sense:

• Cross-border B2B with customers in 20+ countries

• High volume where 0.3-0.5% in fee savings exceeds the orchestrator's monthly fee

• Multi-brand / multi-entity merchants needing different processor relationships per brand

• Platforms reselling payments to their merchants

When they don't:

• SMB single-country merchants with under $100k/month processed

• Teams without engineering capacity to maintain the integration

• Cases where HubSpot Payments' simplicity is the actual value, not the rate

Picking Your HubSpot Payment Gateway

A decision tree that maps to the question "what payment gateway should I use with HubSpot?"

Are you a HubSpot SMB customer in the US/UK/EU/CA/AU, with simple invoicing needs and customers in your home market? → HubSpot Payments. Don't overthink it. The convenience is worth the markup.

Do you already have a Stripe account with negotiated rates? → HubSpot + Stripe native integration. You keep your Stripe rates and add HubSpot CRM attachment for free.

Are you doing recurring B2B billing where direct debit is preferred over cards? → HubSpot + GoCardless (BACS/SEPA/PAD/ACH) for recurring; HubSpot Payments for one-offs.

Do you have a specific gateway requirement (existing Adyen / Worldpay / Braintree / Checkout.com relationship)? → HubSpot App Marketplace connector for that gateway. Verify the connector quality before committing.

Do you have customers in Latin America, Asia, Africa, or the Middle East? → HubSpot Payments will fail you on currency support. Multi-PSP orchestrator or regional marketplace connector (Razorpay, MercadoPago, Paystack, etc.).

Are you processing >$500k/month? → Multi-PSP orchestrator. The savings on transaction fees from PSP routing typically pay back the integration in 2-4 months.

Are you a platform or marketplace reselling payments to your own merchants? → Multi-PSP orchestrator with white-label support. HubSpot's branding controls won't go far enough; you need full white-label.

Side-by-Side Comparison

Common HubSpot Payment Gateway Questions

What payment gateway does HubSpot use by default? HubSpot Payments — HubSpot's own merchant-of-record processor. You can replace it with Stripe, GoCardless, or any of 30+ App Marketplace connectors.

Can I use Stripe with HubSpot? Yes — HubSpot has a native Stripe integration that routes Commerce Hub payment links to your Stripe account at Stripe's direct rates. No HubSpot fee markup. Setup is 5-10 minutes in Settings → Commerce → Connected accounts.

Does HubSpot work with PayPal? Yes, via the HubSpot App Marketplace PayPal connector. PayPal Checkout becomes an option alongside or instead of HubSpot Payments. Not as deeply integrated as Stripe but sufficient for adding PayPal as a payment method.

**Can I use multiple payment gateways in HubSpot?** Yes on Commerce Hub Pro+. You can connect HubSpot Payments + Stripe + GoCardless simultaneously and route different workflows/deals to different gateways. For routing across many more gateways or doing intelligent per-transaction routing, you need a multi-PSP orchestrator.

What's the best payment gateway for HubSpot Sales Hub? For most SMBs the answer is HubSpot Payments or HubSpot + Stripe. Sales Hub customers who already use a specific PSP for their company-wide billing typically integrate that PSP via the App Marketplace or via a workflow-triggered API integration.

Does HubSpot integrate with Adyen? Yes, via the HubSpot App Marketplace. Adyen's HubSpot connector is built for enterprise customers using Adyen as their primary acquirer. For multi-PSP routing (Adyen + others), use a payment orchestrator.

Can I switch payment gateways without disrupting my HubSpot data? Yes — HubSpot stores payment data on the deal/contact record independent of the gateway. Switching gateways changes how new transactions are processed but historical transaction data, invoices, and deals are unaffected. Test the new gateway on a small subset of workflows before cutting over fully.

Related Reading

• HubSpot Payment Links: Complete 2026 Guide

• HubSpot Commerce Hub Transaction Fees

• HubSpot International Payments

• HubSpot Payment Link Branding

• Payment Orchestration vs Payment Layer

• Best Payment Link Providers 2026