steezy971

Thank you i did it, my email on the ticket is [email protected]

This is the Stripe log error message :

{
“error”: {
“code”: “payment_intent_unexpected_state”,
“doc_url”: “https://stripe.com/docs/error-codes/payment-intent-unexpected-state”,
“message”: “This PaymentIntent’s payment_method could not be updated because it has a status of succeeded. You may only update the payment_method of a PaymentIntent with one of the following statuses: requires_payment_method, requires_confirmation,

• This reply was modified 3 years, 9 months ago by steezy971.

https://ibb.co/p1JWBrL

This is the message i got.

Further info after a discussion with Stripe on this issue.

The first error message above;You cannot confirm this PaymentIntent because it has a status of requires_capture. Only a PaymentIntent with one of the following statuses may be confirmed: requires_confirmation, requires_action.” occurs because
when Stripe accounts are using the two step payment flow, ‘Authorization and Capture’, the PaymentIntent is already confirmed and just needs to be captured.

It would seem then that gateway should allow for users who need to use PaymentIntents but also limit the gem functionality to avoid Confirmation of the payment when this will be done by the Spree admin user later either from within Spree, or on the Stripe dashboard.

The next error, You cannot confirm this PaymentIntent because it has already succeeded after being previously confirmed. is normal Stripe behaviour when payment are automatically captured. So the gem should probably not attempt to confirm PaymentIntents when they are captured automatically.

Relevant Stripe API references:
Separate authorization and capture to create a charge now, but capture funds later.
Capture the funds of an existing uncaptured PaymentIntent when its status is requires_capture.

Tell me if it’s help