Choose your integration path
Two decisions define your integration. Both are set per-organisation at onboarding and can be changed later.
Decision 1 — How do your cases reach us?
| Push API (recommended) | Pull API | CSV | |
|---|---|---|---|
| How it works | You POST batches of overdue loans to our API | We fetch from a read endpoint you expose, every 30 min | You send a file; our ops imports it |
| Freshness | Real-time | ≤30 min | Manual |
| You build | Outbound HTTPS client with request signing | One GET endpoint (contract) | Nothing |
| Best for | Teams with engineering capacity | Systems that can't make outbound calls | Getting started before any build |
Decision 2 — How does money reach you?
Always directly. Quikkred never holds or routes your borrowers' funds, and cash is not accepted on your cases — our partner app enforces this. You choose the rail:
| Mode A: your static QR / bank | Mode B: your gateway's links | |
|---|---|---|
| Borrower pays via | Your fixed UPI QR / bank transfer, shown in the partner app | A payment link minted by your gateway, sent to the borrower |
| Confirmation | Partner uploads proof → our ops verifies → webhook | You call payments/confirm when your gateway captures |
| You build | Nothing | A mint-link endpoint + one confirm call |
| Best for | Fastest start; no gateway required | Fully automatic, instant confirmation |
The requirement matrix
You build / provide
- Org registration details (what exactly)
- Push: an API client that signs requests
- Pull: one cursor-paged read endpoint
- A webhook receiver (HTTPS, verifies signatures, dedupes) — or use the poll API instead
- Mode A: your QR image / UPI ID / bank details
- Mode B: a mint-link endpoint + capture confirmations
We provide
- Sandbox + production credentials and this documentation
- The entire field operation: partner network, visits, RBI-compliant conduct
- Case management, deduplication, geocoding, assignment
- Signed webhooks with retries, a poll API, delivery log + self-serve replay
- Proof verification (Mode A) and payment ledger either way
- The reference implementation of every contract you need to build
Whatever you choose, the data contract and the event stream are identical — switching paths later doesn't change your parser.