payerAuthEnrollService_challengeCode {#payer-auth-enroll-service-challenge-code}
================================================================================

Authentication type or challenge presented to the cardholder at checkout.  
This field is available only for the `Banque de France et Tresor Public`, `BNP Paribas France`, and `Credit Mutuel-CIC` processors.  
The challenge is issued after requesting secure transactions through the `Cybersource` payer authentication services.  
A *challenge* means that strong customer authentication is required. The challenge status does the following:

* Informs the issuer about the alternative authentication methods that the cardholder used.
* Enables you to override default values for one transaction at a time and increase the authorization acceptance rate at the risk of accepting a liability shift for the transaction.

Possible values:

* `01`: No preference.
* `02`: No challenge requested, but the reason is unknown.
* `03`: You requested the challenge. You can default to this value for every transaction when you see an increase in fraud rates.
* `04`: Challenge mandated. Strong customer authentication is required when one of the following is true:
  * Transaction amount exceeds 30 EUR and there have been at least five transactions on the payment card during the preceding week.
  * Cumulative amount for the payment card during the preceding week exceeds 100 EUR.
* `05`: No challenge requested because transactional risk analysis has already been performed.
* `06`: No challenge requested because the purpose of this transaction is to share data, not to move money.
* `07`: No challenge requested because strong consumer authentication has already been performed.
* `08`: No challenge requested because the cardholder is on a white list of exempt cardholders.
* `09`: Challenge requested by issuer. Determine whether the cardholder is on a white list of exempt cardholders.

This field defaults to `01` on merchant configuration and can be overridden by the merchant. EMV 3-D Secure version 2.1.0 supports values `01`-`04`. Version 2.2.0 supports values `01`-`09`.  
When you request the payer authentication and authorization services separately, get the value for this field from the payerAuthEnrollService_challengeCode request field.

Specifications {#payer-auth-enroll-service-challenge-code_d2403e139}
--------------------------------------------------------------------

* **Data Type:** Integer
* **Data Length:** 2

Mapping Information {#payer-auth-enroll-service-challenge-code_d2403e158}
-------------------------------------------------------------------------

* **REST API Field:** consumerAuthenticationInformation. challengeCode
* **SCMP API Field:** pa_challenge_code
* **Simple Order API Fields:**
  * ccAuthService_paChallengeCode
  * payerAuthEnrollService_challengeCode
    {#payer-auth-enroll-service-challenge-code_d2403e183}