midenengineering

<p>The Miden Payment Gateway for WooCommerce allows merchants to accept payments through the Miden platform using WooCommerce’s standard checkout flow.</p>
<p>The plugin redirects customers to a hosted Miden checkout page to complete payment securely. Once payment is completed, customers are returned to the store and the order status is updated accordingly.</p>
<p>This plugin requires WooCommerce to be installed and active.</p>
<h3>External services</h3>
<p>This plugin connects to external payment services operated by Miden to create payment sessions and process customer payments.</p>
<p>The services are required to generate a hosted checkout payment link and to complete payment transactions securely. These actions cannot be performed locally within WordPress.</p>
<h3>Buzapay Payment Gateway API</h3>
<p><strong>What the service is and what it is used for</strong><br />
The plugin connects to the Buzapay Payment Gateway API, which is used by the Miden platform to generate hosted checkout payment links and process payment transactions.</p>
<p><strong>Service provider</strong><br />
Buzapay (operated by Miden)</p>
<p><strong>Domain(s)</strong><br />
– https://api.buzapay.com<br />
– https://sandbox-merchant.buzapay.com</p>
<p><strong>What data is sent and when</strong><br />
When a customer places an order and selects Miden as the payment method, the plugin sends the following data to the Buzapay API:<br />
– Order amount<br />
– Currency<br />
– Merchant name<br />
– Customer email address<br />
– Customer phone number<br />
– Transaction reference<br />
– Payment narration<br />
– Redirect URL used to return the customer to the store after payment</p>
<p>Data is sent only at the time an order is submitted during checkout and only for orders using the Miden payment method.</p>
<p><strong>Terms of Service</strong><br />
https://miden.co/terms</p>
<p><strong>Privacy Policy</strong><br />
https://miden.co/privacy</p>


Miden Payment Gateway

Accept payments in WooCommerce using the Miden payment platform.

Fabrick Support

Neting

<p>Fabrick offers solutions to meet and anticipate payment acceptance needs across physical and digital channels. The offering is based on a single platform to accept payments through POS and e-commerce gateways, Banking-as-a-Service (BaaS), and omnichannel solutions that continuously evolve with market changes.</p>
<p>With Fabrick Payment Orchestra, you can:<br />
* Accept payments from all major credit cards.<br />
* Accept payments with alternative methods, including PayPal, and manage them from a single dashboard.<br />
* Customize every aspect of the payment page.<br />
* Use a PCI DSS-compliant payment flow, without storing customers’ full credit card numbers on your servers.<br />
* Rely on 3DS2 support.</p>
<p><a href="https://docs.axerve.com/it/plugin/woocommerce/" title="Ecommerce Fabrick - Usage Documentation" rel="nofollow ugc">Click here to read the full usage documentation on Fabrick</a>.</p>
<h4>WooCommerce Blocks Compatibility</h4>
<p>The plugin is fully compatible with WooCommerce Blocks checkout. All payment methods are supported in both classic checkout and Blocks checkout modes. There is no need to disable WooCommerce Blocks checkout.</p>
<h4>Available Features</h4>
<ul>
<li>S2S SOAP (except <code>callReadTrxS2S</code> and <code>callVerifyCardS2S</code>)</li>
<li>Tokenization</li>
<li>3DS1</li>
<li>3DS2 – Authentication</li>
<li>3DS2 – Recurring Transactions</li>
<li>RBA (Risk-Based Authentication)</li>
<li>PayPal Seller Protection</li>
<li>PayPal Billing Agreement</li>
<li>WooCommerce Subscriptions support (Recurring payments and subscriptions)</li>
</ul>
<h4>Available Payment Methods</h4>
<ul>
<li>Credit Cards</li>
<li>BANCOMAT Pay</li>
<li>MyBank</li>
<li>PayPal</li>
<li>PayPal Billing Agreement</li>
<li>PayPal Buy Now Pay Later</li>
</ul>
<h4>Benefits</h4>
<ul>
<li>Accept credit card payments directly on your checkout page.</li>
<li>Accept payments with a variety of alternative methods to increase conversion by allowing customers to use their preferred payment option.</li>
<li>Reduce fraud risk with advanced fraud detection tools (RBA).</li>
</ul>
<h4>Security</h4>
<ul>
<li>No full credit card data is stored on your servers during the payment process.</li>
<li>All major card brands are supported (Visa, Mastercard, American Express).</li>
<li>3DS2.x support.</li>
</ul>
<h4>Support</h4>
<p>You can contact our support team at ecommerce@sella.it.</p>
<h3>Actions and filters list</h3>
<p>Here is a list of filters and actions used in this plugin:</p>
<h4>Actions</h4>
<ul>
<li>gestpay_before_processing_order</li>
<li>gestpay_after_order_completed</li>
<li>gestpay_after_order_failed</li>
<li>gestpay_after_order_pending</li>
<li>gestpay_before_order_settle</li>
<li>gestpay_order_settle_success</li>
<li>gestpay_order_settle_fail</li>
<li>gestpay_before_order_refund</li>
<li>gestpay_order_refund_success</li>
<li>gestpay_order_refund_fail</li>
<li>gestpay_before_order_delete</li>
<li>gestpay_order_delete_success</li>
<li>gestpay_order_delete_fail</li>
<li>gestpay_after_s2s_order_failed</li>
<li>gestpay_on_renewal_payment_failure</li>
<li>gestpay_my_cards_template_before_table</li>
<li>gestpay_my_cards_template_after_table</li>
</ul>
<h4>Filters</h4>
<ul>
<li>gestpay_gateway_parameters</li>
<li>gestpay_encrypt_parameters</li>
<li>gestpay_settings_tab</li>
<li>gestpay_my_cards_template</li>
<li>gestpay_cvv_fancybox</li>
<li>gestpay_gateway_cards_images</li>
<li>gestpay_alter_order_id -> this can be used to add, for example, a prefix to the order ID</li>
<li>gestpay_revert_order_id -> this must be used to revert back the order ID changed with the <code>gestpay_alter_order_id</code> filter</li>
<li>gestpay_s2s_validate_payment_fields</li>
<li>gestpay_s2s_payment_fields_error_strings</li>
</ul>
<h3>Third Party Libraries</h3>
<p>Questo plugin utilizza le seguenti librerie di terze parti:</p>
<ul>
<li>SOAP Client – Parte della libreria standard PHP, utilizzata per le comunicazioni con l’API Gestpay</li>
<li>WooCommerce – Framework e-commerce per WordPress (GPLv3)</li>
<li>WordPress – CMS principale (GPLv2 o successiva)</li>
<li>jQuery – Libreria JavaScript per la manipolazione del DOM e la gestione degli eventi (MIT License)</li>
</ul>
<h3>External services</h3>
<p>Questo plugin si connette ai seguenti servizi esterni:</p>
<ol>
<li>Axerve Payment Gateway (precedentemente Gestpay)</li>
</ol>
<p>– Scopo: Elaborazione dei pagamenti tramite il gateway di Banca Sella<br />
– Dati inviati: Informazioni sull’ordine, dati del cliente necessari per il pagamento<br />
– Quando: Durante il processo di pagamento e per le operazioni di gestione degli ordini<br />
– Privacy Policy: https://www.axerve.com/privacy-policy<br />
– Termini di servizio: https://www.axerve.com/terms-conditions</p>
<ol>
<li>icanhazip.com</li>
</ol>
<p>– Scopo: Identificazione dell’indirizzo IP del server per la configurazione del gateway di pagamento<br />
– Dati inviati: Nessun dato viene inviato, il servizio risponde solo con l’indirizzo IP pubblico<br />
– Quando: Solo nell’area amministrativa durante la configurazione del plugin<br />
– Privacy Policy: https://major.io/icanhazip-com-faq/<br />
– Note: Questo servizio viene utilizzato solo per aiutare gli amministratori a configurare correttamente il gateway di pagamento nel backoffice di Axerve</p>
<ol>
<li>Script JavaScript di verifica</li>
</ol>
<p>– Scopo: Verifica della compatibilità del browser con il gateway di pagamento<br />
– Dati inviati: Informazioni sul browser dell’utente per verificare la compatibilità TLS<br />
– Quando: Durante il processo di pagamento<br />
– Domini: gestpay.net, gestpay.it, ecomm.sella.it<br />
– Privacy Policy: https://www.axerve.com/privacy-policy</p>
<ol>
<li>MyBank</li>
</ol>
<p>– Scopo: Integrazione con il sistema di pagamento MyBank<br />
– Dati inviati: Informazioni necessarie per il pagamento tramite MyBank<br />
– Quando: Solo quando l’utente sceglie MyBank come metodo di pagamento<br />
– Privacy Policy: https://www.mybank.eu/privacy-policy/<br />
– Termini di servizio: https://www.mybank.eu/terms-and-conditions/</p>
<p>Server di test e sviluppo<br />
Nel codice di esempio (directory <code>sample/</code>) sono presenti riferimenti a domini fittizi (<code>site1.it</code> e <code>site2.it</code>) utilizzati solo come esempio per dimostrare la configurazione multi-sito. Questi domini sono puramente dimostrativi e non sono utilizzati nel codice di produzione.</p>


Ecommerce Fabrick

Fabrick Free Plugin for WooCommerce extends WooCommerce by providing the Fabrick Payment Orchestra payment gateway.

Miden Payment Gateway vs Ecommerce Fabrick