Skip to content
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

Advanced fraud protection page does not render the settings correctly #9520

Closed
eduardoumpierre opened this issue Oct 4, 2024 · 1 comment · Fixed by #9521
Closed

Advanced fraud protection page does not render the settings correctly #9520

eduardoumpierre opened this issue Oct 4, 2024 · 1 comment · Fixed by #9521
Assignees
Labels
category: core WC Payments core related issues, where it’s obvious. category: riskops component: fraud & risk tools Issues related to merchant facing risk tools and processing between auth and capture. focus: fraud tools type: bug The issue is a confirmed bug.

Comments

@eduardoumpierre
Copy link
Contributor

Describe the bug

The settings on the Advanced Fraud Protection page are not being rendered/populated as expected. The data is stored correctly when the changes are saved, but it fails to display it in the UI.

To Reproduce

  1. Go to Payments > Settings and scroll to the Fraud protection section
  2. Check the Advanced option and click on its action button
  3. Scroll to the Purchase Price Threshold section and enable filtering
  4. Save the changes
  5. Refresh the page
  6. The Purchase Price Threshold section will be empty/unchecked

Expected behavior

  1. The fraud protection changes should be reflected in the UI after saving them and refreshing the page
@eduardoumpierre eduardoumpierre added the type: bug The issue is a confirmed bug. label Oct 4, 2024
@eduardoumpierre eduardoumpierre self-assigned this Oct 4, 2024
@eduardoumpierre eduardoumpierre added category: core WC Payments core related issues, where it’s obvious. component: fraud & risk tools Issues related to merchant facing risk tools and processing between auth and capture. category: riskops labels Oct 4, 2024
@csmcneill
Copy link
Contributor

8861147-zen

My tests indicate that this is just a visual bug. If I...

  1. Configure WooCommerce to only accept payments in the US
  2. Enable filtering for international IP addresses
  3. Enable filtering for IP address mismatch
  4. Use a VPN to change my IP address to another country (e.g., DK)
  5. Make a payment using a non-US card (e.g., 4000002080000001 is a DK test card)

...the payment is blocked as expected:

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: core WC Payments core related issues, where it’s obvious. category: riskops component: fraud & risk tools Issues related to merchant facing risk tools and processing between auth and capture. focus: fraud tools type: bug The issue is a confirmed bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants