vitor-paixo_best-practices

[surreal fog]

👋 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/1291012203570532384

📝 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.

• vitor-paixo_best-practices, 23 hours ago, 10 messages

[forest verge]

Which section of the docs are you referring to exactly?

Payment Element should normally handle all errors.

[lethal minnow]

hi

i'm testing the payment elements with differente card types

for instance, using the "3ds required - declined" paymente elements does nothing

Neither does it display any message.

I want a way where all errors are safeguarded to be displayed either by the payment element comp or by an error management component created by us. But so far I haven't fully understood those that are shown in the payment elements vs. those that are not.

can you help me pls?

[forest verge]

In case with 3DS failure confirmPayment() call will return an error.

You can show it or just allow the customer choose a different PaymentMethod/try again.

I am not sure what can I help with exactly. You can just handle the errors as you would normally do in JavaScript

[lethal minnow]

There are different types of errors. Some are handled by payment element, others are not. When I say handled by the payment element, I mean that error messages are displayed in the component that is in the app. There are other errors that are not displayed. And these are the ones I need to deal with.
Maybe I've made myself clearer.

and an example of this is card_error, which can have errors that display messages in the component and others that don't, like 3ds

or if you can show me some documentation where this is state i would appreciate so much. I already tried to find but couldn't.

or maybe this is a code related question

i dont know, e just need some guidelines

[forest verge]

You don't need a list of errors. You just use the returned object from confirmPayment() and check the error property. If an error is present you display it to the customer.

[lethal minnow]

this is an erro that the payment elements make the treatment, so I just let things flow naturally and I don't have to worry about anything.

[forest verge]

I don't understand what you mean by this.

[lethal minnow]

and this is the kind of error where payment element doenst show any error.

[lethal minnow]

which part? I'm just showing you an example of an error that is handled by the component

[forest verge]

Yes, you need to handle this error yourself.

[lethal minnow]

I know, but I want to know the list of those I have to deal with myself to ensure that everyone who is needed gets the right treatment. And I can't find that in the documentation!

[forest verge]

I don't think there's a list, unfortunately. But you can just display the message that's included in the error.