<pat:PatentPublication xmlns:com="http://www.wipo.int/standards/XMLSchema/ST96/Common" xmlns:mat="http://www.w3.org/1998/Math/MathML3" xmlns:pat="http://www.wipo.int/standards/XMLSchema/ST96/Patent" xmlns:tbl="http://www.oasis-open.org/tables/exchange/1.0" com:languageCode="en" com:documentFileName="merged_unified.xml" com:documentStatusText="N" com:st96Version="V4_0" pat:docId="352875558" pat:familyId="41134116"><com:IPOfficeCode>US</com:IPOfficeCode><pat:PublicationNumber>0008150764</pat:PublicationNumber><com:PatentDocumentKindCode>B2</com:PatentDocumentKindCode><com:PublicationDate>20120403</com:PublicationDate><pat:pending>false</pat:pending><pat:BibliographicData com:st96Version="V4_0" pat:source="NATIONAL"><pat:PatentPublicationIdentification pat:dataFormat="original"><com:IPOfficeCode>US</com:IPOfficeCode><pat:PublicationNumber>0008150764</pat:PublicationNumber><com:PatentDocumentKindCode>B2</com:PatentDocumentKindCode><com:PublicationDate>20120403</com:PublicationDate></pat:PatentPublicationIdentification><pat:PatentPublicationIdentification pat:dataFormat="docdb"><com:IPOfficeCode>US</com:IPOfficeCode><pat:PublicationNumber>8150764</pat:PublicationNumber><com:PublicationLanguageCode>en</com:PublicationLanguageCode><com:PatentDocumentKindCode>B2</com:PatentDocumentKindCode><com:PublicationDate>20120403</com:PublicationDate></pat:PatentPublicationIdentification><pat:PatentPublicationIdentification pat:dataFormat="epodoc"><pat:PublicationNumber>US8150764</pat:PublicationNumber><com:PublicationLanguageCode>en</com:PublicationLanguageCode></pat:PatentPublicationIdentification><pat:ApplicationIdentification pat:dataFormat="original"><com:ApplicationNumber><com:ApplicationNumberText>12417182</com:ApplicationNumberText></com:ApplicationNumber><pat:FilingDate>20090402</pat:FilingDate></pat:ApplicationIdentification><pat:ApplicationIdentification pat:dataFormat="docdb" pat:isRepresentative="YES" pat:docId="267548317"><com:IPOfficeCode>US</com:IPOfficeCode><com:ApplicationNumber><com:ApplicationNumberText>41718209</com:ApplicationNumberText></com:ApplicationNumber><pat:ApplicationFilingCategory>National</pat:ApplicationFilingCategory><pat:FilingDate>20090402</pat:FilingDate></pat:ApplicationIdentification><pat:PriorityClaimBag><pat:PriorityClaim com:sequenceNumber="1" pat:dataFormat="docdb" pat:isRepresentative="N"><com:IPOfficeCode>US</com:IPOfficeCode><com:ApplicationNumber><com:ApplicationNumberText>41718209</com:ApplicationNumberText></com:ApplicationNumber><pat:FilingDate>20090402</pat:FilingDate><com:PatentDocumentKindCode>US</com:PatentDocumentKindCode></pat:PriorityClaim><pat:PriorityClaim com:sequenceNumber="1" pat:dataFormat="epodoc"><com:ApplicationNumber><com:ApplicationNumberText>US20090417182</com:ApplicationNumberText></com:ApplicationNumber></pat:PriorityClaim><pat:PriorityClaim com:sequenceNumber="2" pat:dataFormat="docdb" pat:isRepresentative="Y"><com:IPOfficeCode>US</com:IPOfficeCode><com:ApplicationNumber><com:ApplicationNumberText>4262408</com:ApplicationNumberText></com:ApplicationNumber><pat:FilingDate>20080404</pat:FilingDate><com:PatentDocumentKindCode>US</com:PatentDocumentKindCode></pat:PriorityClaim><pat:PriorityClaim com:sequenceNumber="2" pat:dataFormat="epodoc"><com:ApplicationNumber><com:ApplicationNumberText>US20080042624P</com:ApplicationNumberText></com:ApplicationNumber></pat:PriorityClaim><pat:PriorityClaim com:sequenceNumber="3" pat:dataFormat="docdb" pat:isRepresentative="Y"><com:IPOfficeCode>US</com:IPOfficeCode><com:ApplicationNumber><com:ApplicationNumberText>4261208</com:ApplicationNumberText></com:ApplicationNumber><pat:FilingDate>20080404</pat:FilingDate><com:PatentDocumentKindCode>US</com:PatentDocumentKindCode></pat:PriorityClaim><pat:PriorityClaim com:sequenceNumber="3" pat:dataFormat="epodoc"><com:ApplicationNumber><com:ApplicationNumberText>US20080042612P</com:ApplicationNumberText></com:ApplicationNumber></pat:PriorityClaim><pat:PriorityClaim com:sequenceNumber="4" pat:dataFormat="docdb" pat:isRepresentative="Y"><com:IPOfficeCode>US</com:IPOfficeCode><com:ApplicationNumber><com:ApplicationNumberText>5245408</com:ApplicationNumberText></com:ApplicationNumber><pat:FilingDate>20080512</pat:FilingDate><com:PatentDocumentKindCode>US</com:PatentDocumentKindCode></pat:PriorityClaim><pat:PriorityClaim com:sequenceNumber="4" pat:dataFormat="epodoc"><com:ApplicationNumber><com:ApplicationNumberText>US20080052454P</com:ApplicationNumberText></com:ApplicationNumber></pat:PriorityClaim><pat:PriorityClaim com:sequenceNumber="5" pat:dataFormat="docdb" pat:isRepresentative="Y"><com:IPOfficeCode>US</com:IPOfficeCode><com:ApplicationNumber><com:ApplicationNumberText>6055908</com:ApplicationNumberText></com:ApplicationNumber><pat:FilingDate>20080611</pat:FilingDate><com:PatentDocumentKindCode>US</com:PatentDocumentKindCode></pat:PriorityClaim><pat:PriorityClaim com:sequenceNumber="5" pat:dataFormat="epodoc"><com:ApplicationNumber><com:ApplicationNumberText>US20080060559P</com:ApplicationNumberText></com:ApplicationNumber></pat:PriorityClaim><pat:PriorityClaim com:sequenceNumber="6" pat:dataFormat="docdb" pat:isRepresentative="Y"><com:IPOfficeCode>US</com:IPOfficeCode><com:ApplicationNumber><com:ApplicationNumberText>8286308</com:ApplicationNumberText></com:ApplicationNumber><pat:FilingDate>20080723</pat:FilingDate><com:PatentDocumentKindCode>US</com:PatentDocumentKindCode></pat:PriorityClaim><pat:PriorityClaim com:sequenceNumber="6" pat:dataFormat="epodoc"><com:ApplicationNumber><com:ApplicationNumberText>US20080082863P</com:ApplicationNumberText></com:ApplicationNumber></pat:PriorityClaim><pat:PriorityClaim com:sequenceNumber="7" pat:dataFormat="docdb" pat:isRepresentative="Y"><com:IPOfficeCode>US</com:IPOfficeCode><com:ApplicationNumber><com:ApplicationNumberText>5305608</com:ApplicationNumberText></com:ApplicationNumber><pat:FilingDate>20080514</pat:FilingDate><com:PatentDocumentKindCode>US</com:PatentDocumentKindCode></pat:PriorityClaim><pat:PriorityClaim com:sequenceNumber="7" pat:dataFormat="epodoc"><com:ApplicationNumber><com:ApplicationNumberText>US20080053056P</com:ApplicationNumberText></com:ApplicationNumber></pat:PriorityClaim></pat:PriorityClaimBag><pat:PatentClassificationBag><pat:NationalClassification><com:IPOfficeCode>US</com:IPOfficeCode><pat:MainNationalClassification><pat:PatentClassificationText>705/38</pat:PatentClassificationText></pat:MainNationalClassification><pat:FurtherNationalClassification><pat:PatentClassificationText>705/35</pat:PatentClassificationText></pat:FurtherNationalClassification><pat:FurtherNationalClassification><pat:PatentClassificationText>705/39</pat:PatentClassificationText></pat:FurtherNationalClassification></pat:NationalClassification><pat:IPCRClassificationBag><pat:IPCRClassification com:sequenceNumber="1"><pat:PatentClassificationText>G06Q  40/00        20120101AFI20120403BHUS        </pat:PatentClassificationText><pat:ClassificationVersionDate>20120101</pat:ClassificationVersionDate><pat:PatentClassificationLevelCode>A</pat:PatentClassificationLevelCode><com:SymbolPositionCode>F</com:SymbolPositionCode><pat:IPCClassificationValueCode>I</pat:IPCClassificationValueCode><pat:ActionDate>20120403</pat:ActionDate><pat:IPCClassificationStatusCode>B</pat:IPCClassificationStatusCode><pat:PatentClassificationDataSourceCode>H</pat:PatentClassificationDataSourceCode><pat:GeneratingOfficeCode>US</pat:GeneratingOfficeCode><pat:Section>G</pat:Section><pat:Class>06</pat:Class><pat:Subclass>Q</pat:Subclass><pat:MainGroup>40</pat:MainGroup><pat:Subgroup>00</pat:Subgroup></pat:IPCRClassification></pat:IPCRClassificationBag><pat:CPCClassificationBag><pat:MainCPC><pat:CPCClassification pat:text="G06Q  40/02        "><pat:CPCSection>G</pat:CPCSection><pat:Class>06</pat:Class><pat:Subclass>Q</pat:Subclass><pat:MainGroup>  40</pat:MainGroup><pat:Subgroup>02</pat:Subgroup><com:SymbolPositionCode>F</com:SymbolPositionCode><pat:CPCClassificationValueCode>I</pat:CPCClassificationValueCode><pat:ActionDate>20130101</pat:ActionDate><pat:GeneratingOfficeCode>EP</pat:GeneratingOfficeCode><pat:CPCClassificationStatusCode>B</pat:CPCClassificationStatusCode><pat:PatentClassificationDataSourceCode>H</pat:PatentClassificationDataSourceCode></pat:CPCClassification></pat:MainCPC><pat:FurtherCPC><pat:CPCClassification pat:text="G06Q  20/10        "><pat:CPCSection>G</pat:CPCSection><pat:Class>06</pat:Class><pat:Subclass>Q</pat:Subclass><pat:MainGroup>  20</pat:MainGroup><pat:Subgroup>10</pat:Subgroup><com:SymbolPositionCode>L</com:SymbolPositionCode><pat:CPCClassificationValueCode>I</pat:CPCClassificationValueCode><pat:ActionDate>20130101</pat:ActionDate><pat:GeneratingOfficeCode>EP</pat:GeneratingOfficeCode><pat:CPCClassificationStatusCode>B</pat:CPCClassificationStatusCode><pat:PatentClassificationDataSourceCode>H</pat:PatentClassificationDataSourceCode></pat:CPCClassification><pat:CPCClassification pat:text="G06Q  20/102       "><pat:CPCSection>G</pat:CPCSection><pat:Class>06</pat:Class><pat:Subclass>Q</pat:Subclass><pat:MainGroup>  20</pat:MainGroup><pat:Subgroup>102</pat:Subgroup><com:SymbolPositionCode>L</com:SymbolPositionCode><pat:CPCClassificationValueCode>I</pat:CPCClassificationValueCode><pat:ActionDate>20130101</pat:ActionDate><pat:GeneratingOfficeCode>EP</pat:GeneratingOfficeCode><pat:CPCClassificationStatusCode>B</pat:CPCClassificationStatusCode><pat:PatentClassificationDataSourceCode>H</pat:PatentClassificationDataSourceCode></pat:CPCClassification><pat:CPCClassification pat:text="G06Q  20/105       "><pat:CPCSection>G</pat:CPCSection><pat:Class>06</pat:Class><pat:Subclass>Q</pat:Subclass><pat:MainGroup>  20</pat:MainGroup><pat:Subgroup>105</pat:Subgroup><com:SymbolPositionCode>L</com:SymbolPositionCode><pat:CPCClassificationValueCode>I</pat:CPCClassificationValueCode><pat:ActionDate>20130101</pat:ActionDate><pat:GeneratingOfficeCode>EP</pat:GeneratingOfficeCode><pat:CPCClassificationStatusCode>B</pat:CPCClassificationStatusCode><pat:PatentClassificationDataSourceCode>H</pat:PatentClassificationDataSourceCode></pat:CPCClassification><pat:CPCClassification pat:text="G06Q  20/202       "><pat:CPCSection>G</pat:CPCSection><pat:Class>06</pat:Class><pat:Subclass>Q</pat:Subclass><pat:MainGroup>  20</pat:MainGroup><pat:Subgroup>202</pat:Subgroup><com:SymbolPositionCode>L</com:SymbolPositionCode><pat:CPCClassificationValueCode>I</pat:CPCClassificationValueCode><pat:ActionDate>20130101</pat:ActionDate><pat:GeneratingOfficeCode>EP</pat:GeneratingOfficeCode><pat:CPCClassificationStatusCode>B</pat:CPCClassificationStatusCode><pat:PatentClassificationDataSourceCode>H</pat:PatentClassificationDataSourceCode></pat:CPCClassification><pat:CPCClassification pat:text="G06Q  20/204       "><pat:CPCSection>G</pat:CPCSection><pat:Class>06</pat:Class><pat:Subclass>Q</pat:Subclass><pat:MainGroup>  20</pat:MainGroup><pat:Subgroup>204</pat:Subgroup><com:SymbolPositionCode>L</com:SymbolPositionCode><pat:CPCClassificationValueCode>I</pat:CPCClassificationValueCode><pat:ActionDate>20130101</pat:ActionDate><pat:GeneratingOfficeCode>EP</pat:GeneratingOfficeCode><pat:CPCClassificationStatusCode>B</pat:CPCClassificationStatusCode><pat:PatentClassificationDataSourceCode>H</pat:PatentClassificationDataSourceCode></pat:CPCClassification><pat:CPCClassification pat:text="G06Q  30/0234      "><pat:CPCSection>G</pat:CPCSection><pat:Class>06</pat:Class><pat:Subclass>Q</pat:Subclass><pat:MainGroup>  30</pat:MainGroup><pat:Subgroup>0234</pat:Subgroup><com:SymbolPositionCode>L</com:SymbolPositionCode><pat:CPCClassificationValueCode>I</pat:CPCClassificationValueCode><pat:ActionDate>20130101</pat:ActionDate><pat:GeneratingOfficeCode>EP</pat:GeneratingOfficeCode><pat:CPCClassificationStatusCode>B</pat:CPCClassificationStatusCode><pat:PatentClassificationDataSourceCode>H</pat:PatentClassificationDataSourceCode></pat:CPCClassification><pat:CPCClassification pat:text="G06Q  30/0236      "><pat:CPCSection>G</pat:CPCSection><pat:Class>06</pat:Class><pat:Subclass>Q</pat:Subclass><pat:MainGroup>  30</pat:MainGroup><pat:Subgroup>0236</pat:Subgroup><com:SymbolPositionCode>L</com:SymbolPositionCode><pat:CPCClassificationValueCode>I</pat:CPCClassificationValueCode><pat:ActionDate>20130101</pat:ActionDate><pat:GeneratingOfficeCode>EP</pat:GeneratingOfficeCode><pat:CPCClassificationStatusCode>B</pat:CPCClassificationStatusCode><pat:PatentClassificationDataSourceCode>H</pat:PatentClassificationDataSourceCode></pat:CPCClassification><pat:CPCClassification pat:text="G06Q  40/00        "><pat:CPCSection>G</pat:CPCSection><pat:Class>06</pat:Class><pat:Subclass>Q</pat:Subclass><pat:MainGroup>  40</pat:MainGroup><pat:Subgroup>00</pat:Subgroup><com:SymbolPositionCode>L</com:SymbolPositionCode><pat:CPCClassificationValueCode>I</pat:CPCClassificationValueCode><pat:ActionDate>20130101</pat:ActionDate><pat:GeneratingOfficeCode>EP</pat:GeneratingOfficeCode><pat:CPCClassificationStatusCode>B</pat:CPCClassificationStatusCode><pat:PatentClassificationDataSourceCode>H</pat:PatentClassificationDataSourceCode></pat:CPCClassification><pat:CPCClassification pat:text="G06Q  40/025       "><pat:CPCSection>G</pat:CPCSection><pat:Class>06</pat:Class><pat:Subclass>Q</pat:Subclass><pat:MainGroup>  40</pat:MainGroup><pat:Subgroup>025</pat:Subgroup><com:SymbolPositionCode>L</com:SymbolPositionCode><pat:CPCClassificationValueCode>I</pat:CPCClassificationValueCode><pat:ActionDate>20130101</pat:ActionDate><pat:GeneratingOfficeCode>EP</pat:GeneratingOfficeCode><pat:CPCClassificationStatusCode>B</pat:CPCClassificationStatusCode><pat:PatentClassificationDataSourceCode>H</pat:PatentClassificationDataSourceCode></pat:CPCClassification><pat:CPCClassification pat:text="G06Q  40/04        "><pat:CPCSection>G</pat:CPCSection><pat:Class>06</pat:Class><pat:Subclass>Q</pat:Subclass><pat:MainGroup>  40</pat:MainGroup><pat:Subgroup>04</pat:Subgroup><com:SymbolPositionCode>L</com:SymbolPositionCode><pat:CPCClassificationValueCode>I</pat:CPCClassificationValueCode><pat:ActionDate>20130101</pat:ActionDate><pat:GeneratingOfficeCode>EP</pat:GeneratingOfficeCode><pat:CPCClassificationStatusCode>B</pat:CPCClassificationStatusCode><pat:PatentClassificationDataSourceCode>H</pat:PatentClassificationDataSourceCode></pat:CPCClassification></pat:FurtherCPC></pat:CPCClassificationBag></pat:PatentClassificationBag><pat:InventionTitleBag><pat:InventionTitle com:languageCode="en" pat:dataFormat="original">System, program product, and method to authorize draw for retailer optimization</pat:InventionTitle><pat:InventionTitle com:languageCode="en" pat:dataFormat="docdba">System, program product, and method to authorize draw for retailer optimization</pat:InventionTitle></pat:InventionTitleBag><pat:ReferenceCitationBag><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>3752904</com:DocumentNumber><com:EntityName>Waterbury</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19730800</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>4247759</com:DocumentNumber><com:EntityName>Yuris et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19810100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>4334307</com:DocumentNumber><com:EntityName>Bourgeois et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19820600</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>4439636</com:DocumentNumber><com:EntityName>Newkirk et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19840300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>4449040</com:DocumentNumber><com:EntityName>Matsuoka et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19840500</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>4528643</com:DocumentNumber><com:EntityName>Freeny, Jr.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19850700</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>4532416</com:DocumentNumber><com:EntityName>Berstein</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19850700</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>4577061</com:DocumentNumber><com:EntityName>Katzaff et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19860300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>4625276</com:DocumentNumber><com:EntityName>Benton et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19861100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>4677565</com:DocumentNumber><com:EntityName>Ogaki et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19870600</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>4678895</com:DocumentNumber><com:EntityName>Tateisi et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19870700</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>4706275</com:DocumentNumber><com:EntityName>Kamal</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19871100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>4722054</com:DocumentNumber><com:EntityName>Yorozu et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19880100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>4727243</com:DocumentNumber><com:EntityName>Saver</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19880200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>4750201</com:DocumentNumber><com:EntityName>Hodgson et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19880600</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>4797540</com:DocumentNumber><com:EntityName>Kimizu</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19890100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>4827113</com:DocumentNumber><com:EntityName>Rikuna</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19890500</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>4868900</com:DocumentNumber><com:EntityName>McGuire</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19890900</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>4877947</com:DocumentNumber><com:EntityName>Mori</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19891000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>4879744</com:DocumentNumber><com:EntityName>Tasaki et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19891100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>4884212</com:DocumentNumber><com:EntityName>Stutsman</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19891100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>4951308</com:DocumentNumber><com:EntityName>Bishop et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19900800</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>4968873</com:DocumentNumber><com:EntityName>Dethloff et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19901100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5012077</com:DocumentNumber><com:EntityName>Takano</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19910400</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5048085</com:DocumentNumber><com:EntityName>Abraham et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19910900</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5050207</com:DocumentNumber><com:EntityName>Hitchcock</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19910900</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5068891</com:DocumentNumber><com:EntityName>Marshall</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19911100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5101098</com:DocumentNumber><com:EntityName>Naito</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19920300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5138650</com:DocumentNumber><com:EntityName>Stahl et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19920800</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5146067</com:DocumentNumber><com:EntityName>Sloan et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19920900</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5148481</com:DocumentNumber><com:EntityName>Abraham et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19920900</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5155342</com:DocumentNumber><com:EntityName>Urano</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19921000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5163086</com:DocumentNumber><com:EntityName>Ahearn et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19921100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5192947</com:DocumentNumber><com:EntityName>Neustein</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19930300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5220593</com:DocumentNumber><com:EntityName>Zicker et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19930600</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5221838</com:DocumentNumber><com:EntityName>Gutman et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19930600</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5225666</com:DocumentNumber><com:EntityName>Amarena et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19930700</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5264689</com:DocumentNumber><com:EntityName>Maes et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19931100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5265155</com:DocumentNumber><com:EntityName>Castro</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19931100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5266782</com:DocumentNumber><com:EntityName>Alan&#228;r&#228;et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19931100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5272320</com:DocumentNumber><com:EntityName>Hakamada</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19931200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5278752</com:DocumentNumber><com:EntityName>Narita et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19940100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5285382</com:DocumentNumber><com:EntityName>Muehlberger et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19940200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5327482</com:DocumentNumber><com:EntityName>Yamamoto</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19940700</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5334821</com:DocumentNumber><com:EntityName>Campo et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19940800</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5340969</com:DocumentNumber><com:EntityName>Cox</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19940800</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5352876</com:DocumentNumber><com:EntityName>Watanabe et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19941000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5359182</com:DocumentNumber><com:EntityName>Schilling</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19941000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5409092</com:DocumentNumber><com:EntityName>Itako et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19950400</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5416306</com:DocumentNumber><com:EntityName>Imahata</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19950500</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5438186</com:DocumentNumber><com:EntityName>Nair et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19950800</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5442567</com:DocumentNumber><com:EntityName>Small</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19950800</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5448044</com:DocumentNumber><com:EntityName>Price et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19950900</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5477038</com:DocumentNumber><com:EntityName>Levine et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19951200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5504808</com:DocumentNumber><com:EntityName>Hamrick, Jr.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19960400</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5511114</com:DocumentNumber><com:EntityName>Stimson et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19960400</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5513117</com:DocumentNumber><com:EntityName>Small</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19960400</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5550358</com:DocumentNumber><com:EntityName>Tait et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19960800</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5577109</com:DocumentNumber><com:EntityName>Stimson et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19961100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5577112</com:DocumentNumber><com:EntityName>Davis et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19961100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5661254</com:DocumentNumber><com:EntityName>Steuer et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19970800</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5696908</com:DocumentNumber><com:EntityName>Muehlberger et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19971200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5699528</com:DocumentNumber><com:EntityName>Hogan</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19971200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5732136</com:DocumentNumber><com:EntityName>Murphree et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19980300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5814798</com:DocumentNumber><com:EntityName>Zancho</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19980900</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5841365</com:DocumentNumber><com:EntityName>Rimkus</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19981100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5859419</com:DocumentNumber><com:EntityName>Wynn</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19990100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5875437</com:DocumentNumber><com:EntityName>Atkins</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19990200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5878141</com:DocumentNumber><com:EntityName>Daly et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19990300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5893907</com:DocumentNumber><com:EntityName>Ukuda</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19990400</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5897620</com:DocumentNumber><com:EntityName>Walker et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19990400</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5920848</com:DocumentNumber><com:EntityName>Schutzer et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19990700</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5933812</com:DocumentNumber><com:EntityName>Meyer et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19990800</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>5963921</com:DocumentNumber><com:EntityName>Longfield</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19991000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>6000608</com:DocumentNumber><com:EntityName>Dorf</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>19991200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>6012635</com:DocumentNumber><com:EntityName>Shimada et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>20000100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>6021397</com:DocumentNumber><com:EntityName>Jones et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>20000200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>6032859</com:DocumentNumber><com:EntityName>Muehlberger et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>20000300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>6041308</com:DocumentNumber><com:EntityName>Walker et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>20000300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>6065679</com:DocumentNumber><com:EntityName>Levie et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>20000500</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>6112191</com:DocumentNumber><com:EntityName>Burke</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>20000800</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>6144948</com:DocumentNumber><com:EntityName>Walker et al.</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>20001100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>6154738</com:DocumentNumber><com:EntityName>Call</com:EntityName><com:PatentDocumentKindCode>A</com:PatentDocumentKindCode><com:PatentDocumentDate>20001100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>6189787</com:DocumentNumber><com:EntityName>Dorf</com:EntityName><com:PatentDocumentKindCode>B1</com:PatentDocumentKindCode><com:PatentDocumentDate>20010200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>6208978</com:DocumentNumber><com:EntityName>Walker et al.</com:EntityName><com:PatentDocumentKindCode>B1</com:PatentDocumentKindCode><com:PatentDocumentDate>20010300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>6249773</com:DocumentNumber><com:EntityName>Allard et al.</com:EntityName><com:PatentDocumentKindCode>B1</com:PatentDocumentKindCode><com:PatentDocumentDate>20010600</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>6253998</com:DocumentNumber><com:EntityName>Ziamo</com:EntityName><com:PatentDocumentKindCode>B1</com:PatentDocumentKindCode><com:PatentDocumentDate>20010700</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>6467684</com:DocumentNumber><com:EntityName>Fite et al.</com:EntityName><com:PatentDocumentKindCode>B2</com:PatentDocumentKindCode><com:PatentDocumentDate>20021000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>6704714</com:DocumentNumber><com:EntityName>O'Leary et al.</com:EntityName><com:PatentDocumentKindCode>B1</com:PatentDocumentKindCode><com:PatentDocumentDate>20040300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>6739506</com:DocumentNumber><com:EntityName>Constantine</com:EntityName><com:PatentDocumentKindCode>B1</com:PatentDocumentKindCode><com:PatentDocumentDate>20040500</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>6865544</com:DocumentNumber><com:EntityName>Austin</com:EntityName><com:PatentDocumentKindCode>B1</com:PatentDocumentKindCode><com:PatentDocumentDate>20050300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>6999943</com:DocumentNumber><com:EntityName>Johnson et al.</com:EntityName><com:PatentDocumentKindCode>B1</com:PatentDocumentKindCode><com:PatentDocumentDate>20060200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7010507</com:DocumentNumber><com:EntityName>Anderson et al.</com:EntityName><com:PatentDocumentKindCode>B1</com:PatentDocumentKindCode><com:PatentDocumentDate>20060300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7031939</com:DocumentNumber><com:EntityName>Gallagher et al.</com:EntityName><com:PatentDocumentKindCode>B1</com:PatentDocumentKindCode><com:PatentDocumentDate>20060400</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7072862</com:DocumentNumber><com:EntityName>Wilson</com:EntityName><com:PatentDocumentKindCode>B1</com:PatentDocumentKindCode><com:PatentDocumentDate>20060700</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7127452</com:DocumentNumber><com:EntityName>Yashiro</com:EntityName><com:PatentDocumentKindCode>B1</com:PatentDocumentKindCode><com:PatentDocumentDate>20061000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7177829</com:DocumentNumber><com:EntityName>Wilson</com:EntityName><com:PatentDocumentKindCode>B1</com:PatentDocumentKindCode><com:PatentDocumentDate>20070200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7206761</com:DocumentNumber><com:EntityName>Colvin</com:EntityName><com:PatentDocumentKindCode>B2</com:PatentDocumentKindCode><com:PatentDocumentDate>20070400</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7258273</com:DocumentNumber><com:EntityName>Griffin</com:EntityName><com:PatentDocumentKindCode>B2</com:PatentDocumentKindCode><com:PatentDocumentDate>20070800</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7398919</com:DocumentNumber><com:EntityName>Cooper</com:EntityName><com:PatentDocumentKindCode>B2</com:PatentDocumentKindCode><com:PatentDocumentDate>20080700</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7426492</com:DocumentNumber><com:EntityName>Bishop et al.</com:EntityName><com:PatentDocumentKindCode>B1</com:PatentDocumentKindCode><com:PatentDocumentDate>20080900</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7451920</com:DocumentNumber><com:EntityName>Rose</com:EntityName><com:PatentDocumentKindCode>B1</com:PatentDocumentKindCode><com:PatentDocumentDate>20081100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7541920</com:DocumentNumber><com:EntityName>Rose</com:EntityName><com:PatentDocumentKindCode>B2</com:PatentDocumentKindCode><com:PatentDocumentDate>20081100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7509286</com:DocumentNumber><com:EntityName>Bent et al.</com:EntityName><com:PatentDocumentKindCode>B1</com:PatentDocumentKindCode><com:PatentDocumentDate>20090300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7567936</com:DocumentNumber><com:EntityName>Peckover et al.</com:EntityName><com:PatentDocumentKindCode>B1</com:PatentDocumentKindCode><com:PatentDocumentDate>20090700</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7606918</com:DocumentNumber><com:EntityName>Holzman et al.</com:EntityName><com:PatentDocumentKindCode>B2</com:PatentDocumentKindCode><com:PatentDocumentDate>20091000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7607570</com:DocumentNumber><com:EntityName>Constantine</com:EntityName><com:PatentDocumentKindCode>B1</com:PatentDocumentKindCode><com:PatentDocumentDate>20091000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7628319</com:DocumentNumber><com:EntityName>Brown et al.</com:EntityName><com:PatentDocumentKindCode>B2</com:PatentDocumentKindCode><com:PatentDocumentDate>20091200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7653591</com:DocumentNumber><com:EntityName>Dabney</com:EntityName><com:PatentDocumentKindCode>B1</com:PatentDocumentKindCode><com:PatentDocumentDate>20100100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7702583</com:DocumentNumber><com:EntityName>Hamilton et al.</com:EntityName><com:PatentDocumentKindCode>B1</com:PatentDocumentKindCode><com:PatentDocumentDate>20100400</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7757944</com:DocumentNumber><com:EntityName>Cline et al.</com:EntityName><com:PatentDocumentKindCode>B2</com:PatentDocumentKindCode><com:PatentDocumentDate>20100700</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7783571</com:DocumentNumber><com:EntityName>Fish et al.</com:EntityName><com:PatentDocumentKindCode>B2</com:PatentDocumentKindCode><com:PatentDocumentDate>20100800</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7792717</com:DocumentNumber><com:EntityName>Hankins et al.</com:EntityName><com:PatentDocumentKindCode>B1</com:PatentDocumentKindCode><com:PatentDocumentDate>20100900</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7810735</com:DocumentNumber><com:EntityName>Madani</com:EntityName><com:PatentDocumentKindCode>B2</com:PatentDocumentKindCode><com:PatentDocumentDate>20101000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7813955</com:DocumentNumber><com:EntityName>Ariff et al.</com:EntityName><com:PatentDocumentKindCode>B2</com:PatentDocumentKindCode><com:PatentDocumentDate>20101000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7814012</com:DocumentNumber><com:EntityName>Johnson</com:EntityName><com:PatentDocumentKindCode>B2</com:PatentDocumentKindCode><com:PatentDocumentDate>20101000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7904333</com:DocumentNumber><com:EntityName>Perkowski</com:EntityName><com:PatentDocumentKindCode>B1</com:PatentDocumentKindCode><com:PatentDocumentDate>20110300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>7933833</com:DocumentNumber><com:EntityName>Hotz et al.</com:EntityName><com:PatentDocumentKindCode>B2</com:PatentDocumentKindCode><com:PatentDocumentDate>20110400</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>8046256</com:DocumentNumber><com:EntityName>Chien et al.</com:EntityName><com:PatentDocumentKindCode>B2</com:PatentDocumentKindCode><com:PatentDocumentDate>20111000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>8051006</com:DocumentNumber><com:EntityName>Rourk</com:EntityName><com:PatentDocumentKindCode>B1</com:PatentDocumentKindCode><com:PatentDocumentDate>20111100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2001/0021925</com:DocumentNumber><com:EntityName>Ukigawa et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20010900</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2001/0034676</com:DocumentNumber><com:EntityName>Vasic</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20011000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2001/0042785</com:DocumentNumber><com:EntityName>Walker et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20011100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2002/0002075</com:DocumentNumber><com:EntityName>Rowe</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20020100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2002/0032612</com:DocumentNumber><com:EntityName>Williams et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20020300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2002/0038285</com:DocumentNumber><com:EntityName>Golden et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20020300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2002/0077971</com:DocumentNumber><com:EntityName>Allred</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20020600</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2002/0152161</com:DocumentNumber><com:EntityName>Aoike</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20021000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2002/0194122</com:DocumentNumber><com:EntityName>Knox et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20021200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2002/0194124</com:DocumentNumber><com:EntityName>Hobbs et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20021200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2003/0055782</com:DocumentNumber><com:EntityName>Slater</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20030300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2003/0061170</com:DocumentNumber><com:EntityName>Uzo</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20030300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2003/0074311</com:DocumentNumber><com:EntityName>Saylors et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20030400</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2003/0097331</com:DocumentNumber><com:EntityName>Cohen</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20030500</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2003/0135459</com:DocumentNumber><com:EntityName>Abelman et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20030700</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2003/0144935</com:DocumentNumber><com:EntityName>Sobek</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20030700</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2003/0158811</com:DocumentNumber><com:EntityName>Sanders et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20030800</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2003/0167225</com:DocumentNumber><com:EntityName>Adams</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20030900</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2003/0191702</com:DocumentNumber><com:EntityName>Hurley</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20031000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2003/0191714</com:DocumentNumber><com:EntityName>Norris</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20031000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2003/0197059</com:DocumentNumber><com:EntityName>Tidball et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20031000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2003/0200118</com:DocumentNumber><com:EntityName>Lee et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20031000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2003/0208443</com:DocumentNumber><com:EntityName>Mersky</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20031100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2003/0217003</com:DocumentNumber><com:EntityName>Weinflash et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20031100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2004/0036215</com:DocumentNumber><com:EntityName>Butler, II</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20040200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2004/0098351</com:DocumentNumber><com:EntityName>Duke</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20040500</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2004/0111370</com:DocumentNumber><com:EntityName>Saylors et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20040600</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2004/0117250</com:DocumentNumber><com:EntityName>Lubow et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20040600</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2004/0117302</com:DocumentNumber><com:EntityName>Weichert et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20040600</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2004/0133515</com:DocumentNumber><com:EntityName>McCoy et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20040700</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2004/0143527</com:DocumentNumber><com:EntityName>Benkert et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20040700</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2004/0148252</com:DocumentNumber><com:EntityName>Fleishman</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20040700</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2004/0153407</com:DocumentNumber><com:EntityName>Clubb et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20040800</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2004/0215554</com:DocumentNumber><com:EntityName>Kemper et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20041000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2004/0225545</com:DocumentNumber><com:EntityName>Turner et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20041100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2004/0230523</com:DocumentNumber><com:EntityName>Johnson</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20041100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2004/0236646</com:DocumentNumber><com:EntityName>Wu et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20041100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2005/0004839</com:DocumentNumber><com:EntityName>Bakker et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20050100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2005/0015332</com:DocumentNumber><com:EntityName>Chen</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20050100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2005/0021363</com:DocumentNumber><com:EntityName>Stimson et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20050100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:PatentCitationText>705/26</com:PatentCitationText><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2005/0075939</com:DocumentNumber><com:EntityName>Bao et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20050400</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2005/0082364</com:DocumentNumber><com:EntityName>Alvarez et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20050400</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2005/0108121</com:DocumentNumber><com:EntityName>Gravett et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20050500</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2005/0167481</com:DocumentNumber><com:EntityName>Hansen et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20050800</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2005/0173520</com:DocumentNumber><com:EntityName>Jaros et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20050800</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2005/0203837</com:DocumentNumber><com:EntityName>Leigh et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20050900</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2005/0205663</com:DocumentNumber><com:EntityName>Allgiene</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20050900</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2005/0228724</com:DocumentNumber><com:EntityName>Frangiosa</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20051000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:PatentCitationText>705/40</com:PatentCitationText><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2005/0283436</com:DocumentNumber><com:EntityName>Greer et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20051200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2006/0059085</com:DocumentNumber><com:EntityName>Tucker</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20060300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2006/0085334</com:DocumentNumber><com:EntityName>Murphy</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20060400</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2006/0149665</com:DocumentNumber><com:EntityName>Weksler</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20060700</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2006/0149670</com:DocumentNumber><com:EntityName>Nguyen et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20060700</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2006/0161499</com:DocumentNumber><com:EntityName>Rich et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20060700</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2006/0190322</com:DocumentNumber><com:EntityName>Oehlerking et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20060800</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:PatentCitationText>705/35</com:PatentCitationText><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2006/0206402</com:DocumentNumber><com:EntityName>Sullivan</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20060900</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2006/0212392</com:DocumentNumber><com:EntityName>Brown</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20060900</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2006/0212393</com:DocumentNumber><com:EntityName>Brown</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20060900</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2006/0224502</com:DocumentNumber><com:EntityName>McGowan</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20061000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2006/0249570</com:DocumentNumber><com:EntityName>Seifert et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20061100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2006/0259957</com:DocumentNumber><com:EntityName>Tam et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20061100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2006/0282356</com:DocumentNumber><com:EntityName>Andres et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20061200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2006/0282374</com:DocumentNumber><com:EntityName>Stone</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20061200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0000997</com:DocumentNumber><com:EntityName>Lambert et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20070100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0011089</com:DocumentNumber><com:EntityName>DeSchryver</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20070100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0038515</com:DocumentNumber><com:EntityName>Postrel</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20070200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0045401</com:DocumentNumber><com:EntityName>Sturm</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20070300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0061206</com:DocumentNumber><com:EntityName>LeFebvre</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20070300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0083462</com:DocumentNumber><com:EntityName>Cubillo et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20070400</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0087819</com:DocumentNumber><com:EntityName>Van Luchene et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20070400</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0100745</com:DocumentNumber><com:EntityName>Keiser</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20070500</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0106603</com:DocumentNumber><com:EntityName>Whyte et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20070500</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0136194</com:DocumentNumber><com:EntityName>Sloan</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20070600</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0152038</com:DocumentNumber><com:EntityName>Ciancio et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20070700</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0168265</com:DocumentNumber><com:EntityName>Rosenberger</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20070700</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0174189</com:DocumentNumber><com:EntityName>Bishop et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20070700</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0175984</com:DocumentNumber><com:EntityName>Khandaker et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20070800</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0198352</com:DocumentNumber><com:EntityName>Kannegiesser</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20070800</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0198403</com:DocumentNumber><com:EntityName>Aloni et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20070800</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0233596</com:DocumentNumber><com:EntityName>Ambrose</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20071000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0244778</com:DocumentNumber><com:EntityName>Bailard</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20071000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0250380</com:DocumentNumber><com:EntityName>Mankoff</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20071000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0260536</com:DocumentNumber><com:EntityName>Stone</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20071100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0262140</com:DocumentNumber><com:EntityName>Long, Sr.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20071100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0265957</com:DocumentNumber><com:EntityName>Advani et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20071100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0265960</com:DocumentNumber><com:EntityName>Advani et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20071100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0267479</com:DocumentNumber><com:EntityName>Nix et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20071100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0271178</com:DocumentNumber><com:EntityName>Davis et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20071100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2007/0282740</com:DocumentNumber><com:EntityName>Wendt</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20071200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2008/0005001</com:DocumentNumber><com:EntityName>Davis et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20080100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2008/0040261</com:DocumentNumber><com:EntityName>Nix et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20080200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2008/0040265</com:DocumentNumber><com:EntityName>Rackley, III et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20080200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2008/0052189</com:DocumentNumber><com:EntityName>Walker et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20080200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2008/0059363</com:DocumentNumber><com:EntityName>Hotz et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20080300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2008/0065532</com:DocumentNumber><com:EntityName>De La Motte</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20080300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2008/0091519</com:DocumentNumber><com:EntityName>Foss</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20080400</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2008/0103970</com:DocumentNumber><com:EntityName>Books et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20080500</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2008/0120129</com:DocumentNumber><com:EntityName>Seubert et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20080500</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2008/0140561</com:DocumentNumber><com:EntityName>Neel</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20080600</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2008/0140568</com:DocumentNumber><com:EntityName>Henry</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20080600</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2008/0228643</com:DocumentNumber><com:EntityName>Hall</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20080900</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2008/0281734</com:DocumentNumber><com:EntityName>Longe et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20081100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2009/0048963</com:DocumentNumber><com:EntityName>Bishop et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20090200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2009/0063342</com:DocumentNumber><com:EntityName>Beckers</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20090300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2009/0157220</com:DocumentNumber><com:EntityName>Walker et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20090600</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2009/0164362</com:DocumentNumber><com:EntityName>Moore</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20090600</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2009/0164363</com:DocumentNumber><com:EntityName>Ahlers</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20090600</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2009/0192934</com:DocumentNumber><com:EntityName>Chu et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20090700</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2009/0222367</com:DocumentNumber><com:EntityName>Jenkins et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20090900</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2009/0228307</com:DocumentNumber><com:EntityName>Sorbe</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20090900</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2009/0254431</com:DocumentNumber><com:EntityName>Crowe et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20091000</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2010/0030687</com:DocumentNumber><com:EntityName>Panthaki et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20100200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2010/0057554</com:DocumentNumber><com:EntityName>Lanford</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20100300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2010/0076875</com:DocumentNumber><com:EntityName>Ernst et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20100300</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2010/0106555</com:DocumentNumber><com:EntityName>Mneimneh et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20100400</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2010/0222132</com:DocumentNumber><com:EntityName>Sanford et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20100900</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2010/0280949</com:DocumentNumber><com:EntityName>Van Rensburg</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20101100</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2010/0306104</com:DocumentNumber><com:EntityName>Johnson</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20101200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation><com:CitedPatentDocumentIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:DocumentNumber>2010/0312684</com:DocumentNumber><com:EntityName>Kemper et al.</com:EntityName><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PatentDocumentDate>20101200</com:PatentDocumentDate></com:CitedPatentDocumentIdentification></com:PatentCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:PatentCitation/></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/607,780, filed Oct. 28, 2009, titled Shopping Center Gift Card Offer Fulfillment Machine, Program Product and Associated Methods.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/609,896, filed Oct. 30, 2009, titled Machine Methods, and Program Product for Electronic Order Entry.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/626,349, filed Nov. 25, 2009, titled Machine, Methods, and Program Product for Electronic Inventory Tracking.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>International Search Report for PCT/US09/56072 dated Oct. 20, 2009.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Bank Deals&#8212;Best Rates and Deals: EverBank's World Currency CDs&#8212;My Interview with EverBank's Executive Frank Trotter, http://bankdeals.blogspot.com, Jul. 29, 2007.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Foreign Exchange Market, http://en.wikipedia.org.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Avoid Gift Card Pitfalls, ConsumerReports.org.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>VIPGift Receives Investment From Summit Partners and Bridgescale Partners, Nov. 11, 2008, Chattanooga, TN and Palo Alto, CA.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/814,405, filed Jun. 11, 2010 titled Environmental-Friendly Fuel Credit Card System, Program Product, and Computer-Implemented Methods.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/877,490, filed Sep. 8, 2010 titled System, Program Product, and Method for Debit Card and Checking Account Autodraw.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/877,524, filed Sep. 8, 2010 titled System, Program Product, and Method for Debit Card and Checking Account Autodraw.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action in co-pending U.S. Appl. No. 12/609,896 dated Apr. 5, 2011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action in co-pending U.S. Appl. No. 12/417,162 dated Apr. 13, 2011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Orszag, Peter, &#8220;Unemployment Insurance as an Economic Stimulus&#8221;, Center for Budget and Policy Priorities, Nov. 15, 2011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Powell, Robert L., &#8220;Statewide Electronic Commerce Program Status Report&#8221;, State of North Carolina Office of the State Controller, Mar. 7, 2007.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Parrott, James, &#8220;Jittery Wall Street, Calm City?&#8221;, Gotham Gazette, Apr. 16, 2007.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Zandi, Mark, &#8220;Washington Throws the Economy a Rope&#8221;, Moody's Economy.com, Jan. 22, 2008.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Blair, Christine E., et al., &#8220;Challenges to the Dual Banking System: The Funding of Bank Supervision&#8221;, FDIC Bank Review, Mar. 31, 2006.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action for co-pending U.S. Appl. No. 12/367,187 dated Jun. 27, 2011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>&#8220;Developing Asia and the World&#8221;, Asian Development Bank 2002.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Notice of Allowance in co-pending U.S. Appl. No. 12/554,659 dated Aug. 2, 2011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action in co-pending U.S. Appl. No. 12/338,712 dated Jul. 28, 2011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action in co-pending U.S. Appl. No. 12/338,440 dated Aug. 1, 2011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Financial Advice Investment Money Oct. 1, 2009 at 5:50pm, HSBC Offshore Internet Banking.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Financial Advice Investment Money Oct. 1, 2009 at 7:25am, HSBC Offshore Internet Banking.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office action from co-pending U.S. Appl. No. 12/338,497 dated Aug. 18, 2011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Notice of Allowance of co-pending U.S. Appl. No. 12/417,199 dated Aug. 18, 2011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Notice of Allowance of co-pending U.S. Appl. No. 12/417,211 dated Aug. 22, 2011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Wolfe, Daniel, &#8220;An E-Variation on Payday Loan Theme&#8221;, American Banker, Jul. 28, 2005.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>&#8220;Letter of Credit Explained: What is Letter of Credit?&#8221;, Dec. 26, 2005, pp. 1-2.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action from co-pending U.S. Appl. No. 12/338,540 dated Sep. 1, 2011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Notice of Allowance of co-pending U.S. Appl. No. 12/338,365 dated Sep. 1, 2011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action dated Jul. 9, 2010 for U.S. Appl. No. 12/338,365.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action dated Jul. 9, 2010 for U.S. Appl. No, 12/338,645.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 13/036,076, filed Feb. 28, 2011, titled Machine, Program Product, and Computer Implemented Method to Construct a Person-To-Person Loan.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action dated Feb. 18, 2011, in co-pending U.S. Apl. No. 12/338,402.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/554,659, filed Sep. 4, 2009, titled &#8220;System, Method, and Program Product for Foreign Currency Travel Account&#8221;.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/554,432, filed Sep. 4, 2009, titled &#8220;System, Program Product and Methods for Retail Activation and Reload Associated with Partial Authorization Transactions&#8221;.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Cross, Sam Y., All About . . . the Foreign Exhange Market in the United States, 1998, Federal Reserve Bank of New York.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/562,331, filed Sep. 18, 2009, titled Computerized Extension of Credit to Existing Demand Deposit Accounts, Prepaid Cards and Lines of Credit Based on Expected Tax Refund Proceeds, Associated Systems and Computer Program Products.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action dated Mar. 4, 2011, in co-pending U.S. Appl. No. 12/338,684.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action dated Mar. 17, 2011, in co-pending U.S. Appl. No. 12/417,199.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action dated Mar. 17, 2011, in co-pending U.S. Appl. No. 12/465,803.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action dated Mar. 22, 2011, in co-pending U.S. Appl. No. 12/338,584.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action dated Mar. 29, 2011, in co-pending U.S. Appl. No. 12/417,211.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action dated Mar. 29, 2011, in co-pending U.S. Appl. No. 12/407,320.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>International Search Report for co-pending PCT Application No. PCT/US2008/087689 dated Jun. 17, 2009.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Final Office Action dated Jan. 26, 2011, in co-pending U.S. Appl. No. 12/338,365.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Final Office Action dated Jan. 26, 2011, in co-pending U.S. Appl. No. 12/338,645.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Final Office Action dated Jan. 19, 2011, in co-pending U.S. Appl. No. 12/417,162.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action dated Feb. 1, 2011, in co-pending U.S. Appl. No. 12/389,749.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/700,681, filed Feb. 4, 2010.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/889,281, filed Sep. 23, 2010.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/892,847, filed Sep. 28, 2010.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/731,852, filed Mar. 25, 2010.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Microtrax Ltd., PC Electronic Payment Systems Reference Manuel, 1995 (381 pages).</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>John P. Caskey and Gordon H. Selton, Jr., Is the Debit Card Revolution Finally Here?, Federal Reserve Bank of Kansas City, Economic Review, Fourth Quarter 1994, pp. 70-95, vol. 79 #4 (17 pages).</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Laura Castaneda, Business Promote Services to Customers Day In and Out, The Dallas Morning News, Nov. 26, 1994, 3 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Margaret Mannix, Checkout Tech, U.S. News &amp; World Report, Feb. 27, 1995, 6 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Credit Terminals to be Used at Canadian Liquor Outlets, Card News, Jan. 23, 1995, 1 page.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Debit Card Popularity on the Rise, Chain Store Age Executive, Jan. 1994, 1 page.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Debit Goes to Dinner, Credit Card Management , New York, Oct. 1994, 2 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Alan Peppard, Down and Dirty in Deep Ellum, The Dallas Morning News, Dec. 3, 1994, 2 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Everest Reference Manual, VeriFone Part No. 25339, Revision A, Manual Revision 1.0, Jul. 1995, 66 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Express Cards and Trains, Chain Store Age Executive Edition, Jan. 1995, 1 page.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Suzanne Brown, Goodnight Amy, Meg, Beth and Jo, Rocky Mountain News, Dec. 8, 1994, 1 page.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Robert J. Klein, Here Comes the Debit Card, D&amp;B Reports, Jul./Aug. 1990, 2 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Hypercom S7C Advertisement, Chain Store Age, Sep. 1995, 4 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Hypercom S7SC Advertisement, Chain Store Age, Feb. 1996, 2 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>IBM 4680-4690 Advanced Payment System for Chain Drug Sales Application User's Guide, Nov. 1996, 256 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>IBM 4680-4690 Advanced Payment System for Chain Drug Sales Application User's Guide, Jul. 1996, 248 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>IBM 4680-4690 Advanced Payment System for Supermarket Application User's Guide, Sep. 1996, 222 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Fox, Linda A., Keep an Eye on Your Credit Card, The Toronto Sun, Aug. 9, 1996, 1 page.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Pyatt, Rudolph A., Jr., Mobil Stations to Permit Use of Bank Cards, The Washington Post.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>NCR 4430-5000 MSR/PIN User's Guide, 1994, 265 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Nieman Marcus: High-Tech for the Holidays, Adweek, Dec. 5, 1994, 1 page.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Nieman Marcus Offers Electronic Gift Certificate, Card Fax, Jan. 23, 1995, 1 page.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Nieman Marcus to Launch NM Express Automated Gift Card, PR Newswire, Nov. 22, 1994, 1 page.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>NM Express Card Advertisement, The New Yorker, Dec. 12, 1994, 3 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Service Mark Registration No. 1,981,044 for &#8220;NM Express Card&#8221;, registered Jun. 18, 1996, 1 page.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>OMNI 480/490 Programmer's Guide, VeriFone Part No. 12924&#8212;Revision A, Manual Revision 1.0, Oct. 1993, 228 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>One Company's Diversification Shakes Up Peripherals Market, Chain Store Age, Jun. 1996, 3 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>O'Keefe, Michael, Portable POS Debit Terminal Mean Greater Convenience, Bank Systems &amp; Technology, Nov. 1994, 2 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>POS Terminal Can Handle Direct Debits, ABA Banking Journal, Sep. 1984, 2 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Rascal Corp. Advertisement, POS Terminal Eliminates Credit Card Vouchers, ABA Banking Journal, Nov. 1985, 2 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Szabo, Joan C., The Changing World of Financial Services, Nation's Business, Oct. 1994, 7 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>VeriFone Everest Advertisement, Stores, May 1995, 2 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>VeriFone Folio (TM) Brings Credit and Debit Card Payment to the Restaurant Table, PR Newswire, May 16, 1994, 3 pagse.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>David B. Barnes, VeriFone Introduces Everest (TM) Customer Activated Payment System to Multi-Lane Retail Market, PR Newswire, Feb. 20, 1995, 2 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>VeriFone Introduces Pinpad (TM) 1000 to Point-of-Sale Debit Market, M2 Presswire, Apr. 21, 1995, 1 page.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>VeriFone TCL Terminal Control Language Programmer's Manual, VeriFone Part No. 00368-01, Revision G, Manual Revision 8.0, Aug. 1992, 362 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>VeriFone Tranz 330 Reference Manual, VeriFone Part No. 00483-Revision D, Manual Revision 3.01, Apr. 1990, 144 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>MicroTrax Ltd. Omni 490M (and 490ML) Operation Manual for Integrated and Non-Integrated Configurations, 1994, 60 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>MicroTrax Electronic Payment Systems: The MicroTax Pinstripe Lane Equipment Users Guide, MicroTrax Ltd., Newport Beach, CA 1991, 54 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>IBM 4680-4690 Supermarket Application&#8212;Electronic Funds Transfer Feature Enhancement: User's Guide, IBM Corp., Research Triangle Park, NC, Sep. 1995, 318 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>IBM 4680 General Sales Application Electronic Funds Transfer User's Guide, IBM Corp., Research Triangle Park, NC, Dec. 1990, 260 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>IBM 4680 General Sales Application Electronic Funds Transfer User's Guide, IBM Corp., Research Triangle Park, NC, Mar. 1991, 263 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>IBM 4680 General Sales Application: Guide to Operations, Research Triangle Park, NC, Jun. 1991, 429 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Jane Boon Pearlstine, Lenders, Borrowers Hook Up Over the Web: Prosper.com and Other Sites Provide Forum for Individual Bidders Willing to Offer Small Loans, Wall Street Journal, May 20, 2006.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>United Nations Conference on Trade and Development, E-Finance and Small and Medium-Size Enterprises (SMEs) in Developing and Transition Economies, UNCTAD Expert Meeting, Oct. 17, 2001.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Tim Jones, Paradigms lost, RSA Journal, Oct. 2006, pp. 28-31.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Diego Rumiany, Internet Bidding for Microcredit: making it work in the developed world, conceiving it for the developing world, Mar. 2007.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Stefan Heng, Thomas Meyer, and Antje Stobbe, Implications of Web 2.0 for financial institutions: Be a driver, not a passenger, Munich Personal RePEc Archive, Jul. 31, 2007.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Matt Flannery, Kiva and the Birth of Person to Person Microfinance, Innovations, pp. 31-56, Winter &amp; Spring 2007.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Michael K Hulme and Collette Wright, Internet Based Social Lending: Past, Present and Future, Social Futures Observatory, Oct. 2006.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Richard W Coleman, Is the Future of the Microfinance Movement to be Found on the Internet?, International Trade and Finance Association Working Papers 2007.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Amanda Scott and Patrick Towell, The web we weave, Financial World, pp. 12-15, Nov. 2006.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Prosper, Access and Transparency through Person-to-Person Lending, FDIC Advisory Committee on Economic Inclusion, Mar. 28, 2007.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/338,365, filed Dec. 18, 2008, titled &#8220;Transfer Account Systems, Computer Program Products, and Associated Computer-Implemented Methods&#8221;.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/338,402, filed Dec. 18, 2008, titled &#8220;Transfer Account Systems, Computer Program Products, and Associated Computer-Implemented Methods&#8221;.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/338,440, filed Dec. 18, 2008, titled &#8220;Transfer Account Systems, Computer Program Products, and Associated Computer-Implemented Methods&#8221;.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/338,497, filed Dec. 18, 2008, titled &#8220;Private Label Promotion Card System, Program Product, and Associated Computer-Implemented Methods&#8221;.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/338,540, filed Dec. 18, 2008, titled &#8220;Private Label Promotion Card System, Program Product, and Associated Computer-implemented Methods&#8221;.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/338,584, filed Dec. 18, 2008, titled &#8220;Transfer Account Systems, Computer Program Products, and Methods to Prioritize Payments From Preselected Bank Accounts&#8221;.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/338,645, filed Dec. 18, 2008, titled &#8220;Transfer Account Systems, Computer Program Products, and Methods to Prioritize Payments from Preselected Bank Accounts&#8221;.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/338,684, filed Dec. 18, 2008, titled &#8220;Transfer Account Systems, Computer Program Products, and Associated Methods&#8221;.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/338,712, filed Dec. 18, 2008, titled &#8220;Computer-Implemented Methods, Program Product, and System to Enhance Banking Terms Over Time&#8221;.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/397,113, filed Mar. 3, 2009, titled &#8220;Person-to-Person Lending Program Product, System, and Associated Methods&#8221;.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/389,749, filed Feb. 20, 2009, titled &#8220;Methods to Advance Loan Proceeds on Prepaid Cards, Associated Systems and Computer Program Products&#8221;.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/417,199, filed Apr. 2, 2009, titled &#8220;System, Program Product, and Associated Methods to Autodraw for Micro-Credit Attached to a Prepaid Card&#8221;.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/417,211, filed Apr. 2, 2009, titled &#8220;System, Program Product, and Associated Methods to Autodraw for Micro-Credit Attached to a Prepaid Card&#8221;.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/367,187, filed Feb. 6, 2009, titled &#8220;Government Targeted-Spending Stimulus Card System, Program Product and Computer-Implemented Methods&#8221;.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/407,320, filed Mar. 19, 2009, titled &#8220;Computerized Extension of Credit to Existing Demand Deposit Accounts, Prepaid Cards and Lines of Credit Based on Expected Tax Refund Proceeds, Associated Systems and Computer Program Products&#8221;.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/417,162, filed Apr. 2, 2009, titled &#8220;System, Program Product, and Method for Debit Card and Checking Account Autodraw&#8221;.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/465,277 filed May 13, 2009 titled &#8220;System, Program Product, and Computer-Implemented Method for Loading a Loan on an Existing Pre-Paid Card&#8221;.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/465,306 filed May 13, 2009 titled &#8220;System, Program Product, and Computer-Implemented Method for Loading a Loan on an Existing Pre-Paid Card&#8221;.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/465,803 filed May 14, 2009 titled &#8220;System, Program Product, and Method for Loading a Loan on a Pre-Paid Card&#8221;.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>International Search Report for PCT/US2009/034692 dated Apr. 14, 2009.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>International Search Report for PCT/US2009/039495 dated May 18, 2009.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action dated Sep. 28, 2010 for co-pending U.S. Appl. No. 12/338,402 filed Dec. 18, 2008.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action dated Sep. 3, 2010 for co-pending U.S. Appl. No. 12/417,162 filed Apr. 2, 2009.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>International Search Report for PCT/US2009/043988 dated Jul. 14, 2009.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>International Search Report for PCT/US2009/039492 dated May 14, 2009.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Co-pending U.S. Appl. No. 12/562,331, filed Sep. 18, 2009.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Krino, Gary, et al., A Birthday Card That Pays Off, The Orange County Register, Jul. 19, 1996, 2 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Cohen, Bruce, Alternative to Cash Gains Ground, The Financial Post, Apr. 22, 1994, 2 pages.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Bank of Boulder POS Debit Solution at the Table Now in Beta: First Bank to Certify IVI Spirit C2000 on MAPP (R), Business Wire, Aug. 3, 1994, 1 page.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>International Search Report dated May 27, 2009 for PCT/US2009/039504 filed Apr. 3, 2009.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>International Search Report dated Jun. 8, 2009 for PCT/US2009/039512 filed Apr. 3, 2009.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>International Search Report dated Jun. 30, 2009 for PCT/US2009/043978 filed May 14, 2009.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Congressional Budget Office, &#8220;Emerging Electronic Methods for Making Payments&#8221; (Jun. 1996), CBO.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Coady et al., &#8220;Targeted anti-poverty intervention: A selected annotated bibliography&#8221; (Apr. 2002), World Bank.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Notice of Allowance from co-pending U.S. Appl. No. 12/609,896 dated Jan. 3, 2012.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Notice of Allowance from co-pending U.S. Appl. No. 13/233,268 dated Dec. 13, 2011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action from co-pending U.S. Appl. No. 12/367,187 dated Jan. 6. 2012.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action from co-pending U.S. Appl. No. 12/731,852 dated Dec. 22, 2011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Business Dateline, Q Comm Expands Calling Card Products with Best Telecom Point-of-Sale Activated Cards; All Q Comm VeriFone Merchants Can Now Deliver Durable Calling Cards (Dec. 6, 2010), Business Wire (Dec. 8, 2011).</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Notice of Allowance from co-pending U.S. Appl. No. 12/465,803 dated Dec. 20, 2011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>MasterCard Electronic prepaid (Oct. 2003), The Nilson Report, (798), (Dec. 9, 2011), The Banking Source (Document ID 474833171).</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action from co-pending U.S. Appl. No. 12/626,349, dated Nov. 22, 2011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Final Office Action in co-pending U.S. Appl. No. 12/338,584 dated Sep. 15, 2011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Final Office Action in co-pending U.S. Appl. No. 12/338,684 dated Sep. 23, 2011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Lazarus, David, &#8220;120% rate for Wells' Advances&#8221;, Oct. 16, 2004, San Francisco Chronicle.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action in co-pending U.S. Appl. No. 12/397,113 dated Sep. 30, 3011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Notice of Allowance in co-pending U.S. Appl. No. 12/338,645 dated Oct. 3, 2011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Zubko, N., &#8220;An Automotic Connection Electronic Transaction Tools Help Manufacturers Connect With Suppliers to Streamline Sourcing Efforts&#8221;, Industry Week, Jul. 2008, pp. 26-27, vol. 257, No. 7.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Notice of Allowance from co-pending U.S. Appl. No. 12/609,896 dated Oct. 27, 2011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action from co-pending U.S. Appl. No. 12/465,277 dated Oct. 20, 2011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Office Action from co-pending U.S. Appl. No. 12/562,331 dated Oct. 20, 2011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation><pat:ReferenceCitation><com:NPLCitation><com:NPLCitationText>Notice of Allowance from co-pending U.S. Appl. No. 12/407,320 dated Oct. 18, 2011.</com:NPLCitationText></com:NPLCitation></pat:ReferenceCitation></pat:ReferenceCitationBag><pat:SearchField><pat:SearchFieldText>705/38</pat:SearchFieldText><pat:SearchFieldText>705/39</pat:SearchFieldText><pat:SearchFieldText>705/35</pat:SearchFieldText></pat:SearchField><pat:RelatedDocumentBag><pat:RelatedPublication><pat:PatentDocumentIdentification><pat:PatentPublicationIdentification><com:IPOfficeCode>US</com:IPOfficeCode><pat:PublicationNumber>20090254431</pat:PublicationNumber><com:PatentDocumentKindCode>A1</com:PatentDocumentKindCode><com:PublicationDate>20091008</com:PublicationDate></pat:PatentPublicationIdentification></pat:PatentDocumentIdentification></pat:RelatedPublication><pat:ProvisionalApplication><pat:PatentDocumentIdentification><pat:ApplicationIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:ApplicationNumber><com:ApplicationNumberText>61042624</com:ApplicationNumberText></com:ApplicationNumber><pat:FilingDate>20080404</pat:FilingDate></pat:ApplicationIdentification></pat:PatentDocumentIdentification></pat:ProvisionalApplication><pat:ProvisionalApplication><pat:PatentDocumentIdentification><pat:ApplicationIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:ApplicationNumber><com:ApplicationNumberText>61042612</com:ApplicationNumberText></com:ApplicationNumber><pat:FilingDate>20080404</pat:FilingDate></pat:ApplicationIdentification></pat:PatentDocumentIdentification></pat:ProvisionalApplication><pat:ProvisionalApplication><pat:PatentDocumentIdentification><pat:ApplicationIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:ApplicationNumber><com:ApplicationNumberText>61052454</com:ApplicationNumberText></com:ApplicationNumber><pat:FilingDate>20080512</pat:FilingDate></pat:ApplicationIdentification></pat:PatentDocumentIdentification></pat:ProvisionalApplication><pat:ProvisionalApplication><pat:PatentDocumentIdentification><pat:ApplicationIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:ApplicationNumber><com:ApplicationNumberText>61060559</com:ApplicationNumberText></com:ApplicationNumber><pat:FilingDate>20080611</pat:FilingDate></pat:ApplicationIdentification></pat:PatentDocumentIdentification></pat:ProvisionalApplication><pat:ProvisionalApplication><pat:PatentDocumentIdentification><pat:ApplicationIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:ApplicationNumber><com:ApplicationNumberText>61082863</com:ApplicationNumberText></com:ApplicationNumber><pat:FilingDate>20080723</pat:FilingDate></pat:ApplicationIdentification></pat:PatentDocumentIdentification></pat:ProvisionalApplication><pat:ProvisionalApplication><pat:PatentDocumentIdentification><pat:ApplicationIdentification><com:IPOfficeCode>US</com:IPOfficeCode><com:ApplicationNumber><com:ApplicationNumberText>61053056</com:ApplicationNumberText></com:ApplicationNumber><pat:FilingDate>20080514</pat:FilingDate></pat:ApplicationIdentification></pat:PatentDocumentIdentification></pat:ProvisionalApplication></pat:RelatedDocumentBag><pat:PartyBag><pat:RegisteredPractitionerBag><pat:RegisteredPractitioner pat:dataFormat="original" com:languageCode="en"><com:Contact><com:Name><com:OrganizationName><com:OrganizationStandardName>Bracewell &amp; Giuliani LLP</com:OrganizationStandardName></com:OrganizationName></com:Name><com:PostalAddressBag><com:PostalAddress><com:PostalStructuredAddress><com:AddressLineText com:sequenceNumber="1">unknown</com:AddressLineText><com:GeographicRegionName/></com:PostalStructuredAddress></com:PostalAddress></com:PostalAddressBag></com:Contact></pat:RegisteredPractitioner></pat:RegisteredPractitionerBag><pat:InventorBag><pat:Inventor com:languageCode="en" pat:dataFormat="original"><com:Contact><com:Name><com:PersonName><com:PersonFullName>Andrew B. Crowe</com:PersonFullName></com:PersonName></com:Name><com:PostalAddressBag><com:PostalAddress><com:PostalStructuredAddress><com:AddressLineText com:sequenceNumber="1">US NE Omaha</com:AddressLineText><com:CityName>Omaha</com:CityName><com:GeographicRegionName>NE</com:GeographicRegionName><com:CountryCode>US</com:CountryCode></com:PostalStructuredAddress></com:PostalAddress></com:PostalAddressBag></com:Contact><com:NationalityCode>US</com:NationalityCode></pat:Inventor><pat:Inventor com:languageCode="en" pat:dataFormat="original"><com:Contact><com:Name><com:PersonName><com:PersonFullName>Scott H. Galit</com:PersonFullName></com:PersonName></com:Name><com:PostalAddressBag><com:PostalAddress><com:PostalStructuredAddress><com:AddressLineText com:sequenceNumber="1">US NY New York</com:AddressLineText><com:CityName>New York</com:CityName><com:GeographicRegionName>NY</com:GeographicRegionName><com:CountryCode>US</com:CountryCode></com:PostalStructuredAddress></com:PostalAddress></com:PostalAddressBag></com:Contact><com:NationalityCode>US</com:NationalityCode></pat:Inventor><pat:Inventor com:languageCode="en" pat:dataFormat="original"><com:Contact><com:Name><com:PersonName><com:PersonFullName>Trent Sorbe</com:PersonFullName></com:PersonName></com:Name><com:PostalAddressBag><com:PostalAddress><com:PostalStructuredAddress><com:AddressLineText com:sequenceNumber="1">US SD Brookings</com:AddressLineText><com:CityName>Brookings</com:CityName><com:GeographicRegionName>SD</com:GeographicRegionName><com:CountryCode>US</com:CountryCode></com:PostalStructuredAddress></com:PostalAddress></com:PostalAddressBag></com:Contact><com:NationalityCode>US</com:NationalityCode></pat:Inventor><pat:Inventor com:sequenceNumber="1" pat:dataFormat="docdb"><com:Contact><com:Name><com:EntityName>CROWE ANDREW B</com:EntityName></com:Name></com:Contact><com:NationalityCode>US</com:NationalityCode></pat:Inventor><pat:Inventor com:sequenceNumber="2" pat:dataFormat="docdb"><com:Contact><com:Name><com:EntityName>GALIT SCOTT H</com:EntityName></com:Name></com:Contact><com:NationalityCode>US</com:NationalityCode></pat:Inventor><pat:Inventor com:sequenceNumber="3" pat:dataFormat="docdb"><com:Contact><com:Name><com:EntityName>SORBE TRENT</com:EntityName></com:Name></com:Contact><com:NationalityCode>US</com:NationalityCode></pat:Inventor><pat:Inventor com:sequenceNumber="1" pat:dataFormat="docdba"><com:Contact><com:Name><com:EntityName>CROWE ANDREW B.</com:EntityName></com:Name></com:Contact></pat:Inventor><pat:Inventor com:sequenceNumber="2" pat:dataFormat="docdba"><com:Contact><com:Name><com:EntityName>GALIT SCOTT H.</com:EntityName></com:Name></com:Contact></pat:Inventor><pat:Inventor com:sequenceNumber="3" pat:dataFormat="docdba"><com:Contact><com:Name><com:EntityName>SORBE TRENT</com:EntityName></com:Name></com:Contact></pat:Inventor></pat:InventorBag><pat:ApplicantBag><pat:Applicant com:languageCode="en" pat:dataFormat="original"><com:Contact><com:Name><com:PersonName><com:PersonFullName>Andrew B. Crowe</com:PersonFullName></com:PersonName></com:Name><com:PostalAddressBag><com:PostalAddress><com:PostalStructuredAddress><com:AddressLineText com:sequenceNumber="1">US NE Omaha</com:AddressLineText><com:CityName>Omaha</com:CityName><com:GeographicRegionName>NE</com:GeographicRegionName><com:CountryCode>US</com:CountryCode></com:PostalStructuredAddress></com:PostalAddress></com:PostalAddressBag></com:Contact><com:NationalityCode>US</com:NationalityCode></pat:Applicant><pat:Applicant com:languageCode="en" pat:dataFormat="original"><com:Contact><com:Name><com:PersonName><com:PersonFullName>Scott H. Galit</com:PersonFullName></com:PersonName></com:Name><com:PostalAddressBag><com:PostalAddress><com:PostalStructuredAddress><com:AddressLineText com:sequenceNumber="1">US NY New York</com:AddressLineText><com:CityName>New York</com:CityName><com:GeographicRegionName>NY</com:GeographicRegionName><com:CountryCode>US</com:CountryCode></com:PostalStructuredAddress></com:PostalAddress></com:PostalAddressBag></com:Contact><com:NationalityCode>US</com:NationalityCode></pat:Applicant><pat:Applicant com:languageCode="en" pat:dataFormat="original"><com:Contact><com:Name><com:PersonName><com:PersonFullName>Trent Sorbe</com:PersonFullName></com:PersonName></com:Name><com:PostalAddressBag><com:PostalAddress><com:PostalStructuredAddress><com:AddressLineText com:sequenceNumber="1">US SD Brookings</com:AddressLineText><com:CityName>Brookings</com:CityName><com:GeographicRegionName>SD</com:GeographicRegionName><com:CountryCode>US</com:CountryCode></com:PostalStructuredAddress></com:PostalAddress></com:PostalAddressBag></com:Contact><com:NationalityCode>US</com:NationalityCode></pat:Applicant><pat:Applicant com:sequenceNumber="1" pat:dataFormat="docdb"><com:Contact><com:Name><com:EntityName>CROWE ANDREW B</com:EntityName></com:Name></com:Contact><com:NationalityCode>US</com:NationalityCode></pat:Applicant><pat:Applicant com:sequenceNumber="2" pat:dataFormat="docdb"><com:Contact><com:Name><com:EntityName>GALIT SCOTT H</com:EntityName></com:Name></com:Contact><com:NationalityCode>US</com:NationalityCode></pat:Applicant><pat:Applicant com:sequenceNumber="3" pat:dataFormat="docdb"><com:Contact><com:Name><com:EntityName>SORBE TRENT</com:EntityName></com:Name></com:Contact><com:NationalityCode>US</com:NationalityCode></pat:Applicant><pat:Applicant com:sequenceNumber="4" pat:dataFormat="docdb"><com:Contact><com:Name><com:EntityName>METABANK</com:EntityName></com:Name></com:Contact><com:NationalityCode>US</com:NationalityCode></pat:Applicant><pat:Applicant com:sequenceNumber="1" pat:dataFormat="docdba"><com:Contact><com:Name><com:EntityName>CROWE ANDREW B.</com:EntityName></com:Name></com:Contact></pat:Applicant><pat:Applicant com:sequenceNumber="2" pat:dataFormat="docdba"><com:Contact><com:Name><com:EntityName>GALIT SCOTT H.</com:EntityName></com:Name></com:Contact></pat:Applicant><pat:Applicant com:sequenceNumber="3" pat:dataFormat="docdba"><com:Contact><com:Name><com:EntityName>SORBE TRENT</com:EntityName></com:Name></com:Contact></pat:Applicant><pat:Applicant com:sequenceNumber="4" pat:dataFormat="docdba"><com:Contact><com:Name><com:EntityName>METABANK</com:EntityName></com:Name></com:Contact></pat:Applicant></pat:ApplicantBag><pat:OwnerBag><pat:Owner com:languageCode="en" pat:dataFormat="original"><com:Contact><com:Name><com:OrganizationName><com:OrganizationStandardName>Metabank</com:OrganizationStandardName></com:OrganizationName></com:Name><com:PostalAddressBag><com:PostalAddress><com:PostalStructuredAddress><com:AddressLineText com:sequenceNumber="1">US SD Sioux Falls</com:AddressLineText><com:CityName>Sioux Falls</com:CityName><com:GeographicRegionName>SD</com:GeographicRegionName><com:CountryCode>US</com:CountryCode></com:PostalStructuredAddress></com:PostalAddress></com:PostalAddressBag></com:Contact></pat:Owner><pat:Owner com:sequenceNumber="1" pat:dataFormat="docdb"><com:Contact><com:Name><com:EntityName>CROWE ANDREW B</com:EntityName></com:Name><com:PostalAddressBag><com:PostalAddress><com:PostalStructuredAddress><com:CountryCode>US</com:CountryCode></com:PostalStructuredAddress></com:PostalAddress></com:PostalAddressBag></com:Contact></pat:Owner><pat:Owner com:sequenceNumber="2" pat:dataFormat="docdb"><com:Contact><com:Name><com:EntityName>GALIT SCOTT H</com:EntityName></com:Name><com:PostalAddressBag><com:PostalAddress><com:PostalStructuredAddress><com:CountryCode>US</com:CountryCode></com:PostalStructuredAddress></com:PostalAddress></com:PostalAddressBag></com:Contact></pat:Owner><pat:Owner com:sequenceNumber="3" pat:dataFormat="docdb"><com:Contact><com:Name><com:EntityName>SORBE TRENT</com:EntityName></com:Name><com:PostalAddressBag><com:PostalAddress><com:PostalStructuredAddress><com:CountryCode>US</com:CountryCode></com:PostalStructuredAddress></com:PostalAddress></com:PostalAddressBag></com:Contact></pat:Owner><pat:Owner com:sequenceNumber="4" pat:dataFormat="docdb"><com:Contact><com:Name><com:EntityName>METABANK</com:EntityName></com:Name><com:PostalAddressBag><com:PostalAddress><com:PostalStructuredAddress><com:CountryCode>US</com:CountryCode></com:PostalStructuredAddress></com:PostalAddress></com:PostalAddressBag></com:Contact></pat:Owner><pat:Owner com:sequenceNumber="1" pat:dataFormat="docdba"><com:Contact><com:Name><com:EntityName>CROWE ANDREW B.</com:EntityName></com:Name></com:Contact></pat:Owner><pat:Owner com:sequenceNumber="2" pat:dataFormat="docdba"><com:Contact><com:Name><com:EntityName>GALIT SCOTT H.</com:EntityName></com:Name></com:Contact></pat:Owner><pat:Owner com:sequenceNumber="3" pat:dataFormat="docdba"><com:Contact><com:Name><com:EntityName>SORBE TRENT</com:EntityName></com:Name></com:Contact></pat:Owner><pat:Owner com:sequenceNumber="4" pat:dataFormat="docdba"><com:Contact><com:Name><com:EntityName>METABANK</com:EntityName></com:Name></com:Contact></pat:Owner></pat:OwnerBag></pat:PartyBag></pat:BibliographicData><pat:Description com:id="description" com:languageCode="en" pat:dataFormat="original" pat:source="NATIONAL"><com:Heading com:headingLevelCode="H1">RELATED APPLICATIONS</com:Heading><com:P com:pNumber="0001">This application claims priority to and the benefit of: U.S. Provisional Patent Application Ser. No. 61/042,624, by Crowe et al., titled &#8220;System, Program Product, and Method to Authorize Draw for Retailer Optimization&#8221; filed on Apr. 4, 2008; and U.S. Provisional Patent Application Ser. No. 61/042,612, by Ahlers et al., titled &#8220;System, Program Product, and Associated Methods to Authorize Draw for Micro-Credit Attached to a Prepaid Card&#8221; filed on Apr. 4, 2008, all of which are each incorporated herein by reference in their entireties. This application also relates to: U.S. Provisional Patent Application Ser. No. 61/016,213, by Sorbe et al., titled &#8220;Transfer Account Systems, Computer Program Products, and Associated Methods&#8221; filed on Dec. 21, 2007; U.S. Provisional Patent Application Ser. No. 61/052,454, by Sorbe et al., titled &#8220;Transfer Account Systems, Computer Program Products, and Methods to Prioritize Payments from Preselected Bank Account&#8221; filed May 12, 2008; U.S. Provisional Patent Application Ser. No. 61/029,975, by Sorbe et al., titled &#8220;Methods To Advance Loan Proceeds On Prepaid Cards, Associated Systems and Computer Program Products&#8221; filed on Feb. 20, 2008; U.S. Provisional Patent Application Ser. No. 61/032,750, by Ahlers et al., titled &#8220;Methods, Program Product, and System for Micro-Loan Management&#8221; filed on Feb. 29, 2008; U.S. Provisional Patent Application Ser. No. 61/060,559, by Galit et al., titled &#8220;Methods, Program Product, and System to Enhance Banking Terms Over Time&#8221; filed on Jun. 11, 2008; U.S. Provisional Patent Application Ser. No. 61/082,863, by Ahlers et al., titled &#8220;System, Program Product, and Method For Debit Card and Checking Account Autodraw&#8221; filed on Jul. 23, 2008; U.S. Provisional Patent Application Ser. No. 61/053,056, by Galit et al., titled &#8220;System, Program Product, and Method For Loading a Loan On a Pre-Paid Card&#8221; filed on May 14, 2008, all of which are each incorporated herein by reference in their entireties. This application also relates to: U.S. patent application Ser. No. 12/338,365, by Sorbe et al., titled &#8220;Transfer Account Systems, Computer Program Products, and Associated Computer-Implemented Methods&#8221; filed on Dec. 18, 2008, and issued on Nov. 8, 2011 as U.S. Pat. No. 8,055,557; U.S. patent application Ser. No. 12/338,402, by Sorbe et al., titled &#8220;Transfer Account Systems, Computer Program Products, and Associated Computer-Implemented Methods&#8221; filed on Dec. 18, 2008; U.S. patent application Ser. No. 12/338,440, by Sorbe et al., titled &#8220;Transfer Account Systems, Computer Program Products, and Associated Computer-Implemented Methods&#8221; filed on Dec. 18, 2008; U.S. patent application Ser. No. 12/338,584, by Sorbe et al., titled &#8220;Transfer Account Systems, Computer Program Products, and Computer-Implemented Methods to Prioritize Payments from Preselected Bank Account&#8221; filed Dec. 18, 2008; U.S. patent application Ser. No. 12/338,645, by Sorbe et al., titled &#8220;Transfer Account Systems, Computer Program Products, and Computer-Implemented Methods to Prioritize Payments from Preselected Bank Account&#8221; filed Dec. 18, 2008; U.S. patent application Ser. No. 12/389,749, by Sorbe et al., titled &#8220;Methods to Advance Loan Proceeds on Prepaid Cards, Associated Systems and Computer Program Products&#8221; filed on Feb. 20, 2009; PCT/US09/34692, by Sorbe et al., titled &#8220;Methods to Advance Loan Proceeds on Prepaid Cards, Associated Systems and Computer Program Products&#8221; filed on Feb. 20, 2009; U.S. patent application Ser. No. 12/417,199, by Ahlers et al., titled &#8220;System, Program Product, and Associated Methods to Autodraw for Micro-Credit Attached to a Prepaid Card&#8221; filed on the same day herewith, and issued on Nov. 22, 2011 as U.S. Pat. No. 8,065,187; U.S. patent application Ser. No. 12/417,211, by Ahlers et al., titled &#8220;System, Program Product, and Associated Methods to Autodraw for Micro-Credit Attached to a Prepaid Card&#8221; filed on the same day herewith, and issued on Nov. 29, 2011 as U.S. Pat. No. 8,069,085; U.S. patent application Ser. No. 12/338,684, by Ahlers et al., titled &#8220;Computer-Implemented Methods, Program Product, and System for Micro-Loan Management&#8221; filed on Dec. 18, 2008; PCT/US08/87660 by Ahlers et al., titled &#8220;Computer-Implemented Methods, Program Product, and System for Micro-Loan Management&#8221; filed on Dec. 19, 2008; U.S. patent application Ser. No. 12/338,712, by Galit et al., titled &#8220;Computer-Implemented Methods, Program Product, and System to Enhance Banking Terms Over Time&#8221; filed on Dec. 18, 2008, and issued on Jan. 31, 2012 as U.S. Pat. No. 8,108,279; and PCT/US08/87689 by Galit et al., titled &#8220;Computer-Implemented Methods, Program Product, and System to Enhance Banking Terms Over Time&#8221; filed on Dec. 19, 2008; U.S. patent application Ser. No. 12/417,162, by Ahlers et al., titled &#8220;System, Program Product, and Method For Debit Card and Checking Account Autodraw&#8221; filed on the same day herewith, all of which are each incorporated herein by reference in their entireties.</com:P><com:Heading com:headingLevelCode="H1">BACKGROUND</com:Heading><com:P com:pNumber="0002">1. Field of Invention</com:P><com:P com:pNumber="0003">The present invention relates generally to the financial service and banking industries, and, more particularly, to systems, program products, and associated methods for providing a line of credit optimized for a retailer to a demand deposit account or a prepaid card.</com:P><com:P com:pNumber="0004">2. Background</com:P><com:P com:pNumber="0005">It is known that tens of millions of consumers in the United States have either limited or no access to traditional credit, either as a result of poor or limited credit history. It is known that tens of millions of consumers have demand deposit accounts (DDA) with overdraft protection, which allows them to borrow funds. It is further known that millions of prepaid cards are issued each year in the United States. It is also known that many of the customers of prepaid cards rely primarily on cash and a prepaid card account for their personal finances; these customers, for example, often do not have a traditional checking, savings, or other bank deposit account, and they usually do not write checks. It has been acknowledged by many that those without bank accounts and who often rely on prepaid cards, as well as those routinely using overdraft protection for short-term loans, may be underserved. These customers are typically not easily able to access credit through traditional banking channels, though they may have an ongoing relationship with a prepaid card issuer, for example.</com:P><com:P com:pNumber="0006">Even when credit is available to these customers, the costs associated with traditional lending products, including interest, fees, and penalties, are often expensive and can ultimately contribute to the financial situation that negatively impacts the consumer's access to credit. For example, a typical overdraft fee charged by a bank for &#8220;bounced&#8221; check is often larger than the overdraft amount itself.</com:P><com:Heading com:headingLevelCode="H1">SUMMARY OF INVENTION</com:Heading><com:P com:pNumber="0007">In view of the foregoing, Applicants have recognized the costs associated with traditional lending products and the structure of these costs, including interest, fees, and penalties, as sources of problems to consumers and also third parties who sell to these customers, e.g. retailers, or who might otherwise sell to these customers. For example, Applicants have recognized that customer funds spent on the costs associated with traditional lending products, including interest, fees, and penalties, are unavailable to be spent on other goods and services. Moreover, costs can be very expensive for a small amount of credit because of the structure. For example, a $35 overdraft fee is very expensive for a $4 overdraft. In addition, Applicants have recognized a need for enhanced lending options, bank products, and prepaid card products optimized for a retailer so that a retailer can compete for these customer funds. The present invention provides embodiments of systems, program products, and methods for providing a line of credit, optimized for a retailer and attached to a demand deposit account or a prepaid card.</com:P><com:P com:pNumber="0008">According to embodiments of the present invention, a bank or other financial or lending institution can offer a customer a line of credit optimized for a retailer. Funds from the line of credit are accessed in preselected loan increments, e.g., $20 increments, with a customer fee and a retailer fee associated with each increment. In one embodiment of the present invention, the customer fee is zero ($0), and the retailer pays all fees associated with access to the line of credit, say, e.g., $2.50 per preselected loan increment, so that the customer has free access to draws against the line of credit for customer transactions at the retailer. That is, the customer must repay the principle, but no interest or fees for a loan for a customer transaction at the retailer.</com:P><com:P com:pNumber="0009">In another embodiment of the present invention, the customer pays only a portion of the fees associated with a draw from the line of credit for a customer transaction at the retailer, for example, $1.00 instead of a typical $2.50. That is, the customer receives a discount on the fee for a draw on a line of credit for customer transactions at a retailer. The retailer can pay the difference so that the sum of the retailer fee and discounted customer fee equal the typical fee. For example, the retailer fee of $1.50 plus a discounted customer fee of $1.00 equal the $2.50 typical fee. Alternately, the sum of the retailer fee and discounted customer fee can be greater or less than the typical fee. For example, while the typical fee can be $2.50 per preselected loan increment of $20, the customer fee can be $1.00 and the retailer fee can be $1.00, for a sum of $2.00, which is less than the typical fee of $2.50. In another example, the discounted customer fee can be $2.00 and the retailer fee can be $1.00, for a sum of $3.00, which is greater than the typical fee of $2.50.</com:P><com:P com:pNumber="0010">In yet another embodiment of the present invention, the total available line of credit for the customer is decremented by the value of the customer fee as part of the customer transaction, but later is incremented by the value of the retailer fee to thereby define a rebate to the customer of the retailer fee.</com:P><com:P com:pNumber="0011">The benefits of the embodiments of the present invention to the customer include, for example, providing a short-term borrowing alternative that is more cost effective than other expensive financial service products, such as overdraft protection and payday loans, and more convenient to consumers. Embodiments of a line of credit, however, can still be monitored, controlled and managed by a bank or other regulated financial or lending institution, which can be a significant benefit from the perspective of the customer, regulators, and public opinion through consumer activists. To the customer, the benefits of the embodiments of the present invention also include free or discounted access to credit. To the retailer, the benefits of the embodiments of the present invention include reducing the effective price of customer purchases at the retailer and also the promotional value of these discounts. As understood by those skilled in the arts, the advertising value of free credit is substantial.</com:P><com:P com:pNumber="0012">Furthermore, the retailer benefits from additional sales and profits enabled by the embodiments of the present invention. For example, according to one embodiment of the present invention, a retailer sells an item to a customer for $10. The item costs the retailer $6 and has a $4 mark-up. If the customer transaction for this item requires the customer's borrowing of a preselected loan increment of $20 with a customer fee of $0 and retailer fee of $2.50, then the retailer earns an additional $10 in sales and $1.50 in profits through this transaction. The $1.50 profit is the $4 mark-up for the item minus the $2.50 fee paid by the retailer. The effect of the embodiments of the present invention is to lower the profit margin, in this example from 40% to 15% (or $4 per $10 of sales to $1.50 per $10 of sales), for customer transactions involving embodiments of the present invention, while preserving the profit margin for other customer transactions as understood by those skilled in the art. Therefore, the embodiments of the present invention target a discount to customer transactions where credit or financing is needed or useful, and advantageously do not provide a general discount or price reduction.</com:P><com:P com:pNumber="0013">According to other embodiments of the present invention, a predetermined portion of the total available line of credit can be, for example, reserved for customer transactions associated with the retailer. That is, the customer has an increase in available credit from the line of credit for transactions associated with the retailer. For example, according to an embodiment of the present invention, the total available line of credit is $300, with $200 reserved for customer transactions at the retailer and $100 generally available. According to embodiments of the present invention, the portion of credit reserved for customer transactions at the retailer can include different fee amounts received by the financial institution, e.g., the bank, as discussed above, and a different risk assessment from the portion of credit generally available. As understood by those skilled in the art, the different risk assessment for the portion of credit reserved for customer transactions at the retailer from the portion of credit generally available can be due to the source of payment of the fees, the nature of customer transactions at the retailer, or other causes. For the credit reserved for transactions at the retailer, the retailer, not the customer, is the source of payment for all or a portion of the fees. In addition, if the retailer is a casino, the risk assessment can be different than a general customer transaction; likewise, if the retailer is a store that features work shoes and uniforms for hospital employees, the risk assessment can be different than a general customer transaction as understood by those skilled in the art.</com:P><com:P com:pNumber="0014">Embodiments of the present invention can, for example, provide access to a line of credit and advance funds within an authorization stream for a proposed transaction. For example, a customer goes to a retailer and proposes to purchase $22 in goods using a prepaid card; the balance on the prepaid card is only $7. The customer, however, has an established line of credit for the prepaid card with a financial institution, e.g., a bank, for $150, with a total credit available of $130. Within the authorization stream for the proposed transaction, embodiments of the present invention can determine to advance funds through the line of credit to the customer account for the customer transaction, allowing the customer to purchase the items from the retailer without having to leave the store. Moreover, because draws, for example, are available in preselected increments, customers are not forced to borrow amounts that exceed their borrowing needs.</com:P><com:P com:pNumber="0015">Alternately, embodiments of the present invention can provide funds in advance of purchase to the customer account responsive to a request, which can conveniently include a written correspondence from the customer, a customer selection on a website, a telephone conversation with an interactive voice response unit (IVRU), a telephone conversation with a customer service representative, an interaction using mobile phone, or a combination of these as understood by those skilled in the art, allowing a customer to obtain financing without the need to walk into a brick and mortar location. In this model of an embodiment of the present invention, for example, a customer transaction at the retailer can later be reported to the financial institution, e.g., a bank, so that a fee rebate for an eligible transaction can be applied to the appropriate line of credit balance accordingly.</com:P><com:P com:pNumber="0016">Embodiments of the present invention provide, for example, for establishing a line of credit with a financial institution, e.g., a bank, which can include the customer opting in to a program with the financial institution through an interface access device providing access to a line of credit product, e.g., a computer display device, a kiosk, such as located at a retail store, a point of sale terminal, an IVRU, a call center, a cell phone, a personal digital assistant (&#8220;PDA&#8221;), on-line sensors, or other access interfaces as understood by those skilled in the art. A line of credit amount, for example, can be established based on direct deposit data and preselected underwriting formula, as understood by those skilled in the art, that use the amount of direct deposits, among other factors and data, to determine the size of the credit line available.</com:P><com:P com:pNumber="0017">For example, according to an embodiment of a computer-implemented method of advancing funds using a prepaid card to a customer of a retailer, the computer-implemented method includes establishing a retailer-optimized line of credit with a financial institution, e.g., a bank, for a prepaid card of a customer of retailer responsive to customer underwriting data and predetermined qualification parameters to thereby convert customer underwriting data into line of credit data. The computer-implemented method also includes determining whether to advance funds through the line of credit for a customer transaction and loading the prepaid card with one or more preselected loan increments of funds to thereby convert line of credit data into a value associated with the prepaid card to thereby fund the customer transaction. The preselected increments, e.g., $20, for example, can be less than a total available line of credit, e.g., $300, for a customer having an established line of credit with the financial institution, e.g., the bank. The computer-implemented method further includes decrementing the total available line of credit, e.g., $300, by the one or more preselected increments, e.g., $20, provided for the customer transaction and a predetermined fee amount, e.g., $2.50 or $0, for each of the one or more preselected increments loaded on the prepaid card. The computer-implemented method also includes determining a value of a retailer fee, to be paid by the retailer, having a predetermined amount, e.g., $2, for each of the one or more preselected loan increments loaded on the prepaid card.</com:P><com:P com:pNumber="0018">In an embodiment of a program product stored in one or more tangible computer readable media and readable by a computer, for example, the program product can operate to perform the following instructions when read by the computer: establishing a retailer-optimized line of credit attached to a customer account, e.g., a prepaid card account, of a customer of a retailer responsive to customer underwriting data and predetermined qualification parameters; determining whether to advance funds through the line of credit for a customer transaction; advancing funds in one or more preselected loan increments for the customer transaction, e.g., loading the prepaid card, the preselected loan increments being less than a total available line of credit with the bank; decrementing the total available line of credit by the cumulative amount of the one or more preselected loan increments provided for the customer transaction and by a predetermined customer fee amount for each of the one or more preselected loan increments; and determining a value of a retailer fee, to be paid by the retailer, having a predetermined amount for each of the one or more preselected loan increments advanced.</com:P><com:P com:pNumber="0019">An embodiment of a system to advance funds to a customer of a retailer, for example, includes a plurality of customer access interface devices and a remote computer server positioned to provide communication with each of the plurality of customer access interface devices, being associated with a financial institution, and having memory. The system also includes program product stored in the memory of the computer server so that the program product operates to perform the instructions of: establishing a line of credit attached to a customer account with the financial institution for a customer of a retailer through at least one of the plurality of access interface devices with the remote computer server, the line of credit optimized for a retailer, at least one access interface device being defined to provide access to a line of credit product of the financial institution to interface with a potential customer to establish the line of credit; determining whether to advance funds through the line of credit for a customer transaction; initiating provision of only one or more preselected increments of funds for the customer transaction, e.g., advancing funds in one or more preselected loan increments to the customer account to thereby convert line of credit data into a value associated with the customer account to thereby fund the customer transaction, a cumulative amount of the one or more preselected loan increments being less than a total available line of credit for a customer having an established line of credit with the financial institution; decrementing the total available line of credit by the cumulative amount of the one or more preselected loan increments provided for the customer transaction and by a predetermined customer fee amount for each of the one or more preselected loan increments; and determining a value of a retailer fee to be paid by the retailer, the retailer fee having a predetermined amount for each of the one or more preselected loan increments. The system can also include a plurality of point of sale terminals associated with a plurality of retailers, each point of sale terminal having a processor and memory, and a second computer associated with a customer prepaid card account defining a prepaid card processor. The prepaid card processor is in communication with the financial institution computer server and the plurality of point of sale terminals through an electronic communications network. The prepaid card processor has memory and is positioned to process an authorization request for a proposed purchase of one or more items from a point of sale terminal.</com:P><com:P com:pNumber="0020">Embodiments of the present invention also allow the combining of product enhancements with other complimentary enhancements and can continue to provide significantly improved services and credit products by banking or other financial institutions with the conveniences of traditional banking products in order to increase sales, profits, and financing options at a participating retailer.</com:P><pat:DrawingDescription><com:Heading com:headingLevelCode="H1">BRIEF DESCRIPTION OF DRAWINGS</com:Heading><com:P com:pNumber="0021">So that the manner in which the features and benefits of the invention, as well as others which will become apparent, may be understood in more detail, a more particular description of the invention briefly summarized above may be had by reference to the embodiments thereof which are illustrated in the appended drawings, which form a part of this specification. It is also to be noted, however, that the drawings illustrate only various embodiments of the invention and are therefore not to be considered limiting of the invention's scope as it may include other effective embodiments as well.</com:P><com:P com:pNumber="0022"><com:FigureReference com:idrefs="DRAWINGS">FIG. 1</com:FigureReference> is a flow diagram of a method of advancing funds using a prepaid card to a customer of a retailer according to an embodiment of the present invention;</com:P><com:P com:pNumber="0023"><com:FigureReference com:idrefs="DRAWINGS">FIG. 2</com:FigureReference> is a flow diagram of a method of advancing funds to a customer of a retailer according to an embodiment of the present invention;</com:P><com:P com:pNumber="0024"><com:FigureReference com:idrefs="DRAWINGS">FIG. 3</com:FigureReference> is a schematic diagram of a system to advance funds to a customer of a retailer according to an embodiment of the present invention;</com:P><com:P com:pNumber="0025"><com:FigureReference com:idrefs="DRAWINGS">FIG. 4</com:FigureReference> is a schematic diagram of a computer server having program product stored in memory thereof according to an embodiment of the present invention;</com:P><com:P com:pNumber="0026"><com:FigureReference com:idrefs="DRAWINGS">FIG. 5</com:FigureReference> is a schematic diagram of a computer server having program product stored in memory thereof according to another embodiment of the present invention;</com:P><com:P com:pNumber="0027"><com:FigureReference com:idrefs="DRAWINGS">FIG. 6</com:FigureReference> is a schematic diagram of a system to advance funds to a customer of a retailer according to an embodiment of the present invention;</com:P><com:P com:pNumber="0028"><com:FigureReference com:idrefs="DRAWINGS">FIG. 7</com:FigureReference> is a schematic diagram of loan set up flow according to embodiments of the present invention;</com:P><com:P com:pNumber="0029"><com:FigureReference com:idrefs="DRAWINGS">FIG. 8</com:FigureReference> is a schematic front elevational view of an embodiment of an access interface of a program product and system in the form of a graphical user interface of a display of a computer according to an embodiment of the present invention;</com:P><com:P com:pNumber="0030"><com:FigureReference com:idrefs="DRAWINGS">FIG. 9</com:FigureReference> is a schematic diagram of a payroll processor system according to an embodiment of the present invention;</com:P><com:P com:pNumber="0031"><com:FigureReference com:idrefs="DRAWINGS">FIG. 10</com:FigureReference> is a schematic diagram of a program product according to an embodiment of the present invention;</com:P><com:P com:pNumber="0032"><com:FigureReference com:idrefs="DRAWINGS">FIGS. 11A and 11B</com:FigureReference> are respective front and back plan views of a prepaid card according to an embodiment of the present invention; and</com:P><com:P com:pNumber="0033"><com:FigureReference com:idrefs="DRAWINGS">FIG. 12</com:FigureReference> is a front plan view of a display screen of a computer displaying an excerpt of an account activity statement according to an embodiment of the present invention.</com:P></pat:DrawingDescription><com:Heading com:headingLevelCode="H1">DETAILED DESCRIPTION OF INVENTION</com:Heading><com:P com:pNumber="0034">The present invention will now be described more fully hereinafter with reference to the accompanying drawings, which illustrate embodiments of the invention. This invention may, however, be embodied in many different forms and should not be construed as limited to the illustrated embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout.</com:P><com:P com:pNumber="0035">As illustrated in <com:FigureReference com:idrefs="DRAWINGS">FIGS. 1-12</com:FigureReference>, embodiments of systems <com:B>300</com:B>, <com:B>601</com:B>, program products <com:B>401</com:B>, <com:B>501</com:B>, <com:B>1000</com:B>, and methods <com:B>100</com:B>, <com:B>200</com:B>, e.g., computerized methods, of the present invention can be provided through an electronic communication network <com:B>309</com:B> such as a global communication network like the Internet, World Wide Web, or Web 2.0, through a banking type of network, or through a retail, customer or intranet type of network as understood by those skilled in the art. Program products <com:B>401</com:B>, <com:B>501</com:B>, <com:B>1000</com:B>, for example, can be stored on a computer server <com:B>307</com:B>, <com:B>403</com:B>, <com:B>503</com:B> at bank or financial institution <com:B>603</com:B>, can have memory, and be accessible by a plurality of computers <com:B>301</com:B>, and each can have their own respective memory <com:B>304</com:B>C, as well as operating system and browsing software <com:B>304</com:B>E or program product as desired and as understood by those skilled in the art, at bank customer locations, e.g., customer homes, office, and retail locations.</com:P><com:P com:pNumber="0036">Embodiments of the provide invention provide various ways to establish a line of credit, including the customer opting in to a program with a bank through a written correspondence from the customer, a customer selection on a website, a telephone conversation with an interactive voice response unit (IVRU), a telephone conversation with a customer service representative, a mobile phone, or a combination as understood by those skilled in the art. When launched as an accessible website, for example, the website can provide various software based program product segments, as will be understood by those skilled in the art, from which bank products are accessible or downloadable (see, e.g. <com:FigureReference com:idrefs="DRAWINGS">FIG. 3</com:FigureReference>). The website preferably includes secure site pages or portions, as understood by those skilled in the art, as financial and personal data on or for customers may be provided by a customer. As described herein, the website in an exemplary embodiment includes bank account, bank card, or prepaid card management capabilities as understood by those skilled in the art to enhance qualification of customers and tracking of customer usage data or history. By including this feature, embodiments of other program products, methods, and systems can be enhanced and provided.</com:P><com:P com:pNumber="0037">In an embodiment of the present invention involving establishing a line of credit from a bank or other financial institution for a customer of a retailer, the bank can require or define, for example, the following initial qualification parameters for a customer: (1) customer should be a prepaid card customer; (2) customer should provide employment and wage verification through a direct deposit history; (3) customer should authorize bank initiated withdrawals from their prepaid card; and (4) customer should have a history of at least one electronic deposit. Embodiments can include converting such underwriting data into line of credit data. In addition, the following on-going criteria, for example, should be met in an example embodiment: (1) customer's card account should be in good standing, not overdrawn, cancelled, or in default of the customer agreement; and (2) customer should continue to initiate electronic deposits to the card. The bank or financial institution, for example, may elect to make the account ineligible for a line of credit if an electronic deposit ceases. The bank or financial institution can have a dedicated program manager qualify, approve, or authorize a customer or can use program product stored in memory to make sure the criteria or parameters are satisfied or meet certain thresholds as selected by the bank or financial institution.</com:P><com:P com:pNumber="0038">For example, as illustrated in <com:FigureReference com:idrefs="DRAWINGS">FIG. 7</com:FigureReference>, a customer C can go on-line through a computer or IVRU <com:B>22</com:B> in a system <com:B>20</com:B> to register at a website using a program product according to embodiments of the present invention and launched from a server, e.g., at a loan processor, underwriting organization, bank, lending institution, other financial institution, payroll processing company, or other entity which can provide the line of credit product, among others, as will be understood by those skilled in the art. The form or qualification parameters can be consistent with one or more underwriting organizations or institutions or set/defined by the bank or financial or lending institution.</com:P><com:P com:pNumber="0039">As understood by those skilled in the art, a loan, micro-loan, repayment, line of credit, or other type of payment processor, such as provided by First Data Corporation, Total Systems Services, Inc., Fidelity National Information, Inc., or as custom developed by a bank, a financial institution, or other organization, operates to provide a customer interface on a line of credit or micro-loan request (see, e.g., access interface <com:B>800</com:B> of <com:FigureReference com:idrefs="DRAWINGS">FIG. 8</com:FigureReference> in the form of a computer display having a graphical user interface) and determines and decides whether a potential or existing customer qualifies for a line of credit product. First Data Corporation, formerly First Data Resources, is a transaction processing company, including prepaid cards, and is headquartered in Greenwood Village, Colo., as understood by those skilled in the art. With headquarters located in Columbus, Ga., Total System Services, Inc. provides electronic payment services to financial institutions and companies, including consumer-finance, credit, debit, healthcare, loyalty, prepaid, chip and mobile payments, as understood by those skilled in the art. Headquartered in Jacksonville, Fla., Fidelity National Information, Inc. provides core processing for financial institutions, including card issuer, transaction processing, and outsourcing services to financial institutions and retailers, as understood by those skilled in the art. The line of credit or loan processor <com:B>319</com:B>, for example, can be outsourced by a bank if desired, and numerous different loan processors or entities that handle this function can be used as well (see, e.g., <com:FigureReference com:idrefs="DRAWINGS">FIG. 3</com:FigureReference> with computer server <com:B>319</com:B> handling the payment processor and interface access roles for customer lines of credit <com:B>321</com:B>, for example). If the customer qualifies, the credentials can be passed to a bank computer or other financial institution computer <com:B>307</com:B>, and then a flag, code, notation, or other identifier can be associated with a customer's profile in a database <com:B>308</com:B> so that when the customer desires to access the line of credit, e.g., through a customer purchase transaction using the prepaid card, the process acknowledges the identifier to then allow incremental micro-loans on the line of credit to be granted as described herein. Notably, often a loan or other type of payment processor is card processor specific, and in this instance, a dedicated card processor (see, e.g., prepaid card processor <com:B>315</com:B> in <com:FigureReference com:idrefs="DRAWINGS">FIG. 3</com:FigureReference>, and this processor likewise can be associated with computers and have a customer prepaid card account <com:B>317</com:B> associated with or processed thereby as understood by those skilled in the art) can be used, but also as shown in <com:FigureReference com:idrefs="DRAWINGS">FIG. 7</com:FigureReference> and described further in U.S. Provisional Patent Application Ser. No. 61/029,975 titled &#8220;Methods To Advance Loan Proceeds on Prepaid Cards, Associated Systems and Computer Program Products&#8221; filed on Feb. 20, 2008 and incorporated herein by reference methods can be used as well to handle card interface to a variety of card processors (including, e.g., Metavante Corporation (&#8220;Metavante&#8221;) of Milwaukee, Wis.), as understood by those skilled in the art.</com:P><com:P com:pNumber="0040">The customer transaction using a prepaid card, for example, can then cause the request for the loan advance through the line of credit processor <com:B>30</com:B> or other payment processor. The credit processor <com:B>30</com:B> then posts notification of the micro-loan request through an application program interface (API) to post the loan advance in real time through an API Router <com:B>32</com:B> as understood by those skilled in the art. The API Router <com:B>32</com:B> passes the request through a security firewall <com:B>35</com:B> which passes the request through the API to a card processor <com:B>42</com:B> and particular processor API <com:B>44</com:B>, such as, Metavante. The request data can be compared to flat files <com:B>46</com:B>, <com:B>60</com:B>, <com:B>70</com:B>, e.g., data files that have no structural relationship as understood by those skilled in the art, or flat files database so that the bank or financial institution reconciles the loan transaction with the customer's line of credit or other account <com:B>62</com:B>. Some card processors, for example, provide additional processor interfaces or allow development of additional processor interfaces, as understood by those skilled in the art, (see, e.g., API to Program Manager <com:B>52</com:B>). Program manager operations, for example, can be provided by various financial solution/program management companies, such as AccountNow of San Ramon, Calif., as understood by those skilled in the art. A program manager <com:B>54</com:B>, a card processor API <com:B>56</com:B>, and a card processor <com:B>58</com:B> can be used by the credit processor or other payment processor for a customer transaction as understood by those skilled in the art.</com:P><com:P com:pNumber="0041">Embodiments of the present invention include, for example, a line of credit product from a bank, a financial institution, or a lending institution; the line of credit provides funds in preselected loan increments, e.g. $20 increments, to a customer. Each preselected loan increment accessed can generate a predetermined customer fee and a predetermined retailer fee. For example, in an embodiment of the present invention, the customer fee is zero ($0), and the retailer pays all fees associated with access to the line of credit, say, e.g. $2.50 per preselected loan increment. In this example, the customer has free access to draws against the line of credit for customer transactions at the retailer. That is, the customer must repay the principle, but no interest or fees for a loan for a customer transaction at the retailer.</com:P><com:P com:pNumber="0042">In another embodiment of the present invention, the customer receives a discount on the fee for a draw on a line of credit for customer transactions at the retailer. That is, the predetermined customer fee amount for each of the one or more preselected loan increments for a customer transaction is a first amount if the customer transaction is associated with the retailer and is a second amount if the customer transaction is not associated with the retailer, the second amount being greater than the first amount, to thereby define a fee discount by the retailer. In this embodiment, the customer pays only a portion of the fees associated with a draw from the line of credit for a customer transaction at the retailer, for example, $1.00 instead of typical $2.50. In this embodiment the retailer also pays a fee, and the sum of the customer fee and the retailer fee may be greater than, less than, or equal to the typical fee for access to the line of credit for a transaction not associated with the retailer, as understood by those skilled in the art.</com:P><com:P com:pNumber="0043">In yet another embodiment of the present invention, the bank or financial institution provides the value of the retailer fee to the customer as a rebate. That is, the total available line of credit is incremented by the value of the retailer fee to thereby define a rebate to the customer. Advantageously, this embodiment allows the access to funds conveniently to occur in advance of a purchase; later a customer transaction at the retailer can be reported to the financial institution, e.g., the bank, so that a fee rebate for an eligible transaction can be applied to the appropriate line of credit balance.</com:P><com:P com:pNumber="0044">Embodiments of the present invention can provide funds in advance of purchase responsive to a request. The request for an advance can involve a written correspondence from the customer, a customer selection on a website, a telephone conversation with an interactive voice response unit (IVRU), a telephone conversation with a customer service representative, an interaction using mobile phone, or a combination of these as understood by those skilled in the art, allowing a customer to obtain financing without the need to walk into a brick and mortar location. Alternately, embodiments of the present invention can, for example, provide access to a line of credit within an authorization stream for a proposed transaction, allowing the customer to access funds to purchase items from a retailer without having to leave the store and without having to request funds in advance. According to embodiments of the present invention, determining whether to advance funds through the line of credit for a customer transaction can occur within an authorization stream for a proposed transaction and can include receiving proposed transaction data by the financial institution computer from a card reader device associated with a point of sale terminal responsive to the card reader device reading data from a card associated with the customer account and modifying the data to include point of sale data.</com:P><com:P com:pNumber="0045">The benefits of the embodiments of the present invention to the customer include, for example, a short-term borrowing alternative that is more cost effective than other expensive financial service products, with greater convenience. The benefits further include free or discounted access to credit, in advance of purchase or within an authorization stream. Moreover, because draws, for example, are available in preselected increments, customers are not forced to borrow amounts that exceed their borrowing needs.</com:P><com:P com:pNumber="0046">To the retailer, the benefits of the embodiments of the present invention include reducing the effective price of customer purchases at the retailer and also the promotional value of these discounts. The promotional value of being able to advertise free credit is substantial as understood by those skilled in the arts. Furthermore, the retailer benefits from additional sales and profits enabled by the embodiments of the present invention. For example, according to one embodiment of the present invention, a retailer sells an item to a customer for $10. The item costs the retailer $6 and has a $4 mark-up. If the customer transaction for this item requires the customer's borrowing of a preselected loan increment of $20 with a customer fee of $0 and retailer fee of $2.50, then the retailer earns an additional $10 in sales and $1.50 in profits through this transaction. The $1.50 profit is the $4 mark-up for the item minus the $2.50 fee paid by the retailer. The effect of the embodiments of the present invention is to lower the profit margin, in this example from 40% to 15% (or $4 per $10 of sales to $1.50 per $10 of sales), for customer transactions involving embodiments of the present invention, while preserving the profit margin for other customer transactions as understood by those skilled in the art. Therefore, the embodiments of the present invention target a discount to customer transactions where credit or financing is needed or useful, and advantageously do not provide a general discount or price reduction.</com:P><com:P com:pNumber="0047">In an example of another embodiment of the present invention, a customer receives a loan advance of $200 and purchases $190 of goods from the retailer. If the cost of goods to the retailer for the purchase is $125 and the retailer loan fees associated with the advance is $20 (e.g., $2 per $20 loan increment for 10 increments), then the gross profit for the transaction is $45 ($190&#8722;$125&#8722;$20=$45) even with the loan fees included. To the extent that access to the line of credit is necessary for such transactions, the revenue ($190) and gross profit ($45) represent new sales, additive to the retailer's existing business, as understood by those skilled in the art.</com:P><com:P com:pNumber="0048">Embodiments of the present invention can include an increase in available credit from the line of credit for transactions associated with the retailer so that a predetermined portion of the total available line of credit is reserved for customer transactions associated with the retailer. For example, the total available line of credit is $300, with $200 reserved for customer transactions at the retailer and $100 generally available.</com:P><com:P com:pNumber="0049">Products providing embodiments of the present invention can vary by retailer, offer, program, prepaid card holder, cardholder election, promotion, public acceptance and reception, location, season, and other criteria as understood by those skilled in the art.</com:P><com:P com:pNumber="0050">An embodiment of a system <com:B>300</com:B> to advance funds to a customer of a retailer, as illustrated in <com:FigureReference com:idrefs="DRAWINGS">FIGS. 3-12</com:FigureReference>, for example, includes a plurality of customer access interface devices <com:B>301</com:B> and a remote computer server <com:B>307</com:B> is associated with a financial institution and positioned to provide communication with each of the plurality of customer access interface devices <com:B>301</com:B>. Each customer computer <com:B>301</com:B> can include, for example, input-output I/O devices <com:B>304</com:B>A; one or more processors <com:B>304</com:B>B; memory <com:B>304</com:B>C, such as, computer readable media; and a display <com:B>304</com:B>D. The memory <com:B>304</com:B>C of the customer computer <com:B>301</com:B> can include an Internet browser <com:B>304</com:B>E, a computer application used for accessing sites or information on a network, as understood by those skilled in the art. The financial institution computer <com:B>307</com:B> can include, for example, input-output I/O devices <com:B>306</com:B>A; one or more processors <com:B>306</com:B>B; memory <com:B>306</com:B>C, such as, computer readable media; and a display <com:B>306</com:B>D. The memory <com:B>306</com:B>C of the financial institution computer <com:B>307</com:B> can include a computer program product <com:B>401</com:B> as described herein and can include, for example, one or more databases containing account data files <com:B>308</com:B>. The system also includes program product <com:B>401</com:B>, <com:B>501</com:B>, <com:B>1000</com:B> stored in the memory of the computer server so that the program product operates to perform the instructions of: establishing a line of credit attached to a customer account at the financial institution for a customer of a retailer through at least one of the plurality of access interface devices with the remote computer server responsive to customer underwriting data and predetermined qualification parameters to thereby convert customer underwriting data into line of credit data, the line of credit optimized for a retailer, at least one access interface device being defined to provide access to a line of credit product of the financial institution to interface with a potential customer to establish the line of credit; determining whether to advance funds through the line of credit for a customer transaction; initiating provision of only one or more preselected increments of funds to the customer account to thereby convert line of credit data into a value associated with the customer account to thereby fund the customer transaction, a cumulative amount of the one or more preselected loan increments being less than a total available line of credit for a customer having an established line of credit with the financial institution; decrementing the total available line of credit by the cumulative amount of the one or more preselected loan increments provided for the customer transaction and by a predetermined customer fee amount for each of the one or more preselected loan increments; and determining a value of a retailer fee to be paid by the retailer, the retailer fee having a predetermined amount for each of the one or more preselected loan increments loaded on the prepaid card. The system <com:B>300</com:B> can also include, for example, a plurality of point of sale computers <com:B>313</com:B> associated with a plurality of retailers <com:B>311</com:B>. Each point of sale computer <com:B>313</com:B> can include, for example, input-output I/O devices <com:B>314</com:B>A; one or more processors <com:B>314</com:B>B; memory <com:B>314</com:B>C, such as, computer readable media. The system <com:B>300</com:B> further includes a plurality of card readers <com:B>312</com:B> associated with the plurality of point of sale computers <com:B>313</com:B>. Each card reader <com:B>312</com:B> has a processor defining an acquiring processor. Prepaid card data can be read by swiping the card through a slot <com:B>310</com:B>C past a reading head of a card reader <com:B>312</com:B>. The card reader <com:B>312</com:B> can also include a display <com:B>310</com:B>A and input/output (I/O) devices <com:B>310</com:B>B, e.g., a keypad. The system <com:B>300</com:B> can also include, for example, a line of credit processor or loan processor computer <com:B>319</com:B> (see also <com:B>30</com:B> in <com:FigureReference com:idrefs="DRAWINGS">FIG. 7</com:FigureReference>). A loan processor computer <com:B>319</com:B> can include, for example, input-output I/O devices <com:B>320</com:B>A; one or more processors <com:B>320</com:B>B; memory <com:B>320</com:B>C, such as, computer readable media. The line of credit or loan processor <com:B>319</com:B>, for example, can be outsourced by a bank if desired, and numerous different loan processors or entities that handle this function can be used as well, as understood by those skilled in the art. The system <com:B>300</com:B> can also include, for example, a computer associated with a customer prepaid card account <com:B>317</com:B> defining a prepaid card processor <com:B>315</com:B>. The prepaid card processor <com:B>315</com:B> has memory <com:B>316</com:B>C and is positioned to process an authorization request for a proposed purchase of one or more items from a point of sale terminal. The prepaid card processor <com:B>315</com:B> can include, for example, input-output I/O devices <com:B>316</com:B>A; one or more processors <com:B>316</com:B>B; and memory <com:B>316</com:B>C, such as, computer readable media. The memory <com:B>316</com:B>C of the customer computer <com:B>301</com:B> can include stored and manipulated data regarding a customer prepaid card account <com:B>317</com:B>. The prepaid card processor <com:B>315</com:B> is in communication with the financial institution computer server <com:B>307</com:B> and the plurality of point of sale terminals <com:B>313</com:B> through an electronic communications network <com:B>309</com:B>. As understood by those skilled in the art, the electronic communication network <com:B>309</com:B> can be a global communications network like the Internet, World Wide Web, or Web 2.0; a banking type of network; or a retail, customer or intranet type of network.</com:P><com:P com:pNumber="0051">Embodiments of the present invention include, for example, a retailer-paid subsidy for a customer loan from a bank or other financial institution, as illustrated in <com:FigureReference com:idrefs="DRAWINGS">FIG. 6</com:FigureReference>. Traditionally, a bank <com:B>603</com:B> can offer a customer <com:B>605</com:B> funds from a line of credit <com:B>609</com:B> in exchange for repayment of the loan and fees <com:B>613</com:B>. In addition, a retailer <com:B>607</com:B> can offer a customer <com:B>605</com:B> goods and services <com:B>617</com:B> in exchange for funds <com:B>611</com:B>. According to embodiments of the present invention, a retailer <com:B>607</com:B> can also offer to pay loan fees <com:B>615</com:B> to the bank <com:B>603</com:B> to facilitate or subsidize the bank <com:B>603</com:B> offering funds from a line of credit to the customer. Advantageously, payment of the loan fees <com:B>615</com:B> by the retailer <com:B>607</com:B> corresponds to a transaction between the customer <com:B>605</com:B> and the retailer <com:B>607</com:B>. The offer to pay loan fees involves, as understood by those skilled in the art, a line of credit or overdraft product by a bank or financial institution optimized for the retailer.</com:P><com:P com:pNumber="0052">In an embodiment of a computer-implemented method <com:B>100</com:B> of advancing funds using a prepaid card to a customer of a retailer, as illustrated in <com:FigureReference com:idrefs="DRAWINGS">FIG. 1</com:FigureReference>, the computer-implemented method <com:B>100</com:B> includes establishing from a bank a line of credit for a prepaid card of a customer responsive to customer underwriting data and predetermined qualification parameters, where the line of credit is optimized for a retailer <com:B>103</com:B>. The computer-implemented method <com:B>100</com:B> also includes determining whether to advance funds through the line of credit for a customer transaction <com:B>105</com:B> and loading the prepaid card with one or more preselected loan increments of funds for the customer transaction <com:B>107</com:B> to thereby convert line of credit data into a value associated with a prepaid card so that the value associated with the prepaid card is exchanged for goods. The preselected increments, e.g., $20, for example, can be less than a total available line of credit, e.g., $300, for a customer having an established line of credit with the bank. The computer-implemented method <com:B>100</com:B> further includes decrementing the total available line of credit, e.g., $300, by the one or more preselected increments, e.g., $20, provided for the customer transaction and a predetermined fee amount, e.g., $2.50 or $0, for each of the one or more preselected increments loaded on the prepaid card <com:B>109</com:B>. The computer-implemented method <com:B>100</com:B> also includes determining a value of a retailer fee, to be paid by the retailer, having a predetermined amount, e.g., $2, for each of the one or more preselected loan increments loaded on the prepaid card <com:B>111</com:B>. The computer-implemented method <com:B>100</com:B> can further include, for example, incrementing the total available line of credit by the value of the retailer fee to thereby define a rebate to the customer <com:B>113</com:B>.</com:P><com:P com:pNumber="0053">In an embodiment of a computer-implemented method <com:B>200</com:B> of advancing funds using a prepaid card to a customer of a retailer, as illustrated in <com:FigureReference com:idrefs="DRAWINGS">FIG. 2</com:FigureReference>, the computer-implemented method <com:B>200</com:B> includes establishing from a financial institution, e.g., a bank, a line of credit for a customer responsive to customer underwriting data and predetermined qualification parameters to thereby convert customer underwriting data into line of credit data, where the line of credit is optimized for a retailer <com:B>203</com:B>. The computer-implemented method <com:B>200</com:B> also includes determining whether to advance funds through the line of credit for a customer transaction <com:B>205</com:B> and providing only one or more preselected loan increments of funds for the customer transaction <com:B>107</com:B> to the customer account to thereby convert line of credit data into a value associated with the customer account to thereby fund the customer transaction. The preselected increments, e.g., $20, for example, can be less than a total available line of credit, e.g., $300, for a customer having an established line of credit with the bank. The computer-implemented method <com:B>200</com:B> further includes decrementing the total available line of credit, e.g., $300, by the one or more preselected increments, e.g., $20, provided for the customer transaction and a predetermined fee amount, e.g., $2.50 or $0, for each of the one or more preselected increments <com:B>209</com:B>. The computer-implemented method <com:B>200</com:B> also includes determining a value of a retailer fee, to be paid by the retailer, having a predetermined amount, e.g., $2, for each of the one or more preselected loan increments <com:B>211</com:B>.</com:P><com:P com:pNumber="0054">Embodiments of the present invention can also include overdraft protection products or programs, with draws based on actual amounts spent or from a line of credit occurring in preselected increments, e.g. $20 increments, with a customer and retailer fee associated with each increment, to satisfy an overdraft of a checking account, deposit account, or other bank account as understood by those skilled in the art. An overdraft protection product can be associated with the first bank offering the line of credit or a second bank that has integrated the product as understood by those skilled in the art.</com:P><com:P com:pNumber="0055">In an embodiment of a program product <com:B>401</com:B> stored in one or more tangible computer readable media <com:B>405</com:B> and readable by a computer <com:B>403</com:B>, as illustrated in <com:FigureReference com:idrefs="DRAWINGS">FIG. 4</com:FigureReference>, for example, the program product <com:B>401</com:B> can operate to perform the various instructions <com:B>407</com:B> when read by the computer <com:B>403</com:B>. The program product establishes a retailer-optimized line of credit from a bank for a prepaid card of a customer of a retailer <com:B>409</com:B> responsive to customer underwriting data and predetermined qualification parameters to thereby convert customer underwriting data into line of credit data. The program product determines whether to advance funds through the line of credit for a customer transaction <com:B>411</com:B> and then loads the prepaid card with one or more preselected loan increments of funds for the customer transaction to the customer account to thereby convert line of credit data into a value associated with the customer account to thereby fund the customer transaction, the preselected loan increments being less than a total available line of credit with the bank <com:B>413</com:B>. The program product decrements the total available line of credit by the cumulative amount of the one or more preselected loan increments provided for the customer transaction and by a predetermined customer fee amount for each of the one or more preselected loan increments loaded on the prepaid card <com:B>415</com:B>. The program product determines a value of a retailer fee, to be paid by the retailer, having a predetermined amount for each of the one or more preselected loan increments loaded on the prepaid card <com:B>417</com:B>. The program product can further increment the total available line of credit by the value of the retailer fee to thereby define a rebate to the customer.</com:P><com:P com:pNumber="0056">In another embodiment of a program product <com:B>501</com:B> stored in one or more tangible computer readable media <com:B>505</com:B> and readable by a computer <com:B>503</com:B>, as illustrated in <com:FigureReference com:idrefs="DRAWINGS">FIG. 5</com:FigureReference>, for example, the program product <com:B>501</com:B> can operate to perform instructions <com:B>507</com:B>, such as establishing a retailer-optimized line of credit from a bank for a customer of a retailer <com:B>509</com:B> responsive to customer underwriting data and predetermined qualification parameters to thereby convert customer underwriting data into line of credit data, determining whether to advance funds through the line of credit for a customer transaction <com:B>511</com:B>, providing only one or more preselected loan increments of funds for the customer transaction to the customer account, the preselected loan increments being less than a total available line of credit with the bank <com:B>513</com:B>, decrementing the total available line of credit by the cumulative amount of the one or more preselected loan increments provided for the customer transaction and by a predetermined customer fee amount for each of the one or more preselected loan increments <com:B>515</com:B>, and determining a value of a retailer fee, to be paid by the retailer, having a predetermined amount for each of the one or more preselected loan increments <com:B>517</com:B>.</com:P><com:P com:pNumber="0057">A person having ordinary skill in the art will recognize that various types of memory are readable by a computer such as described herein, e.g., bank computer, computer server, financial institution computer, prepaid card processors, or other computers with embodiments of the present invention. Examples of computer readable media include but are not limited to: nonvolatile, hard-coded type media such as read only memories (ROMs), CD-ROMs, and DVD-ROMs, or erasable, electrically programmable read only memories (EEPROMs), recordable type media such as floppy disks, hard disk drives, CD-R/RWs, DVD-RAMS, DVD-R/RWs, DVD+R/RWs, flash drives, memory sticks, and other newer types of memories, and transmission type media such as digital and analog communication links. For example, such media can include operating instructions, as well as instructions related to the system and the method steps described above and can operate on a computer. It will be understood by those skilled in the art that such media can be at other locations instead of or in addition to the locations described to store program products, e.g., including software, thereon. Embodiments of a system to advance funds to a customer, for example, can include a plurality of customer access interface devices as illustrated and described herein and one or more remote computer servers positioned to provide communication with each of the plurality of customer access interface devices and being associated with a financial institution. Each of these computer servers, for example, can having one or more of these various types of memory as understood by those skilled in the art.</com:P><com:P com:pNumber="0058">Embodiments of the present invention can, for example, include repayment of at least portions of the line of credit responsive to a subsequent direct deposit received for customer's benefit by the bank so that the repayment of the at least portions of the line of credit is deducted from the subsequent direct deposit. That is, loans made under a line of credit can be repaid out of the proceeds of a direct deposit. Recurring direct deposits include, for example, employer payroll funds, federal or state government electronic benefits payments, annuities, dividends, interest payments, lottery winnings, royalty payments, and other streams of payments as understood by one skilled in the art. Repayment embodiments also include decrementing a designated direct deposit from the demand deposit account at a second financial institution, e.g., a second bank, for repayment of at least portions of the line of credit.</com:P><com:P com:pNumber="0059">Embodiments of systems, program products, and computer-implemented methods of the present invention can include, for example, for substantially all programs if desired, features such as any repayment of draws on the line of credit can be automatically collected from the next electronic deposit regardless of payment source. As payments are received, fees also can be paid first then the payment applied to the oldest outstanding draw amount. When payments are received, total available line limit is restored by the payment amount. If funds from the electronic deposit are not sufficient to cover the outstanding balance, a partial repayment can be made in the full amount of the electronic deposit resulting in an unpaid balance on the line. Repayment of the remaining unpaid balance can be taken from subsequent electronic deposits until the line has been paid in full. Other cash equivalent repayment options also can be accepted and processed by a line of credit processor as understood by those skilled in the art.</com:P><com:P com:pNumber="0060">It will also be understood by those skilled in the art that embodiments of the line of credit product or program product, for example, can be associated with a payroll processing company that processes direct deposits (see, e.g., <com:FigureReference com:idrefs="DRAWINGS">FIG. 9</com:FigureReference>). Embodiments of the program product and methods can be added to product or service offerings by the payroll processing company <com:B>910</com:B> so that it can be offered to their customers independent of bank or product (DDA or payroll card), by taking money or funds out at the source <com:B>910</com:B>, e.g., as the payroll file is prepared <com:B>920</com:B> and before the direct deposit is even originated, or loaded onto a prepaid card, for example. These embodiments can also allow the processing company <com:B>910</com:B> to have more direct information on employment history. A payroll processing company <com:B>910</com:B> can also use a loan processing system <com:B>940</com:B>, loan processor, or other payment processor either within their facilities or as an outsourcing entity to allow the provision of enrolling and providing customer payroll information <com:B>924</com:B> and for tracking and reconciling repayment or updated customer payroll information with repayments pulled <com:B>944</com:B>. The payroll can be sent, loaded or processed by a payroll processor <com:B>930</com:B> for ACH transmittal, check generation, or card loading/providing, for example (see, e.g., <com:FigureReference com:idrefs="DRAWINGS">FIG. 9</com:FigureReference>). These embodiments of associated methods, for example, can include providing a prepaid card to an employee who gets direct deposit to a DDA whereby the consumer borrow funds from the service/product and has those funds direct deposited onto the card instantly and repaid by pulling funds from the direct deposit file prior to sending to the other bank account to repay the amount withdrawn. An example of and more details on how repayment can be accomplished is illustrated in U.S. Provisional Patent Application Ser. No. 61/016,213 titled &#8220;Transfer Account Systems, Computer Program Products, and Associated Methods&#8221; filed on Dec. 21, 2007 which is incorporated herein by reference in its entirety.</com:P><com:P com:pNumber="0061">Additionally, along these lines, any repayment of a line supersedes repayment of a negative balance on a card due to force posts or settlement transactions that cause the card to go negative. Any monies remaining after a payment is received can be credited to the prepaid card account. If payment takes the card balance to $0, any transactions attempted with the card can be declined. Those transactions can be subject to any related decline fees. Repayment of a draw, for example, should not be taken from the principal balance on a card. That is, if a card balance is positive prior to a draw, only when the next electronic deposit is initiated to the card will repayment be triggered. If a draw is not paid within the preselected time period, preferably days, e.g., 35 day timeframe, any amount owed can be taken from the principal balance on a card.</com:P><com:P com:pNumber="0062">Embodiments of the present invention provide, for example, a program product <com:B>1000</com:B> associated with a bank or other financial or lending institution implemented in modules or components, as illustrated in <com:FigureReference com:idrefs="DRAWINGS">FIG. 10</com:FigureReference>. A retail product configuration tool <com:B>1001</com:B> can, for example, define, adjust, and analyze the predetermined customer fee <com:B>1011</com:B>, the predetermined retailer fee <com:B>1012</com:B>, the portion of credit reserved for transactions with the retailer <com:B>1013</com:B>, and other features, characteristics, and parameters of a line of credit optimized for a retailer. Retail configuration tool <com:B>1001</com:B> embodiments advantageously allow the customization of a product line for each retailer, promotion, or season as understood by those skilled in the art. An underwriting analyzer and interface component <com:B>1005</com:B> of a bank program product <com:B>1000</com:B> can receive underwriting information, e.g., data, and make the determine whether to offer a line of credit or other product to the customer as understood by those skilled in the art. Underwriting data can include whether a customer is an existing prepaid card customer <com:B>1021</com:B>; a direct deposit history <com:B>1022</com:B>; a withdrawal authorization or approval <com:B>1023</com:B>, from an enrollment in a line of credit program; a history of at least one electronic deposit <com:B>1024</com:B>; an account being in good standing, not overdrawn, cancelled, or in default <com:B>1025</com:B>; continued direct deposit <com:B>1026</com:B>; and other data as understood by those skilled in the art. In addition, a loan advance and fee manager module <com:B>1003</com:B> deals with determining whether to advance funds <com:B>1031</com:B>, providing loans in increments <com:B>1032</com:B>, calculating available credit <com:B>1033</com:B>, managing repayments <com:B>1034</com:B>, and other associated tasks as understood by those skilled in the art. Other architectures and organizations will be understood by those skilled in the art to be included within the embodiments of the present invention. Program products can be implemented in a variety of software and programming languages, including without limitation hypertext markup language (&#8220;HTML&#8221;), Java, C, C++, XML, and others as understood by those skilled in the art.</com:P><com:P com:pNumber="0063">As illustrated in <com:FigureReference com:idrefs="DRAWINGS">FIGS. 11A</com:FigureReference>, <com:B>11</com:B>B, and <com:B>3</com:B>, embodiments of the present invention can include, for example, a card <com:B>950</com:B>, e.g., a prepaid card, and a card reader device <com:B>312</com:B>, associated with a point of sale terminal <com:B>313</com:B>. As understood by those skilled in the art, a card <com:B>950</com:B>, e.g., a prepaid card, can have indicia <com:B>952</com:B>, e.g., logos, slogans, source identifiers, of a financial institution, i.e., a sponsoring bank and of a prepaid card processor; a serial number <com:B>954</com:B>; and expiration date <com:B>956</com:B>. The structures of various types of specific cards, e.g., magnetic stripe <com:B>958</com:B>, type of material, are well known to those skilled in the art and can be used with embodiments of the present invention. Typically, a card <com:B>950</com:B> is formed from plastic and has a magnetic stripe <com:B>958</com:B> affixed to the plastic through an application of heat. Those skilled in the art will understand that other embodiments besides a magnetic stripe can include radio frequency identification devices (RFID), smart chips, bar codes, and other similar devices. Embodiments of the present invention can include forming cards or receiving cards already formed. The magnetic stripe card <com:B>950</com:B> can store information, or data, e.g., account information, by modifying the magnetism of particles on the magnetic stripe <com:B>958</com:B> on the card. The information can be read by swiping the card through a slot <com:B>310</com:B>C past a reading head of a card reader device <com:B>312</com:B>. The card reader device <com:B>312</com:B> and associated point of sale terminal <com:B>313</com:B> can include a display <com:B>310</com:B>A and input/output (I/O) devices <com:B>310</com:B>B, e.g., a keypad. Typically, there are two tracks of information on a magnetic card <com:B>950</com:B> used for financial transactions, known as tracks <com:B>1</com:B> and <com:B>2</com:B>. In addition, a third track, known as track <com:B>3</com:B>, can be available for magnetic stripe cards. Tracks <com:B>1</com:B> and <com:B>3</com:B>, if available, are typically recorded at 210 bits per inch, while track <com:B>2</com:B> typically has a recording density of 75 bits per inch. Track <com:B>2</com:B>, as typically encoded, was developed by the American Bankers Association (ABA) provides for 37 numeric data characters, including up to 19 digits for a primary account number (including a Bank Identification Number as understood by those skilled in the art), an expiration date, a service code, and discretionary verification data, such as, a Personal Identification Number, or PIN. The information, e.g., data, on the card can be used, for example, to facilitate a transaction. For example, when the card <com:B>950</com:B> is swiped through a slot <com:B>310</com:B>C, the data on the magnetic stripe <com:B>958</com:B> is read and processed by the point of sale terminal <com:B>312</com:B>, converting data stored in the magnetic particles on the card into data associated with readers <com:B>312</com:B> and a financial institution computer <com:B>307</com:B>. The card reader <com:B>312</com:B> and associated point of sale terminal <com:B>313</com:B> can then communicate through an electronic communications network <com:B>309</com:B> to, for example, a prepaid card processor <com:B>315</com:B> or a financial institution computer <com:B>307</com:B>. The card reader <com:B>312</com:B> communicates the account information, e.g., data, as read from the card, as well as other data, such as, an amount of a proposed transaction for approval from the point of sale terminal <com:B>313</com:B>. The other data, for example, can be entered by merchant personnel (e.g., an amount of the transaction), the consumer (e.g., a PIN, or security code), or bank personnel (e.g., a security approval). The prepaid card processor <com:B>315</com:B> or a financial institution computer <com:B>307</com:B> can then utilize the account information and other data to authorize or reject a purchase by, for example, determining whether a proposed purchase by the consumer is less than an amount of funds remaining on the card. Moreover, optional security measures, including, for example, a mismatch between a PIN supplied by the consumer and a PIN stored on the card or in a database, can result in the rejection of a proposed transaction. The prepaid card processor <com:B>315</com:B> or financial institution computer <com:B>307</com:B> then perform certain functions, including responding to the authorization request so that a point of sale displays an indication of approval or rejection, resulting in a visual depiction to a merchant of the approval or rejection of the proposed transaction. Also, prepaid card processor <com:B>315</com:B> can, for example, write data to a database to record a purchase of other transaction (including advancing a loan from the line of credit), to debit available funds from an account associated with the prepaid card <com:B>950</com:B>, and to credit directly or indirectly a merchant for a purchase. In addition to purchase authorization, embodiments of the present invention also can include customer inquiries into recent transactions or a balance inquiry, i.e., an amount of remaining value associated with the prepaid card.</com:P><com:P com:pNumber="0064">As illustrated in <com:FigureReference com:idrefs="DRAWINGS">FIG. 12</com:FigureReference>, embodiments of the present invention include, for example, providing data associated with a customer account having an attached line of credit as a visual representation of account activity. For example, a customer computer <com:B>301</com:B>, through an Internet Browser <com:B>304</com:B>E, (see <com:FigureReference com:idrefs="DRAWINGS">FIG. 3</com:FigureReference>) can display on a display device <com:B>304</com:B>D an account activity statement <com:B>712</com:B> for a customer-specific account <com:B>713</com:B>, or set of accounts, with each transaction including, for example, a date <com:B>714</com:B>A, a description <com:B>714</com:B>B, a amount credited to the account <com:B>714</com:B>C, an amount debited from the account <com:B>714</com:B>D, a resulting card balance <com:B>714</com:B>E, a line of credit amount available <com:B>714</com:B>F, and a line of credit outstanding balance <com:B>714</com:B>G, or other such data as understood by those skilled in the art. For example, the visual representation can include a card balance inquiry <com:B>715</com:B>A. For example, the visual representation can include advancing funds in one or more preselected loan increments for the customer transaction and decrementing the total available line of credit by the cumulative amount of the one or more preselected loan increments provided for the customer transaction and by a predetermined customer fee amount for each of the one or more preselected loan increments <com:B>715</com:B>B. For example, the visual representation can include a purchase of goods <com:B>715</com:B>C, wherein data associated with a prepaid card representing an amount of value associated with a line of credit is modified in an exchange for products, including goods or services. For example, the visual representation can include incrementing the total available line of credit by the value of a retailer fee to thereby define a rebate to the customer <com:B>715</com:B>D. In addition, the visual representation can include a direct deposit <com:B>715</com:B>E and also a loan repayment from direct deposit funds relatively instantaneously (or prior to) with the direct deposit funds being made available in the consumer's account <com:B>715</com:B>F. Also, the visual representation can include an adjustment to the total loan value responsive to consumer performance data <com:B>715</com:B>G. In other embodiments, advancing the loan increments <com:B>715</com:B>B and an associated purchase of goods <com:B>715</com:B>C can be represented as a single transaction; likewise, the direct deposit <com:B>715</com:B>E and an associated loan repayment <com:B>715</com:B>F can be represented as a single transaction.</com:P><com:P com:pNumber="0065">This application claims priority to and the benefit of: U.S. Provisional Patent Application Ser. No. 61/042,624, by Crowe et al., titled &#8220;System, Program Product, and Method to Authorize Draw for Retailer Optimization&#8221; filed on Apr. 4, 2008; and U.S. Provisional Patent Application Ser. No. 61/042,612, by Ahlers et al., titled &#8220;System, Program Product, and Associated Methods to Authorize Draw for Micro-Credit Attached to a Prepaid Card&#8221; filed on Apr. 4, 2008, all of which are each incorporated herein by reference in their entireties. This application also relates to: U.S. Provisional Patent Application Ser. No. 61/016,213, by Sorbe et al., titled &#8220;Transfer Account Systems, Computer Program Products, and Associated Methods&#8221; filed on Dec. 21, 2007; U.S. Provisional Patent Application Ser. No. 61/052,454, by Sorbe et al., titled &#8220;Transfer Account Systems, Computer Program Products, and Methods to Prioritize Payments from Preselected Bank Account&#8221; filed May 12, 2008; U.S. Provisional Patent Application Ser. No. 61/029,975, by Sorbe et al., titled &#8220;Methods To Advance Loan Proceeds On Prepaid Cards, Associated Systems and Computer Program Products&#8221; filed on Feb. 20, 2008; U.S. Provisional Patent Application Ser. No. 61/032,750, by Ahlers et al., titled &#8220;Methods, Program Product, and System for Micro-Loan Management&#8221; filed on Feb. 29, 2008; U.S. Provisional Patent Application Ser. No. 61/060,559, by Galit et al., titled &#8220;Methods, Program Product, and System to Enhance Banking Terms Over Time&#8221; filed on Jun. 11, 2008; U.S. Provisional Patent Application Ser. No. 61/082,863, by Ahlers et al., titled &#8220;System, Program Product, and Method For Debit Card and Checking Account Autodraw&#8221; filed on Jul. 23, 2008; U.S. Provisional Patent Application Ser. No. 61/053,056, by Galit et al., titled &#8220;System, Program Product, and Method For Loading a Loan On a Pre-Paid Card&#8221; filed on May 14, 2008, all of which are each incorporated herein by reference in their entireties. This application also relates to: U.S. patent application Ser. No. 12/338,365, by Sorbe et al., titled &#8220;Transfer Account Systems, Computer Program Products, and Associated Computer-Implemented Methods&#8221; filed on Dec. 18, 2008, and issued on Nov. 8, 2011 as U.S. Pat. No. 8,055,557; U.S. patent application Ser. No. 12/338,402, by Sorbe et al., titled &#8220;Transfer Account Systems, Computer Program Products, and Associated Computer-Implemented Methods&#8221; filed on Dec. 18, 2008; U.S. patent application Ser. No. 12/338,440, by Sorbe et al., titled &#8220;Transfer Account Systems, Computer Program Products, and Associated Computer-Implemented Methods&#8221; filed on Dec. 18, 2008; U.S. patent application Ser. No. 12/338,584, by Sorbe et al., titled &#8220;Transfer Account Systems, Computer Program Products, and Computer-Implemented Methods to Prioritize Payments from Preselected Bank Account&#8221; filed Dec. 18, 2008; U.S. patent application Ser. No. 12/338,645, by Sorbe et al., titled &#8220;Transfer Account Systems, Computer Program Products, and Computer-Implemented Methods to Prioritize Payments from Preselected Bank Account&#8221; filed Dec. 18, 2008, and issued on Nov. 8, 2011 as U.S. Pat. No. 8,055,557; U.S. patent application Ser. No. 12/389,749, by Sorbe et al., titled &#8220;Methods to Advance Loan Proceeds on Prepaid Cards, Associated Systems and Computer Program Products&#8221; filed on Feb. 20, 2009; PCT/US09/34692, by Sorbe et al., titled &#8220;Methods to Advance Loan Proceeds on Prepaid Cards, Associated Systems and Computer Program Products&#8221; filed on Feb. 20, 2009; U.S. patent application Ser. No. 12/417,199, by Ahlers et al., titled &#8220;System, Program Product, and Associated Methods to Autodraw for Micro-Credit Attached to a Prepaid Card&#8221; filed on the same day herewith, and issued on Nov. 22, 2011 as U.S. Pat. No. 8,065,187; U.S. patent application Ser. No. 12/417,211, by Ahlers et al., titled &#8220;System, Program Product, and Associated Methods to Authorize Draw for Micro-Credit Attached to a Prepaid Card&#8221; filed on the same day herewith, and issued on Nov. 29, 2011 as U.S. Pat. No. 8,069,085; U.S. patent application Ser. No. 12/338,684, by Ahlers et al., titled &#8220;Computer-Implemented Methods, Program Product, and System for Micro-Loan Management&#8221; filed on Dec. 18, 2008; PCT/US08/87660 by Ahlers et al., titled &#8220;Computer-Implemented Methods, Program Product, and System for Micro-Loan Management&#8221; filed on Dec. 19, 2008; U.S. patent application Ser. No. 12/338,712, by Galit et al., titled &#8220;Computer-Implemented Methods, Program Product, and System to Enhance Banking Terms Over Time&#8221; filed on Dec. 18, 2008; and PCT/US08/87689 by Galit et al., titled &#8220;Computer-Implemented Methods, Program Product, and System to Enhance Banking Terms Over Time&#8221; filed on Dec. 19, 2008; U.S. patent application Ser. No. 12/417,162, by Ahlers et al., titled &#8220;System, Program Product, and Method For Debit Card and Checking Account Autodraw&#8221; filed on the same day herewith, all of which are each incorporated herein by reference in their entireties.</com:P><com:P com:pNumber="0066">Many modifications and other embodiments of the invention will come to the mind of one skilled in the art having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the invention is not to be limited to the illustrated embodiments disclosed, and that modifications and other embodiments are intended to be included within the scope of the appended claims.</com:P></pat:Description><pat:ClaimStatement>That claimed is:</pat:ClaimStatement><pat:Claims com:languageCode="en" pat:dataFormat="original" pat:source="NATIONAL"><pat:Claim com:id="CLM-00001" com:pNumber="00001"><pat:ClaimText>1. A system to allow a plurality of customers to access a plurality of line of credits associated with a plurality of customer accounts, the system comprising:
<pat:ClaimText>a computer associated with a financial institution defining a financial institution computer, the financial institution computer being associated with an electronic communications network and adapted to manage a plurality of line of credit accounts with the financial institution; and</pat:ClaimText><pat:ClaimText>non-transitory computer-readable medium encoded with computer program operable on the financial institution computer, the computer program comprising:
<pat:ClaimText>a first computer program to extend one or more line of credit accounts associated with one or more of a plurality of customer accounts defining an incremental line of credit qualifying module, the incremental line of credit qualifying module comprising the instruction of:
<pat:ClaimText>establishing, responsive to customer underwriting data and predetermined qualification parameters, a plurality of line of credit accounts associated with a plurality of customer accounts for a plurality of customers, the plurality of line of credit accounts having a plurality of total credit limits having a first portion and a second portion, the first portion of the plurality of total credit limits being reserved for use with one or more transactions with a retailer, each of the plurality of line of credit accounts further being adapted to be drawn in at least one of a plurality of separate predetermined loan increments each being equal in value;</pat:ClaimText></pat:ClaimText><pat:ClaimText>a second computer program to allow one or more draws to the one or more of the plurality of line of credit accounts in one or more of the plurality of separate predetermined loan increments, the second computer program defining an incremental line of credit dispensing module and comprising the instructions of:
<pat:ClaimText>determining whether to advance funds from one or more of the plurality of line of credit accounts to one or more of the plurality of customer accounts for one or more customer transaction;</pat:ClaimText><pat:ClaimText>determining a number of separate predetermined loan increments to be added to the one or more of the plurality of customer accounts responsive to the determination to advance funds from the one or more of the plurality of line of credit accounts for the one or more customer transactions; and</pat:ClaimText><pat:ClaimText>loading the one or more of the plurality of customer accounts with at least one of the plurality of separate predetermined loan increments that corresponds with the determined number of separate predetermined loan increments to thereby define loaded predetermined increments when the loaded predetermined increments do not exceed a line of credit balance available for the one or more of the plurality of line of credit accounts, a total value of a predetermined loan advance fee being equal to a predetermined financial institution fee plus a predetermined retailer fee multiplied by the number of separate predetermined loan increments.</pat:ClaimText></pat:ClaimText></pat:ClaimText></pat:ClaimText></pat:Claim><pat:Claim com:id="CLM-00002" com:pNumber="00002"><pat:ClaimText>2. A system as defined in <pat:ClaimReference com:idrefs="CLM-00001">claim 1</pat:ClaimReference>, wherein determining whether to advance funds from the one or more of the plurality of line of credit accounts includes: determining, responsive to receipt of transaction data, when one or more customer transaction cards associated with the one or more of the plurality of customer accounts is being used as payment for one or more customer transactions and when a value of the one or more customer transactions is greater than a value associated with the one or more of the plurality of customer accounts.</pat:ClaimText></pat:Claim><pat:Claim com:id="CLM-00003" com:pNumber="00003"><pat:ClaimText>3. A system as defined in <pat:ClaimReference com:idrefs="CLM-00001">claim 1</pat:ClaimReference>, wherein the total value of the predetermined loan advance fee is a first amount when the one or more customer transactions is with the retailer and a second amount when the one or more customer transactions is not with the retailer, the second amount being larger than the first amount so that advances from the one or more of the plurality of line of credit accounts for one or more customer transactions with the retailer are provided at a discount.</pat:ClaimText></pat:Claim><pat:Claim com:id="CLM-00004" com:pNumber="00004"><pat:ClaimText>4. A system as defined in <pat:ClaimReference com:idrefs="CLM-00001">claim 1</pat:ClaimReference>, wherein the incremental line of credit dispensing module further comprises the instructions of:
<pat:ClaimText>deducting the loaded predetermined increments and the total value of the predetermined loan advance fee from a line of credit balance available associated with the one or more of the plurality of line of credit accounts; and</pat:ClaimText><pat:ClaimText>decreasing a line of credit balance associated with the one or more of the plurality of line of credit accounts by at least the predetermined retailer fee to thereby provide a rebate to one or more of the plurality of customers.</pat:ClaimText></pat:ClaimText></pat:Claim><pat:Claim com:id="CLM-00005" com:pNumber="00005"><pat:ClaimText>5. A system as defined in <pat:ClaimReference com:idrefs="CLM-00001">claim 1</pat:ClaimReference>, wherein determining whether to advance funds from the one or more of the plurality of line of credit accounts is responsive to a request to draw funds from the one or more of the plurality of line of credit accounts using an interactive voice response unit; and wherein the financial institution is a first financial institution and one or more of the plurality of customer accounts are managed by a second financial institution different and positioned remote from the first financial institution.</pat:ClaimText></pat:Claim><pat:Claim com:id="CLM-00006" com:pNumber="00006"><pat:ClaimText>6. A system as defined in <pat:ClaimReference com:idrefs="CLM-00001">claim 1</pat:ClaimReference>, wherein the predetermined retailer fee is paid by the retailer when the loaded predetermined increments are used for the one or more customer transactions with the retailer.</pat:ClaimText></pat:Claim><pat:Claim com:id="CLM-00007" com:pNumber="00007"><pat:ClaimText>7. A system as defined in <pat:ClaimReference com:idrefs="CLM-00002">claim 2</pat:ClaimReference>, wherein the determined number of separate predetermined loan increments multiplied by a value of one of the plurality of separate predetermined loan increments plus the value associated with the one or more of the plurality of customer accounts exceeds the value of the one or more customer transactions by less than the value of one of the plurality of separate predetermined loan increments.</pat:ClaimText></pat:Claim><pat:Claim com:id="CLM-00008" com:pNumber="00008"><pat:ClaimText>8. Non-transitory computer-readable medium encoded with computer program operable on a computer to allow a plurality of customers to access a plurality of line of credits associated with a plurality of customer accounts, the computer program comprising:
<pat:ClaimText>a first computer program to extend one or more line of credit accounts associated with one or more of a plurality of customer accounts defining an incremental line of credit qualifying module, the incremental line of credit qualifying module comprising the instruction of:
<pat:ClaimText>establishing, by a computer associated with a financial institution to define a financial institution computer, responsive to customer underwriting data and predetermined qualification parameters, a plurality of line of credit accounts associated with a plurality of customer accounts for a plurality of customers, the plurality of line of credit accounts having a plurality of total credit limits and adapted to be drawn in at least one of a plurality of separate predetermined loan increments each being equal in value;</pat:ClaimText></pat:ClaimText><pat:ClaimText>a second computer program to allow one or more draws to the one or more of the plurality of line of credit accounts in one or more of the plurality of separate predetermined loan increments, the second computer program defining an incremental line of credit dispensing module and comprising the instructions of:
<pat:ClaimText>determining whether to advance funds from one or more of the plurality of line of credit accounts to one or more of the plurality of customer accounts for one or more customer transaction;</pat:ClaimText><pat:ClaimText>determining a number of separate predetermined loan increments to be added to the one or more of the plurality of customer accounts responsive to the determination to advance funds from the one or more of the plurality of line of credit accounts for the one or more customer transactions; and</pat:ClaimText><pat:ClaimText>loading the one or more of the plurality of customer accounts with at least one of the plurality of separate predetermined loan increments that corresponds with the determined number of separate predetermined loan increments to thereby define loaded predetermined increments when the loaded predetermined increments do not exceed a line of credit balance available for the one or more of the plurality of line of credit accounts, a total value of a predetermined loan advance fee being equal to a predetermined financial institution fee plus a predetermined retailer fee multiplied by the number of separate predetermined loan increments.</pat:ClaimText></pat:ClaimText></pat:ClaimText></pat:Claim><pat:Claim com:id="CLM-00009" com:pNumber="00009"><pat:ClaimText>9. Non-transitory computer-readable medium as defined in <pat:ClaimReference com:idrefs="CLM-00008">claim 8</pat:ClaimReference>, wherein determining whether to advance funds from the one or more of the plurality of line of credit accounts includes: determining, responsive to receipt of transaction data, when one or more customer transaction cards associated with the one or more of the plurality of customer accounts is being used as payment for one or more customer transactions and when a value of the one or more customer transactions is greater than a value associated with the one or more of the plurality of customer accounts.</pat:ClaimText></pat:Claim><pat:Claim com:id="CLM-00010" com:pNumber="00010"><pat:ClaimText>10. Non-transitory computer-readable medium as defined in <pat:ClaimReference com:idrefs="CLM-00008">claim 8</pat:ClaimReference>, wherein the plurality of total credit limits of the plurality of line of credit accounts have a first portion and a second portion, the first portion being larger than the second portion and reserved for use with one or more transactions with the retailer; and wherein the predetermined retailer fee being a first amount when the one or more customer transactions is with a retailer and a second amount when the one or more customer transactions is not with the retailer, the second amount being larger than the first amount so that advances from the one or more of the plurality of line of credit accounts for one or more customer transactions with the retailer are provided at a discount.</pat:ClaimText></pat:Claim><pat:Claim com:id="CLM-00011" com:pNumber="00011"><pat:ClaimText>11. Non-transitory computer-readable medium as defined in <pat:ClaimReference com:idrefs="CLM-00008">claim 8</pat:ClaimReference>, wherein the incremental line of credit dispensing module further comprises the instructions of:
<pat:ClaimText>deducting the loaded predetermined increments and the total value of the predetermined loan advance fee from a line of credit balance available associated with the one or more of the plurality of line of credit accounts; and</pat:ClaimText><pat:ClaimText>decreasing a line of credit balance associated with the one or more of the plurality of line of credit accounts by at least the predetermined retailer fee to thereby provide a rebate to one or more of the plurality of customers.</pat:ClaimText></pat:ClaimText></pat:Claim><pat:Claim com:id="CLM-00012" com:pNumber="00012"><pat:ClaimText>12. Non-transitory computer-readable medium as defined in <pat:ClaimReference com:idrefs="CLM-00008">claim 8</pat:ClaimReference>, wherein determining whether to advance funds from the one or more of the plurality of line of credit accounts is responsive to a request to draw funds from the one or more of the plurality of line of credit accounts using an interactive voice response unit; and wherein the financial institution is a first financial institution and one or more of the plurality of customer accounts are managed by a second financial institution different and positioned remote from the first financial institution.</pat:ClaimText></pat:Claim><pat:Claim com:id="CLM-00013" com:pNumber="00013"><pat:ClaimText>13. Non-transitory computer-readable medium defined in <pat:ClaimReference com:idrefs="CLM-00008">claim 8</pat:ClaimReference>, wherein the predetermined retailer fee is paid by the retailer when the loaded predetermined increments are used for the one or more customer transactions with the retailer.</pat:ClaimText></pat:Claim><pat:Claim com:id="CLM-00014" com:pNumber="00014"><pat:ClaimText>14. Non-transitory computer-readable medium as defined in <pat:ClaimReference com:idrefs="CLM-00009">claim 9</pat:ClaimReference>, wherein the determined number of separate predetermined loan increments multiplied by a value of one of the plurality of separate predetermined loan increments plus the value associated with the one or more of the plurality of customer accounts exceeds the value of the one or more customer transactions by less than the value of one of the plurality of separate predetermined loan increments.</pat:ClaimText></pat:Claim><pat:Claim com:id="CLM-00015" com:pNumber="00015"><pat:ClaimText>15. A computer-implemented method to allow a plurality of customer to access a plurality of line of credits associated with a plurality of customer accounts, the computer-implemented method comprising:
<pat:ClaimText>establishing, by a computer associated with a financial institution to define a financial institution computer, responsive to customer underwriting data and predetermined qualification parameters, a plurality of line of credit accounts associated with a plurality of customer accounts for a plurality of customers, the plurality of line of credit accounts having a plurality of total credit limits and adapted to be drawn in at least one of a plurality of separate predetermined loan increments each being equal in value;</pat:ClaimText><pat:ClaimText>determining, by the financial institution computer, whether to advance funds from one or more of the plurality of line of credit accounts to one or more of the plurality of customer accounts for one or more customer transaction;</pat:ClaimText><pat:ClaimText>determining, by the financial institution computer, a number of separate predetermined loan increments to be added to the one or more of the plurality of customer accounts responsive to the determination to advance funds from the one or more of the plurality of line of credit accounts for the one or more customer transactions; and</pat:ClaimText><pat:ClaimText>loading, by the financial institution computer, the one or more of the plurality of customer accounts with at least one of the plurality of separate predetermined loan increments that corresponds with the determined number of separate predetermined loan increments to thereby define loaded predetermined increments when the loaded predetermined increments do not exceed a line of credit balance available for the one or more of the plurality of line of credit accounts, a total value of a predetermined loan advance fee being equal to a predetermined financial institution fee plus a predetermined retailer fee multiplied by the number of separate predetermined loan increments.</pat:ClaimText></pat:ClaimText></pat:Claim><pat:Claim com:id="CLM-00016" com:pNumber="00016"><pat:ClaimText>16. A computer-implemented method as defined in <pat:ClaimReference com:idrefs="CLM-00015">claim 15</pat:ClaimReference>, wherein determining whether to advance funds from the one or more of the plurality of line of credit accounts includes: determining, by the financial institution computer, responsive to receipt of transaction data by the financial institution computer, when one or more customer transaction cards associated with the one or more of the plurality of customer accounts is being used as payment for one or more customer transactions and when a value of the one or more customer transactions is greater than a value associated with the one or more of the plurality of customer accounts.</pat:ClaimText></pat:Claim><pat:Claim com:id="CLM-00017" com:pNumber="00017"><pat:ClaimText>17. A computer-implemented method as defined in <pat:ClaimReference com:idrefs="CLM-00015">claim 15</pat:ClaimReference>, wherein the plurality of total credit limits of the plurality of line of credit accounts have a first portion and a second portion, the first portion being larger than the second portion and reserved for use with one or more transactions with the retailer; and wherein the predetermined retailer fee being a first amount when the one or more customer transactions is with a retailer and a second amount when the one or more customer transactions is not with the retailer, the second amount being larger than the first amount so that advances from the one or more of the plurality of line of credit accounts for one or more customer transactions with the retailer are provided at a discount.</pat:ClaimText></pat:Claim><pat:Claim com:id="CLM-00018" com:pNumber="00018"><pat:ClaimText>18. A computer-implemented method as defined in <pat:ClaimReference com:idrefs="CLM-00015">claim 15</pat:ClaimReference>, wherein determining whether to advance funds from the one or more of the plurality of line of credit accounts is responsive to a request to draw funds from the one or more of the plurality of line of credit accounts using a telephone conversation with an interactive voice response unit; and wherein the financial institution is a first financial institution and one or more of the plurality of customer accounts are managed by a second financial institution different and positioned remote from the first financial institution.</pat:ClaimText></pat:Claim><pat:Claim com:id="CLM-00019" com:pNumber="00019"><pat:ClaimText>19. A computer-implemented method as defined in <pat:ClaimReference com:idrefs="CLM-00015">claim 15</pat:ClaimReference>, wherein the predetermined retailer fee is paid by the retailer when the loaded predetermined increments are used for the one or more customer transactions with the retailer.</pat:ClaimText></pat:Claim><pat:Claim com:id="CLM-00020" com:pNumber="00020"><pat:ClaimText>20. A computer-implemented method as defined in <pat:ClaimReference com:idrefs="CLM-00016">claim 16</pat:ClaimReference>, wherein the determined number of separate predetermined loan increments multiplied by a value of one of the plurality of separate predetermined loan increments plus the value associated with the one or more of the plurality of customer accounts exceeds the value of the one or more customer transactions by less than the value of one of the plurality of separate predetermined loan increments.</pat:ClaimText></pat:Claim></pat:Claims><pat:Abstract com:languageCode="en" pat:dataFormat="original" pat:source="NATIONAL"><com:P com:pNumber="0000">A line of credit optimized for a retailer and attached to a customer account at a financial institution is established for a customer of the retailer. A financial institution computer determines whether to advance funds through the line of credit for a transaction, then advances funds in one or more preselected loan increments to the customer account, up to a total available line of credit for the customer. The financial institution computer decrements the total available line of credit by the amount provided for the customer transaction and by a predetermined customer fee for each of the loan increments. The computer determines a value of a retailer fee to be paid by the retailer, involving a predetermined amount for each of the loan increments. The customer fee amount can be zero or discounted for customer transactions with the retailer. The retailer fee can be a rebate to the customer.</com:P><com:P com:pNumber="00000"><com:Image com:id="EMI-D00000" com:imageContentCategory="Drawing"><com:ImageFormatCategory>TIFF</com:ImageFormatCategory><com:FileName>00000001.tif</com:FileName><com:HeightMeasure com:measureUnitCode="Mm">208.70</com:HeightMeasure><com:WidthMeasure com:measureUnitCode="Mm">174.58</com:WidthMeasure></com:Image></com:P></pat:Abstract><pat:Abstract com:languageCode="en" pat:dataFormat="docdba" pat:source="NATIONAL"><com:P>A line of credit optimized for a retailer and attached to a customer account at a financial institution is established for a customer of the retailer. A financial institution computer determines whether to advance funds through the line of credit for a transaction, then advances funds in one or more preselected loan increments to the customer account, up to a total available line of credit for the customer. The financial institution computer decrements the total available line of credit by the amount provided for the customer transaction and by a predetermined customer fee for each of the loan increments. The computer determines a value of a retailer fee to be paid by the retailer, involving a predetermined amount for each of the loan increments. The customer fee amount can be zero or discounted for customer transactions with the retailer. The retailer fee can be a rebate to the customer.</com:P></pat:Abstract><pat:Drawings com:id="DRAWINGS"><pat:Figure com:id="Fig-EMI-D00001"><pat:FigureNumber>00001</pat:FigureNumber><com:Image com:id="EMI-D00001" com:imageContentCategory="Drawing"><com:ImageFormatCategory>TIFF</com:ImageFormatCategory><com:FileName>00000002.tif</com:FileName><com:HeightMeasure com:measureUnitCode="Mm">208.45</com:HeightMeasure><com:WidthMeasure com:measureUnitCode="Mm">177.04</com:WidthMeasure></com:Image></pat:Figure><pat:Figure com:id="Fig-EMI-D00002"><pat:FigureNumber>00002</pat:FigureNumber><com:Image com:id="EMI-D00002" com:imageContentCategory="Drawing"><com:ImageFormatCategory>TIFF</com:ImageFormatCategory><com:FileName>00000003.tif</com:FileName><com:HeightMeasure com:measureUnitCode="Mm">187.96</com:HeightMeasure><com:WidthMeasure com:measureUnitCode="Mm">179.32</com:WidthMeasure></com:Image></pat:Figure><pat:Figure com:id="Fig-EMI-D00003"><pat:FigureNumber>00003</pat:FigureNumber><com:Image com:id="EMI-D00003" com:imageContentCategory="Drawing"><com:ImageFormatCategory>TIFF</com:ImageFormatCategory><com:FileName>00000004.tif</com:FileName><com:HeightMeasure com:measureUnitCode="Mm">239.01</com:HeightMeasure><com:WidthMeasure com:measureUnitCode="Mm">174.75</com:WidthMeasure></com:Image></pat:Figure><pat:Figure com:id="Fig-EMI-D00004"><pat:FigureNumber>00004</pat:FigureNumber><com:Image com:id="EMI-D00004" com:imageContentCategory="Drawing"><com:ImageFormatCategory>TIFF</com:ImageFormatCategory><com:FileName>00000005.tif</com:FileName><com:HeightMeasure com:measureUnitCode="Mm">279.40</com:HeightMeasure><com:WidthMeasure com:measureUnitCode="Mm">214.38</com:WidthMeasure></com:Image></pat:Figure><pat:Figure com:id="Fig-EMI-D00005"><pat:FigureNumber>00005</pat:FigureNumber><com:Image com:id="EMI-D00005" com:imageContentCategory="Drawing"><com:ImageFormatCategory>TIFF</com:ImageFormatCategory><com:FileName>00000006.tif</com:FileName><com:HeightMeasure com:measureUnitCode="Mm">231.22</com:HeightMeasure><com:WidthMeasure com:measureUnitCode="Mm">177.97</com:WidthMeasure></com:Image></pat:Figure><pat:Figure com:id="Fig-EMI-D00006"><pat:FigureNumber>00006</pat:FigureNumber><com:Image com:id="EMI-D00006" com:imageContentCategory="Drawing"><com:ImageFormatCategory>TIFF</com:ImageFormatCategory><com:FileName>00000007.tif</com:FileName><com:HeightMeasure com:measureUnitCode="Mm">177.55</com:HeightMeasure><com:WidthMeasure com:measureUnitCode="Mm">163.49</com:WidthMeasure></com:Image></pat:Figure><pat:Figure com:id="Fig-EMI-D00007"><pat:FigureNumber>00007</pat:FigureNumber><com:Image com:id="EMI-D00007" com:imageContentCategory="Drawing"><com:ImageFormatCategory>TIFF</com:ImageFormatCategory><com:FileName>00000008.tif</com:FileName><com:HeightMeasure com:measureUnitCode="Mm">234.02</com:HeightMeasure><com:WidthMeasure com:measureUnitCode="Mm">159.34</com:WidthMeasure></com:Image></pat:Figure><pat:Figure com:id="Fig-EMI-D00008"><pat:FigureNumber>00008</pat:FigureNumber><com:Image com:id="EMI-D00008" com:imageContentCategory="Drawing"><com:ImageFormatCategory>TIFF</com:ImageFormatCategory><com:FileName>00000009.tif</com:FileName><com:HeightMeasure com:measureUnitCode="Mm">204.64</com:HeightMeasure><com:WidthMeasure com:measureUnitCode="Mm">180.26</com:WidthMeasure></com:Image></pat:Figure><pat:Figure com:id="Fig-EMI-D00009"><pat:FigureNumber>00009</pat:FigureNumber><com:Image com:id="EMI-D00009" com:imageContentCategory="Drawing"><com:ImageFormatCategory>TIFF</com:ImageFormatCategory><com:FileName>00000010.tif</com:FileName><com:HeightMeasure com:measureUnitCode="Mm">218.10</com:HeightMeasure><com:WidthMeasure com:measureUnitCode="Mm">165.35</com:WidthMeasure></com:Image></pat:Figure><pat:Figure com:id="Fig-EMI-D00010"><pat:FigureNumber>00010</pat:FigureNumber><com:Image com:id="EMI-D00010" com:imageContentCategory="Drawing"><com:ImageFormatCategory>TIFF</com:ImageFormatCategory><com:FileName>00000011.tif</com:FileName><com:HeightMeasure com:measureUnitCode="Mm">212.17</com:HeightMeasure><com:WidthMeasure com:measureUnitCode="Mm">171.11</com:WidthMeasure></com:Image></pat:Figure><pat:Figure com:id="Fig-EMI-D00011"><pat:FigureNumber>00011</pat:FigureNumber><com:Image com:id="EMI-D00011" com:imageContentCategory="Drawing"><com:ImageFormatCategory>TIFF</com:ImageFormatCategory><com:FileName>00000012.tif</com:FileName><com:HeightMeasure com:measureUnitCode="Mm">70.10</com:HeightMeasure><com:WidthMeasure com:measureUnitCode="Mm">168.91</com:WidthMeasure></com:Image></pat:Figure><pat:Figure com:id="Fig-EMI-D00012"><pat:FigureNumber>00012</pat:FigureNumber><com:Image com:id="EMI-D00012" com:imageContentCategory="Drawing"><com:ImageFormatCategory>TIFF</com:ImageFormatCategory><com:FileName>00000013.tif</com:FileName><com:HeightMeasure com:measureUnitCode="Mm">227.16</com:HeightMeasure><com:WidthMeasure com:measureUnitCode="Mm">174.75</com:WidthMeasure></com:Image></pat:Figure></pat:Drawings></pat:PatentPublication>