#victor_unexpected

1 messages ยท Page 1 of 1 (latest)

naive masonBOT
#

๐Ÿ‘‹ 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/1372181046954823710

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

half marlin
#

๐Ÿ‘‹ happy to help

#

the enums are different

#

in ECE the reason value is one of:
'fail' | 'invalid_shipping_address' | 'invalid_billing_address' | 'invalid_payment_data' | 'address_unserviceable'

#

all of what you're asking about could be under invalid_billing_address or invalid_shipping_address

topaz socket
#

Hi @half marlin , I think it's not, because the outcome is different. These screenshots represent the outcome I get with the paymentRequest and the invalid_payer_email error

#

I cannot archive the same behavior using the Express Checkout Element

#

I can archive something similar in Google Pay using the message, but not in Apple Pay

half marlin
#

I hear what you're saying, but that's how ECE was designed

topaz socket
#

AFAIK, Stripe is encouraging a migration from the Payment Request Button Element to the Express Checkout Element. I believe it would be very beneficial to ensure that all scenarios previously supported by the PRBE are covered, in order to make the transition smoother.

half marlin
#

again I hear you, and I can file a feedback to the js team, but I'm not sure why exactly they chose this route but there must have been a reason IMHO

topaz socket
#

That sounds good. Iโ€™m sure there might be a reason behind the current approach, but it could be worth reconsidering. Iโ€™d appreciate it if you could share this feedback with the team.

Thanks, and have a great day!

half marlin
#

the current approach, but it could be worth reconsidering.
I agree, that's why I'm submitting the feedback

#

would you mind sharing your account ID?

naive masonBOT