#Amer Bearat

1 messages · Page 1 of 1 (latest)

grave basinBOT
pulsar lichen
#

Hi there

primal crane
#

can you take look at the pdf the recommended solution by stripe does not require PaymentMethod cloning.

pulsar lichen
#

No I can't read through a multi page document, sorry.

#

If you have specific questions I'm happy to answer them

#

Otherwise you will need to work with your Stripe contact on this.

primal crane
#

Stripe gives us 2 solution approaches:

  1. Recommendation: Single, centralized vault with just-in-time PaymentMethod sharing
  2. Alternative: Each line of business has its own persistent vault
pulsar lichen
#

I don't know what a "centralized vault" is, that isn't really a term we use. But that sounds like PaymentMethod cloning like I linked above — you store the PaymentMethods in your platform account and then clone them to your Connected Accounts when you need to charge them.

primal crane
#

in the document PaymentMethod cloning goes to solution 2

pulsar lichen
#

Then I don't really understand what solution 1 is referring to.

#

You would have to use Destination Charges or Separate Charges & Transfers to not clone.

#

And we don't recommend those flows for Standard Connect

primal crane
#

hmm, i guess i will need to go back to the Stripe Sales engineer to clarify both methods to us.

pulsar lichen
#

That seems like the best bet here. We are happy to help with any specific questions you have and to help troubleshoot, but we can't really help walk through all the pieces of scoping your integration here as we help many folks at once as they come to this server.

primal crane
#

thank you