#kafkaesque_code
soft cragBOT
👋 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/1483175792966893638
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
slim surge
Hello! Taking a look 🙂
fervent torrent
(the code bit is just kinda a psuedo code of kinda what I'd like to be able to do, we're not doing anything exotic with setup params today)
And thanks!
Oh, i think I missed adding that w'ere using destination charges
slim surge
Thanks for the extra context! Using on_behalf_of should change the statement descriptor according to: https://support.stripe.com/questions/sending-invoices-on-behalf-of-connected-accounts
Can you please share your account ID?
fervent torrent
Yeah let me get you some ids and screenshots one sec
fervent torrent
Okay, so here's our account: acct_1Bm6B4FdviIHOKAn
Here's the connected account: acct_1ETHbKLI0cpDKQxa
Here's the setup intent: seti_1TAA7gFdviIHOKAnW35X0EGY
I included a screenshot of what I see in the Stripe Dashboard, which leads me to believe on_behalf_of was correctly set. However, as you can see in the second screenshot, I'm getting Assembly (which is our business name).
It would be really nice if I could configure what microdeposit verification type we used. My UX is already set up to handle the standard 2 microdeposits flow, and I'd have to roll new frontend code to do the descriptor_code flow that this setup intent got configured to be. But if I had no other choice, I'd happily implement that if I could get these statement descriptors working
slim surge
Thanks for your patience! I looked into this and using your connected accounts branding (e.g. for statement descriptors) with destination charges and on_behalf_of is possible but requires approval. You'll need to contact support https://support.stripe.com/contact so they can enable it for you 🙂
Can you please calrify what you mean by your second question?
Is there any way to force "amounts" microdeposits?
fervent torrent
Yeah! So, you see how what I got was one microdeposit, with a code? That's the "descriptor_code" microdeposit type. There's a different microdeposit type that is the "amounts" type. In that flow, instead of getting a code in the description, you enter two microdeposit amounts. I'm migrating from an older implementation that is pre-setup intents. So I have this existing UX that's just for microdeposits. I'd like to be able to configure my setup intent to JUST do the amounts flow, so I don't have to implement a new UX for the descriptor_code flow. Is that possible? Added a picture of the data strucutre I see on stripe that shows descriptor_code and what our UX looks like
slim surge
Sorry for the delay! I was juggling a few threads and I'm not very familiar with microdeposit_type but am looking into it now 🙏
soft cragBOT
elfin leaf
Hi there 👋 jumping in as my teammate needs to step away soon. Offhand I don't think the type of microdeposit flow is configurable, but am trying to double check that.
Yeah, sorry, I'm not seeing anything documented for it in the places I'd expect, which means it isn't something that is generally available. It may be worth checking with our support team about this as well 😉