#salim-bt_api

1 messages · Page 1 of 1 (latest)

fickle elmBOT
#

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

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

ruby osprey
#

i want user to see the reason why the payment failed after this amazon modal closed

#

like Your card has insufficient funds error

native mulch
#

we have this event listener, as i can see, when we use 3434 card, express checkout just fires 'cancel' event (where i see only elementType) and closes popup

image.png
ruby osprey
#

@fickle elm ?

oak cradle
#

hi there, we're currently looking into this

ruby osprey
#

ok thank you, take your time

fickle elmBOT
placid elk
#

👋 Taking over this thread, catching up now

ruby osprey
#

ok

placid elk
#

Thank you for waiting! After checking, I'm afraid cancel event doesn't support returning error reason after choosing the declined test card in Amazon Pay

#

I don't have live mode to test the Amazon Pay

#

In live mode, we likely surface the error message at the confirmPayment() stage after Amazon Pay shares with Stripe on the customer's selected card

native mulch
#

we are using createConfirmationToken, so i need add confirmPayment handling?

image.png image.png
placid elk
#

Are you doing a server or client side confirmation on a Payment Intent / Setup Intent after creating the ConfirmationToken?

#

The decline reason should be at where the confirmation call is in live mode

native mulch
#

at server side

#

"The decline reason should be at where the confirmation call is in live mode" so backend should handle this reason

placid elk
#

Yes. It should be the same on how you handle other wallet payment methods using Express Checkout Element such as Apple Pay and Google Pay

#

You shouldn't need to handle separately for Amazon Pay

native mulch
placid elk
#

In live mode, the authorisation is done at Stripe end where the decline reason will be available. However, it seems like Amazon Pay simulates a failed authorisation at their end, which led to failing to create a confirmation token even before hitting to Stripe

native mulch
#

so we can't test declined case in amazon, can it be fixed somehow?

placid elk
#

Can I suggest you writing to Support https://support.stripe.com/contact, so that they can share the relevant team? However, we can't gaurantee the timeline about when this will be updated / fixed

ruby osprey
#

ok Thanks