Glossary公開プレビュー
Understand the terminology used in payments analytics.
Use this glossary to understand the common terms referenced in the Payments analytics page in the Stripe Dashboard.
公開プレビュー
Payments analytics is in public preview. If you want access to the public preview, join the waitlist.
Acceptance analytics
The following are Acceptance analytics terms:
| Term | Definition |
|---|---|
| Adaptive acceptance | A Stripe payment optimization feature that uses machine-learning to selectively optimize transactions in real-time. Shows the increase in payment success rate and payment volume from payments that Adaptive Acceptance successfully retried after a decline. |
| Authorized payments | Total number of card payments approved by card issuers. |
| Authorization rate | Percentage of card payments approved by card issuers, out of all attempted card payments. Excludes blocked payments and payments that didn’t complete 3D Secure authentication. |
| Authorized volume | Total amount of approved card payments. Defaults to your settlement currency. |
| Blocked by Stripe | Indicates that Stripe blocked the payment due to risk factors, such as card testing. |
| Blocked payments | Total number of card payments blocked by Stripe or Radar. Payments might be blocked for several reasons, such as risk of fraud or configured Radar rules. |
| Blocked payment rate | Percentage of blocked card payments, out of all attempted payments. |
| Blocked payment volume | Total amount of blocked card payments. Defaults to your settlement currency. |
| Card account updater | Card account updater automatically maintains up-to-date card information for your customers. Uplift shown is from successful payments that had updates to cards using the card account updater within 180 days of the payment date. |
| Failed payments | Total number of unsuccessful card payments due to reasons such as insufficient funds, expired cards, fraud prevention, and more. |
| Failed payment rate | Percentage of unsuccessful card payments, out of all attempted card payments. |
| Failed payment volume | Total amount of unsuccessful card payments. Defaults to your settlement currency. |
| High risk - Radar | Card payment blocked by Radar due to a high risk score. |
| Network tokens | A non-sensitive, 16-digit numeric substitute for a card number, also known as a primary account number (PAN), that ensures only the most current card information is used for processing payments. Uplift shown is from successful payments with network tokens that had updates to underlying card information within 180 days of the payment date. |
| Payments | Total number of all card payments, including successful and unsuccessful payments. |
| Payment success rate | Percentage of card payments approved by card issuers, out of all attempted card payments. Unlike authorization rate, this includes blocked payments and payments that didn’t complete 3D Secure authentication. |
| Payment success rate increase | Uplift in payment success rate within a specific period of time. |
| Payment volume | Total amount of all successful card payments. Defaults to your settlement currency. |
| Post-authorization rule match - Radar | Payment blocked that Radar blocked because of a rule match after authorization. For example, a rule that blocks payments that fail CVC or postal code verification. |
| Revenue increase | Uplift in payment volume over the selected time period. Revenue volume is the total amount of revenue defaulted to your settlement currency. |
| Rule match - Radar | Payment that Radar blocked because of a rule match before authorization. |
Authentication analytics
The following are Authentication analytics terms:
| Term | Definition |
|---|---|
| 3D Secure challenge | A security step that requires the cardholder to verify their identity to ensure the legitimacy of online transactions. |
| 3DS failures | Total number of payments that failed 3D Secure. |
| 3DS failure rate | Percentage of all payments where 3D Secure failed, out of all payments where 3DS was requested. |
| 3DS failure volume | Total amount of payments that failed 3D Secure. |
| 3DS not actioned | Payments where the customer didn’t enter the 3D Secure flow, or there was a technical issue. |
| 3DS requests | Total number of payments where 3D Secure was requested. Excludes requests related to card validation. |
| 3DS requested by API | Payments where you requested 3D Secure authentication through the API. Learn more about manual requests in the API. |
| 3DS requested by Card issuer | Payments where the customer’s bank requested 3D Secure. |
| 3DS requested by Radar | Payments that matched a Radar rule to request 3D Secure authentication. View rules. |
| 3DS requested by Stripe | Payments where Stripe requested 3D Secure authentication to comply with regulations. |
| 3DS unavailable | Payments where the card issuer didn’t support 3D Secure or returned an error. |
| All other exemptions | All other reasons that in-scope payments were exempt from Strong Customer Authentication. |
| Authentication rate | Percentage of card payments where 3D Secure authentication was attempted, out of all card payments. |
| Authentication success rate | Percentage of payments where 3D Secure authentication was successful, out of all 3DS requests. |
| Challenge rate | Percentage of card payments where the customer received an authentication challenge, out of all 3D Secure requests. |
| Challenge success rate | Percentage of payments where a challenge was successfully completed, out of all the payments that received a challenge. |
| Failed 3DS challenge | Payments where customer didn’t complete 3D Secure challenge, or the card issuer rejected it. |
| In-scope payments | Total number of card payments that are subject to Strong Customer Authentication. Includes in-scope payments that receive exemptions. Excludes out-of-scope payments such as merchant-initiated transactions (MITs) and mail order/telephone order (MOTO) payments. Also excludes payments that customers make using digital wallets like Apple Pay and Google Pay, because these wallets don’t use 3DS. |
| Low-value exemption | Card payments that successfully received low-value exemptions. Learn more about low-value exemptions. |
| Low-risk exemption | Card payments deemed to have a low likelihood of being fraudulent. For example, on payments that Stripe exempted with Transaction Risk Analysis. |
| Non-exempt | In-scope payments that weren’t exempt from Strong Customer Authentication. |
| SCA exemptions | Total number of in-scope card payments that received an exemption from Strong Customer Authentication. |
| SCA exemption rate | Percentage of card payments exempt from Strong Customer Authentication (SCA) regulations, out of all in-scope payments. |
| Successful 3DS challenge flow | 3D Secure challenge completed successfully. |
| Successful 3DS frictionless flow | 3D Secure authentication completed successfully without a challenge. |