WooCommerce

Install and configure the VINR payment plugin for WooCommerce.

View as MarkdownInstall skills

The VINR plugin for WooCommerce lets WordPress stores accept cards, digital wallets, BNPL, and local payment methods through a single integration. Download the plugin directly from the VINR dashboard, drop it into any WooCommerce 7.0+ store running PHP 8.0+, and your checkout is connected to the full VINR payment stack — including tokenized repeat purchases, 3D Secure, and optional in-person terminals — without touching a line of server-side code.

This is illustrative content. Plugin availability and exact menu paths may differ; refer to your VINR account manager for production details.

Supported payment methodsAsk

MethodOnlineIn-person
Visa / Mastercard / Amex
Apple Pay / Google Pay
SEPA Direct Debit
Local payment methods
Installments / BNPL

RequirementsAsk

Before installing the plugin, confirm the following:

  • WooCommerce 7.0 or higher
  • WordPress 6.0 or higher
  • PHP 8.0 or higher (8.2+ recommended)
  • A valid SSL certificate on your storefront domain
  • An active VINR merchant account — see Account setup if you have not completed onboarding
  • API Key and Merchant ID from the VINR dashboard (Settings → API Credentials)

InstallAsk

Download the plugin

Log in to the VINR dashboard, navigate to Integrations → Plugins → WooCommerce, and download the latest .zip archive.

Upload and activate in WordPress

In your WordPress admin panel go to Plugins → Add New → Upload Plugin, select the .zip you just downloaded, click Install Now, and then click Activate Plugin.

Open the plugin settings

Navigate to WooCommerce → Settings → Payments, locate VINR Payments in the list, and click Manage.

Enter your credentials

Paste your API Key and Merchant ID from the VINR dashboard into the corresponding fields and click Save changes. The plugin will verify the credentials and show a green connection status if successful.

ConfigureAsk

Payment methods

Navigate to WooCommerce → Settings → Payments → VINR Payments → Payment Methods. Each method enabled on your VINR account appears as a toggle here. Methods that are not activated in your VINR account are hidden — contact your account manager to enable additional methods at the account level before toggling them on in the plugin.

Capture mode

The payment is authorized and funds are captured immediately at checkout. This is the right mode for most stores that ship or fulfill digitally at the point of purchase.

Setting path: WooCommerce → Settings → Payments → VINR Payments → Manage → Capture mode → Automatic

The payment is authorized at checkout and captured later — for example, when the WooCommerce order transitions to a fulfillment status. Use this when you ship physical goods and want to capture funds only after you confirm stock and dispatch.

Setting path: WooCommerce → Settings → Payments → VINR Payments → Manage → Capture mode → Manual

With manual capture, VINR holds the authorization for up to 7 days. If you do not capture within that window, the authorization is released and the customer is not charged.

3D Secure

3D Secure is enforced automatically by VINR for any transaction that requires Strong Customer Authentication under PSD2. No plugin configuration is needed — VINR detects whether SCA applies and triggers the 3DS2 challenge flow transparently before the order is placed.

Use VINR test cards tagged 3DS_REQUIRED in the VINR dashboard to verify your checkout handles a challenge flow correctly before go-live. See 3D Secure for the full list of test card numbers and expected outcomes.

Webhooks

The plugin registers a webhook listener automatically at:

https://yourstore.com/wc-api/vinr_payments

Verify the endpoint is registered in the VINR dashboard under Developers → Webhooks. The URL must be publicly accessible — local localhost addresses will not receive events.

WooCommerce order statuses map to VINR payment states as follows:

VINR payment stateWooCommerce order status
authorizedProcessing
capturedCompleted
failedFailed
refundedRefunded

Tokenization and saved cardsAsk

The plugin surfaces WooCommerce's native "Save payment method" checkbox at checkout. When a customer opts in, VINR vaults the card and returns a token; no raw card data ever touches your server. On subsequent checkouts the customer selects a saved card from the dropdown and completes payment without re-entering details.

Saved tokens are also compatible with the WooCommerce Subscriptions plugin. VINR handles the recurring charge against the stored token on each renewal date, so subscription orders process without customer interaction.

For full token lifecycle details — including how to list, remove, and reuse tokens via the API — see Tokenization.

In personAsk

If your VINR account includes terminal access, you can accept card-present payments at a physical point of sale alongside your online store.

Enable in-person acceptance under WooCommerce → Settings → Payments → VINR Payments → In-person and select the terminal(s) assigned to your location. This feature requires either a compatible WooCommerce POS plugin or a custom POS integration that calls the VINR Terminal API.

See In-person payments for terminal setup, reader pairing, and offline mode behaviour.

Go liveAsk

Switch to live API credentials

In WooCommerce → Settings → Payments → VINR Payments → Manage, replace the test API Key and Merchant ID with your live credentials from the VINR dashboard. Save changes.

Place a real test order

Use a live card for a small amount (for example, 1.00 in your store currency) to confirm the end-to-end flow works in production.

Verify both dashboards

Confirm the order appears in WooCommerce → Orders with the expected status and in the VINR dashboard → Payments with the correct amount and captured state.

Enable your payment methods

In the VINR dashboard under Settings → Payment Methods, confirm every method you want to offer is toggled on for live mode. Methods left in test mode will not appear to real customers.

Remove sandbox notices

If you displayed any test-mode banners or notices on your storefront during development, remove or disable them before accepting customer traffic.

TroubleshootingAsk

Next stepsAsk

Was this page helpful?
Edit on GitHub

Last updated on

On this page