# Fieldproof Partner API > Field collections as an API for regulated Indian lenders. Push an overdue loan book over a signed HTTP API; verified field partners work the cases on the ground; collections land directly on the lender's own payment rails and every outcome returns as a sequenced webhook. Fieldproof never holds, routes or touches borrower funds, and cash is never accepted. A Fluxus Forge product. Production API host: gig.quikkred.in. Sandbox: alpha-gig.quikkred.in. Key facts an integrator needs: - Auth is HMAC-SHA256 over a canonical request string; keys are environment-locked. - Cases arrive by push API (real-time), pull API (we fetch every 30 min), or CSV. - Five events: case.received, case.assigned, visit.completed, payment.collected, case.closed. - Every event carries a per-case monotonic `sequence` and absolute (not delta) amounts. - Webhook delivery is at-least-once; dedupe on `eventId`. Retries run 0s/30s/2m/10m/1h/6h/24h, then park replayable for 30 days. - Full corpus for ingestion: https://developers.fluxusforge.in/llms-full.txt - OpenAPI 3 spec: https://developers.fluxusforge.in/openapi/partner-v1.json ## Getting started - [Welcome](https://developers.fluxusforge.in/getting-started/welcome): How the Fieldproof Collection Network works and what integrating takes. - [Integration paths](https://developers.fluxusforge.in/getting-started/integration-paths): Choose how cases reach us and how money reaches you. - [Onboarding & registration](https://developers.fluxusforge.in/getting-started/onboarding): Everything you provide to register, and everything you receive back. - [Environments & credentials](https://developers.fluxusforge.in/getting-started/environments): Sandbox vs production, key environments, and how credentials behave. - [Quickstart: first case in 15 minutes](https://developers.fluxusforge.in/getting-started/quickstart): Health check → push a case → receive your first webhook. ## Core concepts - [Case lifecycle & statuses](https://developers.fluxusforge.in/core-concepts/case-lifecycle): The external status model and visit outcomes you will see. - [Data contract](https://developers.fluxusforge.in/core-concepts/data-contract): Every field a case row can carry — required, recommended, formats. - [Idempotency & reliability](https://developers.fluxusforge.in/core-concepts/reliability): The guarantees — no lost updates, no double-applies, recoverable order. ## Authentication - [Signing requests (HMAC)](https://developers.fluxusforge.in/authentication/signing-requests): The two-part credential and the canonical string every request signs. - [Debugging signatures](https://developers.fluxusforge.in/authentication/debugging-signatures): The sandbox echo endpoint that shows you exactly what the server computed. - [Key lifecycle & security](https://developers.fluxusforge.in/authentication/key-security): Rotation, revocation, lockout, and how to store credentials. ## Sending cases - [Push API (recommended)](https://developers.fluxusforge.in/sending-cases/push-api): POST your overdue book — dry-run, commit, update, snapshot, recall. - [Pull API (we fetch from you)](https://developers.fluxusforge.in/sending-cases/pull-api): The one endpoint you expose if you can't make outbound calls. - [CSV (no-code fallback)](https://developers.fluxusforge.in/sending-cases/csv): Start collecting before writing any code. ## Receiving updates - [Webhooks](https://developers.fluxusforge.in/receiving-updates/webhooks): The receiver contract — five rules and copy-paste implementations. - [Event reference](https://developers.fluxusforge.in/receiving-updates/event-reference): Every event type with a real sample payload. - [Poll API (fallback)](https://developers.fluxusforge.in/receiving-updates/poll-api): The same event stream, pulled by cursor. - [Delivery log & replay](https://developers.fluxusforge.in/receiving-updates/delivery-log): Self-serve visibility into every webhook we sent you — and re-sending them. - [Updating your LMS from our events](https://developers.fluxusforge.in/receiving-updates/updating-your-lms): Copy-paste patterns for applying payment and closure events to your loan records. ## Payments - [How money flows (never through us)](https://developers.fluxusforge.in/payments/how-money-flows): The core guarantee and the two payment modes compared. - [Mode A: your static QR / bank](https://developers.fluxusforge.in/payments/static-qr): Zero-build payments — proof-verified collections into your account. - [Mode B: your gateway's links](https://developers.fluxusforge.in/payments/your-gateway): The mint-link endpoint you build and the confirm call you make. - [Reconciliation](https://developers.fluxusforge.in/payments/reconciliation): Three independent ways to prove the books agree. ## Testing - [Sandbox testing](https://developers.fluxusforge.in/testing/sandbox): Prove every leg of your integration before go-live. - [Reference implementation](https://developers.fluxusforge.in/testing/reference-implementation): A runnable mock organisation implementing every contract in these docs. - [Go-live checklist](https://developers.fluxusforge.in/testing/go-live-checklist): What we verify together before production credentials are issued. ## Resources - [Errors & rate limits](https://developers.fluxusforge.in/resources/errors): Every error code, what causes it, and what to do. - [Security & compliance commitments](https://developers.fluxusforge.in/resources/security): What we guarantee about your data — the answers for your security review. - [Versioning policy](https://developers.fluxusforge.in/resources/versioning): What "v1 is stable" means, precisely. - [FAQ & support](https://developers.fluxusforge.in/resources/faq): Common questions, and how to reach us.