This article covers
Merchant has set the auto_capture setting at Chargebee end to true, yet they see a delay in card payment transaction which is the cause for firing 2 emails.
The merchant informed us that they have set the auto_capture setting at Chargebee end to true, yet they see a delay in card payment transaction which is the cause for firing 2 emails.
For Adyen, the flow is:
When Card is added the payment is Initiated -> to the transaction in progress with Invoice in Payment due state-> then the transaction is updated, the invoice is updated & Payment Succeeded.
Reason: This is because, unlike normal payments, Adyen processes payments in an asynchronous manner. Therefore, Chargebee will have to wait for the webhook from Adyen to know the status of the payment.
Adyen via Hosted Pages for better understanding. This is our internal Chargebee document.
There are 3 event_content_id that we can see, as per our email prioritization logic, the emails have been triggered.
At times, we see the “Charge Initiated” emails for merchants who enabled it (it is disabled in this case). The reason for the 2 emails (different notifications ) is explained above.
capture_delay set to immediate - In this case, we do not wait for the Capture webhook, as soon as we receive the Authorisation webhook, we update the transaction status to Success.
Adyen payment processing continues to remain asynchronous, capture_delay reduces the time of payment captured.
In the reported case, as checked from Splunk, we received the webhook from Adyen at 1:13:40.0 PM IST which is 17:43:40.6 AEST:
Related articles and Documentation
Adyen auto_capture settings at CB