Steps
This section details the different stages (steps) of lead evaluation. The API response content varies depending on these steps and access modules.
Lead Steps​
| Step | Description |
|---|---|
NEEDS_CU | Initial step where leads are created. For some partners, financial information from third parties has already been extracted. A lead may remain in this step for the following reasons: - Has not entered their ClaveĂšnica - Information extracted from ClaveĂšnica is insufficient to determine current formal employment status, requiring the lead to specify their employment condition - In cases where insufficient information is available, some leads are classified for Previred confirmation (via Experian). If the lead enters this flow and hasn't completed it (or an error occurred), they will remain here |
NEEDS_ICP | In cases where there is insufficient information to evaluate a lead, some leads are classified for Previred confirmation (via Experian). If the lead enters this flow and hasn't completed it (or an error occurred during the process), they will remain in this step |
UPLOAD_DOCUMENTS | The lead is required to upload their latest pay stub for Machine Learning algorithm analysis. This occurs in three scenarios: - Being evaluated for a Payroll Deduction (DPP) product - AFC information (via ClaveĂšnica) shows salary above taxable limit and SII information doesn't show higher salary - Previred information shows salary above taxable limit and SII information doesn't show higher salary |
FILL_FORM | Contact data verification step |
DATA_OK | All leads with complete risk parameters (RiskParams) from a reliable information source reach this step. If an API response returns a lead in this step, it indicates an error in the pre-approval/rejection verdict (PreApprove) generation process |
LOAN_SIMULATION | After generating PreApproves, leads from partners with placement access module proceed to product simulation. Depending on the product, some leads may sign digitally automatically |
READY_FOR_LOAN | Reached in three ways: 1. If partner has evaluation:lite access module: Occurs after DATA_OK, ends flow WITHOUT pre-approval/rejection verdict 2. If partner lacks placement module: Occurs after DATA_OK, WITH pre-approval/rejection verdict 3. If risk parameters require agent confirmation: Occurs after LOAN_SIMULATION, WITH pre-approval/rejection verdict |
COMPANY_APPROVE | Specific to partners with Payroll Deduction (DPP) products. Occurs only when partners have the placement module, risk parameters are from a reliable source, and the DPP agreement company explicitly requires credit approval by their team |
ARCHIVED_SUCCESS | Leads successfully granted a product remain in this step |
ARCHIVED_FAIL | Leads classified as unsuitable for partner's product or manually archived via backoffice |
AGENT_CONTACT | Previously rejected leads (ARCHIVED_FAIL) that were manually unarchived |
Data Response Types
The number and type of information returned by the API depends on the current step and access modules.
Step Progression
Steps may vary depending on the partner's access modules and specific requirements of the financial product being evaluated.