Skip to main content

Lead Re-evaluation

A pre-approval is a picture of a person's risk at the moment it was issued, and that picture can change. Lead re-evaluation lets you check a lead's risk again, at any time after its mortgage pre-approval, without the person going through Clave Única again. You send a RUT, and the same call answers whether anything worsened.

What you get back​

ResultMeaning
actualizadoNothing relevant worsened
a_revisarAt least one compared value worsened, but every policy filter still passes
rechazadoWith today's data, the person fails a filter of the policy that pre-approved them

Along with the result: what worsened, with the previous and the current value; the filters that fail, by name and never with their thresholds; the refreshed risk data, each value with its date; and a new lead for the person, with a link they can use to update their own evaluation.

It is an alert, not a new evaluation: it issues no new pre-approval and never modifies the original one. An actualizado over a pre-approval that was rejected does not approve it — estadoUltimoPreAprobacion tells you how that pre-approval stood.

How it works​

It starts from the person's most recent mortgage pre-approval with you, approved or rejected. Its policy is the one whose filters are checked, with the thresholds that applied to that person. If you name a project with externalEntityId, only that project's leads and pre-approvals count.

What banca.me can obtain on its own is refreshed; the rest is carried over. Protests and delinquencies, debts in the financial system, the alimony debtors' registry, age and debt with banca.me are refreshed as of fechaEvaluacion, and the debt ratios are recomputed with them. Salaries and employment data come from the person's own evaluation, so they are carried over.

"Worse" is measured net of inflation. Nine values are compared: protests over one and five years, written-off, consumer, commercial and mortgage debt, monthly debt service, total financial burden, and alimony debtor status. An amount counts as worse only if it rose more than the UF over the period plus a small margin, so a UF-indexed mortgage that only re-adjusted raises no alarm. The first re-evaluation compares against the data in effect when the pre-approval was issued; later ones compare against the previous re-evaluation.

A filter whose input is not available this time does not reject. If a source does not answer, the filters that depend on it are skipped, so an actualizado only says that no filter that could be checked failed.

The new lead​

Every new re-evaluation creates a lead for the same person, in the same PartnerEntity, pending Clave Única and with the refreshed data. It appears among your leads like any other, and no new_lead event is sent for it. If the person completes their evaluation from the link (urlEvaluacion, valid for 72 hours), it is a regular evaluation, with the usual pre_approve.

Only one re-evaluation lead stays open per person: when a new one finishes, earlier ones still pending Clave Única are closed. With externalEntityId, that applies within the project: one open re-evaluation lead per person and project.

Repeating it is safe​

  • Within 30 days of the last re-evaluation over the same pre-approval, you get that one back with reciente: true. Nothing is queried, no lead is created and no event is sent.
  • One runs at a time per lead. A call while one is running answers 409 reevaluacion_en_curso.
  • A person in the middle of an evaluation — from the original lead or from an earlier re-evaluation lead — answers 409 plr_en_evaluacion until it finishes. With externalEntityId, only that project's leads count.

Requirements​

  • The evaluation module. BNPL partners cannot use it.
  • A mortgage pre-approval with you, on a lead created on or after the date from which banca.me's privacy terms cover re-evaluation.
  • One RUT per call.

The result arrives in the response of POST /partner/lead/reevaluacion, in the reevaluation webhook event, and in the seguimiento field of GET /partner/pre-loan-request/{idNumber}. See the Integration Guide to wire it up.