Credit Default Reporting

his guide explains how businesses and lenders integrate with Dikript to report delinquent individual and business loans for bureau submission. You send structured JSON; Dikript validates, submits, and lets you poll submission status until processing completes.

Overview

Capability	Description
Individual reporting	Report a delinquent loan where the borrower is a person (BVN, KYC, loan terms).
Business reporting	Report a delinquent loan where the borrower is a company (RC number, business profile, corporate officers, loan terms).
Status polling	After a successful report request, use submissionId to poll until processing is Success or Failed.
Field catalog	Discover allowed values for accountType, businessType, enums, and delinquency mapping.

Typical flow: Load catalog → build payload → POST report → store submissionId → poll GET status until terminal state.

---

Prerequisites

• Institution account onboarded with Dikript and an active wallet (or subscription model your consultant configured).
• Services enabled on your institution (by your Dikript consultant):
  • CRDEFAULTINDIVIDUAL – report individual defaulter
  • CRDEFAULTBUSINESS – report business defaulter
  • CRDEFAULTSTATUS – poll submission status
• API key – your institution secret API key (same as other Dikript verification APIs).
• Unique accountNumber per loan at your institution (used for updates and idempotency tracking).

---

Authentication

All endpoints use the same institution API key header as the rest of Dikript.

Header: Name is configured per environment (commonly X-Api-Key or as provided at onboarding).

HTTP

X-Api-Key: your_institution_secret_api_key
Content-Type: application/json

---

Recommended integration flow

1. GET  /creditregistry/api/v1/catalog
        → Load accountType, businessType, gender, repaymentFrequency, etc.

2. POST /creditregistry/api/v1/report/individual
   OR   /creditregistry/api/v1/report/business
        → On success: save data.submissionId and data.uploadId

3. GET  /creditregistry/api/v1/report/status/{submissionId}
        → Poll every few minutes until processingStatus is Success or Failed
        → Read uploadStatusList for human-readable progress lines

Important: A successful report response means the submission was accepted for processing, not that the bureau file is already updated. Always use step 3 for the final outcome.

---

Base URL and endpoints

Production base path:

Text

https://{your-dikript-host}/creditregistry/api/v1

Method	Path	Service code	Billed
GET	/catalog	—	No
POST	/report/individual	CRDEFAULTINDIVIDUAL	Yes (on HTTP 200 per Dikript rules)
POST	/report/business	CRDEFAULTBUSINESS	Yes
GET	/report/status/{submissionId}	CRDEFAULTSTATUS	Yes

---