victor_unexpected | Stripe Developers | Page 1

pine kindleBOT Jul 29, 2025, 9:43 AM

#

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

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

#

brazen dagger Jul 29, 2025, 9:45 AM

#

How are you creating the domain? can you share the requestId ?

ocean kestrel Jul 29, 2025, 9:46 AM

#

We're using the python client. Here is a sample request: req_TVsqLM4J1bjrzF

brazen dagger Jul 29, 2025, 9:52 AM

#

And by chance, are you able to accept Apple/Google Pay from that domain 🤔 ?

pine kindleBOT Jul 29, 2025, 10:01 AM

#

ocean kestrel Jul 29, 2025, 10:02 AM

#

yes, listing the payment domains from that account returns the registered domains (e.g. req_wHMTwxncdjMSob), but they're not visible on the connected account dashboard

brazen dagger Jul 29, 2025, 10:04 AM

#

OK I manage to reproduce but I'm not sure if that's expected or not to have the payment methods domains added by connect Headers, checking further...

#

but if you do a connect payment on that domain, you should get the Wallet buttons (as the domain is listed using the connect header)

ocean kestrel Jul 29, 2025, 10:06 AM

#

Yep, the registration is working as expected — we’re able to accept wallet payments on our domain after registration. However, it’s a bit confusing for users not to see our domain listed in their Stripe account.

brazen dagger Jul 29, 2025, 10:08 AM

#

Yeah make sense, checking that part...

boreal elbow Jul 29, 2025, 10:09 AM

#

👋 taking over for my colleague. Let me catch up.

#

this behavior is expected

#

this is a design choice that we've made, so that Connected Accounts don't (unintentionally) remove the domain.

#

we've got similar feedback in the past, but for the time being I don't think we will change this behavior

ocean kestrel Jul 29, 2025, 10:22 AM

#

I understand, thanks for the clarification! As a suggestion, perhaps showing those domains as read-only in the dashboard could help reduce confusion for users.

boreal elbow Jul 29, 2025, 10:23 AM

#

yes we've went through several options. I'm really not sure why we ended up with the current decision, there must have been another factor.

#victor_unexpected