Adobe Commerce

The VINR plugin for Adobe Commerce (Magento 2) integrates VINR payments directly into Magento-powered storefronts. It supports Adobe Commerce 2.4.x and Magento Open Source 2.4.x, is distributed as a Composer package, and exposes the full VINR payment surface — card, wallet, and local payment methods — through the native Magento payment framework.

Supported payment methodsAskCopy

RequirementsAskCopy

• Adobe Commerce 2.4.x or Magento Open Source 2.4.x
• PHP 8.1 or higher
• Composer 2
• An active VINR merchant account
• VINR API Key and Merchant ID (available in the VINR dashboard under Developers → API credentials)

InstallAskCopy

{
  "repositories": [
    {
      "type": "composer",
      "url": "https://packages.vinr.com"
    }
  ]
}

composer require vinr/magento2-payments

bin/magento module:enable Vinr_Payments

bin/magento setup:upgrade && \
bin/magento setup:di:compile && \
bin/magento cache:clean

ConfigureAskCopy

Payment methods

Navigate to Stores → Configuration → Sales → Payment Methods → VINR Payments → Enabled Methods. Toggle individual payment methods on or off. Changes take effect after saving; no cache flush is required for method visibility changes.

Capture mode

bin/magento config:set payment/vinr_payments/payment_action authorize_capture
bin/magento cache:clean

bin/magento config:set payment/vinr_payments/payment_action authorize
bin/magento cache:clean

3D Secure

3D Secure 2 (3DS2) is handled automatically by VINR. No additional Magento configuration is required. When an issuer triggers a challenge flow, the customer is presented with the authentication step during checkout and returned to the Magento order confirmation page on completion. See 3D Secure for the underlying protocol details.

Webhooks

The VINR module registers a webhook listener at:

https://yourstore.com/vinr/webhook

Verify that this URL is reachable from the VINR dashboard under Developers → Webhooks → Add endpoint. The module validates the X-Vinr-Signature header on every incoming event.

Order status mapping:

Multi-store configuration

VINR Payments supports different API credentials per store view. In the Magento Admin, use the Store View scope selector (top-left dropdown in Stores → Configuration) to switch to the target store view, then enter store-specific API Key and Merchant ID values. This allows separate VINR accounts or merchant IDs for different brands within a single Magento installation.

Tokenization and saved cardsAskCopy

The VINR plugin integrates with the Adobe Commerce Vault framework. When a customer selects Save for later at checkout, VINR vaults the card and stores the resulting pm_ token in the Magento Vault. On subsequent checkouts, the customer can select a saved card from the stored-methods list without re-entering card details.

For subscription and recurring billing use cases, the Vault token is compatible with Magento Recurring Payments via a third-party Subscription extension. The VINR token stored in the Vault can be passed as the paymentMethod parameter for off-session charges. For the full tokenization API, see Tokenization.

In-person paymentsAskCopy

VINR for Adobe Commerce supports in-person payments via the VINR POS module, a separate Composer package that bridges the Magento order flow to VINR terminal readers. Install it alongside the core module:

composer require vinr/magento2-pos
bin/magento module:enable Vinr_Pos
bin/magento setup:upgrade && bin/magento cache:clean

The POS module adds a VINR Terminal payment method to the Magento Admin order creation flow, allowing staff to initiate a card-present payment from any order. For terminal setup, reader pairing, and go-live steps, see In-person payments.

Go liveAskCopy

bin/magento cache:clean

TroubleshootingAskCopy

Next stepsAskCopy