Introduction

Nuvei supports scenarios that support a range of merchant payment models.

For example, some merchants require a one-time payment to charge their customers, while others have subscriptions based on recurring payments. In addition, merchants handle 3D-Secure (3DS) differently.

This page summarizes the following payment scenarios:

• 3D-Secure
  • Manage 3DS
  • Always 3DS
  • 3DS-Only (MPI only)
  • Liability Shift (External MPI)
• Non-3DS
• MIT Recurring Payments
• APM Payments

3D-Secure

Manage 3DS

Merchant Requirement

I would like Nuvei to control my 3D management (to process 3D-Secure).

I would like Nuvei to manage all aspects of the 3DS workflow and avoid the implementation complexities (for example, when to process with 3DS; when and how to perform 3DS fingerprinting; when and how to perform the challenge; and so on.)

Nuvei Solutions

• Using Payment Page – Seamless integration.
• Using Simply Connect – Seamless integration.
• Using Web SDK:
  • Use the createPayment() method.
  • For full details, see Quick Start for Web SDK .
• Using Server-to-Server REST API 1.0:
  • When the merchant sends the initial /payment request, include the threeD class containing the 3DS data.
  • When a 3DS challenge is required, after presenting the challenge to the customer, send relatedTransactionId in the final /payment request. Specify the transactionId from the response to the first /payment request.
  • For full details, see REST 1.0.
  For full 3DS details, see 3D-Secure Explained and 3DS Implementations.

Always 3DS

Merchant Requirement

I want to only perform 3DS transactions. If a payment request fails 3DS authentication, then abort the payment and do not continue processing any transaction.

Some merchants wish to perform only 3DS transactions.

Nuvei Solution

The Always 3DS scenario is similar to the Manage 3DS scenario described above. In the Always 3DS scenario, if 3DS authentication fails, then Nuvei aborts the payment, and does not continue processing any transaction. For example, when the card or issuer is not registered for 3DS. On the other hand, in the Manage 3DS scenario, if 3DS authentication fails, Nuvei attempts to process the payment without 3DS.

3DS MPI-Only

Merchant Requirement

I want to use Nuvei for 3DS authorization and authentication, not for processing transactions.

I only want to use Nuvei’s 3DS authorization and authentication services, and then continue to process the transaction using another payment provider.

Nuvei Solutions

• Payment Page – Not available.
• Simply Connect – Not available.
• Using Web SDK:
  • Use the authenticate3d() method.
  • For full details, see 3DS MPI-Only Web SDK.
• Using Server-to-Server REST API 1.0:
  • Perform a 3DS authentication-only transaction by sending an /authorize3d request and then verify it by sending a /verify3d request.
  • For full details, see 3DS MPI-Only REST.

Liability Shift (External MPI)

Merchant Requirement

I want to perform liability-shifted transactions using 3DS authentication data that I received from my (external) MPI provider.

Some merchants prefer to perform the 3D-Secure service using a different party. For example, having one 3DS provider and multiple payment providers.

Nuvei Solutions

• Payment Page – Not available.
• Simply Connect – Not available.
• Web SDK – Not available.
• Using Server-to-Server REST API 1.0:
  • When the merchant sends the initial /payment request, include the externalMpi class with the authentication output from the third-party 3DS provider.
  • For full details, see 3DS External MPI.

Non-3DS

Merchant Requirement

I want to make a simple non-3D-Secure transaction.

This is relevant to merchants who operate in parts of the world that do not support 3DS.

Nuvei Solutions

• Using Payment Page – Seamless integration.
• Using Simply Connect– Seamless integration.
• Using Web SDK:
  • Use the createPayment() method.
  • For full details, see Quick Start for Web SDK.
    
    Before using Web SDK for non-3DS payments, the merchant must contact Nuvei and have us configure the merchant’s account for the non-3DS payment flow.

• Using Server-to-Server REST API 1.0:
  • Send the initial /payment request without the threeD class.
  • For full details, see REST 1.0.

MIT Recurring Payments

Merchant Requirement

I want to manage a recurring payment plan in my system.

Nuvei Solutions

Processing MIT (Merchant Initiated Transaction) recurring payments requires two steps:

• Step 1: Initiating a Recurring Payment Facility
• Step 2: Performing Subsequent Recurring Payments

Step 1: Initiating a Recurring Payment Facility

• Using Payment Page – Seamless integration.
• Using Simply Connect – Seamless integration.
• Using Web SDK:
  • On the server side, send an /openOrder API request and specify isRebilling: “0” to define the initial MIT. Then, send a createPayment() request.
  • For full details, see the Submit the Initial MIT Payment section on the Merchant-Initiated Transactions page.
• Using Server-to-Server REST API 1.0:
  • When the merchant sends the initial /payment request, specify isRebilling: “0” to define the initial MIT.
  • For full details, see Submit the Initial MIT Payment section on the Merchant-Initiated Transactions page.
• The merchant can include 3DS parameters in the initial /payment request, if required.

Step 2: Performing Subsequent Recurring Payments

• Payment Page – Not available (use Server-to-Server below).
  
• Simply Connect – Not available (use Server-to-Server below).
• Web SDK – Not available (use Server-to-Server below).
• Using Server-to-Server REST API 1.0:
  • When the merchant sends the initial /payment request, specify:
    • isRebilling: “1” – Indicates that this is a subsequent MIT.
    • relatedTransactionId – Specify the transactionId from the response to the first /payment request in Step 1.
  • For full details, see Submit Subsequent MIT Payment.

APM Payments

Merchant Requirement

I want to process APM payments using Nuvei.

Nuvei Solutions

• Using Payment Page – Seamless integration.
• Using Simply Connect – Seamless integration.
• Using Web SDK:
  • (Optional) The merchant can send a getAPMs() request to retrieve a list of supported and relevant APMs for the customer to choose from.
  • Send a createPayment() request and include the alternativePaymentMethod class containing the relevant payment method details. If applicable, the customer is automatically redirected to complete the payment.
  • For full details, see APM Payments with Web SDK.
• Using Server-to-Server REST API 1.0:
  • (Optional) The merchant can send a getAPMs() request to retrieve a list of supported and relevant APMs for the customer to choose from.
  • When the merchant sends the initial /payment request, include the alternativePaymentMethod class containing the relevant payment method details. If applicable, the customer is automatically redirected to complete the payment.
  • For full details, see the APM REST API section on the APM Integrations and Flows page.