-
-
Notifications
You must be signed in to change notification settings - Fork 479
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plans on live + test mode with the same stripe IDs #464
Comments
Makes sense and sounds good |
PS: I think the same situation is true for coupons, once we get support for those. |
Not sure if this is exactly related to my question, but seems to be close. I currently only have a text pub & secret key. I just updated to 1.0.0 and am getting odd warnings. putting only tst keys, it tells me: Should't I be able to test with only test keys populated (that's all I have right now) if the LIVE setting is FALSE? |
Make sure you specify |
I'm gonna go ahead and close this as a wontfix. Given that plans are able to have unique IDs now it seems like stripe is "deprecating" having these non-unique IDs. |
Plan.stripe_id
is inherited from StripeObject which makes it unique. Plan stripe IDs don't work quite the same way as other stripe objects though because their IDs are user-input and users are likely to use the same ID on live and test. If this is not supported, it needs to be documented, but I personally think we should move to a unique_together w/ stripe_id + livemode for Plan.The text was updated successfully, but these errors were encountered: