#josula_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/1492095966289989693
๐ 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.
- josula_api, 17 hours ago, 12 messages
- josula_api, 19 hours ago, 6 messages
- josula_api, 1 day ago, 47 messages
Basically we have one customer that is a purchasing department of a company. There's multiple purchasers; each of them has their own account in Stripe. Now when I issue an invoice, every single one of these customers gets their own IBAN, which does not make any sense from an accounting perspective.
๐ Hi there! Let me take a look
I don't believe there's a way of multiple Customer objects sharing the same IBAN
And this isn't a field that can be updated on a Customer
You would have to either have a single Customer for the account, or ensure orders are routed through that one Customer. Or present the IBAN to the customer manually based on the purchasing department's Customer object
How would I ensure that customers route orders through one iban haha?
is there a way that I can just have one set IBAN for my entire stripe account?
not on a customer level
This is something custom you'd have to do in your integration. e.g. if you know that a certain Customer object is associated with this company, you could apply the purchasing department's Customer object instead when creating the payment
No, I believe it's strictly a per-Customer thing, to make reconciliation easier