WooCommerce Paymill Gateway - WordPress Plugin

A Practical Guide to Configuring WooCommerce Paymill Gateway and Safely Testing Payments

WooCommerce Paymill Gateway is not there to dress up your checkout page. It serves a specific purpose - accepting payments through PAYMILL directly inside a WooCommerce store. This guide explains how to prepare your site, where to enable the payment method, which keys you need, why the method may not appear at checkout, and how to run a test order without triggering an accidental charge.

This guide is written for store owners, WordPress administrators, and developers who have inherited an already purchased or installed gateway. There is one important limitation to keep in mind: WooCommerce documentation marks this extension as unavailable for new purchases on WooCommerce.com and maintained only for existing users. That means the right approach is cautious: first verify that the integration is still viable, then enable test mode, and only after that decide whether it is safe to use on a live store.

This is not a guide to purchasing the extension itself or working around access restrictions. The focus is strictly on using a plugin you already have: post-install setup, testing, troubleshooting, and choosing alternatives if PAYMILL is no longer a good fit for your store.

What the PAYMILL Payment Gateway Does in WooCommerce

In WooCommerce, a payment gateway is an extension that adds a new payment method to the checkout page. The customer selects the method, enters payment details, and the store receives a response from the payment provider and updates the order status. In the case of WooCommerce Paymill Gateway, that role comes down to connecting the store to the PAYMILL API and displaying card fields at checkout.

The main idea behind the product is to keep the customer on the store checkout instead of sending them to a separate provider page. According to PAYMILL documentation, card data should be processed through the JavaScript Bridge: sensitive card fields are turned into a token, and the store server works only with that token and the private key. The critical security check before using it is this - the store must not store card numbers, CVC values, or expiration dates in its logs, orders, or custom fields.

For the store owner, this creates a smoother payment flow: the customer stays on the checkout page, and the administrator sees the order in the standard WooCommerce interface. For the admin, it also creates extra responsibility: the checkout page must run over HTTPS, JavaScript must not be broken by the theme or optimization tools, and the merchant country and store currency must be supported by PAYMILL.

Where the Gateway Sits in the Order Flow

In simple terms, the flow looks like this: a product is added to the cart, WooCommerce creates the order, the customer selects PAYMILL, the payment details are turned into a token, the gateway sends a request to PAYMILL, and WooCommerce receives the result and assigns the appropriate order status. If the payment is approved, the order usually moves to processing. If the payment is declined or the connection to the provider is interrupted, the order may remain pending payment or end up in an error state.

It is important not to confuse payment with order fulfillment. For a physical product, a successful payment does not mean the order is complete - it still has to be packed and shipped. For digital products, WooCommerce may grant access faster, but that depends on the store settings and the order status. So after configuring the gateway, check more than just the customer-facing message. Review the order notes, status, emails, and the record in the provider account as well.

Who WooCommerce Paymill Gateway Makes Sense For, and Who Should Look Elsewhere

WooCommerce Paymill Gateway fits a very specific situation: you already have a working PAYMILL account, you have access to both the public and private keys, your store operates in a supported merchant country, the store currency is accepted by the provider, and the plugin is already available in your system. If even one of those conditions is not met, setup may end with the payment method simply not appearing at checkout.

When It Can Be a Good Fit

The plugin is worth testing if the store historically used PAYMILL and your goal is to restore, migrate, or carefully validate an existing payment flow. It can also be useful in an internal staging environment where you need to understand a legacy integration before moving to a modern gateway. In that scenario, this guide helps you avoid clicking through settings blindly: you can see which conditions need to line up and which signs show that the integration is actually working.

• The store already has an active PAYMILL account and access to the dashboard with API keys.
• Payments are accepted in a merchant country and currency supported by PAYMILL.
• The site runs over HTTPS, and the checkout is not broken by cache, minification, or JavaScript conflicts.
• You do not need saved cards, automated subscriptions, or advanced payment features not confirmed in this gateway's documentation.

When PAYMILL Should Not Be Your Starting Point

If you are launching a new store from scratch, this product no longer looks like a primary candidate. The official WooCommerce page warns that the extension is no longer available on WooCommerce.com and that the documentation will not be updated. That does not mean every existing site must disable the gateway immediately, but it does mean that for a new project you should compare Stripe, WooPayments, PayPal Payments, Mollie, or a local provider with active support right away.

The riskiest scenario is enabling an old payment gateway on a live checkout without a test order, a key check, and a backup payment method. Even if everything worked before, changes in WooCommerce, the theme, PHP, the SSL certificate, or the payment provider may only show up during a real payment attempt.

What to Check Before Installing and Enabling Payments

Preparation matters more than the Activate button itself. A payment gateway affects money, customer data, order statuses, and transactional emails. A mistake in a regular widget might only affect the look of a page, but a mistake in a payment method can lead to a lost order, a duplicate payment attempt, or a dispute with a customer.

PAYMILL Availability and API Keys

Start by logging in to your PAYMILL account and confirming that you have both public and private keys. PAYMILL documentation separates test keys from live keys. Test keys are for validation without real charges, while live keys should only be used when the store is ready. Do not copy keys into messages, tickets, public repositories, or third-party services. The private key allows payment operations, so it must be handled like a secret.

SSL, Merchant Country, and Store Currency

The official WooCommerce documentation lists an SSL certificate as a mandatory requirement for Paymill Gateway. PAYMILL also limits the countries from which it can serve merchants and separately ties some errors to unsupported currencies or countries. So before installation, verify three things: the site opens over HTTPS, the merchant location is supported by PAYMILL, and the WooCommerce currency matches something the provider is prepared to process.

Theme and Checkout Compatibility

Older gateways were often built for the classic WooCommerce checkout page. If the store uses block-based checkout, an aggressive page builder, JavaScript optimization, or a custom payment template, test the method on a site copy first. For the payment form, it is critical that the PAYMILL Bridge script loads correctly and can return a token. If an optimizer combines, defers, or reorders scripts indiscriminately, the card fields may appear, but the payment button may never complete the process.

A practical rule: first disable unnecessary optimization on checkout, get a stable test payment working, then re-enable performance settings one by one and repeat the check every time.

Installing the Extension and Running the First Admin Check

If the extension ZIP file is already stored in your legitimate project archive or account, installation follows the standard WordPress workflow. In the admin panel, open Plugins, choose Add New, then Upload Plugin, select the ZIP file, click Install Now, and after installation click Activate. At this stage, there is still no reason to enable real payments.

After activation, make sure WooCommerce is not showing critical errors, the plugins page still opens, and the store settings sections are accessible. Then go to the payment settings. In older documentation, the path is listed as WooCommerce > Settings > Checkout > Paymill. In newer WooCommerce interfaces, the section may be called Payments, so use the list of payment methods and the Paymill entry as your guide.

What Should Appear After Activation

The first healthy sign is a separate Paymill payment method or a gateway settings section appearing in WooCommerce settings. If it does not show up, check whether WooCommerce is active, whether the plugin was disabled by a PHP error, and whether the server error log contains a compatibility message. Do not move on to live keys until the basic settings screen opens reliably.

• The extension is active in the plugin list and does not report a fatal error.
• The Paymill settings screen opens without a blank page or WordPress warnings.
• WooCommerce is set to the currency you plan to test.
• The checkout page opens for both guest and logged-in customers.

The short version of this stage is simple: installation is only complete when the method becomes manageable inside WooCommerce settings, not just when the plugin is activated. If you cannot find the settings screen, solve that first, otherwise every next step turns into guesswork.

Post-Install Configuration: Keys, Mode, and Checkout Text

The settings section is the core of working with WooCommerce Paymill Gateway. This is where you decide whether the method is visible to customers, which fields they see, which mode the gateway runs in, and which keys it uses to talk to PAYMILL. A mistake in a single field may not break the entire site, but it can make payments unavailable.

A Setup Order That Lowers Risk

1. Open the Paymill method settings in WooCommerce and do not switch to live mode right away.
2. Enter a clear Title that the customer will recognize among the payment options.
3. Fill in the Description so it is obvious that payment is processed by card through PAYMILL.
4. Enable test mode if that toggle exists in your version of the settings.
5. Copy the test public key into the public key field, and the test private key into the private key field.
6. Save changes with Save Changes and open checkout in a separate window.

Which Settings to Verify First

Focus on functionality before design. The method name and description should stay short: the customer does not need a long technical explanation in a payment radio button. A good approach is a neutral card payment label and a short note that the data is processed through PAYMILL. If the store runs in Russian, you can write the customer-facing text in Russian, but the admin field labels should remain exactly as they appear in the interface.

Test mode must match test keys, and live mode must match live keys. Do not mix them: a test public key with a live private key, or the reverse, can cause errors that look like a generic payment failure. Before the first real payment, take a screenshot of your own settings without exposing the private key and note which fields were changed. That makes it much easier to roll back if the method disappears or orders start failing after activation.

What to Do About Cache and Optimization

Cart, checkout, and account pages cannot be served like ordinary static pages. If a cache plugin or server-side cache stores checkout with another user's session, fails to refresh the nonce, or defers the payment JavaScript, the customer may see a broken form. Add the standard WooCommerce pages to your cache exclusions and separately confirm that the PAYMILL script is not being pushed into a mode that delays execution until after the payment button is clicked.

How to Safely Roll Back a Questionable Change

If the method disappears after saving, reverse the latest changes in the opposite order: disable checkout optimization, re-enable test mode, recheck the keys, temporarily replace the method description with a simpler one, and disable third-party checkout plugins on staging. Do not start by deleting the plugin. First determine whether the method disappears because of PAYMILL conditions, bad keys, or a conflict on the checkout page.

How Card Tokenization Works and Why It Matters for Security

PAYMILL Bridge exists so that sensitive card data does not pass through the store server as ordinary form fields. The customer's browser sends the payment details toward PAYMILL, receives a token, and only that token is passed to the store to complete the operation. This does not remove all security obligations from the store owner, but it does reduce the risk of unnecessary card data ending up in WordPress.

What Happens on the Checkout Page

The customer selects Paymill and enters the card number, expiration date, and CVC. The PAYMILL Bridge script validates the required fields, creates a token, and passes it forward. If the card requires an extra verification step, the payment flow may include an additional stage, such as a bank check. If no token is created, the order should not be treated as paid.

For the administrator, that leads to three practical conclusions. First, you cannot disable JavaScript on checkout or break the loading order of the payment scripts. Second, you should not output card fields through custom theme edits that add ordinary server-submitted attributes to them. Third, you should not enable verbose logging that stores raw payment form data.

What to Check Inside the WooCommerce Order

After a successful payment, the order should show signs that the transaction was processed: the selected method, a status change, order notes, and if the gateway records it, a transaction ID. Do not expect a physical-product order to become completed automatically. In WooCommerce, processing usually means payment was received, but the store still has to fulfill the order. For virtual and downloadable products, the behavior may differ depending on WooCommerce settings.

If the money appears in the provider account but the WooCommerce order is still pending payment, do not change the order status manually until you have compared the order notes, the gateway log, and the PAYMILL record.

Practical Example: Test Product, Test Payment, and Order Verification

This practical scenario is best run on a staging copy of the site. If you do not have one, choose a low-traffic period, enable maintenance mode for non-essential visitors, and disable the backup payment method only for the short duration of the check. The goal of this example is to prove that the customer can see the method, a token is created, the order receives the expected status, the emails are sent, and the administrator knows where to verify the result.

Goal

You want to generate a controlled test order paid through PAYMILL without touching real money and without mixing test keys with live ones. The end result should be visible at checkout: the payment method appears, the form can be submitted, and you understand which order status is assigned after the gateway responds.

Preparation

• Paymill test mode is enabled and the test public/private keys are entered.
• A simple product has been created with a small price that matches the store currency.
• Cart and checkout pages are excluded from cache.
• A browser is open in guest mode or a clean profile without the admin bar.

Verification Steps

1. Add the test product to the cart and proceed to checkout.
2. Fill in the required customer fields, choose Paymill as the payment method, and confirm that the card fields are displayed.
3. Enter the PAYMILL-recommended test payment data and submit the order.
4. After returning to the result page, open the order in the WooCommerce admin panel.
5. Check the order status, notes, selected payment method, and the confirmation record in the PAYMILL dashboard.

Expected Result and One Important Detail

A successful test should end with a clear message to the customer and an order that does not look abandoned. If the order is created but payment is not confirmed, check whether the token was generated and whether the browser blocked the PAYMILL script. If the method does not appear at all, go back to the visibility conditions: keys, country, currency, method enablement, and HTTPS.

Do not use a customer's real card payment as a test. For final validation, it is safer to place a small order of your own only after test mode has passed successfully, and then immediately refund or cancel it according to your store and provider policies.

Checks Before Switching from Test Mode to Live Mode

Going live is not a single toggle. It is a short operating procedure. First make sure a test order succeeds on a clean checkout. Then confirm that the store currency, merchant country, and PAYMILL account are all ready for real transactions. After that, replace the test keys with live keys, save the settings, and run one final low-value control order if that kind of check is acceptable for your store.

Pre-Launch Checklist

• Test mode passed without token errors, JavaScript issues, or incorrect order statuses.
• The private key did not leak into emails, order notes, public HTML, or analytics reports.
• Checkout, cart, and account pages are excluded from full-page caching.
• The customer sees a clear method name and does not see internal technical keys.
• The administrator has a backup payment method or a quick plan for disabling Paymill.

After enabling live mode, do a short monitoring pass: open checkout as a guest, verify that the method is visible, perform an acceptable control transaction, compare the order and provider record, and then review the WordPress and server error logs. If anything looks unstable at any point, switch back to test mode or temporarily disable the method until you understand the cause.

What Not to Change at the Same Time

Do not combine the move to live keys with a WooCommerce update, a theme switch, a site migration, a new cache plugin, or checkout edits. If something breaks, you will not know which variable affected payments. For payment changes, the one-variable rule is safer: changed the keys - test; enabled optimization - test; updated the theme - test checkout again.

Gateway-Specific Behavior, Limits, and Practical Solutions

WooCommerce Paymill Gateway has several characteristics that should not be treated as minor details. They directly affect who the product is suitable for, how checkout should be built, and what expectations the store owner should have.

The Method Can Be Hidden Because of Keys, Country, or Currency

WooCommerce documentation explicitly lists three reasons the method may not appear: API keys are missing, the merchant country is not supported by PAYMILL, or the store uses an unsupported currency. So do not start troubleshooting with the theme or CSS until you have verified the provider's baseline conditions. A visual problem usually looks different: the radio button is there, but the form looks broken. If the radio button is missing, start with the gateway settings and availability conditions.

Saved Cards and Subscriptions Are Not Confirmed for This Extension

The WooCommerce FAQ for Paymill Gateway states that storing card details for returning customers and subscription support are not implemented in the documented extension. This matters most for stores with repeat purchases, membership access, recurring charges, and subscription products. If your business model depends on automatic renewals, you should use a gateway that officially supports WooCommerce Subscriptions and saved payment methods.

Direct Card Fields Require Discipline on Checkout

Because the customer enters card data inside the store, the administrator needs to watch every script loaded on the payment page carefully. Marketing pixels, third-party widgets, chat tools, and aggressive optimization plugins can interfere with the payment form or broaden the security review surface. For a payment page, less third-party code and more predictability is usually the safer choice. If a script is not necessary for checkout, remove it from the payment page.

Troubleshooting Common Checkout and Order Issues

Payment gateway issues are best diagnosed by symptoms. The same visible result - for example, a customer being unable to pay - may be caused by a bad key, an unsupported currency, broken JavaScript, an SSL problem, or a checkout conflict. The map below is a practical place to begin.

Common symptoms and safe actions

Symptom	Possible Cause	What to Check	How to Fix It
Paymill does not appear among the payment methods.	Keys are missing, the method is disabled, or the country or currency is unsupported.	The key fields, test mode, WooCommerce currency, and merchant country.	Enter the correct key pair, enable the method, choose a supported currency, or temporarily disable the gateway.
The card fields are visible, but the order will not submit.	The Bridge script is not generating a token or is conflicting with JavaScript optimization.	The browser console, cache exclusions, and deferred script loading on checkout.	Exclude checkout from optimization, disable script bundling on the payment page, and retest.
An error appears about invalid payment details.	The card, currency, country, or test data does not match the scenario.	The PAYMILL test data, the order currency, and the test/live mode setting.	Use the correct test data and matching keys, and do not mix modes.
The order is created, but it does not look paid.	The provider did not confirm the transaction, or WooCommerce did not receive a valid response.	Order notes, status in PAYMILL, and WooCommerce and server logs.	Verify the transaction in the provider account, do not release the product before confirmation, and repeat the test after fixing the cause.
The browser or server reports an SSL problem.	The site certificate, trust chain, or server-side SSL library is configured incorrectly.	The HTTPS checkout page, certificate validity and chain, and server errors.	Fix the certificate, update server components through your hosting provider, and do not accept payments until the issue is resolved.

When It Is Better to Roll Back Changes

A rollback is not only for a completely broken site. Temporarily disable Paymill if the payment method appears and disappears inconsistently, if test mode does not pass reliably, if the orders do not contain clear notes about the transaction result, or if a customer can land on a success page without confirmed payment. In a payment integration, instability is worse than an honestly disabled method.

What to Log and What Must Never Be Logged

Logs are useful for finding the cause, but they must never contain card data or private keys. Acceptable log details include technical statuses, order IDs, provider error codes, and transaction timestamps. Raw checkout POST data, full key values, card numbers, CVC values, and expiration dates are not acceptable. If you enable debugging, keep it short-lived and clean up unnecessary records after the check is complete.

Supporting a Legacy Gateway, Handling Updates, and Planning a Migration

The main long-term risk of Paymill Gateway is its support status. When documentation is left only for existing users and no longer updated, the store owner should treat the gateway as a legacy integration. That is not a reason to break a working checkout immediately, but it is a reason to have a plan: how to disable the method quickly, which backup gateway to enable, which orders may need manual review, and when to move to a modern integration.

How to Manage an Existing Store

If PAYMILL is already working, do not update everything at once. Before any major WordPress, WooCommerce, PHP, or theme update, create a site copy and rerun the test scenario. After the update, verify checkout, the order, emails, and statuses. If the plugin has not been updated in a long time, pay especially close attention to PHP warnings, compatibility with newer checkout behavior, and conflicts with optimization tools.

A Backup Payment Method

For an online store, it is useful to have at least one backup method: bank transfer, PayPal, Stripe, WooPayments, Mollie, or a local provider that matches the store's country and currency. The backup does not need to be the primary method, but it gives you a way to keep taking orders while you troubleshoot Paymill. Add the fallback method carefully: the customer should understand how the payment options differ, and the administrator should understand how each method affects order status.

If you decide to keep the legacy gateway after testing, download and store a working copy of the documentation locally, a list of settings without secrets, a shutdown procedure, and the names of the people responsible for it. If you decide to move to another method, do not disable Paymill until the new gateway has passed a full test order and order-status verification.

When WooCommerce Paymill Gateway Is a Reasonable Choice

WooCommerce Paymill Gateway makes sense when the store already has an established PAYMILL history, known working keys, a confirmed supported country and currency, and an owner who is prepared to maintain a legacy integration carefully. In that case, the plugin can still do its job: add PAYMILL payments to WooCommerce checkout and pass the result back into the WooCommerce order flow.

If you are still choosing a payment system, want subscriptions, saved cards, modern express methods, and long-term support, treat Paymill as a legacy option rather than a starting point. Compare alternatives, test order-status behavior, and do not leave the store without a backup payment method.

The main takeaway is simple: start with test mode, then verify the order, then switch to live keys, and only after that allow real customers through. That sequence protects the store from most of the problems caused by enabling a payment gateway too quickly.