#aviran bergic
1 messages · Page 1 of 1 (latest)
Not really. Our suggestion is that just turning on Test mode, and test everything you want there. Test mode guarantee to not generate any transaction, and it behaves (mostly) identical to Live mode
but what can we do in live mode if we dont really want to charge our internal users?
no other alternatives?
no unique credit card number for live mode that is not really charging anything?
@graceful lichen
No. Livemode is... live, so it only takes real card number. Why do you want to test in Live mode anyway? There should be a very few things which can't be tested in Test mode
Basicaly Testmode should be enough to test every scenarios
you did not follow.
as a user in our system you can purchase different plans and also upgrade the plan in order to get specific features.
we want to be able to perform such operation in produciton, not to test the beahvior but to actually have access to the features (performing demo for costumers) so we need to complete a regular user flow
so ill change my question.
will it cause any issue, if we will have 2 instance of the sdk on production from the same server, that sometimes send live mode true/false
example
internal useres -> new Stripe(testApiKey)
regularUser -> new Stripe(liveApiKey)
and we will generate requests with both of them from the same server
Um generaly you would be fine since those requests touch isolated data. But for example if you accidentally try to update a result of this instance by the another one you would found resource not found ish errors
yes thats for sure would be an issue.