Single payment charges a customer multiple times as "Uncaptured" and "successful"

@mattwire I have update to 6.1.4 & mjwshared 0.4.3

I had a customer registered for an event. In stripe there were 2 payments registered as "Uncaptured" and "successful". and he was charged for both. When I spoke to stripe support, I was informed both payments were authorised and will be paid to us unless we cancel the "Uncaptured" transaction. "Uncaptured" transaction seems to have no link to CiviCRM or contains any customer info other than credit card details.

changed the description

I've had the same issue.

@tapash @jjdelta They won't be charged for the uncaptured payment but it may show on their statement for a short time. An uncaptured charge is created every time the payment form is submitted - but that normally converts into a captured charge if there are no errors. Are you able to provide me with a set of steps to reproduce this scenario where you get one uncaptured charge and one successful charge?

added Waiting confirmation label

@mattwire its happening to pretty much every transaction, regardless of submitted via backend or online contribution/event pages.

@tapash That looks correct. The way Stripe now works with paymentIntents and SCA/PSD2 is that:

1. It pre-authorizes the charge (creating an uncaptured charge) when you submit the register/contribution page.
2. If you have a confirm page you submit that page.
3. Before the "Thankyou" page loads the actually payment is taken. So the uncaptured charge is Updated and then captured.

Which looks like what is happening above?

Ok sounds good. Thanks for the clarification!

@tapash Can you confirm that this is now ok and we can close this issue?

added Waiting feedback label and removed Waiting confirmation label

Should be resolved in 6.2

closed