Forum Replies Created
-
Posts
-
ok cool. Subscription cancel and fail scenarios are covered now.
For the change in credit card on file, I will need to transfer the user to Stripe portal which has ‘Change Payment Method’ option. However this means I have to now code a redirect.
The way I envision this code to work
1. User gets transferred to WordPress Url which calls Stripe API to create a Stripe Customer Portal session. I will need to provide the Customer ID for it, which will be wp_wp_estore_customer_tbl.subscr_id table. This will need to be current User’s wp_wp_estore_customer_tbl.member_username.
2. Redirect customer to Strip Customer Portal using the session ID provided by API.
If the customer cancels his/her subscription on the portal, Stripe Webhook will take care of demoting the customer in eMember.
Am I thinking this right?
I would sincerely request for a feature in the stripe payment addon. We would really like to have a shortcut code for it. something like this
[wp_eStore_StripeCustomerPortalLink allowCancel=yes allowCardChange=yes showHistory=yes]
Is there an option to get such a shortcut developed by paying professional services?
Ok, I think i figured out the WebHook part. I will test it now.
https://www.tipsandtricks-hq.com/ecommerce/wp-payment-gateway-bundle-stripe-basic-gateway-setup-4170
However I am still looking for the Update Payment Method / Change Credit Card on file option.
I had the same problem. On investigation here are my findings and how i fixed it.
I have WordPress installed on Azure on MySQL. After installing and uninstalling eMember multiple times i was unable to resolve the issue.
Observation: Tables wp_wp_eMember_membership_tbl, wp_wp_auth_session_tbl, wp_wp_members_meta_tbl, wp_wp_eMember_members_tbl Did not exist in the database.
Issue: The issue seems to be the Database Engine on Azure being InnoDB while the scripts assume MyISAM. (Ref: eMember_installer.php lines: 74, 102, 116, 139, 175, 234, 243, 256, 278)
Solution: I created these 4 tables manually.
Steps:
1. Downloaded a MySQL Client tool. Heidisql worked for me just fine.
2. Run SQL Create Table Statements to create these Tables manually using InnoDB Engine.
3. Only one change in script was needed, looks like InnoDB does not accept Default Date parameters to be ‘0000-00-00’, so I had to change that to ‘2000-01-01’.
4. Restarted the website.
Everything seems to be working now.
