I also have the same issue here. Don’t know where it came from. Everything was fine. I was trying to resolve it but wasn’t very lucky.
Hey everyone!
Just to clarify what’s going on here: Stripe made changes to their API on February 19, 2019 to no longer use the legal_entity key. Labeled as a major change, this means there is a high-possibility that implementations of Stripe API (which includes Stripe.js) may need to be heavily-refactored in order to remain functional. Since the API requests includes in Stripe.js depend on the legal_entity key, it’s understandable why errors like those shared by @austinjarts, @lharrod1 and @nebulonb are possible.
As we’ve been heads-down working on the next implementation of Stripe.js, we do not have the ability to update pre-existing versions (like Version 1.8.10) without reverting our work. Had we had the option to reliably change past versions, we would’ve patched this bug (and others) prompty as we always have. As @neerja mentioned in another thread, we are working with the Bubble team around improving Stripe.js and plugin development as a whole:
In the meantime, there are two options to help those impacted by Stripe’s changes:
Option A: Downgrade API
Stripe parses your API requests based on your Stripe account’s chosen API version, which dictates what’s required or not such as the
legal_entitykey above. If you signed up with Stripe before the February 19, 2019 release and have only recently switched to a newer API version, you could opt to downgrade your API version in your Stripe dashboard. This is the easiest and fastest way to realign with Stripe.js with your Stripe application, just be sure to use Version 1.8.x for best compatibility.Option B: Custom API Calls
As a catch-all if the above isn’t possible for your implementation or status, you can use Bubble’s API Connector plugin to create your own API calls. This requires some technical know-how including an understanding of how APIs work in general (we have a course on this). To get you started, here’s what a Stripe API account creation request may look like in the API Connector.
We understand third-party changes may be inconvenient for plugin users, though not quite as much as they are demanding for plugin developers like us. Get unblocked and keep pushing! 
1 Like
For those who created a Stripe account after February 19th, here are the custom API calls (to be used like any other action):
2 Likes
Thanks for the attached custom API calls, @lharrod1
Would you be able to provide what the API call would be for if I wanted to change a Stripe connect user from automatic payout scheduling to manual? The current option on Stripe.js version 1.8.10 for ‘Stripe.js - Platform - Update a custom seller’s payout schedule’ sends an error.