Stripe question: Moved products from "test data" to "production" and API ID changed

Need help APIs
1

I’m ready to launch my app into production and I ran into an interesting Stripe issue. I know it’s not a Bubble issue per se, but my Bubble app in production isn’t charging properly as a result of this issue.

Below are screenshots of my Stripe test data products and my Stripe production data products:

Test data

test-data
test-data974×264 28.8 KB

Production data

production-data
production-data978×268 28 KB

As you can see, in the test data, the two prices for the one product have different API IDs, but when the test data product is copied to production, the two prices for the one product have the same API IDs, which is causing my ability to charge for the one of the pricing options broken.

Has anyone else seen this?

If so, how did you resolve it?

2

Hi
Not having this issue.
I think you just need to create a new product manually in your production Stripe’s dashboard ?

3

In order to run tests within both Bubble Development and Live modes, I think need the same products to exist in the Stripe test and production environments.

If I create a new product in the Stripe production environment, will Bubble find it when Bubble is running in Development mode?

4

Did you find a solution?

5

Worse.

I was told there isn’t one.

The Stripe API pricing identifies for test and production are just different.

What this means in practical terms is every time I copy my production Bubble data to my development Bubble instance, I need to edit the table where I store the Stripe plans and pricing to edit the pricing IDs.

Something I consider “not ideal”, but can live with.

6

Could it be solve by applying condition “when live” in the workflow and duplicate steps for the live version of the app?
When it’s not live use ID’s from the dropdown, when it’s live version use dynamic values and copy prod price ID’s from Stripe

7

I hadn’t even known of “when live” before, and I like this idea.

When I look for “when live”, I find an

Only when “Isn’t live version”

For this to work, I also need an

Only when “Is live version”

and there doesn’t seem to be one.

8

Yeah, that’s the one I was talking about. “Isn’t live version” has yes and no options. It’s a bit confusing. “Isn’t live version is yes” means test version and “Isn’t live version is no” means live version. Most confusing syntax. Let me know if it works.

9

Thank you for following up.

I failed to notice the “is yes” and “is no” that can be appended.

I do indeed think that will solve my problem.

Thank you.