Skip to main content

WooCommerce Plugin

Our WooCommerce plugin supports payment with CreditCard, using our Token Fields to offset PCI requirements, Apple Pay™ and Google Pay™

WooCommerce subscriptions are supported, as well as 3ds payments

Plugin Installation​

Your NetValve contact will supply you with the plugin in a ZIP archive.

  1. Navigate to the Plugins page in your WordPress admin panel.
  2. Click the Add Plugin button, located at the top of the page; then click the Upload Plugin button and select the provided NetValve plugin archive.
WP - Add Plugin button
WP - Upload Plugin button
  1. Upload the NetValve plugin file for installation.

You should now see the Netvalve Payment Gateway plugin in the list of installed plugins.

WP - Netvalve Payment Gateway plugin

Configuration​

On the WordPress Plugins page click the Settings link under the Netvalve Payment Gateway plugin name.

The following page will appear.

WP - Netvalve Payment Gateway plugin settings

Use the guidelines below to set up the plugin in your environment in order to accept payments via the NetValve gateway.

OptionDescription
Enable/DisableThis checkbox enables/disables the NetValve payment options on your website.
DescriptionAny description you want to show your customers during the payment flow.
Test ModeEnable this, if your credentials are for the NetValve sandbox.
Debug ModeIn case of something not working, enabling this checkbox will write to a server log all actions, requests and responses happening, which can help tracing down the issue.
Client IDEnter the value provided by NetValve for your configuration.
API KeyEnter the value provided by NetValve for your configuration.
siteIdEnter the value provided by NetValve for your configuration.

Apple Pay™​

Scroll down to Apple Pay Settings on the plugin settings page.

WP plugin - Apple Pay settings with NetValve certificates

OptionDescription
Enable Apple Pay ButtonShows the Apple Pay button on checkout when the customer's device and browser support it.
Use the NetValve Apple Pay certificates for processingProcesses Apple Pay with NetValve's own Apple Pay certificates. Ticked by default and recommended. You do not need an Apple Developer account.
Apple Merchant IDOnly shown when the checkbox above is unticked. Your Merchant ID from the Apple Developer portal, e.g. merchant.example.prod.
Apple Merchant Certificate PathOnly shown when the checkbox above is unticked. Absolute server path to your merchant identity certificate, e.g. /var/www/keys/certificate.pem.
Apple Merchant Key PathOnly shown when the checkbox above is unticked. Absolute server path to the matching private key, e.g. /var/www/keys/certificate.key.

There are two ways to configure Apple Pay. Pick Option A unless you already have an Apple Pay setup under your own Apple Developer account, or you are required to hold the certificates yourself. See the Digital Wallets overview for the background on both models.

  1. Tick Enable Apple Pay Button.
  2. Leave Use the NetValve Apple Pay certificates for processing ticked.
  3. Host Apple's domain-association file on your store domain (see Hosting the domain-association file below).
  4. Contact NetValve support to have your store domain registered for Apple Pay processing.

No Apple Developer account and no certificates are needed on your side.

Option B — Your own Apple Pay certificates​

WP plugin - Apple Pay settings with own certificates

  1. Tick Enable Apple Pay Button.
  2. Untick Use the NetValve Apple Pay certificates for processing. Three extra fields appear.
  3. Enter your Apple Merchant ID from your Apple Developer account.
  4. Upload your merchant identity certificate (.pem) and private key (.key) to the web server, outside the web root, and enter their absolute paths in the two path fields.
  5. Complete Apple's domain verification for your store domain under your own Apple Developer account, using the domain-association file Apple provides for your Merchant ID. The NetValve files described below do not apply to this option.

For how to create the Merchant ID and certificates, see Bring your own certificate in the Apple Pay guide.

Hosting the domain-association file​

Applies to Option A only.

Apple verifies that you control your store domain by fetching a static file from it. Serve the file at:

https://<store-domain>/.well-known/apple-developer-merchantid-domain-association

The content must be identical to NetValve's file for the environment you are on. Download it from the matching URL and place it at the same path on your own domain:

EnvironmentCopy this file
Sandbox (plugin Test Mode on)https://checkout.uat.sandbox-netvalve.com/.well-known/apple-developer-merchantid-domain-association
Productionhttps://checkout.netvalve.com/.well-known/apple-developer-merchantid-domain-association

Requirements:

  • No file extension, served as plain text.
  • Reachable over HTTPS with a valid certificate, HTTP 200, no redirect.
  • Sandbox and production files are different. Use the one matching your environment, and switch the file when you go live.

Quick check from a terminal:

curl -I https://<store-domain>/.well-known/apple-developer-merchantid-domain-association

It should return HTTP/2 200. If it does not, Apple's verification will fail and the button will not appear.

note

Some WordPress security plugins and hosting setups block or rewrite requests to /.well-known/. If the check above fails, confirm the file is actually served before contacting support.

Verifying Apple Pay on your checkout​

Open your checkout in Safari on an Apple device (iPhone, iPad, or Mac) that has a card in Apple Wallet. The Apple Pay button should appear next to the other payment options. The button is not shown on browsers or devices that do not support Apple Pay.

With Test Mode enabled, use an Apple sandbox tester account with a test card. See Sandbox Testing - Apple Pay and the Testing section of the Apple Pay guide.

Google Pay™​

Scroll down to Google Pay Settings on the plugin settings page.

OptionDescription
Enable Google Pay ButtonShows the Google Pay button on checkout when the customer's device and browser support it.
Google Merchant IDYour Merchant ID from the Google Pay & Wallet Console. Required for production.
Google Merchant Display NameThe business name shown to the customer in the Google Pay sheet.

Google Pay needs no certificates and no domain registration with NetValve. NetValve is the registered Google Pay gateway, so the plugin handles the gateway parameters for you. See the Google Pay guide for details.