New in Chargebee: Explore Reveal and understand your payment performance end-to-end.Try Now
Docschargebee docs
HomeBillingCPQPaymentsRevRecGrowthReveal
Support

Product Updates


  • Release Notes

Payment Methods


  • Payment Methods Overview
  • Cards
  • Direct Debit
  • Bank Based Payments
  • Wallets
  • Vouchers
  • Articles and FAQ

Payment Gateways and Configuration


  • Payment Gateways Overview
  • Chargebee Test Gateway
  • Stripe
  • PayPal Payment Services
  • Chargebee Pay
  • Adyen
  • Authorize.net
  • Bambora (formerly Beanstream)
  • Bank of America
  • BluePay
  • BlueSnap
  • Braintree
  • Checkout.com
  • CyberSource
  • dLocal
  • EBANX
  • Ecentric
  • Elavon
  • E-xact Direct Integration
  • eWay Rapid
  • Global Payments
  • GoCardless
  • J.P. Morgan Mobility Payment Solutions
  • Metrics Global
  • Mollie
  • Moneris
  • Network Merchants Incorporated (NMI)
  • Nuvei
  • Orbital (Chase Paymentech)
  • Pay.com
  • Paymill
  • Paystack
  • Pin Payments
  • QuickBooks Payments
  • Razorpay
  • Sage Pay
  • Solidgate
  • Tempus
  • Twikey
  • Windcave
  • Worldline Online Payments(formerly Ingenico)
  • Worldpay
  • Articles and FAQ

Level 2/3 Data Support


  • Level 2/3 Data Support

Payment Optimization Engine


  • Overview
  • Defaults
  • Advanced Setup
  • Payment Method Display Rules
  • Verification Rules
  • Routing Rules

Dunning


  • Dunning
  • Articles and FAQ

Payment Components


  • Overview
  • Use Cases
  • Troubleshooting

Card Components and Payment Method Helper


  • Card Components
  • 3DS Helper
  • Payment Method Helper

Offline Checkout


  • Offline Checkout
  • Articles and FAQ

Transaction Sync & Invoice Mapping


  • Transaction Sync and Invoice Mapping

Fraud Management


  • Fraud Management

Error Handling


  • Errors with Root Cause and Troubleshooting

Payment Lifecycle Logs


  • Payment Intents
  • Transactions
  • Gateway Activity Logs
  • Gateway Webhook Logs
  • Retries
  • Articles and FAQ

Others


  • Reach (Merchant of Record)
  • Bulk Deletion of Payment Methods
  • Custom Payment Methods
  • Payment Initiator Parameter
  • PSD2 and Strong Customer Authentication
  • RBI e-Mandate
  • RBI Tokenization Regulations
  • Chargeback Management
  • Transaction Descriptors
  • Payment Preferences
  • Visa Trial Rules
  • Mastercard Trial Rules
  • Co-badged Card Compliance
  • Articles and FAQ

Will there be a reduction in fraud after implementing 3DS?

Problem Statement

You want to know whether implementing 3DS will reduce fraud for your business.

Solution

3DS comes with the promise of making online transactions more secure and reducing fraud rates in the EU. 3DS authorizes card payments by collecting user-verifiable information. Its predecessor (3DS 1.0) was not widely adopted due to lack of mobile-friendliness and poor user experience, resulting in low approval rates for transactions.

3DS 2.0 improved upon its predecessor by making authentication more flexible and secure. Once 3DS 2.0 is rolled out, it is estimated that it would reduce fraudulent transactions to 0.05%.

Additional Information

Online fraud is an ever-growing problem and a threat to SaaS and e-commerce businesses worldwide. Here are some statistics from 2016 to help understand the magnitude of the problem:

  1. There were 27 attacks for every 1,000 transactions conducted in 2015 Q4—an 11% increase from 2015 Q3 and a 215% increase from 2015 Q1.
  2. The attack rate more than quadrupled for digital goods and nearly doubled for luxury goods between Q4 of 2015 and Q1 of 2016.
  3. $4.79 out of every $100 of sales were at risk, up from $2.90 (150%) out of $100 from 2015 Q1.

Source: PYMNTS.com

Related Articles

Was this article helpful?