13.2 Borrower onboarding

User stories

• As a DSA, I want to submit a lead with my attribution so I am paid when it converts.
• As a borrower, I want to know quickly if I’m eligible so I don’t waste time on a full application.
• As a CA, I want to refer my SME clients with their consent and earn a referral fee.
• As a partner (embedded), I want to surface a loan offer inside my product without my user leaving.
• As a repeat borrower, I want a fast path so my second loan disburses in hours.

API requirements

• POST /leads, GET /leads/{id}, POST /leads/{id}/qualify, POST /leads/{id}/convert-to-application.
• POST /pre-eligibility/check (GST / AA / soft bureau).
• POST /partners/sdk/init for embedded.
• GET /borrowers/{id}/repeat-eligibility.

Data model

• lead, channel, partner, sub_agent, campaign, pre_eligibility_check.
• Repeat-borrower attribution: link to existing borrower.

UI screens

• Borrower: landing → entry → pre-elig → continue to application.
• DSA / CA: lead submission, pipeline view.
• Partner: embedded widget / SDK.

Backend services

• Acquisition service.
• Pre-eligibility service.
• Attribution service.

External integrations

• PAN validation, GST summary, bureau soft pull, AA soft pull.
• SMS / WhatsApp for borrower OTP.

Test cases

• Lead created with proper attribution.
• Dedup blocks duplicate within 30 days.
• Pre-eligibility “yes” converts to application.
• Repeat borrower flow recognises existing profile.

Edge cases

• Same borrower via two channels (attribution).
• Channel deactivated mid-flow.
• Pre-eligibility “yes” that fails full underwriting.
• Embedded SDK in iframe-blocking parent.

Acceptance criteria

• Lead deduplication enforced.
• Channel attribution captured 100% of the time.
• Pre-eligibility latency < 30 seconds.
• Repeat-borrower flow disbursement TAT < 4 hours.