Ecrypt

<p>Ecrypt Payment Gateway for WooCommerce provides secure credit/debit card payment processing for your WooCommerce store. With advanced encryption and tokenization, Ecrypt ensures that your customers’ payment information is protected. The plugin is easy to configure and integrates seamlessly with your existing WooCommerce setup. Whether you are handling single transactions or recurring payments, Ecrypt offers a reliable and scalable solution to meet your payment processing needs.</p>
<h3>External Services</h3>
<p>This plugin communicates with the Ecrypt API to perform essential payment and customer management operations.</p>
<h3><strong>API Endpoints</strong></h3>
<p>The following API endpoints are used by the plugin:</p>
<h4>Customer Management</h4>
<ul>
<li><strong>Base Endpoint:</strong> <code>https://api.ecrypt.com/v1/customers</code>
<ul>
<li><a href="https://developer.ecrypt.com/docs/add-customer-wallet" rel="nofollow ugc">Add Customer Wallet</a></li>
<li><a href="https://developer.ecrypt.com/docs/charge-customer-wallet" rel="nofollow ugc">Charge Customer Wallet</a></li>
<li><a href="https://developer.ecrypt.com/docs/charge-customer" rel="nofollow ugc">Charge Customer</a></li>
<li><a href="https://developer.ecrypt.com/reference/post_v1-customers" rel="nofollow ugc">Add Customer API Reference</a></li>
<li><a href="https://developer.ecrypt.com/reference/get_v1-customers-customer" rel="nofollow ugc">Get Customer API Reference</a></li>
<li><a href="https://developer.ecrypt.com/reference/post_v1-customers-customer-wallet" rel="nofollow ugc">Add Customer Wallet API Reference</a></li>
<li><a href="https://developer.ecrypt.com/reference/get_v1-customers-customer-wallet-wallet" rel="nofollow ugc">Get Customer Wallet API Reference</a></li>
<li><a href="https://developer.ecrypt.com/reference/delete_v1-customers-customer-wallet-wallet" rel="nofollow ugc">Delete Customer Wallet API Reference</a></li>
</ul>
</li>
</ul>
<h4>Transactions: Sale</h4>
<ul>
<li><strong>Base Endpoint:</strong> <code>https://api.ecrypt.com/v1/transactions/sale</code>
<ul>
<li><a href="https://developer.ecrypt.com/docs/sale" rel="nofollow ugc">Process Sale Transaction</a></li>
<li><a href="https://developer.ecrypt.com/reference/post_v1-transactions-sale" rel="nofollow ugc">Sale API Reference</a></li>
</ul>
</li>
</ul>
<h4>Transactions: Refund</h4>
<ul>
<li><strong>Base Endpoint:</strong> <code>https://api.ecrypt.com/v1/transactions/refund</code>
<ul>
<li><a href="https://developer.ecrypt.com/docs/refund-process" rel="nofollow ugc">Refund Process Documentation</a></li>
<li><a href="https://developer.ecrypt.com/reference/post_v1-transactions-refund" rel="nofollow ugc">Refund API Reference</a></li>
</ul>
</li>
</ul>
<h4>Transactions: Authorize</h4>
<ul>
<li><strong>Base Endpoint:</strong> <code>https://api.ecrypt.com/v1/transactions/authorize</code>
<ul>
<li><a href="https://developer.ecrypt.com/docs/authorize-capture" rel="nofollow ugc">Authorize and Capture Process Documentation</a></li>
<li><a href="https://developer.ecrypt.com/reference/post_v1-transactions-authorize" rel="nofollow ugc">Authorize API Reference</a></li>
</ul>
</li>
</ul>
<h4>Transactions: Capture</h4>
<ul>
<li><strong>Base Endpoint:</strong> <code>https://api.ecrypt.com/v1/transactions/capture</code>
<ul>
<li><a href="https://developer.ecrypt.com/docs/authorize-capture" rel="nofollow ugc">Authorize and Capture Process Documentation</a></li>
<li><a href="https://developer.ecrypt.com/reference/post_v1-transactions-capture" rel="nofollow ugc">Capture API Reference</a></li>
</ul>
</li>
</ul>
<h4>Transactions: Void</h4>
<ul>
<li><strong>Base Endpoint:</strong> <code>https://api.ecrypt.com/v1/transactions/capture</code>
<ul>
<li><a href="https://developer.ecrypt.com/docs/void-process" rel="nofollow ugc">Void Transaction Process Documentation</a></li>
<li><a href="https://developer.ecrypt.com/reference/post_v1-transactions-void" rel="nofollow ugc">Void API Reference</a></li>
</ul>
</li>
</ul>
<h3><strong>Data Collected</strong></h3>
<p>When interacting with these endpoints, the plugin may transmit the following data to the Ecrypt API:</p>
<ul>
<li>Customer information: Name, email, and associated wallet details.</li>
<li>Transaction data: Amount, transaction ID, and sale or refund specifics.</li>
</ul>
<h3><strong>Legal Agreements</strong></h3>
<p>By using this plugin, you acknowledge and agree to the terms outlined by Ecrypt:</p>
<ul>
<li><a href="https://ecrypt.com/privacy-policy" rel="nofollow ugc">Privacy Policy</a></li>
<li><a href="https://ecrypt.com/terms-and-conditions" rel="nofollow ugc">Terms and Conditions</a></li>
<li><a href="https://ecrypt.com/merchant-processing-agreement" rel="nofollow ugc">Merchant Processing Agreement</a></li>
</ul>
<h3>Privacy Notice</h3>
<p>The Ecrypt Payment Gateway for WooCommerce plugin securely communicates with the Ecrypt API to facilitate transactions and wallet management. During these interactions, customer and transaction data is transmitted to Ecrypt.</p>
<h3><strong>Key Legal Documents</strong></h3>
<ul>
<li><strong>Privacy Policy:</strong> Explains how Ecrypt handles personal and transaction data. Read it <a href="https://ecrypt.com/privacy-policy" rel="nofollow ugc">here</a>.</li>
<li><strong>Terms and Conditions:</strong> Details the terms under which Ecrypt services operate. Read them <a href="https://ecrypt.com/terms-and-conditions" rel="nofollow ugc">here</a>.</li>
<li><strong>Merchant Processing Agreement:</strong> Covers specific agreements for merchants using Ecrypt’s payment processing. Read it <a href="https://ecrypt.com/merchant-processing-agreement" rel="nofollow ugc">here</a>.</li>
</ul>
<h3><strong>User Responsibility</strong></h3>
<p>Users should review these policies to ensure compliance with applicable laws and their own privacy obligations. This plugin does not store sensitive customer data locally and relies on Ecrypt’s security protocols.</p>
<h3>Notes</h3>
<p>This plugin requires a valid Ecrypt API key to function. Please refer to the <a href="https://developer.ecrypt.com" rel="nofollow ugc">Ecrypt Developer Documentation</a> for setup instructions.</p>
<h3>0.0.1 – 2024-07-03</h3>
<ul>
<li>
<p><strong>Security Improvements</strong>:</p>
<ul>
<li>Fixed non-sanitized input variables.</li>
<li>Ensured all output is escaped.</li>
</ul>
</li>
<li>
<p><strong>AI-Assisted Recommendations</strong>: Enhanced security by implementing AI suggestions.</p>
</li>
</ul>
<h3>0.0.2 – 2024-08-22</h3>
<ul>
<li>
<p><strong>Security Improvements</strong>:</p>
<ul>
<li>Improved data validation and sanitization.</li>
</ul>
</li>
<li>
<p><strong>External Service Documentation</strong>:</p>
<ul>
<li>Added detailed documentation on Ecrypt API usage, endpoints, and privacy compliance.</li>
</ul>
</li>
</ul>
<h3>0.0.3 – 2024-11-21</h3>
<ul>
<li>
<p><strong>File Naming Compliance</strong>:</p>
<ul>
<li>Renamed all files to adhere to WordPress naming conventions:</li>
<li><code>EcryptCustomerWallet.php</code> -> <code>ecrypt-payment-gateway-customer-wallet.php</code></li>
<li><code>EcryptPaymentExceptions.php</code> -> <code>ecrypt-payment-gateway-exceptions.php</code></li>
<li><code>EcryptPaymentMethod.php</code> -> <code>ecrypt-payment-gateway-method.php</code></li>
<li><code>EcryptTokenApi.php</code> -> <code>ecrypt-payment-gateway-token-api.php</code></li>
<li><code>EcryptPaymentApi.php</code> -> <code>ecrypt-payment-gateway-transaction-api.php</code></li>
<li><code>core.php</code> -> <code>ecrypt-payment-gateway-core-init.php</code></li>
</ul>
</li>
<li>
<p><strong>Security Improvements</strong>:</p>
<ul>
<li>Added <code>!defined( 'ABSPATH' )</code> checks to prevent direct file access in all PHP files.</li>
<li>Enhanced sanitization and validation:</li>
<li>Used <code>wp_unslash()</code> and <code>sanitize_text_field()</code> for <code>ecrypt_payment_nonce</code>.</li>
<li>Ensured proper escaping for all dynamic outputs in multiple files.</li>
<li>Improved error handling with clear, actionable messages.</li>
</ul>
</li>
<li>
<p><strong>Internationalization (I18n)</strong>:</p>
<ul>
<li>Updated all text domains to <code>ecrypt-payment-gateway-for-woocommerce</code>.</li>
<li>Added translators’ comments for strings with placeholders.</li>
<li>Ensured all strings are translatable and dynamic placeholders are properly formatted.</li>
</ul>
</li>
<li>
<p><strong>ReadMe Updates</strong>:</p>
<ul>
<li>Documented external API usage, endpoints, and terms of service.</li>
<li>Added privacy and security notices for compliance.</li>
</ul>
</li>
</ul>
<p>This update brings significant improvements in security, compliance, and adherence to WordPress plugin development standards.</p>
<h3>1.0.0 – 2024-12-23</h3>
<ul>
<li><strong>Initial commit for Ecrypt Payment Gateway for WooCommerce</strong>:</li>
</ul>
<h3>1.0.3 – 2025-10-08</h3>
<ul>
<li><strong>Added</strong>:
<ul>
<li>Added support for block checkout</li>
<li>Added composer for autoloading and testing</li>
</ul>
</li>
<li><strong>Test</strong>:
<ul>
<li>Added testing via composer, PHPUnit and BrainMonkey</li>
<li>Added unit tests for blocks support class</li>
<li>Added unit tests for customer wallet class</li>
<li>Added unit tests for token api class</li>
<li>Added unit tests for transaction api class</li>
<li>Added unit tests for core class</li>
</ul>
</li>
<li><strong>Refactor</strong>:
<ul>
<li>Add new exception class to handle errors in various classes to reduce return statements in class methods</li>
<li>Refactor various class methods to reduce cognitive complexity</li>
</ul>
</li>
</ul>
<h3>1.0.4 – 2025-10-15</h3>
<ul>
<li><strong>Fixed</strong>:
<ul>
<li>Updated toolkit version for block checkout</li>
</ul>
</li>
</ul>
<h3>1.0.5 – 2026-01-08</h3>
<ul>
<li><strong>Fixed</strong>:
<ul>
<li>Updated toolkit version for block checkout addressing responsive site concerns</li>
</ul>
</li>
<li><strong>Added</strong>:
<ul>
<li>Update order status to failed on failed payment</li>
</ul>
</li>
</ul>
<h3>1.1.0 – 2026-02-23</h3>
<ul>
<li><strong>Added</strong>:
<ul>
<li>Authorization transaction type</li>
<li>Ability to Capture authorized transactions via order actions in order details screen</li>
<li>Ability to Void unsettled orders via order actions in order details screen</li>
<li>Accepted cards icons to block and classic checkout payment box</li>
</ul>
</li>
</ul>
<h3>1.1.1 – 2026-04-02</h3>
<ul>
<li><strong>Fixed</strong>:
<ul>
<li>customer wallet uncaught error responses</li>
</ul>
</li>
</ul>
<h3>1.1.2 – 2026-06-04</h3>
<ul>
<li><strong>Update</strong>:
<ul>
<li>update toolkit version</li>
</ul>
</li>
</ul>


Ecrypt Payment Gateway for WooCommerce

Ecrypt Payment Gateway for WooCommerce provides secure credit/debit card payment processing for your WooCommerce store.

<p>This extension provides a unique combination of payment options for your customers. SnapScan allows South African customers to check out quicker and more securely using the SnapScan app, which encrypts their card details. Customers spend less time at checkout, and more time shopping.<br />
Customers without the SnapScan app can pay using their card details. These payments will reflect alongside your SnapScan payments in your consolidated SnapScan transaction history.<br />
Once the payment process is complete, the order will be created in the WooCommerce system and marked as “processing”, so no manual payment reconciliation is needed.</p>
<h3>Minimum Requirements</h3>
<ul>
<li>WordPress 4.6</li>
<li>WooCommerce 2.6.0 or greater</li>
<li>PHP version 5.6.20 or greater. PHP 7.2 or greater is recommended</li>
</ul>
<h3>Key Features</h3>
<ul>
<li>SnapScan offers a fast and easy online signup</li>
<li>Simple and free payment integration</li>
<li>Customers need not enter card details (unless selecting to pay via card)</li>
<li>Customers scan on desktop or click a link on a mobile device; or select to pay by card</li>
<li>Responsive and mobile friendly</li>
<li>Payment happens onsite with a trusted mobile payment provider</li>
</ul>
<h3>Why choose SnapScan?</h3>
<p>SnapScan is the preferred way for South Africans to pay with their phones.<br />
You may know the app from your favourite weekend market or local coffee shop, but SnapScan also provides payment solutions for larger merchants: from payments and invoicing for Pathcare laboratories to online checkout for big brands like Superbalist, OneDayOnly and Yuppiechef. SnapScan’s rate starts at  3% (excl. VAT) per transaction, and can decrease every month based on the previous month’s turnover.</p>
<h3>How do I start using SnapScan?</h3>
<p>To get started with SnapScan, you need a merchant account. Head over to <a href="https://www.snapsan.co.za" rel="nofollow ugc">www.snapscan.co.za</a> to complete the online signup process. This generally takes 3-5 business days, and the sooner SnapScan gets the required info the quicker it is to get set up.<br />
Once your account has been verified, you can request the WooCommerce integration details from their team.<br />
When the plugin has been integrated, after a customer has paid, their order is automatically completed and the website updates. As a merchant, your order list displays confirmation of the SnapScan payment, and you can begin the delivery process.</p>
<h3>What happens after I have a SnapScan merchant account?</h3>
<ul>
<li>Download this plugin</li>
<li>Email help@snapscan.co.za and let them know you’d like to integrate with the WooCommerce SnapScan plugin</li>
<li>SnapScan will send you all the relevant details and instructions for setting up the payment option on your website.</li>
</ul>


SnapScan Payment Gateway

A free, safe, and secure payment integration where customers can pay via SnapScan or card with automatic WooCommerce payment reconciliation.

Ecrypt Payment Gateway for WooCommerce vs SnapScan Payment Gateway