Post on 03-Feb-2016
description
Page 1
Document on PMJJBY System Integration with Banks
LIC's system integration specification document.
(Version 2.0)
Annexure 1 - Technical Document for SFTP OR Data to be sent to LIC’s P&GS Unit
via e-mail.
Annexure 2 - Technical Document for Web services .
For any technical queries, please send mail to co_pgssdc@licindia.com or call us at 022-66598595 /
022-66598819
20th May 2015
Page 2
Annexure - 1
Technical Document for SFTP as well as Data to be sent to LIC’s P&GS Unit
under PMJJBY
1) Introduction
This document details the requirement of banks to use SFTP Interface of LIC for sending data
under Pradhan Mantri Jeevan Jyoti Yojana (PMJJBY). The file formats described hereunder be
used for sending data to P&GS Unit of LIC, which is servicing the policy. This document talks
about different file formats. This document will be used by the banks to send the data of
account-holders whose saving bank account has been auto-debited with premium. The bank will
credit the premium to LIC’s P&GS Unit Bank Account for a set of accountholders and then
provide the details of such account holders against the UTR/Ref. No. of payment to LIC.
In case the size of the data and control files is small (size less than or equal to 5 MB) , then the
data may be sent via e-mail to the concerned LIC P&GS unit with whom the bank has signed the
MOU.
2) Interface Specification details for PMJJBY
i) Registration with LIC using SFTP :
a) The Bank should send their request for using SFTP interface on co_pgssdc@licindia.com
with following information
b) LIC will convey the decision on the e-mail used for sending the request.
c) If LIC has allowed any bank to use this interface, the bank should send the following on the
above e-mail address :
(a) Bank’s IP address for white listing at LIC end.
(b) Bank’s E-Mail address to share user id.
(c) Declaration from the Bank in the same e-mail as to “The files with specified file
naming convention containing data in required format will be uploaded to LIC’s SFTP
Server and no other file like exe, shell, batch, jpeg,gif etc. will be uploaded”
d) Admin User of LIC will create SFTP user for the bank and will send the user id and
password, on the e-mail address provided by the Bank.
ii) Type of Files :
The banks will send LIC following files against a UTR/Ref. No. :
a) Input Data Files :
A text file (with file extension .csv) containing details of account holders for whom
premium has been credited to LIC’s bank Account. If the number of account holders, for
whom premium has been paid under a UTR No. go beyond 25,000 then separate data
file for each set of records up to 25000 per data file should be prepared. Each data file
will be treated as a batch of records. This will be a comma separated (delimited) file.
b) Input Control File :
A text file (with file extension .ctl) containing control record/s for the data in one or
Page 3
more than one Input Data Files. This file will be used to check receipt of entire data in
input data file/s against a UTR No. This will be a comma separated (delimited) file.
iii) File Naming Convention :
a) Input Data File :
<UTR/Ref. No. (22 digits)>-<Batch Id (3 digits)>-<Batch Date (8 digits)>.csv
Example : YESBR52015033100005075-001-20150601.CSV
Total length of Input Data File Name : 39 characters (inclusive of file extension)
All characters in file name should be in UPPER CASE only.
UTR/Ref. No. : 22 digit UTR No. or 16 digit Ref. no. or any other no. used for crediting
premium to LIC’s P&GS Unit Bank Account. This no. will be used by LIC for
confirming receipt of premium in bank statement and mapping the data of
account holders received. If this no. is less than 22 digits, it should be pre-
fixed with zeros.
Batch Id : It is a unique number for a set of records in a data file. It should be within
a range of 100 to 999. Each data file will have unique batch id. The batch
id should be a unique consecutive number for a batch date E.g. if data
files are created on 01/06/2015, then each data file will have unique
consecutive batch id on that day. The bank may repeat the batch id used
on 01/06/2015 on next day i.e. 02/06/2015 onwards.
Batch Date : The date on which batch has been prepared. The format will be YYYYMMDD.
E.g. If Batch date is 01/06/2015 then it should be 20150601
b) Input Control File :
<UTR/Ref No. (22 digits)>-<First Batch Id (3 digits)>-<Last Batch Id (3 digits)>-<Batch Date (8 digits)>.ctl
Example : YESBR52015033100005075-100-102-20150601.CTL
Total length of Input Data File Name : 43 characters (inclusive of file extension)
All characters in file name should be in UPPER CASE only.
UTR/Ref. No. : 22 digit UTR No. or 16 digit Ref. no. or any other no. used for crediting
premium to LIC’s P&GS Unit Bank Account. This no. will be used by LIC for
confirming receipt of premium in bank statement and mapping the data of
account holders received. If this no. is less than 22 digits, it should be pre-
fixed with zeros.
First Batch Id : Batch id of the first batch/file.
Last Batch Id : Batch id of the last batch/file.
Batch Date : The date on which batch has been prepared. The format will be YYYYMMDD.
Page 4
The bank may credit the premium to LIC’s bank account by following modes :
(1) By RTGS or NEFT, in which UTR No./Ref. No. is generated.
(2) By crediting LIC’s account in their bank, in case LIC is having bank account in the same
bank, which is going to upload the data. The bank will generate some unique no. to
identify the transaction.
The examples of file names for different mode of payments are given below :
Sr.
No.
Mode of
Payment
UTR/Ref. No. File Name
1 RTGS YESBR52015033100005075
(Alpha-numeric no. without
special characters)
YESBR52015033100005075-001-20150601.CSV
(Pre-fix zeros for UTR No. less than 22 digits)
2 NEFT CMS292330258
(Alpha-numeric no. without
special characters)
000000CP15123513510020-001-20150601.CSV
(Pre-fix zeros for UTR no. less than 22 digits)
3 A/C with
same bank
01/002003
(Alpha-numeric no. with
special characters)
0000000000000001002003-001-20150601.CSV
(Remove special characters keep only Alpha-
numeric characters)
iv) File size :
An input data file should contain maximum 25000 records. If the total number of records
against a UTR/Ref No. go beyond 25,000, then separate files containing records upto 25,000
per each file should be prepared. In that case, each input data file will be a separate batch
and will bear a unique consecutive number as batch id.
v) Case Example showing File Naming Convention :
A bank makes payment of premium via RTGS under UTR No. YESBR52015033100005075 for
60,000 records on 01/06/2015 and wants to send the data. It has to prepare three input data
files and one control file. The bank decides to use three consecutive unique no. 1,2 and 3 as
batch ids. The bank will have to use following information to name the files.
UTR No. : YESBR52015033100005075
Batch Ids : 100,101,102
Batch Date : 01/06/2015
The name of files will be as given below :
Input Data file names :
Sr.
No.
Input Data File Name No. of
records
1 YESBR52015033100005075-100-20150601.CSV 25,000
2 YESBR52015033100005075-101-20150601.CSV 25,000
3 YESBR52015033100005075-102-20150601.CSV 10,000
Total No. of Records 90,000
Input Control file name : YESBR52015033100005075-100-102-20150601.CTL
vi) Data Format :
Page 5
Input Control File :
Field Name Expected Data
Type
Data
Length
Data
Format
Mandatory
(M) /
Optional
(O)
Description
PolicyNo Numeric 10 M Master Policy No. issued by LIC
InputDataFileName Alpha-numeric
inclusive of
special character
39 M Name of Input Data File with
file extension as .csv
UTR_Ref_No Alpha-numeric 22 M 22 digit UTR No. or 16 digit Ref.
no. or any other no. used for
crediting premium to LIC’s
P&GS Unit Bank Account
UTR_Ref_Date Numeric 8 YYYYMMDD M Date of Credit in LIC’s Bank
Account
BatchId Numeric 3 M Batch Id - As explained earlier
BatchDate Numeric 8 YYYYMMDD M The date on which batch has
been prepared.
NoOfRecords Numeric 5 M Maximum upto 25,000
FileSize Numeric 10 M File size in bytes. The value
should be less than
1073741824 i.e. less than
10MB
Input Data File :
Field Name Expected Data
Type
Data
Length
Data
Format
Mandatory
(M) /
Optional
(O)
Description
BankIFSC Alpha-numeric 11 M IFSC of the bank
RuralUrban Alpha-numeric 10 O Metro / Urban/Rural/Semi -
Urban type of a/c holder
AccountHolderName Alpha-numeric 50 M Name of the a/c holder
Gender Alphabetic 1 M Gender of the a/c holder
M-Male;F-Female;
T-Transgender
DOB Numeric 8 YYYYMMDD M Date of Birth of a/c holder
BankAccountNo Alpha-numeric 30 M Bank Account Number of a/c
holder
BankCustomerId Alpha-numeric 30 M Unique Customer Ref Id as per
bank records
AadharNo Numeric 12 O Aadhar number of a/c holder
PanCardNo Alpha-numeric 10 O Pan Card Number of a/c holder
Pincode Numeric 6 M Pin code of the a/c holder
MobileNo Numeric 12 O Mobile Number of a/c holder
EmailId Alpha-numeric 50 O Email Id of a/c holder
DOA Numeric 8 YYYYMMDD M Date of opening the savings
account by the a/c holder
DOJ Numeric 8 YYYYMMDD M Date of Enrolment into the
PMJJBY scheme
NomineeName Alpha-numeric 50 O Name of the Nominee
NomineeRelation Numeric 2 O Relation of nominee to the a/c
holder (**)
NomineeAge Numeric 3 O Age of the nominee
AppointeeName Alpha-numeric 50 O Name of appointee , in case of
minor nominee
Page 6
**Nominee Relation codes to be used are as follows
Code Relation Code Relation
1 SELF 11 GRANDSON
2 WIFE 12 GRANDDAUGHTER
3 FATHER 13 GRANDFATHER
4 MOTHER 14 GRANDMOTHER
5 SON 15 BROTHER IN LAW
6 DAUGHTER 16 SISTER IN LAW
7 BROTHER 17 HUSBAND
8 SISTER 18 GUARDIAN
9 FATHER IN LAW 99 OTHERS
10 MOTHER IN LAW
vii) Sample data in files :
Input Control File :
Sample Data :
Field Name First Record Second Record
PolicyNo 9001000010 9001000010
InputDataFileName YESBR52015033100005075-
100-20150601.CSV
YESBR52015033100005075-
101-20150601.CSV
UTR_Ref_No YESBR52015033100005075 YESBR52015033100005075
UTR_Ref_Date 20150601 20150601
BatchId 100 101
BatchDate 20150601 20150601
NoOfRecords 25000 938
FileSize 7586523 281400
Sample Records to be prepared for sending two input data files with batch id 100 & 101
against single UTR/Ref. No.
9001000010,YESBR52015033100005075-100-20150601.CSV,YESBR52015033100005075,
20150601,100,20150601,25000,7586523
9001000010,YESBR52015033100005075-101-20150601.CSV,YESBR52015033100005075,
20150601,101,20150601,938,281400
Page 7
Input Data File :
Sample Data :
Field Name First Record
(With Nominee & Appointee
Details)
Second Record
(Without Nominee Details)
BankIFSC ABABAB12366 ABABAB12365
RuralUrban Urban
AccountHolderName Ramesh Tendulkar Asha Desai
Gender M F
DOB 19900504 19810610
BankAccountNo 3214596977 3214596978
BankCustomerId 123654 123656
AadharNo 689654789632 123654789632
PanCardNo AWEDF5897H STEDF5897P
Pincode 456987 456990
MobileNo 96385274123 8828527424
EmailId ABC@GMAIL.COM PQR@HOTMAIL.COM
DOA 20100512 20150507
DOJ 20150601 20150601
NomineeName RAJU1
NomineeRelation 1
NomineeAge 17
AppointeeName Miss Meena
Sample Record with nominee and appointee details :
The record has been wrapped into three lines. Hence it is one line record.
ABABAB12366,Urban,Ramesh Tendulkar ,M, 19900504,3214596977,123654,689654789632,
AWEDF5897H,456987,96385274123, ABC@GMAIL.COM,20100512, 20150601,RAJU1,
1,17,Miss Meena
Page 8
Sample Record without nominee details :
The record has been wrapped into three lines. Hence it is one line record.
ABABAB12365,,Asha Desai ,F,19810610,3214596978,123656,123654789632,
STEDF5897P,456990,8828527424, PQR@HOTMAIL.COM,20150507,20150601,,,,
viii) Timelines for using the Interface :
The banks may use the interface at the end of the day as per their conveyance.
Page 9
Annexure - 2
Technical Document for PMJJBY Member Enrolment using Webservices : The purpose of this document is to provide information regarding data exchange between LIC and
Banks, who will be Master Policy holders of LIC for Pradhan Mantri Jeevanjyoti Bima Yojana
(PMJJBY).
Reference to MOU between LIC & Bank and Rules of this Scheme is invited before reading
this document.
This document covers following area :
1. Process Flow
2. XML Formats of REQUEST and RESPONSE
3. Data Types of REQUEST and RESPONSE
1) Bank receives consent for coverage under PMJJBY from a saving bank account holder.
2) Bank confirms eligibility of the accountholder and issues the acknowledgement for consent.
3) Bank consolidates data of eligible accountholders at centralised server and sends it to LIC in
batches of maximum 50 records per batch, in the prescribed format.
4) For this, LIC has now hosted 3 web services (WS) viz WS1 , WS2 and WS4 .
Points 5 to 15 pertains to WS1 and WS2 and points 16 to 17 pertains to WS4.
5) Bank uses a web service hosted/exposed by LIC, called “Web Service 1” to upload a batch at
a time.
6) LIC receives a batch containing data.
7) LIC validates the data from the point of view of irregularities in the data structure and
format and checks for de-duplication of data based on IFSC , account number and the unique
customer id , by using the LIC’s database of members under PMJJBY.
8) LIC provides response under “Web Service 1”, by way of status against each record of
account holder. There can be three types of status viz. eligible account holders and records
of account holders with errors related to data format. The third type of error would be
outcome of some programming error in extraction of data at bank’s end. (The bank has to
ensure that they have received a response for a batch already sent, before sending the
next batch.)
( As requested by various banks, this operation of waiting for response from LIC no longer
exists).
9) Bank debits Rs.330/= from eligible account holders towards annual premium. Before
debiting the annual premium, bank must ensure that eligibility of the accountholder has
been confirmed using LIC’s Web Service 1.
10) Bank consolidates data of account holders, whose account has been debited with annual
premium.
Page
10
11) Bank credits total premium recovered from account holders (No. of eligible account holder
multiplied by Rs.289/=) to LIC’s Bank A/C as a single payment on daily basis. The premium
would be credited to Bank A/C of LIC’s designated P&GS Unit.
12) Bank consumes LIC’s second web service called “Web Service 2” to provide details of
account holders, whose premium has been credited to LIC’s Bank A/C. For uploading this
data, bank prepares data in batches of maximum 50 records per batch, in the prescribed
format. Each batch of records would be tagged with a unique "Cluster Id", the same UTR
No., Premium Credit Date, total no. of accountholders under all the batches and amount of
premium credited, for which total premium has been paid to LIC. Hence, the total of
account holders, whose data has been uploaded in all batches tagged with same UTR No.
and payment date, must be equal to the no. of account holders for whom premium has been
credited to LIC’s bank A/C. Any mismatch of data at this stage would generate complexity
at a later stage. Bank has also to ensure that the data of account holders for web service 2
must have passed through eligibility test under web service 1, otherwise the data will go
into errors.
Note : An example for the WS2 :
Lets assume that batch no 10001 comprising of 48 records , batch no 10002 comprising of
50 records were uploaded through WS1 and a response for the same was received, where
the 48 records of batch 10001 are valid and only 40 records of batch 10002 are valid.
The bank can now make a neft / rtgs payment for these 88 valid members. Once payment is
done, the bank can send a request on WS2 by making clusters of maximum 50 records
each(giving one unique cluster id for one lot), under the UTR number generated for the
payment of 88 records.
13) LIC provides positive response by way of acknowledgement, to the request through Web
service 2, for every cluster of data so received.
14) LIC merges the records received under all the clusters with same UTR No., Premium Credit
Date and tallies it with the total number of accountholders tagged.
15) LIC will map UTR No., Premium Credit date and total no. of account holders received under
Web Service 2 with UTR No., date and amount of credit as per Bank Statement of LIC’s
designated P&GS Unit, whose Bank A/C was credited with total premium amount. This
process will take place at LIC’s designated P&GS Unit.
16) In case, the bank decides to upload the data ONLY after the premium is debited from the
account holders' accounts , then the bank needs to consume only one web service viz. Web
Service 4. Here web service 4 will be a single service which clubs both web service 1 and web
service 2, wherein the bank will upload the members' data along with the payment details.
17) LIC will map UTR No., Premium Credit date and total no. of account holders received under
Web Service 4 with UTR No., date and amount of credit as per Bank Statement of LIC’s
designated P&GS Unit, whose Bank A/C was credited with total premium amount. This
process will take place at LIC’s designated P&GS Unit. The response to this service will be a
member wise status of the data with the same error codes and interpretations used in the
response of web service 1.
18) The data types and general conditions for the data are given in an annexure at the end of
the document.
Page
11
WEB SERVICE 1 To upload enrolled Member Data
XML Format of REQUEST to Web Service 1
<?xml version="1.0" encoding="iso-8859-1"?>
<PmjbyMemberDataRQ>
<PolicyData>
<PolicyDetails BankIdentifier="ABC Bank" PolicyNo="900789654" />
</PolicyData>
<MemberData>
<MemberDetails
BankIFSC="ABC20000001"
RuralUrban="RURAL"
AccountHolderName="XYZ JAHGD"
Gender="M"
DOB="19720701"
BankAccountNo="1236543RR123"
BankCustomerId="1236547"
AadharNo="201236547896"
PanCardNo="AYTRH8951W"
Pincode="421430"
MobileNo="9696874563"
EmailId="abdcdf@gmail.com"
DOA="20100512"
DOJ="20150601"
NomineeName="MAGAN KORHALE"
NomineeRelation="5"
NomineeAge="25"
AppointeeName="NULL"/>
<MemberDetails
BankIFSC="ABC20000001"
RuralUrban="RURAL"
AccountHolderName="AGDB HGFFG"
Gender="M"
DOB="19730523"
BankAccountNo="1236543RE564"
BankCustomerId="1987465547"
AadharNo="682147621424"
PanCardNo="REDFF8547N"
Pincode="452430"
MobileNo="9696852147"
EmailId="agsghsh@gmail.com"
DOA="19950104"
DOJ="20150601"
NomineeName="HSDDD DDREEWK"
Page
12
NomineeRelation="4"
NomineeAge="5"
AppointeeName="Mr SHAKDS FFF" />
</MemberData>
<SummaryDetails
WebServiceId="1"
BatchId="10001"
DateofSubmission="20150505"
TotalRecordsInBatch="2" />
</PmjbyMemberDataRQ >
XML Format of RESPONSE from Web Service 1 :
<?xml version="1.0" standalone="yes"?>
<PmjbyMemberDataRS>
<PolicyData>
<PolicyDetails BankIdentifier="ABC Bank" PolicyNo="900789654" />
</PolicyData>
<MemberData>
<MemberDetails
BankIFSC="ABC20000001"
BankAccountNo="1236543RR123"
BankCustomerId="1236547"
MemberStatus="E"
ErrorCode="0"/>
<MemberDetails
BankIFSC="ABC20000001"
BankAccountNo="1236543RE564"
BankCustomerId="1987465547"
MemberStatus="R"
ErrorCode="2"/>
</MemberData>
<SummaryDetails WebServiceId="1" LICResponseTypeId="1" LICReferenceId="101"
BatchId="10001" DateOfReceipt="20150505" TotalRecords="2"
TotalEligible="1" TotalDuplicates="0" TotalError="1"
Status="True" Description="Data Processed"/>
</PmjbyMemberDataRS>
Page
13
WEB SERVICE 2 (For Payment Particulars of PMJJBY Members who have passed eligibility test under
Web Service 1)
XML Format of REQUEST to Web Service 2
<?xml version="1.0" encoding="iso-8859-1"?>
<PmjbyPaymentDataRQ>
<PaymentData>
<PaymentDetails BankIdentifier="ABC Bank" PolicyNo="900789654"
UTRNumber="ABC4236997411115" PaymentDate="20150601" ClusterId="1001"/>
</PaymentData>
<MemberPaymentData>
<MemberPayDetails
BatchId="10001"
BankIFSC="ABC20000001"
BankAccountNo="1236543RR123"
BankCustomerId="123467" />
<MemberPayDetails
BatchId="10002"
BankIFSC="ABC20000001"
BankAccountNo="1236543RE564"
BankCustomerId="1987465547" />
</MemberPaymentData>
<SummaryDetails
WebServiceId="2"
DateofSubmission="20150601"
TotalRecords="2"
TotalAmount="578" />
</PmjbyPaymentDataRQ >
XML Format of RESPONSE from Web Service 2
<?xml version="1.0" standalone="yes"?>
<PmjbyPaymentDataStatusRS >
<PaymentData>
<PaymentDetails BankIdentifier="ABC Bank" PolicyNo="900789654"
UTRNumber="ABC4236997411115" ClusterId="1001"/>
</PaymentData>
<SummaryDetails WebServiceId="2" LICReferenceId="201" ClusterId="1001"
DateOfResponse="20150603" TotalRecords="2" Description="Received for processing"/>
</PmjbyPaymentDataStatusRS >
Page
14
WEB SERVICE 4 (To send enrolled members' data with payment particulars )
XML Format of REQUEST to Web Service 4
<?xml version="1.0" encoding="iso-8859-1"?>
<PmjjbyDataRQ>
<PolicyData>
<PolicyDetails BankIdentifier="ABC Bank" PolicyNo=" 900987456"
UTRNumber="ABC20150106115" UTRDate="20150601" />
</PolicyData>
<MemberData>
<MemberDetails
BankIFSC="ABC20000001"
RuralUrban="RURAL"
AccountHolderName="XYZ JAHGD"
Gender="M"
DOB="19720701"
BankAccountNo="1236543RR123"
BankCustomerId="1236547"
AadharNo="201236547896"
PanCardNo="AYTRH8951W"
Pincode="421430"
MobileNo="9696874563"
EmailId="abdcdf@gmail.com"
DOA="20100512"
DOJ="20150601"
NomineeName="MAGAN KORHALE"
NomineeRelation="5"
NomineeAge="25"
AppointeeName="NULL" />
<MemberDetails
BankIFSC="ABC20000001"
RuralUrban="RURAL"
AccountHolderName="ANBC JAHGD"
Gender="M"
DOB="19721101"
BankAccountNo="1236585KR123"
BankCustomerId="1234500"
AadharNo="201236588896"
PanCardNo="AYTRH8951W"
Pincode="421430"
MobileNo="9696874563"
EmailId="abdcdf@gmail.com"
DOA="20100512"
DOJ="20150601"
NomineeName="MAGAN KORHALE"
NomineeRelation="5"
NomineeAge="25"
AppointeeName="NULL" />
</MemberData>
<SummaryDetails
Page
15
WebServiceId="4" BatchId="1001" DateofSubmission="20150601"
TotalRecordsInBatch="2"/>
</PmjjbyDataRQ >
XML Format of RESPONSE from Web Service 4
<?xml version="1.0" standalone="yes"?>
<PmjjbyDataRS>
<PolicyData>
<PolicyDetails BankIdentifier="ABC Bank" PolicyNo="900789654" UTRNumber="
ABC20150106115"/>
</PolicyData>
<MemberData>
<MemberDetails
BankIFSC="ABC20000001"
BankAccountNo="1236543RR123"
BankCustomerId="1236547"
MemberStatus="E"
ErrorCode="0"/>
<MemberDetails
BankIFSC="ABC20000001"
BankAccountNo="1236543RE564"
BankCustomerId="1987465547"
MemberStatus="R"
ErrorCode="2"/>
</MemberData>
<SummaryDetails WebServiceId="4" LICReferenceId="101" BatchId="1001"
DateOfReceipt="20150605" TotalRecords="2" TotalEligible="1" TotalError="1"
Status="True" Description="Data Processed"/>
</PmjbyMemberDataRS>
Page
16
TEST ENVIRONMENT (UAT) for testing Web services :
1) WSDL : https://pgslink.licindia.in/PmJjbyWS1TestApp/PmJjbyWS?wsdl
2) Web service Name : PmJjbyWS
For Web Service 1 :
Web method : uploadPmjbyMemberData
Request web parameters used :
a) PGSRequestKey : value wil be pmjjby2015 (datatype : string)
b) PGSRequestMsg : value will be the xml data in string format as provided , in this
document.
Response : will be the xml data in string format as provided in this document.
For Web Service 2 :
Web method : uploadPmjjbyPayStatus
Request web parameters used :
a) PGSRequestKey : value will be pmjjby_pay2015 (datatype : string)
b) PGSRequestMsg : value will be the xml data in string format as provided , in this
document.
Response : will be the xml data in string format as provided in this document.
For Web Service 4 :
Web method : uploadPmjjbyFullData
Request web parameters used :
a) PGSRequestKey : value wil be pmjjby_full2015 (datatype : string)
b) PGSRequestMsg : value will be the xml data in string format as provided , in this
document.
Response : will be the xml data in string format as provided in this document.
Page
17
PRODUCTION ENVIRONMENT for LIVE data :
1) WSDL : https://pgslink.licindia.in/PmjjbyProjectApp/PmjjbyProjectWS?wsdl
2) Web service Name : PmjjbyProjectWS
For Web Service 1 :
Web method : uploadPmjbyMemberData
Request web parameters used :
a) PGSRequestKey : value wil be LIcpmJjby##15 (datatype : string)
b) PGSRequestMsg : value will be the xml data in string format as provided , in this
document.
Response : will be the xml data in string format as provided in this document.
For Web Service 2 :
Web method : uploadPmjjbyPayStatus
Request web parameters used :
a) PGSRequestKey : value will be LIcpmJjbyPay##15 (datatype : string)
b) PGSRequestMsg : value will be the xml data in string format as provided , in this
document.
Response : will be the xml data in string format as provided in this document.
For Web Service 4 :
Web method : uploadPmjjbyFullData
Request web parameters used :
a) PGSRequestKey : value wil be LIcpmJjbyFull##15 (datatype : string)
b) PGSRequestMsg : value will be the xml data in string format as provided , in this
document.
Page
18
Response : will be the xml data in string format as provided in this document.
ANNEXURE :
PolicyNo in the parent tag of all web services will be the master policy number allotted to the Bank
after signing the MOU. The bank can contact the LIC unit for this.
BankIdentifier in the parent tag will be the name of the bank limited to 60 characters.
Data Type of REQUEST to Web Service 1
Attribute Expected Data
Type
Expected
Data
Length
Data Format Mandatory
(M) /
Optional(O)
Description
BankIFSC Alpha-numeric 11 M IFSC of the bank
RuralUrban Alpha-numeric 10 O Metro / Urban/Rural/Semi -
Urban type of a/c holder
AccountHolderName Alpha-numeric 50 M Name of the a/c holder
Gender Alpha-numeric 1 M Gender of the a/c holder
DOB Numeric 8 YYYYMMDD M Date of Birth of a/c holder
BankAccountNo Alpha-numeric 30 M Bank Account Number of a/c
holder
BankCustomerId Alpha-numeric 30 M Unique Customer Ref Id as
per bank records
AadharNo Numeric 12 O Aadhar number of a/c
holder
PanCardNo Alpha-numeric 10 O Pan Card Number of a/c
holder
Pincode Numeric 6 M Pin code of the a/c holder
MobileNo Numeric 12 O Mobile Number of a/c
holder
EmailId Alpha-numeric 50 O Email Id of a/c holder
DOA Numeric 8 YYYYMMDD M Date of opening the savings
account by the a/c holder
DOJ Numeric 8 YYYYMMDD M Date of Enrolment into the
PMJJBY scheme
NomineeName Alpha-numeric 50 O Name of the Nominee
NomineeRelation Numeric 2 O Relation of nominee to the
a/c holder
NomineeAge Numeric 3 O Age of the nominee
AppointeeName Alpha-numeric 50 O Name of appointee , in case
of minor nominee
WebServiceId Numeric 1 M Value will be '1'
BatchId Numeric 10 M Unique ID generated by the
bank for each batch
DateofSubmission Numeric 8 YYYYMMDD M Date on which the batch is
sent to LIC
TotalRecordsInBatch Numeric 2 M Total records in the batch
Page
19
Data Type of REQUEST to Web Service 2
Attribute Expected Data
Type
Expected
Data
Length
Data Format Mandatory
(M) /
Optional(O)
Description
UTRNumber Alpha-numeric 22
M The UTR number generated
for the premium payment to
LIC
PaymentDate Numeric 8 YYYYMMDD M Date on which the payment
is sent to LIC
ClusterId Numeric 10
M Unique ID generated by the
bank for each lot being sent
under the UTR Number.
BatchId Numeric 10
M The batch number under
which the data of the
accountholder was sent
through WS1.
BankIFSC Alpha-numeric 11 M IFSC of the bank
BankAccountNo Alpha-numeric 30 M Bank Account Number of a/c
holder
BankCustomerId Alpha-numeric 30 M Unique Customer Ref Id as
per bank records
WebServiceId Numeric 1 M Value will be '2'
BatchId Numeric 10 M Unique ID generated by the
bank for each batch
DateofSubmission Numeric 8 YYYYMMDD M Date on which the batch is
sent to LIC
TotalRecords Numeric 2 M Total records in the batch
Page
20
Data Type of REQUEST to Web Service 4
Attribute Expected Data
Type
Expected
Data
Length
Data Format Mandatory
(M) /
Optional(O)
Description
UTRNumber Alpha-numeric 22
M The UTR number generated
for the premium payment to
LIC
UTRDate Numeric 8 YYYYMMDD M Date on which the payment
is sent to LIC
BankIFSC Alpha-numeric 11 M IFSC of the bank
RuralUrban Alpha-numeric 10 O Metro / Urban/Rural/Semi -
Urban type of a/c holder
AccountHolderName Alpha-numeric 50 M Name of the a/c holder
Gender Alpha-numeric 1 M Gender of the a/c holder
DOB Numeric 8 YYYYMMDD M Date of Birth of a/c holder
BankAccountNo Alpha-numeric 30 M Bank Account Number of a/c
holder
BankCustomerId Alpha-numeric 30 M Unique Customer Ref Id as
per bank records
AadharNo Numeric 12 O Aadhar number of a/c
holder
PanCardNo Alpha-numeric 10 O Pan Card Number of a/c
holder
Pincode Numeric 6 M Pin code of the a/c holder
MobileNo Numeric 12 O Mobile Number of a/c
holder
EmailId Alpha-numeric 50 O Email Id of a/c holder
DOA Numeric 8 YYYYMMDD M Date of opening the savings
account by the a/c holder
DOJ Numeric 8 YYYYMMDD M Date of Enrolment into the
PMJJBY scheme
NomineeName Alpha-numeric 50 O Name of the Nominee
NomineeRelation Numeric 2 O Relation of nominee to the
a/c holder
NomineeAge Numeric 3 O Age of the nominee
AppointeeName Alpha-numeric 50 O Name of appointee , in case
of minor nominee
WebServiceId Numeric 1 M Value will be '4'
BatchId Numeric 10 M Unique ID generated by the
bank for each batch
DateofSubmission Numeric 8 YYYYMMDD M Date on which the batch is
sent to LIC
TotalRecordsInBatch Numeric 2 M Total records in the batch
Page
21
Conditions of Validity for REQUEST to Web Service 1 and Web Service 4
Table of Invalid Error Codes for WS1 and WS4 :
Error Code Reason of Invalidity
1 IFSC code not given / Incorrect
2 Batch Id not given / is duplicate
3 Batch date not given / Incorrect
4 Account Holder's name is not given
5 Gender not given / not equal to (M , F , T)
6 Date of Birth not given / incorrect
7 Bank Account Number and Customer Id not given
8 Date of enrolment is not given
9 Incorrect Policy Number - Contact LIC
General Conditions for data under WS1 and WS4 :
� Expected values in "Gender" - M for Male ; F for Female ; T for Transgender
� There must be maximum 50 records per batch.
� No. of records in a batch / cluster must tally with value in "TotalRecords"
� The optional attributes must contain value NULL (for Character data type) or 0 (for numeric
data type) or 01/01/1900 (for date data type).
� The data must follow aforesaid data type/length/format as mentioned above whereas in
XML attributes, the same data will be presented in double quotes.
� The "BatchId" , "ClusterId" must be an unique number.
� The "PolicyNo" will be alloted by LIC to the bank after signing of MOU.
� " WebServiceId" must be 1 for WS1, 2 for WS2 and 4 for WS4.
� NomineeRelation must be as per the codes provided by LIC.
� When the LIC response is with Status="False", it should be interpreted with value in
attributes "LICResponseTypeId" and " Description".
� When the Status="True" then,
a) the value in the attribute MemberStatus will be "E" for eligible members, "D" for
de-duplication errors and "R" for Errors related to data format.
b) the value in the attribute of "ErrorCode" should be interpreted with the invalidity
codes mentioned in the "Table of Invalid Error Codes".
LIC Response Type ID Master :
LIC Response Type Id Description
1 Received for Processing
2 Error Received : (description of error)
3 XML Parsing error At (description of error)
Page
22
NOMINEE RELATIONSHIP CODES
Code Relation
1 SELF
2 WIFE
3 FATHER
4 MOTHER
5 SON
6 DAUGHTER
7 BROTHER
8 SISTER
9 FATHER IN LAW
10 MOTHER IN LAW
11 GRANDSON
12 GRANDDAUGHTER
13 GRANDFATHER
14 GRANDMOTHER
15 BROTHER IN LAW
16 SISTER IN LAW
17 HUSBAND
18 GUARDIAN
99 OTHERS