Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Payment Instruction
Status Update for Payment Advice
Employee
Role: System
Payment Advice Status (PAG) is the API to fetch the payment advice status from JIT.
Once a PI is accepted at JIT, it is then approved with a digital sign by SSU in JIT.
For approved PI then payment advice is generated.
For Request/ Response parameters, please refer the integration approach document.
The response data is stored and maintained at MUKTASoft for every PAG call.
The API call to be scheduled once in a day at 10:15 PM every day for the Approved payment instructions.
#
Parameter
Description
1
pmtInstId
Payment instruction ID of the payment instruction generated at JIT
2
pmtInstDate
Payment instruction date of the payment instruction generated at JIT
3
billNo
Payment Instruction ID of the payment instruction created in MUKTASoft and then pushed to JIT.
4
billDate
Payment Instruction date of the payment instruction created in MUKTASoft and then pushed to JIT.
5
ssuIaId
Special spending unit ID. A master value maintained in JIT-FS.
#
Parameter
Description
2
billNo
Bill number of the bill created in MUKTASoft and then pushed to JIT-FS as payment instruction.
3
ssuIaId
Special spending unit ID. A master value maintained in JIT-FS.
4
finYear
The financial year for which bill was created.
5
adviceId
Unique Id generated after successfully submission of Advice for payment in JIT.
6
adviceDate
Advice date of payment advice generated in JIT.
7
onlineBillRefNo
Auto generated online bill Reference number in JIT.
8
tokenNumber
Token number generated automatically after auto submitted bill to treasury
9
tokenDate
Token date of the token generated automatically.
Beneficiary List
10
benfName
Beneficiary name
11
benfAccountNo
Beneficiary account number
12
benfBankIfscCode
Beneficiary’s IFSC which was pushed through PI.
13
amount
Amount to be paid to the beneficiary.
14
benfId
Beneficiary unique ID which was generated for PI.
Error message displayed on View Payment Instruction Page. [Message: On call of PAG API: No response is received.]
PI status at MUKTASoft remain unchanged to Approved.
All beneficiaries payment status remain unchanged to Payment Initiated.
Option to refresh the status is provided. It triggers call of PAG.
Error message is stored at MUKTASoft.
Error message displayed on View Payment Instruction Page. [Message: On call of PAG API: <JIT error message>]
PI status at MUKTASoft remain unchanged to Approved.
All beneficiaries payment status remain unchanged to Payment Initiated.
Option to refresh the status is provided. It triggers call of PAG.
Success message is received and same is stored at MUKTASoft.
Info message displayed on View Payment Instruction Page. [Message: On call of PAG API: Response is received and updated successfully]
PI status at the MUKTASoft changes to In Process.
All beneficiaries payment status remain unchanged to Payment In Process.
Option to refresh the status is provided. It triggers call of PD.
#
Response
PI Status (From)
PI Status (To)
Payment Status
User Action
API Call
1
No Response
Approved
Approved
Payment Initiated
Refresh
PAG
2
Response With Error
Approved
Approved
Payment Initiated
Refresh
PAG
3
Response Without Error
Approved
In Process
Payment In Process
Refresh
PD
Not applicable.
Not applicable.
Not applicable.
Not applicable.
Not applicable.
Not applicable
View Payment Instruction
Status is fetched and update in MUKTASoft for both PI and Beneficiary.
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.
The integration with JIT start with the payment instruction. Hence the entity we create at MUKTASoft to push into JIT as Payment Instruction will also be called Payment Instruction.
Payment Instruction
Auto Generation
Employee
Role: System
Payment instruction (PI) is the API to push the PI details into JIT.
For failed transactions, revised PI is generated and then pushed into JIT.
For each bill one PI is prepared and pushed into JIT.
PI is prepared and pushed with approval of Bill (Wage Bill, Purchase Bill, Supervision Bill).
To generate a PI, selection of HOA logic is given under configuration section.
For Request/ Response parameters, please refer the integration approach document.
The response data is stored and maintained at MUKTASoft for each PI and revised PI.
Once a PI is generated can be searched and viewed using search and view PI feature.
System performs a check to decide on the HOA, It picks a HOA first out of three HOAs and check for the fund available for all the sanction orders one by one and when found sufficient fund is available, create PI.
HOAs are scanned in the sequence given below. Sequence of HOA to be selected should be configurable.
SC Head
ST Head
General Head
#
Parameter
Is Mandatory?
Description
2
jitBillNo
Yes
Payment Instruction ID of the payment instruction created in MUKTASoft and then pushed to JIT.
3
jitBillDate
Yes
Payment Instruction date of the payment instruction created in MUKTASoft and then pushed to JIT.
4
jitBillDdoCode
Yes
The code of DDO from the configuration.
5
granteeAgCode
Yes
Grantee code from the configuration.
6
schemeCode
Yes
MUKTA scheme code
7
hoa
Yes
Head of account from which payment to be made.
8
ssuIaId
Yes
Special spending unit id from the configuration.
9
mstAllotmentDistId
Yes
Virtual allotment parent ID/sanction ID from which payment to be made.
10
billNetAmount
Yes
PI net amount of the payment instruction created in MUKTASoft and then pushed to JIT.
11
billGrossAmount
Yes
PI gross amount of the payment instruction created in MUKTASoft and then pushed to JIT.
12
billNumberOfBenf
Yes
The count of beneficiaries in the payment instruction.
13
purpose
Yes
Purpose is the reference text. E.g. Muster Roll ID etc. for which the payment instruction is created.
Beneficiary Details
Array
In a single request multiple beneficiaries can be added.
14
benefId
Yes
The beneficiary's Payment ID, unique for each beneficiary for its payment. Payment of the beneficiary is tracked by this throughout the payment processing. It is generated with the PI generation.
15
benefName
Yes
Beneficiary name maintained in MUKTASoft.
16
benfAcctNo
Yes
Beneficiary’s bank account number maintained in MUKTASoft.
17
ifscCode
Yes
IFSC of bank branch from beneficiary’s accounts details.
18
benfMobileNo
Yes
Beneficiary's mobile number maintained in MUKTASoft.
19
benfAddress
Yes
Beneficiary’s address maintained in MUKTASoft.
20
accountType
Yes
Account type of beneficiary’s account maintained in MUKTASoft
21
paymentAmount
Yes
Amount payable to beneficiary.
22
panNo
No
PAN of beneficiary
23
adhaarNumber
No
Aadhaar of beneficiary
24
purpose
Yes
Purpose is the reference text. E.g. Muster Roll ID etc. for which the bill is created.
#
Parameter
Description
1
jitBillNo
Payment Instruction ID of the payment instruction created in MUKTASoft and then pushed to JIT.
2
jitBillDate
Payment Instruction date of the payment instruction created in MUKTASoft and then pushed to JIT.
3
ssuIaId
Special spending unit ID. A master value maintained in JIT-FS.
4
successCode
0 - for successfully accepting the PI.
7
sucessDescrp
Jit Bill is received successfully ,Payment Instruction will be generated after Bill is submitted by SSU in JIT-FS
PI is created and saved at MUKTASoft.
Error message displayed on View Payment Instruction Page. [Message: On call of PI API: No response is received.]
PI status at MUKTASoft changes to Pending.
Beneficiary payment status update to “Payment Pending”.
Option to re-push the PI is provided, and the same time system will try to push all such PI once in a day at 9PM every day.
Error message is stored at MUKTASoft.
Error message displayed on View Payment Instruction Page. [Message: On call of PI API: <JIT error message>]
PI status at MUKTASoft updated/changes to Declined.
Beneficiary payment status updated to “Payment Pending”.
Option to re-push the PI is provided, necessary correction is made to encounter the error and PI is re-pushed.
Success response is received and same is stored at MUKTASoft.
Info message displayed on View Payment Instruction Page. [Message: On call of PI API: Response is received and updated successfully]
PI status at the MUKTASoft changes to Initiated.
Beneficiary payment status changes to “Payment Initiated”.
An expense transaction is recorded under Fund Allocation Register.
#
Response
PI Status (From)
PI Status (To)
Payment Status
User Action
API Call
1
No Response
Pending
Payment Pending
Resubmit
PI
2
Response with Error
Pending
Declined
Payment Pending
Resubmit
PI
3
Response Without Error
Pending/ Decline
Initiated
Payment Initiated
No Action
Make sure DDO Code and SSUID are passed into requests as per the configuration. In case configuration is missing. [Message: DDO and SSUID configuration is missing.]
Make sure Net or Gross amount of Payment Instruction is not more than the total allotted amount for SSU a HOA and Sanctioned ID. [Message: Insufficient fund.]
Make sure the payment instruction ID is unique and no PI has already been pushed with same PI ID. [Message: Duplicate payment instruction ID.]
Make sure number of beneficiaries mentioned in the header should not mismatch with the actual details. [Message: Number of beneficiaries provided in header doesn’t match with the details.]
Make sure amount mentioned in the net amount should not mismatch with the total of all the beneficiaries amount. [Message: The total net amount provided in hear doesn’t match with total of all the beneficiaries.]
Make sure Gorss amount is either equal to or more than Net Amount and none of them can be zero. [Message: Gross amount can not be less than the net amount.]
Make sure at least one beneficiary is included in PI. [Message: Beneficiary detail is missing.]
Make sure total net amount is equal to sum of all the beneficiaries’ payment amount. [Message: The total net amount provided in header doesn’t match with total of all the beneficiaries.]
Make sure PI doesn’t have duplicate beneficiary. i.e. same a/c and ifsc cannot be repeated. [Message: There are 2 or more than 2 beneficiaries account number and IFSC are same.]
Beneficiaries original account no /IFSC/Bifid is not matching with correction file – Make sure parameter values passed are correct. [Message: The beneficiary <paymentid> was not present in the original payment instruction.]
Status are configured as master data.
PI Status
Pending
Declined
Initiated
Rejected
Approved
In Process
Completed
Payment Status - Beneficiary’s payment status.
Payment Pending
Payment Initiated
Payment In Process
Payment Successful
Payment Failed
Not applicable.
Not applicable.
Resubmit (*On View Payment Instruction)*
PI is re-constructed, availability of fund is checked and push and the response is updated back.
Scheduler: Same time a scheduler running every day at 10PM will try to push such PIs which are created with status Pending.
Not applicable
PI ID is generated following the format given below.
PI-<ULBCODE>/FY/<6 digit running sequence number>. E.g. PI-DK/2022-23/000023.
The Six digit running sequence no. should be running for ULB wise.
It has to be reset to 1 with start of every financial year. i.e. on 01/04 00:00AM
Payment transaction ID is generated for each beneficiary, which is unique for the every transaction. There is not specific format.
View Payment Instruction.
Make sure the the availability of fund is checked before pushing the payment instruction into JIT.
PI is generated for each and every bill and pushed to JIT with the approval of bill.
All the validations are taken care.
PI ID is generated as per the format defined.
If the PI is declined, the same PI can be modified and re-pushed.
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.
Fund Allocation Register
Reports → Fund Allocation Register
Employee
Role: Fund Allocation View
Virtual Allotment Details (VA) is the API to fetch the fund allocation details.
MUKTA as a scheme has multiple HOAs for which fund is sanctioned and allocated.
Fund Allocation Register has to be developed to see and download the details.
For Request/ Response parameters, please refer the integration approach document.
This data is stored and maintained at MUKTASoft for every financial year and used for reporting and reference purposes.
APIs to be triggered daily at 10 PM.
Search Parameters
#
Field
Description
1
Financial Year
Financial year, by default current financial year is selected.
2
Head of Account
HOAs from the configuration.
3
Transaction Type
Allotment types are, 1) Initial Allotment 2) Additional Allotment 3) Withdrawal 4) Expense 5) Expense Reversed
Note: Financial Year is mandatory to select, by default current financial year is selected and records are searched.
Search Result
#
Field
Description
1
HOA
Head of accounts of MUKTA
2
Transaction Number
Transaction number of the transactions fetched from JIT or created in MUKTASoft.
3
Transaction Date
Date of transaction received from JIT-FS in a response of API call or the MUKTASoft PI creation date. Date to be taken care when calling the API again.
4
Transaction Type
A transaction type would be anything from the options given below.
Initial Allotment
Additional Allotment
Withdrawal
Expense
Expense (Reversed) First 3 are received from JIT-FS system through API call while the last one is from MUKTASoft when a PI is pushed. A reverse entry of the Expense is made in the case PI is canceled or failed to create.
5
Transaction Amount
It is transaction amount.
6
Sanctioned Balance
It is the balance remaining from the sanctioned amount and calculated as given below. Sanctioned Balance = Total Sanctioned Amount - Sum of all the allotments.
7
Fund Available
It the fund available for the expenditure and calculated as given below. Fund Available = Sum of all the allotments - (Sum of all the expenditure + Sum of all the withdrawal)
While fetching the details, from date should be taken care properly.
The records/transactions are sorted in chronological order.
The master data which needs to be configured.
Special Spending Unit
SSU ID
SSU Name
Grantee Code
DDO Code
Tenant ID
Head of Accounts
Code
Name
221705789358641045908 (MUKTA - SC Component)
221705800358641045908 (MUKTA - General Component)
221705796358641045908 (MUKTA - ST Component)
Not applicable.
Not applicable.
Search - Fetch and display the records based on the search parameters.
Clear - Clear the search parameters.
Download - Option to download the report into PDF format is provided as per the attached format.
Not applicable
Data fetched is stored for reporting and reference purpose.
Report is developed with the option to download the it into PDF.
Payment Instruction
Status Update for Payment Failed Status
Employee
Role: System
Failed Details (FD) is the API to fetch the failed payment details from JIT.
For Request/ Response parameters, please refer the integration approach document.
The response data is stored and maintained at MUKTASoft for every FD call.
The API call to be scheduled once in a day at 10 PM for Completed payment instructions.
#
Parameter
Description
2
billno
Payment Instruction ID of the payment instruction created in MUKTASoft and then pushed to JIT.
3
billDate
Payment Instruction date of the payment instruction created in MUKTASoft and then pushed to JIT.
4
adviceId
Payment advice ID, generated at JIT-FS
5
onlineBillRefNo
Online bill reference no. generated at JIT and received with PAG response.
6
tokenNo
Token number, generated at JIT-FS
7
tokenDate
Token number, generated at JIT-FS
#
Parameter
Description
2
billNumber
Bill number of the bill created in MUKTASoft and then pushed to JIT-FS as payment instruction.
3
billDate
Bill date of the bill created in MUKTASoft and then pushed to JIT-FS as payment instruction.
4
voucherNo
Voucher generated at JIT-FS for maintaining the accounting.
5
voucherDate
Voucher date.
6
billRefNo
Online bill reference number generated at JIT and received with PAG response.
7
tokenNumber
Token number generated at JIT-FS
8
tokenDate
Token generation date
benfDtls
10
benfAcctNo
Beneficiary’s account number.
11
benfBankIfscCode
Beneficiary’s bank / branch IFSC.
12
utrNo
Unique transaction number used by banks to reconcile the transaction.
13
utrDate
UTR date.
14
endToEndId
End to end id generated to identify a particular beneficiary for a transaction while it is pushed to CPC for payment clearance.
15
orgBillRefNumber
Original online bill reference number, In first failure case billRefNo and orgBillRefNumber are same.
16
challanNumber
Challan number of the challan created to put the amount into suspense account
17
challanDate
Challan generation date
18
failedReason
Reason for failure
19
benfId
Beneficiary unique ID, unique to transaction.
Error message displayed on View Payment Instruction Page. [Message: On call of FD API: No response is received.]
PI status at MUKTASoft remain unchanged to Completed.
Beneficiaries payment status remain unchanged to Payment Successful.
No action is enabled.
Error message is stored at MUKTASoft.
Error message displayed on View Payment Instruction Page. [Message: On call of FD API: <JIT error message>]
PI status at MUKTASoft remain unchanged to Completed.
Beneficiaries payment status remain unchanged to Payment Successful.
No action is enabled.
Success message is received and same is stored at MUKTASoft.
Info message displayed on View Payment Instruction Page. [Message: On call of FD API: Response is received and updated successfully]
PI status at the MUKTASoft remain unchanged to Completed.
The beneficiaries for which details is received in response, the payment status changes to Payment Failed.
SMS notification is sent to all the beneficiaries.
Option to generate revised PI is enabled. It triggered the COR API call.
#
Response
PI Status (From)
PI Status (To)
Payment Status
User Action
API Call
1
No Response
Completed
Completed
Payment Successful
No Action
2
Response With Error
Completed
Completed
Payment Successful
No Action
3
Response Without Error
Completed
Completed
Payment Failed
Generate Revised PI
COR
Not applicable.
Not applicable.
Not applicable.
Not applicable.
Not applicable.
To beneficiary for which failure details is received:
Payment of Rs. {amount} for MUKTA, transaction <UTRNO> is failed. Contact MUKTA Cell at ULB for more detail. MUKTA - Govt. of Odisha.
View Payment Instruction
API is called and status is fetched and updated for beneficiaries.
SMS notification is sent to beneficiary for failed transaction.
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.
Payment Instruction
Status Update API Call
Employee
Role: System
Payment instruction status (PIS) is the API to fetch the PI status from JIT.
Once a PI is accepted at JIT, it is then approved with a digital sign by SSU in JIT.
The approved ones only has the Payment Instruction ID and Date available in response.
For Request/ Response parameters, please refer the integration approach document.
The response data is stored and maintained at MUKTASoft for every PIS call.
The API call to be scheduled once in a day at 10:00PM every day for the Payment Instructions Initiated, and the Payment Instructions Declined having error “Duplicate Payment Information Id”.
#
Parameter
Is Mandatory?
Description
1
jitBillNo
Yes
Payment Instruction ID of the payment instruction created in MUKTASoft and then pushed to JIT.
2
jitBillDate
Yes
Payment Instruction date of the payment instruction created in MUKTASoft and then pushed to JIT.
3
ssuIaId
Yes
Special spending unit ID. A master value maintained in JIT-FS.
#
Parameter
Description
1
pmtInstId
The unique id of payment instruction that’s been generated at JIT.
2
payInstDate
The date of payment instruction created.
3
jitBillNumber
Payment Instruction ID of the payment instruction created in MUKTASoft and then pushed to JIT.
4
jitBillDate
Payment Instruction date of the payment instruction created in MUKTASoft and then pushed to JIT.
5
ssuIaId
Special spending unit ID. A master value maintained in JIT-FS.
6
billNetAmount
Net bill amount sent in the PI
7
billGrossAmount
Gross bill amount sent in the PI
8
schemeCode
Scheme code under which PI is created
9
totalNumberOfBeneficiary
Total beneficiary count
Error message displayed on View Payment Instruction Page. [Message: On call of PIS API: No response is received.]
PI status at MUKTASoft remain unchanged to Initiated.
All beneficiaries payment status remain unchanged to Payment Initiated.
Option is given to user to refresh the status. On refresh API call is triggered.
Error message is stored at MUKTASoft.
Error message displayed on View Payment Instruction Page. [Message: On call of PIS API: <JIT error message>]
PI status at MUKTASoft remain unchanged to Initiated.
All beneficiaries payment status remain unchanged to Payment Initiated.
Option is given to user to refresh the status. On refresh API call is triggered.
If the PI is rejected by SSU user, the same is received in error message.
Error message displayed on View Payment Instruction Page. [Message: On call of PIS API: <JIT error message>]
PI status at MUKTASoft changes to Rejected.
All beneficiaries payment status changes to NA.
A reverse expense transaction is recorded under Fund Allocation Register.
Option to generate new PI is provided from View Payment Instruction Page.
Success message is received and same is stored at MUKTASoft.
Info message displayed on View Payment Instruction Page. [Message: On call of PIS API: Response is received and updated successfully]
PI status at the MUKTASoft changes to Approved.
All beneficiaries payment status remain unchanged to Payment Initiated.
Option to refresh the status is provided. It triggers call of PAG.
#
Response
PI Status (From)
PI Status (To)
Payment Status
User Action
API Call
1
No Response
Initiated
Initiated
Payment Initiated
Refresh
PIS
2
Response with Error Others
Initiated
Initiated
Payment Initiated
Refresh
PIS
3
Response with Error Rejected
Initiated
Rejected
Payment Initiated
Generate New PI
PI
4
Response Without Error
Initiated
Approved
Payment Initiated
Refresh
PAG
Not applicable.
Not applicable.
Not applicable.
Not applicable.
Not applicable.
Not applicable
View Payment Advice
There is scheduler running to fetch the PI status and updated at MUKTASoft.
Status is updated based on response received.
Both the statuses are reflected in View Payment Instruction.
Option to Generate Revised PI is given to user through 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 based on schedule until a response is received. The latest response is recorded in the log.
Payment Instruction
Status Update for Payment Status
Employee
Role: System
Payment Details (PD) is the API to fetch the payment details from JIT.
For Request/ Response parameters, please refer the integration approach document.
The response data is stored and maintained at MUKTASoft for every PD call.
The API call to be scheduled once in a day at 10 PM for In Process payment instruction.
#
Parameter
Description
1
finYear
Financial year received in the APIs response of PAG.
2
ExtAppName
The name of the application from which the call is being made.
3
billRefNo
Online bill reference number received in the APIs response of PAG.
4
tokenNumber
Token number received in the APIs response of PAG.
6
tokenDate
Token date received in the APIs response of PAG.
#
Parameter
Description
1
billNumber
Payment Instruction ID of the payment instruction created in MUKTASoft and then pushed to JIT.
2
billDate
Payment Instruction date of the payment instruction created in MUKTASoft and then pushed to JIT.
3
voucherNumber
Voucher number of the voucher created in JIT to maintain the accounting.
4
voucherDate
The voucher creation date of the voucher created in JIT-FS for payment.
5
billRefNo
Online bill reference number generated in JIT and received in PAG response.
6
paymentStatus
Payment status Message Received from RBI at the time of Debit Scroll.
7
tokenNumber
Token number generated in JIT and received in PAG response.
8
tokenDate
Token date of the token generated in JIT and received in PAG response.
Debit Scroll Details
9
benfAcctNo
Beneficiary’s account number.
10
benfBankIfscCode
Beneficiary’s bank / branch IFSC.
11
utrNo
Unique transaction number used by banks to reconcile the transaction.
12
utrDate
The date of transaction which is used by bank.
13
endToEndId
End to end id generated to identify a particular beneficiary for a transaction while it is pushed to CPC for payment clearance.
14
benfId
Beneficiary unique ID, unique to transaction.
Error message displayed on View Payment Instruction Page. [Message: On call of PD 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 PD.
Error message is stored at MUKTASoft.
Error message displayed on View Payment Instruction Page. [Message: On call of PD 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 PD.
Success message is received and same is stored at MUKTASoft.
Info message displayed on View Payment Instruction Page. [Message: On call of PD 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.
SMS notification is sent to all the beneficiaries.
#
Response
PI Status (From)
PI Status (To)
Payment Status
User Action
API Call
1
No Response
In Process
In Process
Payment In Process
Refresh
PD
2
Response With Error
In Process
In Process
Payment In Process
Refresh
PD
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.
Payment Instruction
Search Payment Instruction to Generate Revised PI
Employee
Role: Accountant
Home Page > Payment Instructions > Search Payment Instruction
Search Payment Instruction to be provided to list all the PIs which have the failed transaction and the revised PI to be generated for them.
Two types of searched to provided with 2 different tabs.
Pending for Action
Open Search
Below are the search parameters to search such payment instructions.
#
Parameters
Description
1
Ward
Drop-down, with the ward name as values.
2
Project Type
Project Types
3
Project Name
Name of project
4
Bill Number
Bill number
5
Status
Status of payment instructions. This parameter is not applicable for “Payment Instruction Pending for Correction”
6
Created from date
Payment instruction created date. This parameter is not applicable for “Payment Instruction Pending for Correction”
7
Created to date
Payment instruction created date. This parameter is not applicable for “Payment Instruction Pending for Correction”
“Pending for Action” tab is displayed by default with the search result of PIs which are pending for action. It means.
The payment instructions which have the status Completed, Declined, and Pending.
Additional condition for Completed PI, It should have at least one beneficiary payment status as Payment Failed .
Open Search, it will allow users to search any payment instruction and view the details.
In this case, at least one parameter is must to search.
For name, fuzzy search is enabled.
Created from and To are considered as one parameters as date range.
#
Parameter
Description
1
Payment Instruction ID
Original/ Revised Payment Instruction ID. It is a hyperlink which opens the payment instruction to view the complete details.
2
Payment Instruction Date
Original/ Revised Payment Instruction Date.
3
No. of beneficiaries
Total number of beneficiaries for which payment is getting processed.
4
No. of successful Payments
Total number of successful payments.
5
No. of failed Payments
Total number of failed payments
6
Total Amount
Total amount of payment instruction which is to be paid.
7
Status
Status of payment instruction
Not applicable
Not applicable.
Not applicable.
Not applicable.
Not applicable.
Not applicable
Search enables users to see the pending correction PI by default.
Search for any PI is also provided to search and view the details.
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 integration approach document.
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.
Payment Instruction
View Payment Instruction
Employee
Role: Accountant
View Payment Instruction to be provided to view the detail and track the status of Original/ Revised Payment Instructions.
Below is the details which is displayed for a payment instruction.
#
Parameter
Description
1
Bill Number
Hyperlink to view the bill details.
2
Payment Instruction Type
Payment instruction type, Original or Revised.
3
Parent Payment Instruction ID
Parent payment instruction id, i.e. original PI ID. It is a hyperlink to view the Original Payment Instruction Details.
4
Payment Instruction ID
Payment Instruction ID.
5
Payment Instruction Date
Payment Instruction Date.
6
Head of Account
Head of account from which amount to be paid
7
Master Allotment ID
Master allotment ID from which amount to be paid
8
Status
Status of payment instruction. A tool-tip is displayed to display the error message for declined and rejected PIs.
9
Payment Advice Details
10
Payment Advice ID
Payment advice ID generated for the original/ revised PI.
11
Payment Advice Date
Payment advice generation date.
12
Token Number
Token no. generated for the payment instruction
13
Token Date
Token no. generated for the payment instruction
14
Online Bill Number
Online bill number for the online bill generated for the payment advice.
Error/ Info Section
A information display band to display the error message/ info messages
Beneficiary Details
Tabular form
15
Beneficiary ID
It is individual ID of wage seeker/ organization ID for CBOs and vendors, and displayed as hyperlink to view details.
16
Payment ID
Unique beneficiary ID for the payment through JIT. It remain same though the process until the payment becomes successful.
17
Beneficiary Name
Name of the beneficiary.
18
Account Number
Account number of beneficiary, only last 4 digits are displayed. Remaining initial digits of A/C are masked.
19
IFSC
IFSC code of the bank/ branch of beneficiary accounts.
20
Payment Status
The payment status, as per the definition. A tooltip is shown to display the error message for failed payments.
21
Payment Amount
The payment amount of beneficiary.
Info
In case of there are failed payments, an information is displayed. “Please make sure all the necessary corrections are made before generating the revised payment instruction for JIT” .
Not applicable.
Not applicable.
Not applicable.
Not applicable.
For Pending and Declined Payment Instruction.
Re-submit - Payment instruction is re-push again.
A success toast message is displayed on successful submission and the status of PI changes to Initiated. [*The payment instruction is submitted successfully.*]
In case, the PI is decline again, the toast message is displayed with the error message and the status of PI remain Declined. [*Submission failed, <error message>*]
2. For Completed Payment Instruction which has at least one failed payment.
Generate Revised PI - A revised PI is generated and push to JIT after clearing all the errors.
A success toast message is displayed on successful submission with the PI ID displayed in message. [*Revised payment instruction <PIID> generated and submitted successfully.*]
In case revised PI is declined, a failure toast message is displayed with the PI ID generated for revised PI. [*Revised payment instruction <PIID> generated successfully, but failed to submit.*]
Not applicable
Payment instruction details is displayed as described in the story.
Actions are enabled based on the status of current payment instruction.
Payment instruction id is generated according to format defined in case revise PI is generated.
Appropriate messages are displayed with each action.
Payment Instruction
Status Update for Payment Failed Status from revised PI
Employee
Role: System
Failed transaction failed payment (FTFPS) is the API to fetch the failed payment details from JIT.
For Request/ Response parameters, please refer the integration approach document.
The response data is stored and maintained at MUKTASoft for every FTFPS call.
The API call to be scheduled once in a day at 10 PM for Completed payment instructions.
#
Parameter
Description
1
jitCorBillNo
Revised PI ID generated in MUKTASoft and pushed for failed transactions into JIT
2
jitCorBillDate
Revised PI date generated in MUKTASoft and pushed for failed transactions into JIT
3
billRefNo
Online bill reference number for revised/current PI
4
tokenNumber
Token number generated in JIT.
5
tokenDate
Token date generated in JIT.
#
Parameter
Description
1
jitCorBillNo
Revised PI ID generated in MUKTASoft and pushed for failed transactions into JIT
2
jitCorBillDate
Revised PI date generated in MUKTASoft and pushed for failed transactions into JIT
3
billRefNo
Online bill reference number for the current revised PI.
4
tokenNumber
Token number generated in JIT.
5
tokenDate
Token date generated in JIT.
Beneficiary Details
7
benfAcctNo
Beneficiary’s account number.
8
benfBankIfscCode
Beneficiary’s bank / branch IFSC.
9
utrNo
Unique transaction reference number used by banks to reconcile the transaction.
10
utrDate
UTR date.
11
endToEndId
It is generated to identify a beneficiary for a transaction while it is pushed to CPC for payment clearance.
12
orgBillRefNumber
Original online bill reference no.
13
challanNumber
Challan number
14
challanDate
Challan date
15
failedReason
Account related errors, Like account that doesn't exist.
16
benfId
Beneficiary unique ID, unique to transaction.
Error message displayed on View Payment Instruction Page. [Message: On call of FTFPS API: No response is received.]
PI status at MUKTASoft remain unchanged to Completed.
Beneficiaries payment status remain unchanged to Payment Successful.
No action is enabled.
Error message is stored at MUKTASoft.
Error message displayed on View Payment Instruction Page. [Message: On call of FTFPS API: <JIT error message>]
PI status at MUKTASoft remain unchanged to Completed.
Beneficiaries payment status remain unchanged to Payment Successful.
No action is enabled.
Success message is received and same is stored at MUKTASoft.
Info message displayed on View Payment Instruction Page. [Message: On call of FTFPS API: Response is received and updated successfully]
PI status at the MUKTASoft remain unchanged to Completed.
The beneficiaries for which details is received in response, the payment status changes to Payment Failed.
Option to generate revised PI is enabled. It triggered the COR API call.
#
Response
PI Status (From)
PI Status (To)
Payment Status
User Action
API Call
1
No Response
Completed
Completed
Payment Successful
No Action
2
Response With Error
Completed
Completed
Payment Successful
No Action
3
Response Without Error
Completed
Completed
Payment Failed
Generate Revised PI
COR
Not applicable.
Not applicable.
Not applicable.
Not applicable.
Not applicable.
To beneficiary for which failure details is received:
Payment of Rs. {amount} for MUKTA, transaction <UTRNO> is failed. Contact MUKTA Cell at ULB for more detail. MUKTA - Govt. of Odisha.
View Payment Instruction
API is called and payment status is fetched and updated for the beneficiaries.
SMS notification is sent to beneficiary for failed transaction.
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.
Payment Instruction
Re-push revised PI for failed transactions
Employee
Role: Accountant
Home Page → Billing → Search Bills → Open Bill → Generate Revised PI
Failed Transaction Correction (COR) is the API to push revised PI to JIT.
A new PI is generated at MUKTASoft to push it as revised PI.
MUKTA accountant login in MUKTASoft open the bill screen and initiate revised PI.
For Request/ Response parameters, please refer the .
The response data is stored and maintained at MUKTASoft for every COR call.
API is called with an action is triggered by user from View Payment Instruction Page.
PI is created and saved at MUKTASoft.
Error message displayed on View Payment Instruction Page. [Message: On call of COR API: No response is received.]
PI status at MUKTASoft updated to Pending.
Beneficiary payment status changes to “Payment Pending”.
Option to re-push the PI is provided, and the same time system will try to push all such PI once in a day at 9PM every day.
Error message is stored at MUKTASoft.
Error message displayed on View Payment Instruction Page. [Message: On call of COR API: <JIT error message>]
PI status at MUKTASoft is updated to Declined.
Beneficiary’s payment status will change to “Payment Pending”.
Option to re-push the PI after clear the error is provided from View Payment Instruction Page.
Success message is received and same is stored at MUKTASoft.
Info message displayed on View Payment Instruction Page. [Message: On call of COR API: Response is received and updated successfully]
PI status at the MUKTASoft changes to In Process.
Beneficiary’s payment status will change to Payment In Process.
Note: PIS and PAG calls are skipped for revised PI.
Make sure the payment instruction ID is unique and no PI has already been pushed with same PI ID. [Message: Duplicate payment instruction ID.]
Make sure PI doesn’t have duplicate beneficiary. i.e. same a/c and ifsc cannot be repeated. [Message: There are 2 or more than 2 beneficiaries having same account number and IFSC.]
Beneficiaries original account no /IFSC/Bifid is not matching with correction file – Make sure parameter values passed are correct. [Message: The beneficiary <paymentid> was not present in the original payment instruction.]
Not applicable.
Not applicable.
Not applicable.
Not applicable.
Not applicable
The format used for Original Payment instruction is followed.
View Payment Instruction
Revised PI is generated and pushed to JIT.
All the validations are taken care which are applicable to Original PI.
PI ID is generated as per the format defined or original PI.
If the PI is declined, the same one can be modified and re-pushed.
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.
#
Parameter
Description
2
jitCorBillNo
Revised PI ID of the PI generated at MUKTASoft to re-push failed transactions into JIT
3
jitCorBillDate
Revised PI date of the PI generated in MUKTASoft to re-push failed transactions into JIT
4
jitCorBillDeptCode
Application code, e.g. MUKTA.
5
jitOrgBillRefNo
Original viz. first (parent) bill reference no. of online bill which was received in the PAG response.
6
jitOrgBillNo
Original viz. first (parent) MUKTASoft PI ID.
7
jitOrgBillDate
Original viz. first (parent) MUKTASoft PI date.
Beneficiaries Details
8
benefId
Beneficiary ID, Beneficiary id of the failed transaction.
9
jitCurBillRefNo
Latest failed transaction bill reference number viz. The PI for which failure is reported (Original/ Revised)
10
orgAccountNo
Original Account Number, The one which was pushed in first PI.
11
orgIfsc
Original IFSC, , The one which was pushed in first PI.
12
correctedAccountNo
Corrected account number, recent corrected account number corrected for this revised PI.
13
correctedIfsc
Corrected IFSC, recent corrected IFSC corrected for this revised PI.
14
curAccountNo
Current account number which was pushed in just previous PI for which failure is reported.
15
curIfsc
Current IFSC which was pushed in just previous PI for which failure is reported.
#
Parameter
Description
2
jitCorBillNo
Revised PI ID, created in MUKTASoft and then pushed to JIT
3
jitCorBillDate
Revised PI date, created in MUKTASoft and then pushed to JIT
4
successCode
0 - Success
5
sucessDescrp
JIT Correction Bill is received successfully ,Forwarded to Treasury officer to generate Return adjust Bill
#
Response
PI Status (From)
PI Status (To)
Payment Status
User Action
API Call
1
No Response
Pending
Payment Pending
Resubmit
COR
2
Response With Error
Pending
Declined
Payment Pending
Resubmit
COR
3
Response Without Error
Pending/ Decline
In Process
Payment In Process
No Action