> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/works/reference-implementations/muktasoft-v2.2/specifications/functional-requirements/user-stories/improvements/re-payment-of-failed-payment.md).

# Re-payment of failed payment

## Context

They payment to the beneficiaries are done through JIT system. In a case when a payment is failed due to wrong bank account number or IFSC, or due to any other reasons the same is submitted again to JIT as a revised PI.

As per the recent conversations, it has been communicated to us that the revised PI works in tried within 90 days or before 30th April of next financial year from the date transaction got failed. Hence change in the system to made to address this use case.

## Details <a href="#details" id="details"></a>

1. This is for the failed transactions which could not be cleared before 90 days from the failure date or 30th April of next FY, whichever is earlier.
2. From the view PI page option to create a new PI to be enabled for such transactions.
3. A new original PI is created with request JSON PI is required and submit to JIT.

## Acceptance Criteria <a href="#acceptancecriteria" id="acceptancecriteria"></a>

New PI is created and send for payment for those failed transactions which could not be cleared before 90 days from the failure date or 30th April of next FY, whichever is earlier.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digit.org/works/reference-implementations/muktasoft-v2.2/specifications/functional-requirements/user-stories/improvements/re-payment-of-failed-payment.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
