PCI Vault Forms
Securely capture payment card data from your site using PCI Vault. PCI Vault is a vendor neutral PCI DSS compliant environment designed to reduce your PCI compliance scope to a SAQ by using credit card tokenization. Data captured with this plugin will be sent to PCI Vault’s DSS compliant environment directly, and will not be present on your own server. This allows you to securely capture and tokenize credit card data without being PCI DSS compliant. How it Works The plugin comes with a short code that loads PCI Vault’s own Payment Card Data (PCD) form, and makes all the necessary requests to the PCI Vault API in order to get the form working. You can read more on the API side of things here. Take note that this includes 2 paid API requests: 1 when the form loads, and 1 when the data is being sent to PCI Vault. To use this plugin, add your authorisation details, and the user/passphrase for a key, in the PCI Vault Options menu. You can then load the capture form anywhere in your site by using the pcivault_capture shortcode. Shortcode Attributes All valid short code attributes are imported directly into the javascript that renders the form. The security of these attributes are the responsibility of the site, and not PCI Vault. Every attribute must be a valid Javascript expression. We recommend to use function calls that return the values you want the attributes to have, this will grant extra flexibility and avoid issues with WordPress’s sanitisation. The attribute options are: success_callback: A JS function to call if the card was successfully stored. error_callback: A JS function to call if the card was not successfully stored. extra_data: Extra data to store along with the card, must be a valid JS object. This is where using a JS function call really helps. show_card: A true/false value on whether or not to show the card on the form. disable_luhn: A true/false value on whether to disable validation on all form fields. force_keypad: A true/false value on whether to force the user to use a randomised on-screen keypad for entering card numbers. This helps to protect you from key-loggers. field_options: A configuration object for specifying which of the form fields to show or validate. For more information on these fields, please check the documentation for PCI Vault’s Payment Card Data (PCD) form. PCI Vault All of the magic behind this plugin happens on PCI Vault’s environment. This plugin sends an authenticated request to PCI Vault, retrieving a unique capturing endpoint. This request includes your authentication details, and the key/passphrase pair specified in the PCI Vault Options menu. This plugin also loads a hosted PCD form from PCI Vault. You need to be a customer of PCI Vault for this plugin to work. You can view our pricing and register an account. Also have a look at our Terms of Service and our Privacy Policy.
Payment Gateway with MPGS for WooCommerce
Accept credit and debit card payments on your WooCommerce store using MasterCard Payment Gateway Services (MPGS) Hosted Checkout. All card data is handled by MPGS servers directly. No sensitive payment information touches your server, keeping you PCI compliant. Features Test Mode – Switch between test and live credentials safely Debug Logging – Built-in WooCommerce logger for troubleshooting Transaction Details – Saves transaction ID, receipt, card type, and last 4 digits with each order HPOS Compatible – Works with WooCommerce High-Performance Order Storage Multiple API Versions – Supports MPGS API versions 49, 52, 55, 62, 63, and 66 3DS Authentication – Supports both 3DS1 and 3DS2 Translation Ready – French translation included Checkout Modes Payment Page – Customer is redirected to the MPGS payment page (all API versions) Lightbox – Payment form opens as a popup on your site (API v49-62 only) Pro Version Everything above stays free, forever. MPGS Pro adds payment operations tooling on top: Transaction Log Viewer – Every gateway event in your dashboard (WooCommerce > MPGS Logs). No FTP, no raw log files. Card Surcharge – Pass processing fees to the customer. Fixed or percentage, with per-country rates. Authorize & Capture – Hold funds at checkout, capture the full or a partial amount from the order screen when you ship. Branded Checkout – Your logo, website, and contact details on the MPGS payment page. Payment Alerts – Instant email or webhook notifications for successful, failed, and refunded payments. Upgrade from the plugin’s Upgrade link on the Plugins page. Learn more on the plugin page. Credits Maintained by Salman Patnee. Originally created by Ali Basheer (v1.0.0-1.5.1). External Services This plugin connects to MasterCard Payment Gateway Services (MPGS) to process payments. Provider: MasterCard International Incorporated – mastercard.com Terms of Use: mastercard.com/terms-of-use Privacy Policy: mastercard.com/privacy When and what data is sent The plugin calls MPGS servers twice per transaction: At checkout – Creates a payment session with order amount, currency, description, customer name/email, and return URL. After payment – Verifies the transaction result using the order ID. Merchant credentials are sent server-side only and never exposed to the browser. Card numbers, CVV, and expiry dates are never sent through this plugin – customers enter these directly on MPGS-hosted pages. Gateway domains https://ap-gateway.mastercard.com/ – Asia Pacific https://eu-gateway.mastercard.com/ – Europe https://na-gateway.mastercard.com/ – North America https://mtf.gateway.mastercard.com/ – Test/Sandbox Your bank will tell you which domain to use. Privacy This plugin does not track users, store card data, use tracking cookies, or share data with anyone other than MPGS for payment processing.