#el-feloe_code

1 messages Ā· Page 1 of 1 (latest)

low grailBOT
#

šŸ‘‹ 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/1339723481658425504

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

shell verge
#

Hello! No, you make this request on your platform account, not on the connected account itself. You're already passing in the connected account ID as a parameter, you don't need to also set the Stripe-Account header with the stripeAccount parameter.

vital forum
#

Ok. I had confused myself. Besides the examples listed here, are there other examples where that header is required to be set?

shell verge
#

I'm not sure I understand. The examples on that page are just that; examples. There are many potential situations where you want to make an API request on a connected account instead of your platform account.

#

Can you ask a more specific question, or provide more context?

vital forum
# 
There are many potential situations where you want to make an API request on a connected account instead of your platform account```
I'm asking what other situations would require me to set the Stripe-Account header apart from the situations presented in that link. For instance when creating paymentMethodDomains does that require the Stripe-Account header or should those be created at the platform level?
```ts
const res = await Stripe.paymentMethodDomains.create({
        domainName,
      })
shell verge
#

That depends on if you're creating direct or destination charges.

#

If you're using direct charges you need to add Payment Method Domains to your connected accounts. If you're using destination charges you only need Payment Method Domains on your platform account.

vital forum
#

I am using direct charges

shell verge
#

Okay, so then you would use the Stripe-Account header to create Payment Method Domains on your connected accounts to make those direct charges with payment methods that require the Domains work.

vital forum
#

Oh alright. I might've been doing it incorrectly then. I was creating the Payment Method Domains under our platform account

await Stripe.paymentMethodDomains.create({
        domainName,
      })

should actually be

await Stripe.paymentMethodDomains.create({
        domainName,
      },
{
  stripeAccount: getStripeAccountId()
}
)

right?

shell verge
vital forum
#

Is it possible for me as the platform to view the Connected Account's Payment Method Domains? Similar to this platform view

shell verge
#

I think you can view them by logging in to your Dashboard as your platform account, then go to the connected accounts section, click on one of the connected accounts, press the ā€¢ā€¢ā€¢ button in the top right, view the Dashboard as that account, and then navigate to the domains.

vital forum
#

I'm having a hard time finding the domains link šŸ˜…

#

I'm able to view the dashboard as the account but do not see domains link

shell verge
#

Ah, we may not make them available there (I'm not that familiar with that part of the Dashboard). You can always list them via the API though.