# Authentication analytics Use the _Authentication_ view in the Dashboard's _Payment lifecycle_ section to track your authentication performance over time and review your authentication analytics. Use the data to: - Monitor and optimize your 3D Secure (3DS) performance. - Review your authentication outcomes. - Compare the effectiveness of frictionless and challenged authentication flows. - Analyze the performance of your targeted exemption strategies to maximize acceptance and minimize customer friction. To access your authentication analytics in the Dashboard: 1. Sign in to the [Dashboard](https://dashboard.checkout.com/). 2. Go to _Payments_ > _Analytics_ > _Payment lifecycle_. 3. Select the _Authentication_ tab. You can use the Analytics Assistant on the authentication analytics page to: - Translate natural language into SQL queries for data filtering. - Ask questions about your authentication performance. - Retrieve data across the entire payment lifecycle. - Generate charts. --- ## Authentication rate Your _Authentication rate_ is calculated using the following formula: `number of successfully authenticated payments / total number of payments submitted for authentication` --- ## Authentication flow The Sankey diagram displays the end-to-end flow of your authentication requests, including their final outcomes. The diagram shows: The _Authenticated Requests Count_ represents the total volume of all transactions in which 3DS is initiated and includes: - _Frictionless Authentication_ - Transactions in which the cardholder authenticates successfully without a challenge. - _Challenged Authentication_ - Transactions in which the cardholder is presented with an authentication challenge. The _Outcomes_ represents the final result of the authentication flow: - _Success_ - The transaction was successfully authenticated. This includes both frictionless and successful challenge authentication flows. - _Issuer Declined_ - The cardholder's bank rejected the transaction during or after the authentication attempt. For example, because of risk factors, the account status, or the cardholder failing the challenge. - _Service Failure_ - A technical error occurred during the authentication process. For example, due to a system timeout or network issue. - _Expired_ - The session timed out because the cardholder failed to complete the challenge within the allowed time limit. --- ## Challenge indicator performance To review the performance of your challenge preferences and exemption strategy, select the _Challenged and frictionless_ tab and find the _Challenge indicators_ section. ### Authentication requests by payment value The _Authentication Requests by Payment Value_ graph displays authentication requests, grouped by the type of exemption you requested and segmented by the payment value. The segmentation is primarily applicable to transactions in the European Economic Area (EEA) and the United Kingdom (UK): | Challenge indicator type | Transaction value range | Exemption strategy | | --- | --- | --- | | Low-value exemption | Transactions below 30 EUR | Requested for transactions under the statutory threshold, to present a frictionless flow.

Cannot be applied if the issuer's cumulative count or value limit is exceeded. | | TRA exemption | Transactions between 30 and 250 EUR | Requested for mid-value transactions deemed low-risk by the Transaction Risk Analysis (TRA) tool used by the acquirer or payment services provider (PSP). | | High-value exemption | Transactions above 250 EUR | Transactions above the highest TRA threshold.

These typically default to a _Challenge Required_ decision by the issuer, unless an out-of-scope reason applies. For example, for merchant-initiated transactions (MITs). | > **Information** > > Low-value and TRA exemptions are directly related to Strong Customer Authentication (SCA) requirements specified by the Revised Payment Services Directive (PSD2). They are primarily applicable for transactions in which the issuer and acquirer are both located within the EEA or UK. > > The authentication flow and liability shift rules for transactions that do not fall within the scope of SCA are governed by standard scheme rules. For example, mail order / telephone order (MOTO) payments. ### Issuer decision by payment value The tabs in the _Issuer decision by payment value_ section enable you to monitor the performance of your specific exemption requests: - _0 EUR_ - Tracks the success rate for 0 EUR transactions, typically used for card-on-file tokenization or account verification. - _0 - 30 EUR_ - Tracks the success rate of challenged and frictionless authentications for transactions under 30 EUR, and shows how often the issuer honors your exemption request. - _30 - 250 EUR_ - Tracks the success rate of transactions in the mid-value range, and shows the efficiency of your risk-based exemption strategy. - _> 250 EUR_ - Tracks the success rate of transactions in which you explicitly requested a challenge. The _Tracking Merchant preference vs. Checkout.com change_ table shows how Checkout.com's optimization engine impacted your challenge indicator: - _Merchant preference_ - The initial `challenge_indicator` you submitted. For example, you requested `No challenge requested` for a low-value exemption. - _Checkout.com change_ - Indicates if the Checkout.com optimization layer modified your request to improve success or ensure compliance. For example, `No challenge requested` was modified to `Modify to challenge` if the issuer's behavior strongly suggests they would decline otherwise. - _Authorization success rate_ - The final rate at which the issuer accepted the payment after authentication. This is a key metric for your authentication strategy. --- ## Key metrics Your authorization analytics data on the Dashboard includes the following key metrics: | Metric | Definition | | --- | --- | | Authentication Success Rate | The percentage of all authentication requests that result in a successful outcome. | | Successful Authentications | The total volume of transactions that were authenticated successfully. | | Authentication Failures | The total volume of transactions where an authentication was attempted but was declined. | > **Information** > > For definitions of other terms used throughout the payment lifecycle, see [Terminology](https://www.checkout.com/docs/business-operations/terminology.md). --- ## Related topics **[Authorization analytics](https://www.checkout.com/docs/business-operations/monitor-payment-performance/authorization-analytics.md)** Track your authorization performance over time and review your authorization analytics. **[Acceptance analytics](https://www.checkout.com/docs/business-operations/monitor-payment-performance/acceptance-analytics.md)** Track your acceptance performance over time and review your acceptance analytics.