# LEO1

> LEO1 is a Mumbai-based education fintech (founded 2017) running an all-in-one campus and financial platform for Indian educational institutions: co-branded student and alumni prepaid cards, institutional fee collection and reconciliation, and fee-financing (education loan) journeys. The LEO1 Fees SDK is the integration surface — a server-to-server transaction start plus a browser checkout SDK, with payment-gateway and fee-finance webhooks. Backed by QED Investors.

Generated by the API Evangelist enrichment pipeline on 2026-07-19. This file was authored from the provider's public surfaces; LEO1 does not publish an llms.txt.

## APIs

- [LEO1 Fees API](https://docs.leo1.in/): Production REST API (service name `leofees_backend`) covering students, fee dues and structures, fee collections, transactions, payments and settlements, refunds, penalties, waivers, NACH/eNACH mandates, documents and institute administration. Base URL `https://api.leo1.in`, all paths under `/api/v1`. OpenAPI 3.0.2, 152 paths, 184 operations, 121 schemas.

## Specs

- [OpenAPI (verbatim, as published)](openapi/leo1-leofees-openapi-original.json): harvested from https://api.leo1.in/openapi.json
- [API Evangelist overlay](overlays/leo1-leofees-overlay.yaml): adds the missing servers[], a real title/description, and the request-signing contract

## Docs

- [Leo1 Fees SDK — introduction](https://docs.leo1.in/intro): what you need to integrate (Access Key + Secret Key)
- [Server integration](https://docs.leo1.in/integrations/server-integration): the SHA-512 hash sequence and Start Transaction call
- [Web integration](https://docs.leo1.in/integrations/web-integration): loading the browser checkout SDK
- [Start Transaction API](https://docs.leo1.in/api/start-transaction)
- [Get Institute Transactions](https://docs.leo1.in/api/get-institute-transactions)
- [Retrieve Institute Transactions](https://docs.leo1.in/api/retrieve-institute-transactions)
- [Retrieve Settlements](https://docs.leo1.in/api/retrieve-settlements)
- [Payment Gateway webhook](https://docs.leo1.in/webhooks/pg)
- [Fee Finance webhook](https://docs.leo1.in/webhooks/fee-finance)

## How to integrate

1. Obtain an Access Key and Secret Key from LEO1 (no self-service signup).
2. Sign the request: lowercase hex SHA-512 of `key|total_fees|fees_paid|student_name|roll_number|branch_name|course_name|parent_name|institute_name|phone_number|erp_transaction_id` with the Secret Key appended. Trim all values first.
3. `POST /api/v1/sdk/start_transaction` server-to-server; the response is an encrypted `data` blob.
4. Pass `data` + Access Key to `initiateLeoFeesPayment()` (payment gateway) or `initiateLeoFees()` (loan journey) in the browser SDK, with `env` set to `test` or `prod`.
5. Reconcile from the webhook on `erp_transaction_id` — not from the browser callback.

## Conventions

- Auth: `secret-key` API key header (`APIKeyHeader`), on 127 of 184 operations.
- Versioning: URI path, `/api/v1`.
- Errors: only `200` and `422` are declared; `422` uses the FastAPI envelope `{"detail":[{"loc":[],"msg":"","type":""}]}`. Not RFC 9457.
- No idempotency key, no pagination, no documented rate limits.
- Environments: `https://api.leo1.in` (prod), `https://uatapi.leo1.in` (UAT/test, not publicly reachable).

## Repo artifacts

- [Conventions](conventions/leo1-conventions.yml)
- [Authentication](authentication/leo1-authentication.yml)
- [Error catalog](errors/leo1-problem-types.yml)
- [Webhook catalog](asyncapi/leo1-fees-webhooks.yml)
- [Data model](data-model/leo1-data-model.yml)
- [Sandbox / environments](sandbox/leo1-sandbox.yml)
- [Embedded components](components/leo1-components.yml)
- [Lifecycle](lifecycle/leo1-lifecycle.yml)
- [Conformance](conformance/leo1-conformance.yml)
- [Domain security](security/leo1-domain-security.yml)
- [Agent skills](skills/_index.yml)

## Optional

- [Company website](https://www.leo1.in/)
- [Terms and conditions](https://www.leo1.in/terms-and-conditions/)
- [Privacy policy](https://www.leo1.in/privacy-policy/)
- [Contact](https://www.leo1.in/alumni/contact_us/)

## Not published

LEO1 publishes no llms.txt, no `.well-known` discovery documents, no security.txt or vulnerability-disclosure program, no trust center or named certifications, no status page, no changelog, no roadmap, no CLI, no public GitHub organisation, no package-registry SDKs, no AsyncAPI, and no MCP server. Those gaps are recorded as honest negatives in the repo artifacts rather than filled in.