Secure soft-pull prequalification and authorized hard-pull credit workflows, giving the store one credit profile that Velocity Finance can structure and route against. Consent and permissible purpose are recorded before any inquiry runs.
A hard inquiry costs the customer something. Running one early, on a customer who is still deciding, is a habit that is easy to build into software and hard to defend afterwards. This module is built so it cannot happen by accident.
Written consent and a permissible purpose are captured and timestamped before an inquiry is made. Not as a checkbox in a settings page: as a gate the workflow cannot get past.
Prequalification with no impact to the customer's score. Enough to tier the deal, rank the routes and have a real conversation about payment.
The authorized hard pull runs when the customer has agreed to a structure and a lender is being submitted. Not before, and never automatically.
Bureau, report, score and date, versioned, and tiered against each lender's current program. One credit picture instead of three copies in three systems.
If a lender declines, the reason is captured with the inquiry, the score and the program version it was judged against. A declined customer can be told why, because the record of why still exists.
Illustrative product interface. Synthetic data, not customer data. Bureau names, scores and lender programs are invented for this mockup.
The consent record sits at the top of the file, with when it was captured, who captured it and what purpose it was captured for. The hard pull is visibly not run. The tiering names the program version each lender was judged against, because a tier assigned against last month’s program is not a tier.
If a lender declines, the reason is captured with the inquiry, the score and the program version. A declined customer can be told why, because the record of why still exists.
Credit is a separate module rather than a feature of the desk, because a credit pull carries obligations that deal structuring does not. Keeping it separate keeps those obligations visible.
Consent is usually captured on the showroom iPad, at the point the customer asks what they can be approved for.
Soft pull, tier, and route options. The hard pull waits for a structure the customer has agreed to.
Both structure and route against the same profile, tiered against the same current programs.
Credit data is non-public personal information, and a pull needs recorded consent and a permissible purpose. The platform never approves or denies credit on its own: it assembles the evidence, shows its reasoning, and a human decides. Every inquiry, score, rule version and approver is auditable.
Reviews the credit profile and the approved structure, then recommends the lender most likely to fund it on the best terms for the customer and the store.
Structures the pencil, then shows which lenders are most likely to approve it and at what gross. Every number deterministic, every route approved by a manager.
