EKYC 3.0 — Stage 11: Final Validation

1. Stage 11 Objective

Stage 11 is the platform’s final automated gate before the account opening form (AOF) is generated. When the customer taps “Review & Proceed”, the backend executes 7 checks in strict sequence. The customer sees a loading screen while these checks run — there is no polling or partial-result display.

• 7 checks run in a defined order (some sequential, some parallel).
• Each check produces a pass/fail/skip result stored in final_validations.
• The STP/Non-STP decision is made at Check 6 — this evaluates all name-match scores, face-match, income proof type, C-SAFE, PEP, and AML flags.
• The customer remains on a loading screen for the entire duration; this is customer-triggered (not background/async).
• On success, the lead advances to FINAL_VALIDATION state with the STP decision recorded.

2. Preconditions

3. The 7 Checks

4. Check Execution Order

The 7 checks do not all run sequentially. The execution order is optimized for fail-fast and parallelism where checks are independent.

5. STP Decision Logic

Check 6 uses StpDecisionService.Evaluate() which inspects 8 independent flags. Every flag must evaluate to STP for the lead to qualify for straight-through processing. A single NON_STP flag routes the lead to operations review.

STP Decision Pseudocode

function StpDecisionService.Evaluate(leadId):
    flags = []

    // 1. Aadhaar name match
    if aadhaar_name_match >= 70:  flags.push(STP)
    else:                          flags.push(NON_STP, reason="AADHAAR_NAME_LOW")

    // 2. Bank name match
    if bank_name_match >= 70:     flags.push(STP)
    else:                          flags.push(NON_STP, reason="BANK_NAME_LOW")

    // 3. Face match
    if face_match >= 70:          flags.push(STP)
    else:                          flags.push(NON_STP, reason="FACE_MATCH_LOW")

    // 4. Income proof
    if income_proof.source == AUTO_FETCH:  flags.push(STP)
    else:                                   flags.push(NON_STP, reason="MANUAL_INCOME_PROOF")

    // 5. C-SAFE
    if csafe_result == CLEAR:     flags.push(STP)
    else:
        flags.push(NON_STP, reason="CSAFE_FLAGGED")
        escalateToCompliance(leadId, "CSAFE_FLAGGED")

    // 6. PEP declared
    if pep_declared == false:     flags.push(STP)
    else:
        flags.push(NON_STP, reason="PEP_DECLARED")
        escalateToCompliance(leadId, "PEP_DECLARED")

    // 7. AML/PEP mismatch
    if csafe_pep_flag == customer_pep_declaration:  flags.push(STP)
    else:
        flags.push(NON_STP, reason="AML_PEP_MISMATCH")
        escalateToCompliance(leadId, "AML_PEP_MISMATCH")

    // 8. eSign mismatch
    if esign_name_matches_lead:   flags.push(STP)
    else:                          flags.push(NON_STP, reason="ESIGN_MISMATCH")

    // Final decision
    if ALL flags == STP:
        return { decision: "STP", reason_codes: [] }
    else:
        return { decision: "NON_STP", reason_codes: [all NON_STP reasons] }

6. Backend Validations

7. Existing Stored Procedure Mapping

The following stored procedures in the existing system handle the logic that Stage 11 encapsulates. These must be analysed for business rules during migration.

8. Error / Drop Codes

9. Exit State

On successful completion of all 7 checks, the following state is written:

Exit State Pseudocode

// After all 7 checks pass
UPDATE leads SET
    state              = 'FINAL_VALIDATION',
    stp_decision       = @stpDecision,          -- 'STP' or 'NON_STP'
    stp_reason_codes   = @stpReasonCodesJson,   -- '[]' or '["AADHAAR_NAME_LOW","MANUAL_INCOME_PROOF"]'
    final_validation_ts = GETUTCDATE(),
    updated_at         = GETUTCDATE()
WHERE lead_id = @leadId;

INSERT INTO final_validations (lead_id, check_number, check_name, result, vendor_response, created_at)
VALUES
    (@leadId, 1, 'PAN_VALIDITY',     @check1Result, @check1Response, GETUTCDATE()),
    (@leadId, 2, 'PAN_NAME_VERIFY',  @check2Result, @check2Response, GETUTCDATE()),
    (@leadId, 3, 'NEGATIVE_LIST',    @check3Result, @check3Response, GETUTCDATE()),
    (@leadId, 4, 'DEDUPE',           @check4Result, @check4Response, GETUTCDATE()),
    (@leadId, 5, 'DATA_COMPLETENESS',@check5Result, @check5Response, GETUTCDATE()),
    (@leadId, 6, 'STP_DECISION',     @check6Result, @check6Response, GETUTCDATE()),
    (@leadId, 7, 'AOF_PRECHECK',     @check7Result, @check7Response, GETUTCDATE());

10. Vendor & Integration Calls

11. Database Tables

12. Implementation Notes