Quikkred Collection Network — Developer Documentation
Quikkred runs a nationwide field-collection network: verified, trained collection partners who visit your overdue borrowers, collect payment on your own payment rails, and feed every update back into your system in near-real-time.
Integrating means two data flows:
- Cases in — you push your overdue loans to our API (or we pull from yours, or ops imports a CSV).
- Our field partners run the entire visit / collection workflow — nothing for you to build there.
- Money goes directly to you — via your static QR / bank details or payment links minted by your own gateway. Quikkred never holds your borrowers' funds, and cash is not accepted on your cases.
- Updates out — every meaningful change (case received, assigned, visit outcome, payment, closure) is delivered to your webhook endpoint as a signed, sequenced event, with a poll API as fallback.
What integration takes
| Effort level | You build | Typical time |
|---|---|---|
| API (recommended) | One outbound API client + one webhook receiver | 1–2 engineer-days |
| Pull | One read endpoint on your side | ~1 engineer-day |
| CSV | Nothing — email us a file | 0 |
Start with the integration paths chooser,
then follow the quickstart — most teams see
their first case.received webhook within an hour of receiving sandbox
credentials.
Working reference implementation
Everything in these docs is implemented in a small runnable reference organisation (mock LMS + dashboard) you can download and run against the sandbox — see Reference implementation.