#[LBG] India-clone

1 messages · Page 1 of 1 (latest)

tepid hinge
#

Hi! So you have a payment method on your platform account that is not attached to a customer, and you would like to clone it to a connected account?

static zephyr
#

Hi ! I have a platform customer with it's own payment_method attached. I would like to clone it on a connected Account as a one-time use payment method. This mean I need to clone it every time (I prefer to clone each time, because if the card expires, we'll have to update every clones on all Connected Account. Is it a good practice ?). How can I clone as a one-time use ?

tepid hinge
#

When you clone a payment method, it won't be attached to any customer on the connected account. So unless you attach the payment method to a customer, the pyament method will be single use.

static zephyr
#

How do I clone a payment method without attaching it to a Connected Account customer ?

#

{
"error": {
"message": "The payment method you provided is attached to a customer so for security purposes you must provide the customer in the request.",
"type": "invalid_request_error"
}
}

#

From API

tepid hinge
#

That's two different things:

  • When you call the API to clone the payment method, you need to pass the customer ID of the platform account.
  • Then once the payment method is cloned on the connected account, it's not attached to a customer.
static zephyr
#

I don't understand why it creates a Connected-Account-Customer-payment_method for each direct charge

tepid hinge
static zephyr
#

I detached manually the 2 payment_methods created during the direct charge

#

And relaunched the workflow

tepid hinge
#

And after cloning the payment method, what do you do with the payment method on the connected account?

static zephyr
#

req_SgXiwbkMUHyn83

#

I think it is this one

#

We clone the payment method to create and capture a paymentIntent

#

Last week during our tests I am pretty sure we managed to clone a platform customer payment_method and create a direct charge between the customer and the connected account without creating a new payment method on the Connected account customer

#

From the Connected Account customer, we could see the payments, with no payment_method underneath

#

Because it was a single use clone

#

I think I found why

#

When both setup_future_usage and a customer are provided on a PaymentIntent, the payment details are automatically saved to the customer once the payment is confirmed

tepid hinge
#

Sorry for the delay, Discord is quite busy right now.

#

Then yes, it looks like cloning the payment method didn't attach the payment method to the customer. It's when you did the actual payment with setup_future_usage.

static zephyr
#

Ok we managed to do it ! In a nutshell, we clone a Platform-Customer-Payment_method to create a DirectCharge between the Connected Account and the Customer without setting setup_future_usage. This leads to DirectCharges between connect accounts and customers without saving the cloned payment method on the connected account

#

Is this a good pratice ?

tepid hinge
#

You are making Direct Charges on Express account? This is not recommended, and I believe we already explained that to you in a previous Discord thread.

static zephyr
#

We are migrating on Standard Connected Accounts