#gewibu_docs
severe wingBOT
👋 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/1219651832071065631
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
random kernel
Hi 👋 no, that method creates a Payment Method (not a Token). The ID of that created Payment Method can be attached to a Customer on the Connected Account or used to process a payment.
honest eagle
So if I was having the business with the Connected Account charge this Customer on their own server, I could send them the Payment Method ID I created? Is that right? Or would I send them the customer ID?
random kernel
How many times are you planning to charge that Payment Method?
honest eagle
I can write out a more in depth description of my use case if that might be helpful. We have one business trying to charge a customer a one time amount and another business looking to use the cloned payment method for monthly charges over the next year
random kernel
Okay, so more than once, which means you have to attach the new Payment Method to a Customer on the Connected Account. Are you planning to leave that action up to your Connected Accounts to handle, or are going to do the attachment for them?
honest eagle
In my case we have Business A and Business B, A is where the checkout experience will be and they will be charging the customer once. B is the business with the connected account that sells a subscription. B needs to exectue the payments on their own servers so I need some kind of token or id to send to them for a given payment method. So would business A be sending B a payment method ID that was created on A's server? And then B is responsible for creating the customer id using that method for further charges?
random kernel
It depends on how you construct your flow, usually for Connect I see the Platform facilitate the future payments. If you're leaving that up to your Connected Accounts to do, then what you need to provide them depends on exactly how much of that flow you want to leave up to them.
Bare minimum, you need to provide them the ID of the created Payment Method. If you also attach the Payment Method to the Customer for them, to help avoid the scenario where a Payment Method is charged before it's attached and is no longer able to be used for additional payments, then you'll want to provide them the ID of the Customer as well.
honest eagle
so for Business B they would get send a payment method id and they would then need to attach it to a customer BEFORE any charges are made so that they have the customer id to store and charge for subsequent payments? Does business A need to send them a customer ID or anything like that, or just the payment method id? Can business A charge the payment method before B can attach it to a Customer or does that not matter in the case of cloning payment methods?
random kernel
so for Business B they would get send a payment method id and they would then need to attach it to a customer BEFORE any charges are made so that they have the customer id to store and charge for subsequent payments?
Yes, if they charge the newly created Payment Method before it's attached to a Customer, it can't be used again. If the new Payment Method on the Connected Account is consumed without being attached, your Platform would need to clone the Payment Method again to create a new Payment Method on the Connected Account for use.
Does business A need to send them a customer ID or anything like that, or just the payment method id?
This is up to you to decide. You don't need to send them a Customer ID, but if you leave it up to the Connected Account to attach the PM to a Customer then they could miss that step and run into the issue I mentioned above.
Can business A charge the payment method before B can attach it to a Customer or does that not matter in the case of cloning payment methods?
If you're referring to the newly created Payment Method on the Connected Account (it's a distinct object from the one on the Platform that you cloned it from) then yes you can charge it before it's attached, and cause the same problem I'm warning about.
honest eagle
I believe I understand how this all will work now- but just to clarify your last point: cloning the payment method means that if Platform A (the one we clone the method from) charges that payment method it WON'T affect the one sent to the connected account?
random kernel
If you charge the Payment Method that is on your Platform account (let's call it PM_A to align with A being the Platform), correct, that will not have any impact on the Payment Method created on the Connected Account (PM_B)
