EP2223275A1 - Système et procédés de capture de signature électronique dans des transactions de contrat électronique - Google Patents

Système et procédés de capture de signature électronique dans des transactions de contrat électronique

Info

Publication number
EP2223275A1
EP2223275A1 EP08731261A EP08731261A EP2223275A1 EP 2223275 A1 EP2223275 A1 EP 2223275A1 EP 08731261 A EP08731261 A EP 08731261A EP 08731261 A EP08731261 A EP 08731261A EP 2223275 A1 EP2223275 A1 EP 2223275A1
Authority
EP
European Patent Office
Prior art keywords
signature
contract
holographic
contracting
signatures
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
EP08731261A
Other languages
German (de)
English (en)
Other versions
EP2223275A4 (fr
Inventor
T.N. Sumramaniam
Mark Leonard
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Routeone LLC
Original Assignee
Routeone LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US12/002,016 external-priority patent/US20080243662A1/en
Application filed by Routeone LLC filed Critical Routeone LLC
Priority claimed from US12/041,010 external-priority patent/US8626622B2/en
Publication of EP2223275A1 publication Critical patent/EP2223275A1/fr
Publication of EP2223275A4 publication Critical patent/EP2223275A4/fr
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02—Banking, e.g. interest calculation or account maintenance
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/166—Editing, e.g. inserting or deleting
    • G06F40/174—Form filling; Merging
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • G06Q50/18—Legal services

Definitions

  • the present invention relates generally to a system and method for electronic contracting, and more particularly, electronic contracting in indirect financing transactions.
  • Computer-implemented systems and methods for electronic contracting in indirect financing transactions described herein provide an improved e-contracting environment in which a customer may acquire an asset (such as, for example, an automobile) from a dealer or other vendor with financing for the transaction provided by an independent finance source.
  • an asset such as, for example, an automobile
  • Fig. 1 is a schematic diagram illustrating one example embodiment of a system for implementing financing transactions in connection with an acquisition of an asset such as an automobile;
  • Fig. 2 is a schematic diagram illustrating one example embodiment of a database for a credit aggregation management system
  • Figs. 3A, B and C are schematic diagrams illustrating one example embodiment of a signature capture device and message format for communication of signature information
  • Fig. 4 is a flow diagrams illustrating one example embodiment of a process of electronic contracting
  • Fig. 5 is a flow diagram illustrating one example embodiment of a process of contract execution.
  • Fig. 6 is a schematic diagrams illustrating one example embodiment of data structures for storing an electronic contract.
  • the components, process steps, and/or data structures described herein may be implemented using various types of operating systems, computing platforms, computer programs, and/or general purpose machines.
  • devices of a less general purpose nature such as hardwired devices, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), or the like, may also be used without departing from the scope and spirit of the inventive concepts disclosed herein.
  • a method comprising a series of process steps is implemented by a computer or a machine and those process steps can be stored as a series of instructions readable by the machine, they may be stored on a tangible medium such as a computer memory device (e.g., ROM (Read Only Memory), PROM (Programmable Read Only Memory), EEPROM (Electrically Eraseable Programmable Read Only Memory), FLASH Memory, Jump Drive, and the like), magnetic storage medium (e.g., tape, magnetic disk drive, and the like), optical storage medium (e.g., CD-ROM, DVD-ROM, paper card, paper tape and the like) and other types of program memory.
  • ROM Read Only Memory
  • PROM Programmable Read Only Memory
  • EEPROM Electrically Eraseable Programmable Read Only Memory
  • FLASH Memory Jump Drive
  • magnetic storage medium e.g., tape, magnetic disk drive, and the like
  • optical storage medium e.g., CD-ROM, DVD-ROM, paper card, paper tape and the like
  • the illustrative embodiments described herein in connection with the drawing figures relate to system and methods for facilitating electronic contracting in the context of indirect financing transactions, such as buying or leasing an automobile offered for sale or lease by an automobile dealership with financing provided by one or more independent finance sources.
  • the financing may be direct whereby the dealer may act as a finance source when the dealer provides financing for the transaction.
  • example embodiments described herein are not limited to such automobile retail environments and automobile vehicle financing applications, but may be implemented in myriad other commercial transaction environments and asset financing transactions, including both unsecured and secured credit applications and financing.
  • a financing transaction may be a lease transaction, a loan transaction, or any other transaction in which a finance source provides financing for a party to obtain use of, and possibly also legal title to, an asset, which asset includes, for example, one or more items such as automobiles (e.g., cars, trucks, and the like), marine, recreational vehicles (RV), aircraft, motorcycles, off-road vehicles, consumer goods, real estate, contract rights, intangible property rights, home furnishings, home improvement, office equipment, inventory, manufacturing equipment, livestock, farm equipment, financial interests, and so on.
  • automobiles e.g., cars, trucks, and the like
  • RV recreational vehicles
  • acquisition used in connection with an asset (e.g., an "asset acquisition” or “acquiring an asset”) may involve a purchase (i.e., buying or a corresponding sale) or a lease of the asset, and thus a financing transaction relating to an acquisition may be a lease transaction, a loan transaction, or any other transaction in which a finance source provides financing for a party to obtain use of, and possibly also legal title to, the asset.
  • a financing transaction relating to an acquisition may be a lease transaction, a loan transaction, or any other transaction in which a finance source provides financing for a party to obtain use of, and possibly also legal title to, the asset.
  • a dealer is not limited to an automobile dealer, but is any individual or entity (e.g., commercial dealership, third party brokers, vendors, retailers, and manufacturers) in the business of selling or leasing assets, including merchandise, to customers, and in doing so may communicate with lenders as well as customers.
  • an individual or entity e.g., commercial dealership, third party brokers, vendors, retailers, and manufacturers
  • lenders may communicate with lenders as well as customers.
  • a contract may be a document prepared in connection with a transaction for the purchase or financing of a vehicle offered for sale by the dealer with financing provided by a finance source.
  • the contract may include a plurality of document each having various contact provisions, information describing the customer, information describing an automobile, information describing a financing program, and a plurality of signature fields.
  • the contract may be considered executed when it is signed by all contracting parties at the appropriate signature fields.
  • the contract may be executed (e.g., signed) by the customer and the dealer, and then transferred (e.g., assigned) by the dealer to the finance source.
  • the contract may be executed by the customer, the dealer and the finance source. Once executed, the contract becomes a legal instrument that binds the contracting parties to the contract provisions contained therein.
  • the contract may be generated in an electronic form
  • the electronic contract may be created as a text document, postscript document, image file or other type of electronic document.
  • the printed copy of the electronic contract may be executed in the following manner.
  • a paper copy of the contract may be signed by the contracting parties, the signature may be scanned by a signature capture device and appended to the electronic version of the contract (i.e., electronic contract), as will be described in a greater detail hereinbelow.
  • an electronic signature pad may be used to sign an electronic version of the contract and the captured electronic signature may be appended to the electronic contract.
  • the captured image of a handwritten signature will be referred to herein as a holographic or electronic signature.
  • each captured holographic signature may include signature identification information, such as a contract identifier and a signature identifier.
  • the contract identifier may be a unique number used to associate the captured signature to a specific electronic contract.
  • the signature identifier may be a unique number used to associate the captured signature with a particular signature field within the specific electronic contract.
  • the contract and signature identifiers may be assigned to each newly generated contract.
  • contract and signature identifiers may be embedded into the electronic contract.
  • the contract identifier may be placed into the margin of the contract and the signature identifiers may be placed into or next to the associated signature fields.
  • the contract and signature identifiers may be embedded into the contract document as unique dot patterns, barcodes, numeric sequences and the like, which may be captured by the signature capture device during contract execution.
  • a special digital paper may be used to print contract documents.
  • Digital paper is patterned paper used in conjunction with a signature capture devices, such as a digital pen, to create handwritten digital documents.
  • the printed dot pattern uniquely identifies the position coordinates on the paper.
  • a digital paper having Anoto dot pattern may used, such paper is manufactured by a Swidish company Anoto Group AB.
  • the Anoto pattern can be printed onto almost any paper, using a standard printing process of at least 600 dpi resolution and carbon-based black ink or the like.
  • the one or more unique dot patterns printed on the paper may be associated with a contract identifier and/or signature identifiers for purpose of identification of captured holographic signatures.
  • the signature caputer device may be used to take photo images of the dot pattern within a signature field and identify location of the captured signature. The location coordinates may then be correlated to the corresponding signature identifier.
  • the captured hologrpahic signature may be associated with a particular electronic contract and, more specifically, with a particular signature field within the contract.
  • Fig. 1 depicts one example embodiment of a system for implementing financing transactions in connection with an acquisition of an asset such as an automobile.
  • System 100 includes automobile dealership computer systems 102a, 102b, 102c, finance source (FS) systems 104a, 104b, 104c, and a credit management system (CMS) 108.
  • Communications between the various dealerships 102, FS systems 104 and CMS system 108 are provided via network 105, which may include any configuration of private and/or public communication networks, packet switched local area networks (LAN) and wide area networks (WAN).
  • network 105 includes the Internet or a data communications network providing similar functionality.
  • FS systems 104 provide processing platforms for processing credit applications for financing (e.g., loans and/or leases) an automobile being offered for sale by a dealer to a customer.
  • financing e.g., loans and/or leases
  • Examples of finance sources include Lexus Financial Bank ® , BMW Financial Services, General Motors Acceptance Corporation (GMAC ® ) Financial Services and others.
  • GMAC ® General Motors Acceptance Corporation
  • Embodiments of the present invention are not limited to such automobile retail environments and automobile vehicle financing applications, but may be implemented in myriad other commercial transaction environments and asset financing transactions, including both unsecured and secured credit applications and financing.
  • a finance source (also referred to herein as a lender) may be considered as any entity providing financing for asset (e.g., automobiles in an example embodiment of Fig. 1) transactions, e.g., banks and credit unions, manufacturer-related financing companies, financial institutions, and other credit granting institutions.
  • asset e.g., automobiles in an example embodiment of Fig. 1
  • transactions e.g., banks and credit unions, manufacturer-related financing companies, financial institutions, and other credit granting institutions.
  • dealerships 102 may be independent automobile dealerships (e.g., separately owned businesses) and, as schematically depicted, each including a computer network comprising one or more computer devices 103 communicably coupled to a Dealer Management System (DMS) 101, which may be operating on one or more servers on the dealership's computer network.
  • DMS Dealer Management System
  • the illustrative dealership computer devices 103 are not limited to personal computers, terminals, or workstations, nor limited to wired network connections within the dealership, but may include any computing device that may communicably connect (e.g., wirelessly; via a WAN, via a virtual private network (VPN) connection, via the Internet, etc.; via one or more hardware devices, such as routers, switches, hubs, etc.; and using any of a variety of communication protocols; etc.) to the Dealer Management System 101.
  • any computing device may communicably connect (e.g., wirelessly; via a WAN, via a virtual private network (VPN) connection, via the Internet, etc.; via one or more hardware devices, such as routers, switches, hubs, etc.; and using any of a variety of communication protocols; etc.) to the Dealer Management System 101.
  • VPN virtual private network
  • a typical DMS 101 e.g., such as provided by
  • ADP, Inc. or Reynolds and Reynolds, Inc. stores and manages dealership data such as that related to inventory, sales, parts, service, customers, etc.
  • the DMS 101 allows salespersons, management, and other authorized users to access stored dealership data.
  • a salesperson may access DMS 101 via a computer device (e.g., 103a) to determine whether the dealership has a certain vehicle in its existing inventory.
  • a dealer assisting a customer in arranging for financing to complete the automobile transaction may use a dealership computer 103 to access the DMS 101 to acquire vehicle information (and possibly also information for a return customer), and may also access (e.g., navigating via a web browser) Credit Management System (CMS) 108 (e.g., which may be a web-based application) to arrange for financing of the vehicle from finance sources 104.
  • CMS Credit Management System
  • the credit management system comprises one or more computer servers connected to the communication network 105.
  • CMS system 108 may be provided by an independent application service provider (ASP), though in various embodiments such a system may be provided, for example, by one or more affiliated dealers.
  • CMS 108 is operable to assist automobile dealers in obtaining automobile financing for customers from disparate finance sources 104.
  • CMS 108 maintains secure, separate accounts for each independent dealership participant (e.g., subscriber) of the credit management system, which automobile dealer may access via communication network 105 (e.g., via a secure (e.g., encrypted) communication link).
  • CMS computer system 108 is depicted as a computer server 108, generally, CMS 108 may be implemented as, or be part of, a multi-server environment having access to multiple databases to provide such a platform (e.g., including geographically dispersed servers to provide service to geographically dispersed dealers).
  • a platform e.g., including geographically dispersed servers to provide service to geographically dispersed dealers.
  • CMS 108 comprises a credit aggregation management system (CAMS) 110 and a database 114 in accordance with one example embodiment.
  • CAMS 110 may be implemented as a web-based application, providing independent dealerships (e.g. 102a, 102b, 102c) a common platform for electronically submitting automobile financing applications to one or more finance sources (e.g., finance sources 104a, 104b, 104c) with which they do business.
  • finance sources 104a, 104b, 104c e.g., finance sources 104a, 104b, 104c
  • CAMS 110 is illustrated as being hosted by the web server 108, system 110 may reside in other locations in the system 100.
  • one or more of these modules, or portions thereof may be incorporated into a dealership's local DMS (e.g., DMS 101a). Additionally, in various embodiments, DMS 101, or portions thereof, may be implemented as a web-based service, similar to CMS 108, and in some implementations such a web-based DMS system, or portions thereof, may be bundled or included with, or otherwise operate as part of, the web-based CMS 108. In short, the particular details of the system 100 may vary depending upon the particular application or embodiment thereof. [0024] In one example embodiment, CAMS 110 facilitates collection of information about available automobile financing programs from FS systems 104. Fig.
  • FS profiles 210 are schematic diagram illustrating one example embodiment of a database 114 for a credit aggregation management system 110.
  • the collected information may be stored in the finance source (FS) profiles 210.
  • finance source profile information stored in FS profiles 210 may include, but is not limited to, application worksheets 202, which may include applicant worksheets for collecting personal information about the customer and deal worksheets for collecting financial information and vehicle information.
  • FS profiles 210 may also include financing programs information 206, which may include information on the term of available loan and lease programs, including their amortization and interest rates and other financial information.
  • FS profiles 210 may also store supplemental forms 208, which may include retail loan agreements, lease agreements and other financial forms, that may be provided to the customer in connection with the financing of the vehicle.
  • FS profiles 210 may also include various application validation rules 212, which may be used to check validity of application data entered by the dealer before it is being submitted to the finance source for approval.
  • FS profiles 210 may also include contract templates 204, which are used to generate electronic contracts based on approved credit application data.
  • contract templates 204 which are used to generate electronic contracts based on approved credit application data.
  • CAMS database 114 further includes an e-contract vault 220 according to one example embodiment.
  • Vault 220 is configured to store a plurality of electronic contract packages 222.
  • Each package may include the original electronic contract 224, supplemental forms 232 and various ancillary documents 234, such as co-buyers agreement, insurance verification, service contract, GAP waiver, odometer statement, vehicle title, after market products and state-specific forms and others.
  • Each electronic contract 224 may include a text document, postscript document, image file or other type of electronic document.
  • each electronic contract 224 may include one or more holographic signatures 228, which indicate execution of the contract by the contracting parties.
  • the holographic signatures 228 may include customer signature, dealers signature and finance source representative's signature.
  • a holographic signature 228 may be a photo image of the original signature captured during contract execution by the signature capture devices 115, as will be described in a greater detail hereinbelow.
  • Each holographic signature 228 may include signature information (not shown) associating each signature to one or more signature fields within the contract 226. Such information may include a signature identifier associated with one or more signature fields.
  • each e-contract package 222 may be signed with a digital signature to indicate authenticity of the contents of each EC package 222.
  • a digital signature is data that binds a user's identity to the information being stored.
  • a digital signature may be bundled with any message, file, or other digitally encoded information, or transmitted separately.
  • Digital signatures are used in public key environments and provide authentication and integrity services.
  • a digital certificate is a digitally signed statement that contains information about an entity and the entity's public key, thus binding these two pieces of information together.
  • a certificate may be issued by a trusted organization (or entity) called a certification authority (CA) after the CA has verified that the entity is who it says it is. Certificates can contain different types of data.
  • CA certification authority
  • CMS 108 can include the format of the certificate, the serial number of the certificate, the algorithm used to sign the certificate, the name of the CA that issued the certificate, the name and public key of the entity requesting the certificate, and the CA's signature.
  • CMS 108 may use an independent digital certificate vendor, such as VeriSign Inc. or a similar vendor, to issue the certificates used in storage of electronic contracts.
  • CAMS 110 further comprises an e-contracting application 1 12, which includes program logic for facilitating electronic creation of credit applications, execution of e-contracts based on applications approved by finance sources 104, and storage and maintenance of executed e-contracts in e-contract vault 220 in the database 1 14.
  • E-contracting application 112 may be implemented as an internal software component of CAMS 110, though as will be understood by those skilled in the art, the e-contracting functionality may be provided as a separate application running on the same or different server as the CAMS 110.
  • e-contracting application 112 may have a user interface, such as a HTML-based graphical user interfaces, accessible to the dealers and finance source representatives through the communication network 105.
  • the interfaces facilitate execution of various electronic contracts.
  • e-contracting application 112 may be configured to communicate with the signature capture devices 115 to facilitate collection of signature related information, as will be described in a greater detail hereinbelow. Operation of the e-contracting application 112 will be described hereinbelow with reference to Figs. 4, 5 and 6.
  • the system 100 further includes a plurality of electronic signature capture devices 115 in accordance with one example embodiment. As depicted in Fig. 1, signature capture devices 115 may be provided to the dealers and finance sources or other parties involved in execution of the vehicle financing contracts.
  • Signature capture devices 1 15 may be connected to the dealers' PCs and may be used to capture both the customers' and the dealers' electronic holographic signatures during execution of printed contract documents or electronic contracts.
  • Signature capture devices 115 may be also configured to capture signature related information, such as contract identifier and one or more signature identifiers embedded in the printed contract documents, as will be described in a greater detail hereinbelow.
  • Signature capture devices 115 are may be configured to transmit the captured signature information to the e-contracting application 112 through the communication network 105.
  • capture devices 115 may include digital pens, such as AutoPen ® manufactured by Coin Data LLC of Norcross, Georgia.
  • the signature capture device may include a handwriting signature pad, such as signature pads manufactured by Coin Data LLC.
  • Device 300 includes a writing instrument 310, such as a digital pen, and a pen base unit 320.
  • digital pen 310 may include a base unit interface 311, such as a Bluetooth interface, USB interface or other types of wireless, wired or contact- type data transfer device.
  • Digital pen 310 may further include a status indicator 312, which may use different color LEDs or an LCD display to indicate the status of the pen, such as charging, capturing data, transferring data, low battery, or other status indicators.
  • Pen 310 may further include a capture control 313, which indicates when to initiated and/or terminated image capture.
  • the capture control 313 may be a pressure sensor, which detects when the tip of the pen is in contact with the item being signed.
  • capture control 313 may be a button activated by the pen user.
  • Digital pen 310 may also include an ink cartridge 314, such as a ballpoint type ink cartridge.
  • pen 310 may also includes a camera 315 for capturing signature images, i.e., holographic signatures, of the signing parties as well as signature related information.
  • the camera 315 may be a charge-coupled device (CCD) camera, a CMOS imager or other type of image capture device.
  • Digital pen 310 may further include a processor 316, such as a microcontroller, a field programmable gate arrays (FPGAs), an application specific integrated circuit (ASIC) or the like.
  • Processor 316 is configured to control the capture and processing of digital images, transfer of captured images to the base unit 320 through interface 311, operation of the status indicators 312 and other functions of the pen.
  • Digital pen 310 further includes a memory 317 for storing captured signature images and signature-related data, such contract and signature identifiers.
  • the capture images may be stored in a JPEG, GIF, Windows bitmap or other file formats.
  • Memory 317 may include Flash memory or other types of electrically erasable programmable read only memory (EEPROM).
  • Pen 310 may also include a rechargeable battery 318, such as a lithium battery, for powering various electronic components of the pen. Battery 318 may be recharged when the pen is docked in base unit 320.
  • Digital pen 310 may include other components known to those of skill in the art. [0031]
  • Fig. 3B depicts one example embodiment of the base unit 320 of the digital pen
  • Base unit 320 is configured to house the digital pen 310 when the pen is not in use and to provide communication between the digital pen and dealer's or finance source's PC.
  • base unit 320 includes a charger 321, which recharges the battery 318 of the digital pen 310.
  • Base unit 320 may also include a pen interface 322 configured to communicate with interface 311 of the digital pen 310.
  • interface 322 may be a Bluetooth interface, USB interface or other types of wireless, wired or contact-type data transfer device.
  • Base unit 320 may also include a processor 323 configured to control various components of the base unit 320 and retrieve captured signature related information from the memory 317 of the digital pen 310. Processor 323 may store the retrieved signature information in memory 324.
  • Base unit 320 also includes a network interface, such as an Ethernet, WiFi or other type of wired or wireless network interface, which facilitates transfer of data from base unit 320 to dealer's or finance source's PC, and, in particular, to the instance of e-contracting application 112 running on the computer to which base unit 320 is connected.
  • a network interface such as an Ethernet, WiFi or other type of wired or wireless network interface, which facilitates transfer of data from base unit 320 to dealer's or finance source's PC, and, in particular, to the instance of e-contracting application 112 running on the computer to which base unit 320 is connected.
  • Fig. 3C depicts one example embodiment of the message format used to transfer data between base unit 320 and e-contracting component 112 in CAMS 110.
  • the data may be transferred using XML-based message over a TCP/IP connection established between base unit 320 and e-contracting application 112 running on CAMS 110.
  • the message may include a plurality of data fields, which include, but are not limited to, contract identifier 331, holographic signature_l image 332, signature_l identifier 333, holographic signature_2 image 334, signature_2 identifier 335 and other data fields.
  • the format and content of the messages may vary based on application requirements, system configuration, network protocol specification and other factors know to those of skill in the art.
  • messages 330 may be encrypted using known symmetric or asymmetric encryption techniques, such as block cipher, public key encryption or other techniques.
  • the e-contracting component 112 may be configured to decrypt the received messages 330, retrieve signature information contained therein and process the retrieved information as will be described below.
  • Fig. 4 depict one example embodiment of a process for electronic contracting in indirect financing transactions in which a customer may acquire an asset (such as, for example, an automobile) from a dealer or other vendor with financing for the transaction provided by an independent finance source.
  • e-contracting application 112 generates an electronic contract for vehicle financing.
  • e-contracting application 112 may assign a unique contract identifier to the newly created contract. This contract identifier may be used to identify and properly route the data in all communications and messaging that may occur between CMS 108, dealership computer systems 102 and finance source systems 104 in connection with execution of this electronic contract.
  • e-contracting application 112 may store a newly created (unexecuted) contract in a contract vault 220, step 410.
  • a structure for storing a newly created e-contract is depicted in Fig. 6.
  • data structure 600 may include an e-contract 405 and a plurality of signature blocks 610-630, where holographic signatures of contracting parties may be inserted once the contract is executed.
  • an e-contract 605 is first created in the contract vault 220 it may be secured with a digital signature 640, as will be described in a greater detail herein below.
  • e-contracting application 112 may assign a transaction number or other identifier to each new contract created in contract vault 220.
  • the transaction number or other identifier may be used as the primary key in storing contract documents in the contract vault 220.
  • the transaction number may be the same as contract identifier described above.
  • embodiment the transaction may be different from the contract identifier
  • e-contracting application 112 may generate an EC Package by systematically merging the electronic contract with various supplemental forms and ancillary documents, step 415.
  • Each finance source may be responsible for creating its own supplemental forms and ancillary documents and ensuring that each is accurate and compliant with all applicable local, state and federal laws and regulations.
  • E-contracting application 1 12 may access these forms from FS profiles 210. For each applicable deal type, the finance source may identify the contract forms and other supplemental forms to be used.
  • the deal type may be determined based on the six deal type parameters selected by the dealer: finance source, application type (e.g., individual, individual with co-buyer), transaction type (e.g., retail), product type (e.g., simple interest, actuarial), state, and sale class (e.g., new, used).
  • the supplemental forms may be customized based on the collected customer data, such as with the customer's name , address etc.
  • Each contract form may explicitly indicate that the customer is agreeing to conduct the transaction electronically and agreeing to use electronic records and electronic signatures to document the contract.
  • the dealer may also ask the customer to provide various ancillary documents, which may then be faxed or transmitted to CMS 108 using mail or other means. The received documents are then appended to e-contract.
  • e-contracting application 112 may provide the dealer with a copy of the EC package documents for review and execution by the contracting parties, step 420.
  • e- contracting application 112 may extract from the contract vault 220 and/or FS profiles 210 a copy of the forms and documents making up the EC package 222.
  • E-contracting application 112 may render each document and present it to the dealer in the electronic form.
  • the dealer may then print all documents constituting the EC package 222, including the electronic contract 224, supplemental forms 232 and ancillary documents 234.
  • e-contracting application 112 may embed the contract identifier and various signature identifiers into the contract document and other documents and forms.
  • the contract identifier may be placed into the margin of the contract and the signature identifiers may be placed into or next to the associated signature fields.
  • the contract and signature identifiers may be embedded into the contract document as unique dot patterns, barcodes, numeric sequences or in other graphic or numeric formats.
  • e-contracting application 112 is configured to collect captured holographic signatures of the contracting parties, so that they can be appended to the electronic contract stored in the in the vault 220, step 425.
  • e-contracting application 112 may use signature identification information, such as contract identifier and signature identifiers, provided along with the holographic signatures to associate each holographic signature to the pre-designated line on the e-contract in the vault 220.
  • the signatures may be affixed in such a way that the date and time of each signature capture, as well as the authenticity of each unique signature is embedded in the e-contract.
  • e-contracting application 1 12 may update the electronic contract from a signatures-in-process status to an Authoritative Copy (AC).
  • AC Authoritative Copy
  • the dealer may assign and distribute the electronic contract to the finance source, step 430.
  • the dealer may invoke the "Assign Contract” function provided by e-contracting application 112.
  • the system will display the finance source as the assignee to which the contract will be sent, and state that by clicking the "Assign” button the dealer is assigning the contract to the finance source under the terms and conditions of the dealer agreement governing such assignments.
  • the e-contracting application will enable the "Distribute" function to the dealer.
  • the offer and acceptance of such assignment shall be affected electronically and recorded by the e- contracting application 112.
  • the ownership logs will be updated and the finance source will become the assignee of record.
  • E-contracting application 112 may then permanently seal the electronic contract using a designated digital certificate that is reserved solely for signing the Authoritative Copy of a contract, step 435. The presence of this digital certificate, as obtainable through the digital signature, will identify it as the Authoritative Copy.
  • the e-contracting application 112 may update contract ownership logs (not depicted) with the dealer ownership information.
  • E-contracting application 112 may enable the dealer to print the entire signed electronic contract package once all required signatures have been affixed thereto.
  • the printed contract documents may be marked in the margin(s) as a non-authoritative copy. It is the dealer's responsibility to ensure that the customer is provided with a printed copy of the signed EC package before leaving the dealership.
  • Fig. 5 depicts one example embodiment of a process for contract execution.
  • the dealer may initiate the contract execution process by retrieving a copy of the EC package from the contract vault via user interface of the e-contracting application. The dealer may then print all documents in the EC package and provide them to the customer for review, step 505.
  • the contract may be printed on a digital paper, as described above.
  • contract identification information such as contract identifier and one or more signature identifiers, may be embedded in the designated locations in the printed contract document.
  • the contract identifier may be placed in the margin of the contract and the signature identifiers may be placed into or next to the associated signature fields.
  • the contract and signature identifiers may be embedded into the contract document as unique dot patterns, barcodes or numeric sequences.
  • the dealer may then provide a signature capture device to the customer, step 510.
  • the signature capture device may be a digital pen.
  • the pen When the user uses the pen to sign paper copy of the contract, the pen is configured to capture a handwritten signature of the contracting party, step 515.
  • the digital pen may take one or more digital photographs of the handwritten signature and save them as a holographic signature.
  • the signature field also includes a signature identifier embedded therein in the form of a dot pattern, barcode or numeric sequence, the digital pen also captures the image of the embedded signature identifier and stores it along with the corresponding holographic signature, step 520.
  • the pen may be used to capture contract identifier, which may be located in a margin of the document or as a barcode to be scanned by the pen.
  • the pen may record the date and time when the signature was captured.
  • the pen may be configured to captures signature location information encoded in the printed dot pattern.
  • the captured location information may be associated with appropriate contract and signature identifiers.
  • the captured holographic signatures and signature identification information may be transferred to the e-contracting application for processing, step 525.
  • the e-contracting application uses signature identification information, and, in particular, the captured contract identifier to locate in the contract vault an electronic contract associated with the captured holographic signatures. Once such contract is located, the e-contracting application determines based on the signature identifiers, which captured holographic signatures are associated with which contract signature fields, step 530. Once signature/field associations are established, the e-contracting application may append captured holographic signatures of contracting parties to the e-contract document in the EC package in the contract vault, step 535.
  • Systems and modules described herein may comprise software, firmware, hardware, or any combination(s) of software, firmware, or hardware suitable for the purposes described herein.
  • Software and other modules may reside on servers, workstations, personal computers, computerized tablets, PDAs, and other devices suitable for the purposes described herein.
  • Software and other modules may be accessible via local memory, via a network, via a browser or other application in an ASP context, or via other means suitable for the purposes described herein.
  • Data structures described herein may comprise computer files, variables, programming arrays, programming structures, or any electronic information storage schemes or methods, or any combinations thereof, suitable for the purposes described herein.
  • User interface elements described herein may comprise elements from graphical user interfaces, command line interfaces, and other interfaces suitable for the purposes described herein. Except to the extent necessary or inherent in the processes themselves, no particular order to steps or stages of methods or processes described in this disclosure, including the Figures, is implied. In many cases the order of process steps may be varied, and various illustrative steps may be combined, altered, or omitted, without changing the purpose, effect or import of the methods described.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Physics & Mathematics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Finance (AREA)
  • General Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Human Resources & Organizations (AREA)
  • Tourism & Hospitality (AREA)
  • Health & Medical Sciences (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Health & Medical Sciences (AREA)
  • Development Economics (AREA)
  • Technology Law (AREA)
  • Operations Research (AREA)
  • Data Mining & Analysis (AREA)
  • Primary Health Care (AREA)
  • Quality & Reliability (AREA)
  • Artificial Intelligence (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • Computational Linguistics (AREA)
  • General Engineering & Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention porte sur un système et sur un procédé pour générer, exécuter et maintenir des contrats électroniques en liaison avec des transactions de financement indirect, mettant en jeu une acquisition par un client d'un actif offert par un vendeur avec un financement fourni par une source financière indépendante. Dans un mode de réalisation à titre d'exemple, le système comprend un composant de contrat électronique configuré pour générer un contrat électronique ayant un ou plusieurs champs de signature. Le contrat comprend également un identifiant de contrat et un ou plusieurs identifiants de signature intégrés dans celui-ci. Le composant de contrat électronique fournit le contrat électronique généré à une ou plusieurs parties contractantes, comprenant le client, le vendeur et les sources de financement. Le système comprend également un dispositif de capture de signature holographique configuré pour capturer une ou plusieurs signatures holographiques indiquant l'exécution du contrat par les parties contractantes. Le dispositif de capture, s'il est en outre configuré pour, transmet les informations de signature capturées au composant de contrat électronique.
EP08731261A 2007-12-14 2008-03-03 Système et procédés de capture de signature électronique dans des transactions de contrat électronique Ceased EP2223275A4 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US12/002,016 US20080243662A1 (en) 2007-03-30 2007-12-14 System and method for electronic contracting
US12/041,010 US8626622B2 (en) 2007-12-14 2008-03-03 System and methods for electronic signature capture in e-contracting transactions
PCT/US2008/055673 WO2009079023A1 (fr) 2007-12-14 2008-03-03 Système et procédés de capture de signature électronique dans des transactions de contrat électronique

Publications (2)

Publication Number Publication Date
EP2223275A1 true EP2223275A1 (fr) 2010-09-01
EP2223275A4 EP2223275A4 (fr) 2012-08-22

Family

ID=40754506

Family Applications (1)

Application Number Title Priority Date Filing Date
EP08731261A Ceased EP2223275A4 (fr) 2007-12-14 2008-03-03 Système et procédés de capture de signature électronique dans des transactions de contrat électronique

Country Status (7)

Country Link
EP (1) EP2223275A4 (fr)
CN (1) CN101903901B (fr)
AU (1) AU2008338916B2 (fr)
CA (1) CA2710208A1 (fr)
MX (1) MX2010006349A (fr)
NZ (1) NZ586128A (fr)
WO (1) WO2009079023A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104486351A (zh) * 2014-12-24 2015-04-01 昆山百润科技有限公司 支持多人对同一份文件签章的客户端、服务器及处理方法

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102930425B (zh) * 2012-11-02 2016-08-31 姚远 远程合约同步签署系统
CN106940846A (zh) * 2016-01-04 2017-07-11 阿里巴巴集团控股有限公司 电子签约的实现方法和装置
CN106127082B (zh) * 2016-06-13 2019-03-15 点击律(上海)网络科技有限公司 一种在线合同生成方法和系统
CN106295405B (zh) * 2016-07-25 2019-02-12 飞天诚信科技股份有限公司 一种订立电子合同的方法及服务器
CN108876362A (zh) * 2017-05-15 2018-11-23 上海策赢网络科技有限公司 一种虚拟资源分配方法及装置
CN109801060A (zh) * 2018-12-14 2019-05-24 平安普惠企业管理有限公司 还款分流方法、电子装置、计算机设备及存储介质
CN111325520B (zh) * 2020-01-21 2023-10-31 江西才气软件技术有限公司 一种房产交易各环节监管方法
CN111832264B (zh) * 2020-06-02 2023-09-15 深圳价值在线信息科技股份有限公司 基于pdf文件的签名位置确定方法、装置及设备
US11822877B2 (en) * 2021-11-01 2023-11-21 LawHQ, LLC Intelligent electronic signature platform

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005010731A2 (fr) * 2003-07-31 2005-02-03 Dealertrack, Inc. Systeme et procede electroniques integres de demande de credit, de passation de marche et de titrisation
WO2006010737A2 (fr) * 2004-07-30 2006-02-02 Hewlett-Packard Development Company, L.P. Procedes, appareil et logiciel permettant de valider des saisies effectuees sur un formulaire
US20060209044A1 (en) * 2005-03-18 2006-09-21 Searete Llc, A Limited Liability Corporation Of The State Of Delaware Forms for completion with an electronic writing device

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6250549B1 (en) * 1998-06-17 2001-06-26 Defabio, Jr. Daniel J. Method for authenticating signatures and memorabilia kit employing same
JP3853528B2 (ja) * 1998-11-12 2006-12-06 日本電気株式会社 認証管理システム及び認証管理方法
US20020152086A1 (en) * 2001-02-15 2002-10-17 Smith Ned M. Method and apparatus for controlling a lifecycle of an electronic contract
US7775428B2 (en) * 2005-05-06 2010-08-17 Berkun Kenneth A Systems and methods for generating, reading and transferring identifiers

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005010731A2 (fr) * 2003-07-31 2005-02-03 Dealertrack, Inc. Systeme et procede electroniques integres de demande de credit, de passation de marche et de titrisation
WO2006010737A2 (fr) * 2004-07-30 2006-02-02 Hewlett-Packard Development Company, L.P. Procedes, appareil et logiciel permettant de valider des saisies effectuees sur un formulaire
US20060209044A1 (en) * 2005-03-18 2006-09-21 Searete Llc, A Limited Liability Corporation Of The State Of Delaware Forms for completion with an electronic writing device

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
GUIMBRETIÈRE F: "Paper Augmented Digital Documents", INTERNET CITATION, 2 November 2003 (2003-11-02), pages 51-60, XP007905358, Retrieved from the Internet: URL:http://delivery.acm.org/10.1145/970000/964702/p51-guimbretiere.pdf?key1=964702&key2=4070957121&coll=GUIDE&dl=GUIDE&CFID=39106926&CFTOKEN=48365048 [retrieved on 2008-08-01] *
See also references of WO2009079023A1 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104486351A (zh) * 2014-12-24 2015-04-01 昆山百润科技有限公司 支持多人对同一份文件签章的客户端、服务器及处理方法

Also Published As

Publication number Publication date
CN101903901B (zh) 2014-06-11
AU2008338916A2 (en) 2010-11-11
AU2008338916A1 (en) 2009-06-25
CA2710208A1 (fr) 2009-06-25
CN101903901A (zh) 2010-12-01
EP2223275A4 (fr) 2012-08-22
AU2008338916B2 (en) 2012-06-07
MX2010006349A (es) 2010-08-23
NZ586128A (en) 2013-06-28
WO2009079023A1 (fr) 2009-06-25

Similar Documents

Publication Publication Date Title
US8626622B2 (en) System and methods for electronic signature capture in e-contracting transactions
AU2008338916B2 (en) System and methods for electronic signature capture in e-contracting transactions
US10733273B2 (en) Dynamic digital consent
US20080243662A1 (en) System and method for electronic contracting
US20200013073A1 (en) Systems and methods for using codes and images within a blockchain
CA2849152C (fr) Systeme et methode de creation, d'entreposage, de transfert et de controle d'enregistrements electroniques transferables a propriete unique
US8307218B2 (en) System and method for creating, vaulting, transferring and controlling transferable electronic records with unique ownership
WO2000029973A1 (fr) Systeme et procede electronique de non repudiation
US20080235038A1 (en) Method, system and computer program for enabling live sales support
EP1141859A1 (fr) Systeme pour negociations iteratives a plusieurs variables sur un reseau
US20070244798A1 (en) Systems and methods for real estate process management
CN101510288A (zh) 一种基于数字物权证的电子合同运营系统
KR102166690B1 (ko) 전자문서를 위한 전자서명 관리서버 및 관리방법
WO2023201360A2 (fr) Procédé, contrôleur et support lisible par ordinateur permettant le remplacement d'une structure de données de transfert à répétition annulée sur un réseau de transfert distribué
US11636494B2 (en) Classic car restoration services systems and methods
JP2009042986A (ja) 金融商品勧誘販売経歴管理システム、金融商品勧誘販売経歴管理方法及び金融商品勧誘販売経歴管理プログラム
CN114049124A (zh) 数据处理方法、装置、计算机设备、存储介质和程序产品
JP2005122370A (ja) 記録システム、記録サーバ、及びプログラム
US20240289908A1 (en) System and method for identification document verification
JP2006318054A (ja) 電子委任状生成装置及び電子委任状生成方法
JP2005011135A (ja) 電子取引支援装置、電子取引支援方法、電子取引支援プログラム及びそのプログラムを記録した記録媒体
JP2003208464A (ja) 電子貿易業務の運用方法およびシステム

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20100714

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MT NL NO PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA MK RS

RIN1 Information on inventor provided before grant (corrected)

Inventor name: LEONARD, MARK

Inventor name: SUBRAMANIAM, T.N.

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: ROUTEONE LLC

DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20120719

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 17/24 20060101ALI20120713BHEP

Ipc: G06Q 40/00 20120101AFI20120713BHEP

17Q First examination report despatched

Effective date: 20140110

REG Reference to a national code

Ref country code: DE

Ref legal event code: R003

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20180210