AEPS Error and Response Codes

Aadhaar Enabled Payment System

Error and Response Codes
Version 2 .3.1
 AEPS Error and Response Codes
Table of Contents
1. Introduction .................................................................................................................................................................................................................................................... 3

2. Final RespPay .................................................................................................................................................................................................................................................. 3

2.1 Result Attribute: ................................................................................................................................................................................................................................................... 4

2.2 ErrorCode Attribute: ............................................................................................................................................................................................................................................. 4
2.3 RespCode Attribute: ............................................................................................................................................................................................................................................6
.................................................................................................................................................................................................................................................................................... 4
3. Codes to be populated by PSP/Banks .............................................................................................................................................................................................................. 4

3.1 Response codes in RespPay Debit, RespPay Credit, RespPay Debit (Mandate) & RespChkTxn API: ...................................................................................................................7
3.2 Response codes in RespPayReversal API ..........................................................................................................................................................................................................12
3.3 Response codes in RespAuthDetail API .............................................................................................................................................................................................................13
3.4 Response codes sent by PSP in Meta API..........................................................................................................................................................................................................15
3.5 Response codes in Settlement ..........................................................................................................................................................................................................................17
3.6 Response codes for Mandate ............................................................................................................................................................................................................................17
3.6.1 RespAuthMandate ....................................................................................................................................................................................................................................17
3.6.2 RespMandate ............................................................................................................................................................................................................................................18
3.7 Response codes for PAN Validation ..................................................................................................................................................................................................................19
3.7.1 RespValCust ...............................................................................................................................................................................................................................................19
3.8 Response code for UPI Global ............................................................................................................................. .............................................................................................. 18
3.8.1 RespPay… .................................................................................................................................................................................................................................................. 18
4. Codes populated by UPI ............................................................................................................................................................................................................................... 19

4.1 Response codes populated by UP .................................................................................................................................................................................................................... 19

4.2 Response code from AEPS .................................................................................................................................................................................................................................21
4.3 UPI API message level Validations ....................................................................................................................................................................................................................23
 AEPS Error and Response Codes
4.3.1 API: ReqPay ...............................................................................................................................................................................................................................................24
4.3.2 API : RespAuthDetails ................................................................................................................................................................................................................................31
4.3.4 Meta API : ReqListPsp ................................................................................................................................................................................................................................39
4.3.5 Meta API : ReqListAccPvd ..........................................................................................................................................................................................................................39
4.3.6 Meta API : ReqListKeys ..............................................................................................................................................................................................................................40
4.3.7 Meta API : ReqListAccount .........................................................................................................................................................................................................................40
4.3.8 Meta API : ReqSetCre.................................................................................................................................................................................................................................41
4.3.9 Meta API : ReqChkTxn ...............................................................................................................................................................................................................................43
4.3.10 Few other Meta Msg Code ......................................................................................................................................................................................................................44
4.3.11 Mandate Codes .......................................................................................................................................................................................................................................49
4.3.12 Online Refund Codes ...............................................................................................................................................................................................................................53
4.3.13 PAN Validation ....................................................................................................................................................................................................................................... 51
4.3.14 UPI Global ....................................................................................................................................... ....................................................................................................... 51
4.4 Errors from UPI Service Layer ........................................................................................................................................................................................................................... 52
4.5 Errors from UPI 2.0 Service Layer .....................................................................................................................................................................................................................61
4.6 Errors and ACTN from UIDAI .............................................................................................................................................................................................................................63
4.6.1 ErrorCodes from UIDAI ..............................................................................................................................................................................................................................63
4.6.2 ACTN from UIDAI .......................................................................................................................................................................................................................................66
4.7 Errors from Common Library ............................................................................................................................................................................................................................68

1. Introduction
This document explains the usage of the final response sent by NPCI/Bank/UIDAI and about the error codes & response codes to be used in AEPS system.

2. Final Response
 AEPS Error and Response Codes
The status of the transaction can be known to the initiator/Remitter/Acquirer Bank in the final response message given by AEPS. AePS sends RespPay
finally to the Remitter/Acquirer bank for pay scenario respectively which gives the information about credit/debit for the particular transaction. The
following tag have to be looked upon to know the status of the transaction.

2.1 Result Attribute:

This will be populated by AEPS and describes the result of the transaction and it will have three values: SUCCESS | FAILURE | DEEMED
SUCCESS: Denotes the transaction is processed successfully.
FAILURE: Denotes the transaction is failed due to some reason. Reason for the failure will be populated with the appropriate error code in the
errCode field.
DEEMED: Denotes the transaction is deemed approved as the Beneficiary bank has timed out during Credit response.

2.2 ErrorCode Attribute:

This element describes the reason code for the failure. It will be populated if the transaction is failed. It explains the reason for the failure.
This will be populated by AEPS and the list is available in the document.

2.3 RespCode Attribute:

The code is populated by Bank in the response leg. This will show the reason for the transaction success/failure at the BANK end.

3. Codes to be populated by Banks

This section contains the codes that will be populated by the Banks.

3.1 Response codes in APIs:

The below response codes should be populated by the bank in case of any error. BANK has to populate the following response appropriately.
 AEPS Error and Response Codes
Back
UPI Error
Response Code Office Status
code
Code Description Decline Nature
00 00 00 A Approved -
03 U30 36 D Invalid Merchant Business Decline
05 U30 02 D DO NOT HONOR Business Decline
08 U30 IU D ISSUER UN-AVAILABLE Technical Decline
12 U30 01 D Invalid transaction Business Decline
13 U30 06 D INVALID AMOUNT Technical Decline
20 U30 07 D ISSUER DECLINE - UNSPECIFIED REASON Technical Decline
22 U68 41 D REVERSAL BY ACQUIRER TERMINAL Technical Decline
30 U30 18 D ACQUIRER FORMAT ERROR Technical Decline
51 U30 24 D INSUFFICIENT FUNDS Business Decline
52 U30 12 D INVALID ACCOUNT ( AADHAAR NOT LINKED ) Business Decline
53 U30 12 D NO SAVING ACCOUNT Business Decline
57 U30 30 D FREEZE/FROZEN ACCOUNT Business Decline
61 U30 14 D Exceeds withdrawal amount limit Business Decline
65 U30 15 D Exceeds withdrawal frequency limit Business Decline
68 U68 41 D REVERSAL BY ACQUIRER UPON TIMEOUT Technical Decline
69 U31 07 D Decline due to min. Valid signatory not available (SHG) Technical Decline
71 U30 71 A Deemed Acceptance Technical Decline
72 U30 72 D version not supported by Issuer Business Decline
76 U30 07 D Unable to locate BAV Technical Decline
 AEPS Error and Response Codes
90 U30 04 D Cut-off in process Technical Decline
91 U67 08 D ISSUER IS INOPERATIVE Technical Decline
92 U30 86 D ISSUER IDENTIFICATION INCORRECT Business Decline
94 U30 38 D Duplicate Transaction Technical Decline
96 U30 39 D System malfunction Technical Decline
UW U30 UW D TRANSACTION AMOUNT EXCEED LIMIT Business Decline
M6 U03 M6 D BANK SETTLEMENT LIMIT EXCEEDED Business Decline
M4 U30 M4 D NRE ACCOUNT Business Decline
M3 U30 M3 D DORMAT ACCOUNT Business Decline
78 - 78 D AePS debit transactions disabled Business Decline
59 - FR D Suspected fraud by issuer ( Issuer decline) Business Decline

Note: Back office Code “40” - REVERSAL BY NPCI NOT ACKNOWLEDGED BY ISSUER and “41” is REVERSAL BY ACQUIRER NOT ACKNOWLEDGED BY ISSUER will be TD

4. Codes populated by AEPS

These are the error codes populated by AEPS in various validation levels

4.1 Response codes populated by AEPS

The below response codes will be populated by AEPS in the final response pay.
 AEPS Error and Response Codes

4.1.1 API: ReqPay

Error Code Message Details Element/ TAG Name Attribute TD/BD
H02 VER NUMERIC/DECIMAL MIN LENGTH 1 MAX LENGTH 6 <Head/> ver TD
H03 TS MUST BE ISO_ZONE FORMAT ts TD
H06 MSGID MUST BE PRESENT MAXLENGTH 35 msgId TD
U17 PSP IS NOT REGISTERED orgId BD
U52 PSP ORGID NOT FOUND <Head/> orgId TD
BUSINESS VALIDATION: API EXPECTED TO HAVE <HEAD/> ELEMENT. ATTRIBUTE VER & TS WILL BE VALIDATED IF CONTAINS DATA. ATTRIBUTE
ORGID IS REQUIRED AND HAS TO BE REGISTERED WITH NPCI. ATTRIBUTE MSGID IS REQUIRED.
T01 TXN NOT PRESENT <Txn/> TD
T02 TXN.ID MUST BE PRESENT MAXLENGTH 35 id TD
T03 TXN.NOTE note TD
T04 TXN.REFID refId TD
T05 TXN REFURL refUrl TD
T06 TXN.TS MUST BE ISO_ZONE FORMAT ts TD
T07 TXN.TYPE MUST BE PRESENT/VALID type TD
TXN.ORGTNXID MUST BE PRESENT <for ChkTxn> TD
T08 orgTxnId
T09 TXN.ORGTNXID orgTxnId TD
TXN.ORGTNXID IS NOT APPLICABLE FOR THIS TYPE OF TD
T10 orgTxnId
TRANSACTION
T12 TXN.CUSTREF MUST BE PRESENT; LENGTH 12 custRef TD

<for CREDIT> TD
T13 TXN.SUBTYPE MUST BE PRESENT subType
 AEPS Error and Response Codes
T14 PURPOSE SHOULD BE PRESENT AND VALID purpose TD
IM0 INITIATIONMODE SHOULD BE PRESENT AND VALID initiationMode TD
IM5 PAYEE PSP DOES NOT SUPPORT VERSION 2.0 initiationMode BD
IM6 BANK/PSP IS NOT SUPPORTING VERSION 2.0 BD
BUSINESS VALIDATION: ELEMENT <TXN/> TAG IS MANDATORY AND HAS TO BE PROVIDED WITH VALID DATA. ATTRIBUTE ID & TYPE ARE
MANDATORY.
R01 PAYER NOT PRESENT < Payer/> TD
R02 PAYER.ADDR MUST BE VALID addr TD
R03 PAYER.NAME ALPHANUMERIC name TD
R04 PAYER.SEQNUM NUMERIC seqNum TD
R05 PAYER.TYPE MUST BE PRESENT/VALID type TD
R06 PAYER.CODE NUMERIC OF LENGTH 4 code TD

R10 Payee redundant or duplicate payment instrument account TD payer TD

BUSINESS VALIDATION: ELEMENT < PAYER /> TAG IS MANDATORY AND HAS TO BE PROVIDED WITH VALID DATA. ATTRIBUTE ADDR & TYPE
ARE MANDATORY. FOR ENTITY TYPE CODE IS MANDATORY. OTHER ATTRIBUTES WILL BE VALIDATED IN DATA GIVEN.
B01 PAYEES NOT PRESENT < Payee/> TD
B02 PAYEE NOT PRESENT TD
B05 PAYEE.NAME ALPHANUMERIC MINLENGTH 1 MAXLENGTH name TD
99
B06 PAYEE.TYPE MUST BE PRESENT/VALID type TD
B07 PAYEE.CODE NUMERIC OF LENGTH 4 Code TD
BUSINESS VALIDATION: ELEMENT < PAYEE /> TAG IS MANDATORY AND HAS TO BE PROVIDED WITH VALID DATA. ATTRIBUTE ADDR & TYPE
ARE MANDATORY. FOR ENTITY TYPE CODE IS MANDATORY. OTHER ATTRIBUTES WILL BE VALIDATED IN DATA GIVEN.
I01 PAYER INFO MUST BE PRESENT <Info/> TD
I02 PAYER .INFO.IDENTITY MUST BE PRESENT identity TD
PAYER.INFO.IDENTITY.TYPE MUST BE PRESENT TD
I03 type
PAYER/PAYEE .INFO.IDENTITY VERIFIEDNAME MUST BE TD
I04 PRESENT verifiedName
 AEPS Error and Response Codes
PAYER/PAYEE .INFO.RATING WHITELISTED TD
I05 verifiedAddress
BUSINESS VALIDATION: ELEMENT <INFO/> TAG IS MANDATORY AND WILL BE VALIDATED. INFO ELEMENT IS GIVEN ALL ATTRIBUTES ARE
REQUIRED. PAYER INCLUDED IN THE MESSAGES WILL COME DEPENDING UPON THEIR TYPE DURING VALIDATION.
D01 PAYER.DEVICE MUST BE PRESENT <Device/> TD

D02 PAYER. DEVICE.TAGS MUST BE PRESENT TD

D03 PAYER.TAG.DEVICE.NAME/VALUE MUST BE PRESENT name/value TD
D04 - D11 SAME VALIDATION MESSAGE BASED ON DEVICE TYPE TD
BUSINESS VALIDATION: ELEMENT < DEVICE /> TAG IS MANDATORY FOR PAYER AND PAYEE FOR RESPECTIVELY PAY AND COLLECT
TRANSACTION. IF DEVICE TAG IS GIVEN WHERE IT IS NOT MANDATORY IT WILL BE VALIDATED. PAYER/PAYEE INCLUDED IN THE MESSAGES
WILL COME DEPENDING UPON THEIR TYPE DURING VALIDATION.
A01 PAYER.AC MUST BE PRESENT < Ac/> TD
A02 PAYER.AC.ADDRTYPE MUST BE PRESENT addrType TD
A03 PAYER.AC.DETAIL MUST BE PRESENT detail TD
A04 PAYER.AC.NAME MUST BE PRESENT name TD
PAYER.AC.DETAIL.ACCOUNT MUST BE PRESENT OR NOT TD
A06
VALID
A07 PAYER.AC.DETAIL.MOBILE MUST BE PRESENT OR NOT VALID TD
A09 PAYER.AC.DETAIL.VALUE INCORRECT FORMAT <NAME> TD

BUSINESS VALIDATION: ELEMENT < AC /> TAG IS MANDATORY FOR PAYER AND PAYEE FOR RESPECTIVELY PAY TRANSACTION.
IF AC TAG IS GIVEN WHERE IT IS NOT MANDATORY IT WILL BE VALIDATED. AC VALIDATION IS DONE BASED ON ACCOUNT or MOBILE. PAYER
INCLUDED IN THE MESSAGES WILL COME DEPENDING UPON THEIR TYPE DURING VALIDATION.

C01 PAYER.CREDS NOT PRESENT <Creds/> TD

C02 PAYER/PAYEE .CREDS.CRED MUST BE PRESENT TD

BUSINESS VALIDATION: ELEMENT < CREDS /> TAG IS MANDATORY FOR PAYER FOR PAY TRANSACTION. IF CREDS TAG IS GIVEN WHERE IT IS
NOT MANDATORY IT WILL BE VALIDATED. PAYER INCLUDED IN THE MESSAGES WILL COME DEPENDING UPON THEIR TYPE DURING
VALIDATION.
V01 PAYER/PAYEE. AMOUNT MUST BE PRESENT < Amount/> TD
 AEPS Error and Response Codes
V02 PAYER/PAYEE .AMOUNT.CUR MUST BE PRESENT curr TD
PAYER/PAYEE.AMOUNT.VALUE MUST BE WITHIN 18 DIGITS TD
V03 INCLUDING TWO DECIMAL value

V06 PAYEE AMOUNT CANNOT BE CHANGED TD

M01 PAYEE.AMOUNT.CUR MUST BE CONSISTENT TD
M02 PAYEE.AMOUNT.CUR IS INVALID TD
M03/M05 PAYER & PAYEE TOTAL AMOUNT NOT MATCHING TD
BUSINESS VALIDATION: ELEMENT < AMOUNT /> TAG IS MANDATORY FOR BOTH PAYER & PAYEE. IT CHECKS CURRENCY & AMOUNT MATCHING
FOR PAYER & PAYEE. PAYER/PAYEE INCLUDED IN THE MESSAGES WILL COME DEPENDING UPON THEIR TYPE DURING VALIDATION.

INSTITUTION TAG SHOULD BE PRESENT IF TD

PI0 INITIATIONMODE=12 <Institution />
(FIR)
PI1 PAYER.INSTITUTION.TYPE MUST BE PRESENT AMONG type TD
MTO|BANK
PI2 PAYER.INSTITUTION.ROUTE MUST BE PRESENT AMONG route TD
MTSS|RDA
PI3 PAYER.INSTITUTION.NAME MUST BE PRESENT <Name/> TD

PAYER.INSTITUTION.NAME.VALUE MUST BE VALID TD

PI4 value

PAYER.INSTITUTION.NAME.ACNUM MUST BE MUST BE VALID TD

PI5 acNum

PI6 PAYER.INSTITUTION.PURPOSE MUST BE VALID <Purpose/> TD

PAYER.INSTITUTION.PURPOSE.CODE MUST BE VALID TD

PI7 code

PI8 PAYER.INSTITUTION.ORIGINATOR MUST BE PRESENT <Originator/> TD

PAYER.INSTITUTION.ORIGINATOR.NAME MUST BE TD
PI9 PRESENT,MINLENGTH 1 MAXLENGTH 50 name

PAYER.INSTITUTION.ORIGINATOR.REFNO MUST BE TD
PJ1 PRESENT,MINLENGTH 1 MAXLENGTH 35 refNo
 AEPS Error and Response Codes
PJ2 PAYER.INSTITUTION.ORIGINATOR.ADDRESS MUST BE <Address/> TD
PRESENT
PAYER.INSTITUTION.ORIGINATOR.ADDRESS.LOCATION MUST TD
PJ3 BE PRESENT,MINLENGTH 1 MAXLENGTH 40 location

PJ4 PAYER.INSTITUTION.BENEFICIARY MUST BE PRESENT <Beneficiary/> TD

PAYER.INSTITUTION.BENEFICIARY.NAME MUST BE TD
PJ5 PRESENT,MINLENGTH 1 MAXLENGTH 50 name

PAYER.INSTITUTION.ORIGINATOR.TYPE MUST BE PRESENT, TD

PJ6 INDIVIDUAL|COMPANY <Originator/> type

PAYER.INSTITUTION.ORIGINATOR.ADDRESS.CITY MUST BE TD
PJ7 PRESENT,MINLENGTH 1 MAXLENGTH 100 <Address/> city

PAYER.INSTITUTION.ORIGINATOR.ADDRESS.COUNTRY MUST TD
PJ8 BE PRESENT,MINLENGTH 1 MAXLENGTH 100 country

PAYER.INSTITUTION.ORIGINATOR.ADDRESS.GEOCODE MUST TD
PJ9 BE PRESENT geocode

PAYER.INSTITUTION.PURPOSE.NOTE MUST BE TD
PJ0 PRESENT,MINLENGTH 1 MAXLENGTH 50 <Purpose/> note

INSTITUTION TAG SHOULD NOT BE PRESENT IF TD

PK0 INITIATIONMODE OTHER THAN 12 <Instituition/>

BUSINESS VALIDATION: ELEMENT <INSTITUTION/> TAG IS NOT MANDATORY FOR BOTH PAYER. IT GIVES INSTITUTION DETAILS
OF NRE|NRO TRANSACTIONS.

4.1.2 API : RespPay

Error Code Message Details Element/ TAG Name Attribute TD/BD
H02 VER NUMERIC/DECIMAL Ver TD
H03 TS MUST BE ISO_ZONE FORMAT ts TD
H06 MSGID MUST BE PRESENT msgId TD
U17 PSP IS NOT REGISTERED orgId TD
U52 PSP ORGID NOT FOUND <Head/> orgId TD
 AEPS Error and Response Codes
BUSINESS VALIDATION: API EXPECTED TO HAVE <HEAD/> ELEMENT. ATTRIBUTE VER & TS WILL BE VALIDATED IF CONTAINS DATA. ATTRIBUTE
ORGID IS REQUIRED AND HAS TO BE REGISTERED WITH NPCI. ATTRIBUTE MSGID IS REQUIRED.
T01 TXN NOT PRESENT <Txn/> TD
T02 TXN.ID MUST BE PRESENT id TD
T03 TXN.NOTE ALPHANUMERIC note TD
T04 TXN.REFID ALPHANUMERIC refId TD
T06 TXN.TS MUST BE ISO_ZONE FORMAT ts TD
T07 TXN.TYPE MUST BE PRESENT/VALID type TD
T13 TXN.SUBTYPE MUST BE PRESENT <Ref/> subtype TD
T14 TXN.PURPOSE MUST BE PRESENT/VALID purpose TD
IM0 INITIATIONMODE SHOULD BE PRESENT AND VALID initiationMode TD
BUSINESS VALIDATION: ELEMENT <TXN/> TAG IS MANDATORY AND HAS TO BE PROVIDED WITH VALID DATA. ATTRIBUTE ID & TYPE ARE
MANDATORY. OTHER ATTRIBUTES WILL BE VALIDATED IN DATA GIVEN. TXN ELEMENT HAS RISKSCORES ELEMENTS REFERRED INSIDE.
E01 <RESP> MUST BE PRESENT < Resp/> TD

E02 RESP.REQMSGID MUST BE PRESENT MAXLENGTH 35 reqMsgId TD

RESP.RESULT MUST BE PRESENT TD
E03 result
ALPHANUMERIC MIN LENGTH 1 MAX LENGTH 20
E04 RESP.ERRORCODE MUST BE PRESENT errCode TD
E05 RESP.ERRORCODE SHOULD NOT BE PRESENT errCode TD
E06 RESP.ERRORCODE MUST BE SUCCESS OR FAILURE result TD
E07 TYPE IS MANDATORY & ALPHANUMERIC <Ref/> type TD
E08 SEQNUM IS MANDATORY & NUMERIC seqNum TD
E09 ADDR IS MANDATORY & ALPHANUMERIC addr TD
E10 SETTLEAMOUNT IS MANDATORY & DECIMAL settAmount TD
E11 SETTLECURRENCY IS MANDATORY & TEXT settCurrency TD
E12 APPROVALNUM IS MANDATORY & TEXT approvalNum TD
E13 RESPCODE IS MANDATORY & ALPHANUMERIC AND MUST BE respCode TD
VALID
 AEPS Error and Response Codes
E14 SETTLEAMOUNT OF FAILURE CASES CANNOT BE MORE THAN settleAmount TD
ZERO
E15 INVALID RESPONSE CODE FOR THIS API respCode TD
E16 REF.ACNUM MUST BE OF MINLENGTH 1 MAXLENGTH 16 acNum BD
E17 REF.CODE MUST BE OF LENGTH 4 code TD
E18 REF.IFSC MUST BE OF LENGTH 11 ifsc BD
E19 REF.ACCTYPE MUST BE PRESENT accType TD
BUSINESS VALIDATION: ELEMENT < RESP /> TAG IS MANDATORY. ATTRIBUTE MSGID AND RESULT ARE MANDATORY.
ERRCODE IS MANDATORY IF RESULT IS FAILURE. REF TAG IS REFERED INSIDE RESP. IF REF ELEMENT IS GIVEN THEN THIS TAG WILL BE
VALIDATED. ALL REF ATTRIBUTES ARE MANDATORY.

4.1.3 Meta API : ReqChkTxn

Error Code Message Details Element/ TAG Name Attribute TD/BD

U17 PSP IS NOT REGISTERED <Head/> orgId BD
U52 PSP ORGID NOT FOUND <Head/> orgId TD
Z02 VER NUMERIC/DECIMAL MIN LENGTH 1 MAX LENGTH 6 <Head/> ver TD
Z03 TS MUST BE ISO_ZONE FORMAT <Head/> Ts TD
Z06 MSGID MUST BE PRESENT MAXLENGTH 35 <Head/> msgId TD
BUSINESS VALIDATION: API EXPECTED TO HAVE <HEAD/> ELEMENT. ATTRIBUTE VER & TS WILL BE VALIDATED IF CONTAINS DATA.
ATTRIBUTE ORGID IS REQUIRED AND HAS TO BE REGISTERED WITH NPCI. ATTRIBUTE MSGID IS REQUIRED.
X01 TXN NOT PRESENT <Txn/> TD
X02 TXN.ID MUST BE PRESENT id TD
X03 TXN.NOTE ALPHANUMERIC note TD
X04 TXN.REFID ALPHANUMERIC refId TD
X06 TXN.TS MUST BE ISO_ZONE FORMAT ts TD
X07 TXN.TYPE MUST BE PRESENT/VALID type TD
X08 TXN.ORGTXNDATE MUST BE PRESENT orgTxnDate TD
 AEPS Error and Response Codes
X09 TXN.ORGTXNDATE SHOULD BE WITHIN 90 DAYS orgTxnDate TD
IM0 INITIATIONMODE SHOULD BE PRESENT AND VALID initiationMode TD
BUSINESS VALIDATION: ELEMENT <TXN/> TAG IS MANDATORY. ATTRIBUTE ID & TYPE ARE MANDATORY. OTHER ATTRIBUTES WILL BE
VALIDATED IN DATA GIVEN.

4.1.4 Few other Meta Msg code

Error Code Message Details Element/ TAG Name Attribute TD/BD

G01 HBTMSG MUST BE PRESENT <HbtMsg/> verifiedAddress TD
G02 HBTMSG.TYPE MUST BE PRESENT/VALID TD
G03 VALUE NOT VALID FOR HBTMSG.TYPE TD
G04 VALUE NOT VALID FOR HBTMSGRESP.RESULT <RespHbt/> name,value TD
G05 VALUE NOT VALID FOR HBTMSGRESP.ERRORCODE TD
G25 CERTIFICATE NOT FOUND TD
G26 SIGNATURE ERROR TD
G27 SIGNATURE MISMATCH TD

UB7 OTHER BANK/PSP IS NOT SUPPORTED IN 2.0 VERSION TD

UH1 HEADER VERSION MISMATCHED TD
UV2 REQRESP VERSION MISMATCHED TD

4.2 Errors from UPI Service Layer

 AEPS Error and Response Codes
API Error Back Description TD/BD
Code Office
Code

U01 07 THE REQUEST IS DUPLICATE TD

U02 07 AMOUNT CAP IS EXCEEDED BD
U03 M6 NET DEBIT CAP IS EXCEEDED BD
U04 07 REQUEST IS NOT FOUND TD
U05 07 FORMATION IS NOT PROPER TD
U06 07 TRANSACTION ID IS MISMATCHED TD
U07 07 VALIDATION ERROR TD
U08 07 SYSTEM EXCEPTION TD
U09 08 REQBALTIME OUT TD
U10 07 ILLEGAL OPERATION BD
U11 07 CREDENTIALS IS NOT PRESENT BD
U12 07 AMOUNT OR CURRENCY MISMATCH TD
U13 08 EXTERNAL ERROR TD
U14 07 ENCRYPTION ERROR TD
U15 07 CHECKSUM FAILED TD
U16 59 RISK THRESHOLD EXCEEDED BD
U17 07 PSP IS NOT REGISTERED BD
U26 07 PSP REQUEST CREDIT PAY ACKNOWLEDGEMENT IS NOT TD
RECEIVED
U27 07 NO RESPONSE FROM PSP TD
U28 IU PSP IS NOT REGISTERED
U31 07 CREDIT HAS BEEN FAILED NA
U46 07 REQUEST CREDIT IS NOT FOUND TD
U48 07 TRANSACTION ID IS NOT PRESENT TD
U49 07 REQUEST MESSAGE ID IS NOT PRESENT TD
 AEPS Error and Response Codes
U53 IU PSP REQUEST PAY DEBIT ACKNOWLEDGEMENT NOT RECEIVED TD
U55 07 MESSAGE INTEGRITY FAILED DUE TO ORGID MISMATCH TD
U57 07 PAYEE AMOUNT DIFFERS FROM ORIGINAL REQUEST TD
U68 07 CREDIT TIMEOUT TD
U78 IU BENEFICIARY BANK OFFLINE TD
U82 07 READ TIMEOUT IN REQPAY CREDIT TD
U84 07 BENEFICIARY BANK DEEMED CHECK DECLINE TD
U85 08 CONNECTION TIMEOUT IN REQPAY TD
U88 07 CONNECTION TIMEOUT IN REQPAY CREDIT TD
U89 07 BENEFICIARY BANK THROTTLING DECLINE TD
U91 07 BENEFICIARY BANK DEEMED HIGH RESPONSE TIME CHECK TD
DECLINE
UZ2 07 PSP FORCED OFFLINE TD
UP3 07 PSP SCHEDULED OFFLINE TD
UP4 07 PAYER FORCED OFFLINE TD
UP5 07 PAYEE FORCED OFFLINE TD
UP6 07 REMITTER FORCED OFFLINE TD
UZ3 07 BENEFICIARY FORCED OFFLINE TD
UP7 07 PAYER SCHEDULED OFFLINE TD
UP8 07 PAYEE SCHEDULED OFFLINE TD
UP9 07 REMITTER SCHEDULED OFFLINE TD
UQ1 07 BENEFICIARY SCHEDULED OFFLINE TD
U80 07 PSP BANK NON RESPONSIVE TD
U86 07 REMITTER BANK NON RESPONSIVE TD
U89 T1 BENEFICIARY BANK NON RESPONSIVE (Throttle Decline) TD
U81 T4 REMITTER BANK DA OUTGOING COUNT (Throttle Decline) TD
U84 T3 BENEFICIARY BANK DA OUTGOING COUNT (Throttle Decline) TD
 AEPS Error and Response Codes
U90 07 REMITTER BANK DA RESPONSE TIME TD
U91 T2 BENEFICIARY BANK DA RESPONSE TIME (Throttle Decline) TD
U94 07 PAYEE PSP THROTTLE DECLINE TD
S99 S9 GRACEFUL DECLINE TD
M16 77 Declined under Risk monitoring BD

5. UIDAI Declines

Description
Response Receipt
Code/BO UIDAI Error Required
Code Code Status (Yes/No)

00 - APPROVED A Yes

KK 317 NUMBER OF BIOMNETRIC MODALITIES SHOULD NOT EXCEED 2 D Yes

KP 531 INVALID SUB AUA code D Yes

KS 318 BFD TRANSACTION SHOULD NOT CONTAIN OTHER IN INPUT D Yes

Yes
AADHAAR LOCKED BY AADHAAR NUMBER HOLDER FOR ALL
KT 331 MODALITIES AUTHENTICATIONS D

KU 332 AADHAAR NUMBER USAGE IS BLOCKED BY AADHAAR NUMBER HOLDER D Yes

KV 591 BFD USAGE NOT ALLOWED AS PER LICENSE D Yes

KW 914 Face alone is not allowed as biometric modality D Yes

KX 915 Face auth is not allowed for this age of resident D Yes
 AEPS Error and Response Codes
KY 916 Invalid face Image format in input D Yes

KZ 917 Invalid face capture type D Yes

M4 - NRE ACCOUNT D Yes

M6 - LIMIT EXCEEDED D Yes

OM 517 EXPIRED VID IN INPUT D Yes

UA 700 INVALID DEMOGRAPHIC DATA D No

UB 710 MISSING PI DATA AS SPECIFIED IN USES D No

UC 720 MISSING PA DATA AS SPECIFIED IN USES D No

UD 730 MISSING PIN DATA AS SPECIFIED IN USES D No

UE 999 UNKNOWN ERROR D No

UF 740 MISSING OTP DATA AS SPECIFIED IN USES D No

UG 800 INVALID BIOMETRIC DATA D Yes

UH 810 MISSING BIOMETRIC DATA SPECIFIED IN USES D No

UI - UIDAI TIME OUT D Yes

UJ 721 Missing PFA data specified in USES D No

UK 820 MISSING VALUE FOR BT ATT IN USES ELEMENT D No

UL 821 INVALID VALUE IN BT ATT IN USES ELEMENT D No

UM 901 NO AUTH FACTORS FOUND IN AUTH REQUEST D No

UN 902 INVALID DOB VALUE IN PI ELEMENT D No

 AEPS Error and Response Codes
UO 910 INVALID MV VALUE IN PI ELEMENT D No

UP 911 INVALID MV VALUE IN PFA ELEMENT D No

UQ 912 INVALID MS VALUE D No

UR 913 BOTH PA AND PFA ARE PRESENT D No

US 930 TECH ERROR 1-RELATED TO ABIS INTERACTION D No

UT 931 TECH ERROR 2- UID DB SERVER DOWN D Yes

UU 932 TECH ERROR 3 - XML ERROR D No

UV 980 UNSUPPORTED OPTION D No

UW - TRANSACTION AMOUNT EXCEED LIMIT D Yes

UY 511 INVALID PID XML FORMAT D No

UX - REQUEST OLDER THAN 24 hours D No

UZ 940 UNAUTHORIZED ASA CHANNEL D Yes

U0 941 UNSPECIFIED ASA CHANNEL D Yes

U1 100 PI BASIC ATTR DEMOGRAPHIC DID NOT MATCH D No

U2 200 PI ADDRESS ATTR DEMOGRAPHIC NOT MATCH D Yes

U3 300 BIOMETRIC DATA DID NOT MATCH D Yes

U4 500 INVALID ENCRYPTION D No

U5 510 INVALID XML FORMAT D No

U6 520 INVALID DEVICE/Invalid tid value D Yes

 AEPS Error and Response Codes
U7 530 INVALID AUTHENTICATOR CODE D Yes

U8 540 INVALID Auth XML VERSION D No

U9 550 INVALID USES ELEMENT ATTRIBUTES D No

VA 571 PIN RETRIES RESET D Yes

VB 572 INVALID BIOMETRIC POSITION D Yes

VC 573 PI USAGE NOT ALLOWED AS PER LICENSE D No

VD 574 PA USAGE NOT ALLOWED AS PER LICENSE D No

VE 575 PFA USAGE NOT ALLOWED AS PER LICENSE D No

VF 576 FMR USAGE NOT ALLOWED AS PER LICENSE D No

VG 577 FIR USAGE NOT ALLOWED AS PER LICENSE D No

VH 578 IIR USAGE NOT ALLOWED AS PER LICENSE D No

VI 579 OTP USAGE NOT ALLOWED AS PER LICENSE D No

VJ 580 PIN USAGE NOT ALLOWED AS PER LICENSE D No

VK 581 FUZZY USAGE NOT ALLOWED AS PER LICENSE D No

VL 582 LOCAL LANGUAGE USAGE NOT ALLOWED AS PER D No

VM 934 TECHNICAL ERROR D No

VN 935 TECHNICAL ERROR D No

VO 936 TECHNICAL ERROR D No

VP 937 TECHNICAL ERROR D No

 AEPS Error and Response Codes
VQ 938 TECHNICAL ERROR D No

VR 939 TECHNICAL ERROR D No

VS 811 Missing Biometric data in UIDAI CIDR D Yes

VT 501 Invalid certificate identifier in “ci” attribute of “Skey” D No

VU 502 INVALID ENCRYPTION OF PID D No

VV 503 INVALID ENCRYPTION OF HMAC D No

VW 542 AUA NOT AUTHORIZED FOR ASA D Yes

VX 543 SUB-AUA NOT ASSOCIATED WITH "AUA" D Yes

VY 541 INVALID PID XML VERSION D No

VZ 311 Duplicate Irises used D No

V0 561 REQUEST EXPIRED D Yes

V1 562 INVALID TIME STAMP D No

V2 563 Duplicate Request D No

V3 564 HMAC VALIDATION FAILED D No

V4 565 AUA licence key expired D Yes

V5 566 ASA licence key expired D Yes

V6 567 INVALID INPUT D No

V7 568 UNSUPPORTD LANGUAGE D No

V8 569 DIGITAL SIGNATURE VERIFICATION FAILED D No

 AEPS Error and Response Codes
V9 570 INVALID KEY INFO IN DIGITAL SIGNATURE D No

W0 312 FMR & FIR IN 1 TXN D No

W1 313 MORE THAN ONE FINGER IN SINGLE FIR D No

W2 314 FMR/FIR EXCEED 10 D No

W3 315 IIR SHDNT EXCD 2 D No

W4 504 SESSION KEY EXPIRE D No

W5 812 BEST FNGR DTCTN NOT DONE D No

W6 310 DUPLICATE FING USED D No

W7 584 INVALD PIN CODE D No

W8 585 INVALID GEO CODE D No

W9 400 OTP VALIDATION FAILD D Yes

WA 330 BIOMETRICS LOCKED D Yes

WB 316 Number of FID should not exceed 1 D Yes

WC 402 “txn” value did not match with “txn” value used in Request OTP API D Yes

WD 512 Invalid resident consent in “rc” attribute of “Auth” D Yes

WE 551 Invalid “tid” value. D Yes

WF 524 Invalid mi code under Meta tag D Yes

WG 555 rdsId is invalid and not part of certification registry D Yes

WH 556 rdsVer is invalid and not part of certification registry D Yes

 AEPS Error and Response Codes
WI 527 Invalid mc code under Meta tag D Yes

WJ 553 Registered devices currently not supported D Yes

WK 554 Public devices are not allowed to be used D Yes

WL 586 FID usage not allowed as per license D Yes

WM 587 Name space not allowed D Yes

WN 588 Registered device not allowed as per license D Yes

WO 590 Public device not allowed as per license D Yes

WP 822 Invalid value in the “bs” attribute of “Bio” element within “Pid” D Yes

WQ 950 OTP store related technical error D Yes

WR 951 Biometric lock related technical error D Yes

WS 995 Aadhaar suspended by competent authority D Yes

WT 996 Aadhaar cancelled D Yes

WU 557 dpId is invalid and not part of certification registry D Yes

WV 558 Invalid dih D Yes

WW 552 WADH validation fail in RD D Yes

WX 559 Device Certificate has expired D Yes

WY 560 DP Master Certificate has expired D Yes

WZ 933 Technical error D Yes

 AEPS Error and Response Codes
X1 505 SYNC KEY USE NOT ALLOWED D No

X2 521 INVALID FNGR DEVICE D Yes

X3 522 INVALID IRIS DEVICE D Yes

Aadhaar suspended (Aadhaar is not in authenticatable status. Actn Code: A311
Your Aadhaar is suspended. Please approach nearest UIDAI Regional Office with
X7 997 valid POI Document. D Yes

X8 998 AADHAR NO DOSENT EXIST IN CIDR D Yes

XA 513 Invalid Protobuf Format D Yes

Maximum number of attempts for OTP match is exceeded or OTP is not generated.
XB 403 Please generate a fresh OTP and try to authenticate again D Yes

XC 516 Invalid/Non Decryptable ANCS Token in input. Use a correct ANCS token. D Yes

XD 518 ANCS Token in input is already used or expired D Yes

Inappropriate ANCS token used. This means that the ANCS token used is not
XE 519 associated with the AUA or with the transaction ID. D Yes

VID is not yet generated. To use specific services like UID lock which require VID
XF 532 to be pre generated, please generate a VID before using service. D Yes

XG 592 Device blocked for more than allowed error percentage D Yes

XH 593 Device blocked for more than allowed velocity D Yes

Face alone is of allowed as biometric modality. You should send face along with
XI 914 another biometric modality like Finger or IRIS or OTP. D Yes
 AEPS Error and Response Codes
XJ 915 Face auth is not allowed for this age of resident D Yes

XK 916 Invalid face Image format in input D Yes

XL 917 Invalid face capture type D Yes

Y1 528 Device key rotation related issue D Yes

Z1 514 Invalid UID token in input D Yes

Z2 515 Invalid VID Number in input D Yes

Response UIDAI Error Back-Office

Code Code (ARCS) Code Description
F0 320 F0 FMR+FIR not present.
Mismatch in “posh” attributes mentioned for FMR and FIR. Value of “posh” if mentioned
F1 333 F1 other than “default” (when both FMR and FIR is used) should have the same finger
position for FMR as that of corresponding FIR.
Mismatch in count of FMR and FIR. I.e. Number of FMRs and FIRs should be same
F2 334 F2
inside PID.
TOTP usage is not allowed for this Aadhaar holder. Please install m-Aadhaar and
F3 430 F3
generate TOTP.
F4 K-516 F4 Invalid ANCS Token used.
F5 K-519 F5 Invalid Authenticator Code.
Z2 K-514 Z2 Invalid UID Token Used.
KQ K-515 KQ Invalid VID used.
OM K-517 OM VID used is expired.
KR K-553 KR KUA License key Expired.
E1 K-571 E1 Technical error while signing the eKYC response.
KL K-955 KL Technical Failure internal to UIDAI
KN K-956 KN Technical error while generating the PDF file.
O1 110 O1 Aadhaar number does not have email ID.
O2 111 O2 Aadhaar number does not have mobile number.
O3 112 O3 Aadhaar number does not have both email ID and mobile number.
 AEPS Error and Response Codes
OI 113 OI Aadhaar Number doesn’t have verified email ID.
OJ 114 OJ Aadhaar Number doesn’t have verified Mobile Number.
OK 115 OK Aadhaar Number doesn’t have verified email and Mobile.
MV 522 MV Invalid “type” attribute.
OL 952 OL OTP Flooding error.
Exceeded Maximum OTP generation Limit. Try After some time, OTP Generation will be
OX 953 OX
blocked for certain duration after exceeding the Max OTP generation limit.
F8 589 F8 FMR+FIR not allowed as per the License
F6 K-546 F6 Invalid value for “pfr” attribute
F7 - F7 Invalid bt for FMR/FIR
F11 101 FC TxnId not present, Missing transaction id
F12 102 FD Duplicate txnId (Reserved)
F13 103 FE Incorrect PidOption’s env value. Please check
F15 120 FF Invalid value for fCount (Reserved)
F16 130 FG Invalid value for iType (Reserved)
F17 140 FH Invalid value for iCount (Reserved)
F19 160 FI Invalid value for timeout
F20 170 FJ Invalid value for posh (Reserved)
F21 190 FK Invalid value for pidFormat
F23 210 FL Protobuf format not supported
F25 731 FM User abort.
F26 732 FN Capture failed. Please move to better lighting.
F27 733 FO Capture failed. Please improve lighting and hold still.
F28 734 FP Capture failed. Please check background.
F29 735 FQ User Capture failed. Please check background.
F30 736 FR Capture failed. Please blink during capture.
F31 737 FS Capture failed. Please improve lighting.
F32 738 FT Capture failed. Please focus towards the camera.
F33 850 FU Unsupported application version. Please upgrade.
F34 860 FV Application seems to be corrupted. Please reinstall.
F35 861 FW Application seems to be corrupted. Please lock your bootloader.
F36 862 FX Application seems to be corrupted. Please restore to factory ROM.
 AEPS Error and Response Codes
Application seems to be corrupted. Please lock your bootloader and restore to factory
F37 863 FY
ROM.
F38 864 FZ Application seems to be corrupted. Please retry after {n} hrs.
F39 870 to 879 LA Application is not allowed to run on this device - {xxx}
F40 880 L2 Application is not allowed, please upgrade Google play services.
F41 881 L3 Unsupported android version. Please upgrade.
F42 890 L4 Application is not allowed to run on this device due to low resources.
F43 891 L5 This functionality not supported below Android 8 OS version.
F44 892 L6 Application will not work on this device as USB Debugging is enabled.
F47 903 L7 Failed to connect with server (Timed Out).
F48 904 L8 Failed due to network related issues.
F49 9701 to 9999 L9 FaceRD app error {xxxx}

Aadhaar deactivated due to deceased status.

FA 994 FA Actn Code: A601 - To re-activate Aadhaar, please visit Aadhaar Centre and update
biometrics or approach regional office of UIDAI.
F51 594 FB Device in blocked state