Paddle for WooCommerce,
the easy way

PimiPay is a WooCommerce Paddle plugin that integrates Paddle Billing with your store. It handles product synchronization, one-time and recurring checkout, refunds, real-time webhooks, and automatic order management — so you can accept payments worldwide with minimal setup.

It is a WordPress plugin that you install on your own site. Nothing is hosted for you and your store does not move anywhere: orders, customers and products stay in your own WordPress database, and Paddle is used only to take the payment and handle the tax. That is the difference between this and selling through a hosted storefront, where your catalogue and customer records live on someone else's platform.

Yes, you need an active Paddle Billing account. You can sign up for free at paddle.com. The plugin works with both sandbox (staging) and production environments for easy testing before going live.

- PHP 8.3 or higher - WordPress 7.0.3 or higher - WooCommerce 4.0 or higher - An active Paddle Billing account - SSL certificate (HTTPS required for webhooks)

Yes. The plugin fully supports WooCommerce High-Performance Order Storage (HPOS), which is the modern order storage architecture. Your store is future-proof whether you use HPOS or the legacy post-based order storage.

Yes. The gateway is registered with the WooCommerce Cart & Checkout Blocks as well as the classic checkout, so Paddle appears as a payment method either way and payment completes on the order confirmation page in both flows. Availability is decided on the server, so the method disappears from the block checkout when the API is not configured or a cart item has not been synced to Paddle. Stores on a WooCommerce version without Blocks are unaffected.

Yes. PimiPay for Paddle registers as a standard WooCommerce payment gateway. Customers can choose between Paddle and any other active gateways (Stripe, PayPal, etc.) at checkout.

Yes. The plugin fully supports both simple and variable products. Each variation is synced as a separate price in Paddle, allowing customers to purchase any variation through the checkout modal.

Yes, since version 1.7.0. Set Pricing to Order total (WooCommerce → Settings → Payments → Paddle) and the plugin creates the Paddle transaction from the order's own lines, after WooCommerce has applied the coupon. Paddle then charges exactly the total the customer saw in the cart, and the Paddle checkout shows that figure when it opens. In the default Catalog price mode, Paddle charges the price synced to each product, so a WooCommerce coupon cannot be applied. Rather than overcharge, the plugin hides the Paddle payment method when the cart carries a coupon discount, and the customer is shown your other gateways instead. Paddle's own discount-code field is a separate thing: a code entered there reduces what Paddle charges without changing the WooCommerce order. If all your discounts are WooCommerce coupons, the Discount Codes setting hides that field so customers see one place to enter a code.

They decide what Paddle charges, and you pick one in the Pricing setting. - Catalog price (the default) opens the checkout with the Paddle price synced from each product. It is how the plugin has always worked: the amount lives in Paddle, and WooCommerce coupons and fees do not reach it. A cart with a coupon discount or a negative fee hides the gateway rather than charging the wrong amount. - Order total creates the Paddle transaction from the WooCommerce order itself — its line items, fees and shipping lines — with fixed amounts. Whatever changed the total in WooCommerce is charged by Paddle as WooCommerce recorded it, and the Paddle checkout opens showing that real total. Products must be synced to Paddle in both modes, because each line references its Paddle product for reporting, but in Order total mode the synced price no longer matters. Tax follows your Paddle account setting in both modes: added on top for a tax-exclusive account, carved out for a tax-inclusive one. In Order total mode the transaction is prepared before the checkout opens and reused if the customer reloads the page. If the order changes, a fresh one is created; paying either still marks the order paid, and an order note records any amount mismatch. Order total is opt-in in 1.7.0, and a later release will make it the default.