Hey @ramzizi,
These issues should already be resolved! Be sure to upgrade to Version 2.0.51 or higher to take advantage of the solution. Plus, weāll be rolling out our new error handling protocol in the coming versions which will help contextualize errors for all users. 
Iām having the same problem, specifically when using PaymentMethod - Attach, and PaymentIntent - Create with external Seller / Account ID.
The plugin works well when the account ID variable is left empty, but returns the same error as above when trying to process the actions on behalf of a connected account.
I sent more detailed information to plugins@withcopilot.com
All the actions still work until version 2.0.40, but Iām hoping the plugin is fixed before version 2.0.40 becomes obsolete.
@copilot Any insight on how to get around the ( TOS IP Address) stripe issue, which requires an IP address? How can I apply the IP address for my app if bubble does not provide?
Hey!
You can explore plugins like Ipiphy and similar to grab IP addresses when onboarding sellers to your application. As of now, Bubble does not offer a native IP address module in their expression builder. 
Thanks, that is the route I ended up doing and that seems to work ok. Thanks for getting back .
Hello @copilot. I am also having the same issue when using a connected seller account. Is there a fix for this in the works? I am unable to use the plugin because of this. Will this be fixed before the version 2.0.4.0 becomes obsolete? Thanks!
I cant get PaymentIntent to work at all for some reason 
Me neither, I ended up re-building the PaymentIntent in the API Connector to make it work. This gives me more flexibility to add any parameter I need.
I only rely on the plugin for the JavaScript snippet that creates the Card Element, and everything else is now custom.
The team at Copilot never responded to any of my emails, so I donāt think that the āConnected Accountsā are part of their focus.
Could you share how you got around this problem?
Like a screen shot or something?
It would really help me out
Thanks for the update @jean.e.losi! They never responded to me either. Would you be willing to share some screenshots of how you set up your API Connector with the card element so that I could get a head start? Thanks!
Besides creating intents with the Stripe.js plugin, what other features are not functioning for connected account, @jean.e.losi ?
you have to use it and pass thru the backend worflows as well . āwhen intent was createdā etc
Hello @copilot
I was wondering if there are any plans to add a ādefault priceā response to the āRetreive a Productā call?
Sometimes a product has more than one price. The āList a productās priceā call makes things complicated at times. Its not always as simple as selecting the :firstitem or the :lastitem and you have to use contraints to narrow it down.
It would be easier to be able to select the specific default price. So just wondering if that is in the roadmap.
Thank you
Hi @copilot and bubble community,
I want to add bank account as payment method for a customer. It is being added to the Stripe main(platform) accountās customers but Iām unable to add bank account as payment method for connected accountās customers. Because, there is no parameter to pass āseller/connected account IDā in āstripe tokenā element or āconvert bank account to stripe tokenā action.
Is it possible or not?
I shall be thankful to you for helping me in this issue.
BUG: Card Element does not work when you have the setting āDo not set cookies on new visitors by defaultā.
When you try to get the payment method ID from the card element with the setting on you receive a āLogin session has changed/expiredā¦please try againā Error and the page crashes.
Also, you cannot add an action to opt new users into cookies on page load because the card element is being rendered before cookie action can run and still crashes. Please fix your plugin. @copilot
Does anyone have the documentation part regarding the PaymentRequest buttons (Apple pay, Link, Google pay etc)?
