Sign Up Protection

overview not every user who tries to create an account on your site has good intentions some are malicious actors attempting to create multiple accounts—whether for account aging and laying the groundwork for future fraud attacks or for abusing new account related discounts stopping abuse and fraud at the entry point protects your account ecosystem in multiple ways it helps prevent losses from users exploiting promotions, ensures compliance with your terms and conditions, and allows you to measure meaningful customer metrics accurately—giving you greater control over your ecosystem the https //docs forter com/reference/signup api helps prevent fraudulent account creation by providing approve/decline decisions in real time when a user attempts to register implementing the signup api is seamless, as outlined in the process below primary use cases there are a number of ways you can utilize the account sign up protection offered by this api the account sign up api can be used to enforce the following scenarios multiple account abuse to prevent the user from creating an account if they’ve already created \[x number] of accounts using alternate identifiers (email, phone) promotional/incentive/bonus abuse to prevent the user from creating an account if they’ve already used a referral code \[x number] times with any other credentials referral abuse to prevent the user from creating an account using a referral code if they’ve already used a referral code \[x number] times with any other credentials fake accounts to prevent the user from creating an account if any of their known aliases have been previously blocked due to fraud in the forter ecosystem seller side abuse to prevent sellers from creating an account if any of their known aliases have been previously blocked due to fraud, abuse, or another policy violation t\&c abuse to prevent the user from creating an account if any of their known aliases have been previously blocked due to policy violation an example may be to prevent the user from creating an account if they are flagged by merchant as a known abuser bot protection to prevent bots from generating accounts on your platform integration steps https //docs forter com/front end integration in your dedicated forter portal, you will receive a javascript snippet for both sandbox and production for native mobile apps, you will receive links to download forter's native sdks you'll paste the js script on the appropriate pages of your website or call mobile sdk methods on relevant mobile app screens so that it can load and asynchronously collect important behavioral data from your customer the script or mobileuid generated by the mobile sdk will also generate a unique token for each user on your site that should be included in the account sign up api request body send signup request for decision the https //docs forter com/reference/signup is used for approving / declining account creation attempts by customers or end users signup api request data points collected are common signup properties account id and additional characteristics (e g type of account) eventtime the time that the trigger event occurred in milliseconds connectioninformation cyber intelligence data to analyze browsing behavior, device and connection quality such as ip address, user agent and data collected via js / mobile sdk user personal details user personal details such as email or additional info collected (phone, names, etc nice to have signup flow indicators (social sso used, "remember this device") { "accountid" "e520 ba9a 367 60b", "eventtime" 1415287568000, "connectioninformation" { "customerip" "10 0 0 127", "useragent" "mozilla/5 0 (windows nt 6 1; wow64) applewebkit/537 36 (khtml, like gecko) chrome/47 0 2526 73 safari/537 36", "fortertokencookie" "2315688945984" }, "channeltype" "web", "accountdata" { "personaldetails" { "firstname" "john", "lastname" "smith", "email" "john s\@test com" }, "created" 1415273168, "type" "business", "merchantaccountstatus" "open", "status" "active", } } signup api response the response body will include the accountid , correlationid , a decision, as well as parameters for the verification method and a recommendation for further identification if needed (i e mfa or supplementary identification documents) upon receipt of the response, you can leverage the forterdecision and recommendation parameters in the response body to curate the customer journey or block bad actors from creating bogus accounts on your site key fields forterdecision the latest forter decision regarding the attempted action said fields may hold one of various options "approve" for approved signup requests, where user should be allowed to register for a new accounts; "decline" for declined signup requests, where user should be declined from registering for new accounts; "verification required" for signup requests, where user should be triggered an additional verification (via email, sms, etc ,; "not reviewed" recommendation a specific recommendation for an action that might help the customer to complete their transaction/action (e g verify phone via sms, verify via push notification, verify email, perform a 3ds check, etc ) correlationid a forter unique identifier that should be sent to forter as part of the advancedauthenticationmethod object to correlate the mfa recommendation given in this response with the relevant additional authentication attempt result { "forterdecision" "verification required", "recommendation" "email verification", "accountid" "e520 ba9a 367 60b", "correlationid" "hgj7512345h3de", "verificationmethod" { "correlationid" "hgj7512345h3de", } }{ "forterdecision" "approve", "recommendation" "", "accountid" "e520 ba9a 367 60b", "correlationid" "hgj7512345h3de", "verificationmethod" { } } send authentication attempts the https //docs forter com/reference/authentication result is used to inform forter of authentication results after an mfa was required by a previous signup api request, using the provided correlation id while no decision is provided on this request, it is required in order to ensure optimal customer experience as well as continuously improving the decision model authentication result api request key fields accountid customer's account uid in merchant's site eventtime the time that the trigger event occurred in milliseconds additionalauthenticationmethod correlationid a forter unique identifier that was provided as part of a forter api response recommending additional authentication measures used to correlate between the user action which triggered the recommendation and the authentication attempt result required when the additional authentication was triggered by forter's recommendation additionalauthenticationmethod verificationoutcome may take various forms depending on verification outcome for example additionalauthenticationmethod verificationoutcome is a general authentication result enumerated field with 3 possible values \["success"; "failure"; none attempted] please see the https //docs forter com/reference/authentication result api reference section for more details { "accountid" "e520 ba9a 367 60b", "eventtime" 1415287568000, "connectioninformation" { "customerip" "10 0 0 127", "useragent" "mozilla/5 0 (windows nt 6 1; wow64) applewebkit/537 36 (khtml, like gecko) chrome/47 0 2526 73 safari/537 36", "fortertokencookie" "2315688945984" }, "channeltype" "web", "additionalauthenticationmethod" { "verificationoutcome" "success", "correlationid" "87363864834", }, } authentication result api response as this api is only used to provide forter's model's additional information, the decision returned will always be "not reviewed" supplementary parameters like correlationid and accountid are also returned in the api response send account status updates the https //docs forter com/reference/account status is used to provide forter model's additional information indication of accounts closed by the merchant or accounts that changed in status that reflect agreement or disagreement with forter's sign up decision (use / ignore the decision) the account status api is only intended to provide forter with additional details and does not return a new decision rather, the response will always be "not reviewed" account status api request main data points are status updated status (forter enum format) enumerated values include ("active"; "suspended"; "closed"; "guest"; "pending") statuschangereason merchant descriptive reason for closing the account { "accountid" "e520 ba9a 367 60b", "eventtime" 1415287568000, "status" "suspended", "statuschangereason" "user violation of coupon abuse policy", "connectioninformation" { "customerip" "10 0 0 127", "useragent" "mozilla/5 0 (windows nt 6 1; wow64) applewebkit/537 36 (khtml, like gecko) chrome/47 0 2526 73 safari/537 36", "fortertokencookie" "2315688945984" }, "type" "business", "merchantaccountstatus" "open", "statuschangeby" "merchant admin" } prepare and upload # to ensure the highest level of accuracy for our decisioning model, forter customizes our model to fit the specific risk profile of each of our customers we achieve this by training the model with your past signup and login data in order to provide you with better accuracy from day 1 complete https //docs forter com/qa#uk1vi the purpose of forter's integration tests is to make sure that your integration covers all relevant use cases, while still in the sandbox or test environment each use case may need a different combination of attributes and values to make sure you have covered each of the use cases we expect in your integration, please go through the test scenario list in the integration tests section of portal for each, you'll need to create the scenario in your sandbox site that will generate a call to forter's api then, select the corresponding api request that forter received and click run to verify that the sample request meets the criteria deploy to production once the integration tests have passed, and you've reviewed any gaps with a forter implementation engineer please, deploy your code to your production environment, with two critical adjustments replace your site id and secret key with your https //docs forter com/reference/environments#x fxu update your javascript snippet and mobile sdks to use your production site id and the production hash keys, if relevant please note that this does not yet complete your integration until forter has switched your site to live (after data validation and listen mode), all forter decisions will return "not reviewed" https //docs forter com/qa#qeexu once in production, forter uses a data validation tool to execute a set of automated tests across your live data in aggregation the test outputs are daily reports that validate the accuracy and completeness of the production data we receive from you you can monitor this output in forter portal under integration center tools we recommend checking the report daily to identify any failed tests, which will prevent you from moving forward to listen mode https //docs forter com/qa#dkxgh in "listen mode", we will monitor the production traffic on your site and calibrate our models before we begin to provide you with decisions this is a critical stage to ensure you meet your kpis, and usually lasts around 7 14 days your implementation engineer will update you on the specific timeline for your integration during this time, forter will continue to return "not reviewed" decisions in the api response go live as forter begins to send decisions and recommendations, confirm that your production site is handling responses as expected