Troubleshooting
Common issues specific to Collection Partner integrations.
Case Access
404 on Case Endpoints
Case access is scoped to your organization. You can read cases currently assigned to you and authorized historical snapshots from withdrawn assignments. Some test/demo reads also allow the managing partner. Unauthorized cases return 404; write operations have their own current-assignment checks.
Check the GET /cases response to see your assigned cases. For cases you submitted on behalf of clients, use GET /managed-cases instead.
Empty Case List Despite Portal Assignments
Cases in PendingVerification status may not appear if you're filtering by Active. Remove status filters or explicitly include PendingVerification:
GET /cases?statuses=PendingVerification,Active
Payment Recording
Amounts Don't Balance
The payment validation requires payoutCreditor + payoutCollectionPartner = paymentAmount (within 0.01 tolerance due to rounding).
Cannot Close as Paid
Close code Paid requires total recorded payments ≥ outstanding amount. If payments don't cover the full debt, use PartiallyPaid instead.
Commission Status Required
When paymentRecipient is Creditor (debtor paid the creditor directly), you must specify whether your commission has been settled:
{
"paymentRecipient": "Creditor",
"commissionPaymentStatus": "Unpaid"
}
Rate Limiting
If you hit 429 responses, you've exceeded the limits (2,000/min, 20,000/hour, 100,000/day). Implement exponential backoff and cache responses where appropriate. See Rate Limiting for retry strategies.