As part of the 3D-Secure v.2 flow, our system performs several transactions that are used to check the enrollment status of the customer’s card and to obtain the verification details of the card. These transactions appear in the Control Panel Transaction Report under transaction types initAuth3D and Auth3D.

They have no financial value and you can filter them out when extracting your Transaction Report by going to the Transactions tab, pressing on the Transactions Type dropdown menu, and selecting only the Financial checkbox.

This error points to the fact that your account is not active. Please contact your account manager.

Our system is expecting a server response to the DMN callback indicating that the callback is received successfully by the merchant. The expected response is status code 200 – OK. If we do not receive this response, we consider the callback not to be received successfully and it enters retry mode.

While in Retry mode, the DMN callback is resent every 15 minutes for 24 hours or a total of 96 times. Once all retries run out and the merchant does not respond with status code 200 to any of the retries, the system stops resending the callback and records it as failed.

Our Payment Page is the primary option for merchants that wish to completely descope from the PCI requirements since the page is handling all secure card data.

The Nuvei Fields service allows you to descope from the PCI while still using a server-to-server transaction flow.

For more information, please refer to Nuvei Fields and PCI and Tokenization.

These parameters are used by our Risk system to detect and prevent fraudulent transactions, therefore, they are mandatory.

In case of bank Decline, Nuvei presents the Decline reason provided by the issuer bank so that the merchant and the customer can act upon it. If a generic Decline reason is presented, the cardholder has to contact their bank for more details.

You cannot refund more than a certain percentage of your total balance on your Nuvei account at any given time. The standard limitation is that you cannot refund/payout more than 100 percent of your deposits for the past 7 days. Attempting a refund or payout above this amount triggers the “Credit amount exceeds total charges” error.

You can change the default time zone in which your reports are generated by going to your production Control Panel and changing the time zone (see Setting the Time Zone).

There are several parameters that you can use – customData, merchant_unique_id or clientUniqueId, and the customFieldX parameters. The customData, merchant_unique_id, and clientUniqueId parameters are returned in the response to your system and are visible in the Transaction Report in your Control Panel. On the other hand, the customFieldX parameters are only returned in the response to your system.

You can find the parameters in the full list of Payment Page parameters or at the payment.do parameters list for the REST API integration at https://docs.nuvei.com/api/main/indexMain_v1_0.html?json#payment.

Whenever you encounter an error, you receive a relevant error code.

In this case, the Error Code is 1136.

A field that is mandatory for the transaction is missing or has an incorrect value. Note that per Risk configuration the following parameters must be included (besides the API mandatory fields):

• billingAddress: country; email
• deviceDetails: ipAddress
• paymentOption: cardHolderName

The Nuvei Cashier page includes a validation check that prevents customers from reloading the page or storing the request and loading it later. This feature validates the Checksum value. If it was used before, the request is canceled and the customer is shown a relevant error message.

To activate this validation, please contact Nuvei’s Integration Team.

The notification URL for withdrawals cannot be sent dynamically, unlike the URL for deposits. Please provide your withdrawals notification URL to Nuvei’s Integration Team.

The DMN callbacks for deposits are asynchronous. However, the pre-deposit DMN callbacks and the initial withdrawals are synchronous. The latter two types of notification are synchronous since our system is expecting a response by the merchant – acknowledgment of the request and decision.

Please refer to Handling Withdrawal DMNs for more information.

The Nuvei Hosted Payment Page is capable of sending analytics events to the parent frame if it is opened in an IFrame. For a full list of the events and their triggers, please see our Cashier Events Guide.

By default, our withdrawal cashier page keeps the customer on the page after they request a withdrawal. To redirect the customer to your page, you must enable this setting for your account. Please contact Nuvei’s Integration Team to set this up. The redirect URLs can be set up statically in your account settings or can be provided dynamically via request parameters – successUrl and failUrl.

Nuvei Fields collects only the sensitive card data and the Cardholder name can be collected normally. Please collect it and pass it in the createPayment() request via the parameter “cardHolderName” as described in Step 8 in Simple Card Integration.

The approved method for storing card details for future use is to perform an Authorization transaction for amount 0. You can read more about this feature in our Zero Authorization article.

Yes, this is a real status and instructs you that the transaction is not completed yet. The end user needs to be redirected to a web page to complete the transaction. There are two cases in which this response is returned:

• 3D-Secure – The user needs to be redirected to paymentOption.threeD.acsUrl. See our 3D-Secure v2 Payment topic for full details.
• An APM that requires redirection – The URL is on paymentOption.redirectURL.
  • See the Redirect to the APM for REST API topic for full details.
  • Or see the Redirect to the APM for Web SDK topic for full details.

Both methods are used for the same purpose – to authenticate the merchant and generate a session. The openOrder.do request should be used if you intend to use sessionToken with our Web SDK solution, and the getSessionToken.do should be used if you intend to use our REST API processing methods.

Currently, we do not yet support IPv6 format addresses. Please use the IPv4 format addresses only.