Hemal

<p><strong>PII Tokenizer</strong> allows website owners to secure Personally Identifiable Information (PII) such as first name, last name, email, phone, and address in WordPress forms. With seamless integration and a modern admin interface, this plugin provides:<br />
– Vaultless tokenization and detokenization of PII fields via Java-based APIs.<br />
– Dynamic buttons for “Tokenize” functionality appended to form fields for easy usage.<br />
– API key registration after email verification, with secure client ID generation.<br />
– Compatibility with popular WordPress form plugins like WPForms and Gravity Forms.</p>
<p>Key Features:<br />
– Protect sensitive data by tokenizing form fields.<br />
– Use individual “Tokenize” buttons for profile and address fields.<br />
– Easily detokenize data when required.<br />
– Modern admin interface for API key registration and management.<br />
– Backend integration with customizable Java tokenization and detokenization services.</p>
<h3>External Services</h3>
<p>This plugin connects to external APIs to provide vaultless tokenization and detokenization services for Personally Identifiable Information (PII). These services are required to tokenize or detokenize sensitive data securely.</p>
<h3>External API Endpoints</h3>
<ol>
<li>
<p><strong>Vaultless Tokenization API</strong></p>
<ul>
<li><strong>Purpose</strong>: The Vaultless Tokenization API is used to convert sensitive PII fields such as name, email, mobile, and address into secure tokens.</li>
<li><strong>Data Sent</strong>: When a user initiates tokenization, the plugin sends the following data to the external API:
<ul>
<li>The specific field data (e.g., name, email, address).</li>
<li>API key for authentication.</li>
</ul>
</li>
<li><strong>Conditions</strong>: This API is triggered when the “Tokenize” button is clicked by the user in a form integrated with the plugin.</li>
<li><strong>Service Provider</strong>: Samuday Technology Services</li>
</ul>
</li>
<li>
<p><strong>Detokenization API</strong></p>
<ul>
<li><strong>Purpose</strong>: The Detokenization API is used to convert secure tokens back into their original PII form.</li>
<li><strong>Data Sent</strong>: When a user initiates detokenization, the plugin sends the following data to the external API:
<ul>
<li>The tokenized data (e.g., tokenized name or address).</li>
<li>API key for authentication.</li>
</ul>
</li>
<li><strong>Conditions</strong>: This API is triggered when the “Detokenize” button is clicked by the user in a form integrated with the plugin.</li>
<li><strong>Service Provider</strong>: Samuday Technology Services</li>
</ul>
</li>
<li>
<p><strong>Address Tokenization and Detokenization APIs</strong></p>
<ul>
<li><strong>Purpose</strong>: These APIs are specifically designed to handle tokenization and detokenization of address data. </li>
<li><strong>Data Sent</strong>: The following data is sent when address-related actions are triggered:
<ul>
<li>Complete address JSON (e.g., street, city, zip code).</li>
<li>API key for authentication.</li>
</ul>
</li>
<li><strong>Conditions</strong>: This API is triggered when address tokenization or detokenization actions are performed via the respective buttons in a form.</li>
<li><strong>Service Provider</strong>: Samuday Technology Services</li>
</ul>
</li>
</ol>
<h3>License</h3>
<p>This plugin is released under the GPLv2 (or later). You can find the license details here: https://www.gnu.org/licenses/gpl-2.0.html</p>


PII Tokenizer

Secure Personally Identifiable Information (PII) with vaultless tokenization. Easily tokenize and detokenize profile and address fields in your forms  …

PayPlus Tech Team

<p>PayPlus Payment Gateway for WooCommerce<br />
Accept debit and credit cards on your WooCommerce store in a secure way with the ability to design your own payment page and add high functionalities to it. SSL is not required.</p>
<p><strong>Supported PHP Versions:</strong><br />
This plugin is compatible with PHP versions from 7.4 up to 8.3.</p>
<p>Before installation:<br />
You need your account credentials. For that, you have to contact PayPlus and to join the service.</p>
<p>Plugin Disclaimer:<br />
PayPlus does not accept liability for any damage, loss, cost (including legal costs), expenses, indirect losses or consequential damage of any kind which may be suffered or incurred by the user from the use of this service.</p>
<p>It is important to know that this plugin relies on third-party services.<br />
However, the third-party so mentioned is the PayPlus core engine at their servers – the providers of this plugin.</p>
<p>By being a payment processor, just like many of its kind, it must send some transaction details to the third-party server (itself) for token generation and transaction logging statistics and connecting to invoices.</p>
<p>It is this transfer back and forth of data between your WooCommerce and the PayPlus servers that we would like to bring to your attention clearly and plainly.</p>
<p>The main links to PayPlus, its terms and conditions, and privacy policy are as listed:<br />
– Home Page: https://www.payplus.co.il<br />
– Plugin Instruction page: https://www.payplus.co.il/wordpress<br />
– Terms and Conditions: https://www.payplus.co.il/privacy</p>
<p>The above records, the transaction details, are not treated as belonging to PayPlus and are never used for any other purposes.</p>
<p>The external files referenced by this plugin, due to WordPress policy recommendations, are all included in the plugin directory.</p>
<h3>8.2.1  – 10-06-2026</h3>
<ul>
<li>Fix       – Payment page: prevented duplicate payment page creation per order by saving the meta fields the existing duplicate-prevention guard relies on. Eliminates duplicate PRUID entries.</li>
</ul>
<h3>8.2.0  – 07-06-2026</h3>
<ul>
<li>Fix       – Cron: when “Exclude manually cancelled orders from cron” checkbox is enabled, orders cancelled by an admin or shop manager are now excluded from cron instead of deleting payment data.</li>
<li>Fix       – Cron: order status change hook registers only once, preventing duplicate order notes. Works for admins and shop managers via admin, AJAX, or REST.</li>
<li>Fix       – Cron: minimum order age reduced to 10 minutes for faster processing.</li>
<li>Tweak     – Settings: cancel checkbox relabeled to “Exclude manually cancelled orders from cron”.</li>
</ul>
<h3>8.1.9  – 03-06-2026</h3>
<ul>
<li>Fix       – Blocks checkout: validation errors no longer show a persistent PayPlus error popup; WooCommerce native inline notices are used instead.</li>
<li>Fix       – Blocks checkout: corrected set_payment_details calls to pass arrays instead of strings, preventing PHP foreach warnings.</li>
<li>Fix       – Hosted Fields: card number field now shows a green checkmark when card brand is detected.</li>
<li>Fix       – Hosted Fields: lock and CVV icons now use inline data URIs, eliminating CORS errors on local/dev environments.</li>
<li>Fix       – SEO: noindex meta tag for error page no longer incorrectly applied to other pages.</li>
</ul>
<h3>8.1.8  – 19-05-2026</h3>
<ul>
<li>Feature   – Invoice+ Documents: Added POS EMV to the “Do not create documents” exclusion list.</li>
<li>Fix       – Invoice+ Documents: POS EMV exclusion now works correctly (POS EMV orders are detected via transaction meta).</li>
<li>Fix       – Invoice+ Documents: Payment method detection now uses alternative_method_name (bit, apple-pay, google-pay) when available.</li>
<li>Fix       – Invoice+ Documents: Payment query is now HPOS-compatible (queries correct meta table on High-Performance Order Storage sites) – Fix for docs that came out as other instead of payment app.</li>
<li>Fix       – Payment meta is now fully stored before order save, preventing race conditions with automatic invoice creation hooks.</li>
</ul>
<h3>8.1.7  – 05-05-2026</h3>
<ul>
<li>Fix       – Resolved WC_Order_Item_Coupon::offsetGet deprecation notice (since WooCommerce 4.4.0) when coupons are applied at checkout.</li>
<li>Feature   – Refund fee: Option to automatic 5% or 100 NIS (whichever is lower) refund fee for PayPlus refunds.</li>
<li>Feature   – POS Only Mode option for dedicated POS terminal setups.</li>
<li>Fix       – Hide PayPlus Gateway checkbox now works reliably for all checkout types (Classic and Blocks), regardless of Hosted Fields or EMV configuration.</li>
<li>Fix       – Hosted Fields: resolved duplicate rendering issues on Blocks checkout.</li>
<li>Fix       – Subscriptions: token now correctly retrieved from subscription or parent order (ON ALL CASES).</li>
<li>Fix       – Blocks checkout: payment errors now display correctly to frontend users.</li>
<li>Fix       – Cron job no longer fires at order creation, only at scheduled intervals.</li>
<li>Tweak     – Optimized user_has_cap filter: now registers only once and only in admin, eliminating ~200ms overhead on every frontend request.</li>
</ul>
<h3>8.1.6  – 18-03-2026</h3>
<ul>
<li>Fix       – PayPlus payment gateway now displays correctly in the WooCommerce Blocks checkout page editor (resolved “payment methods not supported” message).</li>
<li>Feature   – Blocks checkout: closing a payment page (iframe/popup) or re-selecting a payment method no longer requires a full page reload.</li>
<li>Fix       – Blocks checkout: PayPlus Embedded (hosted fields) no longer requires a full page reload on payment failure or when coupons/gift cards change.</li>
<li>Fix       – Order status polling now stops correctly when a payment page is closed or the cart total changes (both Classic and Blocks checkout).</li>
<li>Feature   – J5 Weight Estimate: added a configurable percentage-based cart fee (5%–20%) for Authorization (J5) mode, visible only when a PayPlus gateway is selected.</li>
<li>Feature   – J5 Weight Estimate: customizable fee name and optional description message displayed below the fee line.</li>
<li>Feature   – New option to prevent double rendering of the payment page iframe on the receipt page (common with Elementor or other page builders).</li>
<li>Tweak     – Removed TV power-down effect feature.</li>
</ul>
<h3>8.1.5  – 15-03-2026</h3>
<ul>
<li>Feature   – Added VAT selection prompt for partial refunds, allowing admins to choose whether the refunded amount includes VAT or is VAT-exempt.</li>
<li>Fix       – Resolved an issue where saved payment tokens could override the PayPlus Embedded selection, causing the checkout to revert to a previously saved card instead of using newly entered card details.</li>
<li>Fix       – Fixed token saving failure when the optional “Name for Invoice” or “Alternative ID/VAT” fields were filled during PayPlus Embedded checkout.</li>
<li>Feature   – PRUID history tracking: all payment page request UIDs are now stored with timestamps, enabling recovery of orders where the UID changed. The “Get PayPlus Data” button shows a selection popup with a “Try All” option.</li>
<li>Feature   – Optional order total display inside PayPlus Embedded payment form for both Classic and Blocks checkout, with automatic updates on coupon/shipping changes.</li>
<li>Tweak     – Reduced checkout order-status polling frequency to prevent excessive server load on slower sites.</li>
<li>Fix       – Fixed Hebrew character corruption (appearing as raw Unicode escapes) in PayPlus API payloads for certain server configurations.</li>
<li>Tweak     – PRUID history is now used by the cron job and the Orders Validator for more reliable order status recovery.</li>
<li>Fix       – Fixed expiry field order in PayPlus Embedded for LTR locales.</li>
<li>Fix       – The “Include Apple Pay Script” setting now correctly loads the Apple Pay script on Blocks checkout for all iframe display modes.</li>
</ul>
<h3>8.1.4  – 10-03-2026</h3>
<ul>
<li>Fix       – Fixed an issue where redirect URLs after payment could be malformed (& converted to &), potentially causing broken thank-you page loads or missing order details.</li>
</ul>
<p><a href="https://plugins.svn.wordpress.org/payplus-payment-gateway/trunk/CHANGELOG.md" rel="nofollow ugc">See changelog for all versions</a>.</p>


PayPlus Payment Gateway

Accept credit/debit card payments or other methods such as bit, Apple Pay, Google Pay in one page. Create digitally signed invoices & much more!

PII Tokenizer vs PayPlus Payment Gateway