#hillct_global-payouts
dense muskBOT
👋 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/1445824914161406022
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- hillct_best-practices, 1 day ago, 51 messages
native coral
hello! just want to acknowledge your question - currently working on another thread but i'll be back to you asap
polar sonnet
👍
native coral
ok sorry about the delay, looking into your question now
polar sonnet
I guess I'm concerned that I was able ot call the accountLink generation with missing information, without an error result. Made the failure tough to diagnose. I was calling const accountLink = await StripeService.createRecipientAccountLink(accountId, returnUrl, refreshUrl); which I would epect from today's review of the docs, would definatively fail
The docs I'm reviewing at these https://docs.stripe.com/global-payouts/stripe-hosted-recipient-creation?lang=node
I also updated my CC payment collection code (independant of payouts) to use v2 accounts. I gather a user who both makes payments and collects payouts can be represented by the same v2 account, but I'm somewhat confused about how the account need to be updated, to facilitate an existing v2 account (created for CC payments (incoming) needs to be update to facilitate that user being a payout recipient. Is it just a matter of collecting country, and payout destination type, then updating the accounr with something like
configuration: {
recipient: {
capabilities: {
bank_accounts: {
local: {
requested: true,
},
},
},
}
sorry for the slow response - our team is a little less familiar with the global payouts feature as it's still in preview, so i'm just doing a bit of research real quick
polar sonnet
I can expect there will also be accounts where I need to go the other way, where the account was initially created to encapsulate a payout recipient, but later I need to update it to allow the user to make CC payments incoming
Understandable...
While I'm deluging you with qurstions, how are debit cards handled, with regard to for example a user initially, making payments using a debit card, then later wanting to receive payouts using the same card. I haven't tested this yet in the andbox but I imagine the hosted flow handles this elegantly in some way
native coral
i think i'm still a little unclear on this - can you share an example request ID (which start with req_) of an example that worked as expected and one that was missing necessary data as you say?
the account links API let me call it absent the needed data, without throwing an error
polar sonnet
I haven't been able to get one to work as expected yet. My theory is I simply failed to include the use_case node in the JSON link genretion object
use_case: {
type: 'account_onboarding',
account_onboarding: {
configurations: ['recipient'],
return_url: 'https://example.com/return',
refresh_url: 'https://example.com/reauth',
},
}
aha! so apparently it defaults to use case onboarding, but doesn't actually link the account after the flow completes: req_v2RcsbkMEZIaki11u
In this case acct_1Sa1UnS1vTYQ9lZM does not end up with a properly linked payout destination
even though bank account fca_1Sa1eVS1vTHZWfgbstcL7biK is marked as belonging to that user recipient account
native coral
ok, i've been chatting with my colleagues about this and i think that this would best be handled by our support team since this is pretty deep in the weeds regarding preview functionality. i would recommend getting in touch with them via this link below for now:
https://support.stripe.com/
polar sonnet
will do
native coral
sorry i couldn't be of more help, but i wish you the best of luck 🙂
polar sonnet
I see an FAQ there but no means to generate a support ticket
native coral
the "Contact support" button on the right should bring up a chat window
there's a chat agent that you have to interface with a bit but then you should be able to get past that to a person
dense muskBOT
mellow helm