Find answers to common questions about the payments tool.
Your business or organization must be located in the US, have a US bank account, and must be using a paid version of HubSpot. In the future, HubSpot may expand eligibility to customers located in additional countries.
You may not be eligible if your company is in a high-risk industry, or sells certain products or services. Payments is powered in part by Stripe, and they don’t accept payments for some types of businesses. You can find more details and examples in Stripe’s restricted businesses list. Keep in mind that this isn’t a complete list, and all businesses are reviewed on an individual basis.
Payments is only supported in the US for now.
If you're not located in the U.S., HubSpot welcomes your feedback on whether you'd be interested in using payments in other countries. You can let HubSpot know which countries you want to use payments in following the steps below:
The payments tool currently supports credit cards, debit cards, and ACH debits (bank transfers). You decide which payment methods to accept from your customers - cards, ACH, or both.
Yes, you can accept card payments denominated in US dollars from buyers outside the US. HubSpot support global and regional card brands, including Visa, Mastercard, American Express, Discover, Diners and Japan Card Bureau (JCB).
Payment processing is subject to financial laws and regulations that are aimed at preventing money laundering, funding of terrorism and other illegal activities. To satisfy these regulations, HubSpot and other payment service providers are required to verify basic information about the business entity, its primary owners, and the individual who will serve as the authorized representative for the payments account. These obligations are referred to as the “know your customer” (KYC) rules. In addition, HubSpot will also use this information to mitigate fraud that could impact you or HubSpot.
The payments tool uses your tax identification number to verify the identity of your business and for reports that HubSpot is required to file with the IRS. The IRS requires HubSpot and other payment service providers to report the total amount of payments you receive on an annual basis. Form 1099-K is the document required by the IRS for this purpose. HubSpot will send you a completed Form 1099-K by January 31 following each calendar year in which payments are processed.
As a payment service provider, HubSpot bears financial risk associated with the processing of your transactions. To protect customers and the businesses and consumers they serve, HubSpot needs to understand the types of products and services that your business sells, your financial situation, and the potential credit risk of your business. This is done through a process called credit underwriting.
In most cases, HubSpot can complete this process automatically in the background within one to two business days of when you first start using the payments tool. Occasionally HubSpot may need to request additional information or speak with you to complete the underwriting process before activating your account.
When the underwriting process is completed, your account will be activated and you can begin accepting payments.
The payments tool is not supported in a sandbox account, but learn how to test your payment links in test mode before sharing them with your buyers.
The payments tool uses multiple layers of security to protect sensitive payment information. The payments tool is built using Stripe's API integration to manage the secure collection and transmission of payment data. Your buyer's payment credentials are encrypted and tokenized by Stripe to help ensure that unauthorized parties do not gain access to sensitive payment information.
Yes, HubSpot payments uses infrastructure provided by Stripe, Inc., a leading provider of digital payments infrastructure. Stripe’s infrastructure is certified to comply with the Payment Card Industry’s Data Security Standards (PCI-DSS) Level 1, the payment industry’s highest level of protection.
With most traditional payment processors, businesses that accept card payments are required to annually validate their compliance with PCI by submitting documentation and undergoing network vulnerability scans. With the payments tool, Stripe acts as the payments processor, which means that unless you separately process card data, you are not exposed to card data and are therefore not required to validate your compliance with PCI.
There are no setup fees, monthly fees, minimums, or hidden charges. HubSpot charges a percentage of each transaction, so you only pay for the service when you use it.
You can also find the current payment processing rates in your payments settings:
Rather than being included on your regular HubSpot invoice, the fees for payments are automatically deducted from each transaction. To see the fee for a particular transaction, navigate to the Transaction history tab and select the transaction. To generate a report showing the total fees for a particular time period, click Download reports and select Payments.
HubSpot does not currently charge a fee for processing a refund. However, you will not receive a refund of the fee associated with the original transaction.
There is no limit to the number of transactions that can take place, though the maximum individual transaction size is $100,000.
There is also a maximum dollar amount per month that applies to each account, which is determined through the underwriting process and communicated to you in your welcome email.
Stripe provides the underlying infrastructure for payments features that are built in HubSpot and is responsible for the secure processing, transmission, and storage of sensitive payment information. HubSpot does not directly capture or store such information, and only surfaces certain tokenized or partial information about transactions within your HubSpot account.
The payments tool is not the same as the HubSpot-Stripe integration, and you can't use an existing account. When you set up payments, you’ll navigate to Stripe to enter a few details about your company and verify your identity. You’re not creating a new login, and you won't need to log in to Stripe after that.
With the Stripe integration, you can integrate a quote with Stripe checkout so customers can pay with a credit card directly from the quote. The payment details will then appear in your Stripe account.
When you set up payments with HubSpot, you don't need to install the Stripe app. Instead, you’ll send customers to a checkout page with your own branding. You can also support more payment options, including ACH and credit card, and offer more flexible terms for recurring payments. After customers pay, you won’t need to log into a separate account and can instead track and manage all of your data in HubSpot.
Unfortunately, Stripe doesn't support migrating data from an existing account to HubSpot.
A chargeback is a reversal of a card-based transaction. It is a forced refund from you, the seller, to your customer, the buyer. Chargebacks occur when a buyer disputes a charge by contacting the bank that issued their credit or debit card. The cardholder’s bank will then take one of the following actions:
Cardholders may initiate chargebacks only for certain permitted reasons. Those reasons include:
In most cases, the cardholder must initiate the chargeback no later than 120 days following the original transaction.
HubSpot’s payments risk team will notify you via email if you receive a chargeback. HubSpot will assist you with challenging the chargeback if you do not believe the reasons for the chargeback are valid. HubSpot will also handle all communications with the card networks on your behalf and inform you of the outcome.
If you decide to challenge the chargeback, respond to the notice quickly, because most of the card brands only provide a 20 day response window from the chargeback date. After that, the chargeback will be final. If the chargeback is upheld by the card network, HubSpot will recapture the original transaction amount by deducting it from your future payouts or debiting it from your bank account. You do not need to issue a refund for the chargeback amount, as the cardholder's bank will issue the credit for the disputed charge, and the cardholder should contact their bank to check on the status.
Transactions passing through the Automated Clearing House (ACH) system can fail or be reversed later for a variety of reasons. The most common reasons for upfront failure are:
An ACH transaction that initially succeeds may be reversed later for the following reasons:
HubSpot’s payments risk team will notify you via email. For upfront failures, HubSpot will notify you within five business days of the transaction date.
When an ACH transaction initially succeeds and is reversed later, HubSpot will notify you as soon as the team is aware of the return. ACH rules provide a two business day window for business bank account holders to reverse an unauthorized transaction. However, consumer bank account holders have up to 60 calendar days following the original transaction date.
When responding to an ACH return, you will need to directly contact your buyer to arrange an alternative payment. If this is not successful, your remaining recourse is to take legal action against the buyer. If your buyer has reversed the transaction due to a claim that they did not authorize the transaction, and you believe this is incorrect, providing evidence that the buyer authorized the transaction may be helpful to your case. To retrieve a copy of the buyer’s original authorization, navigate to the Transaction history tab in your payments settings.
You can use QuickBooks workflow actions to sync payments collected in HubSpot to your QuickBooks Online account. These payments can be synced as paid sales receipts or paid invoices based on your business requirements.
If you use accounting software other than QuickBooks online, you can export the data from HubSpot then upload it into your accounting system. Navigate to theTransaction history and click Download reports to export transactions from HubSpot. For security purposes, only users with super admin permissions may perform this action.