#mike-j_api
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/1410167373117521972
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
It's because you're passing on_behalf_of so we look for PMCs on that connected account (acct_1RlWa3R7hhUUIyWS)
Aaah. That's going to complicate things. We have 100's of connected accounts, but I thought we could have a single collection of payment configurations and only override them in occasional scenarios...
Is there some way to achieve that?
Not with on_behalf_of, no: https://docs.stripe.com/connect/dynamic-payment-methods?connect-payment-integration-type=payment&connect-charge-type=separate&connect-dashboard-type=full&on-behalf-of=true
You'd essentially have to create/manage the PMC objects on each connected account and use those IDs accordingly
Doing that manually is going to be painful. I guess I'd have to programatically have the "default" configs created against the new connected accounts during connection?
Well there's always default configs on accounts that we fallback to if the p_m_c param is omitted. But if you want your own platform managed 'default', then yes you'd need to create those via API and persist the pmc_xxx ID internally against that 'account' somewhere