Native App + Stripe CheckOut

Hi everyone,

I have a question about how URL redirects from external services (Stripe Checkout) work in Bubble Native Apps.

In my Web app:

  • Stripe redirects to: https://myapp.com/home?success=true

  • Page loads and reads the parameter

  • I execute workflows and show confirmation

  • :white_check_mark: Works perfectly

In my Native App:

  • Stripe redirects to: app-myapp://home?success=true

  • Deep link opens the app

  • :cross_mark: App resumes at last view, does NOT reload

  • :cross_mark: Doesn’t detect parameters

  • :cross_mark: Doesn’t execute workflows

My question:

Do URL redirects with parameters from external services currently work in Bubble Native Apps?

And if they DON’T work:

  • What is the official recommended solution for payment confirmation flows?

  • Is this planned to be supported soon?

  • Should we use webhooks + Custom Events as an alternative?

I’ve seen that basic deep links do work, but I need to know if:

  1. URL parameters are accessible

  2. View reload can be forced

  3. App resume to foreground can be detected

Any guidance is very welcome. I need to know whether I should wait for this to be implemented or find an alternative solution now.

Thanks.

@javila Right now, URL parameters from external redirects aren’t reliably handled in Bubble Native Apps. The deep link can open the app, but the view usually resumes instead of reloading, so parameters aren’t read and workflows don’t fire.

The practical solution is to treat Stripe confirmation as server-side, not redirect-based. Use Stripe webhooks to mark the payment as successful in Bubble, then let the app check that state when it returns to the foreground. Once the backend shows “paid,” update the UI.

So don’t wait on redirect params, use webhooks as the source of truth for native payment flows.

1 Like