Our integration with Stripe makes a lot of things easier. Here are a few tips in case things are currently not so easy: 

As part of the process of connecting the integration, you will see a pop-up window that asks you to authorize ConvertKit with Stripe.

If you don’t see the pop-up, your browser might be blocking it. Double-check your browser settings, you may need to enable pop-ups before you can proceed.

If you’ve gone through the connection process but you still aren’t seeing your data, check that you have authorized the correct Stripe account. When authorizing via the pop-up window, you need to be logged into the Stripe account that you wish to connect. You also need to be logged in to the same account when adding the webhook to your Stripe dashboard.

If in doubt, disconnect your integration, log out of Stripe entirely (or go through this process in an incognito window), and try again. Double-check that the account names match all the way through the process.

For purchases to show up under Visual Automation, after connecting the integration, at least one purchase must be made before the option is available. 

A test purchase will not work here, because the webhook will only trigger for live purchases. So you must make a live purchase—but you can set a discount to minimize the fees Stripe will charge.

The current Stripe integration will only pull in certain purchases and not others. Specifically it watches for these events: "charge succeeded" and "subscription updated." If your Stripe setup is sending data on some other event, our integration may not capture it.

So, if your Subscriber has made a purchase and you don't see the purchase reflected through the integration, this might be the reason. We have plans to build out the Stripe integration further, in the future!

Stripe sends ConvertKit webhooks that contain information about purchases that were completed. From this information, ConvertKit needs to assign the purchase to a product record. We determine which product record through the information provided by Stripe. When there is not enough information from Stripe to determine the product, we assign it to the fallback “Stripe Payment,” which is what you may see in areas like Visual Automations.

These might be bug-related, so if you encounter this, let us know. We'd be happy to investigate!