<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Guillaume&#039;s blog &#187; integration</title>
	<atom:link href="http://lebleu.org/blog/tags/integration/feed/" rel="self" type="application/rss+xml" />
	<link>http://lebleu.org/blog</link>
	<description>Thoughts on the future of money</description>
	<lastBuildDate>Tue, 16 Jun 2015 08:19:39 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.1.42</generator>
	<item>
		<title>Improving the home loan application process</title>
		<link>http://lebleu.org/blog/2009/01/31/improving-the-home-loan-application-process/</link>
		<comments>http://lebleu.org/blog/2009/01/31/improving-the-home-loan-application-process/#comments</comments>
		<pubDate>Sun, 01 Feb 2009 03:46:38 +0000</pubDate>
		<dc:creator><![CDATA[Guillaume Lebleu]]></dc:creator>
				<category><![CDATA[banking]]></category>
		<category><![CDATA[integration]]></category>
		<category><![CDATA[oauth]]></category>

		<guid isPermaLink="false">http://lebleu.org/blog/2009/01/31/improving-the-home-loan-application-process/</guid>
		<description><![CDATA[I recently was very fortunate to purchase a house in San Francisco. As most home buyers, as part of the process, I had to get a loan approval  and to provide a lot of paper-based information. Unsurprisingly, I submitted this information in the form of electronically scanned print outs of various online Web services (thank &#8230; <a href="http://lebleu.org/blog/2009/01/31/improving-the-home-loan-application-process/" class="more-link">Continue reading <span class="screen-reader-text">Improving the home loan application process</span></a>]]></description>
				<content:encoded><![CDATA[<p>I recently was very fortunate to purchase a house in San Francisco. As most home buyers, as part of the process, I had to get a loan approval  and to provide a lot of paper-based information. Unsurprisingly, I submitted this information in the form of electronically scanned print outs of various online Web services (thank Science I didn&#8217;t have to mail printed statements). This pile of information was then manually verified for accuracy and authenticity, and the relevant information was manually fed to a mortgage approval system.</p>
<p>Here is the information I had to provide:</p>
<ul></ul>
<ol>
<li>Hazard insurance policy</li>
<li>Complete institutional statements covering most recent months + as applicable, reasonable explanation and documentation for any large deposits within the last 60 days</li>
<li>Copy of the purchase signed agreement</li>
<li>To verify salary: 1) paystubs for the last 30 days 2) last 2 years W2s</li>
<li>Landlord reference verifying payment history for the past 12 months</li>
<li>Verification of stocks/bons as stated in application</li>
<li>Evidence of residency and employment status in the US</li>
<li>Verified employment with employee through verbal conversation or electronic verification of employment</li>
<li>Verification of applicant&#8217;s identity (identification certification document signed by authorized bank representative and faxed)</li>
</ol>
<ul></ul>
<p>I won&#8217;t talk about #9, which is simply ridiculous since I&#8217;ve applied for this loan at a bank I&#8217;ve been banking with since 1998 and who also handles my brokerage account. I don&#8217;t know how many times they have verified thoroughfully my identity. I won&#8217;t comment on #7, but needless to say that when I know very well that the INS has this information accessible in real-time. Regarding #3, it might already be possible to directly extract from a digitally signed pruchase agreement PDF form the relevant information. If not today, probably very soon.</p>
<p>What&#8217;s really interesting is #1, #2, #4 and #6.</p>
<p>#1 is information I received from my insurer, but I assume it is available from my insurance&#8217;s Web service in HTML/PDF format.</p>
<p>#2 and #6 (and partially for #4 since I receive my paychecks by wire transfer to my checking account) is information that can be retrieved today directly from my bank or brokerage&#8217;s firm Web service.</p>
<p>There are several building blocks needed to achieve this:</p>
<ul>
<li>Information can be extracted from content. This assumes that the HTML content is either semantically tagged using a (yet to define) microformat, or available in alternative format, say some industry XML standard like ACORD XML for insurance or OFX for banking/brokerage information.</li>
<li>I can tell my bank to authorize the inquiring party that they can retrieve specific pieces of information. Also, I can specify to the inquiring party who they can inquire this information from. This is were an authentication delegation protocol like OAuth can be useful.</li>
</ul>
<p>#4 (Landlord reference verifying payment history for the past 12 months) is interesting. My current landlord and I banking at the SAME bank, I would have enjoyed the possibility of being able to tag some of my transactions with &#8220;rent&#8221; and share it with him so that he could validate them.</p>
]]></content:encoded>
			<wfw:commentRss>http://lebleu.org/blog/2009/01/31/improving-the-home-loan-application-process/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>
