Create Revised Payment Instruction
Context
Solution
Scope
Payment Instruction
Re-push revised PI for failed transactions
Actors
Employee
Role: Accountant
Home Page → Billing → Search Bills → Open Bill → Generate Revised PI
Details
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 integration approach document.
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.
API Request
# | 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. |
API Response
# | 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 |
No Response
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.
Response With Error
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.
Response Without Error
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.
API Call - Status - Payment Status - Actions Mapping
# | 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 |
|
Note: PIS and PAG calls are skipped for revised PI.
Validations
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.]
Configurations
Master Data
Not applicable.
Attachments
Not applicable.
Workflow
Not applicable.
Actions
Not applicable.
Notifications
Not applicable
ID Generation
The format used for Original Payment instruction is followed.
User Interface
View Payment Instruction
Acceptance Criteria
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.