Monthly level is charged daily (Stripe)

Hi @graphical

Thank you for reaching out to Paid Memberships Pro.

This doesn’t require a premium Add On or license to work and works in the core version of Paid Memberships Pro.

Can you please tell me what version of Paid Memberships Pro you are on?

Also inside Stripe, have you adjusted the plan at all from the Stripe dashboard?

Hi Andrew,

thanks for the answer. We are using Version 2.7.3

Are you saying we have to re-adjust all the plan in stripe each time someone subscribe? Probably not, as it wouldn’t really make sense. We can’t change the “product” recurring option in Stripe because it’s been used with the user that subscribed.

Question:
Do you have any docs, video or tutorial on how to integrate the Stripe plan with your plugin? Does it create a new “product” each time someone subscribe? How do we “link” the Stripe “product” with the PaidMembership Pro plan?

Sorry for the slow reply. We’ve been looking into this and trying to recreate it.

You should not have to adjust subscriptions in Stripe to use PMPro. PMPro will create products and prices on the fly. We did however introduce recently a method to reuse “prices”, and wondered if maybe tweaking that on the Stripe side led to the issue you are seeing.

I’m still testing, but I don’t believe that would. We double check that the price matches what PMPro needs before reusing it.

FYI here is our code where the subscription/plan is set up. https://github.com/strangerstudios/paid-memberships-pro/blob/dev/classes/gateways/class.pmprogateway_stripe.php#L4149-L4159

It would be interesting to debug around there to see if PMPro is confused about the details of the plan or if the issue is happening after we send it to Stripe.

If it’s the former, it’s possible some conflict in add ons or custom code is affecting the level or plan during checkout.

Does the level cost show up correctly on the checkout page?

Is there any other information you could share about your setup or how to recreate this issue?

I actually linked to some old code that is still included for backwards compatibility. With PMPro 2.7 and higher, this code is the relevant bit that looks for a “price” or creates a new one.

https://github.com/strangerstudios/paid-memberships-pro/blob/5ca74f946d62c7783bb248fd8d128289b39f6d68/classes/gateways/class.pmprogateway_stripe.php#L2285-L2364

It would be useful to debug at the top of that function to see what the values of cycle_period, cycle_number, and is_recurring are.

Then later to see if an existing price is being found and if it matches. And later when we create a price if the values there are correct.

I don’t know if you have the skills to do that debugging. If you do it helps. If not, learning more about your setup to help us recreate the issue will help. This is not happening for us in our testing yet.

Thanks, and sorry again for the problem.

Hi Jason,

thanks for the information. The site is using legacy API keys to connect to Stripe, could it be an issue with your new code?

Should we create a new subscription level and link it again to Stripe?

Hi Jason, any update on that?

Would you recommend created a completely new subscription level? What would you like to know about our setup? Is there a way to reach you directly?

> Should we create a new subscription level and link it again to Stripe?

I don’t think this should change things, but it’s worth a shot. What do you mean by “link it again to Stripe”? PMPro should handle the integration with Stripe automatically.

> What would you like to know about our setup? Is there a way to reach you directly?

At a minimum the output of the Site Health export would be helpful. You can use our contact form on our website to email it to us. You can also get paid support there, where we would be able to get access information from you to take a closer look.