CRIF HIGH MARK

February 2024 Release Notes

PAN Service Update from NSDL

Internal
 Release Notes
PAN Service Update from NSDL

Table of Content

Business Need .............................................................................................................................................. 3

Solution......................................................................................................................................................... 3
Impacted Areas............................................................................................................................................. 7
Targeted Customers ..................................................................................................................................... 7
Frequently Asked Questions (FAQ).............................................................................................................. 7

2
Internal
 Release Notes
PAN Service Update from NSDL

Business Need

As per directives of Income Tax Department, NSDL has updated API service to make few changes in API of
PAN verification service.

Previously, PAN was mandatory to execute PAN verification service. Now Name and DOB is also
mandatory along with PAN to execute PAN verification service. The response from NSDL will be Y or N for
Name match instead of returning name on PAN. Also, the response from NSDL would have Y and N for
DOB match as well.

Solution
CHM will make changes at their end in the verification products (Idencheck 2.0, Fusion 1.0 and 2.0)
response the details of which has been described in the subsequent sections below.

1. Handling of PAN verification service for Idencheck 2.0 (Request Structure)

a. Changes in Idencheck 2.0 for API Mode: In Idencheck 2.0 request structure currently only
PAN is mandatory field to fetch response. However now Name and DOB are also mandatory
fields and should be provided along with PAN to fetch response from bureau. Impacted
request fields in the request are mentioned below.
• <NAME1> which is present within <APPLICANT-NAME> tag
• <PAN> which is present within <IDS> tag
• <DOB-DATE> which is present within <DOB> tag
b. Changes in Idencheck 2.0 for Web Single Mode: Presently on web single channel whenever
PAN verification checkbox is selected to execute PAN verification service, only PAN field is
highlighted which indicates it as a mandatory field. However, now as Name and DOB has also
become a mandatory field, both these fields will be highlighted as well. Below is the
screenshot for reference.

3
Internal
 Release Notes
PAN Service Update from NSDL

c. Changes in Idencheck 2.0 for Web Bulk Mode: In the bulk input format for Idencheck 2.0
only PAN is a required field to execute PAN verification service but now onwards along with
PAN, Name and DOB must be provided to execute PAN verification service in bulk mode.

2. Handling of PAN verification service for Idencheck 2.0 (Response Structure)

a. Changes in Idencheck 2.0 for API Mode: There is minor change in the overall response
structure of Idencheck 2.0.
The change is that we have modified the <REMARK> tag with new remark as PAN
Status|Name Match Flag|DOB Match Flag basis the response received from NSDL.
Previously, we used to give remark basis PAN provided in the request and returning Name
basis name match.
Refer to the TO-BE screenshot below for reference.

b. Changes in Idencheck 2.0 for Web Single Mode: On HTML/PDF, currently in the remark
field, remark shown is basis PAN provided in the request and returning Name basis name
match. However now we have updated the remark as PAN Status|Name Match Flag|DOB
Match Flag based on the response received from NSDL.
Refer to the TO-BE screenshot below for reference.

c. Changes in Idencheck 2.0 for Web Bulk Mode: Currently in the bulk response for Idencheck
2.0, remark in the REMARK_1 field is populated basis PAN provided in the request and
returning Name basis name match.

4
Internal
 Release Notes
PAN Service Update from NSDL

Now we will update the REMARK_1 value as PAN Status;Name Match Flag;DOB Match Flag
based on the response received from NSDL.
Refer to the TO-BE screenshot below for reference.

3. Handling of PAN verification service for Fusion 1.0 and 2.0 (Request Structure)

a. Changes in Fusion 1.0 and 2.0 for Web Bulk Mode: In the bulk input format for Fusion 1.0
and 2.0, only PAN is a required field to execute PAN verification service but now onwards
along with PAN, Name and DOB must be provided to execute PAN verification service in bulk
mode.
b. Changes in Fusion 2.0 for API Mode: In fusion 2.0 request structure currently only PAN is
mandatory field to fetch response. However now Name and DOB are also mandatory fields
and should be provided along with PAN to fetch response from bureau. Impacted request
fields in the request are mentioned below.
• <NAME> which is present within <APPLICANT-SEGMENT> tag
• <PAN> which is present within <APPLICANT-SEGMENT> tag
• <DOB-DATE> which is present within <APPLICANT-SEGMENT> tag
c. Changes in Fusion 2.0 for Web Single Mode: Presently on web single channel whenever PAN
verification checkbox is selected to execute PAN verification service, only PAN field is
highlighted which indicates it as a mandatory field. However, now as Name and DOB has also
become a mandatory field, both these fields will be highlighted as well.
Below is the screenshot for reference.

5
Internal
 Release Notes
PAN Service Update from NSDL

4. Handling of PAN verification service for Fusion 1.0 and 2.0 (Response Structure)
a. Changes in Fusion 1.0 and 2.0 for API Mode: There is minor change in the overall XML
response structure of fusion 1.0 and 2.0. The only change is that we have modified the
<SCORE-DESCRIPTION> tag as PAN Status|Name Match Flag|DOB Match Flag basis the
response received from NSDL. Also, we are modifying the <REMARK> tag as PAN, Name
Match Flag.
Previously, we used to give score description and remark basis PAN provided in the request
and returning Name basis name match.
Below is the screenshot for reference.

Similarly, on the HTML/PDF response of fusion 2.0 we will modify the Score-Description field
as PAN Status|Name Match Flag|DOB Match Flag basis the response received from NSDL.
Also, we are modifying the Remarks field as PAN, Name Match Flag. Previously, we used to
give score description and remark basis PAN provided in the request and returning Name basis
name match.
Below is the screenshot for reference.

b. Changes in Fusion 2.0 for Web Single Mode: The HTML/PDF response will be similar to the
one described in point (a).
c. Changes in Fusion 1.0 and 2.0 for Web Bulk Mode: On bulk response, we are modifying
SCORE-DESCRIPTION and REMARK-1 columns as PAN Status;Name Match Flag;DOB Match
and PAN, Name Match Flag respectively based on the response received from NSDL.
Refer to the TO-BE screenshot below for reference.

6
Internal
 Release Notes
PAN Service Update from NSDL

5. Changes in L1 validations error response

a. For Idencheck 2.0 and Fusion 1.0 and 2.0: Since Name and DOB are mandatory fields along
with PAN, we will introduce L1 validation error message in case name and DOB are not
provided in the request.
The validation error message will be – “Name is required for PAN verification” and “DOB is
required for PAN verification”.
Error code in API mode and web bulk mode to be displayed as “NAME_BLANK” and
“DOB_BLANK”.
These validation messages will be displayed in the existing error tags/field across all channels.

6. Changes in consumer reconciliation report: The consumer reconciliation report will display the
REMARK1 column value as PAN Status;Name Match Flag;DOB Match only when PAN service is
executed and service type pricing model is opted.

Impacted Areas
Verification CIRs that includes Idencheck 2.0, Fusion 1.0 and 2.0. Details are mentioned above.

Targeted Customers
All customers fetching report of subscribed products through all channels and modes.

Frequently Asked Questions (FAQ)

1. Will there be any changes in other request and response fields/tags other than the ones
mentioned?

No. There is no change in the other request and response fields/tags other than the ones already
highlighted.

2. Will there be any impact on PAN score range due to changes at NSDL?

No, there will be no impact on PAN score range. The PAN score range remains the same from 0 to
100.

7
Internal