Title: Paypercut Payments for WooCommerce Author: Paypercut Dev Published: 14 Gennaio 2026 Last modified: 4 Ottobre 2026 --- Ricerca i plugin ![](https://ps.w.org/paypercut-payments-for-woocommerce/assets/banner-772x250.png? rev=3593040) ![](https://ps.w.org/paypercut-payments-for-woocommerce/assets/icon-256x256.png? rev=3593040) # Paypercut Payments for WooCommerce Di [Paypercut Dev](https://profiles.wordpress.org/paypercutdev/) [Scarica](https://downloads.wordpress.org/plugin/paypercut-payments-for-woocommerce.0.2.4.zip) * [Dettagli](https://it.wordpress.org/plugins/paypercut-payments-for-woocommerce/#description) * [Recensioni](https://it.wordpress.org/plugins/paypercut-payments-for-woocommerce/#reviews) * [Installazione](https://it.wordpress.org/plugins/paypercut-payments-for-woocommerce/#installation) * [Sviluppo](https://it.wordpress.org/plugins/paypercut-payments-for-woocommerce/#developers) [Supporto](https://wordpress.org/support/plugin/paypercut-payments-for-woocommerce/) ## Descrizione Make it easy for customers to pay — and easier for you to manage — with Paypercut for WooCommerce. This plugin brings fast, secure, and intuitive checkout to your online shop, helping you boost conversions and streamline operations. Paypercut enables a range of trusted payment methods while giving you a single, unified view of all your transactions — whether online or in person. Whether you’re selling physical products or digital downloads, Paypercut for WooCommerce makes taking payments effortless — so you can focus on growing your online business. ### External services This plugin connects to the Paypercut Payments API (api.paypercut.io) to process payments and manage checkout sessions for your WooCommerce store. This connection is required for the plugin to function, as all payment processing is handled through Paypercut’s secure infrastructure. **What the service is used for:** * Creating and managing payment checkout sessions* Processing customer payments securely * Verifying payment status and updating order status * Managing refunds for completed orders * Setting up and managing webhooks for payment notifications **What data is sent and when:** The plugin sends data to Paypercut’s API (https://api.paypercut.io/) in the following scenarios: * **During checkout session creation** (when a customer initiates checkout): - Store information (store name, store URL, WooCommerce order identifiers) - Order details (order total, currency, line items, shipping costs, tax amounts) - Customer billing information (name, billing address, email address) - Customer shipping information (if applicable: shipping name and address) - Technical metadata (session identifiers, return URLs, webhook URLs) * **During payment verification** (when verifying payment status): - Checkout session identifiers - Order identifiers * **During refund processing** (when a store administrator issues a refund): - Payment intent identifiers - Refund amount and currency - Refund reason (if provided) * **During webhook setup** (when configuring the plugin): - Webhook URL for payment notifications - Webhook event types to subscribe to * **During API credential validation** (when testing connection in settings): - API credentials for authentication purposes only * **During a debug session** (only while a store administrator has explicitly started one): * Debug sessions are **off by default**. A store administrator starts one from WooCommerce > Settings > Payments > Paypercut, after confirming a consent dialog. The session lasts about 60 minutes and then stops on its own; it can also be stopped at any time. While it is running, the plugin sends diagnostic data to the Paypercut telemetry service (https://telemetry.paypercut.io/): - Plugin, WordPress, WooCommerce, PHP and theme versions - The plugins active on this store and their versions - How this store has the Paypercut gateways configured (which checkout mode is selected and which options are switched on — never the values of your credentials) - A record of each checkout, refund and payment notification the plugin handled and whether it succeeded, identified by WooCommerce order number and Paypercut payment reference - When an order is created and how many products, fees, coupons and shipping lines it carries - The names of any fees another plugin adds to the basket - When something fails, the error message, the file and line it came from, and which plugin or theme raised it - When the session started and stopped * **Not sent:** customer names, email addresses, billing or shipping addresses, order totals, product names and prices, payment card data, the reason text you type when issuing a refund, or any API key, webhook secret or password. * Starting a session also sends your API key once, over HTTPS, to the Paypercut API (https://api.paypercut.io/) to obtain a short-lived diagnostic token. Your API key is never sent to the telemetry service itself. * Paypercut keeps this diagnostic data for 30 days. **Important:** Payment card data (credit card numbers, CVV codes, etc.) is collected and processed directly by Paypercut through its secure checkout components. This sensitive payment information never passes through or gets stored by this plugin or your WordPress site. **Service provider:** This service is provided by Paypercut. For more information about how Paypercut handles data, please refer to: * Privacy policy: https://paypercut. com/privacy-policy ### Development This plugin uses npm and @wordpress/scripts (which uses webpack) to build the Blocks checkout integration. ### Source Code Location **IMPORTANT:** The human-readable source code for all compiled JavaScript is included in this plugin. The minified/compiled file `assets/build/index.js` is generated from the following source file: * **Source file:** `assets/blocks/index.js` – This is the human-readable, unminified source code for the Blocks checkout integration All source code is included in the published plugin. The source file (`assets/blocks/ index.js`) contains the original, readable JavaScript code with ES6 modules, comments, and proper formatting. The compiled version (`assets/build/index.js`) is generated from this source using the build process described below. ### Building assets To rebuild the compiled assets from source: 1. Install dependencies: `bash npm install 2. Build production assets: `bash npm run build This will compile `assets/blocks/index.js` into the minified `assets/build/index. js` using @wordpress/scripts. ## Screenshot [[ [[ ## Installazione 1. Upload the plugin files to the `/wp-content/plugins/paypercut-payments-for-woocommerce` directory, or install the plugin through the WordPress plugins screen directly. 2. Activate the plugin through the ‘Plugins’ screen in WordPress. 3. Navigate to WooCommerce > Settings > Payments and configure Paypercut Payments. 4. Enter your API credentials from your Paypercut account. 5. Save changes and start accepting payments. ## FAQ ### Do I need a Paypercut account? Yes, you need a Paypercut account and API credentials to use this plugin. ### Does this plugin work with WooCommerce Blocks checkout? Yes, this plugin supports both Classic and Blocks checkout. ### Is this plugin secure? Yes, all payment processing is handled securely through Paypercut’s infrastructure. The plugin follows WordPress and WooCommerce security best practices. ## Recensioni Non ci sono recensioni per questo plugin. ## Contributi e sviluppo “Paypercut Payments for WooCommerce” è un software open source. Le persone che hanno contribuito allo sviluppo di questo plugin sono indicate di seguito. Collaboratori * [ Paypercut Dev ](https://profiles.wordpress.org/paypercutdev/) * [ paypercut ](https://profiles.wordpress.org/paypercut/) [Traduci “Paypercut Payments for WooCommerce” nella tua lingua.](https://translate.wordpress.org/projects/wp-plugins/paypercut-payments-for-woocommerce) ### Ti interessa lo sviluppo? [Esplora il codice](https://plugins.trac.wordpress.org/browser/paypercut-payments-for-woocommerce/) segui il [repository SVN](https://plugins.svn.wordpress.org/paypercut-payments-for-woocommerce/), segui il [log delle modifiche](https://plugins.trac.wordpress.org/log/paypercut-payments-for-woocommerce/) tramite [RSS](https://plugins.trac.wordpress.org/log/paypercut-payments-for-woocommerce/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 0.2.4 * Stability Improvements #### 0.2.3 * Stability improvements. #### 0.2.2 * Stability improvements. #### 0.2.1 * Updated compatibility information for WordPress 7.1 and WooCommerce 11.0. No checkout behavior changed. #### 0.2.0 * Added Elements Checkout as an optional checkout experience across Checkout Blocks, Classic Checkout, Pay for Order, and Add payment method. * Added Apple Pay and Google Pay to ordinary checkout, plus Express Checkout on supported product, cart, mini-cart, and checkout placements. * Added migration statuses and explicit checkout-experience controls. Upgrading preserves your current Checkout Widget or Hosted Checkout selection. * Improved payment reliability with duplicate-payment protection, customer-action handling, payment-status recovery, and expanded diagnostics. * Checkout Widget and Hosted Checkout remain available. #### 0.1.31 * Added debug sessions: when Paypercut support needs to see what your store is doing, you can start a session from the gateway settings that sends diagnostics for about an hour and stops by itself. Nothing is sent when no session is running. * Debug sessions can now be started on any store. They previously refused with a message about the connection not recording an environment. * Payment confirmations from Paypercut now arrive on stores that already had a webhook registered. Those stores held no signing secret for it and refused every notification, so orders were left unconfirmed. * Order status is now reported accurately in a debug session, instead of showing orders as pending after they had already moved on. * When a Paypercut request is refused, the reason is now recorded rather than a generic transport error. #### 0.1.30 * Mapped shipping_options and tax_rate in Paypercut Checkout creation flow #### 0.1.29 * Update the bundled Paypercut Checkout SDK to the latest version, which fixes the Apple Pay pop-up so it opens detached during checkout. #### 0.1.28 * Embedded checkout now records your WooCommerce order number on the payment even when the order total no longer matches the amount that was paid, so those payments can still be matched to their order in the Paypercut dashboard. #### 0.1.27 * The Mode column in the Shop Domain / Payment Domains table now correctly shows whether each domain is in live or test mode. Previously it always showed “Test mode” regardless of your actual setup. #### 0.1.26 * Prevent duplicate charges when an embedded checkout submission fails after the payment already succeeded: the paid checkout session is reused on retry and payment status is verified with the Paypercut API on the server. * Fix a stale “Pay now” banner on paid orders when the active theme’s thank-you template does not fire the woocommerce_before_thankyou hook. #### 0.1.25 * Changed embedded checkout layout view”. #### 0.1.24 * Change default payment method button title from “Pay with Paypercut” to “Pay with Card”. #### 0.1.23 * Recover checkout webhooks that arrive before the WooCommerce order has finished saving: the plugin now returns a retryable response so Paypercut re-delivers the notification until the order can be linked, replacing the previous local scheduled-retry mechanism. #### 0.1.22 * Updated Greek translations #### 0.1.21 * Improve Blocks checkout appearance: remove highlight border on the selected payment option and replace with a subtle neutral outline. * Fix accordion content padding in Blocks checkout. * Remove embedded checkout container padding to prevent content overflow on small mobile screens. #### 0.1.20 * Complete paid Paypercut orders through WooCommerce’s canonical payment completion flow for better compatibility with WooCommerce emails, fulfillment, and third- party integrations. * Add an order note when a verified Paypercut webhook finds an order that has already been processed, so store operators can see the webhook was received and verified. #### 0.1.19 * Improve checkout compatibility when layout plugins render Classic checkout markup on a Blocks checkout page. * Prevent Paypercut from falling through to WooCommerce payment verification before a checkout session is created in hybrid checkout layouts. * Bundle the latest Paypercut checkout SDK build. #### 0.1.18 * Verify redirected checkout payment status before updating WooCommerce orders. #### 0.1.17 * Improve embedded modal checkout so payment processing shows a merchant-page warning and asks for confirmation before closing. #### 0.1.16 * Prevent duplicate WooCommerce order emails when webhook and thank-you page payment verification arrive at the same time. * Make Paypercut payment confirmation idempotent across webhook, Classic checkout, Blocks checkout, and return-page verification flows. #### 0.1.15 * Improve embedded checkout reliability for Classic and Blocks checkout flows. * Add Greek translations. * Bundle the stable Paypercut checkout SDK. #### 0.1.14 * Add Paypercut Connect setup for account-based API credential provisioning. * Add connected account details, test mode badge, disconnect, and switch account actions to gateway settings. * Add webhook and payment domain management sections with registration dialogs. * Add SSL certificate warning with dismiss support. * Improve Paypercut Connect setup reliability and error handling. #### 0.1.13 * Stability improvements #### 0.1.12 * Stability improvements #### 0.1.11 * Stability improvements #### 0.1.10 * Update order reference in Paypercut Dashboard * Improve webhook handling * Stability improvements #### 0.1.9 * Return non 200 when webhook handling cannot find order #### 0.1.8 * Stability improvements #### 0.1.7 * Stability improvements #### 0.1.6 * Bugfix: wrong currency handling for custom currency setup #### 0.1.5 * Make default order status `processing` #### 0.1.4 * Add option to select completion status for order after payment * Stability improvements * UX improvements #### 0.1.3 * Add compatibility with custom order tables for WooCommerce #### 0.1.2 * Stability improvements #### 0.1.1 * Add support for paying abandoned checkouts #### 0.1.0 * Initial release * Support for Classic and Blocks checkout * Secure payment processing * API credential validation * Webhook support ## Meta * Versione **0.2.4** * Ultimo aggiornamento **4 giorni fa** * Installazioni attive **100+** * Versione WordPress ** 6.6 o superiore ** * Testato fino alla versione **7.1.3** * Versione PHP ** 8.1 o superiore ** * Lingua * [English (US)](https://wordpress.org/plugins/paypercut-payments-for-woocommerce/) * Tag * [checkout](https://it.wordpress.org/plugins/tags/checkout/)[ecommerce](https://it.wordpress.org/plugins/tags/ecommerce/) [payment gateway](https://it.wordpress.org/plugins/tags/payment-gateway/)[payments](https://it.wordpress.org/plugins/tags/payments/) [woocommerce](https://it.wordpress.org/plugins/tags/woocommerce/) * [Visualizzazione avanzata](https://it.wordpress.org/plugins/paypercut-payments-for-woocommerce/advanced/) ## Valutazioni Non sono state ancora inviate recensioni. [La tua recensione](https://wordpress.org/support/plugin/paypercut-payments-for-woocommerce/reviews/#new-post) [Vedi tutte le recensioni](https://wordpress.org/support/plugin/paypercut-payments-for-woocommerce/reviews/) ## Collaboratori * [ Paypercut Dev ](https://profiles.wordpress.org/paypercutdev/) * [ paypercut ](https://profiles.wordpress.org/paypercut/) ## Supporto Problemi risolti negli ultimi due mesi: 0 su 1 [Chiedi nel forum di supporto](https://wordpress.org/support/plugin/paypercut-payments-for-woocommerce/)