Document Version: 1.3.

13

YES BANK Ltd.

Domestic Payments API
Technical Specifications
Document Version: 1.3.13

Page 1 of 69
Document Version: 1.3.13

Table of Contents
Section 1 ......................................................................................................................................................... 5
Purpose of Web service............................................................................................................................ 5
Authentication/Security ......................................................................................................................... 5
2 Way SSL.................................................................................................................................................. 5
API Portal Links ....................................................................................................................................... 6
API URL: ................................................................................................................................................... 6
Web service Interface Overview: ........................................................................................................... 7
Process Note.............................................................................................................................................. 7
Transfer Type wise Processing ............................................................................................................... 7
IMPS transactions................................................................................................................................. 8
NEFT Transactions ............................................................................................................................... 8
RTGS transactions ................................................................................................................................ 9
Pending Nodal and Refund Payments............................................................................................ 11
GST Payments..................................................................................................................................... 11
Pennydrop (Beneficiary Name check) Service ............................................................................... 11
Non English text restriction .............................................................................................................. 11
Section 2: Interface Methods ..................................................................................................................... 12
Method Name: GetStatus ...................................................................................................................... 12
Method Name: fund-confirmation ...................................................................................................... 12
Method Name: domestic-payments .................................................................................................... 14
Request Structure for Nodal .................................................................................................................. 15
Request Structure for GST ...................................................................................................................... 16
Request Structure for REFUND............................................................................................................. 17
Method Name: payment-details .......................................................................................................... 25
Circuit Breaker........................................................................................................................................ 30
Benificiary LEI ............................................................................................................................................ 32
Section 3: Response Codes ........................................................................................................................ 34
Domestic-payments Response Codes ................................................................................................. 34
Payment-details -Response Codes ....................................................................................................... 34
Section 4: Schema Level validations ........................................................................................................ 67
HTTP Errors ............................................................................................................................................ 67
Section 5: Escalation Matrix ...................................................................................................................... 68

Page 2 of 69
Document Version: 1.3.13

# Comment Changes by Date

1 Domestic Payments API Document Christine Issac 28th-Jan-2020

1.2 Updates as per business and onboarding team Wilma Cardoza 2nd May 2020
comments
1.3 New Error codes added Wilma Cardoza 26th May 2021

1.3.4 Updates for error codes nse:500, http 500, nse:404, IMPS Megha Chauhan 7th Feb 2022
% lakh
1.3.5 BeneficiaryLEI Nisha Atmaramani 28March2022

1.3.6 Error code flex:E18 description corrected to Invalid Nisha Atmaramani Aug 8th 2022
destination bank
1.3.7 npci:E52 – Beneficiary Not Acceptable / ns:E307 Nisha Atmaramani OCT 18th 2022
- Current Transaction Time not within Window Period.
/ New Domain URL / Bene name acceptable characters

1.3.8 npci:E61- Transfer Amount Exceeds Limit Mayank Derashri Mar 2nd 2023
1.3.9 Error code ns:E400 recommended action Mayank Derashri May 11th 2023
corrected

Network and Technical Issue L1 Level name

updated
1.3.10 Update status code ACCEPTED Mayank Derashri June 30th 2023
Error code ns:E506- Error While Executing
Datatbase Call

Error code ns:E507- Error While Fetching Data

From Backend For Beneficiary Code

CA Signed Certificate requirement and Static IP

whitelisting updated

YBL Logo Updated

New IMPS Error Codes updated

Error code update: npci:E12 ,npci:E01 ,npci:E96

,npci:E13 ,npci:E22 ,npci:E20 ,npci:E94 ,npci:E92
,npci:EM0 ,npci:EMN ,npci:EM8 ,npci:EM6
,npci:E65 , npci:EEXT_RSP9011, npci:EE npci:EUB
npci:EE15 npci:EXF,npci:E78,npci:EXC
npci:E59,npci:EXD,npci:E39,npci:E24
npci:E17

Recommended Action Note updated for ns:E500,

ns:E404
1.3.11
Error code update: npci:EU78, npci:EU84 and
Mayank Derashri July 6th 2023
npci:EU88

Page 3 of 69
Document Version: 1.3.13

1.3.12 Error code update: npci:EUQ1, npci:EU26, npci:EU16, Mayank Derashri August 22nd 2023
npci:EUZ3, npci:EM1

Recommended Action updated for errorcodes-

npci:E91, npci:E02, npci:E08, npci:ECE, npci:EMP,
September 4th
npci:E01, npci:E20, npci:EM0, npci:EMT, npci:EUB,
npci:EE15, npci:EXF, npci:EXC, npci:E39 2023

Recommended Action Note added for error codes

ns:E5XX October 12th 2023
1.3.13 Mayank Derashri November 6th,
Error code update: npci:EEXT_RSP9901 2023

Page 4 of 69
Document Version: 1.3.13

Section 1
Purpose of Web service

The Payments Web Service is a comprehensive money transfer service that can be used to remit
money to beneficiaries through various payment settlement systems. The three web service calls
available under this API service are Payments details, Fund confirmation and Domestic Payments.
This service supports GST payments as well.

This service works on Asynchronous mode for transaction processing. The status of transactions shall
be checked by calling the Domestic Payments details API after a preset time duration.

Authentication/Security

2 Way SSL is the recommended connectivity method available for accessing the service.

2 Way SSL

This will involve SSL Certificate exchange and trust between Bank and Corporate and customer‘s
Static IP whitelisting by the bank.

SSL Certificates - These will be used to establish a peer-to-peer trust relationship. By means of these
certificates all incoming and outgoing XML messages will be encrypted/decrypted and sent by way
of HTTPS for efficiency.

For accessing the API in UAT and Production - 2048 bit root, sha2 256 bit encryption, certificate from
a Class 3 CA and TLS1.2 version and Static IP will be required.

Static IP whitelisting will be needed both in UAT and Production

LDAP Authentication – One time User ID and Password will be created and sent via Email on the
Authorized Email ID of each Corporate during PRODUCTION Phase of on Boarding. This User ID
and Password are to be passed with each request to the Web service to authenticate the Corporate.

For UAT use the below credentials:

UserId: testclient
Password will be shared separately on email

API Authentication – Client Id and Secret are (generated one time, during API Subscription process
on API Portal hosted on locations mentioned in next section) are to be provided with each request
with below parameters in HTTP headers.
X-IBM-Client-Id
X-IBM-Client Secret

Page 5 of 69
Document Version: 1.3.13

API Portal Links

For subscribing to the API in UAT Environment – https://uatdeveloper.yesbank.in

For subscribing to the API in Production Environment – https://developer.yesbank.in

Test Environment:

White list IPs – Partner Public IP has to be white listed to allow test requests.

Web Service Description

The Web Service description can be accessed at the following url:

Test Environment:

API Name: Domestic Payments

Plan Name: Domestic Payments

API URL:

https://uatskyway.yesbank.in/app/uat/api-banking/domestic-payments
https://uatskyway.yesbank.in/app/uat/api-banking/fund-confirmation
https://uatskyway.yesbank.in/app/uat/api-banking/payment-details

Production Environment:

API Name:

Plan Name:

URL :

https://skyway.yesbank.in/app/live/api-banking/domestic-payments
https://skyway.yesbank.in/app/live/api-banking/fund-confirmation
https://skyway.yesbank.in/app/live/api-banking/payment-details

Page 6 of 69
Document Version: 1.3.13

Web service Interface Overview:

Category Method Name Purpose

Post domestic-payments To submit Asynchronous payment order
transaction. Such transfers will be
acknowledged instantly and processed later.

Post payment-details Retrieve status for transaction previously

submitted

Post fund-confirmation Retrieved the funding account balance.

Process Note

Customers may initiate transfer request for payment transaction to Yes Bank Ltd (YBL) using various
transaction type like IMPS, NEFT, RTGS, APBS, FT or ANY (When ‘ANY’ is passed, the transfer type will be
determined by the bank system after the request is received).

Following Decision Grid indicates the transaction behavior based on the Request Type, Amount and applicable
cut off for the mode of payment.

IMPS
Request Yes Bank RTGS Cut
Amount Enabled IMPS? NEFT? RTGS? FT?
Type Beneficiary? off
beneficiary?
ANY N <5L Y Y
ANY N <5L N Y
Within cut Not
ANY N >2L Y
off Applicable
Outside
ANY N >2L Y
cut off
ANY Y No check No check No check Y
NEFT No check Y
IMPS Y Y
IMPS
IMPS N
Reject
Within Cut
RTGS >2L Y
off
Outside
RTGS >2L Reject
Cut off
FT Y

**GST Payments coming in with transfer type ‘ANY’ will be routed through ‘NEFT’ or ‘RTGS’, whichever is
best suited.

Transfer Type wise Processing

Page 7 of 69
Document Version: 1.3.13

Transactions can be raised for NEFT, RTGS, IMPS, A2A or ANY transfer types. These
transactions will go through the above statuses mentioned in Transaction status section

IMPS transactions

The amount is debited from the remitter and a request is sent to NPCI which in turn
forwards it to the beneficiary bank. Within 90 seconds, NPCI sends back the response to the
remitter bank which in turn is intimated to CORPORATE as a transaction status response.
Any transactions above Rs. 5 L will be rejected due to IMPS transaction amount limit being
Rs. 5 L.
Status of IMPS Transaction Meaning What to Do

SettlementCompleted Transaction has been

successful
SettlementInProcess Final status of IMPS Check the status by calling payment-details
transaction is not known API after T+1 (day). If the Final Status is not
from the beneficiary available even after T+1, kindly raise a dispute
bank/NPCI with the bank support team for investigation
Pending Transaction is in process Check the status by calling payment-details
API before refunding/reinitiating the
transaction. If the Final Status is not available
even after one working day, kindly raise a
dispute with the bank support team for
investigation
FAILED Transaction has failed Kindly check the error code sent in the
response basis which appropriate action is to
be taken internally or with the beneficiary
before refunding / reinitiating the transaction.
Retry the transaction post correction if
required. If Corporate account if debited, the
same would be credited instantly or once
reconciliation is completed.

NEFT Transactions

The transactions will be bunched as a batch and processed at pre-defined time intervals as
per RBI settlement cycle. The transactions are processed as per RBI NEFT window between 8
AM and 7 PM. Transactions initiated after 7 PM will be processed after EOD processing. Also
NEFT transaction will not be allowed on RTGS Holidays, 2nd and 4th Saturday and all
Sundays and it will be processed on next working day. It is beneficial if transactions are sent
till 6:00 PM. The remitter bank debits the account and sends the transaction request further
The beneficiary bank has to send back a negative confirmation in the next 2 cycles(hours),
however this SLA is not always met. As the confirmations are received, the status is updated
to either completed or failed.

Page 8 of 69
Document Version: 1.3.13

Status of NEFT Transaction Meaning What to Do

SettlementInProcess Transaction has been sent to Check the first status by calling getStatus API after 20-

beneficiary bank. 30 min and second status after 3 Hours.If

the
transaction has been sent in last batch
of NEFT, check the status on next
working day. If the final status is not
available for 2 working days, raise a
dispute with the bank support team for
investigation. If transaction has been
posted after NEFT cut-off time then
check the status on next working day
SettlementCompleted Transaction is successful
Pending Transaction is in process Check the status by calling payment-
details API If the Final Status is not
available even after one working day,
kindly raise a dispute with the bank
support team for investigation
SettlementReversed Beneficiary bank has not The transaction has been returned by
accepted the transaction the beneficiary bank. Kindly check
with the beneficiary for exact
discrepancy. Retry the transaction post
correction if required. Remitter’s
account, if debited would be credited
back. Will also consider for
transactions returned by Beneficiary
Bank after confirmation from
NPCI/sfms
FAILED Transaction has failed Kindly check the error code sent in the
response basis which appropriate
action is to be taken internally or with
the beneficiary before
refunding/reinitiating the transaction.
Retry the transaction post correction if
required. If Corporate account if
debited, the same would be credited
instantly or once reconciliation is
completed.

RTGS transactions

The transactions are processed as per RBI RTGS window between 8 AM and 6 PM. The
remitter bank debits the debit account of the customer and sends the transaction request to
RBI for further processing. As per agreed process the beneficiary bank has to send back the
acknowledgement in next 15 minutes. As and when the confirmations are received, the
status is updated to either SettlementCompleted or FAILED. Kindly initiate a payment-
details call after 15 minutes or alternatively the status will be posted by the bank to your
web service in case you have opted for push status service.

RTGS transactions sent after RTGS Cut-off time would be rejected and not rescheduled.
Page 9 of 69
Document Version: 1.3.13

Status of RTGS Transaction Meaning What to Do

SettlementInProcess Transaction has been sent to Check the first status by calling getStatus API

beneficiary bank. after 20-30 min and second status after 3 Hours.
If the final status is not available
raise a dispute with the bank
support team for investigation
SettlementCompleted Transaction has been successful
Pending Transaction is in process Check the status by calling
payment-details API after 30
minutes. If the Final Status is not
available, raise a dispute with the
bank for investigation
FAILED Transaction has failed Kindly check the error code sent in
the response basis which
appropriate action is to be taken
internally or with the beneficiary
before refunding / reinitiating the
transaction. Retry the transaction
post correction if required. If
Corporate account if debited, the
same would be credited instantly
or once reconciliation is completed.

Duplicate Check

For incoming requests, when a request is received, the UniqueRequestNo is checked against existing requests for
a duration of last 90 days. Data more than 90 days old will be migrated:-

1. if there is already a successful transaction, the request is rejected as duplicate

2. if there is in ‘pending’ status, the request is rejected as ‘pending’
3. if there is already a failed transaction, the request is accepted as ‘retry’ attempt

To summarize, for the following statuses received in payment-details call, money will never reach the
beneficiary, so customers, if required may initiate the transaction again after taking necessary action.

1. FAILED
2. SettlementReversed

For the following status' received in payment-details call, money may reach the beneficiary, so customers
should use payment-details API till final status is available, or may reach out to the bank support staff post
above mentioned TAT for further investigation.

1. SettlementInProcess
2. Pending

Page 10 of 69
Document Version: 1.3.13

Pending Nodal and Refund Payments

As per RBI regulations Nodal Transfers can be made only to registered beneficiaries. The Customers who have
an agreement with the bank for Nodal Transfers shall initiate the payment with Purpose Code shared with
them by the bank and pass pre-registered Beneficiary Code in the request instead of Beneficiary Detail. Service
will allow Nodal transfers only to beneficiaries already registered with the bank and/or Refund Transfers
(passed with beneficiary details) to any beneficiary. Please get in touch with the Bank team to understand
Beneficiary Registration Process through relevant APIs.

(Refer to Sample Domestic Payments Request for Nodal Payments)

GST Payments
As per RBI regulations GST Transfers can be made using CPIN generated on GST Portal. Corporates can make
their GST payments by passing their CPIN in beneficiaryAccountNo with purposeCode as ‘GST’.

GST Payments coming in with transfer type ‘ANY’ will be routed through ‘NEFT’ or ‘RTGS’, whichever is
best suited.

(Refer to Sample Domestic Payments Request for GST Payments)

Pennydrop (Beneficiary Name check) Service

Corporate customers will be able to verify the beneficiary details (i.e. Name of the Account Holder with the
Beneficiary Bank) prior to carrying out the actual transactions and will allow to send transactions only to verified
beneficiaries for the remittances via IMPS as transfer type.
Corporate Customer will have to initiate FT2 domestic payment service with ₹ 1.00 (one) or more to YesBank.
Corporate Customer will initiate payment details API to get details of the beneficiary.
Yes Bank can provide the name of the account holder with the beneficiary bank only if the beneficiary bank
provides the name as a part of response for IMPS.

Sample request and response for Pennydrop

Non English text restriction

Domestic Payments service will accept only English text in the API request and response. Any Non
English text will be rejected at the schema level itself.

Sample non English values: ప వర మ , Евгений Евгеньевич Румянцев

Page 11 of 69
Document Version: 1.3.13

Section 2: Interface Methods

Method Name: GetStatus
 It is recommended to call Status API after all Payment API request calls.
 Please do not check status instantly/simultaneously after sending Payment request as is not a
recommended process.
 We recommend to check the status by calling payment-details API according to mentioned duration for
respective pay mode .
o IMPS/ FT : Status check should be done after 15-20 min once Payment is initiated .
o NEFT / RTGS : Status check should be done after 20-30 min once Payment is initiated

Please find the Input and Response JSON Structures below

Method Name: fund-confirmation

Description:
Used to retrieve the balance in the funding account.

Sample Request Structure

{
"Data": {
"DebtorAccount": {
"ConsentId": "26530",
"Identification": "000183200000042",
"SecondaryIdentification": "26530"
}
}
}

Request Fields:

Element Description Type Size (Min, Format Required

Max)
ConsentId A unique ID String (5,20) -- Mandatory
assigned to every
application. The
appID shall be valid
and enabled in the
back end systems
Identification Account Number String (1,32) Mandatory
from Customer

SecondaryIdentifica Unique String (1,10) -- Mandatory

tion CustomerID of the
corporate account

Page 12 of 69
 Document Version: 1.3.13

Success Response Structure

{
"Data": {"FundsAvailableResult": {
"FundsAvailableDateTime": "2020-04-23T17:36:21.939+05:30",
"FundsAvailable": true,
"BalanceAmount": "22222222209096850.99"
}},
"Links": {"Self": "https://uatesbtrans.yesbank.com:7085/api-banking/v2.0/domestic-
payments/fund-confirmation"}
}

Failure Response Structure

{
"Code": "ns:E2000",
"Message": "Either customer does not exist or Customer/Account combination is invalid or
Customer/Account Relationship is invalid",
"ActionCode": "AC_CONTACT_RELMGR",
"ActionDescription": "Contact Relationship/Sales Manager"
}

Response Fields:

Format/
Element Description Type Required
Values
Data Local Complex type
FundsAvailableResult Local Complex type
FundsAvailableDateTi
Request Timestamp Date Mandatory
me
FundsAvailable -- TRUE Mandatory
Numeri
BalanceAmount Account balance amount Mandatory
c
Links Local Complex type

Self <GET Status URL with Payment ID> Mandatory

Meta Local Complex type

ErrorCode subStatusCode String Conditional Mandatory

ErrorSeverity subStatusDescription String Conditional Mandatory

ActionCode actionCode String Conditional Mandatory

ActionDescription actionDescription String Conditional Mandatory

Page 13 of 69
Document Version: 1.3.13

Method Name: domestic-payments

Description:
Used to remit funds on behalf of remitter.

Sample Request Structure:

{
"Data": {
"ConsentId": "26530",
"Initiation": {
"InstructionIdentification": "19FDPTESTA15",
"EndToEndIdentification": "",
"InstructedAmount": {
"Amount": "2021111.88",
"Currency": "INR"
},
"DebtorAccount": {
"Identification": "001190100016907",
"SecondaryIdentification": "16521"
},
"CreditorAccount": {
"SchemeName": "HDFC0000001",
"Identification": "026291800001091",
"Name": "BeneName",
"Unstructured": {
"ContactInformation": {
"EmailAddress": "yes_b@yesb.com",
"MobileNumber": "9563256485"
}
}
},
"RemittanceInformation": {
"Reference": "FRESCO-101",
"Unstructured": {
"CreditorReferenceInformation": "RemeToBeneInfo"
}
},
"ClearingSystemIdentification": "RTGS"
}
},
"Risk": {
"DeliveryAddress": {
"AddressLine": [
"Flat 7",
"Acacia Lodge"

Page 14 of 69
Document Version: 1.3.13

],
"StreetName": "Acacia Avenue",
"BuildingNumber": "27",
"PostCode": "600524",
"TownName": "MUM",
"CountySubDivision": [
"MH"
],
"Country": "IN"
}
}
}

Request Structure for Nodal

{
"Data": {
"ConsentId": "1057462",
"Initiation": {
"InstructionIdentification": "DPTESTER26APR1",
"EndToEndIdentification": "",
"InstructedAmount": {
"Amount": "210.88",
"Currency": "INR"
},
"DebtorAccount": {
"Identification": "016190100002100",
"SecondaryIdentification": "1066462"
},
"CreditorAccount": {
"BeneficiaryCode": "23DECFT"
},
"RemittanceInformation": {
"Unstructured": {
"CreditorReferenceInformation": "RemeToBeneInfo2233@#4Va..--lidation Test on
UAT for fundstransfer change where lenght "
}
},
"ClearingSystemIdentification": "FT"
}
},
"Risk": {
"PaymentContextCode": "NODAL"
}
}

Page 15 of 69
Document Version: 1.3.13

Request Structure for GST

{
"Data": {
"ConsentId": "26530",
"Initiation": {
"InstructionIdentification": "RAHULR170",
"EndToEndIdentification": "",
"InstructedAmount": {
"Amount": "1110.83",
"Currency": "INR"
},
"DebtorAccount": {
"Identification": "000183200000042",
"SecondaryIdentification": "26530",
"Unstructured": {
"ContactInformation": {
"EmailAddress": "ybl@ybl.com",
"MobileNumber": " 7845451575 "
}
}
},
"CreditorAccount": {
"SchemeName": "RBIS0GSTPMT",
"Identification": "01245454415454415800000162",

"Name": "GST",

"Unstructured": {
"ContactInformation": {
"EmailAddress": "ybl@ybl.com",
"MobileNumber": "7845451575"
}

}
},
"RemittanceInformation": {
"Reference": "FRESCO-101",
"Unstructured": {
"CreditorReferenceInformation": " DED?{}@#\\%!.-\/(),'+ C000"
}
},
"ClearingSystemIdentification": "NEFT"
}
},
"Risk": {
"PaymentContextCode": "GST",
"DeliveryAddress": {
"AddressLine": [
"AEDEDED?{}@#\\%!.-\/(),'+ C000",
"ABCDEED?{}@#\\%!.-\/(),'+ C000"

Page 16 of 69
Document Version: 1.3.13

],
"StreetName": "ABCDD?{}@#\\%!.-\/(),'+ C000",
"BuildingNumber": "ABCDD?{}@#\\%!.-\/(),'+ C000",
"PostCode": "444645",
"TownName": "Mum():?{}@#%!.-baii",
"CountySubDivision": [
" Mum():?{}@#%!.-baii"
],
"Country": "IN"
}
}
}

Request Structure for REFUND

{
"Data": {
"ConsentId": "26530",
"Initiation": {
"InstructionIdentification": "R1EMMTEST00@!11",
"EndToEndIdentification": "",
"InstructedAmount": {
"Amount": "2212121212.8",
"Currency": "INR"
},
"DebtorAccount": {
"Identification": "000183200000042",
"SecondaryIdentification": "26530",
"Unstructured": {
"ContactInformation": {
"EmailAddress": "yes_b@yesb.com",
"MobileNumber": "9563256485"
}
}
},
"CreditorAccount": {
"SchemeName": "HDFC0000001",
"Identification": "2965304111",
"Name": "RAHUL FERAN",

"Unstructured": {
"ContactInformation": {
"EmailAddress": "yes_b@yesb.com",
"MobileNumber": "9563256485"
}

Page 17 of 69
 Document Version: 1.3.13

}
},
"RemittanceInformation": {
"Reference": "FRESCO-101",
"Unstructured": {
"CreditorReferenceInformation": "Re"
}
},
"ClearingSystemIdentification": "NEFT"
}
},
"Risk": {
"PaymentContextCode": "REFUND",
"DeliveryAddress": {
"AddressLine": [
"Flat 7",
"Acacia Lodge"
],
"StreetName": "Acacia Avenue",
"BuildingNumber": "27",
"PostCode": "6000024",
"TownName": "MUM",
"CountySubDivision": [
"MH"
],
"Country": "IN"
}
}
}

Request Fields:

Size(
Format/
Element Description Type Min,M Required
Values
ax
Data Local Complex type
A unique ID (5,20)
assigned to every
application. The
ConsentId String Mandatory
appID shall be valid
and enabled in the
back end systems.
Initiation Local Complex type
Request Reference (1,32)
InstructionIdentification Number from String Mandatory
Customer
Required in GetStatus No
EndToEndIdentification
Response after length

Page 18 of 69
 Document Version: 1.3.13

clearing system define

generates response d
InstructedAmount Local Complex type
No Mandatory
length
Amount Transfer Amount String
define
d
No Mandatory
Transfer Currency length
Currency String
Code define
d INR
DebtorAccount Local Complex type
No
length
SchemeName Debit IFSC String Optional
define
d
Identification Debit Account No Numeric (10,20) Mandatory
No
Debit Account length
Name String Optional
Name define
d
For transfer of 50cr 20
beneficiaryLEI or more beneficiary Alpha numeric Optional
LEI to be passed
Customer Id of the (1,10)
SecondaryIdentification String Mandatory
debit account
Unstructured Local Complex type
ContactInformation Local Complex type
EmailAddress String (3,100) Optional
MobileNumber Numeric (7,16) Optional
Identities Local Complex type
AadhaarNumber String (12,12) Optional
MobileNumber Numeric (7,16) Optional
CreditorAccount Local Complex type
No Mandatory
length
SchemeName Beneficiary IFSC Bene IFSC
define
d
Beneficiary Account (1,34) Mandatory
Identification
Number
String –Characters defined (1,255) Mandatory
below in pattern are
allowed.
Characters
[.|'|\- defined below in
|:|{}|@|#|?|!|\s pattern are
allowed.
Name Beneficiary Name ]*[A-Z|a-z|0- [.|'|\-
9]{1}[A-Z|a-z|0- |:|{}|@|#|?|!|\s
]*[A-Z|a-z|0-
9|.|'|\- 9]{1}[A-Z|a-z|0-
|:|{}|@|#|?|!|\s 9|.|'|\-
|:|{}|@|#|?|!|\s
]* ]*
No
SecondaryIdentification Optional
length
Page 19 of 69
 Document Version: 1.3.13

define
d
(1,255) Conditiona
BeneficiaryCode Beneficiary Code l
Mandatory
Unstructured Local Complex type
ContactInformation Local Complex type
EmailAddress Beneficiary EmailID (3,100) Optional
Beneficiary (7,16) Optional
MobileNumber
MobileNo
Identities Local Complex type
Beneficiary Aadhaar (12,12) Optional
AadhaarNumber
Number
Beneficiary Mobile (7,16) Optional
MobileNumber
Number
RemittanceInformation Local Complex type
No
length
Reference Optional
define
d
Unstructured
CreditorReferenceInform (2,120)
Remarks Mandatory
ation
Conditiona
ClearingSystemIdentificat NEFT/A2A/RTGS/I
Transfer Type l
ion MPS
Mandatory
Risk Local Complex type
No
GST Conditiona
length
PaymentContextCode Purpose Code REFUND l
define
NODAL Mandatory
d
No Optional
length
MerchantCategoryCode
define
d
No Optional
MerchantCustomerIdentif length
ication define
d
DeliveryAddress Local Complex type
Beneficiary Address (1,35)
AddressLine Mandatory
1
Beneficiary Address (1,35) Optional
StreetName
2
Beneficiary Address (1,35) Optional
BuildingNumber
3
Beneficiary Postal (1,15) Optional
PostCode
Code
TownName Beneficiary City (1,50) Optional
Beneficiary State Or (1,50) Optional
CountySubDivision
Province

Page 20 of 69
 Document Version: 1.3.13

No Optional
length
Country Beneficiary country
define
d

Success Response Structure

{
"Data": {
"ConsentId": "26530",
"TransactionIdentification": "aa7157144e6111eabbe60a0028fc0000",
"Status": "Received",
"CreationDateTime": "2020-02-13T18:36:36.442+05:30",
"StatusUpdateDateTime": "2020-02-13T18:36:36.442+05:30",
"Initiation": {
"InstructionIdentification": "RAHULR104",
"EndToEndIdentification": "",
"InstructedAmount": {
"Amount": "21.83",
"Currency": "INR"
},
"DebtorAccount": {
"Identification": "000183200000242",
"SecondaryIdentification": "26530",
"Unstructured": {"ContactInformation": {
"EmailAddress": "ybl@ybl.com",
"MobileNumber": " 7845451575 "
}}
},
"CreditorAccount": {
"SchemeName": "HDFC0000001",
"Identification": "019887700000129",
"Name": "Va on T12tspaces in between and length greater then",
"Unstructured": {"ContactInformation": {
"EmailAddress": "ybl@ybl.com",
"MobileNumber": "7845451575"
}}
},
"RemittanceInformation": {
"Reference": "FRESCO-101",
"Unstructured": {"CreditorReferenceInformation": " DED?{}@#\\%!.-/(),'+ C000"}
},
"ClearingSystemIdentification": "NEFT"
}
},
"Risk": {
"PaymentContextCode": "REFUND",
Page 21 of 69
Document Version: 1.3.13

"DeliveryAddress": {
"AddressLine": [
"AEDEDED?{}@#\\%!.-/(),'+ C000",
"ABCDEED?{}@#\\%!.-/(),'+ C000"
],
"StreetName": "ABCDD?{}@#\\%!.-/(),'+ C000",
"BuildingNumber": "ABCDD?{}@#\\%!.-/(),'+ C000",
"PostCode": "444645",
"TownName": "Mum():?{}@#%!.-baii",
"CountySubDivision": [" Mum():?{}@#%!.-baii"],
"Country": "IN"
}
},
"Links": {"Self": "https://uatesbtrans.yesbank.com:7085/api-banking/v2.0/domestic-
payments/payment-details?InstrId=RAHULR104&ConsentId=26530&Id=26530"}
}

Failure Response Structure in case of Bad request

{
"Code": "ns:E400",
"Id": "iib:E5026",
"Message": "Bad Request: cvc-minLength-valid: The length of value \"\" is \"0\" which is not
valid with respect to the minLength facet with value \"1\" for type
\"#Anonymous\".:/Root/{http://www.ybl.com/paymentServices}:DomesticPayments/{http:
//www.ybl.com/paymentServices}:Data/{http://www.ybl.com/paymentServices}:Initiation
/{http://www.ybl.com/paymentServices}:DebtorAccount/{http://www.ybl.com/paymentSe
rvices}:SecondaryIdentification",
"ActionCode": "AC_CONTACT_SUPPORT",
"ActionDescription": "Technical error / Invalid message. Contact Support"
}

Failure Response Structure in case of Functional error

{
"Data": {
"ConsentId": "26530",
"TransactionIdentification": null,
"Status": "Failed",
"CreationDateTime": "2020-02-14T19:26:00.000+05:30",
"StatusUpdateDateTime": "2020-02-14T19:26:03.000+05:30",
"Initiation": {
"InstructionIdentification": "RAHULR152",
"EndToEndIdentification": null,
"InstructedAmount": {
Page 22 of 69
Document Version: 1.3.13

"Amount": 124,
"Currency": "INR"
},
"DebtorAccount": {
"Identification": "000183200000242",
"SecondaryIdentification": "265310"
},
"CreditorAccount": {
"SchemeName": "YESB0000001",
"Identification": "019887700000029",
"Name": "Va on T12tspaces in between and length greater then",
"BeneficiaryCode": null,
"Unstructured": {"ContactInformation": {
"EmailAddress": "ybl@ybl.com",
"MobileNumber": "7845451575"
}},
"RemittanceInformation": {"Unstructured": {"CreditorReferenceInformation": "
DED?{}@#\\%!.-/(),'+ C000"}},
"ClearingSystemIdentification": "FT"
}
}
},
"Risk": {
"PaymentContextCode": "REFUND",
"DeliveryAddress": {
"AddressLine": "AEDEDED?{}@#\\%!.-/(),'+ C000,ABCDEED?{}@#\\%!.-/(),'+ C000",
"StreetName": "ABCDD?{}@#\\%!.-/(),'+ C000",
"BuildingNumber": "ABCDD?{}@#\\%!.-/(),'+ C000",
"PostCode": "444645",
"TownName": "Mum():?{}@#%!.-baii",
"CountySubDivision": " Mum():?{}@#%!.-baii",
"Country": "IN"
}
},
"Links": {"Self": "https://uatesbtrans.yesbank.com:7085/api-banking/v2.0/domestic-
payments/payment-details?InstrId=RAHULR152&ConsentId=26530&Id=26530"},
"Meta": {
"ErrorCode": "ns:E402",
"ErrorSeverity": " Transaction Amt is exceeding the limit Amt. Account is going to
Overline. ",
"ActionCode": "AC_TXN_FAILED",
"ActionDescription": "Transaction Failed. Please check error description and action"
}
Page 23 of 69
 Document Version: 1.3.13

Response Fields:

Element Description Type Format/ Values Required

Data Local Complex type
A unique ID assigned to
every application. The
ConsentId appID shall be valid and String Mandatory
enabled in the back end
systems.
TransactionIdentification Unique Response No String Mandatory

Status Status Code String Mandatory

CreationDateTime Transaction Date Date Mandatory

StatusUpdateDateTime Date Mandatory

Initiation Local Complex type

Request Reference
InstructionIdentification String Mandatory
Number from Customer
Required in GetStatus
EndToEndIdentification Response after clearing String
system generates response
InstructedAmount Local Complex type
Transfer Amount. Mandatory
Amount Numeric
Amount in ISO Format?
Currency Transfer Currency Code -- Mandatory
INR
DebtorAccount Local Complex type
SchemeName Debit IFSC String Optional
Identification Debit Account No Numeric Mandatory
Name Debit Account Name String Optional
Customer Id of the debit
SecondaryIdentification String Mandatory
account
Unstructured Local Complex type
ContactInformation Local Complex type
EmailAddress String Optional

MobileNumber String Optional

Identities Local Complex type

AadhaarNumber String Optional

MobileNumber Numeric Optional

CreditorAccount Local Complex type

SchemeName Beneficiary IFSC String Mandatory
Beneficiary Account Mandatory
Identification Numeric
Number
Mandatory
Bene Name in case of
NEFT/RTGS,
if IMPS and
Name String
nameWithBeneficiaryBank
is not null, then populate
nameWithBeneficiaryBank

SecondaryIdentification String Optional

Conditional
BeneficiaryCode Beneficiary Code String
Mandatory
Unstructured Local Complex type

Page 24 of 69
 Document Version: 1.3.13

ContactInformation Local Complex type

EmailAddress Beneficiary emailID Optional

MobileNumber Beneficiary mobileNo Numeric Optional

Identities Local Complex type

Beneficiary Aadhaar Optional
AadhaarNumber String
Number
Beneficiary Mobile Optional
MobileNumber Numeric
Number
RemittanceInformation Local Complex type
Reference String Optional
Unstructured Local Complex type
CreditorReferenceInformation Remarks String M
Conditional
ClearingSystemIdentification Transfer Type -- NEFT/A2A/RTGS/IMPS/Aadhaar
Mandatory
Risk Local Complex type
GST
Conditional
PaymentContextCode Purpose Code -- REFUND
Mandatory
NODAL
MerchantCategoryCode String Optional

MerchantCustomerIdentification String Optional

DeliveryAddress Local Complex type

AddressLine Beneficiary Address 1 String M
StreetName Beneficiary Address2 String Optional

BuildingNumber Beneficiary Address3 String Optional

PostCode Beneficiary postal Code Numeric Optional

TownName Beneficiary city String Optional

Beneficiary Optional
CountySubDivision String
stateOrProvince
Country Beneficiary country String Optional
Links Local Complex type
<Full Resource for
Domestic Payments
Self should be replayed as part String Mandatory
of response/{Payment-
ID}>
Meta Local Complex type
Conditional
ErrorCode subStatus Code String
Mandatory
Conditional
ErrorSeverity subStatus Description String
Mandatory
Conditional
ActionCode Action Code String
Mandatory
Conditional
ActionDescription Action Description String
Mandatory

Method Name: payment-details

Description:

Used to retrieve the status of transaction that was previously submitted.

Note : If amount is greater than 1 crore amount will be displayed in Exponential form

Page 25 of 69
 Document Version: 1.3.13

Sample Request structure

{
"Data": {
"InstrId": "RRAA102T140",
"ConsentId": "26530",
"SecondaryIdentification": "2653012"
}
}

Request Fields:

Element Description Type Size (Min, Format Required

Max)
InstrId Request Reference String (1,32) Mandatory
Number from Customer

ConsentId A unique ID assigned to String (5,32) Mandatory

every application. The
appID shall be valid and
enabled in the back end
systems.
SecondaryIde Unique String (1,10) Mandatory
ntification CustomerID of the
corporate account .

Success Response Structure

"Data": {
"ConsentId": "26530",
"TransactionIdentification": "2653012",
"Status": " SettlementCompleted ",
"CreationDateTime": " 2020-04-21T18:44:49.000+05:30 ",
"StatusUpdateDateTime": " 2020-04-21T18:44:53.000+05:30 ",
"Initiation": {
"InstructionIdentification": "ACME412",
"EndToEndIdentification": " 2414920190405000200048988 ",
"InstructedAmount": {
"Amount": "165.88",
"Currency": "INR"
},
"DebtorAccount": {
"Identification": "000183200000042",
"SecondaryIdentification": "26530"
},
"CreditorAccount": {
"SchemeName": "YESBOCMSNOC",
"Identification": "08080021325698",

Page 26 of 69
Document Version: 1.3.13

"Name": "ACME Inc",

"BeneficiaryCode": "0002"
},
"RemittanceInformation": {
"Reference": "FRESCO-101",
"ClearingSystemIdentification": "FT" }
}
},
"Risk": {
"PaymentContextCode": "REFUND",
"DeliveryAddress": {
"AddressLine": "AEDEDED?{}@#\\%!.-/(),'+ C0lk00,ABCDEED?{}@#\\%!.-/(),'+ C000",
"StreetName": "ABCDD?{}@#\\%!.-/(),'+ C000",
"BuildingNumber": "ABCDD?{}@#\\%!.-/(),'+ C000",
"PostCode": "444645",
"TownName": "Mum():?{}@#%!.-baii",
"CountySubDivision": " Mum():?{}@#%!.-baOii",
"Country": "IN"
}
},
"Links": {
"Self": " https://uatsky.yesbank.in/api/v3.1/uat/domestic-payments/58923-001"
},
"Meta": {}
}

Failure response Structure in case reference no is not found in ESB transaction table
(Request has not reached ybl system)

Response

{"Code":"ns:E404","Message":"Request Not
Found","ActionCode":"AC_TXN_NOTFOUND","ActionDescription":"Transaction not found"}

Failure Response Structure

{
"Data": {
"ConsentId": "26530",
"TransactionIdentification": null,
"Status": "Failed",
"CreationDateTime": "2020-02-14T19:12:02.000+05:30",
"StatusUpdateDateTime": "2020-02-14T19:12:02.000+05:30",
"Initiation": {
"InstructionIdentification": "RAHULR142",
"EndToEndIdentification": null,
"InstructedAmount": {
"Amount": 1111125.83,

Page 27 of 69
Document Version: 1.3.13

"Currency": "INR"
},
"DebtorAccount": {
"Identification": "000183200000042",
"SecondaryIdentification": "26530"
},
"CreditorAccount": {
"SchemeName": "HDFC0000001",
"Identification": "019887700000029",
"Name": "Va on T12tspaces in between and length greater then",
"BeneficiaryCode": null,
"Unstructured": {"ContactInformation": {
"EmailAddress": "ybl@ybl.com",
"MobileNumber": "7845451575"
}},
"RemittanceInformation": {"Unstructured": {"CreditorReferenceInformation": "
DED?{}@#\\%!.-/(),'+ C000"}},
"ClearingSystemIdentification": null
}
}
},
"Risk": {
"PaymentContextCode": "REFUND",
"DeliveryAddress": {
"AddressLine": "AEDEDED?{}@#\\%!.-/(),'+ C000,ABCDEED?{}@#\\%!.-/(),'+ C000",
"StreetName": "ABCDD?{}@#\\%!.-/(),'+ C000",
"BuildingNumber": "ABCDD?{}@#\\%!.-/(),'+ C000",
"PostCode": "444645",
"TownName": "Mum():?{}@#%!.-baii",
"CountySubDivision": " Mum():?{}@#%!.-baii",
"Country": "IN"
}
},
"Links": {"Self": "https://uatesbtrans.yesbank.com:7085/api-banking/v2.0/domestic-
payments/payment-details?InstrId=RAHULR142&ConsentId=26530&Id=26530"},
"Meta": {
"ErrorCode": "ns:E1001",
"ErrorSeverity": "The transaction amount exceeds the maximum amount for IMPS:
200000",
"ActionCode": "AC_INVALID_DATA",
"ActionDescription": "Invalid/Incorrect data in message. Update and retry"
}
}
Page 28 of 69
 Document Version: 1.3.13

Response Fields:

Element Description Type Format/ Values Required

Data Local Complex type
A unique ID assigned
to every application. String
ConsentId The appID shall be whiteSpace(colla Mandatory
valid and enabled in pse) pattern(\w)
the back end systems.
TransactionIdentification Unique response String Mandatory
Status number
Status of Transcation String Mandatory
Date and time when the
CreationDateTime Date YYYY-MM-DDTHH:mm:ss Mandatory
transaction was
received
The date by
andthe bank.
time
StatusUpdateDateTime when the transaction String Mandatory
status was updated
Initiation Local Complex type
InstructionIdentification Unique request no String Mandatory
Unique Transaction
Reference Number
EndToEndIdentification String Mandatory
generated by payment
network. (UTR/RRN)
InstructedAmount Local Complex type
Amount Transfer Amount Numeric Mandatory
The currency code of
Currency the transaction amount. String Allowed Values INR Mandatory
Only INR allowed.

DebtorAccount Local Complex type

String
Identification Credit Account No Mandatory

Customer ID of the
SecondaryIdentification String Optional
account

CreditorAccount Local Complex type

SchemeName Credit IFSC String Optional
Identification Credit Account No String Mandatory
Name Credit Account Name String Optional
Conditional
BeneficiaryCode Beneficiary Code String
Mandatory
Unstructured Local Complex type
ContactInformation Local Complex type
Page 29 of 69
 Document Version: 1.3.13

EmailAddress String Optional

MobileNumber Numeric Optional
Identities Local Complex type
AadhaarNumber String Optional
MobileNumber Numeric Optional
RemittanceInformation Local Complex type
Reference String Optional
Unstructured Local Complex type
CreditorReferenceInformatio
Remarks String Mandatory
n
ClearingSystemIdentificatio NEFT/A2A/RTGS/IMPS/A Conditional
Transfer Type --
n Aadhaar/ANY Mandatory
Risk Local Complex type
Conditional
PaymentContextCode Purpose Code String GST
Mandatory
MerchantCategoryCode String Optional
MerchantCustomerIdentifica
String Optional
tion
DeliveryAddress Local Complex type

AddressLine Beneficiary Address1 String Mandatory

StreetName Beneficiary address2 String Optional

BuildingNumber Beneficiary address3 String Optional

PostCode Beneficiary postalCode Numeric Optional

TownName Beneficiary city String Optional

Beneficiary
CountySubDivision String Optional
stateOrProvince
Country Beneficiary country String Optional
Links Local Complex type
<GET Status URL with
Self String Mandatory
Payment ID>
Meta Local Complex type
Conditional
ErrorCode subStatus Code String
Mandatory
Conditional
ErrorSeverity subStatus Description String
Mandatory
Conditional
ActionCode Action Code String
Mandatory
Conditional
ActionDescription Action Description String
Mandatory

Circuit Breaker

Circuit breaker is a functionality where if you initiate any transactions while the backend system is
down, it will auto-reject the transaction with error code:- “ns:E503” along-with description “Service
Page 30 of 69
Document Version: 1.3.13

Unavailable”.

In case of any queries / clarification required, you can write to us at dlesbl2support@yesbank.in

Below is the sample response of FT3 transaction in case Backend system is down
FT3 Response -

{
"Data": {
"ConsentId": "26530",
"TransactionIdentification": "558b51fa229011eca6c90a0028fc0000",
"Status": "FAILED",
"CreationDateTime": "2021-10-01T13:49:44.588+05:30",
"StatusUpdateDateTime": "2021-10-01T13:49:44.588+05:30",
"Initiation": {
"InstructionIdentification": "DPXZaCCXF3",
"EndToEndIdentification": "",
"InstructedAmount": {
"Amount": "22.08",
"Currency": "INR"
},
"DebtorAccount": {
"Identification": "000183200000042",
"SecondaryIdentification": "26530",
"Unstructured": {"ContactInformation": {
"EmailAddress": "surabhi.joshi.ext@yesbank.in",
"MobileNumber": " 7845451571235 "
}}
},
"CreditorAccount": {
"SchemeName": "Yesb0000001",
"Identification": "041583800000162",
"Name": "Va on T12t .'-:{}@#?!fundstransfer servicesdsdfdssss sdsdss in UAT for
spaces in between and length greater then",
"Unstructured": {"ContactInformation": {
"EmailAddress": "rahul.feran.ext@yesbank.in",
"MobileNumber": "7276482212123"
}}
},
"RemittanceInformation": {
"Reference": "FRESCO-101",
"Unstructured": {"CreditorReferenceInformation": " DEFSDEFDD?{}@#\\%!.-/(),'+
C000 TO check the length for @ this lion tif"}
},
"ClearingSystemIdentification": "NEFT"
}
},
Page 31 of 69
Document Version: 1.3.13

"Risk": {
"PaymentContextCode": "REFUND",
"DeliveryAddress": {
"AddressLine": [
"AEDEDED?{}@#\\%!.-/(),'+ C000",
"ABCDEED?{}@#\\%!.-/(),'+ C000"
],
"StreetName": "ABCDD?{}@#\\%!.-/(),'+ C000",
"BuildingNumber": "ABCDD?{}@#\\%!.-/(),'+ C000",
"PostCode": "444645",
"TownName": "Mum():?{}@#%!.-baii",
"CountySubDivision": [" Mum():?{}@#%!.-baii"],
"Country": "IN"
}
},
"Links": {"Self": "https://uatesbtrans.yesbank.com:7085/api-banking/v2.0/domestic-
payments/payment-details"},
"Meta": {
"ErrorCode": "ns:E503",
"ErrorSeverity": "Service Unavailable"
}
}

Benificiary LEI

For all transactions with amount 50Cr or more via the NEFT/ RTGS channel, please pass 20 characters
alphanumeric Beneficiary LEI.
Sample Request:
{
"Data": {
"ConsentId": "26530",
"Initiation": {
"InstructionIdentification": "19FDPTESTA15",
"EndToEndIdentification": "",
"InstructedAmount": {
"Amount": "2021111.88",
"Currency": "INR"
},
"DebtorAccount": {
"Identification": "001190100016907",
"SecondaryIdentification": "16521"
},
"CreditorAccount": {
"SchemeName": "HDFC0000001",
"Identification": "026291800001091",
"Name": "BeneName",
“beneficiaryLEI”:”red34262222”
"Unstructured": {
Page 32 of 69
 Document Version: 1.3.13

"ContactInformation": {
"EmailAddress": "yes_b@yesb.com",
"MobileNumber": "9563256485"
}
}
},
"RemittanceInformation": {
"Reference": "FRESCO-101",
"Unstructured": {
"CreditorReferenceInformation": "RemeToBeneInfo"
}
},
"ClearingSystemIdentification": "RTGS"
}
},
"Risk": {
"DeliveryAddress": {
"AddressLine": [
"Flat 7",
"Acacia Lodge"
],
"StreetName": "Acacia Avenue",
"BuildingNumber": "27",
"PostCode": "600524",
"TownName": "MUM",
"CountySubDivision": [
"MH"
],
"Country": "IN"
}
}
}

Note: Transactions with LEI value less than 20 characters will fail with error code ns:E400 - Bad
Request

Element Description Type Format/ Values Element

For transfer of 50cr or more 20
beneficiaryLEI Alpha numeric Optional
beneficiary LEI to be passed

Page 33 of 69
Document Version: 1.3.13

Section 3: Response Codes

Domestic-payments Response Codes

Error
# statusCode subStatusCode Message(subStatusText) When Does it Come? Recommended Action
Classification
Transaction initiated
is a valid transaction
Transaction has been
1 Received and has been Transaction successful Technical
Accepted
accepted for
processing
A transaction with same UniqueRequestNo Retry with a new UNR
reference number is has already come
2 Duplicate ns:E8000 Technical
already processed or before for a
under processing successful transaction

Payment-details -Response Codes

Note: All failed transactions can be considered as Failed. Status will not change after that.
ESB does not retry for any failed transactions.
For every payment made, checking status of respective transaction is advisable before any retry.
If Status API doesn’t give the finality of the transaction after multiple attempts, get in touch with YBL
support Team (Refer escalation matrix in Section 5)

Action
Action Code Descripti
When Error
ErrorCod Recommen on
No Status ErrorSeverity Does it Classificat
e ded Action
Come? ion
TEXT (50 TEXT(256
chars) chars)
Retry
initiating
transaction
s 3 times at
an interval
of 30 mins
considering
status
remains
Transaction
failed for
has failed at
every
downstream
attempt. In Retry
system/transa Technical AC_RETRY_TX
1 FAILED ns:E307 case status Business transactio
ction cannot Failure N
still n
be processed
remains
during this
failed,
period
please
contact
APIL1.helpd
esk@yesban
k.in with
transaction
details
along with
error code

Page 34 of 69
Document Version: 1.3.13

Current Please
Business Please
Transaction reinitiate
Failure reinitiate as
Time not AC_TXN_FAIL as per
2 FAILED ns:E307 per next Business
within ED next
available
Window available
window
Period. window

When the
Debit
Transactio
account
n Failed.
Insufficient does not Kindly
Please
Balance in have fund the
AC_TXN_FAIL check
2 FAILED ns:E402 debit account, sufficient debit Business
ED error
payment Balance to account
descriptio
required process and retry
n and
the
action
transactio
n

The Basic
Auth User
ID &
Password
The Basic
are
Auth User
provided to
ID &
you by the Technical
Password
Customer / bank. error /
sent in the
Account Ensure that AC_CONTACT Invalid
3 FAILED ns:E403 request, Technical
Access you are _SUPPORT message.
was not
Forbidden using the Contact
found in
correct Support
the
values. If
configurat
you believe
ion.
you are,
then
contact
support.

Retry with
a valid
Request
Reference
Number. If
Request
Number
was valid
Request please do
Reference payment
Number details Transactio
Request Not AC_TXN_NOT
4* ns:E404 sent in the status Business n not
Found FOUND
request check 3 found
was not times in 30
found. mins
duration
and if still
request is
not found
then u can
initiate a
new
transaction

Page 35 of 69
Document Version: 1.3.13

None of the Transactio

transfer types The Retry the n Failed.
allowed to the Transactio transaction Please
app id or n Type is with a valid AC_TXN_FAIL check
5 FAILED ns:E405 Business
customer can not from transferTyp ED error
perform the the list e or with descriptio
requested specified ANY n and
transaction. action

Transactio
Kindly n Failed.
Problem check with Please
Beneficiary with Beneficiary AC_TXN_FAIL check
6 FAILED ns:E406 Technical
not acceptable beneficiar before ED error
y account reinitiating descriptio
transfer n and
action

When a
CBS
reference
Transactio
no is not
n Failed.
None: The found in
Please do Please
requested the core
Get Status AC_TXN_FAIL check
7 FAILED ns:E410 entity is no banking Business
after some ED error
longer table
time descriptio
available during a
n and
getStatus
action
of the
transactio
n

Number
of requests
that have
come from
(Limit you have Retry
Daily/transact exceeded Retry next AC_RETRY_TX transactio
8* FAILED ns:E429 Technical
ion/rate) the day N_NEXTDAY ns next
exceeded permissibl day
e limit set
by an
upstream
system

An
Do Get
upstream
status after
service Retry
30 minutes AC_RETRY_TX
9 FAILED ns:E502 Bad Gateway returned Technical transactio
and act N
an n
basis the
unexpecte
response
d error

The
The Ensure
transactio Invalid/In
transaction Transaction
n amount correct
amount amount is
exceeds AC_INVALID_ data in
10 FAILED ns:E1001 exceeds the less than or Business
the DATA message.
maximum equal to
maximum Update
amount for INR
amount and retry
IMPS: 2,00,000
for IMPS:

Page 36 of 69
Document Version: 1.3.13

The
The transfer Check the
transfer Invalid/In
currency is currency
currency correct
not passed in
is not AC_INVALID_ data in
11 FAILED ns:E1002 supported. the request Business
supported. DATA message.
Supported and rectify
Supported Update
currency is before
currency and retry
INR. reinitiating
is INR.

Transaction
Transfer Transactio Invalid/In
Amount
Amount is n Amount correct
should be
less than is less than AC_INVALID_ data in
12 FAILED ns:E1004 more than Business
minimum RTGS DATA message.
or equal to
amount for Minimum Update
INR
RTGS Amount and retry
2,00,000

When
Beneficiar
y bank is
Invalid/In
IMPS is not not IMPS
correct
enabled for enabled Retry with
AC_INVALID_ data in
13 FAILED ns:E1028 the and you transfer Business
DATA message.
beneficiary have type 'ANY'
Update
IFSC passed
and retry
transfer
type
'IMPS'

Contact
Relationshi Invalid/In
Creditor
FT Transfer p / Sales correct
IFSC for
with Non yes Manager of AC_INVALID_ data in
14 FAILED ns:E1029 FT must Technical
bank the Bank or DATA message.
be yes
beneficiary initiate a Update
bank
transaction and retry
with NEFT

When
either
customer
Either
ID-
customer does
account
not exist or Retry with
No
Customer/Ac correct
combinati Contact
count customerID
on is AC_CONTACT Relationsh
15 FAILED ns:E2000 combination is – account Business
invalid or _RELMGR ip/Sales
invalid or No
customer- Manager
Customer/Ac combinatio
account
count n
does not
Relationship
have
is invalid
relationshi
p that is
allowed

Page 37 of 69
Document Version: 1.3.13

Please retry
Remitter
using Contact
Account account
correct AC_CONTACT Relationsh
16 FAILED ns:E2001 status is status is Business
remitter _RELMGR ip/Sales
inactive inactive or
account Manager
dormant
number

Beneficiar
y details
Transactio
are not Maintain
n Failed.
maintaine beneficiary,
Please
Beneficairy d in the verify the
AC_TXN_FAIL check
17 FAILED ns:E2005 not found for beneficiar beneficiary Business
ED error
code y and then
descriptio
maintenan retry
n and
ce system transaction
action
for the
code

Purpose
Pass correct
Code Invalid/In
purpose
passed in correct
code or
Purpose Code the AC_INVALID_ data in
18 FAILED ns:E6000 contact Business
not found: request DATA message.
Sales or
does not Update
Relationshi
exist in the and retry
p team
system

Beneficiar
y Code
passed in
the Ensure
Only request valid Invalid/In
registered does not beneficiary correct
beneficiaries exist in the code is AC_INVALID_ data in
19 FAILED ns:E6001 Business
are allowed system or being DATA message.
for this Beneficiar passed in Update
purpose code: y Code is payment and retry
not passed request
in the
payment
request

Kindly Pass Invalid/In

Purpose
appropriate correct
Purpose Code code is not
Purpose AC_INVALID_ data in
20 FAILED ns:E6002 is required for passed in Business
Code in DATA message.
this customer: payment
payment Update
request
request and retry

Page 38 of 69
Document Version: 1.3.13

Key In the
When correct
debit debit Invalid/In
account Account correct
Invalid Debit
no. does number or AC_INVALID_ data in
21 FAILED ns:E6003 Account for Business
not exist Contact DATA message.
Customer
in the Relationshi Update
customer p / Sales and retry
set up Manager of
the Bank

Either
Beneficiary
When
Name or
Beneficiar
beneficiary
y Name or Retry after
IFSC code is Invalid/In
Beneficiar correcting
not valid for correct
y IFSC the
GST payment. AC_INVALID_ data in
22 FAILED ns:E6005 Code for Beneficiary Business
Valid value is DATA message.
GST Name or
for beneficiary Update
Payment Beneficiary
name: < GST> and retry
Request is IFSC
and ifsc code
not as
is:
expected
<RBIS0GSTP
MT >

When
Beneficiary
Beneficiar Retry with Invalid/In
account no
y Account your CPIN correct
length is not
length in as AC_INVALID_ data in
23 FAILED ns:E6006 valid for GST Business
the GST beneficiary DATA message.
payment
Payment Account Update
allowed
request is No and retry
length is 14
not 14

When
request
comes
with a Invalid/In
The specified
purpose correct
purpose code
code Contact AC_INVALID_ data in
24 FAILED ns:E6007 is not allowed Business
which Support DATA message.
for the chosen
does not Update
transferType
allow the and retry
transfer
type
passed

Length of
Unique Unique
Retry the
request no Request Invalid/In
transaction
length is not No in the correct
after
valid for request is AC_INVALID_ data in
25 FAILED ns:E6008 correcting Business
APBS transfer more than DATA message.
the Unique
type, max 13 and Update
Request
allowed transfer and retry
Number
length is 13 type is
‘APBS’

Page 39 of 69
Document Version: 1.3.13

UniqueRe
A transaction questNo Transactio
with same has n Failed.
reference already Please
number is come Retry with AC_TXN_FAIL check
26 FAILED ns:E8000 Business
already before for a new UNR ED error
processed or a descriptio
under successful n and
processing transactio action
n

There is a Contact
Account Contact
memo present AC_CONTACT Relationsh
27 FAILED flex:E11 cannot be Sales Business
on the Debit _RELMGR ip/Sales
debited RM/PSM
account. Manager

Please re- Please re-

check check
Invalid Invalid
destination AC_CONTACT destinatio
28 FAILED flex:E18 destination destinatio Business
bank _RELMGR n bank
bank n bank
details in details in
request. request.

Retry
initiating
transaction
s 3 times at
an interval
of 30 mins
considering
status
remains
failed for
In case of
every
issues
Rejected/Faile attempt. In Retry
arising at AC_RETRY_TX
29 FAILED flex:E307 d at upstream case status Technical transactio
upstream N
CBS Service still n
CBS
remains
Service
failed,
please
contact
APIL1.helpd
esk@yesban
k.in with
transaction
details
along with
error code

Pass correct
No
combinatio
Relationsh
No n of A/C
ip Exists
Relationship number Contact
with the
Exists with the and AC_CONTACT Relationsh
30 FAILED flex:E404 debit Business
debit Account customer id _RELMGR ip/Sales
Account
{AccountNo} or Contact Manager
{Account
and partner Relationshi
No} and
p / Sales
partner
Manager

Page 40 of 69
Document Version: 1.3.13

In case of
issues
arising at
Rejected by
upstream
upstream CBS Correct
CBS Retry
Service for the beneficiary AC_RETRY_TX
31 FAILED flex:E449 Service for Business transactio
request details and N
the n
parameters retry
parameter
passed
s passed in
the
request

Invalid Input -
To/Credit
Contact
Account Has Contact
flex:E243 Account is AC_CONTACT Relationsh
32 FAILED Invalid Sales and Business
5 Dormant _RELMGR ip/Sales
Account Support
Manager
Status : 07-
Dormant.

Account
Contact
not found Contact
flex:E285 Account not AC_CONTACT Relationsh
33 FAILED for Sales Business
3 found _RELMGR ip/Sales
debit/cred RM/PSM
Manager
it

Retry
initiating
transaction
s 3 times at
an interval
of 30 mins
Called considering
function has status
had a Fatal remains
Error failed for
Different every
Error in
reference attempt. In Retry
flex:E340 transactio AC_RETRY_TX
34 FAILED number case status Technical transactio
3 n N
passed. still n
processing
Probably, remains
multiple keys failed,
generated in please
same contact
interaction APIL1.helpd
esk@yesban
k.in with
transaction
details
along with
error code
Invalid/In
Provide
correct
Invalid input Incorrect amount in
flex:E683 AC_INVALID_ data in
35 FAILED TransactionA format of correct Business
3 DATA message.
mount amount format and
Update
retry
and retry

Page 41 of 69
Document Version: 1.3.13

Retry
initiating
transaction
s 3 times at
an interval
of 30 mins
considering
status
Unhandled remains
Message failed for
Received - every
This is not Error at attempt. In Retry
flex:E758 AC_RETRY_TX
36 FAILED expected, turn internal case status Technical transactio
5 N
on validation server still n
on remains
HTTPRequest failed,
Node please
contact
APIL1.helpd
esk@yesban
k.in with
transaction
details
along with
error code
Invalid/In
NEFT - Provide
correct
Customer Invalid Correct
flex:E803 AC_INVALID_ data in
37 FAILED Mobile Mobile Mobile Technical
5 DATA message.
number is not Number Number
Update
valid. and retry
and retry

Email Id
and
mobile
number is Contact
not Relationshi
NEFT - Both
mapped to p / Sales Contact
Customer
flex:E803 the debit Manager AC_CONTACT Relationsh
38 FAILED Mobile and Technical
6 account in for _RELMGR ip/Sales
Email is not
core updating Manager
valid.
banking account
system, as details
mandated
by
regulator

Transaction Fund debit

Debit
Amount is account Retry
flex:E803 Account AC_RETRY_TX
39 FAILED Greater Than and then Business transactio
7 has low N
Available perform n
balance
Balance. transaction

Provide
Invalid/In
correct
correct
From Account Incorrect debit
flex:E808 AC_INVALID_ data in
40 FAILED Number is Remitter account Business
6 DATA message.
Invalid. Account and retry
Update
after 30
and retry
mins

Page 42 of 69
Document Version: 1.3.13

Invalid/In
Retry with
Invalid correct
To Account correct
flex:E808 beneficiar AC_INVALID_ data in
41 FAILED Number is Beneficiary Business
7 y account DATA message.
Invalid. /customer
number Update
Account.
and retry

Beneficiar
y IFSC is
Invalid/In
Destination not
Retry with correct
Bank and available
flex:E907 correct AC_INVALID_ data in
42 FAILED Branch could in the Business
2 beneficiary DATA message.
not be respective
IFSC Code Update
resolved. regulator's
and retry
processing
system

Check Invalid/In
Transactio
status of correct
RemitOrg1 - n Failed
flex:E907 transaction AC_INVALID_ data in
43 FAILED Max length due to Business
4 and retry DATA message.
(35) exceeded incorrect
based on Update
mapping
response and retry

Core
banking
rejected
System Rejects Contact
transactio Retry
FLEX:E1 due to YES BANK AC_RETRY_TX
44 FAILED n due to Technical transactio
1017 format/functi support N
format or n
onal issues team
incorrect
client
details.

Retry
initiating
transaction
s 3 times at
an interval
of 30 mins
considering
status
remains
Connectivity Connectivi Retry
failed for AC_RETRY_TX
45 FAILED npci:E02 issue with ty issue Technical transactio
every N
NPCI with NPCI n
attempt. In
case status
still
remains
failed,
please retry
initiating
NEFT
transaction
Retry
initiating
Beneficiar transaction
Transactio
y bank's s 3 times at
n Failed.
CBS is an interval
Please
Acquiring offline or of 30 mins
AC_TXN_FAIL check
46 FAILED npci:E08 Bank CBS or the considering Technical
ED error
node offline connectivi status
descriptio
ty with remains
n and
NPCI is failed for
action
offline every
attempt. In
case status

Page 43 of 69
Document Version: 1.3.13

still
remains
failed,
please retry
initiating
NEFT
transaction

Retry
initiating
transaction
s 3 times at
an interval
of 30 mins
considering
Sorry, this
status
service is
remains
currently Retry
Error at failed for AC_RETRY_TX
47 FAILED npci:ECE unavailable. Technical transactio
server every N
Please try n
attempt. In
again after
case status
sometime.
still
remains
failed,
please retry
initiating
NEFT
transaction
Retry
initiating
transaction
s 3 times at
an interval
Functionality of 30 mins
not yet considering Transactio
Beeneficia
available for status n Failed.
ry bank is
funds transfer remains Please
not
npci:EM based on failed for AC_TXN_FAIL check
48 FAILED enabled Business
P account every ED error
on the
number attempt. In descriptio
respective
through case status n and
channel
beneficiary still action
bank remains
failed,
please retry
initiating
NEFT
transaction
Retry
initiating
transaction
s 3 times at
an interval
of 30 mins
Transactio
considering
n could
npci: status
Transaction not be Retry
EMP remains AC_RETRY_TX
49 FAILED could not be processed Technical transactio
failed for N
processed due to n
every
internal
attempt. In
exception
case status
still
remains
failed,
please retry
initiating

Page 44 of 69
Document Version: 1.3.13

NEFT
transaction

Beneficiar Kindly ask

y bank the
account beneficiary
does not to update
Invalid/In
have account
Invalid correct
relevant details with
Beneficiary AC_INVALID_ data in
50 FAILED npci:EM1 details beneficiary Business
MMID/Mobil DATA message.
mapped bank or
e Number Update
for alternativel
and retry
accepting y process
IMPS transaction
transactio through
ns NEFT

Transactio
Transactio n Failed.
Contact
n Amount Please
beneficiary
Amount limit exceeds AC_TXN_FAIL check
51 FAILED npci:EM2 Or try Business
exceeded IMPS ED error
payment
Maximum descriptio
Type NEFT
Limit n and
action

Beneficiar
Contact
y account
Account Beneficiary Retry
is either AC_RETRY_TX
52 FAILED npci:EM3 blocked/froze before Business transactio
blocked or N
n reinitiating n
in frozen
payment
state

Please
Invalid/In
check
correct
Invalid account
npci:E12 INVALID AC_INVALID_ data in
53 FAILED Beneficiar details with Business
ACCOUNT DATA message.
y Account Bene Bank
Update
and
and retry
reinitiate

Page 45 of 69
Document Version: 1.3.13

Retry
initiating
transaction
s 3 times at
an interval
of 30 mins
considering
status
INVALID remains
AC_RETRY_TX Retry
npci:E01 TRANSACTI Technical failed for
54 FAILED Technical N transactio
ON Decline every
n
attempt. In
case status
still
remains
failed,
please retry
initiating
NEFT
transaction

Please Please
contact check
There is a
Beneficiary account
memo present Issue with AC_TXN_FAIL
55 FAILED npci:E96 some issue Business details
on the Credit Bene Bank ED
with with Bene
account.
Beneficiary Bank and
Bank. reinitiate

Invalid/In
Provide
Amount correct
amount in
Invalid value or AC_INVALID_ data in
56 FAILED npci:E13 correct Business
amount Field tag is DATA message.
format and
incorrect Update
retry
and retry

Page 46 of 69
Document Version: 1.3.13

TRANSACTI Transactio Invalid/In

Transaction
ON NOT n Amount correct
Amount
ALLOWED for IMPS data in
should be AC_INVALID_
57 FAILED npci:E22 AS AMOUNT entered is Business message.
less than 5 DATA
IS GREATER greater Update
Lakhs
THAN 5 than 5 and retry
LAKHS lakh

Retry
initiating
transaction
s 3 times at
an interval
of 30 mins
considering
status
Incorrect
remains
INVALID response AC_RETRY_TX Retry
npci:E20 failed for
58 FAILED RESPONSE received Technical N transactio
every
CODE from n
attempt. In
NPCI
case status
still
remains
failed,
please retry
initiating
NEFT
transaction

Duplicate Transactio
transaction n Failed.
Similar
initiated Please
DUPLICATE transactio
more then AC_TXN_FAIL check
59 FAILED npci:E94 TRANSACTI n initiated Technical
once . ED error
ON more then
Please descriptio
once
recheck the n and
request. action

Page 47 of 69
Document Version: 1.3.13

NO
Issue with
ROUTING Beneficiar
Beneficiary Retry
FOR y Bank AC_RETRY_TX
60 FAILED npci:E92 Bank please Business transactio
INSTITUTIO connectivi N
try after n
N/NETWOR ty failure
sometime
K

Retry
initiating
transaction
s 3 times at
an interval
of 30 mins
considering
VERIFICATIO status
N Failure remains Retry
npci:EM0 SUCCESSFUL received failed for AC_RETRY_TX transactio
61 FAILED Technical
ORGINAL from every N n
TRXN NPCI attempt. In
DECLINED case status
still
remains
failed,
please retry
initiating
NEFT
transaction

Beneficiary
Transactio
account is
n Failed.
FOREIGN Beneficiar an NRE
Please
INWARD y Account Account for
npci:EM AC_TXN_FAIL check
62 FAILED REMITTANC type was which Business
N ED error
E NOT not Domestic
descriptio
ALLOWED Domestic Transaction
n and
s is not
action
permitted.

Page 48 of 69
Document Version: 1.3.13

Transaction is
Transactio
declined Limit
n Failed.
based on Failure Exceeded
Please
transaction response Contact
AC_TXN_FAIL check
63 FAILED npci:EM8 limit imposed received Beneficiary Business
ED error
on the From from or try
descriptio
account type BeneBank NEFT
n and
and To Paymode
action
account type

Transactio
Limit n Failed.
Failure Exceeded Please
Limit response Contact AC_TXN_FAIL check
64 FAILED npci:EM6 exceeded for received Beneficiary Business ED error
member Bank from or try descriptio
BeneBank NEFT n and
Paymode action

Transaction Transactio
Amount n Failed.
Failure
exceeds Please
EXCEEDS response
IMPS AC_TXN_FAIL check
65 FAILED npci:E65 AMOUNT received Business
Maximum ED error
LIMIT from
Limit. Try descriptio
BeneBank
payment n and
Type NEFT action

Page 49 of 69
Document Version: 1.3.13

Beneficiary
account is
an NRE
Account for
There
which Transactio
could be
Beneficiary Domestic n Failed.
some
Bank is not Transaction Please
restriction
enabled for s not AC_TXN_FAIL check
66 FAILED npci:EM4 s at Business
Foreign permitted. ED error
beneficiar
Inward This will descriptio
y bank for
Remittance not come n and
this
for Inward action
account
Remittance
Via
RDA/MTS
S

Transactio
Contact n Failed.
Beneficiary Please
Beneficiar
Account before AC_TXN_FAIL check
67 FAILED npci:EM5 y account Business
closed reinitiating ED error
is closed.
the descriptio
payment n and
action

No Transactio
description Check n Failed.
Transactio
found for status of Please
n Failed
NPCI transaction AC_TXN_FAIL check
68 FAILED npci:E0 due to Technical
response code and retry ED error
incorrect
: 0 in based on descriptio
mapping
ATOM.ERRO response n and
R_MASTER action

Correct the
Invalid Incorrect payload as Retry
AC_RETRY_TX
69 FAILED npci:E30 message message per the Technical transactio
N
format in payload spec and n
retry

Please Please
check check
INVALID AC_INVALID_
70 FAILED npci:E52 account Technical account
ACCOUNT DATA
details with details
Beneficiary Bene Bank with Bene
Not and Bank and
Acceptable reinitiate reinitiate

No Transactio
description Check n Failed.
Transactio
found for status of Please
n Failed
NPCI transaction AC_TXN_FAIL check
71 FAILED npci:E80 due to Technical
response code and retry ED error
incorrect
: 80 in based on descriptio
mapping
ATOM.ERRO response n and
R_MASTER action

Page 50 of 69
Document Version: 1.3.13

Retry
initiating
transaction
s 3 times at
an interval
of 30 mins
considering
status
remains
Transactio
failed for
n Failed.
In case of every
Rejected/Faile Please
technical attempt. In
npci:E30 d at AC_TXN_FAIL check
72 FAILED issues at case status Technical
7 beneficiary ED error
beneficiar still
bank descriptio
y bank remains
n and
failed,
action
please
contact
APIL1.helpd
esk@yesban
k.in with
transaction
details
along with
error code.
Transactio
Rejected n Failed.
Rejected by by Please
npci:E30 beneficiary beneficiar Contact AC_TXN_FAIL check
73 FAILED Business
8 bank in y bank in Support ED error
reconciliation reconciliat descriptio
ion n and
action
Rejected
by the
Transactio
beneficiar
Rejected by n Failed.
y bank
beneficiary Correct Please
when the
npci:E44 bank for beneficiary AC_TXN_FAIL check
74 FAILED details Business
9 request details and ED error
passed in
parameters retry descriptio
the
passed n and
request
action
are not
correct
Transactio
Contact n Failed.
Transactio Customer Please
npci:E45 Beneficiary n failed at and get AC_TXN_FAIL check
75 FAILED Business
0 bank rejection beneficiar alternate ED error
y bank beneficiary descriptio
account n and
action

Check
status of
transaction
Error at after 30 Retry
AC_RETRY_TX
76 FAILED atom:E11 CBS ISSUE IMPS mins Technical transactio
N
switch interval n
and retry
based on
response

Page 51 of 69
Document Version: 1.3.13

Technical
failure
Retry
initiating
transaction
s 3 times at
an interval
of 30 mins
considering
status
remains
In case of
failed for
issues
Rejected/Faile every Retry
atom:E30 arising at AC_RETRY_TX
77 FAILED d at upstream attempt. In Technical transactio
7 upstream N
IMPS Service case status n
IMPS
still
Service
remains
failed,
please
contact
APIL1.helpd
esk@yesban
k.in with
transaction
details
along with
error code.

Pass correct
There is a
combinatio
mismatch
n of A/C
in the
No number,
account
Relationship Partner Id Contact
number
atom:E40 Exists with the and cust id AC_CONTACT Relationsh
78 FAILED and Technical
4 debit Account or Contact _RELMGR ip/Sales
customer
{AccountNo} Relationshi Manager
id being
and partner p / Sales
passed in
Manager
the
for
request
assistance

In case of
issues
arising at
Rejected by
upstream
upstream Correct
IMPS Retry
atom:E44 IMPS Service beneficiary AC_RETRY_TX
79 FAILED Service for Business transactio
9 for the request details and N
the n
parameters retry
parameter
passed
s passed in
the
request

IMPS
system Transactio
rejected n Failed.
System Rejects transactio Please
Try NEFT
ATOM:E due to n due to AC_TXN_FAIL check
80 FAILED OR Refund Business
450 format/functi format or ED error
money
onal issues incorrect descriptio
client/ben n and
eficiary action
details.

Page 52 of 69
Document Version: 1.3.13

Retry
initiating
transaction
s 3 times at
an interval
of 30 mins
considering
status
remains
failed for
Sorry, we are
every
unable to
attempt. In Retry
atom:EA process your Error at AC_RETRY_TX
81 FAILED case status Technical transactio
19 request. server N
still n
Please try
remains
again later.
failed,
please
contact
APIL1.helpd
esk@yesban
k.in with
transaction
details
along with
error code.

Check
status of
An
Error in transaction
Unhandled Retry
transactio and retry AC_RETRY_TX
82 FAILED sfms:99 Exception Technical transactio
n after 30 N
Occurred In n
processing mins based
Processing
on the
response

Failed in
Transactio
payment
Transactio n Failed.
body's
n is not Please
system,
Rejected by accepted AC_TXN_FAIL check
83 FAILED sfms:E18 Kindly Business
SFMS by the ED error
reinitiate or
payment descriptio
refund
body. n and
your
action
customer

Retry
initiating
transaction
s 3 times at
an interval
of 30 mins
considering
status
remains
failed for
every Retry
Authorisation Technical AC_RETRY_TX
84 FAILED sfms:E55 attempt. In Business transactio
Complete Failure N
case status n
still
remains
failed,
please
contact
APIL1.helpd
esk@yesban
k.in with
transaction
details
Page 53 of 69
Document Version: 1.3.13

along with
error code.

Retry
initiating
transaction
s 3 times at
an interval
of 30 mins
considering
status
remains
failed for
every
attempt. In Retry
Message Technical AC_RETRY_TX
85 FAILED sfms:E59 case status Technical transactio
Encoded failure N
still n
remains
failed,
please
contact
APIL1.helpd
esk@yesban
k.in with
transaction
details
along with
error code.

Failed in
Transactio
Transactio payment
n Failed.
n is in body's
Please
Outward error due system,
AC_TXN_FAIL check
86 FAILED sfms:E70 Transaction to issue Kindly Business
ED error
Rejected with the reinitiate or
descriptio
transactio refund
n and
n details. your
action
customer

Failed in
Transactio
Transactio payment
n Failed.
n is in body's
Please
Manually error due system,
AC_TXN_FAIL check
87 FAILED sfms:E99 Marked in to issue Kindly Business
ED error
Error with the reinitiate or
descriptio
transactio refund
n and
n details. your
action
customer

Transactio
The IMPS n Failed.
transaction Returned Please
Contact
sfms:ERE has reversed from AC_TXN_FAIL check
88 FAILED Beneficiary Business
V back to Beneficiar ED error
Bank
remitter y Bank descriptio
account n and
action

Page 54 of 69
Document Version: 1.3.13

IMPS:
IMPS: Check
Transactio status after
n accepted 1 hour.
by NPCI Transaction
but no status
Retry
response expected to
AC_RETRY_GE GetStatus
89 SettlementInProcess received clear to
TSTATUS after 30
from COMPLET
minutes
beneficiar ED/
y bank FAILED
within the after 2
time limit working
set days in
most cases.

NEFT:
Check
status after
NEFT: 1 hour in
Transactio NEFT
n has been working
accepted window. If
Retry
by RBI but transaction
AC_RETRY_GE GetStatus
90 SettlementInProcess the has been
TSTATUS after 30
acknowle posted after
minutes
dgement NEFT Cut-
has not yet off time
been then check
received the status
on next
working
day
Check
status 4
times in
30mins and
get in touch
with L2
Retry
Error at Support
Internal AC_RETRY_GE GetStatus
91* SettlementInProcess ns:E500 internal Team in Technical
Server Error TSTATUS after 30
server case of
minutes
error.
Retry with
a valid
Request
Reference
Number
Check
status 4
times in
30mins and
get in touch
with L2
Retry
Error at Support
Internal AC_RETRY_GE GetStatus
92* FAILED ns:E500 internal Team in Technical
Server Error TSTATUS after 30
server case of
minutes
error.
Retry with
a valid
Request
Reference
Number

Page 55 of 69
Document Version: 1.3.13

An
Do Get
upstream
status after Retry
service
30 Minutes AC_RETRY_GE GetStatus
93 SettlementInProcess ns:E502 Bad Gateway returned Technical
and act TSTATUS after 30
an
basis the minutes
unexpecte
response
d error

Do Get
An status after Retry
Gateway upstream 30 Minutes AC_RETRY_GE GetStatus
94 SettlementInProcess ns:E504 Technical
Timeout service and act TSTATUS after 30
times out basis the minutes
response

A request was
Transactio
found, but a Do Get
n is in
corresponding status after Retry
error due
entry for IMPS 30 Minutes AC_RETRY_GE GetStatus
95 SettlementInProcess ns:E9001 to issue Technical
in CBS and act TSTATUS after 30
with the
(transaction_ basis the minutes
transactio
master) for response
n details.
Ref

Failed
A request was while
Outward
found, but a processing
transactio
corresponding at Retry
n is
entry for Remitter's AC_RETRY_GE GetStatus
96 SettlementInProcess ns:E9002 rejected by Technical
NEFT in CBS end , TSTATUS after 30
the
(pm_bulk_ms Kindly minutes
payment
g_details) for reinitiate
body
Ref after 30
Minutes

No
description
Transactio
found for
n response Retry Retry
NPCI
npci:EN from getStatus AC_RETRY_GE GetStatus
97 SettlementInProcess response code
A beneficiar after 30 TSTATUS after 30
: NA in
y bank mins minutes
ATOM.ERRO
awaited
R_MASTER
80

IMPS:
Check
status after
3 hours.
Transaction
Kindly status
Retry
confirm with expected to
Error in AC_RETRY_GE GetStatus
98 SettlementInProcess npci:E91 YES Bank clear to Business
processing TSTATUS after 30
before COMPLET
minutes
reinitiating ED/
FAILED
after 2
working
days in
most cases.

Page 56 of 69
Document Version: 1.3.13

If status
does not
change,
please
contact
support
Retry
initiating
transaction
s 3 times at
an interval
of 30 mins
considering
status
Kindly
remains Retry
confirm with
Error in failed for AC_RETRY_GE GetStatus
99* FAILED npci:E91 YES Bank Business
processing every TSTATUS after 30
before
attempt. In minutes
reinitiating
case status
still
remains
failed,
please retry
initiating
NEFT
transaction

Retry get
status after
Transactio Retry
every 30
Authorisation n sent to AC_RETRY_GE GetStatus
100 SettlementInProcess sfms:E55 mins Business
Complete beneficiar TSTATUS after 30
interval till
y bank minutes
success is
received

Transactio
Transactio Check with n Failed.
n accepted Beneficiary Please
by RBI but before AC_TXN_FAIL check
101 SettlementReversed Business
beneficiar reinitiating ED error
y bank the descriptio
rejected it. payment n and
action

Transactio
Beneficiar
Multiple n Failed.
y bank
reasons why Please
could not
beneficiary Return the AC_TXN_FAIL check
102 SettlementReversed sfms:E62 credit to Technical
account could beneficiary ED error
the
not be descriptio
beneficiar
credited n and
y account
action

Do Get
status after Retry
Transactio
30 Minutes AC_RETRY_GE GetStatus
103 Pending n is under Technical
and act TSTATUS after 30
process
basis the minutes
response

Failed atom:EA Internal Internal Check Technical

19 Server Error Server status of
Error transaction Retry
and retry AC_RETRY_GE GetStatus
104
based on TSTATUS after 30
response minutes

Page 57 of 69
Document Version: 1.3.13

Failed atom:E Rejected/Faile Rejected/ Check Technical

d at Failed at status of
1001 Retry
downstream downstrea transaction
system m system and retry AC_RETRY_GE GetStatus
105
based on TSTATUS after 30
response minutes

Failed atom:E Rejected/Faile Rejected/ Check Technical

d at Failed at status of
1003 Retry
downstream downstrea transaction
system m system and retry AC_RETRY_GE GetStatus
106
based on TSTATUS after 30
response minutes

Failed atom:E Rejected/Faile Rejected/ Check Technical

d at Failed at status of
1206 Retry
downstream downstrea transaction
system m system and retry AC_RETRY_GE GetStatus
107
based on TSTATUS after 30
response minutes

Failed atom:E Rejected by Check Technical

downstream Rejected status of
2778
system for the by transaction
request downstrea and retry Retry
parameters m system based on AC_RETRY_GE GetStatus
108
passed for the response TSTATUS after 30
request minutes
parameter
s passed

Failed atom:E Bad Gateway Bad Retry Technical

Gateway
3403 Retry
AC_RETRY_GE GetStatus
109
TSTATUS after 30
minutes

Failed atom:E Rejected by Rejected Check Technical

downstream by status of
3769
system for the downstrea transaction
Retry
request m system and
AC_RETRY_GE GetStatus
110 parameters for the Correct
TSTATUS after 30
passed request parameters
minutes
parameter retry based
s passed on response

Failed atom:E INVALID INVALID Retry with Business

ACCOUNT ACCOUN Correct Invalid/In
52 correct
T Beneficiary AC_INVALID_
details data in
111 DATA
message.
Update
and retry

Failed atom:E Rejected by Rejected Check Technical

downstream by status of
8087
system for the downstrea transaction
Retry
request m system and
AC_RETRY_GE GetStatus
112 parameters for the Correct
TSTATUS after 30
passed request parameters
minutes
parameter retry based
s passed on response

Page 58 of 69
Document Version: 1.3.13

Failed atom:E NO NO Retry with Business

ROUTING ROUTING Correct Be Invalid/In
92 correct
FOR FOR neficiary AC_INVALID_
INSTITUTIO INSTITUT Bank data in
113 DATA
N/NETWOR ION/NET Account D message.
K WORK etails Update
and retry

Failed atom:E Invalid Invalid Check Technical

Mobile/Acco Mobile/A status of Invalid/In
A52
unt Number ccount transaction correct
AC_INVALID_
Number and data in
114 DATA
Correct message.
parameters Update
retry based and retry
on response
Failed atom:E Rejected/Faile Rejected/ Check Technical
d at Failed at status of
DR Retry
downstream downstrea transaction
system m system and retry AC_RETRY_GE GetStatus
115
based on TSTATUS after 30
response minutes

Failed atom:E Rejected/Faile Rejected/ Check Technical

d at Failed at status of
EXT_R Retry
downstream downstrea transaction
SP9010 system m system and retry AC_RETRY_GE GetStatus
116
based on TSTATUS after 30
response minutes

Failed atom:E There is a There is a

memo present memo
EXT_R Contact
on the Debit present on AC_CONTACT
SP9011 Account the Debit Relationsh
117 _RELMGR
Account ip/Sales
Manager

Failed atom:E Rejected/Faile Rejected/ Check Technical

d at Failed at status of
EXT_R Retry
downstream downstrea transaction
SP9014 system m system and retry AC_RETRY_GE GetStatus
118
1 based on TSTATUS after 30
response minutes

Failed atom:E Rejected/Faile Rejected/ Check Technical

d at Failed at status of
EXT_R Retry
downstream downstrea transaction
SP9014 system m system and retry AC_RETRY_GE GetStatus
119
2 based on TSTATUS after 30
response minutes

Failed atom:E Insufficient Insufficien Credit the Business Transactio

Balance in t Balance account and n Failed.
EXT_R
debit account, in debit retry Please
SP9014 AC_TXN_FAIL
payment account, transaction check
120 ED
5 required payment error
required descriptio
n and
action

Page 59 of 69
Document Version: 1.3.13

Failed atom:E Hold Funds Hold Contact Business

Present - Refer Funds Sales
EXT_R
to Drawer Present - RM/PSM
SP9018 (Account Refer to Contact
AC_CONTACT
would Drawer Relationsh
121 _RELMGR
Overdraw) (Account ip/Sales
would Manager
Overdraw
)

Failed atom:E Rejected/Faile Rejected/ Check Technical

d at Failed at status of
EXT_R Retry
downstream downstrea transaction
SP9027 system m system and retry AC_RETRY_GE GetStatus
122
0 based on TSTATUS after 30
response minutes

Failed flex:E3 Rejected/Faile Rejected/ Check Technical

d at Failed at status of
403 Retry
downstream downstrea transaction
system m system and retry AC_RETRY_GE GetStatus
123
based on TSTATUS after 30
response minutes

Failed npci:E0 Rejected/Faile Rejected/ Retry with Business

d at Failed at Correct Be Invalid/In
4 correct
beneficiary beneficiar neficiary AC_INVALID_
bank y bank Bank data in
124 DATA
Account D message.
etails Update
and retry

Failed npci:E1 Rejected/Faile Rejected/ Retry with Business

d at Failed at Correct Be Invalid/In
0 correct
beneficiary beneficiar neficiary AC_INVALID_
bank y bank Bank data in
125 DATA
Account D message.
etails Update
and retry

Failed npci:E1 Rejected/Faile Rejected/ Check Technical

d at Failed at status of
4 Retry
downstream downstrea transaction
system m system and retry AC_RETRY_GE GetStatus
126
based on TSTATUS after 30
response minutes

Failed npci:E Beneficiary Beneficiar Verify Business

bank rejection y bank beneficiary Invalid/In
M7 correct
rejection account AC_INVALID_
details data in
127 DATA
message.
Update
and retry

Failed npci:E Beneficiary Beneficiar Verify bene Business

bank rejection y bank account Invalid/In
MR correct
rejection details AC_INVALID_
data in
128 DATA
message.
Update
and retry

Page 60 of 69
Document Version: 1.3.13

Failed npci:E Customer Validation Contact Business Technical

Transaction at beneficiary
MI error /
Limit Beneficiar AC_CONTACT Invalid
129 Exceeded y Bank _SUPPORT message.
Contact
Support

Failed npci:E Invalid When Contact Business

Beneficiary invalid beneficiary Invalid/In
MJ correct
IFSC Code or IFSC or AC_INVALID_
NBIN NBIN is data in
130 DATA
entered message.
Update
and retry

Failed npci:E Transaction Validation Contact Business Technical

Not Allowed at beneficiary
MQ error /
As Invalid Beneficair AC_CONTACT Invalid
131 Payment y Bank _SUPPORT message.
Reference Contact
Support

Failed npci:E Transaction In case of Retry Technical

Not Allowed technical initiating
MT
As General issues at transactions
Error beneficiar 3 times at
y bank an interval
of 30 mins
considering
status
remains Retry
failed for AC_RETRY_GE GetStatus
132
every TSTATUS after 30
attempt. In minutes
case status
still
remains
failed,
please retry
initiating
NEFT
transaction
Failed npci:E6 Exceeds Validation Contact Business
Account Limit at beneficiary Technical
1 error /
Beneficiar AC_CONTACT
y Bank Invalid
133 _SUPPORT
message.
Contact
Support

ACCEPTED The As this is Do Business Do

transactions the getstatus as getstatus
have reached functionali per the as per the
YBL ty of minimum minimum
Applicatio TAT of 30 TAT of 30
n, the min and till min and
status of the DP_SAF_TRA till the
134 NSACTIONS
transactio transaction transactio
ns is has reached n has
Accepted their reached
as it terminals. their
passes terminals.
SAF

Page 61 of 69
Document Version: 1.3.13

Failed ns:E506 Error While Technical Retry the Technical Transactio

Executing Failure transaction n Failed.
Datatbase Call with valid Please
reference retry the
no. AC_TXN_FAIL transactio
135 n after
ED taking
confirmati
on from
Support
Team.
Failed ns:E507 Error While Technical Retry the Technical Transactio
Fetching Data Failure transaction n Failed.
From Backend with valid Please
For reference retry the
Beneficiary no. AC_TXN_FAIL transactio
136 Code n after
ED taking
confirmati
on from
Support
Team.
Retry
initiating
transactions
3 times at
an interval
of 30 mins
considering
status
remains
UNABLE TO Retry
Technical failed for AC_RETRY_TX
137 FAILED npci:EUB PROCESS
Failure every
Technical
N
transactio
n
attempt. In
case status
still
remains
failed,
please retry
initiating
NEFT
transaction
Retry
initiating
transactions
3 times at
an interval
of 30 mins
considering
status
remains
INVALID Retry
npci:EE1 Technical failed for AC_RETRY_TX
138 FAILED
5
RESPONSE
Failure every
Technical
N
transactio
CODE n
attempt. In
case status
still
remains
failed,
please retry
initiating
NEFT
transaction
Retry
initiating
Incorrect transactions Retry
INVALID AC_RETRY_TX
139 FAILED npci:EXF
MESSAGE
message 3 times at Technical
N
transactio
in payload an interval n
of 30 mins
considering

Page 62 of 69
Document Version: 1.3.13

status
remains
failed for
every
attempt. In
case status
still
remains
failed,
please retry
initiating
NEFT
transaction
Transaction Transactio
Amount n Failed.
TRANSFER Validation exceeds Please
AC_TXN_FAIL
AMOUNT at IMPS check
140 FAILED npci:E78
EXCEEDS Beneficiar Maximum
Business ED
error
LIMIT y Bank Limit. Try descriptio
payment n and
Type NEFT action
Retry
initiating
transactions
3 times at
an interval
of 30 mins
considering
status
INVALID remains
Retry
TRANSACTI Technical failed for AC_RETRY_TX
141 FAILED npci:EXC
ON Decline every
Technical
N
transactio
n
attempt. In
case status
still
remains
failed,
please retry
initiating
NEFT
transaction
SUSPECTED Transactio
FRAUD, n Failed.
DECLINE Validation Please
AC_TXN_FAIL
npci:E59 TRANSACTI at Contact check
142 FAILED
ONS Beneficiar Beneficiary
Business ED
error
DECLINED y Bank descriptio
BASIS RISK n and
SCORE action

Invalid/In
Provide
correct
INVALID Incorrect amount in
AC_INVALID_ data in
143 FAILED npci:EXD AMOUNT amount correct Technical
DATA message.
FIELD format format and
Update
retry
and retry

Retry
initiating
transactions
3 times at
an interval
of 30 mins Retry
UNABLE TO Technical AC_RETRY_TX
144 FAILED npci:E39
PROCESS Failure
considering Technical
N
transactio
status n
remains
failed for
every
attempt. In
case status
Page 63 of 69
Document Version: 1.3.13

still
remains
failed,
please retry
initiating
NEFT
transaction

Response
Some issue
received Transactio
at
from NPCI n Failed.
Beneficiary
INSUFFICEN where there Please
Bank, please
is an AC_TXN_FAIL
T BALANCE check with check
145 FAILED npci:E24
IN POOL
insufficient
the
Business ED
error
balance in
A/C Beneficiary descriptio
pool
and then n and
account of
retry action
beneficiary
bank

Invalid/In
Validation correct
EXCEEDS
at Contact AC_INVALID_ data in
146 FAILED npci:E17 ACCOUNT
Beneficiar beneficiary
Business
DATA message.
LIMIT
y Bank Update
and retry

There is a Contact
npci:EEX Account Contact
memo present AC_CONTACT Relationsh
147 FAILED T_RSP90
on the Debit
cannot be Sales Business
_RELMGR ip/Sales
11 debited RM/PSM
account. Manager

Please Enter a
Value Please
Recheck
benAccountN recheck Retry
Beneficiar AC_RETRY_TX
148 FAILED npci:EE o Field
y Account
Beneficiary Business
N
transactio
Between 1 Account n
No.
And 30 No.
Characters

Retry the
transaction Retry
BENEFICIAR Beneficiar
npci:EU7 with AC_RETRY_TX transactio
149 FAILED
8
Y BANK y Bank is
different
Technical
N n
OFFLINE offline
reference
no.

BENEFICIAR Retry the

Y BANK Validation transaction Retry
npci:EU8 DEEMED at with AC_RETRY_TX transactio
150 FAILED
4 CHECK Beneficiar different
Technical
N n
DECLINE y Bank reference
no.

Retry the
CONNECTIO
transaction Retry
N TIMEOUT
npci:EU8 Connectio with AC_RETRY_TX transactio
151 FAILED
8
IN REQPAY
n Timeout different
Technical
N n
CREDIT
reference
no.

Page 64 of 69
Document Version: 1.3.13

Decline as
BENEFICIAR Downtime there is a
Retry
Y scheduled scheduled
npci:EU AC_RETRY_TX transactio
152 FAILED
Q1
SCHEDULED at downtime Technical
N n
OFFLINE Beneficiar at
y Bank Beneficiary
Bank
Retry as
NPCI has
NPCI has
not
BANK not
received
REQUEST received
ACKNOW Retry
CREDIT PAY ACKNOW
npci:EU2 LEDGEM AC_RETRY_TX transactio
153 FAILED
6
ACKNOWLE
ENT for
LEDGEME Technical
N n
DGEMENT IS NT for
ReqPay
NOT ReqPay
from
RECEIVED from
Beneficiar
Beneficiary
y Bank
Bank
Decline as
the Risk
Score
maintained
TRANSACTI at
Validation Retry
ON Beneficiary
npci:EU1 at AC_RETRY_TX transactio
154 FAILED
6
DECLINED
Beneficiar
Bank for Business
N n
BASED ON Beneficiary
y Bank
RISK SCORE account
does not
permit the
transaction

Decline as
NPCI is
NPCI is not
not able to
able to
connect/r
connect/rec Retry
BENEFICIAR eceive
npci:EUZ eive AC_RETRY_TX transactio
155 FAILED
3
Y FORCED heartbeat
heartbeat Technical
N n
OFFLINE request
request
from
from
Beneficiar
Beneficiary
y Bank
Bank
Retry if
beneficiary
account has
been
enabled by
beneficiary
bank for
IMPS
Invalid transactions
Invalid Bene Bene . Retry with Retry
Mobile Mobile correct Business AC_RETRY_TX transactio
156 FAILED npci:EM1
number/Acco number/ Beneficiary N n
unt Details Account Mobile
Details no/MMID/
Account
No/IFSC
code.
Alternativel
y process
transaction
through
NEFT

Page 65 of 69
Document Version: 1.3.13

Current Transactio
Balance + n Failed.
Insufficient
npci: OD limit Please
Funds - Fund the AC_TXN_FAIL
of Debit check
157 Failed EEXT_R Account in
account is
Debit Business ED
error
SP9901 Overline/TO Account
less than descriptio
D
transactio n and
n amount action

*Note :

Received ns: E500 error code in Status enquiry- (GetStatus API) This error is received when
there is connectivity failure in downstream system at banks end. Recommended action-

 Check if there is any email notification from Yesbank on Down time.

 Please do not mark the transaction as Failed, can keep the status as Pending.
 Check status Enquiry 4 times in duration of half an hour to check the updated status if
received ns:E500.
 If reference number is not generated then please reinitiate request with same request number,
If CBS reference number is generated then raise request to L2 support team on mail and
accordingly take decision on the status of the transaction. In case client system does not allow
to reinitiate with same request number then raise request to L2 support team on mail and
accordingly take decision on the status of the transaction.

Received ns: E404 – as the payment request for which you are checking status have not
reached us or old request beyond 30 days is migrated.
Recommended action:
 Please do not check status instantly after sending Payment request. We suggest checking the
status by calling payment-details API according to mentioned duration for respective pay
mode.
 Check status thrice after 30 min of initiating a transaction. On same response please initiate
new request with same request number. In case client system does not allow to reinitiate with
same request number then raise request to L2 support team on mail and accordingly take
decision on the status of the transaction.
 Recommended process for transaction status of transactions more than 30 days, please refer
the section Duplicate check.

Received ns: E429: Please do not re-initiate the transaction as this is the limit on request of API calls
not status of the transaction. Please do call the status API to get the updated status of the transactions

Received npci:E91 with Failed status : If status gives Failed instead of SettlementInProcess.
Raise to L2 support team on mail and accordingly take decision on the status of the
transaction

Received npci:E5XX with Failed status : If status gives Failed along with ns:E5XX, please keep it
pending and Kindly share the impacted cases with L2 Support . Additionally, have a logic
implemented in your respective system for handling this error code.

Page 66 of 69
 Document Version: 1.3.13

Section 4: Schema Level validations

Schema Level validations which will be thrown upfront

# Code SubCode Meaning When Does it Come Recommended payment domest fund- Error
Action -details ic- confirma Classificati
payme tion on
nts
1 Sender ns:E400 Bad Request When any request Fix the Request Y Y Y Technical
elements fail schema (Likely Schema
validation. Validation
Error)

If it is a payment
request, fix the
payment request
& if it is a status
check request,
fix the status
check request

2 Sender ns:E403 Customer / Account The Basic The Basic Y Y Y Technical

Access Forbidden Authorization User ID Authorization
& Password pair sent User ID &
in the request, was not Password are
found in the provided to you
configuration. by the bank.
Ensure that you
are using the
correct values. If
you believe you
are, then contact
support.

3 Sender ns:E401 401 Unauthorized The credentials passed Please retry Y Y Y Technical
is not correct using correct
credentials

**Kindly refer to fault error code for action on transaction status, fault code in Header is FYI**

HTTP Errors

Page 67 of 69
 Document Version: 1.3.13

# HTTP Status Meaning When does it come Recommended Error

code Action Classification

1 401 Authorization Required User credentials are invalid The Basic Technical
Authorization User
ID & Password are
provided to you by
the bank. Ensure
that you are using
the correct values.
If you believe you
are, then contact
support.
2 404 Not Found Incorrect EndPoint Contact Support Technical
after verifying the
endpoints
3 429 (Limit Daily/transaction/rate) Number of requests that Retry next day Technical
exceeded have come from you have
exceeded the permissible
limit set at Data Power
4 500 Internal Server Error Error at Internal Server Retry Get status Technical
after 30 Mins

Note:
Received HttpCode 500 error in response to the Fund transfer API/start Transfer API and/or in Get
status API due to requests timeouts/ by an error on the target/backend server:
• Please do not mark the transaction as Failed, can keep the status as Pending.
• Check status Enquiry in duration of half an hour to check the updated status if received http500
while initiating start transfer/fund transfer API
• Check status Enquiry in duration of 10-15 mins to check the updated status if received http500
while calling the Get status API to check the status of the transaction
• Raise to L2 support team on mail and accordingly take decision on the status of the transaction

If Status API doesn’t give the finality of the transaction, get in touch with YBL support Team (Refer
escalation matrix in Section 5)

Section 5: Escalation Matrix

Issue TAT Support Team Escalation

Status of timed out IMPS 1 working DLCSE_PSRM@yesbank.in 1st level - DLCSE_PSRM@yesbank.in
transactions after prescribed day Tel - 2nd Level - Product Sales Manager
TAT of calling getStatus API 3rd Level -
DLTBGCMSPAYMENTSPRODUCT@ye
sbank.in
Raise Chargeback As per Cms.helpdesk@yesbank.in 1st Level - Product Sales Manager,
Beneficiary 2nd Level -
bank TAT DLTBGCMSPAYMENTSPRODUCT@ye
sbank.in
Issue in reports or bank 1 working DLCSE_PSRM@yesbank.in 1st Level - Product Sales Manager,
statement generation / day Tel - 2nd Level -
delivery DLTBGCMSPAYMENTSPRODUCT@ye
sbank.in
Status of txn / URN not 1 working DLCSE_PSRM@yesbank.in 1st Level - DLCSE_PSRM@yesbank.in
available through your day Tel - 2nd Level -
getStatus API call. Please DLTBGImplementation@yesbank.in

Page 68 of 69
 Document Version: 1.3.13

provide URN and Bank

Reference Number to support
team while raising the query

URN stuck in IN_PROCESS or 1 working DLCSE_PSRM@yesbank.in 1st Level - DLCSE_PSRM@yesbank.in

SENT_TO_BENEFICIARY day Tel - 2nd Level -
state the following day of txn DLTBGImplementation@yesbank.in
initiation
Network and Technical Issue 1 working DLESBL2Support@yesbank.in 1st level -
day Tel - 022-33478167/022- Prashant.bornare.ext@yesbank.in
33479084 2nd level – amresh.penkar@yesbank.in

Page 69 of 69