#Profesorpump
1 messages · Page 1 of 1 (latest)
However this domain does not appear in the Stripe Dashboard
This is expected, as you suspect, because its for a connected account
Can you share the PMD ID please?
The pmd id is pmd_1OP80ZDcXHrWOYGdtWyAMVJh
Ok, looks active
and where you're working locally, how are you initializing Stripe.js?
are you using the platform PK + stripeAccount option for the connected account?
I'm using stripe and react-stripe. Let me find that part of the code
Yes i'm using loadStripe() from the stripe/stripe-js package and using the platform's PK + the accountId of the Connect account
Can you share that snippet when you find it?
let stripePromise = loadStripe(publishableKey, { stripeAccount: cart?.commerceCart?.stripeAccountId });
setStripe(stripePromise);
Which saves it to a state value and once the state is updated/set, it renders the payment form.
I should say our integration was working at some point. I could have sworn it was still working when we moved to Connect.
And for one of our Connect users, I added the PMD through the UI as I have direct admin access to this particular user. ApplePay began to show up for that user's checkout page once I added it. But for some of my Connect users, I don't have this admin access + it would be time consuming to do across my entire platform so I was looking at the API method
Have you verified stripeAccountId is populated like you expect?
And for one of our Connect users, I added the PMD through the UI as I have direct admin access to this particular user.
You mean via their dashboard?
That won't currently work for a Connect call like you've initialized above
You must add it via the API using the connected account stripe-account header to use that way in a client
That's very strange because I was able to get ApplePay to show up for this one particular user by adding the domain via the UI. And we're using Stripe Connect with Standard Accounts + Direct Charges. And yes I did verify the stripeAccountId is populated, sorry that code snippet does look like it's ambiguous
I'm assuming the UI shows a different set than the API does but I noticed some weirdness throughout the UI like discrepancies between the old and new UI. Not sure if that's related at all
Like I originally created the pmd for my ngrok test site in the UI. Then I realized i should probably test via API so I tried to delete it. Only the old UI has a delete option. I'm pretty sure I deleted the ngrok url but on the new UI it still shows up
They are related, but having the one you shared active should be sufficient
oh hang on, thats for live mode
it looks like the test mode equivalent is not verified
So you're saying this particular pmd that i shared is not verified for test mode? I tried to add the pmd with my live key so I assumed it would verify/set for both live and test. But I am using my test PK for checkout so I guess it would check for the status of the test version
However I toggled test/live and it didn't say it was unverified
Well I guess the UI isn't supposed to show it either way so that's not really relevant
Yea it looks like the live mode verified but test mode did not, so you can try to trigger the verify again for that and see if that fixes the issue
okay
The dashboard only shows the domains for "self" usage for the account, it does not show the separate domain registration for platform usage
That's API-only
Yeah sorry got some wires crossed. I am trying to verify with the php SDK so if I want to validate the test version, should I use my test SK? Right now I'm using the live SK
Yes, platform test SK
Hi that looks like it did the trick. I assumed using the live SK would validate both the live and test domain but I guess for testing, I'll need to do that for both environments. Thanks!