PayU and WooCommerce: integration and setup step by step
PayU for WooCommerce, set up step by step: the REST API point of sale, four details, the sandbox, common errors and fees. Check it before you switch payments on.
The PayU WooCommerce integration connects a shop to a payment gateway and passes on information about paid orders automatically. The customer picks a convenient method and pays, and you see the current status in the shop’s admin panel.
How the PayU WooCommerce integration works
Image generated by AI
The official PayU plugin connects WooCommerce to the payment gateway. The customer can pay with BLIK, a card, Google Pay, a bank transfer, in instalments or through a “płacę później” (pay later) service, and the order status updates automatically.
Once a payment method is chosen, the shop passes the order details to PayU. What happens next depends on the method: the customer may be redirected to the operator’s site or finish the payment directly in the checkout. After the transaction is confirmed, PayU sends the information to WooCommerce.
The plugin lets you show a single combined method, “PayU - standard”. The customer then goes to the PayU page and only there chooses BLIK, a card, a transfer or another available option.
You can also show individual methods as separate items in the checkout. The official module supports, among others, BLIK, cards, Google Pay, instalments, PayPo and Twisto (two deferred payment services). Whether each one is available also depends on how your point of sale is set up in PayU.
On your side you get a panel with a list of transactions. There you can check payments, issue a refund and review payouts. You still manage orders in WooCommerce, so the day-to-day running of the shop stays in one place.
Before you start: a PayU account and a REST API point of sale
Image generated by AI
To run PayU with WooCommerce you need a production account and a point of sale of the REST API type. The plugin requires four details: the pos_id, the second MD5 key, the client_id and the client_secret.
You open the production account with PayU. During registration you give the company details, the bank account and information about the shop. The operator then verifies the business. The shop should be complete by then: with terms and conditions, a privacy policy and a working checkout. If you are only just setting it up, go through my guide on how to start an online store on WordPress first.
While full verification is under way you can already take payments by bank transfer and BLIK up to a limit of PLN 2,500. This lets you start selling earlier and check basic order handling. The full set of services becomes available once the process is finished.
After creating the shop in the PayU panel, add a point of sale and make sure its type is REST API. The WooCommerce module will not work with a point created in a different standard. This is a common cause of connection problems, especially when the PayU account was used earlier by an older shop. You will find the technical details in the PayU plugin documentation.
In the point’s settings you will find the four details needed for the setup. The pos_id identifies the point of sale. The second MD5 key is used to check that communication is valid. The client_id and client_secret pair lets the plugin authenticate with PayU.
Copy the values without extra spaces and keep them like a password. The client_secret and the MD5 key give access to important payment operations, so they should not end up in a public support ticket, a forum post or a screenshot.
Setting up PayU in WooCommerce step by step
Setting up PayU in WooCommerce comes down to installing the official module, entering the four details and choosing the payment methods. At the end you need to place a test order and check the whole flow from the basket to the status change.
Step 1. Install the PayU plugin from the WordPress directory
Log in to the WordPress admin and go to the section for adding plugins. Type “PayU GPO Payment for WooCommerce” into the search box. This is the official PayU module in the WordPress directory. Check the author’s name, install the module and activate it.
The PayU plugin requires PHP 7.4 or newer and the cURL library. cURL handles the communication between the shop and the operator’s servers. It is usually already available on the hosting, and you can check its status in the WordPress site health information or with your server provider.
After activation go to the WooCommerce settings, open the payments tab and find the methods labelled PayU. How many there are depends on the version of the module and the services available on your account.
Step 2. Enter the point of sale details (pos_id, second key, OAuth)
Open the settings of the basic PayU gateway. Paste the pos_id, the second MD5 key, the OAuth client_id and the OAuth client_secret into the right fields.
All four values have to come from one point of sale and one environment. Details from a production account go with production mode. Test details work in the sandbox.
After saving the settings, check that WooCommerce does not show a message about failed authentication. If the connection does not work, compare each value with the PayU panel. Pay particular attention to the second MD5 key and the client_secret, because the two look alike and are easy to paste the wrong way round.
Step 3. Choose the payment methods shown in the checkout
The simplest variant is the single method “PayU - standard”. The customer sees one item, goes to PayU and chooses how to pay on the operator’s site. This setup gives a short, clear checkout.
Separate items shorten the way to popular payments. The customer can click BLIK, a card or Google Pay straight away. That makes sense when you know your buyers’ preferences and want to bring forward the two or three most used options.
You do not have to switch on everything the module offers. A long list of banks, cards, instalments and deferred payments takes up a lot of space, especially on a phone. Start with the methods that matter most to your customers and leave the rest under the combined PayU option.
You set the order in the WooCommerce payments section. Put the most often chosen method high up, ideally near the shipping options and the price summary. After changing the layout, open the checkout on a phone and check that the names are readable and the fields do not push the order button far down the page.
Step 4. Place a test order and check the status change
Add a cheap test product to the basket and go through the full purchase path. Choose PayU, start the payment and check that the shop redirects you to the right environment.
After a successful transaction go back to the order in WooCommerce. Its status should change according to the shop’s configuration, usually from “Pending payment” to “Processing”. With virtual products WooCommerce may complete the order straight away.
Check the emails, the stock level and the transaction record in the PayU panel as well. The thank-you page only confirms the return from the operator’s site. You only get the full picture from the whole set: the payment, the operator’s confirmation, the status change and the order being handled correctly.
The PayU sandbox: a separate test account
The PayU sandbox is a separate environment with its own account, panel and POS details. Production is not switched into test mode with a single toggle in the PayU panel.
For your own tests you can create a separate sandbox account. After registering you add a test shop and a point of sale, then take its pos_id, second MD5 key, client_id and client_secret. PayU also provides a public test point, but your own account gives you access to the panel and lets you trace transactions.
In the first scenario make a successful payment and check the status change. Then cancel a payment before it is finished. Finally, issue a refund from the PayU panel and see whether the amount and the status match the order.
After testing, enter the full set of production details in the plugin and switch off sandbox mode. Clear the cache, open the checkout in a new window and make sure the payment address leads to the production environment.
Common integration errors and how to fix them
Problems with PayU and WooCommerce most often come from the point of sale settings, mixed-up details or blocked notifications. Start by checking the environment and all four fields, and only then look for a conflict in the shop’s code.
The first suspect is the type of the point of sale. If you see a standard other than REST API in the panel, create or configure the right point and copy its details to WooCommerce.
Production and sandbox often get mixed up too. The four fields can look correct even though they come from two different panels. The safest thing is to copy the whole set once more, without relying on an old message or note.
Sometimes the payment goes through but the order is still waiting for payment. In that case PayU may have sent a notification that the shop did not accept. Check the firewall rules, the hosting’s security features and the cache. The addresses that handle payment notifications should be excluded from the cache, the mechanism that saves a ready-made version of a page.
The next point is the currency. The order currency in WooCommerce has to be supported by the given PayU point of sale and the active payment method. The problem can appear after a currency converter is installed or when selling in several markets.
If the error started after an update or after installing another payment module, run a test on a copy of the shop with the other gateways switched off. Conflicts also happen with add-ons that modify the checkout. Once you have found the module at fault, check its updates and its compatibility with the WooCommerce version you use.
PayU fees in practice
PayU’s offer for small and medium-sized businesses includes one-off registration for PLN 29 on promotion, against a standard price of PLN 199. There are two fee variants to choose from: PLN 0.30 plus 1.1%, or 1.49% of the transaction value. You will find current rates and the full price list on the PayU offer page for SMEs.
For an order of PLN 100 the first variant costs PLN 1.40 and the second PLN 1.49. For a basket worth PLN 50 it is PLN 0.85 and about PLN 0.75 respectively. The line falls at around PLN 77: below that amount the percentage-only fee looks better, and above it the variant with a fixed charge and a lower percentage wins more often.
Do this calculation on the average basket value, not on the price of a single product. A shop selling accessories at PLN 30 each can have an average order of PLN 120 if customers regularly buy several items.
0% instalments and “płacę później” services are charged at the same rate. With turnover above PLN 800,000 PayU prepares an individual offer. The terms of the promotion can change, so check the current price list and settlement rules before signing the agreement. Fees are only one item in a shop’s budget. You will find the full breakdown of costs in the article how much does an online store cost.
PayU or Przelewy24: which to choose for WooCommerce
PayU and Przelewy24 (another Polish payment gateway) both handle the most popular WooCommerce payments well, including fast transfers, BLIK and cards. The choice usually comes down to the details of the implementation, the price list and the way your accountant settles incoming payments.
You install the official PayU plugin directly from the WordPress directory. The Przelewy24 module is downloaded from the operator’s site and uploaded to WordPress as a package. PayU requires the pos_id, the second MD5 key and two OAuth details. In Przelewy24 you will come across, among others, the Merchant ID, the POS ID, the CRC key and the API key. I have described the whole process in my guide to the Przelewy24 integration with WooCommerce.
Both operators provide test environments with separate details. In PayU the sandbox has a separate registration and its own panel, which you need to allow for during setup and when going to production later.
If you already have an active account with one operator, migrating will rarely bring a big change in how convenient paying is. Compare the fee at your average order value, the payout times, the reports for your accountant and the availability of the methods you need. Those four things usually give a more practical answer than the list of logos in the checkout.
FAQ
How much is the PayU fee in WooCommerce?
In the offer for small and medium-sized businesses there are two variants to choose from: PLN 0.30 + 1.1%, or 1.49% per transaction. Registration costs a one-off PLN 29 on promotion (PLN 199 as standard). 0% instalments and “płacę później” are charged at the same rate, and with turnover above PLN 800,000 PayU prepares an individual offer.
Will the PayU WooCommerce plugin work with every PayU account?
The module only works with a point of sale of the REST API type. If your account has a point in an older standard, add a new REST API point in the PayU panel and copy its details into the plugin.
How do I test PayU payments before the shop launches?
Open a separate sandbox account. The PayU test environment has its own panel and its own point of sale details. Go through a successful payment, a cancellation and a refund, and after testing replace the whole set of details with the production one and switch off sandbox mode.
Why does the order not change status after being paid through PayU?
Most often the notification from PayU does not reach the shop. Check the firewall rules, the hosting’s security features and the cache: the addresses that handle payment notifications should be excluded from the cache. Compare the currency and the amount of the order with the transaction in the panel too.
Does PayU support BLIK and Google Pay in WooCommerce?
Yes. You can show both methods as separate items in the checkout or leave them under the combined “PayU - standard” option, where the customer chooses how to pay on the operator’s site. Which methods are available depends on how your point of sale is set up.