#Austin_Rowe-ach-payment-method

1 messages ยท Page 1 of 1 (latest)

gentle swallow
#

Oh, you're specifically talking about cloning payment methods?

heavy sphinx
#

Yeah, we're using connect and are facilitating transactions between companies. We store payment methods on the platform customer and then need a way for users to use those saved payment methods with connected accounts.

#

I don't want to go the route of cloning the customer to the connected account and having to keep payment methods in sync across multiple cloned customer objects, because that sounds like a nightmare

#

But then as I read it, in section 2 I saw that it states If your platform uses the Sources API, you must create a Source from that customer rather than creating a token. If your platform uses the Payment Methods API, you must create a PaymentMethod from that customer. After following either of these guides, proceed to Creating charges without creating a token.

#

Which then took me to the original doc that I attached which says you can only clone cards

swift flicker
#

Hi there ๐Ÿ‘‹ taking over for toby

I thought that cloning was supported on ACH debit, but I might be mistaken. Let me see if I can test on my end really quick

heavy sphinx
#

Ok, thanks!

#

Really the payment method type is us_bank_account, is that what would be considered ach debit?

swift flicker
#

That's what I'm going to check

#

Okay, so the docs are stale. We're going to see if we can fix them today. ACH Debit and cards are both supported for payment method cloning

heavy sphinx
#

Amazing news! Thanks @swift flicker

swift flicker
#

Sure thing!

heavy sphinx
#

One other question with this

#

When we clone the customer to the connected account along with the payment method in step 3 and later come around for another transaction with that same customer will there be any issue in cloning them again?

#

Or is the clone more of a temporary/record-keeping thing?

swift flicker
#

They're reusable if you attach them to a customer, otherwise the cloning is single-use

#

You should be able to clone multiple times

heavy sphinx
#

I guess it's really the first action that's shown under step 3 that throws me off, because it depicts creating a customer for the connected account and passing in the cloned payment method, then creating the charge with that customer to the connected account.

const customer = await stripe.customers.create( {source: '{{CREATED_TOKEN_ID}}'}, {stripeAccount: '{{CONNECTED_ACCOUNT_ID}}'} );

#

Is it possible to forego the connected account customer creation and just pass in the cloned payment method?

Or would the created customer for the connected account just be temporary?

swift flicker
#

Is it possible to forego the connected account customer creation and just pass in the cloned payment method?
Yes. You would just create the payment method and pass the connected account ID as the stripe-account header without a customer ID (example of the api call I'm talking about here: https://stripe.com/docs/payments/payment-methods/connect#cloning-payment-methods)
Or would the created customer for the connected account just be temporary?
I believe the customer would persist.

heavy sphinx
#

Got it, I'm going to try it out and may be back if I run into any issues with it. Can I ask in here @swift flicker?