Hi,
However, with Simple Membership, the account status is set to “expired” a few hours before the payment is made on Stripe.
This phenomenon occurs because Stripe uses the “time of registration” as the payment update time, while Simple Membership compares the date of the payment with the date of the payment when the date changes, and processes the expired account as an expired account if it has expired. Does this mean that this is the case?
It is a good idea to offer 1 or 2 extra days by setting the access duration value to something like 31 or 32 days. Because of the way PayPal’s IPN works, the plugin can’t offer hourly granularity. Giving access for an extra day is really nothing but it offers the customer full satisfaction.
Adding membership access levels for your site is very important. The following documentation can help you further understand this process.
https://simple-membership-plugin.com/adding-membership-access-levels-site/
Let me know if the information above helps you.
Thank you.
thank you for your answer.
When I set the access expiration date of the member created by Simple Membership longer than the expiration date of Stripe,
The access expiration date for Simple Membership was not renewed after the Stripe expiration date.
In that case, I think that the access expiration date of Simple Membership will shift little by little, but if the renewal process is done on the Stripe side before the expiration date, will it not expire?
Hi,
When I set the access expiration date of the member created by Simple Membership longer than the expiration date of Stripe,
The access expiration date for Simple Membership was not renewed after the Stripe expiration date.
Can you provide an example so that I know exactly what you did.
Thank you.
Thank you for your reply.
The work contents are as follows.
1) Create a membership level [test] with an expiration date of 2 days on the site side
Added products with a billing cycle of 2 days in Stripe’s test mode
2) Purchase products as a member level [test] user (= 6/10 18:15)
3) Change the expiration date of the user to “5 days”
（Confirm that the expiration date of the corresponding user has been extended to 6/15）
4) Confirm that payment processing is running on 6 / 12.6 / 14 with Stripe ⇒ Expiration date remains 6/15 and is not renewed
5) Access expiration date will be 6/15 ⇒ The expiration date remains 6/15 and is not renewed, and the account status remains “valid”
I would like to know why was not renewed even after the Stripe payment date and the member’s access expiration date.
thank you.
Hi, please check the following documentation to create a subscription button.
https://simple-membership-plugin.com/sca-compliant-stripe-subscription-button/
Also make sure you enable debug mode before you begin your test. After the test is completed, please check the log file and report back with any findings.
Thank you.
Thank you for your reply.
We have already created a subscription button.
This button connects the membership level [test] to the product with a 2-day billing cycle in Stripe test mode.
Please note that we have already created the subscription button for the product.
Also, debug mode was enabled.
However, the expiration date of the user who became a member by pressing the button was not updated after the Stripe payment date and access expiration date.
We would appreciate it if you could tell us the cause of this.
Also, we are testing the “Sakura Internet”
I am testing the staging environment at the following URL.
https://rs.sakura.ad.jp/function/backup_staging.html
Thank you in advance for your confirmation!
Hi,
Please take note of all the following items one by one:
#1) Share the debug log file’s content after a subscription payment is received so we can verify/confirm that our plugin is actually receiving the payment notification (the webhook notification) after the transaction. If the Stripe webhook is not setup correctly or you have some kind of a firewall setup (maybe with another plugin) that is blocking the webhook notification then our plugin won’t know about that transaction (hence it won’t update anything).
The following documentation will be helpful to understand the log file feature:
https://simple-membership-plugin.com/enable-debug-logging/
#2) Read the following posts which has some useful information in terms of how our plugin calculates the expiry. Some users can have a different idea (due to another plugin they have used in the past) of how the expiry works. So it can create some confusion from what they are expecting vs what our plugin does.
https://simple-membership-plugin.com/adding-membership-access-levels-site/
https://simple-membership-plugin.com/manually-activating-expired-members-account/
#3) For a subscription payment, as long as the subscription payment is received before the account is expired, the account’s access will be extended. The extension will be based on the “Duration” that is set in the membership level (not the stripe’s subscription period). Once a subscription payment is setup, it will simply wait to receive another payment to come in and then it will extend the membership. If no payment comes in within the timeframe or if the subscription is cancelled or refunded, the account will be deactivated.
Our plugin works on a very simple and low maintenance type setup. You may need a different and more heavyweight plugin if you need a more in-depth setup.
Thank you for your reply.
＃1）Where can I find the debug log files?
I will check on #2), #3).
Thank you for your continued cooperation.
