ingridwong

[waxen agate]

I believe the platform only has access to customers that were created by the platform. So in this case, you would have access to customers created by you, but your connected account could create their own customers that you would not have access to.

[ancient spear]

That's very interesting. Is there an attribute on the Customer that denotes whether the Customer was created by the platform or the connected account?

Just to confirm, in the following scenario, will the platform account have full access to the Customer & Payment Method?

Platform creates Customer in the connected account with:

response = Stripe::Customer.create(
{
  description: 'test_customer',
  email: '[e-mail]'
},
{stripe_account: connected_account }
)

customer = response.id

Platform creates Checkout Session in the connected account with:

response = Stripe::Checkout::Session.create(
{
  success_url: 'https://example.com',
  cancel_url: 'https://example.com',
  mode: 'setup',
  customer: customer,
  payment_method_types: ['card', 'us_bank_account']
},
{ stripe_account: connected_account }
)

url = response.url

Will that PaymentMethod created as a result of completing the Checkout Session be accessible by the Platform?

[waxen agate]

Yes, you would be able to charge that Payment Method

[ancient spear]

Will I be able to update/destroy the Payment Method?

[waxen agate]

You can delete the card at anytime:https://stripe.com/docs/api/cards/delete

[ancient spear]

Even if that card/customer exist in the connected account?

so basically, the platform account has full permission on any objects in a connected account, as long as the platform created it?

[waxen agate]

You can also detach the payment method if it's not a card: https://stripe.com/docs/api/payment_methods/detach which will make it unusable

so basically, the platform account has full permission on any objects in a connected account, as long as the platform created it?
Correct

[ancient spear]

Perfect, thank you so much for all your help