Paypercut Payments for WooCommerce

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 via their hosted checkout interface. 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.