This page details what to do when sending us a transaction for which you already have an external 3DSv2 authentication.

Introduction

This document describes the way to use an external 3DS Server along with the PayXpert low-level transaction processing API.

Context

The PayXpert low-level transaction processing API provides a full implementation of the EMV 3DS v2 including the authentication workflow.

This is the recommended way of integrating, nevertheless some merchants or payment service providers may have a way of doing this authentication workflow on their side and just need to process the transaction by providing the authentication result only. The following section describes what needs to be provided in that case.

Implementation

Authentication data

Handling the EMV 3DS authentication returns some authentication result data that must then be forwarded to the acquirer of the transaction.

When using the internal implementation of the 3DS most of these data are obtained by the embeded 3DS Server. In the case of the use of an external 3DS Server these information must be provided through the payment API.

The concerned data are:

• CRes: the detailed result of the authentication as a Base64 encoded JSON string

• Authentication Value: payment system-specific value that may be used to provide proof of authentication, binary string encoded as Base64

• ECI: payment system-specific value that indicates the result of the attempt to authenticate the cardholder

• Directory Server Transaction Identifier: a UUID generated by the directory server for this authentication operation

API dedicated fields

To have the complete list of fields to process a transaction, please refer to the official API documentation at: https://developers.payxpert.com/gateway/..

Specific fields are used in the transaction processing low-level API to provide the authentication data from an external 3DS Server, the table below describes them.

External 3DS Server API Parameters: