PAG: Payment Advice Status

Context

Solution

Scope

Payment Instruction

Status Update for Payment Advice

Actors

Employee

Role: System

Details

1. Payment Advice Status (PAG) is the API to fetch the payment advice status from JIT.

2. Once a PI is accepted at JIT, it is then approved with a digital sign by SSU in JIT.

3. For approved PI then payment advice is generated.

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

5. The response data is stored and maintained at MUKTASoft for every PAG call.

6. The API call to be scheduled once in a day at 10:15 PM every day for the Approved payment instructions.

API Request

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

API Response

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

No Response

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

2. PI status at MUKTASoft remain unchanged to Approved.

3. All beneficiaries payment status remain unchanged to Payment Initiated.

4. Option to refresh the status is provided. It triggers call of PAG.

Response With Error

1. Error message is stored at MUKTASoft.

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

3. PI status at MUKTASoft remain unchanged to Approved.

4. All beneficiaries payment status remain unchanged to Payment Initiated.

5. Option to refresh the status is provided. It triggers call of PAG.

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 PAG API: Response is received and updated successfully]

3. PI status at the MUKTASoft changes to In Process.

4. All beneficiaries payment status remain unchanged to Payment In Process.

5. Option to refresh the status is provided. It triggers call of PD.

API Call - Status - Payment Status - Actions Mapping

#	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

Validations

Not applicable.

Configurations

Master Data

Not applicable.

Attachments

Not applicable.

Workflow

Not applicable.

Actions

Not applicable.

Notifications

Not applicable

User Interface

View Payment Instruction

Acceptance Criteria

1. Status is fetched and update in MUKTASoft for both PI and Beneficiary.

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

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

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