# Fannie Mae # Fannie Mae A government-sponsored enterprise whose automated underwriting engine is one of the two behind the agency eligibility product. Fannie Mae's Desktop Underwriter is one of the two engines Government fans a single canonical request out to. The engine returns a recommendation, an eligibility determination, and a set of numbered findings messages. The mapping is measured rather than estimated: the recorded design puts 378 elements on this side against 437 on the other, with 258 in common. Everything outside that intersection is why one canonical request needs a translation layer rather than a field-rename table. Its published test personas are the sandbox convention every integration adopted: identifiers in a defined range select success scenarios, and identifiers in another select failure scenarios, deterministically. ## Products it serves - Government - Connection ## How this integration is built - **connection configuration** — The wire protocol. One repository per vendor API call, not per vendor. - **language configuration** — The field mapping between the vendor's vocabulary and the canonical model. - **flow file** — The four-way translation: canonical request, vendor request, vendor response, canonical response. - **waterfall priority** — One line naming where this vendor sits in the vertical's ordering. - **status call** — Activating the vendor for a lender, optionally with the lender's own credentials. ## Evidence This vendor is on the roster because each of the following resolves to a committed artifact. - `1003-fanniemae-language-configuration` - `partner-fanniemae-language-configuration`