- Combining the Authentication and the Authorization Services
- Implementing SDK Payer Authentication
- Authentication Examples Using Primary Account Numbers
- Authentication Examples Using Digital Payment (Google Pay)
- Authentication Examples Using TMS Tokens
- Authentication Examples Using Flex Microform Tokens
- Authentication Examples Using Network Token/Tokenized Cards
- Authentication Examples of Merchant-Initiated Transactions
Interpreting the Response
In EMV 3-D Secure, there are two possible responses:
- Frictionless: No challenge or stepup to the cardholder. While frictionless authentication can indicate a successfully authenticated outcome because the customer's card is enrolled in a payer authentication program, it can also result from the bank failing or rejecting authentication without challenging the cardholder. In the frictionless authentication flow, you receive a PAResStatus of eitherY,A,N,I,R, orUwith an associated ECI value. With successful frictionless authentication, the PAResStatus =YorAand you receive a CAVV. You may also receive a PAResStatus =Iindicating successful authentication, but it might not include a CAVV.
- Challenge: The response contains PAResStatus =C. A challenge response has a payload and contains an ACS URL and a step up URL. Challenge the cardholder to provide additional authentication information and display an authentication challenge window to the cardholder so the cardholder can respond to a validation request and receive a validation response.