Multi-factor Authentication API Specifications

Email One-Time Hyperlink

When an Account Creation or Login request triggers a challenge in Kount 360 Policy Management, the customer can conduct a real-time verification of an email address. A verification email is sent to the email address being used to create or log in to the account. This ensures that the person logging in does have access to the email address.

Once you have email one-time hyperlink (OTH) activated for your Kount 360 account, you can create messaging templates with your company branding to send to customers in the API.

Then, to see status notifications, you can set up webhooks in Kount 360. Webhooks enable real-time data synchronization and automated workflows. They facilitate faster response times by pushing data instantly when an event triggers, removing the need for continuous API calling. This leads to improved efficiency, reduced latency, and enhanced responsiveness.

Login API Requirements

The following attributes are needed to facilitate email Multi-Factor Authentication (MFA):

The end user's email address where the authentication is sent.
```
person.emailAddress
```
The name of the email one-time hyperlink template.
```
strategy.mfaTemplateName
```

When the customer receives the response from the API Login and the MFA request is sent to the end user, the API response body contains the attributes previously listed. Go to the Login API documentation for more information.

New Account Opening API Requirements

The following attributes are needed to facilitate email verification:

The customer's email address used for account creation.
```
person.emailAddress
```
The name of the email one-time hyperlink template.
```
strategy.verificationTemplateName
```

When the customer receives the response from the API New Account Opening and the verification request is sent to the end user, the API response body contains the attributes previously listed. Go to the New Account Opening API documentation for more information.

SMS One-Time Hyperlink

When a New Account Opening or Login request triggers a challenge in Policy Management, the customer can conduct a real-time verification of a phone number. A one-time hyperlink is sent to the user's phone number. This ensures that the person logging in does have access to the phone number.

Once you have SMS one-time hyperlink (OTH) activated for your Kount 360 account, you can create messaging templates with your company branding to send to customers in the API.

Then, to see status notifications, you can set up webhooks in Kount 360. Webhooks enable real-time data synchronization and automated workflows. They facilitate faster response times by pushing data instantly when an event triggers, removing the need for continuous API calling. This leads to improved efficiency, reduced latency, and enhanced responsiveness.

Login API Requirements

The following attributes are needed to facilitate phone Multi-Factor Authentication (MFA):

The end user's phone number where the authentication is sent.
```
person.phoneNumber
```
The name of the SMS one-time passcode template.
```
strategy.mfaTemplateName
```

When the customer receives the response from the API Login and the MFA request is sent to the end user, the API response body contains the attributes previously listed. Go to the Login API documentation for more information.

New Account Opening API Requirements

The following attributes are needed to facilitate phone verification:

The end user's phone number used for account creation.
```
person.phoneNumber
```
The name of the SMS one-time passcode template.
```
strategy.verificationTemplateName
```

When the customer receives the response from the API New Account Opening and the verification request is sent to the end user, the API response body contains the attributes previously listed. Go to the New Account Opening API documentation for more information.

SMS One-Time Passcode

When an Account Creation or Login request triggers a challenge in Policy Management, the customer can conduct a real-time verification of a phone number. A verification message is sent to the phone number being used to create or log in to the account. This ensures that the person logging in does have access to the phone number.

Once you have SMS one-time passcode (OTP) activated for your Kount 360 account, you can create messaging templates with your company branding to send to customers in the API.

Then, to see status notifications, you can set up webhooks in Kount 360. Webhooks enable real-time data synchronization and automated workflows. They facilitate faster response times by pushing data instantly when an event triggers, removing the need for continuous API calling. This leads to improved efficiency, reduced latency, and enhanced responsiveness.

Login API Requirements

The following attributes are needed to facilitate phone Multi-Factor Authentication (MFA):

The end user's phone number where the authentication is sent.
```
person.phoneNumber
```
The name of the SMS one-time passcode template.
```
strategy.mfaTemplateName
```

When the customer receives the response from the API Login and the MFA request is sent to the end user, the API response body contains the attributes previously listed. Go to the Login API documentation for more information.

New Account Opening API Requirements

The following attributes are needed to facilitate phone verification:

The end user's phone number used for account creation.
```
person.phoneNumber
```
The name of the SMS one-time passcode template.
```
strategy.verificationTemplateName
```

When the customer receives the response from the API New Account Opening and the verification request is sent to the end user, the API response body contains the attributes previously listed. Go to the New Account Opening API documentation for more information.