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, meaning 3D Secure (3DS) 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 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 Method	Who Collects Card Details	Merchant PCI Responsibilities
   Payment Page (hosted page)	Nuvei – Using the Nuvei Payment Page.	Submit the Simplest SAQ-A form (stating you outsource PCI to Nuvei). Perform quarterly scans
   Simply Connect	Nuvei – Collects directly from Nuvei form merchant embeds in its payment page.	Submit the Simplest SAQ-A form (stating you outsource PCI to Nuvei). Perform quarterly scans
   Web SDK with Nuvei Fields	Nuvei – Collects directly from Nuvei Fields merchant embeds in its payment page.	Submit the Simplest SAQ-A form (stating you outsource PCI to Nuvei). Perform quarterly scans
   Web SDK without Nuvei Fields	The merchant – Collects and passes to Nuvei directly from the merchant's 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 the merchant's checkout or payment page and passes the details to Nuvei from the backend.	If you store card details for even a short time, submit the detailed SAQ-D form. If you immediately delete card details, submit the moderate SAQ-A EP form (shorter than the SAQ-D). Agree to conform to the required security standards. Perform quarterly scans. Depending on your annual number of transactions with a card scheme, you might be required to undergo a Level 1 ROC. For more information, see the card scheme's website. For example: VISA Mastercard AMEX

Key Features and Benefits

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 3DS 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.

Simply Connect

Simply Connect allows you to keep control over your functionality, UI/UX, design, and payment flow, while enjoying a range of benefits.

• Simple implementation.
• Full 3DS and PCI compliance with minimum effort.
• End-to-end payment process in one call.
• Customizing UI / UX / Processing:
  • General UI Customization – Control text and local options as well as the general look and feel.
  • Payment Customization – Control the payment flow and payment methods displayed for particular users or use cases. Control payment method processing behavior for the various cards, PayPal, Google Pay, Apple Pay, other the APMs.
  • Event Callbacks – Hooking into the payment process events to access event notifications, affect and react to events in the payment process, and improve the user experience.
    Full customization, locale customization, controlling the payment flow and the payment methods.
• Accessibility compliance:
  • Navigation and interaction through the checkout flow using only the Tab, Spacebar, and Enter keys.
  • Screen reader navigation support.

Web SDK and REST API

The Nuvei Web SDK and REST API products provide you with a flexible, dynamic payment solution, which is fully customizable, but 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 3DS, which is mandated by the card schemes. The 3DS 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 3DS.
• 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 3DS 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.