#trandn
1 messages · Page 1 of 1 (latest)
The Token belongs to: acct_1LId4kPjAHms0CXf, but the Customer belongs to: acct_1LG2crBtzXV796ZI
interesting, okay thank you
so when I'm creating the customer should I pass the account_id as well?
If you want the Customer to live on the Connect Account and be able to do things with Payment Methods on the Connect Account, then yes
Currently all our customers live on our Platform account from the migration completed with Stripe Support. If I start passing the account_id, will this have any impact?
It depends on what you're wanting to do. If you simply want to allow the Customers to be linked to payments created on the Connect Account, then you might want to look into Cloning (though you may already be doing that): https://stripe.com/docs/connect/cloning-customers-across-accounts#storing-customers
So if I understood this correctly, if a new customer is created. I can create them in the platform account first (returns customerID1) then create a token passing the stripe connect ID and then create another customer with the created token (returns customerID2) then must use customerID2 to create a charge?
Yes, because there must be a Customer object on the Connect Account, you are essentially passing in the Token to recreate the Customer a second time on that Connect Account
and the customerID2 will live in the connected account and I need to use that customer ID going forward for the platform account to make a charge on behalf of the connected account, is that correct?
Exactly!
Thats odd because I currently have customers that exist on the platform account, and when I go to create a card token for an existing customer I'm not cloning the customers and the charge is still able to process. I'm only receiving this error when I create a new customer and try to bind a new card to their account via the platform
Do you have an example request of a Charge that worked this way? There's a lot of nuance to this, so I want to make sure that nothing is being lost in ambiguous verbiage
payment intent:
pi_3MEaokBtzXV796ZI1UM0514E
connect account: acct_1LIcGCPbGFHEBzlH
customer: cus_MyXiiZ9Sbs4jP1
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
The customer in the call belongs to the platform account but the payment amount is reflected in the connect account
via a transfer
Okay, so this is a Destination Charge (see here: https://stripe.com/docs/connect/destination-charges), which is essentially a charge that was created on your Platform account. That Charge creates an immediate corresponding Transfer to the Connect Account.
The previous payment flow where you clone the Customer is used for Direct Charges (see here: https://stripe.com/docs/connect/direct-charges), which is where the Charge is created on the Connect Account
Theres a step in our flow where we create the customer if they dont exist, so this customer is created in the platform account cus_MyacRSseddoOvB and I'm guessing this token is created for the connect account tok_1MEeZyPjAHms0CXfBFIW4HKB and I would like to get the card details to attach to this customer, but it fails.
No such token: 'tok_1MEeZyPjAHms0CXfBFIW4HKB'
When I did pass the account_id to this call self.stripe.Customer.create_source I got the customer doesnt exist issue, but I dont think we want to move the customers to the connect account
https://dashboard.stripe.com/test/logs/req_yD5KtZB4ZV5opg?t=1670961355
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
What are you trying to do, at the end of the day? When working with customers, saved payments methods and payments, these objects all need to exist in the same account context. Either all at the platform level or all in the same connected account.
I would like to save them all at the platform level and when a credit card is entered from the connected accounts website, bind it to the platform account customer
entered from the connected accounts website
can you elaborate on that?
We support "cloning" payment methods saved on your platform to a connected account, but not the other way around
See docs: https://stripe.com/docs/payments/payment-methods/connect#cloning-payment-methods