HubSpot Payments, the default processor for HubSpot Commerce Hub payment links, is available to businesses in three countries: the United States, the United Kingdom and Canada. If your customers pay in Brazilian Real, Singapore Dollars, Indian Rupees, Mexican Pesos, South African Rand, Japanese Yen, or any other currency, HubSpot Payments can't process the transaction at all.
For most HubSpot Commerce Hub customers in the US, UK and Canada, this isn't a problem. For anyone selling cross-border into Latin America, Asia-Pacific, the Middle East, or Africa, or anyone whose customer base spans 20+ countries, HubSpot Payments stops working at the currency boundary.
The fix isn't to leave HubSpot. The fix is to route international payments through a third-party processor while keeping HubSpot's CRM, workflow, and invoicing layer intact. This guide covers exactly which countries HubSpot Payments serves, what currencies international customers can pay in, and the three integration patterns that let HubSpot process payments worldwide.
Quick Answer
HubSpot Payments currencies (as of 2026): HubSpot doesn't publish a list. Payouts go to a bank account in the US, UK or Canada, and euro payments are taken from buyers by SEPA Direct Debit.
HubSpot Payments merchant countries: United States, United Kingdom and Canada. Your business must be incorporated in one of these countries to onboard.
Can HubSpot Payments accept international cards? Yes. Cards from anywhere can pay you in your supported currency. A US merchant accepting USD can charge a card from Brazil. But the customer pays in USD with their bank's FX, plus typically a cross-border fee of ~1.5% added to your transaction.
Can HubSpot Payments charge in non-supported currencies (BRL, SGD, INR, etc.)? No. Not natively. You need a third-party integration.
Cross-border card fees on HubSpot Payments: +1.5% on top of the standard US rate of 2.9%, so about 4.4% on international cards, before any currency conversion or platform fee.
Workarounds: HubSpot's native Stripe integration extends currency support to 135+. Multi-PSP integrations like Shuttle connect 40+ underlying processors.
What HubSpot Payments Actually Supports
There are three different layers of "international support". They get conflated in HubSpot's marketing copy.
Layer 1: Merchant region
Where your business is incorporated and your bank account lives. HubSpot Payments will onboard merchants in:
United States
United Kingdom
Canada
If your business is incorporated in Brazil, India, Singapore, UAE, South Africa, or anywhere outside the above, HubSpot Payments cannot onboard you at all. You'll need a third-party processor integration regardless of where your customers are.
Layer 2: Settlement currencies
The currencies HubSpot Payments will deposit into your bank account. Payouts go to a bank account in the US, UK or Canada, and Canadian businesses can add a USD account. Multi-currency on a single contract requires Commerce Hub Professional or above.
Layer 3: Customer payment currencies
What customers can be charged in. HubSpot Payments only charges in your settlement currencies. A US merchant cannot present a checkout in Brazilian Real to a Brazilian customer through HubSpot Payments. The checkout shows USD, and the customer's bank handles the FX on their side.
That last layer is what most teams discover too late. The customer experience for international payments is poor: prices in unfamiliar currency, surprise FX on the bank statement, higher card decline rates, and abandoned checkouts.
What "International Cards" Actually Costs You
When a non-domestic card pays a HubSpot Payments invoice, three fees stack:
The standard transaction fee: 2.9% (US merchant accepting USD).
Cross-border / international card fee: +1.5% for a US merchant, listed in HubSpot's payments FAQ.
Currency conversion fee: if HubSpot is converting between settlement and customer currency, +1% for a US merchant and +2% in the UK and Canada.
On a $1,000 invoice paid by an international card that needs currency conversion: $29 standard + $15 cross-border + $10 conversion = $54 in fees, or 5.4% of the transaction, plus the 0.5% platform fee after the first year. Compare that to 2.9% domestic.
For US merchants billing international B2B contracts at $5,000+, this is the largest line item in payment costs and rarely surfaces in finance reviews until quarterly statement reconciliation. For SMB merchants selling cross-border ecommerce, it compounds quickly across hundreds of transactions.
The Three Integration Patterns
There are three ways to accept international payments inside HubSpot, each with different tradeoffs.
Pattern 1: Stay on HubSpot Payments, accept the cross-border premium
Cheapest setup, highest per-transaction cost. Works if:
You're invoicing in USD, GBP or CAD and your customer can pay in that currency
Your international transaction volume is low enough that 5-6% all-in doesn't matter
You don't need local-currency presentation for conversion
For most HubSpot SMBs with occasional international transactions, this is the right answer. For anyone with serious cross-border volume, the next two patterns pay back fast.
Pattern 2: HubSpot + Stripe native integration
HubSpot has a native integration with Stripe that lets you connect your own Stripe account. Payment links generated in HubSpot Commerce Hub route to Stripe instead of HubSpot Payments.
What this unlocks:
135+ currencies via Stripe's coverage (full list at stripe.com/global)
Local payment methods: iDEAL (Netherlands), Bancontact (Belgium), Klarna (EU), Alipay/WeChat Pay (China)
CRM attachment preserved: HubSpot still tracks payment status against the contact/deal
What this doesn't unlock:
Merchant onboarding outside Stripe's supported markets (Latin America beyond Brazil/Mexico, much of Africa, parts of Asia)
PSP optionality: you're locked to Stripe
White-label checkout
Best for: Teams already on Stripe who want to keep that relationship while using HubSpot CRM, with customer bases concentrated in Stripe's supported countries.
Pattern 3: Multi-PSP coverage via Shuttle (or an orchestrator)
For teams whose customer base spans regions that no single PSP covers, typically anything involving 20+ countries or specific markets like Latin America, Southeast Asia, India and Africa, a multi-PSP layer lets you connect the processors that cover those markets. An orchestrator such as Primer or Gr4vy also picks a processor for each transaction; Shuttle is a payment layer and doesn't. With Shuttle, each payment method or business entity goes to the gateway you set.
What this unlocks:
40+ underlying processors (Stripe, Adyen, Checkout.com, Worldpay Access, Cybersource, plus regional specialists such as PayU and Xendit)
Local acquiring: run each business entity on a processor with local acquiring in its own market, which can lower decline rates and FX costs
Local payment methods through the connected processors that support them
Open banking / pay-by-bank in markets that support it, through PSPs that offer it
Trade-offs:
Adds a layer to the integration stack
Requires Commerce Hub Professional+ for the workflow triggers
Setup is more complex than the native Stripe integration
Best for: Cross-border B2B platforms, marketplaces, SaaS companies with global customer bases, or any HubSpot Commerce Hub merchant with material volume outside North America / Western Europe.
Which Countries Does HubSpot Payments Actually Reach?
HubSpot Payments reaches:
Strong support (merchant + customer + local currency): United States, United Kingdom, Canada.
Card acceptance only (customer can pay you, but you can't onboard as a merchant): The rest of the world, if the card brand is Visa, Mastercard, or American Express, and the customer is willing to be charged in your supported currency, and their bank doesn't decline the cross-border transaction.
Genuinely unreachable (where HubSpot Payments adds no value vs not having it):
Most of Latin America: Brazil, Mexico, Argentina, Colombia, Chile, Peru. Local payment methods (Pix, OXXO, boleto, PSE) aren't supported.
South & Southeast Asia: India, Indonesia, Vietnam, Philippines, Thailand. UPI, OVO, GCash, PayMaya, PromptPay all absent.
Africa: South Africa, Nigeria, Kenya, Egypt. M-Pesa, instant EFT, USSD payments absent.
Middle East: UAE, Saudi Arabia, Israel. Mada, Knet, regional wallets absent.
Eastern Europe outside EU: Russia, Ukraine, Turkey. Regional methods absent.
For merchants whose customers cluster in these regions, HubSpot Payments isn't a workable solution and the conversation should start with multi-PSP orchestration, not optimisation of HubSpot Payments itself.
HubSpot International Payments: Decision Framework
Your situation | Recommended pattern |
|---|---|
US/UK/CA merchant, customers mostly in same region | HubSpot Payments native ✓ |
US/UK/CA merchant, occasional international cards | HubSpot Payments + accept the 5-6% cross-border ✓ |
Single-PSP team already on Stripe, customers in Stripe-supported countries | HubSpot + Stripe native integration ✓ |
Customers in Latin America, India, SEA, Africa, ME | Multi-PSP layer (Shuttle) or orchestrator (Primer / Gr4vy) ✓ |
Cross-border B2B with high invoice values | Multi-PSP with open banking on supported corridors ✓ |
Marketplace / platform with global merchants | Multi-PSP, possibly Commerce Hub Enterprise + custom workflow ✓ |
Merchant incorporated outside the US, UK or Canada | Can't use HubSpot Payments: third-party only ✓ |
Implementation Notes for Non-Standard Currencies
For HubSpot Commerce Hub teams adding non-standard currencies via Pattern 3, three workflow patterns:
1. Native HubSpot multi-currency on the deal record. Commerce Hub Professional+ supports multi-currency at the deal level. Configure the additional currencies, set FX rates (manual or auto), and HubSpot will store the deal value in the chosen currency. This is the display layer. It doesn't change what currency the customer pays in.
2. Workflow-triggered payment link generation in the deal's currency. When a deal moves to a payment-required stage, a HubSpot workflow calls your payment layer's or orchestrator's API with the deal currency, and it generates a payment link denominated in that currency. The link is inserted into the invoice or email automatically.
3. Payment status back to HubSpot. A webhook returns the payment status, transaction currency and processor used, and a workflow updates HubSpot's deal record.
Frequently Asked Questions
Does HubSpot accept international credit cards? Yes for payment: a card issued anywhere can pay a HubSpot Payments invoice as long as the card brand is Visa, Mastercard, or American Express and the customer is willing to be charged in your supported currency. Expect a +1.5% cross-border fee and higher decline rates on international cards.
Can I charge customers in their local currency through HubSpot? Not natively through HubSpot Payments. HubSpot Payments pays out only to bank accounts in the US, UK and Canada. Local-currency presentation requires a third-party processor integration (Stripe for 135+ currencies, a multi-PSP layer or orchestrator for wider coverage through local processors).
Which countries can use HubSpot Payments as a merchant? United States, United Kingdom and Canada. Merchants anywhere else need a third-party processor.
What's the cross-border fee on HubSpot Payments? Typically 1.5% on top of standard rates, levied when a non-domestic card pays your invoice. Combined with FX and standard fees, all-in cost on international cards is typically 5-6% in the US.
Can I use HubSpot Commerce Hub with Stripe instead of HubSpot Payments? Yes. HubSpot has a native Stripe integration that routes Commerce Hub payment links to your Stripe account. You keep HubSpot CRM and workflow attachment.
How do I accept Pix, UPI, M-Pesa, or other local payment methods in HubSpot? HubSpot Payments doesn't support these directly. You need a multi-PSP integration via a payment orchestrator. The orchestrator handles local payment method presentation, processing, and reconciliation back to HubSpot via webhook.
Does HubSpot support multi-currency on a single deal? Yes, on Commerce Hub Professional+. The deal record displays in the chosen currency and HubSpot tracks FX. Whether the payment happens in that currency depends on your processor configuration. See the implementation patterns above.