> For the complete documentation index, see [llms.txt](https://developer.sahamati.org.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.sahamati.org.in/sahamatinet-agent-sna/billing.md). # Billing This section covers the billing data that SNA captures and submits to Sahamati on behalf of the AA, including the API endpoints, payload schema, and response codes. SNA captures billing data at the AA-FIU interface (integration points E, F, G, H). No separate integration is needed: AAs call `sna.dispatch()` at these points and send the applicable additional attributes. SNA aggregates the data and pushes it to Sahamati automatically. See Integration Points and Additional Attributes (addlAttr). #### What SNA Uses for Billing * **FIU-side API transactions:** consent and data-fetch requests received from FIUs, and the AA's responses to them. * **Consent types:** the `consentTypes` attribute sent with each /FI/request lets SNA identify whether a data fetch is for transactions or only for profile and summary, since these are billed differently. Billing data is reported per FIU and per FIP. #### In This Section * **Endpoints & Authentication** - the Sahamati billing endpoint URLs and how authentication works. * **Billing Payload** - schema reference for the billing payload. * **Response Codes** - HTTP responses returned by the Sahamati billing endpoint. --- # 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://developer.sahamati.org.in/sahamatinet-agent-sna/billing.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.