Authentication analyticsPublic preview
Learn how 3D Secure affects your payment success rate for card payments.
Public preview
Payments analytics is in public preview. If you’re not part of the public preview, you can still access authentication analytics by navigating to Reporting > Reports > Authentication analytics in the Dashboard.
Use the Authentication page in the Dashboard to see how 3D Secure (3DS) affects your payments success rate. 3DS is an authentication method for card payments and can help protect businesses from liability for fraud. You must first set up 3DS to see your authentication analytics.
To navigate to this page in the Dashboard, click Payments > Analytics > Authentication.
Configure your data set
Use filters to control all the metrics, charts, and tables on this page.
These metrics and charts exclude:
- 3DS requests that occur during card validations
- Payments made with digital wallets such as Apple Pay and Google pay. These digital wallets use device-based authentication methods (such as biometrics) instead of 3DS
- 3DS requests for Data Only authentication. Data Only doesn’t lead to 3DS challenges or liability shift for your customers.
Specify currency
If you don’t apply a currency filter, all payments appear in your default settlement currency, regardless of the actual payment currency. If you apply a currency filter, only payments made using the selected currency appear.
To change the currency, click + More filters > Currency, and select the currency you want from the list.
Specify data as Raw or Deduplicated
You can also view your data as Raw or Deduplicated:
- Raw (default): Raw data includes all payment attempts, including repeat attempts to complete a payment. When Stripe calculates the raw rate, we include all attempts except invalid API requests.
- Deduplicated: Deduplicated data only includes the final outcome of payment attempts that belong to the same payment. For example, Stripe considers a single customer repeatedly trying and failing a payment as a single attempt.
Specify Connect
Connect platforms see direct charge activity aggregated across all of their connected accounts. Data from Standard accounts is only visible to platforms if you enable Platform controls.
To include connected accounts data, click Include connected accounts. To exclude, click Don’t include connected accounts.
Download authentication data
To download these analytics, at the top of each chart click Download .
The CSV file you download matches any filters you selected and displays your analytics in your settlement currency by default. To change the currency, click Currency, and select the currency you want from the list.
Key metrics
These metrics include all payments where 3D Secure was requested, covering both successful and unsuccessful authentication attempts.
| Metric | Definition |
|---|---|
| Authentication rate | Percentage of payments where 3DS was attempted, out of all payments. |
| Authentication success rate | Percentage of payments where 3DS was successfully completed out of all 3DS attempts. |
| Challenge rate | Percentage of payments where the customer receives a challenge out of all 3DS attempts. |
| Challenge success rate | Percentage of payments where a 3DS challenge was successfully completed out of all the payments that require and receive a challenge from 3DS. |
Calculate authentication rates
The following example explains how Stripe calculates authentication success rates:
| Metric | Value |
|---|---|
| Total payments requests to Stripe | 100,000 |
| Total payments without 3DS | 60,000 |
| Total payments with 3DS requests | 40,000 |
| Total 3Ds requests with challenge flow | 20,000 |
| Total 3DS requests successful with challenge flow | 16,000 |
| Authentication rate | 40% = (40,000 / 100,000) |
| Authentication success rate | 87.5% = (35,000 / 40,000) |
| Challenge rate | 50% = (20,000 / 40,000) |
| Challenge success rate | 80% = (16,000 / 20,000) |
3D Secure authentication outcomes
Use this chart to see all the outcomes for payments authentication through 3D Secure. You can toggle this chart by 3DS requests, share of 3DS requests, and 3DS request volume.
| Successful 3DS frictionless flow | This outcome represents payments that successfully completed 3DS without any additional cardholder input needed, including payments that were successfully exempted through 3DS. |
| Successful 3DS challenge flow | This outcome includes payments that successfully authenticated using 3DS where the customer provided additional input to verify their identity to the card issuer. |
| Failed 3DS challenge | This outcome represents payments where the customer abandoned the authentication flow or the payment was rejected by the customer’s bank. |
| 3DS unavailable | This outcome represents situations where the bank doesn’t support 3DS or the issuing bank returns an error. |
| 3DS not actioned | This outcome refers to instances where the customer didn’t enter the 3DS flow, or there was an issue with your integration and it didn’t action the attempt. To troubleshoot, review your 3DS integration. |
3D Secure authentication request reasons
Use this chart to see what initiated 3D Secure for your payments to evaluate if you want to make adjustments to the frequency of when 3DS is requested.
| API request | Payments where you requested 3DS through your Stripe integration. 3DS can be triggered manually using the API. Stripe’s SCA rules run automatically, regardless of whether or not you manually request 3DS. You can include additional 3DS prompts but they aren’t required for SCA. |
| Radar request | Payments that match a Radar rule to request 3DS. The default method to trigger 3DS is using Radar to dynamically request 3DS based on risk level and other requirements. |
| Stripe request | Stripe requests 3DS because of regulations or optimizations using our Authentication engine. Stripe automatically attempts to maximize payments success while minimizing fraud. |
| Bank request | Payments where the customer’s bank requests 3DS with the soft decline code authentication_. |
Strong Customer Authentication
Use this chart to see which of your payments were considered in scope of Strong Customer Authentication (SCA) rules. SCA requires businesses in Europe and the UK to use 3DS to help prevent fraud for customer-initiated online payments.
Stripe might request exemptions on your behalf for qualifying in scope payments to minimize friction for your users and to increase your payments success rate. Stripe won’t attempt to request exemptions in cases where you explicitly request 3DS using the API. Exempted payments don’t benefit from liability shift.
- This chart is only visible if your business is based in Europe.
- This chart includes payments within SCA scope.
- This chart includes payments considered as SCA exemptions. SCA exemptions are considered in scope of SCA rules.
- This chart excludes payments outside of SCA scope, such merchant-initiated payments.
- This chart excludes payments from digital wallets like Apple Pay and Google Pay because they don’t use 3DS.