Fix/payment link autocorrect #324
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes #321.
Users frequently pass string values (e.g.,
"true","false") in theoptionsdictionary, expecting them to work like booleans. The Razorpay API strictly requires integers (1/0). When strings are sent, the API silently ignores them (defaulting to False), causing issues like PayPal options not appearing.Changes
payment_link.create."true","false") inoptions.checkout.methodand automatically casts them to integers (1,0).Verification
{"card": "true"}is correctly transformed to{"card": 1}before the network request.