riskFORCE

About riskFORCE

Access & Authentication

/public/checkactor

/public/v2/checkactor

Working Example

/secure/checkactor

/add/selfexclusion

/checkip

Default

riskFORCE is designed for Proprietary Trading Firms and Funding companies to minimize the risk of bad actors (chargebacks, fraudulent users, etc) from entering their programs.Our API is powered by a shared collective, with contributions from many different companies. Your records are never shared with another company, but they are used to power our API and our response.Using our API - you can query our database the instant a new user signs up, registers, or performs a ‘reset’. Simply pass the user email, name or IP address to our servers and we will alert you if we have found a match. Dont want to send your customer details? No problem - use our secure endpoint to send an Encrypted SHA256 hash instead.Put an end to bad actors for good.

is designed for Proprietary Trading Firms and Funding companies to minimize the risk of bad actors (chargebacks, fraudulent users, etc) from entering their programs.

Our API is powered by a shared collective, with contributions from many different companies. Your records are never shared with another company, but they are used to power our API and our response.

Using our API - you can query our database the instant a new user signs up, registers, or performs a ‘reset’. Simply pass the user email, name or IP address to our servers and we will alert you if we have found a match. Dont want to send your customer details? No problem - use our secure endpoint to send an Encrypted SHA256 hash instead.

The riskFORCE API uses token authentication. In order to access the API, you must pass a <code class="slate-code">key</code> parameter, using your unique token, with each request. Your API token can be found on your dashboard by logging into <code class="slate-code">https://app.riskforce.io</code> and clicking ‘View API Key’.

 API uses token authentication. In order to access the API, you must pass a 

 parameter, using your unique token, with each request. Your API token can be found on your dashboard by logging into 

Query the riskFORCE database to search for a potential Bad Actor using plain text search strings (for a more private option where you don&apos;t send us customer details, see <code class="slate-code">/secure/checkactor</code>). This is most commonly done during the purchase journey at the time of a user purchase / registration. If a record is found in our Database, you will receive a response back. We only return records that are a Very Likely match or better. You can decide how to best utilize our data, but we recommend blocking all users where a ‘High’ or higher <code class="slate-code">riskLevel</code> match is found from entering your program.Note on query parameters:When making an API call to our system, you can pass only one query parameter at a time. The available query parameters are:<code class="slate-code">name</code><code class="slate-code">email</code><code class="slate-code">ip</code>We recommend searching by IP address when available, followed by email address. Searching by name should only be used when no other option is available.Our algorithm will search the Database and report the results back in an easy to use format.Often times, users will register the same email with different names, and visa-versa to try and skirt your rules. It is not uncommon for a Bad Actor to use dozens of aliases. Luckily, our system does the dirty work for you - and searches the entire database with an advanced matching engine.<div class="slate-mention_input"></div>

database to search for a potential Bad Actor using plain text search strings (for a more private option where you don't send us customer details, see 

). This is most commonly done during the purchase journey at the time of a user purchase / registration. If a record is found in our Database, you will receive a response back. We only return records that are a Very Likely match or better. 

You can decide how to best utilize our data, but we recommend blocking all users where a ‘High’ or higher 

 match is found from entering your program.

When making an API call to our system, you

 can pass only one query parameter at a time

We recommend searching by IP address when available, followed by email address. Searching by name should only be used when no other option is available.

Our algorithm will search the Database and report the results back in an easy to use format.

Often times, users will register the same email with different names, and visa-versa to try and skirt your rules. It is not uncommon for a Bad Actor to use dozens of aliases. Luckily, our system does the dirty work for you - and searches the entire database with an advanced matching engine.

email

name

Is true if match is found in riskFORCE Database

matchFound

riskFORCEAnalysis

matchData

Sample response for checking a users EMAIL

We&apos;ve added a new endpoint that allows you to send multiple query params in a single request. Unlike with our <code class="slate-code">/public/checkactor</code> endpoint, you can now send multiple parameters in the body of a request in one go.You can decide how to best utilize our data, but we recommend blocking all users where a ‘High’ or higher <code class="slate-code">riskLevel</code> match is found from entering your program.Our algorithm will search the Database and report the results back in an easy to use format.Often times, users will register the same email with different names, and visa-versa to try and skirt your rules. It is not uncommon for a Bad Actor to use dozens of aliases. Luckily, our system does the dirty work for you - and searches the entire database with an advanced matching engine.<div class="slate-mention_input"></div>

We've added a new endpoint that allows you to send multiple query params in a single request. Unlike with our 

 endpoint, you can now send multiple parameters in the body of a request in one go.

matches

You can send the following request to our public endpoint (<code class="slate-code">/public/checkactor</code>) API to see how a response is returned when a match is found. Please update with your API Key. Note: This endpoint accepts a plain text value query param (ex: john.smith@gmail.com).

You can send the following request to our public endpoint (

) API to see how a response is returned when a match is found. 

Please update with your API Key. Note: This endpoint accepts a plain text value query param (ex: john.smith@gmail.com).

While the <code class="slate-code">/public/checkactor</code> endpoint utilizes the advanced riskFORCE matching algorithm and often times will return the best results, there may be customers who prefer a more private option, unwilling to send us their customer details.We&apos;ve designed the secure endpoint to allow you to simply pass an SHA256 hash value instead of any identifying information. Using this method ensures that your customer data never reaches our servers.All of the Known Bad Actors in our database have SHA256 hashes saved for their <code class="slate-code">email</code>, <code class="slate-code">name</code> and <code class="slate-code">ip</code> (if present). This allows you to send a search query using the same SHA256 hash value to perform a lookup against our database. In addition, this ensures GDPR compliance. Note on query parameters:When making an API call to our system, you can pass only one query parameter at a time. The available query parameters are:<code class="slate-code">name</code><code class="slate-code">email</code><code class="slate-code">ip</code>IMPORTANT:When performing a lookup request to our secure endpoint, make sure and format your query string <code class="slate-code">toLowerCase()</code> client side before hashing and sending to our API. All of our saved database values are first adjusted to lower case before we hash them, so any request you send to lookup against our tables will need to also be adjusted to lower case before hashing.We recommend searching by IP address when available, followed by email address. Searching by name should only be used when no other option is available.While the secure endpoint allows complete privacy from your customer details, it is limited by only returning exact matches.

 endpoint utilizes the advanced riskFORCE matching algorithm and often times will return the best results, there may be customers who prefer a more private option, unwilling to send us their customer details.

We've designed the secure endpoint to allow you to simply pass an SHA256 hash value instead of any identifying information. Using this method ensures that your customer data never reaches our servers.

All of the Known Bad Actors in our database have SHA256 hashes saved for their 

 (if present). This allows you to send a search query using the same SHA256 hash value to perform a lookup against our database. In addition, this ensures GDPR compliance. 

When making an API call to our system, you can

When performing a lookup request to our secure endpoint, make sure and format your query string 

All of our saved database values are first adjusted to lower case before we hash them, so any request you send to lookup against our tables will need to also be adjusted to lower case before hashing.

While the secure endpoint allows complete privacy from your customer details, it is limited by only returning 

You can send the following request to our public endpoint (<code class="slate-code">/secure/checkactor</code>) API to see how a response is returned when a match is found. Please update with your API Key. Note: This endpoint accepts a SHA256 hash query param (ex: d0c648bc36f12061bec770df216cea2ab95851b9350fd54b658de53b0407767a).

Please update with your API Key. Note: This endpoint accepts a SHA256 hash query param (ex: d0c648bc36f12061bec770df216cea2ab95851b9350fd54b658de53b0407767a).

In addition to using the riskFORCE database to search for potential Bad Actor&apos;s, you can also use our service to flag users who have self-excluded themselves from your services. Self-exclusion is often seen in online gaming and casino providers, but is becoming more popular with Proprietary Trading and Funding companies as well. By building a self-exclusion form / button into your web application, you can be one step ahead in the eyes of regulators as you show you are looking out for the well being of your customers.

database to search for potential Bad Actor's, you can also use our service to flag users who have self-excluded themselves from your services. Self-exclusion is often seen in online gaming and casino providers, but is becoming more popular with Proprietary Trading and Funding companies as well. 

By building a self-exclusion form / button into your web application, you can be one step ahead in the eyes of regulators as you show you are looking out for the well being of your customers.

message

exclusionEnds

success

In addition to checking if a user is in our Database of known Bad Actors, riskFORCE also allows you to check if a specific IP address originates in an OFAC sanctioned country or a VPN service.Note on query parameters:When making an API call to this endpoint, you simply pass an IP address along with your API key.

In addition to checking if a user is in our Database of known Bad Actors, 

also allows you to check if a specific IP address originates in an OFAC sanctioned country or a VPN service.

When making an API call to this endpoint, you simply pass an IP address along with your API key. 

countryName

countryCode

If the Country is on the OFAC Sanctioned List