WO2025072029A1

WO2025072029A1 - Digital identification verification systems and methods

Info

Publication number: WO2025072029A1
Application number: PCT/US2024/047432
Authority: WO
Inventors: Nicholas Kenneth John TRISTRAM
Original assignee: Verifone Inc
Current assignee: Verifone Inc
Priority date: 2023-09-29
Filing date: 2024-09-19
Publication date: 2025-04-03
Anticipated expiration: 2026-03-29

Abstract

The present disclosure is directed to systems and methods for verifying the identity (e.g., identification information) of one or more individuals using a payment device like a point-of-sale (POS) payment terminal. As described herein, the systems and methods utilize a registration process that connects identification information of the individuals to a corresponding payment card, such that a zero-value transaction may be used to verify the identities of the individuals. As a result, a bank, merchant, or other entity can reliably identify customers while eliminating the need for the customer to provide multiple means of identification beyond their payment card.

Description

DIGITAL IDENTIFICATION VERIFICATION SYSTEMS AND METHODS

Cross-Reference to Related Applications

[0001] This application claims priority to U.S. Provisional Patent Application Serial No. 63/586,534, filed on September 29, 2023, and titled “Digital Identification Verification Systems and Methods,” the disclosure of which is herein incorporated by reference in its entirety.

Field of the Disclosure

[0002] The present disclosure relates generally to digital identification verification, and more specifically to systems and methods for verifying the identity of an individual using a payment device.

Background

[0003] While performing certain financial transactions, a bank or merchant may require verification of the customer’s identity before completing the purchase or operation. For example, if an individual attempts to make changes to a banking account, making a large purchase, or taking out a loan, the bank or merchant may require the individual to correctly answer certain security questions or to provide some identification before proceeding. In certain cases, the customer may also be required to provide a specific type of identification (e.g., a photo-ID card, passport, driver’s license, etc.) and/or provide additional information, such as their permanent address. However, verifying the customer’s identity can be a challenge and often requires the customer to possess specific forms of physical identification. This can be especially challenging in situations where there is a lack of standardized identification (e.g., in countries where residents do not have a government-issued identification card).

Summary of the Disclosure

[0004] According to an embodiment of the present disclosure, a payment device configured to digitally verify an identity of a customer is provided. The payment device can include: a payment data reader configured to receive payment data from one or more types of payment data sources; a user interface configured to receive user input; a computer-readable storage medium having stored thereon computer-readable instructions to be executed by one or more processors; and one or more processors in communication with the computer-readable storage medium and configured by the computer-readable instructions stored thereon to perform the following operations: (i) receive payment data via the payment data reader, wherein the payment data is received from a payment data source associated with an unverified customer; (ii) receive a personal identification code via the user interface; (iii) attempt a zero-value transaction based on the payment data and personal identification code received; and (iv) if the zero-value transaction is successful, providing an indication via the payment device that the identity of the unverified customer is verified.

[0005] According to another embodiment of the present disclosure, a computer- implemented method of digitally verifying an identity of a customer is provided. The method can include: receiving, via a payment data reader of a payment device, payment data from a payment data source associated with an unverified customer; receiving, via a user interface of the payment device, a personal identification code associated with the payment data source; attempting, via the payment device, a zero-value transaction based on the payment data and personal identification code received; and if the zero-value transaction is successful, providing an indication via the payment device that the identity of the unverified customer is verified.

[0006] According to yet another embodiment of the present disclosure, a system configured to digitally verify an identity of one or more customers is provided. The system can include: a verification sub-system comprising one or more remote servers having a computer-readable storage medium configured to securely store payment data and identification information for a plurality of users, and one or more processors configured to process one or more zero-value transactions; and one or more payment devices in communication with the verification subsystem, wherein each payment device comprises: a payment data reader configured to receive payment data from one or more types of payment data sources; a user interface configured to receive user input; a computer-readable storage medium having stored thereon computer- readable instructions to be executed by one or more processors; and one or more processors in communication with the computer-readable storage medium and configured by the computer- readable instructions stored thereon to perform the following operations: (i) receive payment data via the payment data reader, wherein the payment data is received from a payment data source associated with an unverified customer; (ii) receive a personal identification code via the user interface; (iii) attempt, via the verification sub-system, a zero-value transaction based on the payment data and personal identification code received; and (iv) if the zero-value transaction is successful, providing an indication via the payment device that the identity of the unverified customer is verified.

[0007] These and other aspects of the various embodiments will be apparent from and elucidated with reference to the embodiments described hereinafter. Brief Description of the Drawings

[0008] In the drawings, like reference characters generally refer to the same parts throughout the different views. Also, the drawings are not necessarily to scale, emphasis instead generally being placed upon illustrating the principles of the various embodiments.

[0009] FIG. 1 is a diagram illustrating a system for registering and verifying the identity of one or more customers in accordance with aspects of the present disclosure.

[0010] FIG. 2A is a diagram illustrating a registration sub-system in accordance with aspects of the present disclosure.

[0011] FIG. 2B is a diagram illustrating a verification sub-system in accordance with aspects of the present disclosure.

[0012] FIG. 2C is a diagram illustrating an on-site sub-system in accordance with aspects of the present disclosure.

[0013] FIG. 3 is a diagram illustrating a payment device in accordance with aspects of the present disclosure.

[0014] FIG. 4 is a flowchart illustrating a computer-implemented method of verifying the identity of a customer in accordance with aspects of the present disclosure.

Detailed Description of Embodiments

[0015] The present disclosure is directed to systems and methods for verifying the identity (e.g., identification information) of one or more individuals using a payment device like a point-of-sale (POS) payment terminal. As described in more detail below, the systems and methods utilize a registration process that connects identification information of the individuals to a corresponding payment card, such that a zero-value transaction may be used to verify the identities of the individuals. As a result, a bank, merchant, or other entity can reliably identify customers while eliminating the need for the customer to provide multiple means of identification beyond their payment card.

[0016] With reference to FIG. 1, a system 100 configured to digitally verify an identity of one or more customers is illustrated in accordance with various aspects of the present disclosure. As shown, the system 100 may include a registration sub-system 110, a verification sub-system 120, and an on-site sub-system 130. In embodiments, the registration sub-system 110 can be configured to enable one or more users to register certain identification information such that the identification information is then connected with a payment card associated with the user(s). The registration sub-system 110 may communicate with the verification sub-system 120 by, for example, a communications network 170, which can include wired and/or wireless network connections. The verification sub-system 120 can be configured to receive identification information from the registration sub-system 110 and securely store such identification information for a plurality of users. In embodiments, the verification sub-system 120 is further configured to facilitate one or more zero-value transactions with one or more financial institutions 150 over a secure connection 160 based on payment card data received from one or more on-site sub-systems 130. In embodiments, the on-site sub-systems 130 may communicate with the verification sub-system 120 via a communications network 170, which can include wired and/or wireless network connections.

[0017] With reference to FIGS. 2A-2C, the registration sub-system 110, verification subsystem 120, and the on-site sub-system 130 are illustrated in more detail in accordance with further aspects of the present disclosure. For example, as shown in FIG. 2A, a registration subsystem 110 is illustrated according to certain aspects of the present disclosure. In embodiments, the registration sub-system 110 is configured to facilitate the collection and registration of identification information in the verification sub-system 120. As described herein, a user 202 may use an application on a personal mobile device 204, desktop computer 206, and/or a similar device to provide relevant identification information. In embodiments, identification information can include, but is not limited to, personal identifiable information such as name, address, social security number or other identifying number or code, telephone number, email address, and/or the like. In some embodiments, the identification information may include digital images (pictures, scans, etc.) of one or more forms of physical identification 208, such as government-issued identification cards, licenses, badges, passports, and/or the like. In particular embodiments, the identification information can also include a picture of the user’s face.

[0018] During the registration process, the user 202 must also enter valid payment card details, which can be done via an NFC tap or by manual entry, for example. Once the payment card details and the identification information are entered, a digital identity 210 is generated. The application running on the mobile device 204 or desktop computer 206 used by the user 202 can communicate the digital identity 210 to a backend verification sub-system 120 via a communications network 170. As shown in FIG. 2A, once the backend verification sub-system 120 confirms the details of the digital identity 210 of the user 202, the backend verification sub-system 120 may communicate a digital confirmation 212 (e.g., an email, text, etc.) to the user 202 in response to the user 202 successfully registering their digital identity 210.

[0019] Turning to FIG. 2B, the backend verification sub-system 120 can be configured to receive, confirm, and/or store identification information for one or more users 202. As shown, the verification sub-system 120 can include an e-receipt service 214 that generates and communicates a digital confirmation 212 of the registration to the one or more users 202. In particular embodiments, the verification sub-system 120 can include a computer-readable storage medium 216 configured to securely store the identification information for one or more users 202. The verification sub-system 120 can include a verification module 218 that comprises the storage medium 216 or otherwise is able to access the storage medium 216 to add, retrieve, delete, or otherwise modify the contents thereof. In embodiments, the verification sub-system 120 can also include a payment interface module 220 configured to communicate with various financial institutions 150 via a secure connection 160 in order to facilitate one or more zero-value transactions based on payment data / information passed along through the verification module 218. In further embodiments, the verification sub-system 120 can include a Global Service Connector (GSC) module 222 configured to send information (such as registration confirmations) and/or receive communications (such as registration requests and/or verification requests) from the registration sub-system 110 and/or the on-site sub-system 130. [0020] As described herein, each of the modules / services 214, 216, 218, 220, 222 can include one or more remote servers comprising a computer-readable storage medium (not shown) and one or more computer processors (not shown) configured to perform one or more operations described herein. The one or more processors may include a microprocessor, a multi-core processor, a multithreaded processor, an ultra-low voltage processor, an embedded processor, and/or the like, including combinations thereof. In some embodiments, the one or more processors may include multiple processor cores on a single die and/or may be a part of a system on a chip (SoC) in which the processors and other components are formed into a single integrated circuit, or a single package. In further embodiments, the computer-readable storage medium can be variously embodied in one or more forms of machine-accessible and machine- readable storage media. In some examples, this may include one or more types of memory, including one or more types of transitory and/or non-transitory memory. In particular embodiments, the storage medium may include a magnetic disk storage device, an optical disk storage device, an array of storage devices, a solid-state memory device, and/or the like, including combinations thereof. The storage medium may also include one or more other types of memory, such as dynamic random-access memory (DRAM), static random-access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, and/or the like.

[0021] With reference to FIG. 2C, an example of one on-site sub-system 130 is illustrated according to aspects of the present disclosure. However, it should be appreciated that the system 100 can include multiple or a plurality of on-site sub-systems 130 located across different geographical locations. Put another way, the verification sub-system 120 may communicate with one or more of the on-site sub-systems 130 as described herein. In embodiments, each of the on-site sub-systems 130 can include one or more point-of-sale (POS) payment devices 230. Each payment device 230 can be configured to digitally verify an identity of a customer 232. That is, the payment device 230 can include an identity verification application that uses payment card data to digitally verify the identity of a customer 232.

[0022] For example, customer 232 enters the business of a merchant 234 and wishes to perform a financial transaction (e.g., make a purchase, take out a loan, etc.) that requires verification of the customer’s identity. Rather than require the customer 232 to bring various forms of identification, the merchant 234 may verify the customer’s identity using the payment device 230 and a payment card 236 of the customer 232. To confirm the customer’s identity, the merchant 234 may instruct the customer 232 to provide their payment card 236 to the payment device 230. The payment device 230 can include a payment data reader configured to receive the payment data from one or more types of payment data sources (e.g., payment cards, etc.). Using an identity verification application on the payment device 230, the customer 232 provides their payment card 236 and provides a personal identification code (such as a PIN number) associated with the payment card 236. In embodiments, the payment device 230 can include a user interface configured to receive user input such as a personal identification code. [0023] Then, in embodiments, the payment device 230 will attempt a zero-value transaction based on the payment data and the personal identification code received. More specifically, the payment device 230 will communicate the payment data and personal identification code received to the verification sub-system 120 via the communications network 170, which facilitates the zero-value transaction through the payment interface module 220. If the transaction is approved, the identity verification module 218 will send back to the on-site subsystem 130 an indication that the identity of the customer 232 is verified.

[0024] In some embodiments, upon approval of the zero-value transaction, the verification sub-system 120 sends back relevant information for that verified user 232. Put another way, the indication that the identity of the customer 232 is verified can include relevant identification information. For example, in some embodiments, the relevant information could include a picture indication or other information that is stored in the verification sub-system 120 (e.g., address, email, phone numbers, etc.). In certain embodiments, the payment device 230 may display certain identification information 238 for the customer 232, or may transmit the information 238 to a secondary device 240 for display as shown in FIG. 2C. In some embodiments, the information 238 can also include an explicit indication 242 of whether the customer’s identity was verified based on whether or not the zero-value transaction was successful. In embodiments, if the financial institution 150 declines the zero-value transaction, then the verification sub-system 120 will transmit an indication that the user 232 is not verified, and display that information 238 accordingly.

[0025] As described herein, the payment device / terminal 230 can be configured to receive payment data via a payment data reader and process the payment data in order to complete one or more zero-value transactions. More specifically, with reference to FIG. 3, a payment device may comprise: a display 302, a payment data reader 304 (e.g., a magnetic stripe reader, an EMV chip reader, a contactless reader like a near-field communication reader, a bar code reader, and/or the like, including combinations thereof), a networking component 306 (e.g., enabling connection to a network via Ethernet, Wi-Fi, Bluetooth, etc.), one or more computer processors 308, memory 310 maintaining a file system of software packages (e.g., a combination of machine-readable instructions 312 and data 314), and a user interface 320. The payment device 230 can be configured by the software packages stored in the corresponding memory to receive protected payment card information (PCI) and/or other payment information (e.g., loyalty program information, gift card information, etc.) and securely communicate the payment information to a payment processor in order to facilitate the completion of a financial transaction (such as a zero-value transaction). As described in more detail herein, the payment device 230 can also be configured by the software packages stored in the corresponding memory to perform / participate in an identity verification process.

[0026] Generally, however, the components of the payment device 230, including the one or more processors 308, machine-readable memory 310, the input/output interface 316, the networking unit 306, and the user interface 320, may be interconnected and/or communicate through a system bus 318 containing conductive circuit pathways through which instructions (e.g., machine-readable signals) may travel to effectuate communication, tasks, storage, and the like. As described above, the payment device 230 may include a payment data reader 304 and/or a display 302 also connected via the system bus 318.

[0027] The one or more processors 308 may include one or more high-speed data processors adequate to execute the program components described herein and/or perform one or more steps of the methods described herein. The one or more processors 308 may include a microprocessor, a multi-core processor, a multithreaded processor, an ultra-low voltage processor, an embedded processor, and/or the like, including combinations thereof. The one or more processors 308 may include multiple processor cores on a single die and/or may be a part of a system on a chip (SoC) in which the processor 308 and other components are formed into a single integrated circuit, or a single package.

[0028] The input/output (I/O) interface 316 of the payment device 230 may include one or more I/O ports that provide a physical connection to one or more external devices, such as diagnostic equipment or other peripheral components. In some embodiments, the I/O interface 316 may include one or more serial ports.

[0029] The networking unit 306 of the payment device 230 may include one or more types of networking interfaces that facilitate wireless communication between one or more components of the payment device 230 and/or between the payment device 230 and one or more external devices. In embodiments, the networking unit 306 may operatively connect the payment device 230 to the verification sub-system 120 via a communications network 170, which may include a direct interconnection, the Internet, a local area network (“LAN”), a metropolitan area network (“MAN”), a wide area network (“WAN”), a wired or Ethernet connection, a wireless connection, a cellular network, and similar types of communications networks, including combinations thereof. In some examples, a payment device 230 may communicate with one or more remote devices, including but not limited to remote / cloudbased servers, cloud-based services (e.g., GSC module 22), payment processors, and/or the like.

[0030] The memory 310 of the payment device 230 can be variously embodied in one or more forms of machine-accessible and machine-readable storage media. In some examples, the memory 310 may include one or more types of memory, including one or more types of transitory and/or non-transitory memory. In particular embodiments, the memory 310 may include a magnetic disk storage device, an optical disk storage device, an array of storage devices, a solid-state memory device, and/or the like, including combinations thereof. The memory 310 may also include one or more other types of memory, such as dynamic randomaccess memory (DRAM), static random-access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, and/or the like.

[0031] In particular embodiments, the memory 310 can be configured to store data 314 and machine-readable instructions 312 that, when executed by the one or more processors 308, cause the payment device 230 to perform one or more steps of the methods and/or processes described herein. Put another way, provided herein is a computer-readable storage medium 310 having stored thereon machine-readable instructions 312 to be executed by one or more processors 308, and one or more processors 308 configured by the machine-readable instructions 312 stored on the computer-readable storage medium 310 to perform one or more of the operations of the methods described herein.

[0032] For example, with reference to FIG. 4, a computer-implemented method of digitally verifying an identity of a user is illustrated in accordance with aspects of the present disclosure. The method 400 includes: in a step 410, receiving registration information (e.g., identification information, payment data, etc.) for one or more users; in a step 420, validating and storing the registration information in a backend verification sub-system 120; in a step 430, initializing an identity verification application on a payment device 230 (i.e., of an on-site sub-system 130); in a step 440, receiving payment data from a payment data source via the payment device; in a step 450, receiving a personal identification code via a user interface of the payment device; in a step 460, attempting a zero-value transaction via the verification sub-system 120 based on the payment data and personal identification code received; and, in a step 470A/470B, providing an indication of whether the user’s identity is verified based on whether the zerovalue transaction was successful or not.

[0033] It should be appreciated that all combinations of the foregoing concepts and additional concepts discussed in greater detail below (provided such concepts are not mutually inconsistent) are contemplated as being part of the inventive subject matter disclosed herein. In particular, all combinations of claimed subject matter appearing at the end of this disclosure are contemplated as being part of the inventive subject matter disclosed herein. It should also be appreciated that terminology explicitly employed herein that also may appear in any disclosure incorporated by reference should be accorded a meaning most consistent with the particular concepts disclosed herein.

[0034] All definitions, as defined and used herein, should be understood to control over dictionary definitions, definitions in documents incorporated by reference, and/or ordinary meanings of the defined terms.

[0035] The indefinite articles “a” and “an,” as used herein in the specification and in the claims, unless clearly indicated to the contrary, should be understood to mean “at least one.” [0036] The phrase “and/or,” as used herein in the specification and in the claims, should be understood to mean “either or both” of the elements so conjoined, i.e., elements that are conjunctively present in some cases and disjunctively present in other cases. Multiple elements listed with “and/or” should be construed in the same fashion, i.e., “one or more” of the elements so conjoined. Other elements may optionally be present other than the elements specifically identified by the “and/or” clause, whether related or unrelated to those elements specifically identified. [0037] As used herein in the specification and in the claims, “or” should be understood to have the same meaning as “and/or” as defined above. For example, when separating items in a list, “or” or “and/or” shall be interpreted as being inclusive, i.e., the inclusion of at least one, but also including more than one, of a number or list of elements, and, optionally, additional unlisted items. Only terms clearly indicated to the contrary, such as “only one of’ or “exactly one of,” or, when used in the claims, “consisting of,” will refer to the inclusion of exactly one element of a number or list of elements. In general, the term “or” as used herein shall only be interpreted as indicating exclusive alternatives (i.e. “one or the other but not both”) when preceded by terms of exclusivity, such as “either,” “one of,” “only one of,” or “exactly one of.” [0038] As used herein in the specification and in the claims, the phrase “at least one,” in reference to a list of one or more elements, should be understood to mean at least one element selected from any one or more of the elements in the list of elements, but not necessarily including at least one of each and every element specifically listed within the list of elements and not excluding any combinations of elements in the list of elements. This definition also allows that elements may optionally be present other than the elements specifically identified within the list of elements to which the phrase “at least one” refers, whether related or unrelated to those elements specifically identified.

[0039] As used herein, although the terms first, second, third, etc. may be used herein to describe various elements or components, these elements or components should not be limited by these terms. These terms are only used to distinguish one element or component from another element or component. Thus, a first element or component discussed below could be termed a second element or component without departing from the teachings of the inventive concept.

[0040] Unless otherwise noted, when an element or component is said to be “connected to,” “coupled to,” or “adjacent to” another element or component, it will be understood that the element or component can be directly connected or coupled to the other element or component, or intervening elements or components may be present. That is, these and similar terms encompass cases where one or more intermediate elements or components may be employed to connect two elements or components. However, when an element or component is said to be “directly connected” to another element or component, this encompasses only cases where the two elements or components are connected to each other without any intermediate or intervening elements or components.

[0041] In the claims, as well as in the specification above, all transitional phrases such as “comprising,” “including,” “carrying,” “having,” “containing,” “involving,” “holding,” “composed of,” and the like are to be understood to be open-ended, i.e., to mean including but not limited to. Only the transitional phrases “consisting of’ and “consisting essentially of’ shall be closed or semi-closed transitional phrases, respectively.

[0042] It should also be understood that, unless clearly indicated to the contrary, in any methods claimed herein that include more than one step or act, the order of the steps or acts of the method is not necessarily limited to the order in which the steps or acts of the method are recited.

[0043] The above-described examples of the described subject matter can be implemented in any of numerous ways. For example, some aspects can be implemented using hardware, software or a combination thereof. When any aspect is implemented at least in part in software, the software code can be executed on any suitable processor or collection of processors, whether provided in a single device or computer or distributed among multiple device s/ computers .

[0044] The present disclosure can be implemented as a system, a method, and/or a computer program product at any possible technical detail level of integration. The computer program product can include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present disclosure.

[0045] The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium can be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium comprises the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire. [0046] Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network can comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

[0047] Computer readable program instructions for carrying out operations of the present disclosure can be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, statesetting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, comprising an object oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions can execute entirely on the user’s computer, partly on the user’ s computer, as a stand-alone software package, partly on the user’s computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, comprising a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider). In some examples, electronic circuitry comprising, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) can execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present disclosure.

[0048] Aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to examples of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions. [0049] The computer readable program instructions can be provided to a processor of a, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions can also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture comprising instructions which implement aspects of the function/act specified in the flowchart and/or block diagram or blocks.

[0050] The computer readable program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

[0051] The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various examples of the present disclosure. In this regard, each block in the flowchart or block diagrams can represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the blocks can occur out of the order noted in the Figures. For example, two blocks shown in succession can, in fact, be executed substantially concurrently, or the blocks can sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

[0052] Other implementations are within the scope of the following claims and other claims to which the applicant can be entitled.

[0053] While several inventive embodiments have been described and illustrated herein, those of ordinary skill in the art will readily envision a variety of other means and/or structures for performing the function and/or obtaining the results and/or one or more of the advantages described herein, and each of such variations and/or modifications is deemed to be within the scope of the inventive embodiments described herein. More generally, those skilled in the art will readily appreciate that all parameters, dimensions, materials, and configurations described herein are meant to be exemplary and that the actual parameters, dimensions, materials, and/or configurations will depend upon the specific application or applications for which the inventive teachings is/are used. Those skilled in the art will recognize, or be able to ascertain using no more than routine experimentation, many equivalents to the specific inventive embodiments described herein. It is, therefore, to be understood that the foregoing embodiments are presented by way of example only and that, within the scope of the appended claims and equivalents thereto, inventive embodiments may be practiced otherwise than as specifically described and claimed. Inventive embodiments of the present disclosure are directed to each individual feature, system, article, material, kit, and/or method described herein. In addition, any combination of two or more such features, systems, articles, materials, kits, and/or methods, if such features, systems, articles, materials, kits, and/or methods are not mutually inconsistent, is included within the inventive scope of the present disclosure.

Claims

Claims What is claimed is:

1. A payment device configured to digitally verify an identity of an unverified customer, the payment device comprising: a payment data reader configured to receive payment data from one or more types of payment data sources; a user interface configured to receive user input; a computer-readable storage medium having stored thereon computer-readable instructions to be executed by one or more processors; and one or more processors in communication with the computer-readable storage medium and configured by the computer-readable instructions stored thereon to perform the following operations: (i) receive, via the payment data reader, payment data from a payment data source associated with the unverified customer; (ii) receive, via the user interface, a personal identification code; (iii) attempt a zero-value transaction using the payment data and the personal identification code received; and (iv) if the zero-value transaction is successful, providing an indication via the payment device that the identity of the unverified customer is verified.

2. The payment device of claim 1, wherein the payment device is a point-of-sale terminal.

3. The payment device of claim 1, wherein the one or more processors are configured to: (v) if the zero-value transaction is not successful, providing an indication via the payment device that the identity of the unverified customer is not verified.

4. The payment device of claim 1, wherein the one or more processors are configured to attempt the zero-value transaction by: communicating the payment data and the personal identification code received via the payment device to a verification system via a communications network; and receiving, from the verification system, an indication of whether the zero-value transaction was approved by a financial institution associated with the payment data; wherein the verification system is configured to communicate with one or more financial institutions via a secure connection in order to facilitate one or more zero-value transactions.

5. The payment device of claim 4, wherein the indication received from the verification system comprises identification information for the unverified customer if the zerovalue transaction was approved.

6. The payment device of claim 5, wherein the identification information comprises an address, email, phone number, and/or photograph of the unverified customer.

7. The payment device of claim 5, further comprising a display; wherein the one or more processors are further configured to: (vi) display the identification information of the unverified customer on the display.

8. The payment device of claim 5, wherein the one or more processors are further configured to: (vii) transmit the identification information of the unverified customer to a secondary device for display.

9. The payment device of claim 1, wherein the payment data reader comprises a magnetic stripe reader, an EMV chip reader, a near-field communication reader, and/or a bar code reader.

10. The payment device of claim 1, wherein the payment data source associated with the unverified customer is a payment card.

11. A computer-implemented method of digitally verifying an identity of an unverified customer, the method comprising: receiving, via a payment data reader of a payment device, payment data from a payment data source associated with the unverified customer; receiving, via a user interface of the payment device, a personal identification code associated with the payment data source; attempting, via the payment device, a zero-value transaction using the payment data and the personal identification code received; and if the zero-value transaction is successful, providing an indication via the payment device that the identity of the unverified customer is verified.

12. The computer-implemented method of claim 11, further comprising: if the zero-value transaction is not successful, providing an indication via the payment device that the identity of the unverified customer is not verified.

13. The computer-implemented method of claim 11 , wherein the payment device is configured to attempt the zero-value transaction by: communicating the payment data and the personal identification code received via the payment device to a verification system via a communications network; and receiving, from the verification system, an indication of whether the zero-value transaction was approved by a financial institution associated with the payment data; wherein the verification system is configured to communicate with one or more financial institutions via a secure connection in order to facilitate one or more zero-value transactions.

14. The computer-implemented method of claim 13, wherein the indication received from the verification system comprises identification information for the unverified customer if the zero-value transaction was approved.

15. The computer-implemented method of claim 14, wherein the identification information comprises an address, email, phone number, and/or photograph of the unverified customer.

16. The computer-implemented method of claim 15, further comprising: displaying, on a display of the payment device, the identification information of the unverified customer.

17. The computer-implemented method of claim 15, further comprising: transmitting the identification information of the unverified customer to a secondary device for display.

18. A system for digitally verifying an identity of one or more unverified customers, the system comprising: a verification system comprising one or more remote servers having a computer- readable storage medium configured to securely store payment data and identification information for a plurality of registered users, and one or more processors configured to process one or more zero-value transactions; and one or more payment devices in communication with the verification system, wherein each payment device comprises: a payment data reader configured to receive payment data from one or more types of payment data sources; a user interface configured to receive user input; a computer-readable storage medium having stored thereon computer- readable instructions to be executed by one or more processors; and one or more processors in communication with the computer-readable storage medium and configured by the computer-readable instructions stored thereon to perform the following operations: (i) receive, via the payment data reader, payment data from a payment data source associated with the unverified customer; (ii) receive, via the user interface, a personal identification code; (iii) attempt a zero-value transaction using the payment data and the personal identification code received; and (iv) if the zero-value transaction is successful, providing an indication via the payment device that the identity of the unverified customer is verified.

19. The system of claim 18, wherein the one or more processors of the verification system are configured to process a zero-value transaction by: receiving, from one payment device of the one or more payment devices, the payment data and the personal identification code associated with the unverified customer; communicating, via a secure connection, with one or more financial institutions associated with the payment data in order to facilitate the zero-value transaction; receiving, from the one or more financial institutions, a determination of whether the zero-value transaction was approved; and transmitting, to the one payment device, an indication of whether the zero-value transaction was approved by the one or more financial institutions.

20. The system of claim 19, wherein the indication transmitted by the verification system comprises identification information for the unverified customer if the zero-value transaction was approved.