HubSpot Commerce Hub payment links carry HubSpot branding by default: a generic checkout page on a HubSpot subdomain, with a "Powered by HubSpot Payments" footer. For B2B sellers, agencies, and high-value transactions, that default checkout works against the trust signal the rest of the buyer journey worked to build.
The good news: HubSpot supports progressively deeper branding as you move up Commerce Hub tiers, and full white-label is achievable through a third-party integration. The bad news: most of the meaningful branding controls (custom domain, full checkout customisation, branded receipts) sit behind Commerce Hub Professional or above.
This guide covers exactly what branding controls each Commerce Hub tier unlocks, how to configure them, and how to go beyond HubSpot's native limits when the in-platform branding isn't enough.
Quick Answer
Logo + colours on payment links: Available on all Commerce Hub tiers.
Custom subdomain (e.g.
pay.yourcompany.com): Commerce Hub Professional+.Custom checkout fields and flow: Commerce Hub Professional+ with workflow customisation.
Fully white-labeled checkout on your own domain: Not available natively. Requires a third-party payment link provider with white-label support.
What ranks in Google for "custom payment link branding HubSpot": Real configuration documentation is sparse. Most published content is HubSpot's own marketing. This guide covers what's actually configurable and what isn't.
What HubSpot Branding Controls Are Available by Tier
Free Commerce Tools (with HubSpot Free CRM)
Your company name on the checkout page ✓
Default HubSpot checkout layout (no custom layout) ✗
HubSpot subdomain on the URL (e.g.
app.hubspot.com/payments/...) ✗"Powered by HubSpot Payments" footer present ✗
Free tier is fine for testing but the checkout looks like a HubSpot test environment. Not for production B2B.
Commerce Hub Professional
Custom subdomain:
pay.yourcompany.comor similar, pointed at HubSpot's checkout via DNS CNAMECustom email sender domain for invoice and receipt emails
Workflow-driven payment link generation: different branding per workflow / deal type / customer segment
Branded customer portal for self-service subscription management
"Powered by HubSpot Payments" footer can be removed (check current tier docs)
More customisable checkout page layout (limited templating, not full HTML control)
Professional is where HubSpot's branding becomes acceptable for serious B2B. The custom subdomain in particular makes the checkout feel like part of your domain rather than a HubSpot product.
Commerce Hub Enterprise
Everything in Professional, plus:
Single sign-on on the customer portal for repeat buyers
Custom field types on the checkout (beyond HubSpot's standard set)
Audit logs for branding changes (compliance use case)
Sandbox environment for testing branding changes before production
Enterprise pricing rarely justifies itself for branding alone: most teams pay for Enterprise for workflow approvals, audit, and SSO. Branding controls are a bonus.
How to Configure HubSpot Payment Link Branding (Step by Step)
The basic branding configuration:
Settings → Commerce → Payment configuration
Upload your logo (PNG/SVG, recommended 200×60px)
Set primary and accent colours (hex codes)
Add business name, support email, support phone
Enable / disable HubSpot Payments footer (Pro+)
Settings → Commerce → Invoices
Configure the default invoice template
Set sender name and email
Enable the "Pay Now" button visibility
Map the button colour to your primary brand colour
Settings → Marketing → Email → Templates
Customise the payment confirmation email
Customise the receipt email
Set the sender domain (requires DNS records on Pro+)
Settings → Account → Domains (Professional+ only)
Add your custom subdomain (e.g.
pay.yourcompany.com)Configure the DNS CNAME record per HubSpot's instructions
Wait for SSL provisioning (typically 1-24 hours)
Verify the subdomain serves the payment checkout
The whole setup takes 30-60 minutes if your DNS access is sorted and your brand assets are ready.
What HubSpot Native Branding Doesn't Cover
Five gaps regularly come up when teams reach the limit of HubSpot's in-platform branding.
1. The URL still says "checkout.hubspot.com" without Professional. B2B finance teams sometimes flag this as a phishing risk: your beautifully branded payment page is on a third-party domain they don't recognise. Custom subdomain (Pro+) solves this if the customer notices the URL bar.
2. Layout customisation is template-bound. You can pick from a small set of HubSpot-provided templates and customise colours/logos within them. You can't materially restructure the checkout: add custom fields above the card entry, embed a video, change the flow from one-page to multi-step, etc.
3. Receipt and invoice PDF branding is limited. The PDF templates HubSpot generates support logo and basic colour customisation but not full layout control. Agencies, accountants, and others who care about the precise look of the invoice PDF often supplement HubSpot with a separate invoicing tool.
4. "Powered by HubSpot Payments" persists at lower tiers. Removing it requires Pro+.
5. White-label means "your logo on HubSpot's product", not your product. Even with all controls maxed out, the experience is HubSpot's product styled to look like yours. For platforms reselling payments to their own customers (the actual white-label use case), this isn't enough: your customers shouldn't ever land on a HubSpot URL.
Going Beyond HubSpot's Native Branding
For teams that need full white-label (payments on your own domain, your own checkout flow, your own receipt format), the answer is a third-party payment link provider integrated with HubSpot via API and workflow triggers.
Two patterns make this work.
Pattern A: Embed external payment links in HubSpot
The simpler version. Your payment link provider generates a unique URL per invoice/deal via API, and a HubSpot workflow inserts that URL into the email / invoice template instead of the native HubSpot payment link.
What this unlocks:
Full control of the checkout: your domain, your layout, your fields
Custom flows like deposit-then-balance, instalments, donations, multi-amount
Multi-PSP routing under the hood
Your branding on the receipt and follow-up emails
What stays HubSpot:
The deal/contact record, CRM workflow, automation, reporting
Setup complexity: Low-medium. Most modern payment link providers have direct HubSpot connectors (in the App Marketplace) or connect via the API.
Pattern B: Iframe a custom checkout inside HubSpot pages
For teams that want the payment experience embedded inside a HubSpot CMS page (say, a custom landing page with form + payment in one flow), the payment link provider's checkout iframe can be embedded directly in the HubSpot page. Customer never leaves the HubSpot domain; the iframe loads from your payment provider but the surrounding chrome is yours.
Trade-offs: PCI scope considerations. Depending on the integration mode, the iframe approach can keep the merchant in SAQ A (cleanest). Confirm with your provider that the integration is SAQ A eligible. See PCI compliance service provider guide for the scope-reduction implications.
Pattern C: Branded checkout with Shuttle
For teams that need payments on their own domain (e.g. pay.yourcompany.com) with full HubSpot CRM attachment:
Domain & branding: Checkout served from your own custom domain
HubSpot attachment: Webhook back to HubSpot with full transaction data
Multi-PSP under the hood: Connect 40+ processors, with each payment method on its own gateway
Side-by-Side: HubSpot Native vs Third-Party White-Label
Branding control | Free | Pro/Enterprise | Stripe via HubSpot | Shuttle via HubSpot |
|---|---|---|---|---|
Your logo on checkout | ✓ | ✓ | ✓ | ✓ |
Your colours on checkout | ✓ | ✓ | Limited | ✓ |
Custom subdomain | ✗ | ✓ | ✗ (Stripe domain) | ✓ |
Full custom domain (e.g. checkout.yourcompany.com) | ✗ | ✗ | ✗ | ✓ |
Remove "Powered by..." | ✗ | ✓ | Partial | Embedded Payment Layer only |
HubSpot CRM attachment | ✓ | ✓ | ✓ | ✓ (via webhook) |
When HubSpot Native Branding Is Enough
Most teams overthink this. HubSpot's Pro-tier branding (logo, colours, custom subdomain) is sufficient for:
B2B invoicing where customers already know your business and trust the relationship
Agency client payments where the agency name is on the invoice
Recurring SaaS billing where the brand is already established
E-commerce where conversion data shows no impact from the subdomain
Where it falls short:
Marketplaces reselling payments to merchants under the marketplace's brand
Platforms embedding payments as a product feature
High-trust transactions (escrow, large B2B, regulated industries) where any third-party domain triggers questions
Cross-currency or international flows that need bank-grade trust signals on the checkout
Frequently Asked Questions
Can I add my logo to HubSpot payment links? Yes. Settings → Commerce → Payment configuration. Logo + colours apply across all HubSpot payment links generated from that account.
How do I get a custom domain on my HubSpot payment links? Commerce Hub Professional or Enterprise is required. Configure under Settings → Account → Domains with a DNS CNAME pointing your subdomain (e.g. pay.yourcompany.com) at HubSpot's checkout host. SSL provisioning takes 1-24 hours.
Can I remove the "Powered by HubSpot Payments" footer? Yes, on Commerce Hub Professional+.
What's the most customisable HubSpot checkout option? HubSpot's native customisation tops out at logo, colours, and custom subdomain. For checkout layout, custom fields, and full white-label flows, you need a third-party payment link provider integrated with HubSpot.
Does HubSpot support white-label payment links for resellers? Not natively. HubSpot Commerce Hub branding is for the merchant using HubSpot, not for resellers of HubSpot. For reseller / marketplace scenarios, use a white-label payment link provider integrated with HubSpot CRM.
How much does HubSpot Commerce Hub Professional cost? Check HubSpot's pricing page for current figures. It unlocks custom subdomain, custom email sender, workflow-driven payment link generation, and branded customer portal.