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

Can I pass raw card information to Chargebee and still be 3DS compliant?

Problem Statement

You want to know whether you can pass raw card details to Chargebee via API and still be 3DS compliant.

Solution

Sending raw card details to Chargebee via API is not recommended for 3DS compliance.

3DS authorizes card payments by collecting user-verifiable information. Gateways play the role of collecting the background information of the customer from the browser using their JavaScript. Once they collect the information, they send it to the issuing bank and authorize the payments.

Apart from communicating the customer's background data to the issuing bank, gateways also seamlessly handle 3DS flows. Therefore, it is recommended that you incorporate the gateway JavaScript and collect the card information from your customers. The gateway would then return a token using which you can create subscriptions in Chargebee.

Related Articles

Was this article helpful?