#ian-goldberg_api
patent rootBOT
đź‘‹ 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/1233477628078456922
đź“ť Have more to share? Add more details, code, screenshots, videos, etc. below.
viscid tendonBOT
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.
- ian_subscriptionschedule-event, 3 days ago, 13 messages
umbral grove
Hi đź‘‹
Do you have an example payment ID I could take a look at?
craggy loom
pi_3P6bukFNVbYFceRM0ESoRT5q
hey btw, thanks for jumping in
and my immediate question is, do we have this level of control over the payment intent? It’s one thing if we’re executing the payment from our code and can “inject” whatever parameters we want. But since we’re using Stripe Subscriptions, things like invoices and payment intents get created automatically. So that’s the thing I’d be curious to learn more about. Can we somehow get payment intents with ACH to use the statement_descriptor_suffix while all other payments don’t?
umbral grove
Still looking. Statement descriptors are a serious nest of confusion
craggy loom
100%
umbral grove
The statement descriptor properties on both the payment intent and accounts are for Card payments specifically. ACH uses different logic.
craggy loom
Roger. Would be good to know if/how to set it for ACH
umbral grove
Also, this is for a Subscription, correct?
craggy loom
yes
umbral grove
Yeah in that case you don't have direct control since you don't actually create the invoice or payment intent. You can set the statement_descriptor on the Invoice while it's still in draft status: https://docs.stripe.com/api/invoices/update#update_invoice-statement_descriptor
Or you can specify the statement descriptor on the Product itself: https://docs.stripe.com/api/products/object#product_object-statement_descriptor
craggy loom
but if we are a platform account, and want to set statement descriptors based on invoices associated with an account based on the on_behalf_of paramater, then we would need to do something like listen to a webhook and update the descriptor while still in draft? does that seem like the only way?
umbral grove
For some types of Connected Accounts you can update the settings.payments.statement_descriptor but our docs state that this applies to card payments.
craggy loom
Yeah, ours is express and its how we handle card payments currently
but we dont support ACH today because we havent been able to set the descriptor for those
Do you agree we should use webhook to update while in draft? If so, which webhook do you think would be most efficient?
umbral grove
I think that would be the most direct approach. I would listen for the invoice.created event and then make an update call to that invoice in response.
craggy loom
thanks -- dunno if you can take feedback for the product but it would be really nice if it would follow the same protocol as card payments
umbral grove
Yes I can raise that as feedback
viscid tendonBOT