December 4, 2019 at 4:27 pm #15391
Hello, I’ve done two tests on my site where I’m using WP eStore with WP eMember for recurring membership subscriptions.
The first test I did said that the payment went through, sent me the emails, created my member account, but then a payment was never received in Stripe – nothing there.
Then I created a test membership level (all same settings as other level, just lower price), and it worked.
Then I went and purchased the actual membership which had been updated the day before to a new price, and it seemed to go through, sent me the emails, created my membership account, but again no payment was received in Stripe. And the WP eStore stats shows that the old price was ‘charged’, $87 instead of $97.
What could be going on? Is this a caching issue?December 4, 2019 at 7:16 pm #80160wzpModerator
Is this a caching issue?
***ARE*** you using any page caching plugins?
I’ve done two tests…
Are you doing “live” payment processing, or are you (…trying…) to use “sandbox testing?”
P.S. Are you using the eMember or the eStore subscription buttons? Your posts seem to indicate that you may trying to use both.December 5, 2019 at 12:05 pm #80161
No, we’re not using any caching plugins.
Both of the tests have been ‘live’ payment processing (no sandbox). And actually, there’s been a total of three tests – first one by me, which didn’t work, and then second by me, which did work, and then the most recent third one by someone else, which didn’t work and showed old information (rather than the updated price).
We’re using the eStore subscription link that I was given here in the forum by one of your moderators, but not in the button shortcode. I’m simply using it in one of the button modules that comes with our DIVI visual builder theme. Here’s the link: cryptotaxaudit.com/?wp_eStore_subscribe=1&gateway=stripe_subsc
I’ve checked and made sure that the eStore product is correctly integrated with the correct Membership Level ID as well.
Thanks for the help!December 6, 2019 at 6:29 am #80162wpCommerceModerator
@cryptotaxfixer, Have you made any changes to the price after the first payment? I mean did you edit the price from estore’s product management interface after a transaction of that subscription product took place?December 6, 2019 at 1:06 pm #80163
Yes, after the first two payments (the first that failed and the second that succeeded) I had changed the price in the estore’s product management.
The first time, which failed, I had changed the price only in the first section of the product details and then after trying to process it, realized I had not changed it in the subscription settings. This was all done within the same hour, so a short amount of time.
Once I had the price correctly changed in both areas of the product, I tested it the next day and that’s when it worked.
For the third payment a day later, I had to change the price and did so in both areas, then the next day tested it and that one failed as well.
Today, I did another test and haven’t changed the price or anything about the products and it worked.
In all the cases, the email notifications were sent, the sale was recorded in eStore and the membership account created, regardless of whether the charge was successfully processed or not.December 7, 2019 at 4:07 am #80164wpCommerceModerator
@cryptotaxfixer, A plan is automatically created in your Stripe account when you first make a payment with your subscription product. So even if you change the price later in eStore, Stripe will continue to charge the amount that was set when the plan was initially created.
So please create a NEW estore product if you want to create a subscription plan at a different pricing plan.December 9, 2019 at 2:03 pm #80165
This would be something really important to note on your documentation! Please make sure and address this better regarding the Stripe subscription feature.December 9, 2019 at 11:55 pm #80166adminKeymaster
Stripe doesn’t allow the editing of an existing plan. I will update the following documentation and add the info there:
- You must be logged in to reply to this topic.