3DS requirements

Run card transactionRun card transaction

For using three-domain secure (3DS), the following requirements need to be met, depending on the transaction:

Initial transactions

Initial or first-time transactions may be subject to cardholder authentication depending on the merchant account or region.

Nexio provides transaction information to the gateway and responds to your system with a 3DS redirect URL where required. We recommend, therefore, that your system be equipped to handle any 3DS redirect returned by Nexio.

Nexio’s check3ds flag allows you to indicate whether your system is equipped to handle a 3DS redirect.

  • If set to true, Nexio returns the redirect URL to you or prompts users to continue with the authentication if using the ecommerce iframe.
  • If set to false, Nexio attempts to process transactions without 3DS. However, if 3DS is required, Nexio instead returns an error so your system does not get hung up with the 3DS workflow.

Nexio recommends that you also send the paymentType parameter when sending check3ds as true. If you do not include paymentType in a 3DS transaction, the system assumes the following:

  • If there is a cached or passed card security code, the system assumes a type of initialScheduled
  • If there is not a card security code, the system assumes a type of scheduled (see below about Recurring transactions)

Recurring transactions

To process recurring transactions, follow the steps below depending on whether your gateway supports the paymentType parameter.

If the initial transaction had a paymentType of initialMoto, the gateway or processor may not allow subsequent transactions for that payment method.

If your gateway supports paymentType, do the following:

  • Set check3ds: true for all recurring transactions.
    This indicates to Nexio that the integrator is equipped to handle a 3DS redirect if required.
  • Set the correct value for paymentType as described in the paymentType table.

If your gateway does not support paymentType, do the following:

  • Set check3ds: false for all recurring transactions.
    This indicates to Nexio that either the transaction is using a payment token that has been previously authenticated or used for processing a transaction, or that your system is not equipped to handle a 3DS redirect workflow.

Nexio determines whether to flag transactions as recurring to the gateway. The transaction gets flagged as recurring depending on the paymentType sent. If no paymentType is sent, then the transaction gets flagged as recurring if the security code is not present and the system assumes a paymentType of scheduled.

Next steps

Complete the steps for Using 3DS to run transactions with either the ecommerce iframe or the API.