#arden-malikb_unexpected
1 messages · Page 1 of 1 (latest)
đź‘‹ 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/1319469614417313883
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
The recommended way is using the Platform Publishable Key and a Stripe account header
I want to ensure I fully understand your suggestion. The end-user expects the Payment Element to display the payment methods enabled on their connected Stripe account.
Suppose I use the platform’s publishable key with the Stripe-Account header. Will the Payment Element dynamically render the payment methods based on the connected account’s configuration rather than the platform account’s configuration?
My concern is that the platform account’s settings may override or restrict the payment methods available for the connected account. Could you clarify how this setup ensures the Payment Element reflects only the connected account's payment methods?
So on the Platform Dashboard settings, you will see a page which shows which options any Connected Account of it will “inherit”
On Settings > Connect > Payments
And in the request to create a PI on Platform and Stripe Account header, it will returns a pmc object (payment method configuration) and a parent pmc object (parent payment method configuration) which matches the setting pages onDash board
and it also tell which payment method will be available
I understand now that the Connected Accounts inherit payment method configurations from the platform based on the settings under Settings > Connect > Payments in the dashboard.
I have a couple of follow-up clarifications:
-
When creating a Payment Intent with the Stripe-Account header, how do the pmc (Payment Method Configuration) and parent pmc interact to determine which payment methods are available in the Payment Element? Does the platform's settings always take precedence over the connected account's settings?
-
If a connected account has enabled a specific payment method that is not enabled on the platform, is there a way to override this inheritance to allow that method for the connected account?
- The child PMC inherits from the parent PMC, and then it decide that latest, final payment methods. So you can say the parent PMC "influence" the child PMC
- The Dashboard settings page will tell if Platform want to let the child PMC inherit, or block it
You see the pmc_xxx on top left
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
So first of all I need to verify the platform account settings of the connect account right? what pmc settings with my stripe's account right?
because I enabled all the required payment methods for the testing here you can see the connected account
No this is the settings for your own account, not for connect
This account is connected with my platform account
Ah this is the Connected Account?
Yes
This will apply to all transactions on this account, without any relation with the Platform
You want to look at https://dashboard.stripe.com/test/settings/connect/payment_methods on the Platform first, instead
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Can I share the publishiable key? which I getting when oAuth with the platform or my account?
Nope you should use the Platform Publishable Key, and the Stripe Account header. Using the returned Secret Key and Publishable Key by the connection is a legacy flow and will be deprecated soon
so what is the new flow for the oAUth? It's very confusion or not clearance?
Now all the working expected Just want know about the do i need to enabled the both end same payment methods to get the dynamic payment methods on my checkhout form of stripe just this?
Here is the new flow (for Standard Account): https://docs.stripe.com/connect/standard-accounts
do i need to enabled the both end same payment methods to get the dynamic payment methods on my checkhout form of stripe just this?
Yes, and the most certain way to confirm is checking the PMC object in the Payment Intent
Currently, we are using https://connect.stripe.com/oauth/authorize
to get the authorization code and after the https://connect.stripe.com
we request the access token the response from the https://connect.stripe.com is StripePublishableKey from that we have rendered the form of checkout.
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Hi there, I'm taking over this thread
Let me know if you have any follow-up questions
I messaged last one upon of the thread
This is a long thread, I can assist you more quickly if you let me know the most recent issue you're trying to address.