13.4 Application

User stories

• As a borrower, I want to fill the application across multiple sessions without losing progress.
• As a DSA, I want to create and submit applications on behalf of the borrower.
• As an analyst, I want a complete data room per application to review quickly.
• As a borrower, I want consent screens that explain what data is being collected and why.

API requirements

• POST /applications, GET /applications/{id}, PUT /applications/{id}.
• POST /applications/{id}/sections/{name} (section save).
• POST /applications/{id}/submit.
• POST /applications/{id}/documents.
• POST /applications/{id}/consents.
• POST /applications/{id}/withdraw.

Data model

• application, application_section_data, existing_debt, application_bank_account, consent, document.

UI screens

• Borrower: multi-step form with save-and-resume; consent screens; document upload.
• DSA / analyst: assisted entry; submission and tracking.

Backend services

• Application service (orchestration).
• Document service (uploads + verification).
• Consent service.

External integrations

• PAN / GSTIN / Udyam / MCA / penny-drop for in-app validation.

Test cases

• Save-and-resume across sessions.
• Submit blocks on missing mandatory field.
• Consent capture full trail (IP, device, timestamp).
• Withdrawal closes application cleanly.

Edge cases

• Borrower changes section mid-fill.
• Document upload fails partway (large file).
• Borrower submits with stale GST status.
• Co-applicant with conflicting data.

Acceptance criteria

• Borrower can complete in 15 – 30 minutes typical.
• Save-and-resume works across devices.
• All consents persistently captured with audit trail.
• Submission blocked when prerequisites missing.