Interface
Dashboard
Transactions
Transaction Details
Customers
Alerts
Cases
Manual Lookup
AML
Scoring Engine
Lists
Monitoring
Channels
Settings
API license keys
Logs
Sandbox Environment
Transactions & Scoring
Scoring Engine Overview
Transactions overview
Default rules
Custom rules and parameters
Automated chargeback management with SEON
Lists & Flagging overview
Transaction Details – General widgets
Similarity Features
Custom fields and industry-specific widgets
Digital Footprint Widgets
Rule categories
Custom scoring and states with rule categories
Lightning track
How to use regular aggregates
How to create a new filter
How to run a batch test
Assigning transactions for review
Streamlining teamwork with proposed system-level changes and approvals
Tagging transactions
Clone search
How to run post-decision automations
Rule Configuration Guide: Best Practices for High Performance
Anti-Money Laundering
AML customer screening & monitoring solution
Payment screening
Configure screening & monitoring settings
Integration methods & API access
Manual lookup & batch screening
AML Data Sources
Optimize screening with fuzzy search
Entity search
Brazil Sports Betting Compliance (SPA Check)
Review customer screening hits
Case Management
Case management overview
Configuring roles & permissions
Creating & managing alert triggers
Handling and resolving alerts
Conducting case investigations
Filing regulatory reports
Integrating & optimizing data flows
Device Intelligence
Device Intelligence Overview
What makes SEON's Device Intelligence unique?
Device Intelligence integration options
Understanding the Hashes - Device Identification with SEON Device Intelligence
Devices Intelligence Widget
Get started with Device Intelligence Rules
Block multi-accounting with Device Intelligence
Residential proxy and VPN detection
Understanding geolocation data with Device Fingerprinting
Understanding behavioral data signals with Device Intelligence
Remote access detection with SEON's Device Intelligence SDKs
True Device ID - Device Identification with SEON Device Intelligence
Settings
Upgrade your account to a paid plan
Setting priority platform timeouts
How to adjust Digital Footprint timeout
SSO with Azure AD – Setup Guide
SSO with Ping Identity – Setup Guide
SSO with Okta – Setup Guide
SSO with Google – Setup Guide
Machine Learning
Machine Learning Overview
Activate blackbox scoring
Whitebox Machine Learning
Blackbox Machine Learning
Understanding a confusion matrix
Email clusters
Network Scores in Advanced Digital Footprinting
Feedback Loops & Label API: Labeling and feedback best practices
SEON for Shopify
Quick Start Guide to SEON for Shopify
Tweak your SEON for Shopify settings
Customize your risk appetite with SEON for Shopify
Capture Shopify payments with SEON
Chargeback management for Shopify
Hold the order fulfillment in Shopify
Cancel risky Shopify orders automatically
Checking orders with SEON for Shopify
SEON’s Shopify admin extensions
How to send custom order information to SEON
Shopify FAQ
Whitepapers
Manual processes - Fraud Investigation
Dynamic Friction - Bringing Pre-KYC into the mix
SEON Compliance Whitepaper
Build a machine learning model using SEON data
How to make the most out of your machine learning model
Identity Verification
Getting started with ID Verification
iOS integration guide
Android integration guide
Web integration guide
Checks and verifications
Operational details
Admin interface
Fraud API connection
Templates
FAQ - Frequently Asked Questions
Sandbox FAQ
Billing and pricing FAQ
Admin Panel FAQ
Rules FAQ
Features FAQ
Miscellaneous FAQ
AML API
Lists and flagging
Integration
Geofence API
Legal and Compliance
Product Changelog
Product changelog

If there isn't a way to verify payment provider accounts, can we at least have info if such an account has already been requested for verification?

Updated on 06.04.22

Copy link

Yes! With Velocity rules, you can check if multiple clients used the same device, IP address, payment information, address, and virtually any other information.