3D Secure (3DS) authorization flow in Chargebee
Problem Statement
This article explains the 3D Secure (3DS) authorization flow in Chargebee, including why a trial subscription's authorization is voided at the gateway.
Solution
This article covers
Why do I see voided transactions at the gateway?
The transaction is getting voided for the full amount specified while generating the payment intent.
Use cases
- I have plans with a trial. So, I am not collecting the payment upfront. I see that the transactions are getting VOIDED in the gateway.
- I am passing the complete amount as part of the 3DS verification with payment intent flow via Chargebee JS. This gets refunded back to the source.
Clarification
When you use the payment intent ID to create a trial subscription that has no immediate charge, Chargebee creates an authorization transaction only to verify the payment method.
This is expected behavior. After successful verification, the gateway may void an uncaptured authorization and release the hold. If funds were captured, the gateway may refund the payment instead.
Because you generate the Payment Intent, you can reduce the amount while generating the Payment Intent for the customer.