Overview

Nuvei supports several payment flows to accommodate 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 payment. In addition, many merchants handle 3D-Secure differently.
This page summarizes the main merchant payment flows:

• 3D-Secure
  • Manage 3D-Secure
  • Always 3D
  • 3D-Only (MPI only)
  • Liability Shift Payment (External MPI)
• Non-3D
• MIT/Recurring
• Alternative Payment Methods (APMs)

3D-Secure

Manage 3D-Secure (recommended for cards)

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 3D-Secure workflow and avoid the implementation complexities (e.g. when to process with 3D-Secure and which 3D-Secure version to use, how processing differs between the two 3D-Secure versions, when and how to perform 3D-Secure fingerprinting, when and how to perform challenge, etc.)

Nuvei Solutions

• Using Checkout Page: Seamless integration.
• Using Web SDK:
  • Use the createPayment() method.
  • For full details, see: Web SDK Quick Start.
• Using Server-to-Server:
  • When a 3D challenge is required, after presenting the 3DS Challenge to the customer, send a Liability Shift Payment and include the relatedTransactionId field containing the initial 3D-Secure payment_id.
  • When a 3D challenge is not required, then send a 3D-Secure /payment request and include the threeD block containing the 3D data.
  • For full details, see Server-to-Server.
  For full 3D details, see 3D-Secure Explained and 3DS Authentication Flows.

Always 3D

Merchant Requirement

I would like to perform 3D transactions only. If a payment request fails the 3D-Secure authentication, then abort the payment and don’t continue processing any transaction.

Some merchants wish to perform 3D-Secure transactions only.

Nuvei Solution

This is a sub-case of the Manage 3D-Secure scenario (described above), which does not continue processing the transaction if the 3D authentication fails.
In the standard the Manage 3D-Secure scenario, if 3D authentication fails (e.g. if the cardholder or issuer is not registered for 3D-Secure), then the system continues to process the payment as a non-3D transaction.

3D-Only (MPI only)

Merchant Requirement

I would like to run authorizer/authenticate 3D.

I would like to use Nuvei’s 3D-Secure authorization and authentication services only and then continue to process the transaction using another payment provider.

Nuvei Solutions

• Checkout Page – Not applicable
• Using Web SDK:
  • Use the authenticate3d() method.
  • For full details, see 3DS MPI-Only for Web SDK.
• Using Server-to-Server:
  • Perform a 3D Auth by using an /authorize3d() call and then verify it using a /verify3d() API call.
  • For full details, see 3DS MPI-Only for Server-to-Server.

Liability Shift Payment (External MPI)

Merchant Requirement

I want to run a liability-shifted transaction using 3D authentication that I received from my (external) MPI provider.
Some merchants prefer to perform the 3D-Secure service using a different party (e.g. having one 3D-Secure provider and multiple payment providers).

Nuvei Solutions

• Checkout Page – Not applicable
• Web SDK – Not applicable
• Using Server-to-Server:
  • Use /payment and include the externalMpi block that specifies the authentication output received from the third-party 3D provider.
  • For full details, see External MPI (Third-Party 3D-Secure).

Non-3D

Merchant Requirement

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

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

Nuvei Solutions

• Using Checkout Page: Seamless integration.
• Using Web SDK:
  • Use the createPayment() method.
  • See Web SDK Quick Start.
    
    Before using Web SDK for non-3D payments, you must contact Nuvei and have them configure your account for the non-3D payment flow.

• Using Server-to-Server:
  • Send 3D-Secure /payment requests without the threeD block.

Merchant Initiation Transaction (MIT) / Recurring

Merchant Requirement

I would like to manage a recurring plan on my system.

Nuvei Solutions

Nuvei offers seamless integration solutions to manage your recurring payment system on your behalf. These solutions conform to all the relevant rules prescribed by the various card schemes.

However, if you prefer to “self-manage” your recurring payment system, we also provide the full range of services needed to do that.

Steps

Processing recurring payments involves:

1. Initiating a “recurring payment” facility in the first payment request.
2. Followed by any number of subsequent payment requests.

Step 1: Initiating a Recurring Payment Facility

• Using Checkout Page: Seamless integration.
• Using Web SDK:
  • On the server-side, call the /openOrder API and set "isRebilling": "0" to define the initial MIT transaction.
    Then use the createPayment() method.
  • For full details, see: Merchant-Initiated Transactions (MIT).
• Using Server-to-Server:
  • Use /payment and set "isRebilling": "0" to define the initial MIT transaction.
  • For full details, see: Merchant-Initiated Transactions (MIT).

Step 2: Performing subsequent Recurring Payments

• Checkout Page – Not applicable
• Using Web SDK:
  • On the server-side, call the /openOrder API and set "isRebilling": "1" to indicate that this is a subsequent MIT transaction.
    Then use the createPayment() method.
  • For full details, see Merchant-Initiated Transactions (MIT).
• Using Server-to-Server:
  • Use /payment and include:
    • "isRebilling": "1" – To indicate that this is a subsequent MIT transaction.
    • relatedTransactionId – Returned from the initiating payment request in Step 1.
  • See Submit Subsequent MIT Payments or, for full details, see Merchant-Initiated Transactions (MIT).

Alternative Payment Methods (APMs)

Merchant Requirement

I would like to process APMs using Nuvei.

Nuvei Solutions

• Using Checkout Page: Seamless integration.
• Using Web SDK:
  • For full details, see Web SDK APMs.
  • Use the createPayment() method and include the alternativePaymentMethod block containing the relevant payment method details. You can also use the getAPMs() method to retrieve the relevant APMs for the customer.
  • The function automatically redirects the customer for the completion of the payment.
• Using Server-to-Server:
  • Use the /payment method and include the alternativePaymentMethod block.
  • Use the /getMerchantPaymentMethods method.