We’ve successfully connected our Hubspot instance with our Stripe account, so we should be good to go to have any payments processed by Stripe while seeing payment status information in Hubspot. (We need to use Stripe since Hubspot payment processing is not available in Europe.)
Now, we’d like to test this integration properly with all our workflows and for that we need to actually execute payments. On Stripe’s end, there’s “test mode” as well as a sandbox environment, but it seems that Hubspot only wants to interact with Stripe’s live environment, forcing us to use real cards, which obviously isn’t what we want to do for testing purposes.
Am I overlooking some setting perhaps? Or can anyone advise on what would be a workable solution?
Thank you for referring to that resource @Jigar_Thakker . This helps indeed to test the connection between Hubspot and Stripe, and to verify if payments are registered correctly in Stripe.
But testing something beyond that doesn’t seem possible?
We have a simple workflow where an invoice (including a payment link) is created and sent out. In that case there isn’t really a Payment Link we can open in test mode. We can assume though that if it works for Payment Links, that it’ll also work for invoices.
However there’s still no way to test the next step of the workflow, being the invoice status update, since no payment records are created when using test mode. This is also mentioned explicitly in the documentation, so I guess that means there’s currently no way to properly test if the interaction between both plaforms is working as expected.
That’s true, payment records and actual Stripe transactions occur only in live mode, but once you have tested the payment link and the “test” contact and deal are created/updated, you can rest assured in the live environment.
Double check for reliability:
Other steps in workflows that do not include a payment record should trigger (you can replace the invoice update for the time being).
Stripe integration settings: make sure you have authorized any required permissions
Lastly, if possible, make a real payment (very small) using a real card to ensure all parts, including payment records and related workflow triggers, properly function in the live environment.
After a real payment, check for updates on both the HubSpot and Stripe dashboards.
You don’t need to “accept” the changes in Sourcetree — the red/green lines are just showing the diff.
If you’re happy with the edits, the next step is to stage the file (check the box next to it), then commit your changes. After committing, you can push to your remote repo.
“Reverse hunk” is only there if you want to undo the changes, but if the changes are correct, just stage → commit → push.
and give it an upvote 
!