Dummy Results

Requirements:

API key pair
DEV environment
Finances added to your environment

Dummy results only work in the DEV environment. Calling either endpoint from any other environment returns an error:

Environment	Error message
DEMO	`"This endpoint is not available for DEMO partners."`
TEST / PROD	`"This endpoint is not available for TESTING/PRODUCTION partners."`

Why is DEMO excluded? The DEMO environment is intended for showing the real verification flow to prospective clients. Dummy shortcuts would let partners simulate completed verifications without going through the actual process, which could give clients a misleading picture of what the product does. The restriction is intentional.

Dummy Auto Results

POST https://ivs.idenfy.com/api/v2/token
Authorization: Basic {API_KEY}:{API_SECRET}
Content-Type: application/json

You can create a session with a dummy auto status for verification in the development environment. The request must contain the same parameters as session creation plus dummyStatus, which defines the dummy session’s auto result.

JSON key	Type	Description
`dummyStatus`	`String`	Auto status of the verification. Possible values: `APPROVED`, `DENIED`, `SUSPECTED`, `EXPIRED`. See Verification Statuses for details.

Request Example

{
  "dummyStatus": "APPROVED",
  "clientId": "100000",
  "firstName": "John Tom",
  "lastName": "Smith",
  "successUrl": "https://www.my-company.com/idenfy/success",
  "errorUrl": "https://www.my-company.com/idenfy/fail",
  "locale": "en",
  "showInstructions": true,
  "expiryTime": 600,
  "sessionLength": 600,
  "country": "lt",
  "documents": ["PASSPORT", "ID_CARD"],
  "dateOfBirth": "1990-12-20",
  "dateOfExpiry": "1990-12-20",
  "dateOfIssue": "1990-12-20",
  "nationality": "lt",
  "personalNumber": "123456789",
  "documentNumber": "123456",
  "sex": "M",
  "address": "Address",
  "tokenType": "IDENTIFICATION",
  "externalRef": "reference"
}

Response Example

A successful API call returns a JSON response with a scanRef that can be used to add a dummy manual status.

{
  "message": "Dummy token and verification created successfully",
  "authToken": "pgYQX0z2T8mtcpNj9I20uWVCLKNuG0vgr12f0wAC",
  "scanRef": "ec6a7108-8c26-11e9-9758-309c231b1bac",
  "clientId": "100000",
  "firstName": "JOHN TOM",
  "lastName": "SMITH",
  "successUrl": "https://www.my-company.com/idenfy/success",
  "errorUrl": "https://www.my-company.com/idenfy/fail",
  "locale": "en",
  "showInstructions": true,
  "country": "lt",
  "expiryTime": 600,
  "sessionLength": 600,
  "documents": ["PASSPORT"],
  "dateOfBirth": "1990-12-20",
  "dateOfExpiry": "1990-12-20",
  "dateOfIssue": "1990-12-20",
  "nationality": "lt",
  "personalNumber": "123456789",
  "documentNumber": "123456",
  "sex": "M",
  "digitString": "4823657",
  "address": "Address",
  "tokenType": "IDENTIFICATION",
  "externalRef": "reference"
}

Dummy Manual Result

POST https://ivs.idenfy.com/api/v2/add-dummy-status
Authorization: Basic {API_KEY}:{API_SECRET}
Content-Type: application/json

You can add a dummy manual status for a verification in the development environment and receive the same webhook as after a real manual review.

The client’s verification must already be created. If not, generate a new token with dummyStatus first.
For an approved verification, you need to provide both FACE_MATCH and DOC_VALIDATED statuses.

Request Parameters

Key	Type	Description
`scanRef`	`String`	A unique string identifying a client verification.
`manualFaceMatchResult`	`String`	Dummy manual face status. Possible values: `FACE_MATCH`, `FACE_MISMATCH`, `NO_FACE_FOUND`, `TOO_MANY_FACES`, `FACE_TOO_BLURRY`, `FACE_UNCERTAIN`, `FACE_NOT_ANALYSED`, `FACE_NOT_CHECKED`, `FACE_ERROR`, `AUTO_UNVERIFIABLE`, `FAKE_FACE`. See Verification Statuses → Face Status Values for details.
`manualDocumentValidity`	`String`	Dummy manual document status. Possible values: `DOC_VALIDATED`, `DOC_INFO_MISMATCH`, `DOC_NOT_FOUND`, `DOC_NOT_FULLY_VISIBLE`, `DOC_NOT_SUPPORTED`, `DOC_FACE_NOT_FOUND`, `DOC_TOO_BLURRY`, `DOC_FACE_GLARED`, `MRZ_NOT_FOUND`, `MRZ_OCR_READING_ERROR`, `BARCODE_NOT_FOUND`, `DOC_EXPIRED`, `COUNTRY_MISMATCH`, `DOC_TYPE_MISMATCH`, `DOC_DAMAGED`, `DOC_FAKE`, `DOC_ERROR`, `AUTO_UNVERIFIABLE`, `DOC_NOT_ANALYSED`, `DOC_NAME_ERROR`, `DOC_SURNAME_ERROR`, `DOC_EXPIRY_ERROR`, `DOC_DOB_ERROR`, `DOC_PERSONAL_NUMBER_ERROR`, `DOC_NUMBER_ERROR`, `DOC_DATE_OF_ISSUE_ERROR`, `DOC_SEX_ERROR`, `DOC_NATIONALITY_ERROR`. See Verification Statuses → Document Status Values for details.

Request Example

{
  "scanRef": "unique_scan_ref",
  "manualDocumentValidity": "DOC_ERROR",
  "manualFaceMatchResult": "FACE_MATCH"
}

A successful API call returns a response with a 200 status code.

Soft KYC Dummy Data

In the development environment, Soft KYC checks against the US_15 and UK databases use a set of predefined dummy people instead of a real database. Each dummy person returns the same results every time, so you can test how your integration handles each field status without sending real personal data. There is no separate endpoint. Send a regular Soft KYC request from your development environment. No real database check is run for US_15 or UK.

How Matching Works

If the submitted data matches a dummy person from the same database, that person’s predefined field statuses are returned.
If it matches none of them, every submitted field returns NO_DATA (NO_MATCH on UK).
On US_15, idNum takes the full 9-digit SSN or its last 4 digits. Both return the same result.

Validation

Input is validated the same way as in production:

US_15 requires firstName, lastName, and at least one of dob or idNum.
UK requires firstName, lastName, dateOfBirth and address.

Missing required fields or badly formatted values return the same error or INVALID status as in production.

US Dummy People (`US_15`)

Field	John Sample Butch	Manfred Weber	Cliff Hazard	John Escobar
`firstName`	John	Manfred	Cliff	John
`lastName`	Sample Butch	Weber	Hazard	Escobar
`dob`	1965-03-10	1972-07-14	1980-01-01	1949-12-01
`idNum` (SSN)	666000001 or 0001	666000002 or 0002	666000003 or 0003	666000004 or 0004
`address1`	100 Sample Street	200 Sample Street	300 Sample Street	400 Sample Street
`city`	San Jose	New York	Austin	Miami
`state`	CA	NY	TX	FL
`zip`	95128	10001	73301	33101
`phone`	+1 555 010 0001	+1 555 010 0002	+1 555 010 0003	+1 555 010 0004
`email`	john.butch@example.com	manfred.weber@example.com	cliff.hazard@example.com	john.escobar@example.com

UK Dummy People (`UK`)

Field	John Sample Butch	Manfred Weber	Cliff Hazard	John Escobar
`firstName`	John	Manfred	Cliff	John
`lastName`	Sample Butch	Weber	Hazard	Escobar
`dateOfBirth`	1965-03-10	1972-07-14	1980-01-01	1949-12-01
`address`	1 Sample Street, London, SW1A 1AA	2 Sample Street, London, SW1A 2AA	3 Sample Street, Manchester, M1 1AA	4 Sample Street, Birmingham, B1 1AA

Expected Field Statuses

The UK database only returns MATCH and NO_MATCH. Where a US_15 check returns PARTIAL_MATCH, the UK check returns MATCH. Where a US_15 check returns NO_DATA, the UK check returns NO_MATCH.

Person	`US_15`	`UK`
John Sample Butch	All fields `MATCH`	All fields `MATCH`
Manfred Weber	All fields `MATCH`	All fields `MATCH`
Cliff Hazard	`firstName`, `lastName`: `MATCH` `dob`: `PARTIAL_MATCH` `idNum`, `address1`, `zip`: `NO_MATCH`	`firstName`, `lastName`, `dateOfBirth`: `MATCH` `address`: `NO_MATCH`
John Escobar	`firstName`, `lastName`: `MATCH` All other fields: `NO_MATCH`	`firstName`, `lastName`: `MATCH` `dateOfBirth`, `address`: `NO_MATCH`
Anyone else	All submitted fields `NO_DATA`	All submitted fields `NO_MATCH`

AML Results and Overall Outcome

Each dummy person also has a predefined AML screening result and overall outcome. These are the same for US_15 and UK.

Person	AML screening	Overall outcome
John Sample Butch	No hits	Approved
Manfred Weber	PEP hit	Identity confirmed, AML suspected
Cliff Hazard	Adverse media hit	Doubtful identity, with adverse media
John Escobar	Sanctions hit	Rejected
Anyone else	—	Person not found

Start Here

ID Verification (KYC)

Business Verification (KYB)

AML Screening

Face Authentication

Age Estimation

Bank Card Verification

Fraud Prevention

Bank Verification

Social Screening

Going Live

Reference

Dummy Auto Results

Request Example

Response Example

Dummy Manual Result

Request Parameters

Request Example

Soft KYC Dummy Data

How Matching Works

Validation

US Dummy People (`US_15`)

UK Dummy People (`UK`)

Expected Field Statuses

AML Results and Overall Outcome

​Dummy Auto Results

​Request Example

​Response Example

​Dummy Manual Result

​Request Parameters

​Request Example

​Soft KYC Dummy Data

​How Matching Works

​Validation

​US Dummy People (US_15)

​UK Dummy People (UK)

​Expected Field Statuses

​AML Results and Overall Outcome

Dummy Auto Results

Request Example

Response Example

Dummy Manual Result

Request Parameters

Request Example

Soft KYC Dummy Data

How Matching Works

Validation

US Dummy People (`US_15`)

UK Dummy People (`UK`)

Expected Field Statuses

AML Results and Overall Outcome