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

PayPlus Tech Team

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!

Bakrypt

Brand Guard QR

Brand Guard QR - Enhanced Product Identification Generate dynamic product identification codes replacing traditional GTIN/UPC usage backed by the Card …

Hemal

PII Tokenizer 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: 
– Vaultless tokenization and detokenization of PII fields via Java-based APIs. 
– Dynamic buttons for “Tokenize” functionality appended to form fields for easy usage. 
– API key registration after email verification, with secure client ID generation. 
– Compatibility with popular WordPress form plugins like WPForms and Gravity Forms.
Key Features: 
– Protect sensitive data by tokenizing form fields. 
– Use individual “Tokenize” buttons for profile and address fields. 
– Easily detokenize data when required. 
– Modern admin interface for API key registration and management. 
– Backend integration with customizable Java tokenization and detokenization services.
<h3>External Services</h3>
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.
<h3>External API Endpoints</h3>
<ol>
<li>
Vaultless Tokenization API
<ul>
<li>Purpose: The Vaultless Tokenization API is used to convert sensitive PII fields such as name, email, mobile, and address into secure tokens.</li>
<li>Data Sent: 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>Conditions: This API is triggered when the “Tokenize” button is clicked by the user in a form integrated with the plugin.</li>
<li>Service Provider: Samuday Technology Services</li>
</ul>
</li>
<li>
Detokenization API
<ul>
<li>Purpose: The Detokenization API is used to convert secure tokens back into their original PII form.</li>
<li>Data Sent: 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>Conditions: This API is triggered when the “Detokenize” button is clicked by the user in a form integrated with the plugin.</li>
<li>Service Provider: Samuday Technology Services</li>
</ul>
</li>
<li>
Address Tokenization and Detokenization APIs
<ul>
<li>Purpose: These APIs are specifically designed to handle tokenization and detokenization of address data. </li>
<li>Data Sent: 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>Conditions: This API is triggered when address tokenization or detokenization actions are performed via the respective buttons in a form.</li>
<li>Service Provider: Samuday Technology Services</li>
</ul>
</li>
</ol>
<h3>License</h3>
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

Alternatives to PII Tokenizer

Top alternatives