Signup

Account Sign Up Integration

Step 1: 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.

Step 2: Account SignUp API

Sign Up Protection API Request
The Sign Up Protection API is used for Approving / Declining account creation attempts by customers or end users. 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")

Please see the Customer Account Sign Up 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",
  "accountData": {
    "personalDetails": {
      "firstName": "John",
      "lastName": "Smith",
      "email": "[email protected]"
    },
    "created": 1415273168,
    "type": "BUSINESS",
    "merchantAccountStatus": "open",
    "status": "ACTIVE",
  }
}

Account Sign Up API Response
The Account Sign up 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": {
  }
}