#anuraag - cloning payment methods

1 messages · Page 1 of 1 (latest)

regal cosmos
#

Hello! Just starting a thread for you -- I'll review and respond as soon as I can 🙂

#

Just to make sure I understand what you're referring to, you mean the customer attribute of the newly created payment method for the connected account?

kind mica
#

Yes

regal cosmos
#

OK great -- in that case this is expected. The new PM for the connected account is not attached to any customer. You need to decide if you want to attach it to a customer on the connected account or use it as a one-time-use PM without attaching it.

#

The new PM on the connected account is separate form the platform PM and customer

kind mica
#

So what we are trying to achieve is that we create the PM in the mobile and then pass the PM Id to the backend which will then clone the PM for the connected account. How do we attache a customer to the PM while creating the PM in the first place in our mobile app?

regal cosmos
#

Well being mobile or otherwise is irrelevant -- the two PMs exist on two different accounts. If you want to have the PM attached to a customer on the connected account then you need to create a customer there and attach the PM to it (or use an existing customer on the connected account)

kind mica
#

Ok, the scenario is that we will have multiple connected accounts. But we want the customer to be at the platform level, so that the same customer objects can be used for PaymentIntent of different connected accounts. Is that a possibility? If yes, how?

regal cosmos
#

No, that's not possible natively. You need to manage those customer links. You could, for example, create a representation of the same customer on each connected account where they purchase, with a metadata reference to your platform customer if you need to know that.

kind mica
#

Is there a document that explains how to achieve this concept?

#

Even if I create a link between customer at platform level with the customer at the connected account level, how do we manage the saved cards for such customers?

regal cosmos
#

There is no documentation for this, no -- it's an advanced connect use case

#

Manage in what way? It the same as any other customer, except it exists on the connected account

kind mica
#

When a customer decides to save the card details with Stripe, the saved card token is associated with the customer object. Now, suppose we create the customer object at the connected account level. When the customer decides to shop at different connected accounts, they will have to provide their card details for each connected account. How can this be avoided such that card details are saved to customer objects at the platform level?

#

I hope I articulated my question well enough?

regal cosmos
#

You saved it to the platform level initially -- the sharing is how you get those details to the connected account. It's already saved at the platform so I don't understand what details you're referring to at this point.

kind mica
#

Ok, give me a few minutes, I will try to explain differently

#

So here is a scenario. I create two connected accounts, say Biz-1 and Biz-2. Also, create one customer object at the platform level. The customer decides to shop with Biz-1 and selects the option to save his card. Now he decides to shop at Biz-2. He wants to use the card that he saved last time when he shopped with Biz-1. How can this scenario be effected?

regal cosmos
#

You would need to manage that and clone the PM form platform to biz2, if that's how your payment flow works

kind mica
regal cosmos
#

Yes, thats the link you shared when we started this conversation, so I assume you are already doing this

kind mica
#

Yes, I am. I think I am getting it. I will try again and get back to you in case I have further queries