Fix KRIDES KYC Verification Issue

Our KRIDES user-onboarding flow stalls at the KYC step. After applicants upload their documents the system either hangs or returns a generic failure message, blocking new registrations and support tickets keep piling up. The task is to trace whatever is causing that break, patch it, and restore a smooth, fully automated verification loop.

You will need to:
• Audit the current KYC logic (front-end hand-off, API call, callback handling, database write).
• Identify and eliminate the error that prevents the “verified / rejected” status from reaching the user interface.
• Implement clear error messaging for edge cases so support can see exactly why a submission failed.
• Hand over a concise changelog explaining what was fixed and how to replicate the solution on staging and production.

Acceptance criteria
1. A fresh test account can move from document submission to verified status without manual intervention.
2. Average verification time is back under two minutes.
3. No 500-level errors appear in server logs during the flow.
4. Changelog delivered and code committed to the main repository without breaking existing features.

Access to the repo, staging keys, and the current KYC provider’s dashboard will be shared as soon as we start. I’m ready to test a working fix right away, so please bring solid debugging skills and an eye for clean, maintainable code.