Scheme passkeys<\/h3>
Checkout using registered passkey biometrics.<\/p><\/div><\/p><\/a><\/div>\n","url":"https:\/\/docs.adyen.com\/online-payments\/authentication","articleFields":{"description":"Learn how Adyen optimizes the authentication process for online card payments.","feedback_component":true,"filters_component":false,"section_label":"Features"},"algolia":{"url":"https:\/\/docs.adyen.com\/online-payments\/authentication","title":"Authentication","content":"Strong customer authentication (SCA) requires shoppers to verify their identity for card-not-present transactions. This can reduce fraud and fraudulent chargebacks. Successful authentication can also result in a liability shift from you to the issuer.\nIn some regions and markets, regulations mandate SCA, including PSD2 in the EEA and the Payment Services Regulations 2017 in the UK. In markets without an SCA mandate, issuers can still use authentication data to assess transaction risk.\nTo support these requirements, you can implement authentication in your regular payment flow. This lets shoppers complete authentication when it is required and lets Adyen use the authentication result when it processes the payment. You can then optimize the authentication flow to reduce unnecessary checkout friction.\nOptimize the authentication flow\nAdyen offers the following features to optimize the authentication flow:\n\nDynamic 3D Secure and risk-based authentication: Evaluates transaction risk to determine whether to request a challenge. When you use Protect premium, real-time risk signals, machine learning rules, and your custom risk rules inform this assessment. High-risk transactions can require shopper authentication, while low-risk transactions can qualify for an exemption or frictionless authentication.\n\n Authentication Engine\n: Selects the most appropriate authentication method, such as 3D Secure 2, scheme passkey authentication, or Google Secure Payment Authentication (Google SPA). It considers device capabilities, risk signals, issuer data, real-time performance data, and local regulatory requirements. The Authentication Engine also optimizes the data and the shopper experience for 3D Secure flows to increase issuer acceptance and reduce unnecessary challenges.\n\n Adyen Uplift\n: Analyzes authorization rates and payment performance, then provides targeted recommendations. For example, it can identify missing integration data, recommend experiments, or suggest features that can increase frictionless authentication and ultimately boost conversion.\n\nYou can combine these features to optimize the authentication flow. This helps to reduce shopper friction during checkout, and improves the overall checkout experience by preventing soft declines and improving authentication rates.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nAn online payments integration.\n\n\nLimitations\nIncluding certain parameters in your payment request overrides Adyen's authentication decisions, reducing our ability to optimize the authentication flow. To use the optimized flow, ensure that you do not send the following parameters in your request. authenticationData.attemptAuthentication threeDS2RequestData.threeDSRequestorChallengeInd scaExemption threeDSVersion\n\n\nSetup steps\nTo use the Authentication Engine, make sure that you: Support the redirect flow for 3D Secure 2 authentication:\n Sessions flow\n: 3D Secure 2 support is built-in. You must set the nativeThreeDS to disabled in your POST \/sessions request.\n Advanced flow\n: Implement redirect 3D Secure 2 and make sure you send in the applicable 3D Secure 2 parameters for your integration type in your POST \/payments request.Add the payment methods that you want to accept in your Customer Area.\n\n\n\nHow an optimized authentication flow works\nThe following steps show how an optimized authentication flow works, when you combine Adyen's authentication features:\n\n\nYou make a payment request with the shopper's card details. To use the Authentication Engine, the request must support the redirect flow for 3D Secure 2 authentication.\n\n\n Sessions flow\n: 3D Secure 2 support is built-in. You must set the nativeThreeDS to disabled in your POST \/sessions request.\n\n Advanced flow\n: Implement redirect 3D Secure 2 and make sure you send in the applicable 3D Secure 2 parameters for your integration type in your POST \/payments request.\n\n\n\nAdyen uses Dynamic 3D Secure and risk-based authentication to evaluate the transaction and determine whether it needs a challenge based on issuer requirements. The following table explains the results tied to Adyen's risk evaluations:\n\n\n\nTransaction risk\nResult\n\n\n\n\nLow\nLow risk transactions go through one of the following flows:PSD2 exemption: the transaction is exempt from PSD2 requirements.Frictionless 3D Secure 2: the acquirer, issuer, and card scheme exchange all necessary information in the background through passive authentication using the shopper's device fingerprint.3D Secure 2 data-only: you share the shopper data with the scheme directly, who then handles the authentication.\n\n\nHigh\nHigh risk transactions go through the challenge flow. The shopper must verify their identity by completing a Strong Customer Authentication (SCA) challenge using one of Adyen's authentication methods. The Authentication Engine automatically selects the best method based on factors such as the shopper's browser, the payment method, and other criteria.\n\n\nVery high\nVery high risk transactions are declined entirely.\n\n\n\n\n\nAdyen Uplift analyzes your transactions and provides insights and targeted recommendations to optimize your authentication flow and conversion rates.\n\n\nAuthentication Engine\nWhen Strong Customer Authentication (SCA) or identity verification is required for a transaction, Adyen offers three ways in which the shopper can authenticate. If the authentication is successful, You reduce the chance of fraud, and the liability shifts to the issuer. The Authentication Engine automatically selects the best method based on factors such as the shopper's browser, the payment method, and other eligibility criteria.\n\n\n\nAuthentication method\nDescription\nSupported channels\nShopper experience\n\n\n\n\n\n Google Secure Payment Authentication (Google SPA)\n\nGoogle Secure Payment Authentication (Google SPA) is a method of authentication that uses Google's security features to verify the identity of the shopper.\nChrome \/ Android\nBiometric verification integrated directly into Google Wallet\/Chrome.\n\n\n\n Scheme passkeys\n\nScheme passkeys are a method of authentication that uses the shopper's device to verify their identity.\nWeb \/ Mobile Redirect\nOne-time 3D Secure 2 registration. Subsequent checkouts use device biometrics.\n\n\n\n 3D Secure 2\n\n3D Secure 2 is a method of authentication that uses the shopper's device to verify their identity.\nWeb, iOS, Android\nStandard issuer web view, SMS OTP, or bank app push notification.\n\n\n\nDuring the payment process, the Authentication Engine automatically selects the best method based on factors such as the shopper's browser, the payment method, and other eligibility criteria. After the shopper successfully completes the challenge, the payment is authorized.\nNext steps\n\nrequired3D Secure 2Verification using an SMS or notification on the shopper's device.Google Secure Payment AuthenticationBiometric verification integrated directly into Google Wallet\/Chrome.Scheme passkeysCheckout using registered passkey biometrics.\n","type":"page","locale":"en","boost":18,"hierarchy":{"lvl0":"Home","lvl1":"Online payments","lvl2":"Authentication"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/online-payments","lvl2":"\/online-payments\/authentication"},"levels":3,"category":"Online Payments","category_color":"green","tags":["Authentication"]}}