It seems like my complete payment gateway tutorial is not that complete after all. I didn’t mention there how you can validate payment gateway admin options.
For example let’s assume that we have to validate a USDT address of a TRON network. Here is how it should work:
Let’s assume that we’ve already added a field for a USDT address inside
init_form_fields() method. Just like that:
Welcome to a detailed guide about setting up payments on the websites using cryptocurrency. First of all I will explain some basics to you and then we will create our own payment gateway for WooCommerce (it is a eCommerce platform for WordPress).
Almost 7 years ago I created a tutorial about Stripe integration on a website. When I created it, it seemed quite difficult to me, but now it looks easy-breezy.
The thing is that it is obsolete right now. Well, it actually works for some cards, but mainly for those cards that are operating in North America. Today our goal is to implement it with brand new Stripe API which is called Payment Intents.
And I am going to guide your through it step by step.
There are three different WooCommerce hooks after payment completed I would like to talk about.
All of those hooks are fired when an order is either paid or doesn’t require a payment (Cash on Delivery for example). They also apply for custom payment gateways.
As you probably know, shipping classes apply to every product individually.
What does it mean for us? It means that we have to loop through all the products in the cart in our code and check their shipping classes using either
Also we have two options here – if any product in the cart has a specific shipping class or if all the products in the cart have the specific shipping class.
In this tutorial I will show how to perform a redirect to a custom order received paged depending on a payment gateway used by customer.
In this tutorial I will show you how to enable or disable WooCommerce payment gateways for a specific user role. And also how to condition them for registered users.