#kostyantyn_confirmationtoken-error

1 messages · Page 1 of 1 (latest)

fluid thunderBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1291078399451988008

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

native crag
#

async getConfirmationToken() {
const { error, confirmationToken } = await this.stripe.createConfirmationToken({
elements: this.elements,
params: {},
});

if (error) {
  this.onSubmitFail(error);
  return null;
}

return confirmationToken;

}

#

I uploaded both the ConfirmationToken and the PaymentIntentCreateParams. What is wrong with them?
Everything else works OK. Both card payments and some other us_bank_account payments are created fine, no errors.

bold oriole
#

Hi 👋

That is an odd error message. You aren't providing the payment_method_data parameter in that request

native crag
#

Thank you, but why should we provide payment_method_data? We provide a confirmation token with all necessary data from FE configured. This setup is working fine for both cards and us_bank_account. It just generates this error in a few rare cases.
What should be set in the payment_method_data and why?
Why it is working fine for many other payments?

bold oriole
#

Thank you, but why should we provide payment_method_data?
You shouldn't. I wasn't saying you should

#

I was saying the error message didn't make sense because it was referencing a parameter you were not using

native crag
#

Yes, that is true

bold oriole
#

But I'm having a hard time identifying why this error was thrown

#

I'm reaching out to some colleagues to see if we can identify what is going on here

native crag
#

Thank you very much!

bold oriole
#

Can. you provide a couple requests that use the same flow but are successful?

native crag
#

One moment

fluid thunderBOT
native crag
#

It was us_bank_account again and it was successful

radiant wedge
#

kostyantyn_confirmationtoken-error

#

Thanks, having a look

#

@native crag do you have a more recent example of both success and errors or are those rare on your account? Trying to figure out if something changed on our end

native crag
#

No. We only recently started to accept payments from our customers, only a few use it, and most of them pay by cards (no problems), so we have only a few us_bank_account examples.
This failed one was the last one - on 2024-09-27 and after that we have not had any other us_bank_account attempts

radiant wedge
#

okay makes sense, thanks for clarifying.

#

Unfortunately this is strange and I recommend reaching out to our support team at https://support.stripe.com/contact so that they can dig into this further and figure out what's causing this.
I'm going to work with the product team internally to look into this now but our support team can clarify the issue async once they figure out the problem