#ghostchups_unexpected

1 messages · Page 1 of 1 (latest)

pale valleyBOT
#

👋 Welcome to your new thread!

⏱️ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime!

🔗 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/1212514110420553811

📝 Have more to share? You can add more detail below, including code, screenshots, videos, etc.

⏲️ 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. Thank you for your patience!

foggy mountainBOT
real mist
uneven turtle
#

Hello

real mist
#

hi

uneven turtle
#

Interesting

#

So to be clear, mail@interia.pl is a valid email

#

But you are getting a suggestion otherwise

#

Just to be explicit here

real mist
#

correct

#

this is a valid domain

uneven turtle
#

Gotcha, I can file a ticket for that internally

#

Thanks for reporting

real mist
#

no problem, I have another report. Should i make a new thread?

uneven turtle
#

Nope you can use this one

real mist
#

I am relaying from a Polish client so I'll jsut copy paste here and explain if that is ok

#

the list of banks in P24 we have one position that's spelled weirdly (screenshot 2). It should say "Płać z iPKO (PKO BP)". I understand it takes the list from Stripe, but maybe it's something that can be fixed?

#

P24 is a payment option

#

that we have enabled for the client

#

Przelewy24 is the full name sorry

uneven turtle
#

Yep gotcha

#

I'll report that as well.

real mist
#

awesome thank you

uneven turtle
#

Thank you

foggy mountainBOT
real mist
#

just on the first one, is there any option I can pass through to the Payment element that will turn off the email domain suggestions?

#

E.g. my code is:

<PaymentElement
onChange={handleElementChange}
options={{
defaultValues: {
billingDetails: {
email: email ?? '',
},
},
readOnly: isConfirmingPayment,
layout: {
type: 'tabs',
defaultCollapsed: false,
radios: false,
spacedAccordionItems: false,
},
}}
/>

uneven turtle
#

No, that's not possible right now.

real mist
#

ok no worries

uneven turtle
#

Is that company a customer of yours?

real mist
#

yes

uneven turtle
#

So you anticipate collecting payments from folks with an interia.pl email specifically

real mist
#

oh sorry

uneven turtle
#

Like Link is based on the customer's email.

real mist
#

they were testing the Stripe integration and tried an email address

uneven turtle
#

So it shouldn't really be a huge issue unless you expect the majority of your customers to have addresses from that domain.

#

But we will get it fixed up, regardless.

real mist
#

yeah that's fair. I did ask if they tried other domains and they said yes and saw a similar message, but they did not advise me which ones. gmail.com worked.

They were also not using a VPN or anything

#

I can also reproduce it on my end

#

from a New Zealand IP

#

I assumed Stripe has a list of email providers to use as suggestions to try help people get their emails right.

uneven turtle
#

Yeah I believe so, I'm not positive about how that feature was built. I filed a ticket for our Eng team to look into it further though to at least get this case fixed and it improved here.

real mist
#

Also if it helps this is a react app using:

"@stripe/react-stripe-js": "^2.3.1",
"@stripe/stripe-js": "^2.1.7",

#

I haven't tried upgrading dependencies, so I can try that incase it's already been fixed.

It's not a deal breaker, I just promised I'd raise a ticket with Stripe

#

appreciate the help @uneven turtle

uneven turtle
#

Yeah you aren't far behind current -- pretty positive the version isn't going to matter here.