Where can I see all the input fields, are there any examples? Can I add custom fields as well?
Is there a possibility to edit a record at blacklist (for example to add a comment)?
How can we integrate a third party identity verification software in SEON?
Do you use any 3rd party providers for email/phone data enrichment?
Our servers are located in North America, do you have a mirror nearby?
Would I be able to initiate a Fraud API call client-side?
Is it enough to use JS seon.saveSession once per call?
What is an open port, how can it help detecting fraud?
Do IP addresses need to be whitelisted for API access on SEON?
Where can I get the license_key I need?
We're getting a lot of "All APIs +Device, normal Fraud API calls for deposits and withdrawals", but not many "Email+Fraud API+Device". Why is that?
Can you provide a CSP-Settings which is needed to be done here for your script to work properly?
Unauthorised access, account hacking/takeover, whatever you call it, it is a nuisance. How can you prevent it?
If we send a transaction to SEON, will it appear immediately in the dashboard or is there a delay?
Is there a limit as to how often checks are performed?
Should we send session_id alongside with the session or can we ignore the session_id and not send it?
Would I be able to initiate a Fraud API call client-side?
How is the card hash calculated? What data is fed into the hashing?
What is the maximum timeout for both APIs? (Fraud API & Phone API)
Where can I find our API key?
What is the maximum length of request parameters?
What should the 'device_id' contain and is it a mandatory field?
Which version value should we use for the different APIs?
In order to obtain the most accurate fraud score does having the card details make a big difference?
What happens in case the device fingerprinting module is called yet no session payload is sent in the request?
How long does it usually take for the JSAgent to load?
Does the JS Agent v4.0 work with the Fraud API v1.0?
Does it cost extra to use the 'include' parameter to receive additional API information (history, flags, id)?
One of your API endpoints is asking for password_hash. How important is this and what would you expect the method of hashing the password is?
How does the PUT endpoint work?
Is there a way to get raw data that SEON has received or stored?
How is the user ID generated?
Is there a difference between sandbox and prod key?
We are currently using v1 of the Fraud API. Is there any good reason to upgrade it to v2?
What would be the current equivalent of email_details.email_exists?
What is the name of the purchase and registration API methods?
Is it possible to use the same key for 2 different websites, if so what are the differences between using the same or a separate key?
Should the AAP be called by API or by the backend system?
Do we leave the public key on JS v4, that we are using on the v3?
If we would like to check transactions in crypto currencies, is it possible to send transaction_amount as xx.xxxxxxxxx (lots of digits after .)? And transaction_currency like BTC, etc.?
Device info is not being picked up for certain customers and transactions. Is it because the device info call is made after the Fraud API-call on customer registration or sign in?
Can we provide our merchants the possibility to mark transactions with the Label API directly?
What is the "Label API" used for?
What action_type is the best to use when a user adds a new email address to their account?
Is there a built in API against spamming in SEON? What do we do in the case of API abuse on the frontend?
How long do you store data as default at SEON?
Does SEON track virtual numbers and disposable, temporary phone numbers?
What are harmful IPs?
What devices are included in the Device Fingerprinting feature?
How many digits can you check for Card BINs?
How is encryption handled in SEON?
What does SEON look for to check spoofing under suspicious browser profiles?
What makes certain browsers high-risk?
Which browser extensions can I use to test the device fingerprinting module?
How do you decide which browsers are fraudulent?
Is it possible to expand on the current fields with additional data points?
What does "Customer is using a datacenter ISP" mean?
Which fingerprinting hash should I use to determine whether two accounts belong to the same person?
Can the APIs get data about the user's age?
Is there documentation about the device fingerprinting and the different hashes?
What does "device hash" mean exactly?
What is the standard expected information to share that you need when it comes to crypto transactions?
Are you able to detect if someone is preventing port scans?
When the email is not deliverable should we consider that the email address doesn't exist?
When should we call device fingerprinting?
Which APIs should we run at registration?
Do you have a test environment?
How should we use Fraud API if we only need device data?
Does SEON support IPv6 addresses?
How does password hash matching work?
Do we need to provide an email address for SEON to assign a Fraud Score for a user?
Where can I see all input fields, are there any examples? Can I add custom fields as well?
Is there a field in the Fraud API where a Paysafe account number can be passed?
In order to verify additional user details such as phone number, address, and bank account we have used the action_type 'verification'. Does it matter which one will be used, and if so, is there a better one?
Can we recover data from our past transactions in SEON?
Is there a retry logic in place for failed webhook deliveries?
Does your service simply accept or decline requests based on the data we send? Or do you provide a detailed response?
Can we access the payload only through the Admin Panel?
The Fraud API has both the State and the Score in the response, but other APIs don't. Why is that?