I am using the Bubble’ Stripe plugin to register users as sellers on my platform.
Stripe Connect is correctly configured in my Stripe Dashboard (test), and the URI as been set to a page where the registered users are then redirected too (this page is a kind of routing page : can I do that or should I wait few seconds in order for Bubble to correctly manage the poststripeauth stuff ?)
During my tests with test users (some of them create a stripe account during the workflow, some others have alreeady a stripe account), I don’t get any error and users are correctly redirected to my platform, the poststripeauth URI first then the destination page.
BUT, the “Current user’s Stripe seller account’ Id” is ALWAYS empty, so I can’t check if the registration worked… But in my (test) Stripe Dashboard, I have no connected account, so I guess either I miss something, either that does not work.
I’m using the Bubble’ Stripe plugin V3 (should I use V2, didn’t tested yet…)
Many help for any help or guidance you could bring to me !
Cheers
Any luck resolving this? I’m having the same issue. The process looks like it’s working great, and then after stripe the /poststripeauth page just says “Please Wait” and nothing happens.
I had to use the @ZeroqodeSupport Stripe Marketplace plugin, which is a paid plugin but of high quality and excellent results. Great ROI for Stripe use cases implementation.
I only had to implement the Account token creation using the API connector, but the Stripe documentation is one of the best of the IT world, so it’s not a problem.
It appears to work. Reading the documentation you would think that replacing bubble.io with your domain would be the correct step in adding the URI. It is not. Add the URI of https://bubble.io/poststripauth and bubble will do the rest and return your user to the page they started on. Good luck To test it, put this in the URI https: //bubble.io/version-test/poststripeauth (note: remove any spaces in my url) if you try posting in the forum with no spaces it looks like this Stripe Authentication
Something changed. I kept getting the same error and had to rework the call. If I remember correctly it was something weird, like you don’t need to include version-test. I lost my mind about a month ago but got it working again. — edit: I think I remember having to check and alter the redirect URI in stripe… I knew I should have written that down.
Then there has to be a bug. I was running into the same problem, reset the uri and it worked. I had someone sign up as a seller the other day and the following workflow didn’t run. So I may be having the same issue again. I’ll have to test it. That stinks
Rather than wait for Bubble I run a workflow on page load that checks for poststripeauth in the URL and then grabs the code from the URL … and does the token exchange you posted above.
This then gets me the Stripe Key which I store. Not great security, but can’t have two different ways of working across Live and Dev.
