HubSpot Payment Links: How to Create, Brand & Integrate (2026 Guide)

By Shuttle Team, April 27, 2026

HubSpot has steadily added payment functionality over the last few years. Today there are three ways to take payments through HubSpot: native HubSpot Payments, HubSpot Commerce Hub payment links, and third-party integrations via HubSpot's marketplace, Zapier, or Make.com. Each has its own trade-offs around supported gateways, transaction fees, branding, and international support.

This guide covers what each option does, when each is the right fit, and how to use any compatible payment gateway with HubSpot, including Stripe, Adyen, Worldpay, Checkout.com, Mollie, and others.


Yes, but with limits depending on which HubSpot product you have.

  • HubSpot Payments (available to businesses in the US, UK and Canada) lets you create payment links that take cards and bank debits, but it only processes payments through HubSpot's own Stripe-powered system. No alternative gateway.

  • HubSpot Commerce Hub (a paid add-on on Sales Hub Professional+) lets you create custom payment links with your own logo and basic branding. It handles invoices, recurring billing, and quotes. Underneath, it still runs on Stripe (or HubSpot Payments in supported regions).

  • Third-party integration via Shuttle + Zapier/Make.com lets you use any of 40+ payment gateways, your own logo, colours and domain, international cards via local PSPs, and your own PSP's rates.

If you're a UK, EU, or non-US merchant, or you want to use a specific gateway (Adyen, Worldpay, Checkout.com, Mollie), the third-party route is usually the right call.


Option 1: HubSpot Payments (US, UK and Canada)

HubSpot Payments is HubSpot's own payment product, available to merchants based in the US, UK and Canada. You connect your bank account directly. Card payments are powered by Stripe under the hood.

What you get

  • Payment links sendable from quotes, invoices, deals, or directly from a contact record

  • ACH and card payment support

  • Automatic reconciliation against the contact and deal record

  • HubSpot-branded checkout (limited customisation)

Transaction fees

HubSpot Payments charges its own per-transaction fees on card and ACH payments, plus a platform fee after the first year.

Limitations

  • Available only to businesses in the US, UK and Canada

  • No alternative payment gateway support

  • Limited checkout branding (HubSpot logo on the page)

  • No international card processing through local PSPs (Adyen, Worldpay, Mollie)

  • No support for non-card payment methods like BLIK, iDEAL, Bancontact

When it's the right fit

US-based merchants with simple payment needs, where the convenience of native HubSpot integration outweighs the lack of gateway choice.


Option 2: HubSpot Commerce Hub

HubSpot Commerce Hub is a paid add-on (sits on Sales Hub Professional or Enterprise) and gives you a richer commerce toolset. It includes payment links, invoices, recurring billing, quotes-to-payment, and subscription management.

What you get

  • Custom payment links with your logo and basic colour customisation

  • Invoice and quote payment links bundled with the document

  • Recurring billing (subscriptions) with native dunning

  • Reporting on payment status, MRR, and revenue across the commerce funnel

Transaction fees

Commerce Hub uses HubSpot Payments or Stripe Connect underneath. The fees are the same as Option 1, plus the cost of Commerce Hub itself, which sits on top of Sales Hub Professional.

Limitations

  • Still tied to Stripe / HubSpot Payments

  • US-first (international support is improving but partial)

  • Branding is "your logo on a HubSpot-branded page", not a fully custom checkout

  • Limited support for region-specific payment methods

When it's the right fit

US merchants on Sales Hub Professional+ who want subscriptions, recurring billing, and a unified commerce dashboard inside HubSpot.


Option 3: Third-Party Integration via Shuttle + Zapier or Make.com

This is the most flexible route and the only option if you need:

  • A payment gateway other than Stripe (Adyen, Worldpay, Checkout.com, Mollie, Braintree, Square, GoCardless, etc.)

  • International card processing through a local PSP

  • Region-specific payment methods (SEPA Direct Debit, BACS, iDEAL, Bancontact, BLIK, Apple Pay, Google Pay)

  • Custom checkout branding (your logo, colours and domain, not a HubSpot-branded page)

  • Multi-PSP support, with each business entity on its own gateway

  • Payment links that work outside HubSpot too (Slack, SMS) using the same Shuttle account

How it works

Shuttle Links Checkout connects to HubSpot via Zapier or Make.com. The integration is no-code. The basic flow:

  1. Trigger: a HubSpot deal moves to a particular stage, an invoice is sent, a quote is accepted, or a custom property changes

  2. Generate: Zapier or Make.com calls Shuttle to create a payment link with the deal's value, customer email, and any metadata you want to track

  3. Deliver: the link is delivered to the customer via HubSpot's email tool, SMS via Twilio, Slack, or any of Zapier/Make's connected channels

  4. Sync back: when the payment is captured, a webhook fires that updates the HubSpot record with the paid status, posts to Slack, and creates an invoice in your accounting tool

Supported payment gateways

The full Shuttle gateway list is available regardless of which workflow tool you use:

  • Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, Mollie, GoCardless, PayPal, Paysafe, Global Payments, FreedomPay, Authorize.Net, USAePay, Trust Payments, and 15+ more

You can switch PSP without rebuilding the HubSpot integration, though saved cards stay with the gateway that stored them. The Shuttle side abstracts the gateway, so the same Zap or scenario runs against the PSP you have configured.

Transaction fees

Transaction fees are whatever your chosen PSP charges. Each PSP sets its own rates.

Shuttle doesn't mark up your PSP's rates. You pay your PSP directly, and Shuttle's own pricing is separate (see the pricing page).

Branding

Custom branding. Your logo, your colours, your URL on a hosted checkout page that looks like part of your brand. Mobile-first, optimised for conversion. No HubSpot logo or HubSpot branding on the customer-facing checkout.

When it's the right fit

  • Non-US merchants

  • Merchants with an existing PSP relationship (Adyen, Worldpay, Checkout.com)

  • Merchants who want control over checkout branding

  • Multi-entity operations (each business entity on its own gateway)

  • Anyone who wants payment links that work consistently across HubSpot, Slack, and SMS


These are the patterns we see most often when teams use Shuttle with HubSpot:

When a deal moves to "Closed Won" (or any custom stage like "Awaiting Payment"), a Zapier or Make.com workflow generates a Shuttle payment link with the deal's value and customer email. The link is sent through HubSpot's email tool with merge fields, so it looks like a standard email from your sales rep.

Quote accepted → deposit collected

When a HubSpot quote is accepted by the prospect, generate a payment link for the agreed deposit.

When you send a HubSpot invoice, attach a Shuttle payment link as a CTA in the same email. Customer pays with one tap on their phone. The payment outcome syncs back to HubSpot, marking the invoice as paid automatically.

A workflow runs 7 days before a contract renewal date. Generates a payment link for the renewal amount, sends it to the customer with a "your renewal is coming up" message.

Any HubSpot property change can trigger a payment link. "Outstanding balance" becomes greater than zero: send a link. "Late fee applied" toggles to true: send a link with the fee included.


HubSpot Sales Hub vs HubSpot Commerce Hub: Which Do You Need?

The question we get most often is: do you need Commerce Hub to take payments through HubSpot? The honest answer is no, not necessarily.

You need Commerce Hub if:

  • You want HubSpot-native subscriptions, recurring billing, and dunning

  • You want a unified commerce dashboard inside HubSpot for revenue reporting

  • You're on Sales Hub Professional+ and have the budget for the add-on

  • US merchant where Stripe-via-HubSpot is the right gateway

You don't need Commerce Hub if:

  • You want to use a non-Stripe gateway (Adyen, Worldpay, Checkout.com, Mollie)

  • You're a UK, EU, or non-US merchant

  • You want custom checkout branding

  • You'd rather build the workflow in Zapier or Make.com (more flexible)

  • You only need transactional payment links (one-off, not subscriptions)

For most non-US merchants, the Shuttle + Zapier/Make.com route is a better fit than Commerce Hub. You get more gateway choice and your own logo, colours and domain, at the price of building the workflow yourself.


Frequently Asked Questions

Does HubSpot accept international credit cards?

HubSpot Payments processes international cards through Stripe's standard cross-border flow. They work, but rates are higher. For a better international rate, you can connect a local PSP (Adyen, Worldpay, Checkout.com) via Shuttle and process through them instead.

HubSpot Payments charges its own per-transaction fees, plus a platform fee after the first year. If you connect a third-party gateway via Shuttle, fees are whatever your PSP charges, depending on the PSP, card type, and volume. Shuttle doesn't mark up your PSP's rates; you pay your gateway directly, and Shuttle's own pricing is separate.

HubSpot Commerce Hub allows your logo and basic colour on the checkout page, but the page is HubSpot-branded underneath. For custom checkout branding (your domain, logo and colours, no HubSpot logo), use Shuttle Links Checkout via Zapier or Make.com integration.

Yes, both via HubSpot's native tools and via the third-party route. HubSpot Commerce Hub lets you generate links from deals directly. Shuttle + Zapier/Make.com lets you trigger links from any HubSpot stage change, custom property change, or workflow event with full flexibility on amount, description, currency, and metadata.

Does HubSpot integrate with Stripe directly?

Yes, but with caveats. HubSpot Commerce Hub uses Stripe Connect internally, so any Commerce Hub merchant is on Stripe by default. For a more flexible Stripe integration where you keep your own Stripe account separate from HubSpot, use the Stripe + HubSpot integration via Zapier or Make.com, or use Shuttle as the middle layer if you want to add other gateways alongside Stripe.

PayPal is supported through Shuttle's Braintree integration (Braintree is the PayPal-owned PSP). Connect Braintree to your Shuttle account, build the HubSpot trigger via Zapier or Make.com, and customers can pay by PayPal or card on the Shuttle hosted checkout. No direct PayPal integration is available natively in HubSpot Payments or Commerce Hub.

What happens to the payment in HubSpot after the customer pays?

If you use HubSpot Payments or Commerce Hub, the payment is automatically logged against the contact and deal record. If you use Shuttle via Zapier or Make.com, configure a "Payment Received" webhook that fires a Zap or scenario to update the HubSpot record (mark deal as paid, add a note, change a property). Both routes give you a clean record in HubSpot.


Where to Start

If you're a US merchant on Sales Hub Professional+ and want subscriptions, HubSpot Commerce Hub is the right starting point. The convenience of native integration outweighs the gateway lock-in for many US businesses.

If you're a UK, EU, or non-US merchant, or you have an existing PSP relationship you don't want to lose, start with Shuttle + Zapier or Make.com. Build one workflow (CRM stage change → payment link) and see how much faster it converts than chasing invoices. Expand from there.

Either way, start with one workflow, ship it, and measure the time-to-payment uplift. The biggest mistake teams make is over-designing the payment system before it's connected to the CRM trigger that matters.

Start collecting payments faster

Send branded payment links by email or SMS, track them in real time, and connect any compatible payment provider.

A Links payment page on a phone, showing the merchant logo, amount, reference and card fields