Activate fraud services before WPCOM/Jetpack connection and account onboarding #7520
Conversation
This file contains 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
…-and-account-creation
…m-connection-and-account-creation
Test the buildOption 1. Jetpack Beta
Option 2. Jurassic Ninja - available for logged-in A12s🚀 Launch a JN site with this branch 🚀 ℹ️ Install this Tampermonkey script to get more options. Build info:
Note: the build is updated when a new commit is pushed to this PR. |
|
Size Change: +6 B (0%) Total Size: 1.43 MB
ℹ️ View Unchanged
|
…m-connection-and-account-creation
…m-connection-and-account-creation
…m-connection-and-account-creation
dmallory42
approved these changes
Oct 22, 2023
There was a problem hiding this comment.
Tested following the instructions and everything worked perfectly as described (one small note, for the last step of checking the checkout page, for me it was wcpay_upe_config instead of wcpayConfig - I guess it depends on which checkout is enabled).
Thanks for the care and attention in the instructions and the comments in the code as well, very much appreciated! 🐐
Left a few questions/comments but nothing blocking from my side, thanks for working on this!
…m-connection-and-account-creation
|
Thank you, @dmallory42, for doing this review! I really appreciate it. |
…m-connection-and-account-creation
…m-connection-and-account-creation
vladolaru
changed the title
vladolaru
deleted the
add/7517-activate-fraud-services-pre-wpcom-connection-and-account-creation
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #7517
Changes proposed in this Pull Request
Title: Activate fraud tracking before onboarding and/or WPCOM/Jetpack connection
Description:
Until now, we have provided the fraud services configuration only through the account data (the
fraud_servicesentry). This meant that we could not activate them prior to onboarding. This hampers our accounts fraud detection capabilities.We now take advantage of a new server API endpoint (
accounts/fraud_services) that will provide the public, account-agnostic fraud services configuration so we can properly initialize them without the need for an account or a Jetpack connection (the endpoint is public). This refers right now to Sift activation.The fraud services configuration in the account data is still used and takes precedence over the one from the public endpoint.
We will activate the Sift JS SDK tracking in all WooCommerce admin pages and the WooPayments Connect page.
Testing instructions
Broken Token Utilitieshttps://cdn.sift.com/s.js(search bysift). You should also have a request tohttps://hexagon-analytics.comnpm run listenwcpaySettings.fraudServices.sift. It should have entries like these:user_idinwcpaySettings.fraudServices.siftmatches the one in WCPay Dev Tools' Store Details sidebarwcpayConfig.fraudServices.sift. It should have entries like these:npm run changelogto add a changelog file, choosepatchto leave it empty if the change is not significant. You can add multiple changelog files in one PR by running this command a few times.Post merge