- This topic has 2 replies, 2 voices, and was last updated 9 years, 10 months ago by
.
-
Posts
-
For the past year, we have been running a small streaming video membership site using a combination of WP eStore, WP eMember, and CCBill as our payment gateway. We’ve always had issues with ccbill and eMember communicating in terms of memberships auto-renewing and in terms of unsubscribing (it’s only reliable for setting up new accounts). These webhooks don’t seem to be integrating properly. We contacted Tips and Tricks via email last year and were eventually able to solve the problem by adjusting where ccbill sends the webhooks (which just involved adding a at the end of our site’s main URL). Around Christmas, we had some security issues with the site, so we installed the plugin Bulletproof Security. However, since installing Bulletproof, the CCBill renewal/unsubscribe webhooks no longer seem to be working with eMember. We’ve tried deactivating Bulletproof, and we’ve made sure that the ccbill webhooks are going to the same place they were before, but nothing seems to be working. And in my conversations with CCBill customer service, they seem surprised that the webhooks are supposed to go just to our main website URL instead of someplace more specific. But in my conversations with Tips and Tricks last year, they indicated our main URL is exactly where it should be sending them. So my questions are this:
1) Are we correct that the webhooks are supposed to be going directly to our main website URL and not someplace more specific?
2) Is there a way for me to define where WP eMember receives webhooks to make sure that it coincides with where CCBill is sending them?
3) Is there something that the Bulletproof Security plugin may have changed that would still be affecting the site even when it’s disabled? If so, is that something I can restore? I know we had it conceal our directory page because that’s where our security issues were happening. Could that have caused it?
4) Is there a better way for us to handle this integration between CCBill and eMember? Having members’ access expire even though they’ve been charged has been a big source of frustration for us and for our customers, and we’ve been losing business as a result.
We’d love to rectify this as soon as possible. Thank you for your help.
1 and 2) Yes, the CCBill webhook needs to go directly to your site (our plugin has code that a notification from CCBill and processes it). This is not your issue anyway.
3) Yes, they may have changed the htaccess file so it is rejecting any communication from CCBill to your site. Have you looked at your htaccess file to make sure it doesn’t have any rule blocking CCBill’s notification?
4) It is already implemnted the best way possible. If you have added firewall that is blocking communication from CCBill, there is nothing we can do really.
- You must be logged in to reply to this topic.