March 23, 2020 at 7:32 pm #79016
Good advice. I just realized that I thought the Approval URL and the Approval Post URL where the same thing. Now I realize that the Approval Post URL requires the specific URL for collecting the necessary data from CCBill. That appears to have resolved this data posting problem. Although the data collection page was created, it hadn’t been populated in the URL on the settings page. So, that was another place I was missing something.
However, returning to the original webhooks issue, as I said at the beginning these are subscriptions for my membership site. CCBill is biling them for recurring memberships. So, I still need to get the data from CCBill to WP eStore when their membership has renewed after 30, 60 or 90 days.March 24, 2020 at 1:21 am #79017adminKeymaster
Once the webhook starts to work correctly (meaning no more 301 errors), the subscription will continue to work fine. The plugin will keep processing the payment at the specified interval.March 24, 2020 at 6:19 pm #79018
Let’s just be clear, is there a unique URL for CCBill to use for webhooks with the plugin? Because right now, based on the information I have, it is just the generic site URL and this seems wrong. Could someone just answer this question which I have asked multiple times?March 25, 2020 at 12:42 am #79019adminKeymaster
No unique URL is needed. You only specify your website URL (just the homepage URL) for the webhook. When the webhook is received, the plugin listens for the data and then it processes the payment notification.
Let me know if that was a clear answer to your question.March 26, 2020 at 12:03 am #79020
Your answer is clear, but why CCBill’s webhooks use of the plugin is different is not clear. Why do the other payment gateways have specific URL’s that call the plugin code directly? They don’t talk to a generic port on the root of the website. But you are saying CCBill is going to send me critical data just off a port on the root of my website?March 26, 2020 at 3:36 am #79021wpCommerceModerator
@BSLLC, CCBiLL’s system is not like other payment gateways. The plugin cannot receive the data correctly from CCBiLL when other parameters are present in the URL. There is a reason why we had to implement it this way.
Receiving a webhook notification to a special page or with parameters doesn’t make it more secure. The data is available on the whole site if there a script listening to it.March 26, 2020 at 11:02 pm #79022
Yes, I understand what you are saying. That is unfortunate that the implementation with CCBill is less than ideal. I may need to just work with CCBill’s email notifications for transactions because the webhooks don’t appear to want to function properly and I don’t think I want to spend too much more time trying to troubleshoot the issue.
- You must be logged in to reply to this topic.