-
Notifications
You must be signed in to change notification settings - Fork 4.2k
refactor(connector): pass optional browser_info to stripe for increased trust #4374
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hrithikesh026
previously approved these changes
Apr 17, 2024
hrithikesh026
previously approved these changes
Apr 18, 2024
srujanchikke
previously approved these changes
Apr 22, 2024
b7f7258
Narayanbhat166
previously approved these changes
Apr 23, 2024
Narayanbhat166
approved these changes
Apr 23, 2024
hrithikesh026
approved these changes
Apr 23, 2024
srujanchikke
approved these changes
Apr 23, 2024
pixincreate
added a commit
that referenced
this pull request
Apr 25, 2024
…to-env * 'main' of github.com:juspay/hyperswitch: ci(postman): Fix Adyen postman collection (#4459) docs(cypress): Update Cypress README Documentation (#4380) Refactor(core): make save_payment_method as post_update_tracker trait function (#4307) refactor(connector): pass optional browser_info to stripe for increased trust (#4374)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-connector-integration
Area: Connector integration
C-feature
Category: Feature request or enhancement
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.
Type of Change
Description
This PR adds optional
browser_info
where we pass theuser_agent
andip_address
in the name of added security for increasing trust as recommended here in their docs.Additional Changes
Motivation and Context
This changes helps increase trust in the transactions done and reduce fraudulent transactions.
How did you test it?
Tested locally.
For a Payment made that has
browser_info
passed, we're passingip_address
anduser_agent
info to the connectorNormal Payments
Logs:

Sent info can also be verified in the Stripe dashboard under
request_parameters
:Mandate Payments
Setup Mandate
Logs:
In recurring payments, you're cannot pass
browser_information
, hence we passnull
Logs:
Ran postman tests for regressions
Even if you pass entire supported
browser_info
, onlyip_address
anduser_agent
is sent to StripeChecklist
cargo +nightly fmt --all
cargo clippy