WO2012151486A2

WO2012151486A2 - System and method of using mobile devices to personalize and issue personalized identification documents

Info

Publication number: WO2012151486A2
Application number: PCT/US2012/036520
Authority: WO
Inventors: Kathleen Phillips; Brian Johnson; Eran KAHANA; Yannick MIAFFO; Christopher Jacques Marie BIEHLMANN
Original assignee: Datacard Corporation
Priority date: 2011-05-04
Filing date: 2012-05-04
Publication date: 2012-11-08
Also published as: WO2012151486A3; WO2012151486A9

Abstract

Systems and methods are described that utilize mobile devices that are provided with applications that allow the user of the mobile device to request a personalized identification document from an issuing entity using the user's mobile device. After the issuing entity receives a request for a personalized identification document from the user, the issuing entity issues the personalized identification document to the user. The use of mobile devices in the personalized identification document issuance process is attractive because of their portability, the versatility of their operating systems, and their relatively long battery life. The use of mobile devices permits extraction of a variety of functions that are not available with the use of laptop computers.

Description

SYSTEM AND METHOD OF USING MOBILE DEVICES TO PERSONALIZE

AND ISSUE PERSONALIZED IDENTIFICATION DOCUMENTS

Field

The use of mobile devices to personalize and issue or reissue personalized identification document is described. Background

It is known to personalize cards such as, but not limited to, credit cards, debit cards, healthcare identification cards, other types of identification cards, gift cards, loyalty cards, and the like, and passports, using machines, for example desktop personalization printers, controlled by laptop computers interfaced to the machines. However, the portability and versatility of laptop computers is limited. In addition, the battery life of laptop computers is often inadequate and in some instances can make them unsuitable for use as control devices for personalization machines.

Summary

Systems and methods are described that utilize mobile devices to issue or reissue personalized identification documents. In one embodiment, the identification documents are real (i.e. tangible) documents that are issued by personalization applications that are configured to personalize the identification documents through interfacing with the mobile device. In another embodiment, the identification documents are virtual identification documents that reside on the mobile device.

The use of mobile devices is attractive because of their portability, the versatility of their operating systems, their growing popularity, and their relatively long battery life. The use of mobile devices permits extraction of a variety of functions that are not available with the use of laptop computers. As used herein, a mobile device is intended to encompass the types of devices that are also referred to as handheld devices, handheld computers or handhelds, and tablet computers. Laptop computers are excluded from the definition of a mobile device used herein, A mobile device typically has a smaller footprint or size as well as lower weight than a laptop computer, and is intended to include the types of devices that one would normally carry around on their person. As of the filing date of this application, examples of mobile devices intended to be included herein include, but are not limited to, tablet computers such as the iPad™, iPad2™ and third generation iPad, and smartphones such as the iPhone™ line of smartphones, and those mobile devices whether tablet computers or smartphones using the Android¹"' operating system. These examples are intended to be illustrative and not exhaustive. Other mobile devices in existence at the time of filing this application, and mobile devices developed after the filing date of this application, are intended to be encompassed with the definition of mobile devices, as long as they have size, power consumption and functionalities comparable to the examples listed above.

A mobile device as used herein is also intended to encompass a device that is specifically designed for use in the described systems and methods and which is designed to have data capture functionalities comparable to commercially available mobile devices such as tablet computers and smartphones.

The functionalities of mobile devices that are useful in the systems and methods described herein can include, but are not limited to, one or more of the following: web browsing capability, near field communication (NFC), radio frequency identification (RFID), WiFi, Bluetooth™, cameras for picture taking and/or video conferencing, microphones for audio pick-up, data storage, and USB or other technology for direct wired interfacing with one or more peripheral devices.

As used herein, a personalized identification document includes, but is not limited to, a card or a passport. Identification documents contemplated herein often include, but do not require, one or more of personal information of an intended user of the document, information such as, but is not limited to, an account number that is linked or assigned to the intended user in a database, a requested monetary value, the user's name and/or picture, and other data that can be provided by a user that is input via the mobile device. Cards include tangible plastic or composite cards, often times generally rectangular in shape and having nominal ID-l card dimensions of 2.125 x 3.370 inches. However, other card shapes, sizes and materials can be used. Cards also include virtual cards that can have functionalities that are similar to real cards, but which reside on the mobile device.

Examples of cards that can be personalized include, but are not limited to, credit cards, identification cards such as driver's licenses and other government authorized cards, healthcare cards or work place identification cards or badges, loyalty cards, debit cards, gift cards, and facility access cards (such as, but not limited to, amusement parks). Passports include passports and identification booklets and other types of ID3-sized booklets. In the case of tangible documents, the secure identification document can include one or more of a magnetic stripe and/or an integrated circuit chip for data storage, printing (direct and/or indirect)- thereon via conventional ink or dye based printing techniques and/or using a laser, embossing, and other forms of personalization. A personalized document such as a card excludes a paper document that is printed on a general purpose printer connected to a personal computer or the like.

A virtual identification document, since it resides on the mobile device, can also be considered to have data storage such as the data storage on the mobile device. The virtual identification document can function as a contactless identification document, such as a contactless card, where the card functions via proximity to a reader device. The virtual identification document could also function more similarly to a traditional identification document, such as a traditional credit card, where visual access to an image of the virtual card displayed on the mobile device is required in order to provide visual access to one or more features of the card, such as a photograph, an account number, a signature, a bar code, or the like, is required in order to use the virtual document.

In the case of a real identification document, personalization as used herein includes, but is not limited to, one or more of magnetic stripe programming, integrated circuit chip programming, printing (direct and/or indirect) via conventional ink or dye based printing techniques such as thermal printing, inkjet, or reverse transfer printing and/or printing using a laser, embossing, and indent printing in the case of tangible documents. A machine that performs one or more these personalization tasks is referred to herein as a personalization device.

In the case of a virtual identification document residing on the mobile device, personalization as used herein includes, but is not limited to, storing data necessary to use the virtual card on a storage device of the mobile device, or adding various types of personal data mentioned below to an image of the identification document on the display of the mobile device.

Personalization includes, but is not limited to, adding personal data to the document, such as the name, address, family member names and other family member information, social security number, a photograph of the document user or one or more photographs selected by the document user, account number and/or other data that is personal, assigned to or unique to the intended user of the document, and the like.

Personalization is also intended to include adding non-personal data to a document, such as increasing a monetary value assigned to the card, adding/removing permissions, and other non-personal data.

As used herein, to issue a personalized document includes taking a new unpersonalized document, adding personalization to it, and providing it to the user for use by the user. To issue a personalized document also includes taking an identification document that already contains some existing personalization, adding personalization to the existing identification document, such as, but not limited to, increasing a monetary value stored in the card, and re-issuing the document for use by the user. Therefore, issuing includes issuing new personalized documents and re-issuing existing personalized documents after updating the personalization. To issue a personalized document also includes creating a virtual personalized document on a user's mobile device after approving the user's request for a virtual personalized document.

In one embodiment, a method of issuance of a personalized identification document to a user includes an issuing entity providing an application to the user that the user is able to load onto the user's mobile device, the application permitting the user to request a personalized identification document from the issuing entity using the user's mobile device. The issuing entity can be the entity that controls or is operating a mechanical personalization device that personalizes a real document, or an entity with authority to issue a virtual document. After the issuing entity receives a request for a personalized identification document from the user, the issuing entity issues the personalized identification document to the user.

In an embodiment, a system for issuing personalized identification documents includes a personalization device configured to perform one or more personalization operations on an identification document, and a mobile device that is configured to interface with the personalization device to request the issuance of the personalized identification document.

In an embodiment, the mobile device can interface directly with the

personalization device via a wired connection, for example a USB cable, or wirelessly via WiFi, Bluetooth or other form of wireless connection.

In an embodiment, the mobile device can interface indirectly with the

personalization device via a server using the application that is installed on the mobile device. In such a case, the mobile device is in suitable communication with a server which in turn is in communication with the personalization device.

In another embodiment, a method of issuance of a personalized identification document to a user using a document personalization device includes configuring the document personalization device to permit interfacing with a mobile device, receiving at least one command and/or user data at the document personalization device from the mobile device via the interface, based on the received at least one command and/or user data, personalizing the identification document using the document personalization device, and once the identification document is personalized, issuing the personalized identification document from the document personalization device.

The mobile device can be the user's own mobile device, and the received at least one command and/or user data can be entered into the user's mobile device by the user.

In addition, the personalized identification document can be personalized and issued to the user while the user is present at the document personalization device.

Alternatively, the personalization and issuance can occur while the user is not present at the document personalization device. In addition, the at least one command and/or user data can be entered into the user's mobile device by the user while the user is present at the document personalization device or while the user is remote from the document personalization device.

In one embodiment, the document personalization device receives at least one command and user data from the mobile device. The user data can be, but is not limited to, the data discussed in the preceding paragraphs. The command can be, but is not limited to, a command to begin personalization and issuance, or a command by the user to see available card design options.

The application can be provided to the user that the user is able to load onto the user's mobile device, where the application permits interfacing between the user's mobile device and the issuing entity. The application can be provided by the issuing entity, by the entity that owns or controls the card personalization device, by a third party unrelated to either the mobile device owner or the card personalization device owner, or by any other entity. The application can permit indirect interfacing between the user's mobile device and the personalization device via a server. Alternatively, the application can permit direct interfacing between the user's mobile device and the personalization device if the personalization device is WiFi-enab ed or otherwise equipped for direct

communications with the mobile device. The application can also permit creation of a virtual card that resides on the user's mobile device.

The application on the user's mobile device can provide a number of user interface capabilities. Examples of user interface capabilities include, but are not limited to, data entry and capture that allow a user to enter or capture data on the mobile device, such as taking a photograph using a camera on the mobile device; data and/or image processing such as allowing the user to modify an image; various print options including, for example, printing a test document from a file that is stored on the personalization device or on the mobile device, printing a file(s) stored on the mobile device, and canceling all or select print jobs; and settings control allowing a user to retrieve and/or change information relating to the personalization device and/or supplies installed in the personalization device, or allowing a user to adjust settings on the personalization device. In another embodiment, a system for issuing a personalized identification document for a user includes a personalization device configured to perform one or more personalization operations on the identification document, and a mobile device that is configured to interface with the personalization device to request the issuance of the personalized identification document.

Drawings

Figure 1 illustrates a first embodiment of an exemplary system that utilizes a mobile device interfaced with a personalization device to personalize and issue a secure identification document.

Figure 2 is a schematic depiction of some of the capabilities that a mobile device used in the system of Figure 1 can have.

Figure 3 illustrates a mobile device with an application installed thereon that permits interfacing between the user's mobile device and the document personalization device.

Figure 4 illustrates an example of a home screen for the application in Figure 3.

Figure 5 illustrates an exemplary menu structure for the application in Figure 4.

Figure 6 illustrates an example of a workflow involved in another embodiment of a system and method that creates a virtual identification document that resides on the mobile device.

Figure 7 is a screen shot of an exemplary virtual identification document displayed on a mobile device.

Figure 8 is a screen shot of a user interface on the mobile device that displays the virtual identification documents on the mobile device.

Detailed Description

With reference to Figure 1 , a system 1 0 is illustrated that includes a mobile device 12 and a document personalization device 14 controlled or authorized by an issuing entity. The mobile device 12 is used by a user to interface, directly or indirectly via a server 16, with the personalization device 14 to personalize a real or tangible identification document such as, but not limited to, a card or a passport. In locations where power supply is unavailable or is limited, a battery pack 18 can be provided to power the personalization device 14.

The mobile device 12 can have a number of functionalities that are necessary to perform the intended personalization function(s). The functionalities may be an integral part of the mobile device in the out-of-box version thereof, or they may need to be added to the mobile device, for example in the form of an application. An example of such an application includes, but is not limited to, an iOS-based banking application that allows a user to print their debit or credit card or increase a monetary stored value at an ATM equipped with such a personalization device. Applications running on other operating systems could be used as well including, but not limited to, Android™ and Windows.

Figure 2 depicts some exemplary capabilities that the mobile device 12 can have in order to implement personalization on an identification document. For example, the mobile device 12 can have a user interface 20 specifically designed for the user to enter at least some data and/or allow the user to access web pages on the server 16. The user interface 20 can, for example, permit full character entry for entering data such as names, addresses, monetary values, and the like. The user interface 20 may also permit the user to select a photograph that is stored in an internal or external memory (such as, but not limited to a remote server) or to take a photograph using a camera built into the mobile device. The user interface 20 may also permit entry of biometric data, such as a user fingerprint, using a biometric capture device either connected to the mobile device, such as by a USB cable, or run directly on the mobile device using a suitable application. If the identification document is to be personalized with audio, the user interface 20 can allow the user to capture audio using a microphone built into the mobile device.

The amount and type of data entry using the user interface 20 can vary depending upon, for example, whether or not the mobile device is directly connected to the personalization device 14 or indirectly connected via the server 16, the type of

identification document being personalized, and the field of use of the system 10. For example, for personalizing an identification card, the user interface 20 may permit entry of name, address, photograph and biometric data. For a gift card, the user interface 20 may only permit entry of a monetary value and/or, depending on the merchant, the addition of a personal photograph.

The mobile device 12 may also include a personalization device interface 22 capability, for example via a web service client, preferably without using printer drivers. The interface 22 would be necessary if the mobile device 12 will interface directly with the personalization device.

In addition, the mobile device 12 can include a suitable form of communications protocol for communicating with the personalization device 14 or with the server 16. The mobile device 12 can include NFC, RFID, WiFi, Bluetooth™, Secure Sockets Layer (SSL), or other suitable wireless communications technology for direct wireless communications with the personalization device 14 which would have similar wireless communication capability built-in. In the case of direct wired communication with the personalization device 14, the mobile device can have a USB port or other wired interface for direct tethering to the personalization device.

If the mobile device 12 is to communicate indirectly with the personalization device 14 via the server 16, the mobile device 12 should have a web browser 24 for interfacing with the server via the internet or a suitable application that renders use of a web browser 24 unnecessary, for example an iOS-based or other operating system based banking application.

In one embodiment, the personalization device 14 can be provided with a docking station to permit the mobile device 12 to physically dock onto the personalization device. This would permit, for example, data to be entered into the mobile device by a user, with the mobile device then being docked with the personalization device to download the entered data to the personalization device. The docking station could be integrated onto the personalization device or can be a separate docking station that is connected to the personalization device such as by a USB cable.

Depending upon the field of use, the data being transmitted from and to the mobile device 12 may be confidential. Therefore, the mobile device can also have secure data transmission 26 capability such as data encryption/decryption. The mobile device 12 may also have data storage 28. In one implementation, the data storage 28 can store data entered into the mobile device. In another implementation, the data storage is a secure data storage that stores data for use in authenticating data entered into the mobile device. For example, the data storage can store a list of names and other information indicating individuals authorized to receive a document personalized by the personalization device. When the individual's name or other data is entered into the mobile device, that data is checked against the stored data as part of an authorization process to determine whether or not it is proper to personalize an identification document for that individual.

In instances where there is a fee associated with personalizing the identification document and/or the identification document has a stored monetary value, the mobile device 12 may also have electronic funds transfer 30 capability to allow for payment.

Many of the functionalities discussed above are already implemented in existing mobile devices or can be easily implemented using suitably designed applications. For example, existing mobile devices have significant data capture capabilities including full character entry capability and cameras, web browsers, significant data storage, WiFi, USB ports, and the like, making them suitable for implementation in document personalization systems and methods.

The mobile device 12 can be any one of the mobile devices that are currently readily available to consumers including handheld devices, handheld computers or handhelds, and tablet computers. Laptop computers are excluded from the definition of a mobile device used herein. Specific non-limiting examples of mobile devices include, but are not limited to, tablet computers such as the iPad™ and iPad2^1M, and smartphones such as the iPhone™, and those mobile devices whether tablet computers or smartphones using the Android™ operating system. Other mobile devices, including those developed after the filing date of this application, are intended to be encompassed with the definition of mobile devices used herein, as long as they have size, power and functionalities comparable to or better than the mobile device examples listed above. A mobile device can also be a device that is specifically designed for use in the described systems and methods, which is not intended to be readily available to consumers or the general population, and which is designed to have size, power and functionalities comparable to or better than mobile devices that are intended for consumers such as tablet computers and smartphones.

With reference to Figures 3-5, an example of an application that can be loaded onto a user's mobile device for interfacing with the personalization device 14 via the server 16 is illustrated. In the illustrated example, the application is based on the

Android™ operating system. However, this is an example only, and the application could be based on other operating systems such as, but not limited to, iOS or Windows.

Figure 3 illustrates the mobile device 12 displaying a plurality of icons for various applications installed on the mobile device, including an application 50 called

PrintManager that permits interfacing between the mobile device 12 and the document personalization device 14 via the server 16.

Figure 4 illustrates an example of a home screen 52 for the application 50 once the application is launched in the appropriate manner. In this example, the home screen 52 displays the name of the application, as well as a number of menu selections 54, 56, 58. In this example, the menu selections include a Settings 54 menu selection, a Data Capture 56 menu selection, and a Print Card 58 menu selection. These particular menu selections 54, 56, 58, and the following described menu structures, are exemplary only and intended to help explain possible functionalities of the application 50. Other and/or additional menu selections and menu structures can be provided.

Figure 5 illustrates an exemplary menu structure for the various menu selections 54, 56, 58 that are available for selection by the user. For example, in the Settings 54 menu selection, a plurality of submenus can be provided that allow a user to retrieve and/or change information relating to the personalization device and/or supplies installed in the personalization device, or allowing a user to adjust settings on the personalization device. Although the Settings 54 menu selection may be visible to all users, only an administrator or other authorized personnel would be able to utilize the Settings 54 menu via entry of a password or the like. For example, one submenu can be a "Printer

Discovery" submenu 54a that allows the user to retrieve and display on the mobile device information that is unique to the personalization device such as the name of the manufacturer of the personalization device, the model, the serial number, an authorization key, and the version of the firmware currently installed in the printer. In addition, another submenu can be a "Supplies" submenu 54b that allows the user to retrieve information describing the type of supplies installed in the personalization device, as well as some indicator of the amount of supplies left in the printer that could be used to perform successful personalization tasks. The Setting 54 menu could also allow a user to update or adjust certain settings on the personalization device, such as YMC Power, KPower, registration and vertical offsets in the case of a card printer.

With respect to the Data Capture 56 menu selection, one submenu can be a "Get image" submenu 56a that, when selected, turns on a camera of the mobile device, allows the user to capture an image using the camera; and saves the image on the mobile device. Another submenu can be a "Design Card" submenu 56b that, when selected, allows the user to load an image that is saved on the mobile device, and optionally permitting the user to perform image processing on the loaded image, for example adding effects to the image or adding text. The submenu 56b can also permit data entry by the user, such as entering the user's name or a message, using data entry techniques available on the mobile device, such as user keys.

The use of a mobile device with an application for card design and controlling the personalization device permits a number of new functionalities. For example, a business office can have a personalization device and all the employees in the office could then print their identification document using an application loaded onto their mobile device. In another example, people away from their office without direct access to their personalization device could personalize an identification document while away from the office using their mobile device.

With respect to the Print Card 58 menu selection, one submenu can be a "Print

Test Pattern Card" submenu 58a that, when selected, prints a template document using the personalization device from a file that is stored on the personalization device or on the mobile device. Another submenu can be a "Print From File" submenu 58b that, when selected, prints a file(s) stored on the mobile device. The file can be one of the files resulting from the Get Image 56a or the Design Card 56b submenus. Another submenu can be a "Cancel All Print Jobs" submenu 58c that, when selected, permits the user to cancel all or select print jobs.

The system can be used to personalize any type or size of identification documents such as a card (typically plastic) or a passport. Identification cards include, but are not limited to, plastic or composite cards, often times generally rectangular in shape and having nominal ID-1 card dimensions of 2.125 x 3.370 inches. However, other card shapes, sizes and materials can be used. Examples of identification cards include, but are not limited to, credit cards, identification cards such as driver's licenses, healthcare cards or work place identification cards or badges, loyalty cards, debit cards, and gift cards, embossed cards, flat (i.e. un-embossed) cards, card with or without magnetic stripes, cards with or without programmable chips, facility access cards (such as, but not limited to, amusement parks), etc. Passports include, but arc not limited to, passports and identification booklets and other types of ID3-sized or other sized booklets. The identification document can include one or more of a magnetic stripe and/or an integrated circuit chip for data storage, printing (direct and/or indirect) thereon via conventional ink or dye based printing techniques and/or using a laser, embossing, and other forms of personalization. A personalized identification document as used herein excludes a paper document that is printed on a general purpose printer connected to a personal computer or the like.

The identification document can be personalized to include one or more of personal information of an intended user of the document such as, but not limited to, the person's name and address, information such as an account number that is linked or assigned to the intended user in a database, a monetary value, and other data provided by a user that is input via the mobile device. Personalization includes, but is not limited to, one or more of magnetic stripe programming, integrated circuit chip programming, printing (direct and/or indirect) via conventional ink, inkjet, or dye based printing techniques such as thermal printing or reverse transfer printing and/or printing using a laser, embossing, and indent printing.

Personalization includes adding personal data to the document, such as an individual's name, address, family member names and other family member information, social security number, a photograph of the document user or a photograph selected by the document user, account number and/or other data that is personal, assigned to or unique to the intended user of the document. Personalization is also intended to include adding non-personal data to a document, such as adding or increasing a monetary value assigned to the card, adding/removing permissions, and other non-personal data.

The personalization device 14 can be designed to perform one or more these personalization tasks on an identification document. In one embodiment, the

personalization device is a type of device commonly referred to as a desktop card printer. Examples of suitable desktop card printers currently include the CD or SD series desktop card printers available from DataCard Corporation of Minnetonka, Minnesota.

The personalization device 14 personalizes a document and issues the document. Issuing a personalized document includes taking a new document, adding personalization to it, and discharging it immediately to the user for use. Issuing a personalized document also includes taking an already existing personalized document that is input into the personalization device 14, adding personalization to the existing document, such as increasing a monetary value stored in the card, and re-issuing the card immediately for use by the user.

In one embodiment, the system includes the mobile device 12, the personalization device 14 which is a desktop card printer that issues personalized cards, and optionally the battery pack 18 for powering the desktop card printer if no power supply is available or power is unpredictable or limited where the desktop card printer is to be used. In this embodiment, data to be applied to the card is entered into the mobile device 12 via the user interface 20. The data is transmitted to the desktop card printer 14 which

personalizes the card with the data, such as by printing on the card or programming a magnetic stripe or a chip on the card. Once personalization is complete, the card is discharged from the device 14 and given to the intended card holder. This embodiment can be used in a number of applications including, for example, issuance of credentials in the field where power supply is limited, unpredictable or non-existent, such as in a developing country or in a location in the aftermath of a natural disaster. In another embodiment suitable for a retail store environment, a user uses his mobile device to interface with a personalization device installed in a retail location. For example, when a user walks into the retail store and the WiFi of the user's mobile device is enabled, the mobile device can automatically synch with the WiFi of the retail store. Alternatively, the user can log onto the WiFi of the retail store. The retailer can then query the user through the user's mobile device whether the user would like to receive a retailer credit card (i.e. financial card instant issuance at the retail level), a gift card or other personalized card while the user is in the store. The retailer can also serve up web pages to the user showing various card designs and card types available for selection by the user. Alternatively, a user may already have the retailer's application installed in their mobile device. This renders serving up web pages by the retailer unnecessary and offers more efficient interface and possibilities with the personalization device. The user can then use his mobile device to request a desired type of personalized card and if necessary enter appropriate data and/or a photograph for adding to the card. The request is transmitted to the personalization device installed in the retail store to issue the card. Where the user already has a credit card with the retailer, the retailer may already have access to the user's personal information and can use the information they have access to in order to personalize a new card for the user, minimizing the user's data entry or negating any user data entry. In the case of gift cards, the user may be asked to enter a desired monetary value or the user could be offered a selection of available monetary values to choose from. Further, payment for the gift card or other personalized card could be made using electronic funds transfer or via use of a retailer credit card held by the user.

In another embodiment, a user uses his mobile device in a bank setting to instantly issue a credit card, i.e. financial card instant issuance at a bank level. In this embodiment, the mobile device can function similarly to the terminal described in US Patent 7806338 or used in the CardWizard^® instant issuance system from DataCard Corporation of Minnetonka, Minnesota. A user with a suitable mobile device walks into a participating bank location and uses his mobile device to enter suitable data. The data is transmitted to a server which in turn is in communication with a card management system to approve, if necessary, the issuance of a credit card to the user. Upon receiving approval, a card printer at the bank location then personalizes the credit card and issues a credit card to the user while the user waits.

In another embodiment, the mobile device 12 must be recognized by the personalization device 14 so that the personalization device only works with the recognized mobile device and/or the personalization device provides enhanced functionality when used with a recognized mobile device compared to use with a non- recognized mobile device, and vice versa so that the mobile device only works with a recognized personalization device. Such recognition can be accomplished using X.509 or SSL certificate technology, by requiring a particular key or password sent with each data packet between the mobile device and the personalization device, or by other recognition means. If there is a match in certificates, keys or other recognition technology, the personalization device is enabled to perform a personalization function or the mobile device is enabled to process data received from the personalization device. If there is no match, the mobile device and/or the personalization device can be disabled or either could perform with lesser functionality.

In another embodiment, the mobile device with installed application acts as a command interpreter between customers and a kiosk. The application provides the ability to communicate with a server for authentication and validation of the customers and customer credentials before proceeding with the transaction at the kiosk containing the personalization device. For example, airports could have kiosks to instantly create customized credit or debit cards where a customer could use their own image and text on the card. This would permit customers to instantly print a new or lost credit or debit card on the go without having to stop at a bank.

In another embodiment, some mobile devices have the ability to create wireless hot spots. In the event that the personalization device has wireless capability, a user could personalize a document from almost any location with phone services. For example, the user can create a hot spot using their smart phone. The personalization device detects and connects to the hot spot. The application on the user's phone is setup to communicate with the IP address of the personalization device. The user then personalizes a document using the application.

In another embodiment, where the mobile device directly interfaces with the personalization device, the personalization device is loaded with a plurality of card design options available to the user which are presented to the user via the mobile device for selection.

In another embodiment, where the mobile device indirectly interfaces with the personalization device via the server, the server is loaded with a plurality of card design options available to the user which are presented to the user via the mobile device for selection. Alternatively, the personalization device is loaded with the card design options which are presented to the user via the server.

Another embodiment is illustrated in Figures 6 and 7. In this embodiment, rather than issuing a real or tangible document, the document that is issued is a virtual card or other document that resides on the user's mobile device. With reference to Figure 6, the cardholder makes a request 90 to an issuer 100 to download an application for loading onto the user's mobile device 12. The issuer 100 is the issuing entity that is responsible for or authorized to issue the personalized document. Examples of issuing entities include, but are not limited to, a bank or bank branch location, a governmental authority such as a local, state or federal government entity, or a hospital. The request can be made by the user by any suitable means including, but not limited to, using the mobile device's web browser to access the issuer's website or another website.

Assuming the issuer 100 approves the request, the issuer 100 permits the cardholder to download and install the application onto the user's mobile device. The issuer 100 can send the cardholder information, such as a web address or a link, directing the cardholder to where the application can be downloaded, including any log in and/or password that may be necessary. This information can be provided by the issuer 100 to the cardholder in any suitable manner, including but not limited to, verbally directly to the user, using a SMS text message, an e-mail, a voice message, a letter, or the like.

Regardless of how the cardholder is notified, the cardholder is able to download and install the application on their mobile device. Once the application is downloaded and installed, the cardholder can make a card or other document request 1 10. The request is sent from the cardholder's mobile device to a server 1 12 via the issuer 100. The server 1 12 performs an eligibility verification check 1 14 to determine if the cardholder is eligible to receive the virtual card. To perform the verification check, the server 1 12 can utilize a user ID and password that are entered by the cardholder so that the server knows who is making the request. The eligibility verification check 1 14 can be based on any suitable criteria currently used in the industry to determine whether a person is eligible to receive a credit card or other type of identification document. For example, eligibility can be based on the cardholder's credit score and/or income level. The server 1 12 can be affiliated with the issuer 100 or it can be a server controlled by a separate entity that the issuer has access to.

If the eligibility verification determines that the cardholder is approved, a signal is sent to the user's mobile device 12. The signal automatically enables a card process that is part of the installed application. The signal can be sent by any suitable means such as SMS text message, an e-mail, or other means.

The card process that is enabled is part of the installed application. For example, the installed application can include a "blank", encrypted virtual card format that is initially inactive, invisible and inaccessible to the cardholder. The signal sent to the user's mobile device can decrypt and activate the virtual card format so that the cardholder can now see the virtual card on the display screen of the user's mobile device. At this point, the virtual card residing on the mobile device is now ready to be

personalized and a card personalization process 120 is executed.

The card personalization process 120 includes the cardholder sending a card personalization request 122 from the mobile device to the server 1 12. The request 122 can be triggered by, for example, a menu selection button that is displayed to the user on the user's mobile device. To send the request, the user must enter their user ID and password to interact with their account features. However, the user ID and password could have been previously entered by the user, such as during the request 1 10.

When the server receives the request 122, the server performs a credential verification 124 to determine that the request 122 is from the correct cardholder. The verification 124 can include checking the cardholder's name, entered by the user using the mobile device or otherwise forwarded by the mobile device, against the account, and/or by checking other cardholder information against the account.

If the credential verification passes, the server sends an enable card signal back to the mobile device which authorizes the virtual card to be personalized. The type of personalization that occurs depends upon how the virtual card is to be used. In one embodiment, the virtual card functions essentially as a contactless card, whereby the mobile device itself essentially forms the card body. In this contactless card

embodiment, the enable signal can program a chip in the mobile device, such as, but not limited to, a microSD chip, a SIM card or other hardware on the mobile device. The programming of the chip permits the mobile device to function as a contactless card by bringing the mobile device into proximity to a suitable reader which reads the chip. In this contactless card embodiment, display of a card image on the mobile device is optional. If displayed, the displayed card image can be an image of a personalized card personalized with cardholder data.

In another embodiment of the virtual card, the virtual card must be displayed on the mobile device for visual reading by a human or a machine. In this case, the virtual card functions more like a traditional card, where visual access is required in order to provide visual access to one or more features of the card, such as a photograph, an account number, a signature, a bar code, or the like. In this embodiment, the displayed virtual card can be automatically populated with cardholder data, which can be forwarded by the server, already resident on the mobile device, and/or entered by the cardholder.

Figure 7 is a screen shot of an exemplary virtual identification document 150 displayed on a mobile device. In this example, the virtual identification document 150 is displayed in the form of a traditional credit card that displays the cardholder's name, the account number, the card expiration date, and other graphic data found on typical tangible credit cards. In addition, the mobile device can also display a scrolling arrangement 152 of all of the virtual cards that are available on the mobile device. For example, in addition to the credit card, the mobile device can contain other virtual identification documents such as, but not limited to, a debit card, a prepaid card, a driver's license, a school identification card, and the like. The virtual card that is displayed in the primary display of the mobile device can be selected by the user using his finger to tap the appropriate virtual card in the scrolling arrangement 152. The selected virtual card is then enlarged and displayed in the primary display area, replacing the previously displayed card.

Figure 8 is a screen shot of a user interface on the mobile device that displays the various virtual identification documents that are available on the mobile device in a vertical list, and allows the user to select one of the virtual identification documents for deletion by tapping the appropriate radio button at the right, as well as begin the process of adding a new virtual card by tapping the area at the base of the screen.

Any combination of the embodiments described herein, utilizing any combination of data to be added to the document and any combination of data entered by a user via the mobile device, any combination of mobile device functionalities, any combination of personalization and any combination of personalization devices, can be used and are intended to be included in this patent application.

The embodiments disclosed in this application are to be considered in all respects as illustrative and not limitative. The scope of the claimed invention is indicated by the appended claims rather than by the foregoing description; and all changes which come within the meaning and range of equivalency of the claims are intended to be embraced therein.

Claims

1. A method of issuance of a personalized identification document to a user, comprising:

an issuing entity making available an application to the user that the user is able to load onto the user's mobile device, the application permitting the user to request a personalized identification document from the issuing entity using the user's mobile device; and

after the issuing entity receives a request for a personalized identification document from the user, the issuing entity issuing the personalized identification document to the user.

2. The method of claim 1 , wherein the personalized identification document is real and is personalized by a document personalization device.

3. The method of claim 1 , wherein the personalized identification document is virtual and resides on the user's mobile device.

4. The method of claim 2, further comprising:

configuring the document personalization device to permit interfacing with the mobile device via an interface;

receiving at least one command and/or user data at the document personalization device from the mobile device via the interface;

based on the received at least one command and/or user data, personalizing the identification document using the document personalization device; and

once the identification document is personalized, issuing the personalized identification document from the document personalization device.

5. The method of claim 4, wherein the interface is a direct interface with the document personalization device.

6. The method of claim 4, wherein the interface is an indirect interface with the document personalization device via a server.

7. The method of claim 6, wherein the application permits interfacing between the user's mobile device and the document personalization device via the server.

8. The method of claim 1 , wherein the application:

allows the user to capture data using the mobile device that is to be added to the identification document; and

allows the user to send a personalization command.

9. The method of claim 8, wherein the application:

allows the user to store the captured data on the mobile device and allows the user to personalize the identification document using data from a data file stored on the mobile device.

10. The method of claim 1 , wherein the application is iOS-based, Android™ based, Windows based, or other functionally similar mobile operating system,

1 1. The method of claim 1 , wherein the application is made available to the user from an application store.

12. The method of claim 3, wherein the virtual personalized identification document is enabled on the user's mobile device after an eligibility verification and credential verification performed by a server in communication with the issuing entity.

13. The method of any one of claims 1 to 12, wherein the personalized identification document is a card, and the mobile device is a smartphone or a tablet computer.

14. The method of claim 2, wherein the document personalization device is a card printer that is loaded with a plurality of card design options that can be presented to the user via the mobile device for selection.

15. A system for issuing a personalized identification document to a user, comprising:

an issuing entity that is authorized to issue the personalized identification document to the user; and

an application suitable for installing onto a mobile device of the user, the application permitting the user to request issuance of the personalized identification document from the issuing entity using the user's mobile device.

16. The system of claim 15, wherein the personalized identification document is a real or virtual card, and the application is suitable for installation onto a smartphone or a tablet computer.

17. The system of claim 15, wherein the application:

allows the user to capture data using the mobile device that is to be added to the identification document, and

allows the user to send a personalization command to the issuing entity.

18. The system of claim 17, wherein the application:

19. The system of claim 15, wherein the application is iOS-based, Android™ based, Windows based, or other functionally similar mobile operating system.