Introducing the Chargebee CLI
chargebee docs

Why do virtual card payments fail with 3D Not Authenticated when CVV is optional?

Problem Statement

Customers pay or add a card on Checkout, Pay Now, or the Self-Serve Portal after you make the CVV field optional, but the payment still fails with 3D Not Authenticated (or the cardholder sees an issuer authentication screen that asks for a card security code they do not have). This often comes up with virtual or corporate cards that do not provide a three-digit or four-digit CVV/CID to the cardholder.

  • Payments fail when Auto collection is Off and the customer uses Pay Now or adds a payment method in the Self-Serve Portal, even though you do not want automatic charging for every subscription.
  • The cardholder believes Chargebee still requires CVV because the authentication screen (for example, an American Express SafeKey page) asks for card verification details after they leave the Chargebee card form.
  • You enabled Auto collection or asked customers to turn on auto-pay, but authentication still fails before the card can be saved or charged.

Solution

Optional CVV on Checkout fields only changes what Chargebee collects on its card form. It does not disable 3D Secure (3DS) when the issuer or gateway requires cardholder authentication. See Configure Fields and Labels for how Checkout CVV settings relate to issuer 3DS screens, and PSD2 and Strong Customer Authentication for how issuer challenge flows work.

When 3D Not Authenticated appears, Chargebee and the gateway typically completed the 3DS handoff, but the cardholder did not finish verification on the issuer or card-network side. That is an authentication failure at the bank or card program, not a Chargebee configuration defect. Auto collection does not bypass 3DS for customer-initiated pay or add-card flows; it only controls whether Chargebee automatically charges invoices when payment is due.

For virtual or corporate cards (including some American Express virtual cards), the issuer challenge may ask for a CID or the last digits from the signature panel. If the cardholder cannot supply what the issuer requests, authentication fails even when CVV is optional on Checkout.

  1. Confirm the failure in Logs or Payment Lifecycle Logs and note the decline reason (3D Not Authenticated or similar) and whether the flow was Pay Now, Checkout, or Self-Serve Portal add payment method.
  2. Ask the cardholder which screen failed. If it is the issuer or card-network page (not the Chargebee card form), the issuer controls that step; optional CVV in Chargebee will not remove it.
  3. Review Settings > Configure Chargebee > Checkout and Self-Serve Portal > Fields > Payments only to confirm how you collect CVV on the Chargebee form; do not expect this alone to change issuer prompts.
  4. Have the cardholder contact their corporate or virtual card administrator to confirm whether a security code exists, whether another authentication method is supported, or whether a physical card that supports 3DS should be used instead.
  5. If card payments cannot complete authentication, offer an alternative payment method your site supports (for example, ACH or direct debit) when available.

Important Notes

  • Gateway Card verification settings (authorize on add) are separate from Checkout CVV field visibility. See Card verification on the Cards page.
  • For gateway capability errors at checkout (for example, Gateway not supported for 3DS), see Payment Components troubleshooting. That is a different failure mode than 3D Not Authenticated after an issuer challenge.
  • If you need help tracing a specific live transaction, contact Chargebee Support with the payment or transaction identifier from your site logs.