> 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/cash-goods-and-services.md).
# Cash, goods & services
The G2P Bridge subsystem of OpenG2P handles all kinds of commodities and services that a benefit program wishes to disburse. All commodities and services are internally classified into 5 types
1. **Cash - Digitally transferred** (into beneficiary bank accounts or mobile wallets)
2. **Cash - Physically** given to beneficiaries by on field agents (G2P Bridge transfers money into accounts or wallets of agents)
3. **Goods** - Staples, fuels, books and other goods
4. **Services** - Any kind of services delivered as part of benefit delivery
5. **Combination** - A combination of goods & services
A single benefit program in the PBMS system might deliver more than one benefit (of varying types). However, prior to handing over the disbursement information to G2P Bridge, the upstream PBMS has to split the disbursement into distinct disbursement envelopes. Each envelope handles exactly one benefit code. Thus if a benefit program is configured to distribute 3 products, let's say, Wheat, Soy Beans and Oil, the PBMS will create 3 envelopes in G2P Bridge and hand over the individual disbursements under each of these distinct envelopes.
The processing of disbursement instructions within an envelope depends on the envelope's benefit code type (one of the 5 types given above).
The following diagram shows the detailed workflow within G2P Bridge for each of these product types.
---
# 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/cash-goods-and-services.md?ask=&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.
