Open the loan in Vesta, run CreditDecisionEngine and PricingEngine on your rules, and get the findings and the price back on the file.
Re-keying between Vesta and pricing is how quotes go stale.
The file lives in Vesta. The quote often lives on another screen. Someone types the same facts twice, and the price on the call is not the price on the file.
Swivel chair
Price in one system. Decide in another. The desk copies fields by hand.
Duplicate entry
The same loan facts get typed twice. High-volume desks feel it first.
A stale quote
The rate sheet moved. The Vesta file did not.
Run the engines from the LOS you already use.
CreditDecisionEngine from Vesta
Your underwriting rules run through the integration and return conditions on the file.
PricingEngine from Vesta
Price the scenario from Vesta. Eligibility comes from the same rules that underwrite the loan.
Findings and price on the file
The decision and the quote come back inside Vesta. No second window for the answer.
Open the file. Request the engines. Stay in Vesta.
Open the loan in Vesta
The API puts LoanPASS on the file you already have open.
Request a price or a decision
CreditDecisionEngine and PricingEngine read the same rules as the shelf.
Read the answer on the file
Findings and price land in Vesta. Lock-desk rules can stop an ineligible lock.
Decision, price, and MI on one file.
CreditDecisionEngine decides the file. PricingEngine prices only the products that decision says the file fits. PMIPricer quotes MI from the LTV, FICO, and product already on the file. No re-keying.
Decision
CreditDecisionEngine returns approve, refer, or decline against your credit policy.
Explore CreditDecisionEngine
Price
PricingEngine returns rate, points, and adjustments for the products that decision says the file fits.
Explore PricingEngine
MI
PMIPricer compares every carrier using the LTV, FICO, and product already on the file.
Explore PMIPricer
What lenders ask first
What is the LoanPASS Vesta integration?
It is how lenders run CreditDecisionEngine and PricingEngine from a Vesta loan file. Pricing, eligibility, and underwriting stay on the file you already use.
Is LoanPASS integrated with Vesta?
Yes. LoanPASS connects by API with Vesta so pricing and decisioning can run inside your LOS.
What can I do from inside Vesta?
You can price loans, run eligibility, apply underwriting logic, and return conditions, all from the rules you configured in LoanPASS.
Does the integration support custom products?
Yes. Product guidelines, pricing structures, adjustments, and rules stay yours. LoanPASS brings them into the Vesta interface.
Can I apply underwriting rules in real time?
Yes. CreditDecisionEngine runs through the integration and returns conditions automatically.
Can lock controls run through Vesta?
Yes. You can enforce lock-desk policies and stop an ineligible loan from locking, based on your rules.
Does the integration need custom development?
No. LoanPASS uses open, documented APIs and works with your existing Vesta environment.
Can it run Non-QM and business purpose programs?
Yes. The same rules can cover Non-QM, DSCR, business purpose, and conventional, if you configured those programs.
Does LoanPASS replace Vesta?
No. Vesta keeps the file. CreditDecisionEngine returns the decision and PricingEngine returns the price.
See a live file priced in Vesta
Bring a Vesta file to the demo. We will run a price and a decision on your rules and show both coming back on the loan.
Schedule a Demo