Do you deliver a HubSpot website to your client without testing? Or do you simply run it through the tools for formality's sake because you have to do it? If you answer yes to any of these answers, it won't be uncommon for your clients to find more bugs in the final product than your testing team.
Stakes are even high when you have a payment gateway attached to your website because if that is not tested or secured, then every website user's credit card details, address, and personal information is at risk.
Why Test a Website in the First Place?
1. Ensuring functionality: Testing a HubSpot website ensures all the pages and features work correctly. This includes checking for broken links, site errors, and other issues.
2. User Experience: Testing a HubSpot website helps ensure the site is user-friendly and easy to navigate. This includes testing the site's layout, navigation, and other features that impact the user experience.
3. Security: Testing a HubSpot website helps to identify potential security vulnerabilities on the website. This includes testing for issues such as SQL injection and cross-site scripting that could open the site to attack.
4. Accessibility: Testing a HubSpot website ensures that the website is accessible to all users, including those with disabilities who may use assistive technologies such as screen readers.
5. Performance: Testing a HubSpot website can help optimize the website's performance, including page loading times, response times, and other factors that impact the user experience.
What is HubSpot Sandbox Environment?
To conduct successful website testing, HubSpot has allowed it users to create a Sandbox account. Through a Sandbox account, the web developers have access to the exact replica of their HubSpot platform to test features, custom properties, CRM definitions, integrations, and developer assets, without touching the live or actual versions of the website.
But there's a limitation in the Sandbox account as well. Users cannot test their payment links in a Sandbox account for some reason.
Many clients ask us if they can test the payment links in a Sandbox account, to which we reply that you can only test it manually because that feature is not available in Sandbox. So, testing the payment links in a HubSpot website is a special case, which we will learn in this blog.
How to Test Payment Links On a HubSpot Website
Open your HubSpot account and Go to Sales and then to Payments. On the opened page, you will see the option of 'Manage payment links' option on the top right. Open the Actions dropdown and click 'Open link in test mode.'
This option will open the payment gateway option in test mode. You don't have to share your personal credit card details here. HubSpot has provided some sample credit card details that users can use to test the payment link feature validity.
| Brand |
Credit Card Number |
| Visa |
4242424242424242 |
| Visa (debit) |
4000056655665556 |
| Mastercard |
5555555555554444 |
| Mastercard (2-series) |
2223003122003222 |
| Mastercard (debit) |
5200828282828210 |
| Mastercard (pre-paid) |
5105105105105100 |
| American Express |
378282246310005 |
| American Express |
371449635398431 |
| Discover |
6011111111111117 |
| Discover |
6011000990139424 |
| Diners Club |
3056930009020004 |
| Diners Club (14-digit card) |
36227206271667 |
| JCB |
3566002020360505 |
| UnionPay |
6200000000000005 |
For failed payment simulation, use the below values
| Simulation |
Credit Card Number |
| ZIP code validation fails & payment is declined. |
4000000000000036 |
| Card is declined. |
4000000000000002 |
| Payment is declined due to insufficient funds. |
4000000000009995 |
| Payment is declined due to an expired card. |
4000000000000069 |
| Payment is declined due to incorrect CVC. |
4000000000000127 |
