Revised PI: Update payment details
Last updated
Was this helpful?
Last updated
Was this helpful?
Payment Instruction
Status Update for Successful Payment Details of Revised PIs
Employee
Role: System
Success Payment Details (FTPS) is the API to fetch the payment details of revised PI from JIT.
For Request/ Response parameters, please refer the .
The response data is stored and maintained at MUKTASoft for every FTPS call.
The API call to be scheduled once in a day at 10 PM for In Process payment instruction.
#
Parameter
Description
1
jitCorBillNo
PI ID of revised PI generated in MUKTASoft to re-push failed transactions into JIT
2
jitCorBillDate
PI date of revised PI generated in MUKTASoft to re-push failed transactions into JIT
3
jitCorBillDeptCode
Application code.
4
jitOrgBillRefNo
Original online bill reference no. in JIT while payment failed first time.
5
jitOrgBillNo
Original Payment Instruction ID in MUKTASoft while payment failed first time.
6
jitOrgBillDate
Original Payment Instruction Date in MUKTASoft while payment failed first time.
#
Parameter
Description
1
jitCorBillNo
Revised PI ID generated in MUKTASoft and push failed transactions into JIT
2
jitCorBillDate
Revised PI date generated in MUKTASoft and push failed transactions into JIT
3
jitOrgBillRefNo
Original, the first online bill reference number generated in JIT.
4
voucherNumber
The voucher number of voucher generated in JIT to maintain the accounting.
5
voucherDate
The voucher creation date for the voucher created in JIT for payment.
6
billRefNo
Online bill reference number for revised PI/ Current PI.
7
paymentStatus
Payment status, message received from RBI at the time of Debit Scroll.
8
tokenNumber
Token number generated in JIT.
9
tokenDate
Token date generated in JIT.
Beneficiary Details
10
benfAcctNo
Beneficiary’s account number.
11
benfBankIfscCode
Beneficiary’s bank / branch IFSC.
12
utrNo
Unique transaction reference number used by banks to reconcile the transaction.
13
utrDate
UTR date.
14
endToEndId
It is generated to identify a beneficiary for a transaction while it is pushed to CPC for payment clearance.
15
benfId
Beneficiary unique ID, unique to transaction.
Error message displayed on View Payment Instruction Page. [Message: On call of FTPS API: No response is received.]
PI status at MUKTASoft remain unchanged to In Process.
All beneficiaries payment status remain unchanged to Payment In Process.
Option to refresh the status is provided. It triggers call of FTPS.
Error message is stored at MUKTASoft.
Error message displayed on View Payment Instruction Page. [Message: On call of FTPS API: <JIT error message>]
PI status at MUKTASoft remain unchanged to In Process
All beneficiaries payment status remain unchanged to Payment In Process
Option to refresh the status is provided. It triggers call of FTPS.
Success message is received and same is stored at MUKTASoft.
Info message displayed on View Payment Instruction Page. [Message: On call of FTPS API: Response is received and updated successfully]
PI status at the MUKTASoft changes to Completed.
The beneficiaries payment status is changed to Payment Successful.
No action is enabled.
#
Response
PI Status (From)
PI Status (To)
Payment Status
User Action
API Call
1
No Response
In Process
In Process
Payment In Process
Refresh
FTPS
2
Response With Error
In Process
In Process
Payment In Process
Refresh
FTPS
3
Response Without Error
In Process
Completed
Payment Successful
No Action
Not applicable.
Not applicable.
Not applicable.
Not applicable.
Not applicable.
To all the beneficiaries:
Payment of Rs. {amount} for MUKTA, transaction <UTRNO> is made to your registered bank account. Contact your bank if not credited within 72 hours. MUKTA - Govt. of Odisha.
View Payment Instruction
API is called and status is fetched and updated for both PI and Beneficiary.
SMS notification is sent to all the beneficiaries.
Status is reflected in View Payment Instruction Page.
The response is captured in MUKTASoft for debugging and error reporting.
Technical glitched in the integration are defined as error and captured.
System keep trying until a response is received. The latest response is recorded in the log.