logo Mercanet

Release 24.3

go directly to content

Search by keywords

initialChallengeMode3DS

To search in the page use Ctrl+F on your keyboard

Holder authentication level requested on initial transaction.

Format
ANS20(restricted values)
ANS
Any character is accepted
restricted values
Indicates a restricted list of accepted values.

Contained in

Methods

Methods containing the data and the availability per connector
Methods / Reports inApp office paypage office batch walletpage
cardOrder Unavailable view Unavailable Unavailable Unavailable
getTransactionData Unavailable view Unavailable Unavailable Unavailable
walletOrder Unavailable view Unavailable Unavailable Unavailable
cardOrder (batch) Unavailable Unavailable Unavailable view Unavailable
walletOrder (batch) Unavailable Unavailable Unavailable view Unavailable

Values

CHALLENGE
The merchant desired authentication challenge mode is to have a client authentication. In other words, it is a “challenge” request
CHALLENGE_MANDATE
The merchant need is to apply the regulatory mode to have a strong customer authentication (for example for the first payment of payment schedule)
NO_CHALLENGE
The merchant desired authentication challenge mode is to have no customer authentication. In other words, it is a “challenge” request
NO_CHALLENGE_DTA
The merchant does not want customer authentication in a Direct to Authorize kinematics
NO_CHALLENGE_TRA_ACQ
The merchant desired no authentication of the cardholder by invoking the TRA acquirer exemption. It’s a request for “Frictionless”.
NO_CHALLENGE_TRA_ACQ_DTA
The merchant wishes to bypass cardholder authentication by invoking the Acquirer TRA exemption. This is a Direct to Authorize request.
NO_PREFERENCE
The merchant has no desired authentication challenge mode