#jan123459371

1 messages · Page 1 of 1 (latest)

viscid jayBOT
#

Hello! We'll be with you shortly. 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.

warm belfry
#

Is this for a direct or destination charge? You say 'same customer, different address data'? Does that mean they're different cus_xxx objects?

#

Any examples would help

half whale
#

destination charge.

customer has ID cus_123 with address data already in stripe:
Max Man
Street 1
12345 City

connect account 1: wants to issue invoice for cus_123 with billing adress:
Max Man
Street 2
54321 City2

connect account 2: wants to issue invoice for cus_123 with billing adress:
Max Man
Street 4
6789 City3

warm belfry
#

Well the Customer objects would exist on the platform account for a destination charge so you can re-use the same cus_xxx ID with different billing addresses

half whale
#

My question is that it is the same customer object

#

I have two accounts which request an invoice for a customer at the same time with different addresses

#

example:

account 1:
update(cus_123, [new address]);

account 2:
update(cus_123, [new address 2]);

account 1:

#

createInvoice for cus_123 > would use address 2 not address 1

#

how can i use different billing addresses for a customer?

warm belfry
#

You can't as I just explained. They'd need to be separate cus_xxx objects to have different billing addresses

half whale
#

there is no way to specify a billing address for a customer when creating an invoice?

warm belfry
#

No, you just pass customer param and it's pulled from there

half whale
#

that is not pragmatic and would lead to lots of redundant data

warm belfry
#

Maybe. But currently a Customer can only have a single address. If you need to represent the same person/customer in Stripe with a different address then you'll require unique objects

half whale
#

how many objects can be stored in my stripe platform account?

warm belfry
#

No limits

half whale
#

any other suggestion?
It is not user friendly for the customers since they have no aggregated data in stripe

#

like getting all open invoices etc

#

the customer can change the billing details in the "user portal" in stripe. But that would be not possible with redundant accounts

warm belfry
#

No other workarounds I'm afraid

half whale
#

but it is not usable then 😄

#

would you please consult someone else?

warm belfry
#

They'll tell you the same answer I'm afraid

half whale
#

your kidding.

So until an invoice is not finalized every update on a customers object will update the invoice.

#

there would not be any need to store payments for a customer if any billing address needs a different customer object

warm belfry
#

Yes, that's exactly how it works. As I explained, if you want to represent the same individual with multiple addresses then they each need a unique Customer object

half whale
#

that does not meet realistic use cases

#

where would be a channel to submit that feedback?

warm belfry
#

I don't necessarily disagree, but that's how it works today. You can share your feedback via support

past dewBOT
#

:question: Have a non-technical question, account issue, or need one-on-one support?
We wish we could help, but this community is focused on developers and technical discussions. Our support team will be able to assist you better than we can: https://support.stripe.com/contact