#kaitlyn-tierney_docs
fallow kayakBOT
👋 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/1283731469738442753
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
minor sparrow
We have a lot of different domains so it might help for me to share them here just for additional context:
There are two brands under the group: Bloom & Wild, and Bloomon. Bloom & Wild brands use our Stripe platform account, while Bloomon use connected accounts. Each of these has a currently hosted apple-developer-merchantid-domain-association file available, but the contents of them appear to be different between the two brands. The staging environments and production environments use the same files.
Bloom & Wild staging
UK: https://www.bloomdev.org
Ireland: https://www.bloomdev.org/?countryId=2
German website in German DE-DE: https://de.bloomdev.org
German website in English EN-DE: https://www.bloomdev.org/?countryId=6
Austrian website in English EN-AT: https://www.bloomdev.org/en-at/
Austrian website in German DE-AT: https://www.bloomdev.org/de-at/
bloomon staging
UK: https://bloomon-uk.bloomdev.org
DE: https://bloomon-de.bloomdev.org
NL: https://bloomon-nl.bloomdev.org
BE: https://bloomon-be.bloomdev.org
DK: https://bloomon-dk.bloomdev.org
minor sparrow
Where did you get the old files from exactly?
I really wish I knew the answer to this but so far it seems it's been lost to the sands of time/organisational attrition/people not documenting their work. I don't know where they came from but the would have been added around 3 years ago when we were first integrating Bloomon with Stripe and configuring those connected accounts, as that's when the brand was acquired by Bloom & Wild group.
As far as I can tell, the file that I can download from the Stripe UI -- both in the doc at https://docs.stripe.com/payments/payment-methods/pmd-registration?dashboard-or-api=api and in the Stripe dashboard UI -- does not match any of the files we currently have hosted, and the contents of this file are the same regardless of which brand's account is selected in the account selector drop-down.
Is this a static file? Should it always be the same, and be the same regardless of which account/brand/environment is being used? Would it possibly be safe to replace the one we have currently hosted with this new one, or is there a risk to doing so that our current Apple Pay implementation could break if we made changes here? We also have iOS and Android apps so will need to make sure not to have unintended consequences for the Apple Pay on that side as well.
snow field
And do the files you're downloading from Dashboard for your Platform and Connected Accounts match right now?
minor sparrow
As far as I can tell, every file I can currently download from dashboard.stripe.com and docs.stripe.com is the same regardless of which account is selected, which is a bit curious to me.
snow field
I guess then you can replace the files and your current integration won't be broken.
minor sparrow
That "I guess" is not giving a lot of confidence 😂
Is the file supposed to be the same regardless of which account is being used? And the same for test and for live?
snow field
There's many factors at play, it's impossible to say until you try this. But I am fairly confident that I most cases you won't run into any issues.
The worst case scenario - Apple Pay will not work for the short period of time, but other PMs should not be affected. But I don't see how it would get to this.
minor sparrow
Can we discuss some of the other factors to so I have a bit of a deeper understanding? I think that just replacing the files will still not be sufficient. Do the Stripe Elements need a different kind of verification to our previous integration? We use Apple Pay currently on all of the domains, but when I navigate to one of the connected account domains, e.g. bloomon.nl, I can see Apple Pay for our current integration but trying to load the new Elements results in an error about the verification and the Apple Pay doesn't show up. Would this be only due to the file mis-match, or do I need to ensure the domain has been registered in a different way?
The weirdest bit is that in my Stripe dashboard, all of these domains are showing as "enabled" and verified. Let me give an example that you can navigate to, to see it in action, one moment...
Here is the live site, with our experiment enabled to run the Stripe Elements: https://www.bloomon.nl?experiment=STRIPE_PAYMENT_ELEMENT&variant=1
(If you omit the query param, it will load the site with the current Stripe integration instead of the Elements)
snow field
What errors do you see exactly?
minor sparrow
Here I can see in the dashboard all of the domains verified except the first one -- I suspect with the first one it would be solved by changing the verification file to use the new one, but I've been too uncertain of how it works to be bold enough to change it from the one we're currently using. But DE is a smaller market for us, so I could update the file there as a test. But de.bloomdev.org will use the Platform account, and the problem we're seeing is predominantly with the bloomon domains using the connected accounts.
I see the error:
[Stripe.js] You have not registered or verified the domain, so the following payment methods are not enabled in the Payment Element:
- apple_pay
Please follow https://stripe.com/docs/payments/payment-methods/pmd-registration to register and verify the domain.
I also see an error on, e.g., https://bloomon-nl.bloomdev.org/?experiment=STRIPE_PAYMENT_ELEMENT&variant=1 related to another payment method we would like to be using. In this I'm also confused because this payment method is showing as active in the dashboard.
[Stripe.js] The following payment method types are not activated:
- ideal
They will be displayed in test mode, but hidden in live mode. Please activate the payment method types in your dashboard (https://dashboard.stripe.com/settings/payment_methods) and ensure your account is enabled for any preview features that you are trying to use.
snow field
@minor sparrow could I ask you to write in to Stripe Support so my engineering team can look at this asynchronously? This is a bit too broad for Discord and my colleagues might miss some context when I will need to step away eventually.
https://support.stripe.com/?contact=true
minor sparrow
Yes, I can do, but I'm a bit worried as we were hoping to launch next week and in the past it's taken a very very long time to get help via Support 😦
snow field
Please write in an say you talked to us on Discord. If you share your account ID, I will try to pull your case directly to our team. Please let me know when you posted the case.
minor sparrow
Thanks, I've opened a chat. The account ID is acct_14h0t4Koz4lNOAHN I believe
I've been connected with Kenneth on chat 🙂
fallow kayakBOT