Learn how Greip can help you prevent multi-accounting in your application.
/geoip
, /lookup/ip
, /lookup/ip/threats
How it helps:
Detect if multiple accounts are being created from the same IP address or a suspicious IP range.
Identify high-risk IPs (e.g., VPNs, proxies, Tor nodes) that are commonly used for multi-accounting.
Use the security module to check if the IP is associated with malicious activity.
/geoip
(with the device module)
How it helps:
Greip can provide device-related information (e.g., browser, OS, device type) that can be used to fingerprint devices.
If multiple accounts are being created from the same device, it could indicate multi-accounting.
/scoring/email
, /scoring/phone
How it helps:
Detect disposable or temporary email addresses (common in multi-accounting).
Validate phone numbers to ensure they are legitimate and not reused across multiple accounts.
Flag suspicious email domains or phone numbers associated with fraud.
/scoring/payment
How it helps:
Analyze payment details (e.g., credit card, billing address) to detect patterns of multi-accounting.
Identify if the same payment method is being used across multiple accounts.
/lookup/asn
, /lookup/bin
How it helps:
Detect if multiple accounts are being created from the same Autonomous System (ASN), which could indicate coordinated multi-accounting.
Validate credit card BINs to ensure they are not being reused fraudulently.
/scoring/profanity
How it helps:
Detect if users are creating accounts with offensive or suspicious usernames, which could indicate multi-accounting for abusive purposes.
Step 1:
Step 2:
/geoip
and
/lookup/ip/threats
endpoints to check if the IP is high-risk (e.g., VPN, proxy, or Tor).Step 3:
/scoring/email
to ensure it’s
valid, correct, and not disposable.Step 4:
/scoring/phone
to ensure it’s
legitimate and not disposable.Step 5:
Step 6:
/scoring/payment
to analyze
payment details for signs of fraud.Step 7: