#josula_api

1 messages · Page 1 of 1 (latest)

nova graniteBOT
#

👋 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/1491458523442184355

📝 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.

gaunt birch
#

hello?

#

I feel like overall the B2B capabilities of Stripe are super limited

#

For example just the fact that I cannot create a company account and then assign customers from the same company to the same Stripe account as sub-customers is pretty annoying

#

Do you have any idea how to do this? The problem is that in our business, because it is B2B e-commerce, the time between creating an invoice and the time between finalizing it can be weeks sometimes. If the customer changes their address in the meantime, the invoice would get a totally wrong address and most likely also other data.

lavish arrow
#

Hello and sorry for the delay! I was juggling a few threads but am taking a look at your question now 🙂

#

Do you care about the Invoice's shipping address? That can be set here: https://docs.stripe.com/api/invoices/update#update_invoice-shipping_details

If we derive this from the customer, we will always run into issues
Can you please clarify what these issues are?

I cannot create a company account and then assign customers from the same company to the same Stripe account as sub-customers
I'm also not sure what you mean by this. Are you trying to link multiple Customer objects together when they're the same underlying customer? And is this within a Stripe account or accross multiple Stripe accounts?

If the customer changes their address in the meantime, the invoice would get a totally wrong address and most likely also other data
How are you getting the customer's updated data when they change it?

gaunt birch
#

its both

nova graniteBOT
gaunt birch
#

shipping and billing

#

How are you getting the customer's updated data when they change it?

via stripe api node sdk. updateCustomer I think

brisk reef
#

fyi i'm taking over this thread! gimme just a minute to catch up

gaunt birch
#

*I'm also not sure what you mean by this. Are you trying to link multiple Customer objects together when they're the same underlying customer? And is this within a Stripe account or accross multiple Stripe accounts?
*

What is the difference between a Stripe account and a Stripe customer? Can an account have multiple customers? Is an account like an organization or a business or how do I have to think about it? I always thought the Stripe account is simply my account as the owner of Stripe.

brisk reef
#

for most intentsd and purposes, an Account is usually just like what you said, someone who is processing payments via Stripe. under our new Accounts V2 model we're moving towards a world where these Accounts can also be used as Customers, but I don't think that's what you're asking about so I won't go into too much detail there. but yes, a Customer is typically the atomic unit around which payments are organized

gaunt birch
#

I think my main problem is that in Stripe every email address is treated as an individual customer. I want to have companies that are in turn attached to customers so that a company has a one-to-n relationship to all its employees, which are our customers. On that company level I want to set addresses and manage everything for all the accounts.

#

For example we have a company A and they have a purchase department of 15 different people. All of them buy daily on our platform. Now I have 15 different customer accounts that I cannot summarize under one main company account.

#

Is there any way to do this?

#

Every other payment provider has this even the small ones. I am very astonished Stripe doesn't have this functionality

brisk reef
#

so you effectively want each of the customers to share the same billing info shared between them? is that your end goal there?

gaunt birch
#

No, first of all my end goal is to have n addresses per company which has n customers. I'm already very confused that in Stripe only one address is available for a customer, especially in the B2B context that doesn't make any sense

#

We have customers that have 30 different branches from which they order from one single purchasing office. How am I supposed to manage all these addresses? I can't always update the address for a customer when they place an order; that is a total mess.

#

The worst is that in B2B pay-on-invoice systems the customer usually receives an invoice only weeks after they have made the payment because the invoice is issued and finalized the moment the goods are shipped. If I create a draft invoice as soon as the customer pays and then finalize it only weeks later when the goods are shipped, the chances are really high that the customer has made a different order in the meantime, changing the customer's address. When I then finalize the invoice, the invoice will have a totally different address than during the original order.

#

Every other small payment provider has thought through these concepts like Mollie or Paddle. They all have some organizations / company concept.

#

For example in Paddle, addresses are their own entity and they are not one-to-one tied to a customer so I could just attach an address ID to an invoice instead of needing to go via the customer

#

So what if my customer has ten different addresses? How would I handle this?

#

I mean if the second suggestion is already metadata, I already know that this is just an afterthought and there is no clear concept behind it. Of course I could build some logic on my end but I would expect you guys to handle this

image.png
brisk reef
#

ok yep, i can confirm that this is a feature other users have asked for. for now the only way to handle this would be to create separate customers per address, or to manage it via metadata (which feels risky and generally not like a great idea because then the address info wouldn't be used automatically in multiple contexts)

gaunt birch
#

Okay that is almost a reason to migrate away to be honest

#

It's just completely unsuitable for B2B

#

Is there a road map or anything I can see both for multiple addresses as well as organizations in the sense of having company accounts with customers?

brisk reef
#

yep, completely valid 😅 for now i can tag your feedback to the existing request to see if we can get some momentum on it but as with all feature requests i can't guarantee a timeline or anything like that

gaunt birch
#

ok

#

No, no need for that

#

Okay I just had another idea. I think I could still work with a single customer account and just use the address as a reference

#

Whenever I finalize an invoice, I have to call the updateCustomer SDK method before to make sure that the customer has the same data as the invoice. Then when I finalize the invoice, I am more or less guaranteed that it takes over the customer data that I just updated the customer with

#

I'm very surprised that this issue hasn't come up much earlier in Stripe. Basically anyone who is working with B2B customers will run into this issue at some point

brisk reef
#

yep, i can't speak to the history but like i mentioned earlier i know at least a few large users have reported this to us already

brisk reef
gaunt birch
#

I know but I know that I cannot wrap Stripe transactions into an actual database transaction. I asked about this before

#

That is another big feature I am missing

#

Once we finalize the invoice, there is no going back

#

Let me know if you have a better idea

brisk reef
#

can you explain more about what you mean by that? i don't think i follow

#

but yeah with the current state you would probably either need to maintain separate customers, or do what you suggested and just design your system in such a way that you aren't asyncronously processing invoices for a given customer at the same time

nova graniteBOT