Good question! Maybe the best way to go about this is to share what Bubble’s Stripe plugin doesn’t have.
To allow Bubblers to take payments securely, Bubble implemented Stripe’s Checkout modal which many think takes away from the anonymity of your payment processor as well takes away from your user experience. Being able to design your own payment flow with your own inputs is a game-changer for designers, like us.
Managed Accounts fall under the Stripe Connect umbrella, which allow you to set up sellers without ever having them go through Stripe’s signup flow. Standalone Accounts require a redirection to Stripe which isn’t the smoothest way to onboard sellers, especially since gaining trust to acquire financial information is difficult as-is.
If you would like sellers to come back to your site after exiting the Stripe seller signup flow, you could pass sellers directly to your website without having to be redirected from Bubble’s generic endpoint. If your business relies on keeping the ‘built by Bubble’ bit under wraps, this one matters a ton just like the above.
Since you have more control over the creation of your sellers’ accounts, you also get a ton more control over their abilities such as payouts, external accounts, currencies, defaults and others things that you can address in your platform. On top of this, you can securely manipulate their accounts at any time.
The last point worth mentioning here is that this plugin is made by a group that has been working with Bubblers and non-Bubblers alike for a quite a while. Not to toot our own horn too much, but we think we have a pretty good idea of what platform builders and users need, because we work with them full-time. As you can imagine, we use our own products too, so if there’s a shortcoming, you bet we’ll investigate how we can work on or around it.
If you ever have ideas for this plugin or any of our upcoming components, give us a shout via email.
@iamsalar
Ok. Just had the idea to test the Pre-release build and it worked fine.
The problem seems to be with the 1.0.0 Plus version of the release build.
We have Stripe.js Plus running on our website, as a live test of sorts, which seems to be just fine.
Try Version 1.0.1, which features an updated Stripe library reference.
Hey @iamsalar thank you for the plugin and reasonable price! great work.
Regarding credit card token, in the video you mentioned that you don’t suggest storing it in the database because of security reasons, they expire etc. but can I create customer object and attach cc token to it and therefore it would be saved in the Stripe database?
I guess that’s how Bubble is ding it with ‘save customer CC info’ in order to charge customer at any time.
This is an awesome and perfect timing. I will be buying later today.
I noticed in the testing that when a charge ID is saved via result of step x that it adds a space to the end of the ID. Other than that, so far amazing.
@alvis That’s right, you shouldn’t be storing any tokens to your database outside of Customer or Account tokens. The Customer object is the recommended method of keeping a reference to a user/seller which may have all their information stored. We’ll be adding some Stripe management calls later today.
@nomadkelley Since Bubble handles the response parsing, there isn’t much we can do as plugin developers. Regardless, if you’re seeing errors arise as a result of the extra character, take advantage of the :trimmed modifier to remove any and all spaces.
Hi @iamsalar, I watched the video and the plugin looks great. Do you have any further documentation available (related specifically to the core offering of charging cards, not connected accounts)? Also, does the plugin provide support for Subscriptions? Thanks!
We’re in the middle of testing Version 1.1, which features support for customers and subscriptions!
Give us a shout at plugins@cobubble.com with your ideas, concerns, and support requests.