Description
Take card payments in your WooCommerce store through the PayLolly gateway.
- Works with the block checkout (the default in current WooCommerce) and with the classic checkout.
- The card is sent from the customer’s browser straight to PayLolly, which gives back a token: card numbers never reach your server and are never stored.
- Saved cards for logged in customers (optional), refunds from the WooCommerce order screen, and subscription renewals with WooCommerce Subscriptions (optional).
- Compatible with High-Performance Order Storage (HPOS).
- Clear reporting when PayLolly refuses something: a private note on the order, a notice for administrators after repeated failures, and plain instructions for the shopper when the card details need correcting.
- The payment method is only offered at checkout when it is set up (merchant id and key present, HTTPS in live mode); the configuration problems are shown to administrators only.
You need a PayLolly merchant account. The plugin is translation ready: translations are contributed on translate.wordpress.org.
External services
This plugin sends payment data to the PayLolly payment service. Without it the plugin cannot take payments.
PayLolly API (https://api.paylolly.app for live payments, https://api.stg.paylolly.app when “Enable Test Mode” is on)
- What it is used for: creating card payments, refunds and subscription renewals, and getting a short-lived session key for the card form.
- What is sent, and when:
- At checkout, when the customer places an order: the order amount and currency, the order number, the billing name, email address, phone number and address, the customer’s IP address, the merchant id, the card token and the encrypted security code made by the card form (never the card number), the address of the thank you page and of the store’s notification URL.
- When a refund is made from the order screen: the merchant id, the amount and the PayLolly payment id.
- When a subscription renewal is charged (WooCommerce Subscriptions): the merchant id, the amount, the currency and the saved card token.
- When a checkout page is shown (and when a page that has been open too long asks for a new key): a request for a session key, authenticated with your merchant key. Your merchant key is only ever sent from your server and is never shown to visitors.
- Every request from the server carries a User-Agent that names the plugin version and the WordPress, WooCommerce and PHP versions. It contains no store address, merchant id or customer data.
- The customer’s browser calls PayLolly directly from the checkout page: the card form sends the card number, the expiry date and the security code to PayLolly’s tokenisation endpoint (https://api.paylolly.app/api/rest/v1.0/TokenJS/, or the api.stg.paylolly.app equivalent in test mode) using the short-lived session key, and receives a token and an encrypted security code in return. No other script is loaded from another host: the scripts of the plugin are part of the plugin.
- PayLolly also posts a signed notification to your store when a payment is approved. The plugin checks the signature before it marks an order as paid.
- Terms of service: https://paylolly.com/legal/terms-of-service
- Privacy policy: https://paylolly.com/legal/privacy-policy
Installation
- Install the plugin and activate it through the “Plugins” menu in WordPress. WooCommerce must be active.
- Go to WooCommerce > Settings > Payments > PayLolly and enter the merchant id and key of your PayLolly merchant account (use the test ones while “Enable Test Mode” is on).
- Tick “Enable PayLolly Gateway” and save.
FAQ
Does it work with the block checkout?
Yes, since version 2026.11.12. The classic checkout keeps working too.
Where do I find my merchant id and key?
In your PayLolly portal. Use the test keys while “Enable Test Mode” is on, and the live keys when it is off. The key stays on your server: the browser only gets a time limited session key.
Does it need PHP 8.3?
Yes. PHP 8.3 is the version WooCommerce requires, and it gets security fixes until the end of 2027. A site on an older PHP is told by WordPress that this update is not compatible and keeps the version it has.
Why is the payment method not shown at checkout?
It is only offered when it is set up: both the merchant id and the key of the current mode must be entered, and live mode needs the store to be served over HTTPS. Administrators see what is missing in the WordPress admin.
What happens when PayLolly refuses a payment?
The customer is told what to do when it is something they can fix (for example a mistyped card number); otherwise they see a general message. The administrator gets a private note on the order with PayLolly’s error code, and after repeated failures a notice in the admin area. The notes and the log (WooCommerce > Status > Logs, source paylolly) never contain card data, tokens or keys.
Is it translated?
The plugin is translation ready. Translations are contributed on translate.wordpress.org.
Changelog
2026.11.12
- Security: the “payment approved” notification from PayLolly is now verified (SHA-512 signature made with your merchant key) and checked against the order (payment id, merchant reference, amount and currency) before an order is marked as paid. Before, anyone who knew an order number could mark it as paid.
- Security: a refund is reported as done only when PayLolly confirms it; a refused or failed refund now shows an error instead of a success note.
- Block checkout support (WooCommerce Blocks), including saved cards.
- High-Performance Order Storage (HPOS): order data is read and written through the WooCommerce order object.
- Needs PHP 8.3 or higher.
- The customer returns to the order page after the payment, and the order gets the customer’s phone number, IP address and a reference in the PayLolly portal.
- The session key for the card form is cached for 15 minutes instead of being requested on every page view, and is renewed when a page has been open too long.
- Failed or unreadable answers from PayLolly give the customer a clear message instead of an error; a card tokenisation error is reported on the checkout page, with specific advice for the common card mistakes.
- Refusals from PayLolly are reported to the merchant: a private order note with PayLolly’s error code, an admin notice after repeated failures, and log entries at error level.
- A store that is not set up (no merchant id or key, or live mode without HTTPS) no longer shows a message to shoppers: the payment method is simply not offered, and the problem is shown to administrators.
- Fixes for WooCommerce Subscriptions renewals (hook name and order lookup).
- Fixes for PHP 8.2 and later (no deprecation notices), the plugin no longer errors when WooCommerce is not active, and all texts are translatable.
- A User-Agent that names the plugin version is sent with every request to PayLolly.
1.0.0
- First release.
