Excess payment transaction details
get
/service/v1/excessPaymentInq
This endpoint is used to fetch the excess payment transaction details basis of payment reference number.
Request
Supported Media Types
- application/json
- application/xml
Query Parameters
Header Parameters
Back to Top
Response
Supported Media Types
- application/json
- application/xml
200 Response
Successful performs the operation
Root Schema : ExcessPaymentInqResponseModel
Type:
Show Source
object
-
currency:
string
Excess Payment Currency
-
excessPaymentAmt:
number
Excess Payment Amount
-
excessPaymentRefNo:
string
Excess Payment Reference Number
-
paymentRefNo:
string
Payment Reference No
-
reconciledTxnDet:
array reconciledTxnDet
-
refundTxnModelArr:
array refundTxnModelArr
-
valueDate:
string
Value Date
Nested Schema : ReconciledTxnModel
Type:
Show Source
object
-
amount:
number
Excess Payment Reconciled/Refunded Amount
-
beneAccNo:
string
Beneficiary Account Number
-
beneIfscCode:
string
Beneficiary IFSC Code
-
beneName:
string
Beneficiary Name
-
currency:
string
Excess Payment Currency
-
reconRule:
string
recon Rule
-
reconRuleType:
string
recon Rule Type
-
reconRuleVersion:
number
recon Rule Version
-
reconType:
string
recon Type
-
ruleDescription:
string
rule Description
-
status:
string
Payment Status
-
txnRefNo:
string
Reconciled Transaction Reference Number
-
utrRefNo:
string
UTR Reference Number
Nested Schema : RefundTxnModel
Type:
Show Source
object
-
amount:
number
Excess Payment Reconciled/Refunded Amount
-
beneAccNo:
string
Beneficiary Account Number
-
beneIfscCode:
string
Beneficiary IFSC Code
-
beneName:
string
Beneficiary Name
-
currency:
string
Excess Payment Currency
-
status:
string
Payment Status
-
txnRefNo:
string
Reconciled Transaction Reference Number
-
utrRefNo:
string
UTR Reference Number
400 Response
Malformed syntax.
401 Response
Request does not have sufficient credentials.
403 Response
Request is not authorized.
500 Response
Internal error