• Documentation
  • API Reference
  • Documentation
  • API Reference
Expand All Collapse All
  • Payment Overview
    • Introduction
    • Choosing an Integration Method
  • Accept Payment
    • Payment Page
      • Quick Start
      • Input Parameters
      • Output Parameters
    • Web SDK
      • Quick Start
      • Nuvei Fields
        • Styling
      • Additional Functions
      • APM Payments
      • Tokenization-Only Flow
      • Scenarios
      • Using ReactJS
        • Full Samples
        • Sandbox Examples
      • FAQs
    • Checkout
      • Quick Start
        • UI Customization
        • Payment Customization
        • Advanced Controls
        • Checkout Examples
      • Server-to-Server
      • Payment Scenarios
      • Mobile SDKs (Beta Release)
        • Android Mobile SDK (Beta Release)
        • iOS Mobile SDK (Beta Release)
      • Flow Diagrams
      • Plugins
        • Magento
          • Rebilling with Magento
        • WooCommerce
          • Rebilling with WooCommerce
        • PrestaShop
          • PrestaShop with Web SDK
          • PrestaShop with Checkout
        • OpenCart
        • Shopify (via AsiaBill)
        • Mirakl
        • Salesforce
        • SAP
        • WIX
      • Marketplaces
    • Features
      • Authentication
      • Financial Operations
        • Refund
        • Void
        • Auth and Settle
        • Partial Approval
        • Currency Conversion (DCC and MCP)
        • Payout
      • Card Operations
        • Card-on-File
        • PCI and Tokenization
        • Zero-Authorization
        • Merchant-Initiated Transactions (MIT)
        • Blocking Cards
      • Subscription (Rebilling)
      • 3D-Secure
        • 3D-Secure Explained
        • 3DS Implementations
          • 3DS MPI-Only Web SDK
          • 3DS MPI-Only REST
          • 3DS External MPI
          • 3DS Responses
        • 3DS Functions
          • 3D-Secure Fingerprinting
          • 3D-Secure Authentication Challenge
      • Webhooks (DMNs)
        • Payment Transaction Requests
        • Control Panel Events API
    • Guides
      • Testing Cards, APIs and APMs
        • Testing Cards
        • Testing APIs with Postman
        • Testing APMs
      • Response Handling
      • Alternative Payment Guides (APMs)
      • Airline Ticket Guides
        • Airline Addendum
        • External Authorization Addendum
      • Payment Facilitators (PayFac)
      • Cashier
        • Cashier Events Guide
        • Cashier Features
      • Withdrawal Guide
      • Risk Guide
        • Appendix 1: Transaction Types
        • Appendix 2: Credits and Payouts
        • Appendix 3: Fraud to Sale Programs
        • Appendix 4: Compliance Programs
        • Appendix 5: Chargebacks
      • eKYC Guide
      • Server SDKs
        • Java SDK
        • .NET SDK
        • PHP SDK
        • Node.JS SDK
      • Fast Track Onboarding Developer Guide
      • Currency Conversion Guides
        • Multiple Currency Pricing (MCP)
        • Dynamic Currency Conversion (DCC)
          • DCC in Cashier or Payment Page
          • DCC in REST API Workflows
          • DCC in Web SDK Workflows
      • Website Compliance Guides
    • Additional Links
      • FAQs
      • API Reference
      • Release Notes
      • Country and Currency Codes

    Choosing an Integration Method

    On this page:
    • Factors to Consider
    • Nuvei Integrations Compared
    • Key Features
      • Payment Page
      • Web SDK and REST API

    Factors to Consider

    These are some of the key factors to consider when choosing the Nuvei product set that suits your requirements best:

    1. Your industry segment and business needs:
      • Whether you need to process single payments, repeat customers, or recurring payments.
      • Does your business activities fall into the scope of the PSD2 directive, or into 3D-Secure v1 Strong customer authentication.
    2. Your development resources:
      The size, skill set, extensibility, and availability of development resources.
    3. PCI DSS certification level:
      The level of your involvement in the collection of customer credit card details, as well as your PCI reporting responsibilities, is different for each Nuvei product set (integration type), as described below:
      Merchant PCI Responsibilities
      Nuvei Integration TypeWho Collects Card Details

      Merchant PCI Responsibilities

      Payment Page
      (hosted page)
      Nuvei –
      Using Nuvei Payment Page.
      • Submit the Simplest SAQ-A form
        (stating you outsource PCI to Nuvei).
      Web SDK FieldsNuvei –
      Collects directly from the merchant page.
      • Submit the Simplest SAQ-A form
        (stating you outsource PCI to Nuvei).
      CheckoutNuvei –
      Collects from their checkout or payment page.
      • Submit the Simplest SAQ-A form
        (stating you outsource PCI to Nuvei).
      FrontEnd API
      Card Tokenization
      The merchant –
      Collects and passes it to Nuvei directly from their frontend.
      • Submit the Moderate SAQ-A EP form (shorter than the SAQ-D).
      • Agree to conform to the required security standards.
      • Perform quarterly scans.
      Server-to-Server
      • REST API
      • Server-Side SDK
      The merchant –
      Collects from their checkout or payment page.
      • Submit the Detailed SAQ-D form.
      • Agree to conform to the required security standards.
      • Perform quarterly scans.

    Nuvei Integrations Compared

    These are some of the key features of the Nuvei solution sets (integration platforms):

    Features Compared

    ProductQuick IntegrationCustomizationPCIMulti-PSPNotes
    Payment PageMerchant: Logo and Main colors.
    Nuvei: Full customization.
    • Basic customization.
    • No control of UI/UX.
    CheckoutFullFull control, PCI, Simple integration process.
    Web SDKFullFull control of UI/UX, PCI, Simple integration process.
    Server-to-Server
    • REST API
    • Server-Side SDK
    Fullnote * • 3D-Secure fully implemented by the merchant.
    • Full control of processes.
    * A merchant that wishes to descope PCI can combine API with SDK.

    Key Features

    Payment Page

    The Nuvei Payment Page provides the quickest way to integrate to Nuvei and benefit from all our features in a single solution.

    • You only need to load the page via IFrame or by full page redirect and all features and functionalities are seamlessly integrated.
    • It provides the full range of payment methods – credit and debit cards, eWallets, bank transfers and local payment methods, presented smartly to the customer, based on their IP address.
    • The page handles all complex interactions with the card issuer, such as 3D-Secure verification and is fully compliant with PSD2.
    • The Payment page also provides useful features such as currency conversion, decline recovery functionality, different page layouts and styles based on the customer’s device, quick deposit and withdrawal functionalities, creation of subscriptions, as well as eKYC.
    • The Payment Page can be used to collect only the card data from the customer, as well as personal details, billing and shipping details, which can then be passed to the merchant.
    • Using the Payment Page requires the lowest level PCI SAQ form – SAQ-A – and is perfect for merchants who wish to completely descope PCI.
    • The Payment Page can be customized with a number of different validations and checks aimed at preventing duplicate charges, and to establish a one-to-one relationship between customer and card or account, etc.
    • In addition, you can even perform basic customization of your Payment Page via the Page Builder menu located in the Control Panel.

    Web SDK and REST API

    The Nuvei Web SDK and REST API products provide you with a flexible, dynamic payment solution, that is fully customizable, but at the same time requires higher development effort.

    • The Web SDK is a JavaScript library that you can use on your own payment page to perform end-to-end payments.
    • The strength of the Web SDK is its integration simplicity, yet completely freeing from any PCI overheads and responsibilities, while giving you complete control over the UI and UX.
    • The considerable benefit of integration simplicity is especially valuable when you consider the complexities involved in 3D-Secure v2, which is mandated by the card schemes. The 3D-Secure v2 mandate introduces a compulsory flow that turns any API based solution (including Nuvei’s) from a simple API call to a complete workflow implementation, which requires a thorough understanding of 3D-Secure v2.
    • REST API offers an array of methods that allow customers to one-time or recurring payments, perform settlements, refunds, voids, or payouts, and manage user and payment method data stored in our system.
    • By combining Web SDK, for accepting payments under the 3D-Secure v2 mandate, with REST API methods, for all the other operations, merchants can build the payment flow entirely on their side, and benefit from retaining control over all the processes. However, the price to be paid for this level of control is the increased merchant development effort required to implement features, which would have been provided seamlessly by our Payment Page.
    Nuvei Integration Type Who Collects Card Details Merchant PCI Responsibilities
    Nuvei Integration Type
    Who Collects Card Details

    Merchant PCI Responsibilities

    Nuvei Payment Page
    (hosted page)
    Nuvei –
    Using Nuvei Payment Page.
    • Submit the Simplest SAQ-A form, (stating you outsource PCI to Nuvei).
    Web SDK Fields Nuvei –
    Collects directly from the merchant page.
    • Submit the Simplest SAQ-A form, (stating you outsource PCI to Nuvei).
    Nuvei Checkout Nuvei –
    Collects from their checkout or payment page.
    • Submit the Simplest SAQ-A form, (stating you outsource PCI to Nuvei).
    Frontend Tokenization
    API methods: cardTokenization
    The merchant –
    Collects and passes it to Nuvei directly from their frontend.
    • Submit the Moderate SAQ-A EP form (shorter than the SAQ-D).
    • Agree to conform to the required security standards.
    • Perform quarterly scans.
    Server-to-Server
    • REST API
    • Server-Side SDK
    The merchant –
    Collects from their checkout or payment page.
    • Submit the Detailed SAQ-D form.
    • Agree to conform to the required security standards.
    • Perform quarterly scans.

     

    Product Quick Integration Customization PCI Multi-PSP Notes
    Product
    Quick Integration
    Customization
    PCI
    Multi-PSP
    Notes
    Payment Page Merchant: Logo and Main colors.
    Nuvei: Full customization.
    • Basic customization.
    • No control of UI/UX.
    Checkout Full Full control, PCI, Simple integration process.
    Web SDK Full Full control of UI/UX, PCI, Simple integration process.
    Server-to-Server
    • REST API
    • Server-Side SDK
    Full note * • 3D-Secure fully implemented by the merchant.
    • Full control of processes.
     
    2022 Nuvei. All rights reserved.