HubSpot Payments: What the Transaction Fee Really Costs

HubSpot Payments isn’t priced with a single processing rate — it’s two fees stacked on the same transaction. A processing fee (which varies by payment method) and a separate platform fee (which varies by which processor is behind the transaction) both apply, and the gap between them is easy to miss until a business is moving meaningful volume through it.

How the two-layer fee structure works

• Cards are billed a processing percentage with no ceiling. Card transactions carry a percentage-based processing fee on every dollar processed, uncapped regardless of transaction size.
• ACH/bank transfers carry a lower rate and a hard cap. Bank-debit transactions are billed at a lower percentage than cards, capped at a fixed dollar amount per transaction — for a large invoice, that cap is the difference between a modest flat fee and a card fee that scales with the invoice total.
• A platform fee applies on top of processing, and it depends on which processor is used. Native HubSpot Payments carries a lower platform-fee rate than routing payments through Stripe inside HubSpot — Stripe’s platform fee is described as uncapped across all transactions, on top of whatever HubSpot’s own processing terms already charge.
• Native HubSpot Payments is geo-gated. It’s available to businesses located and operating in the US, UK, or Canada with a bank account in one of those countries; businesses outside that footprint are routed to Stripe by default, which carries the higher platform-fee tier.

Why the two-fee structure is easy to underbudget

A business that quotes “HubSpot’s processing fee” from memory is usually pricing only the first layer. The platform fee is a second, separate line that scales with total processed volume the same way the processing fee does — for a business doing meaningful monthly payment volume through HubSpot, that second layer compounds into a real cost that a seat-based HubSpot budget doesn’t account for at all.

Card vs. ACH: the practical difference

	Card payments	ACH / bank transfer
Processing fee	Percentage of transaction, uncapped	Lower percentage, capped per transaction
Best for	Smaller transactions, faster settlement	Larger invoices, where the cap keeps the fee from scaling with size
Platform fee	Applies on top regardless of method	Applies on top regardless of method

Where the fix actually lives

For a business collecting meaningful payment volume, the practical move is routing large invoices to ACH wherever the customer relationship allows it, since the capped fee structure avoids the percentage scaling that applies to cards. Beyond that, a custom-built billing layer that connects directly to a merchant processor can carry high-volume invoicing on a flat monthly fee instead of a percentage that scales with revenue, while HubSpot stays the CRM system of record. See how to reduce CRM licensing costs for the general pattern, and HubSpot Revenue Hub’s seat-plus-transaction pricing for how the two layers interact with CPQ seats.

Frequently asked questions

Is HubSpot’s platform fee the same regardless of which processor is used?

No — native HubSpot Payments and Stripe-through-HubSpot carry different platform-fee rates, with Stripe’s routed through HubSpot generally the higher of the two.

Can any business use native HubSpot Payments?

No — it’s limited to businesses located and operating in the US, UK, or Canada with a bank account in one of those countries; businesses outside that footprint use Stripe instead.

Does ACH avoid the platform fee entirely?

No — the platform fee applies on top of processing regardless of payment method; ACH’s advantage is a lower, capped processing rate, not an exemption from the platform fee.