i configured YAPE and QR Payments, and the only available payments is bank transfer…
i already enable/configured both plugins YAPE A1 tiendas and QR Payments,
But they dont work…
I dont get any problems, on other hosting is working properly
I can tell you many things about our hosting, but I don’t have in-depth experience with WooCommerce. I’ve also never heard of YAPE or QR Payments in general, let alone having ever used their WooCommerce plugins.
So as far as I can tell, it could indeed be a hosting issue, it could be a compatibility issue, or it could be something else entirely. All I know is that I have no way to tell, and have no idea where to start looking.
Maybe you could try asking this question to the payment plugin developers first? They should know more about what could cause a payment provider to not be shown. And if it is indeed a hosting issue, they should be able to tell what hosting problem exactly we should fix to make this work.
Payment plugin works by handling your payment transactions securely outside of WordPress, then the gateway will send a webhook notification back to your online store to update the order status on your end.
Most plugins will not have a sync function because it’s assumed that your online store should be able to grab these notifications efficiently. However it’s not the case here because of a security system in place preventing non-browser external hits to your site.
If you have a day to spare, you can optionally find the article using keyword ?i=1 somewhere in the Documentation .
Ask your payment provider for the IP ranges that they use for notifications, then pass it on to the admin or via support ticket, and hopefully they’ll consider having those whitelisted from the security system. I say hopefully as there’s no guarantee that they will do so, nor does the gateway keeps on using the same IP ranges for the years to come.
However for business sake, you might be better off using a paid hosting, ideally VPS. Free hosting is also subject to other limitations that might negatively impact what you’re trying to do, especially with the hits and unavailability to backups.
While many payment providers do indeed use payment notifications in the form of webhooks, that should only ever cause problems with handling the payment after the payment has been submitted.
In this case, the problem is (as I understand it), that the payment provider just isn’t visible on the checkout page. Which sounds much more like a configuration issue in the website itself, because WooCommerce ultimately handles which payment providers are shown on the page.
Please don’t bother. We don’t whitelist anything on request.
Paid hosting, yes. VPS, no.
Unless you know how to properly manage a server, you should not use a VPS for business critical stuff. VPS require ongoing effort to secure and maintain, and if something breaks you want to be able to have it fixed quickly, which is not what you get if you set it up by copy-pasting commands from a tutorial.
If you don’t have this expertise, you should leave server management to the experts. Which is what you get if you use web hosting.
Not sure where this is from but at least major payment gateways would by default use webhooks, and it’s the industry norm.
This depends on how the plugin is coded, if it cannot reach the endpoint, it deregisters itself from the payment handler list.
Expected.
only ideally, that excludes if he/she is not familiar with the technology. Alternatively, seek managed VPS services so that there’s no need to deal with commands and just reach out to support, which is also very basic service includes in nowadays, managed or not.
While the webhooks are a potential future issue, it’s unrelated to the issue of not having a payment option on the checkout page. Which is what this question is about.
Even if a plugin would de-register itself like that (which would surprise me a lot, pinging all payment providers just to see if they are available seems very inefficient), then it still wouldn’t matter.
Because unlike a common misunderstanding that tends to get parroted on this forum, the browser validation system only affects API calls from the external party to your site, not the other way around. There is nothing blocking WooCommerce from reaching the payment provider.
Is it now showing up or not showing up? The way you phrase it make it seem like a typo. But you also marked your own answer as the solution which implies your issue was solved.