m2pfintech
API LibraryMl falcon fly

Face Liveness Pro

Face Liveness Pro API distinguishes live persons from spoofing attacks, deepfakes, and Generative AI avatars using a single image — no action or movement required.

Spoofs or Presentation Attacks involve representations of human faces used by fraudsters to deceive face biometric systems and commit identity theft. Our Facial Liveness Pro API can distinguish a live person from a spoofing attack through Liveness Detection or Presentation Attack Detection (PAD) along with Deepfakes detection. Unlike most other systems that perform PAD, our Facial Liveness does not require any action or movement — it only requires a single image of the user taken from the front camera of their phone.

Types of Presentation Attacks

#Attack TypeDescription
1Printed Photo AttackA fraudster prints photos of an individual and presents them in front of the camera during verification.
2Video Replay AttackA fraudster uses a digital screen (e.g., phone or tablet) to play a video of an individual and presents it in front of the camera to deceive the verification system.
3Printed Mask AttackA fraudster uses a cut-out photo in front of their face during verification, often with holes for blinking, which is a common liveness test in other systems.
43D Mask AttackA fraudster creates a silicon or resin mask of an individual and presents it in front of their face during verification.

Advanced Fraud Detection

The Face Liveness Pro API detects not only spoofing attempts but also advanced fraudulent techniques:

  • Deepfakes — Hyper-realistic images created using deep learning algorithms to replace one person's face with another's. The API detects subtle inconsistencies and artifacts unique to deepfakes, ensuring genuine images pass verification.

  • Generative AI Avatars — Highly realistic synthetic faces created using AI techniques like GANs. The API identifies these synthetic images by analyzing patterns and data structures that differ from real human faces.

The API returns a score and percentage used to determine liveness and deepfake detection.

Image Guidelines

#Guideline
1Supported image formats: PNG, JPG, JPEG.
2Image size should not exceed 3MB.
3The image should be taken in a well-lit room, with the face clearly visible to the camera.
4The face should be straight and not tilted.
5Minimum resolution of the detected image should be 224×224 pixels.
6The distance between the eyes should be at least 100 pixels.
7Any occlusions on parts of the face (glasses, masks) should be removed during the liveness check.
8The detected face should occupy at least 30% of the total image area.
9The image should be taken as a selfie in portrait mode only.
10Image compression is not recommended.
11Only live/camera-captured images are permitted — screenshot images will not be detected.
POST
/CheckLivenessPro

Authorization

AuthKeyAuth
authkey<token>

Authentication token obtained from /userauthentication endpoint

In: header

Header Parameters

apikey*string

API key provided by Synt izen

authkey*string

Authentication token obtained from /userauthentication endpoint

Request Body

application/json

liveimage*string

Base64 encoded image (PNG, JPG, JPEG). Max size 3MB.

rrn*string

Request Reference Number, any unique number for the identification of transaction

type*string

Type of detection to perform:

  1. BOTH - Checks for both Liveness and Deepfake detection
  2. LIVENESS - Checks for only Liveness
  3. DEEPFAKE - Checks for only Deepfake
Value in"BOTH" | "LIVENESS" | "DEEPFAKE"
isvkyc?string

Video KYC flag

Response Body

application/json

application/json

application/json

curl -X POST "https://api.syntizen.com/CheckLivenessPro" \  -H "apikey: 0" \  -H "authkey: string" \  -H "Content-Type: application/json" \  -d '{    "rrn": "23242456234",    "type": "LIVENESS",    "isvkyc": "0",    "liveimage": "base64 image"  }'

{
  "respcode": "200",
  "respdesc": "success",
  "rrn": "23242456234",
  "liveness_results": {
    "liveness_description": "real",
    "liveness_score": 0.9767711162567139,
    "liveness_percentage": "97.68"
  }
}

{
  "respcode": "400",
  "respdesc": "Bad Request - Missing or invalid request parameters"
}
{
  "respcode": "401",
  "respdesc": "Unauthorized - Invalid or expired auth key"
}

On this page