You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use different keys for different purposes / customers etc etc.
We don't cache the client object created using client = razorpay.Client(auth=(keyX, secretX)). We create a new one every time processing starts, eg create or verify, and its immediately consumed in the call, eg client.order.create(data=data), or client.utility.verify_payment_signature(verify_params)
Is there any issue in having multiple clients created with different keys like this? Obviously this is quite normal at the API, so my question is regarding the SDK internals.
The text was updated successfully, but these errors were encountered:
wrt https://github.com/razorpay/razorpay-python?tab=readme-ov-file#usage
We use different keys for different purposes / customers etc etc.
We don't cache the client object created using
client = razorpay.Client(auth=(keyX, secretX))
. We create a new one every time processing starts, eg create or verify, and its immediately consumed in the call, egclient.order.create(data=data)
, orclient.utility.verify_payment_signature(verify_params)
Is there any issue in having multiple clients created with different keys like this? Obviously this is quite normal at the API, so my question is regarding the SDK internals.
The text was updated successfully, but these errors were encountered: