#svikramjeet-connect

1 messages · Page 1 of 1 (latest)

robust igloo
#

Hi, gimme a few min to read through

wide wren
#

thanks, if you need a short description here is what we are trying to achieve:

  1. Can we create Payments in a Connected account directly
  2. Can we create Customers in a Connected account directly
  3. If we do either of the above, does it also create a Payment/Customer in the Main account
robust igloo
#

1 and 2, yes possible via Stripe Account header (Direct Charge/Standard Account), but that Payments and Customers will lives under the Connected Account

#

3 No, objects a separated in account level

#

In any given time it will have different customer on Platform and on connected account

wide wren
#

how we can create a payment in a connected account directly?

#

@robust igloo

robust igloo
#

It's a direct charge, if you happen to know already. You create a PaymentIntent like normal, but specify the connected account id in the call

#

Keep in mind that choosing a fund flow (Direct Charge vs Destination Charge/Separate Charges and Transfers) means choosing the connected account type (Standard vs Express/Custom)

wide wren
#

if you gone though main requirement as described, can you please suggest a way - as we need to ask card information only once

robust igloo
#

There is a flow that might help

#

To allow you to clone Customer from Platform over Connected Account. Then you basically have they linked.

#

Unfortunately that Doc is not very well written. We are happy to help if you want to go over it

wide wren
#

so this willbe basic step:

  1. user signup on the our website with card details - we will create a customer on main/platform stripe account & then clone the same customer to vendor account
  2. when vendor approve user request -> we can deduct any amount from customer and send it to either platform or bendor or both?
robust igloo
#
  1. is right. 2. not I am not sure I am following. You would create 2 separated transactions against 2 customers object if needed
#

They are still separated objects. They just "linked" and you are ready to collect payment, without asking them to provide card info again

#

For some business models, it’s helpful to reuse your customers’ payment information across connected accounts. For example, a customer who makes a purchase from one of your connected sellers shouldn’t need to re-enter their credit card or bank account details to purchase from another seller.

wide wren
#

can you please confirm if the link you shared has enough information

#
  • can we use standard account for cloning customer?
robust igloo
#

The Doc is correct, but its demonstrate by Token/source which is a legacy approach. You can do the same thing with Payment Intent/Payment Method

#

And yes, you can use Standard Account

wide wren
#

how we can collect the card information?

#

As we are not PCI compliance so i don;t want user data to be posted on our server so was thinking of using token/source approach

robust igloo
#

You can use a regular PaymentElement or even Checkout. which is newer and better than token/source

#

Those components are PCI ready

wide wren
#

can we embed the paymentElement in our html form

#

the idea to keep user on our website rather than sending him to stripe

robust igloo
wide wren
#

but we donot want the user to pay straightaway

#

as explained in first message -> user will enter card details for LATER PAYMENT

robust igloo
wide wren
#

doesn't it take user to external url (created by session)?

#

if we collect card details send them directly to stripe token API and then attach source on our server -> ths process will be PCI compliance + keep the user on our website & we can customise the form as we want

robust igloo
#

Choose the "Custom Payment Flow"

wide wren
#

i will check it

robust igloo
#

Hi, I am stepping down for the day. If you have other questions, feel free to ask in the channel!