HomeProduct DocsAPI ReferenceChangelog
RecurlyAPI GuidesRecurly.jsWebhooksAPI ReferenceSupportBook demo
Product Docs

Nuvei

Connect Nuvei to Recurly to process card, Apple Pay, and Google Pay transactions globally — with 3DS2 support, dynamic descriptors, and AVS/CVV verification.

Early Access Nuvei is currently available in Early Access. Contact [email protected] to request access.
Nuvei is a full-service payment gateway supporting recurring subscriptions, ecommerce, MOTO, and 3DS transactions. Integrating it with Recurly gives you access to a wide range of card brands, Apple Pay, Google Pay, and global currency support. Recurly.js is required for all new card signups and billing info updates.
Available on all Recurly plans

Limitations

Recurly.js required Nuvei requires browser information on all transactions. Use Recurly.js for all new signups and billing info updates — regardless of whether you're using 3DS. Browser details are collected automatically by Recurly.js. For 3DS on stored billing info, see Recurly.js with Stored Billing Information.
  • No raw card details or billing info IDs via API — Sending raw card data or billing info IDs without Recurly.js is not supported due to Nuvei's strict browser information requirement.
  • Site mode switching not supported — Switching between production and development modes on a single site is not supported. Maintain separate Recurly sites for production and development testing.
  • CVV required for all CIT card payments — This includes MOTO. Collect the CVV for all return customer transactions, signups, and one-time transactions. Recurly does not store CVV codes.
  • Gateway tokens and chargeback notifications not supported — These features are not available for Nuvei at this time.
  • Admin UI processing may not be supported — Nuvei's CVV and Customer IP requirements can prevent transaction processing via the Recurly Admin UI. For MOTO transactions, integrate via the API and collect the CVV from your customer directly.

Definition

Nuvei is a payment gateway that supports recurring subscriptions, ecommerce, MOTO, and 3D Secure transactions. It integrates with Recurly via REST API credentials and requires Recurly.js for all customer-facing card interactions due to browser information requirements. For pricing and new account setup, contact your Nuvei representative directly.

Key details

FeatureDetails
Services that work with RecurlyRecurring subscriptions, payments (eCommerce and MOTO), 3D Secure
Supported operationsAuthorize and Capture, Purchase, Refund, Verify, Void, Recurring, Unscheduled MIT
Supported payment typesCredit card, Apple Pay, Google Pay
Supported card brandsVisa, Mastercard, Amex, Discover, JCB, Diners Club, Union Pay
Unified 3DS2 supportedYes
Card on file supportedYes
RegionsWorldwide
CurrenciesSee all available
Additional feature supportBilling and shipping information, Level 2 data, dynamic descriptors, AVS / CVV checks, line item passthrough

Set up Nuvei with Recurly

Step 1: Obtain your Nuvei credentials

In your Nuvei account, go to the REST API Configuration tab and click Generate New API Key. You'll also need the following credentials — see Nuvei's API credentials guide for details:

  • Site ID
  • Merchant ID
  • Secret
  • Source Verification Key

If you intend to use 3DS, also gather:

  • Acquirer BIN (6 digits)
  • Acquirer Merchant ID
  • Acquirer Country

Step 2: Set up Nuvei webhooks

1

Open Events Configuration

In the Nuvei dashboard, go to Settings → My Account → Events Configuration and choose Client from the dropdown.

2

Add the webhook endpoint

For the Chargeback and Chargeback/Dispute events, enter your Recurly callback URL using the format below. You may need to repeat this for each event.

https://callbacks.recurly.com/nuvei/YOUR_SUBDOMAIN

3

Enable the events

Toggle each event's status to ON.

Step 3: Enter credentials in Recurly

1

Open Payment Gateways

In Recurly, navigate to Configuration → Payment Gateways and select Nuvei.

2

Enter your credentials

Input your Merchant ID, Site ID, Secret Key, and Source Verification Key.

Step 4: Enable 3D Secure (optional)

Check Enable 3D Secure and enter your Acquirer BIN, Acquirer Merchant ID (CAID), and Acquirer Country. Contact Nuvei directly to obtain these values.

Before enabling 3DS Confirm that your consumer-facing website domain (URL) and your business's main MCC value are both present in your Default Business Entity in Nuvei before enabling 3DS.

Step 5: Enable currencies

Select the currencies your Nuvei gateway is approved to accept.

Step 6: Save the gateway

Click Add Payment Gateway. If you're editing an existing configuration, this button reads Update Payment Gateway.

Step 7: Configure AVS and CVV checks (optional)

AVS and CVV settings apply to all supported gateways, not just Nuvei. Configure these in Configuration → Payment Settings.

Enable Address Verification (AVS)

1

Open Payment Settings

Navigate to Configuration → Payment Settings and scroll to Address Verification Check.

2

Select your AVS rules and save

Choose Enabled (default) or Disabled, then click Save Changes. When enabled, transactions where the address doesn't match the issuer's records will be rejected.

Enable Card Code Verification (CVV)

1

Open Payment Settings

Navigate to Configuration → Payment Settings and scroll to Credit Card Verification Code Check.

2

Enable CVV and save

Set the radio button to Enabled, then click Save Changes. Invalid or mismatched CVV submissions will be rejected based on issuer feedback.

Step 8: Test your integration

In Recurly, go to Configuration → Payment Gateways, select your Nuvei gateway, and click Options → Test Configuration. A confirmation message confirms Recurly can communicate with Nuvei successfully.

Step 9: Go live

Once testing passes, you're ready to accept live transactions. Monitor your transactions in both Recurly and Nuvei to confirm everything is running as expected.

Tip Ensure PCI compliance when handling sensitive card data. For questions specific to your integration, contact your Nuvei representative or Recurly Support.

Production and sandbox behavior

Nuvei's production and sandbox environments are entirely separate endpoints. If you create a Nuvei gateway instance while your Recurly site is in Production or Sandbox mode, transactions route to the corresponding Nuvei environment automatically.

If your site mode changes — for example, being moved to Development mode by Support — existing gateway instances will stop functioning. You'll need to create new gateway tiles and disable the old ones.

Warning Gateway configuration is not copyable between site modes. If you're going live from a development site, you must re-onboard the Nuvei gateway from scratch — the copied gateway does not share the same site identifiers. Best practice is to keep each Recurly site in a fixed mode and add gateway accounts only after confirming the correct mode.


Did this page help you?