> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/products/g2p-bridge/features/funds-management.md).

# Funds Management

Funds Management with Sponsor Bank

<figure><img src="https://3034178245-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJZcdob2emEcLMvLyIxqT%2Fuploads%2Fd3WprD6IPwuJqFZ8ZJHs%2FFlow%20-%20Digital%20Cash%20Transfers.jpg?alt=media&amp;token=86e5d1a2-23a6-4170-b225-718549f4e2b9" alt=""><figcaption></figcaption></figure>

#### Verify Fund Availability

Check with sponsor bank that sufficient funds are available for the full disbursement amount.

#### Reserve Funds at Bank

Block or reserve funds at the sponsor bank to guarantee availability for payment.

#### Initiate Payments

Trigger actual payment execution from sponsor bank to beneficiary accounts.

#### Support Multiple Payment Methods

Support payments via:

* Bank account transfer (using IFSC codes)
* Mobile wallet (with provider codes)
* Email wallet (with provider information)

#### Track Payment Status

Monitor payment status from initiation through completion (pending, processed, failed).

#### Handle Payment Failures

Capture and document payment failures with specific failure codes and reasons.

#### Automatic Payment Retries

Automatically retry failed payments up to configurable maximum attempts.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openg2p.org/products/g2p-bridge/features/funds-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
