Revised PI: Updated Failed Payments

Context

Solution

Scope

Payment Instruction

Status Update for Payment Failed Status from revised PI

Actors

Employee

Role: System

Details

1. Failed transaction failed payment (FTFPS) is the API to fetch the failed payment details from JIT.

2. For Request/ Response parameters, please refer the integration approach document.

3. The response data is stored and maintained at MUKTASoft for every FTFPS call.

4. The API call to be scheduled once in a day at 10 PM for Completed payment instructions.

API Request

#	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.

API Response

#	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.

No Response

1. Error message displayed on View Payment Instruction Page. [Message: On call of FTFPS API: No response is received.]

2. PI status at MUKTASoft remain unchanged to Completed.

3. Beneficiaries payment status remain unchanged to Payment Successful.

4. No action is enabled.

Response With Error

1. Error message is stored at MUKTASoft.

2. Error message displayed on View Payment Instruction Page. [Message: On call of FTFPS API: <JIT error message>]

3. PI status at MUKTASoft remain unchanged to Completed.

4. Beneficiaries payment status remain unchanged to Payment Successful.

5. No action is enabled.

Response Without Error

1. Success message is received and same is stored at MUKTASoft.

2. Info message displayed on View Payment Instruction Page. [Message: On call of FTFPS API: Response is received and updated successfully]

3. PI status at the MUKTASoft remain unchanged to Completed.

4. The beneficiaries for which details is received in response, the payment status changes to Payment Failed.

5. Option to generate revised PI is enabled. It triggered the COR API call.

API Call - Status - Payment Status - Actions Mapping

#	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

Validations

Not applicable.

Configurations

Master Data

Not applicable.

Attachments

Not applicable.

Workflow

Not applicable.

Actions

Not applicable.

Notifications

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.

User Interface

View Payment Instruction

Acceptance Criteria

1. API is called and payment status is fetched and updated for the beneficiaries.

2. SMS notification is sent to beneficiary for failed transaction.

3. Status is reflected in View Payment Instruction Page.

4. The response is captured in MUKTASoft for debugging and error reporting.

5. Technical glitched in the integration are defined as error and captured.

6. System keep trying until a response is received. The latest response is recorded in the log.