Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stripe confirming 3Ds PaymentIntent (with a failed authorization) gives wrong error #225

Open
ixperiencenl opened this issue Jun 29, 2023 · 1 comment

Comments

@ixperiencenl
Copy link

ixperiencenl commented Jun 29, 2023

I am using version 3.2.0 and trying to implement PaymentIntents in a correct way.

First, I create a new payment, using the authorize function, provided with the following data:
'amount' => $amount, 'currency' => $currency, 'description' => $description, 'paymentMethod' => $paymethod_id, 'returnUrl' => $returnUrl, 'confirmation_method' => 'automatic', 'confirm' => true,
On the front-end I enter a 3DS test key, which always requires authentication (4000002760003184) - I then get redirected to the Stripe page, here I choose 'Fail Authentication' - then I get redirected back to my application, the url provides a paymentIntent id.

Then, I call the following:
confirm([ 'paymentIntentReference' => $paymentIntent, 'returnUrl' => $returnUrl ])->send();
Which results into the following error:
You cannot confirm this PaymentIntent because it's missing a payment method. You can either update the PaymentIntent with a payment method and then confirm it again, or confirm it again directly with a payment method

This error should contain the error that the card was declined. Why is it showing this? I see I am missing the payment method, but how to provide this in this stadium?

When clicking on 'Complete authentication' in the Stripe screen, the payment verifies without any issues

Please help. I am at a loss here.

@nowrap
Copy link

nowrap commented Aug 11, 2023

We are facing the same problem in an aimeos shop system which is using "omnipay/stripe": "^3.2"

// edit
in our case it was a problem on the aimeos side

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants