Developer documentation
Disputes and corrections
Accept, investigate and resolve challenges while preserving a complete audit trail.
Open a dispute
POST /public/disputes is an intake endpoint and does not require authentication. At least enough context should be provided to identify the contested subject, account, event or reporting institution. description must be 20–5,000 characters and evidence_links accepts up to ten URLs.
Request body
{
"subject_id": "SUBJECT_ID",
"credit_event_id": "EVENT_ID",
"reported_institution_id": "INSTITUTION_ID",
"opened_by": "ExampleBorrower",
"reason": "PAYMENT_REPORTED_LATE",
"description": "The payment cleared before the due date. Ledger receipt attached.",
"evidence_links": ["https://evidence.example/receipt-1042"]
}Resolution workflow
- Acknowledge intake and preserve the returned dispute ID.
- Verify the requester and collect sufficient evidence through an approved channel.
- Review the reported account and immutable event history.
- Ask the reporting institution to validate its source record when required.
- If data is wrong, append a CORRECTION event; never delete history to hide the error.
- An RCN administrator records RESOLVED_CORRECTED, RESOLVED_UPHELD or REJECTED with a clear resolution.
- Notify the requester and retain the investigation record according to policy.
Institution monitoring
GET /disputes returns the authenticated institution's reported disputes; platform administrators receive the network list. Institutions should review this queue routinely and use dispute-linked audit evidence when responding.