Closed Stanteq closed 4 years ago
In my own app, I don't work with cards that require multi-step interactions, so I'm just guessing from looking at the Stripe documentation.
It appears that you are handling the error return from the server incorrectly. The Stripe documentation says that for the error authentication_required
"the customer should contact their card issuer for more information, or retry with a different form of payment" and "this means that a customer should retry the payment using 3D Secure authentication".
Since paymentIntents.create
on the server returned an error, I suspect the PaymentIntent did not actually get created, which is why you are getting that error on the client.
Your description makes it sound like you are trying to collect payment later (such as when you ship a physical good). This Stripe page discusses that use case.
@RobertGardner, first thx for the hints and help even if the issue (apparently) is not generated by the plugin.
The only part that I figured out is that paymentIntents.create
get created but under connect account and not under stripe platform. Now I pass also the connect account to authenticate the card but i get another error:
The provided PaymentMethod was previously used with a PaymentIntent without Customer attachment, shared with a connected account without Customer attachment, or was detached from a Customer. It may not be used again. To use a PaymentMethod multiple times, you must attach it to a Customer first.
because I just cloning the paymentMethod of the client which is saved under stripe platform.
As I understand the documentation (though I haven't done this myself), you want to ask the customer to authenticate in the response to confirmSetupIntent
. If the card still needs (or again needs?) authentication when charging the card, you need to create a "recovery flow" where you can ask the customer to re-authenticate. This is described in step 5 of the Setup future payments document. In the "Let your customer try again" section, it gives instructions on what to do if payment failed because it requires authentication. This seems to fit your scenario, based on the error message you are getting.
Hi devs. I have an issue (or maybe a question) about authenticate and charge on the UI.
So, I trying to set up the cards for future payments. I using this test card: 4000002760003184 which should ask every time to authenticate. First time (with
stripe.confirmSetupIntent()
) works fine.After, when I try to charge:
on server:
which return "authentication_required". I send to the client:
error.payment_intent.client_secret
anderror.payment_intent.last_payment_error.payment_method.id
:Error on Android
Error on IOS (here is written: No such payment_intent, very strange, I just created)