Clone customers across accounts

With Connect, you can clone your customers' payment information across multiple connected accounts for reuse.

Caution

The content of this section refers to a Legacy feature. We recommend that you refer to the guide for cloning PaymentMethods instead. We don’t guarantee continued support for this feature. If you have processes that rely on it, change them.

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.

With Connect, you can accomplish this by following three steps:

Storing customers, with a payment method, on the platform account.
Creating tokens to clone the payment method when it’s time to charge the customer on behalf of a connected account.
Creating charges using the new tokens.

Storing customers

When not cloning payment methods, you save the Stripe Customer objects on each individual connected Stripe account. When cloning payment methods, you instead save them on the platform Stripe account.

This is an API call but be sure to use your own secret and publishable keys instead of the connect account’s.

Command Line

curl https://api.stripe.com/v1/customers \
  -u "sk_test_4eC39HqLyjWDarjtT1zdp7dc
:" \
  --data-urlencode email="paying.user@example.com" \
  -d source=tok_mastercard

Creating tokens

Caution

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.

When you’re ready to create a charge on a connected account using a customer saved on your platform account, create a new token for that purpose. You’ll need:

The Stripe account ID of the connected account (for example, acct_sV2r3HW6ZJxB2DYC) that you’re creating the charge for
The ID of the customer in your platform account (for example, cus_NNQHbY3138QryJ) being charged
The card or bank account ID for that customer, if you want to charge a specific card or bank account rather than the default

Command Line

curl https://api.stripe.com/v1/tokens \
  -u "sk_test_4eC39HqLyjWDarjtT1zdp7dc
:" \
  -H "Stripe-Account: {{CONNECTED_ACCOUNT_ID}}
" \
  -d customer={{CUSTOMER_ID}}

Creating charges

With the token generated in the previous step, attach this token to a customer on the connected account.

Caution

Charges that are made on the cloned customer aren’t reflected on the original customer. This feature is intended for multiple connected accounts that need to charge the same user.

Caution

If your platform uses the Payment Methods API, you must pass the payment method ID as the payment_method parameter instead of passing the source parameter.

Command Line

curl https://api.stripe.com/v1/customers \
  -u "sk_test_4eC39HqLyjWDarjtT1zdp7dc
:" \
  -H "Stripe-Account: {{CONNECTED_ACCOUNT_ID}}
" \
  -d source={{TOKEN_ID}}

Then, use the customer ID (for example, cus_2yNPJvxboVhf7j) and the payment method ID (for example, card_a03yV2TYEV01qA) returned by the customers.create call to charge the customer.

Command Line

curl https://api.stripe.com/v1/payment_intents \
  -u "sk_test_4eC39HqLyjWDarjtT1zdp7dc
:" \
  -H "Stripe-Account: {{CONNECTED_ACCOUNT_ID}}
" \
  -d amount=999 \
  -d currency=usd \
  -d "payment_method_types[]"=card \
  -d customer={{CUSTOMER_ID}} \
  -d payment_method={{PAYMENT_METHOD_ID}}

Clone customers across accounts

Caution

Storing customers

Creating tokens

Caution

Creating charges

Caution

Caution

See also