Forum Academy Marketplace Showcase Pricing Features

Stripe/Bubble process to register the payee as a seller at a later time


Need some advice about a Stripe/Bubble process.

I would like to have a workflow where the user is charged after another user is registered as a seller(the payee of the transaction). Today if the payee hasn’t created and connected his account with Stripe when the user is being charged, the transaction fails.

So in other words to pre-authorize the payment until the payee is registered with Stripe:

  1. current user is being charged using saved CC
  2. the payee of the transaction is another payee (B) - this payee is already registered on my website so his email is available and connected to the transaction locally.
  3. this payee (B) can register at a later time as a seller within 7 days
  4. once registered as a seller the initial user (A) has his CC charged to pay the payee (B)
  5. the initial user (A) doesn’t need to confirm again the payment so no action is required once approved the first time.

I would like to give the flexibility of the payee to register as a seller at a later time as Stripe requires quite a few information to be available such as IBAN to register as a seller via their OAuth form.

if the Stripe form could be skipped that would be one way but it doesn’t seem possible,

so Is there any way to achieve this?

Thank you

Hey there @gil06000,

One thing that you can do is charge the current user, and then schedule something from the API Connector to pay out the payee at a time of your choosing, by which the payee should have registered. If they haven’t registered in that time, the money won’t be sent to the payee.

By using the API Connector instead of Bubble’s built-in method of sending money to payees, you can control exactly when the money gets sent.

You can learn how to set up an API call that manually pays out payees in this new video tutorial for Stripe.

1 Like

Thank you for your suggestion.

As per my understanding, Stripe is not letting me charge the current user if the payee has not been connected to the Stripe account.

However, I am considering paying for your video tutorial but my concern is that it could covering basics and won’t teach me the things I don’t know. I would mainly like to:

  1. Be able to “Deferred account activation” as per this link in stripe
  2. so to spin up a standalone account with just a country and email address. (same link from above) instead of filling out the full OAuth form.

Doing this will solve the basic problem because the Payee can just enter this simple information (email and country), connect to Stripe and fill out the rest later.

One more thing, I would like to have the current user pay the charge fee from Stripe and not the payee who will pay in fact the collected fee.

Will your video teach me that?

Thank you


So, the deferred account method can work for you as well. The method I suggested has more to do with controlling when the money gets sent out to your payees.

The video tutorials definitely cover more than basics, but they don’t currently show you how to create a deferred account. (Although the process is pretty simple.)

With my suggestion, similar to Uber/Lyft, you would handle all customer payments on your end. (Meaning that when you charge a customer, instead of making the “payee” another user, it would go straight to your Stripe Account.) After your users have paid, you can use an API call to send the money to the seller if (and only if) they have fully finished setting up their standalone account. If they don’t set it up, the money doesn’t get sent.

I haven’t found anything in Stripe’s documentation yet about having the customer pay the fee, as opposed to the seller. You’d most likely have to compensate for that in Bubble, when you calculate the amount being charged.

1 Like

I am in and registered for the course. :slight_smile:

But have problems to make the API running :frowning:
I get this error message when I try to create a customer for instance:

Any idea?

Yes, another user had the same issue.

It’s because a new version of the API connector plugin was released right after these calls were created.

Clicking the “Querystring” checkbox next to the parameter should fix it.

I’ll be transferring the calls to the new plugin soon.