U.S. patent application number 15/650690 was filed with the patent office on 2019-01-17 for systems for generating an auditable digital certificate.
The applicant listed for this patent is Trunomi Ltd.. Invention is credited to Stuart H. Lacey, Naresh Singhal.
Application Number | 20190019184 15/650690 |
Document ID | / |
Family ID | 64999449 |
Filed Date | 2019-01-17 |
View All Diagrams
United States Patent
Application |
20190019184 |
Kind Code |
A1 |
Lacey; Stuart H. ; et
al. |
January 17, 2019 |
Systems for Generating an Auditable Digital Certificate
Abstract
The systems described herein are configured to generate an
auditable digital certificate upon receiving a request for user
information associated with a user of the plurality of users and
determining that authorization from the user is required The
digital certificate comprises: a unique identifier associated with
the requester, a context of the request, and a date and time
associated with the request. The system then sends an authorization
request that includes: a request for consent to grant the request
from the requester, and a request for identity verification
evidence. Upon receiving the consent and identity verification
evidence, the system adds to the digital certificate: a unique
identifier associated with the user, the consent, and a date and
time associated with receipt of the consent. Finally, the system
closes and tamperproofs the digital certificate before storing the
digital certificate in a certificate database.
Inventors: |
Lacey; Stuart H.; (Paget,
BM) ; Singhal; Naresh; (Fremont, CA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Trunomi Ltd. |
Pembroke |
|
BM |
|
|
Family ID: |
64999449 |
Appl. No.: |
15/650690 |
Filed: |
July 14, 2017 |
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
G06Q 20/4016 20130101;
G06Q 20/42 20130101; G06Q 20/38215 20130101; G06Q 20/02 20130101;
G06Q 20/40145 20130101 |
International
Class: |
G06Q 20/38 20060101
G06Q020/38; G06Q 20/40 20060101 G06Q020/40; G06Q 20/02 20060101
G06Q020/02; G06Q 20/42 20060101 G06Q020/42 |
Claims
1. A server system for generating an auditable digital certificate,
the server system comprising: a first server with one or more
processors and memory for storing (i) one or more programs for
execution by the one or more processors and (ii) one or more data
structures, the one or more data structures including a user
information database storing user information associated with a
plurality of users; a second server with one or more processors and
memory for storing (i) one or more programs for execution by the
one or more processors and (ii) one or more data structures, the
one or more data structures including a certificate database
storing digital certificates associated with requests for the user
information stored in the user information database; a third server
with one or more processors and memory for storing one or more
programs for execution by the one or more processors, the one or
more programs including instructions for: receiving, from a
requester at a remote enterprise device, a request for user
information associated with a user of the plurality of users,
wherein the user information corresponds to user information stored
in the user information database; before granting the request,
determining that an authorization from the user is required; in
response to determining that authorization from the user is
required: creating a digital certificate comprising: a unique
identifier associated with the requester, a context of the request,
and a date and time associated with the request; sending, to a
remote client device associated with the user, an authorization
request that includes: a request for consent to grant the request
from the requester, and a request for identity verification
evidence; receiving, from the remote client device, the consent and
the identity verification evidence; adding to the digital
certificate: a unique identifier associated with the user, the
consent, and a date and time associated with receipt of the
consent; closing and tamperproofing the digital certificate,
including (i) digitally signing the certificate, and (ii)
preventing further changes to the certificate; and storing the
digital certificate in the certificate database.
2. (canceled)
3. The server system of claim 1, wherein the identity verification
evidence is an image from a camera of the remote client device.
4. The server system of claim 1, wherein the identity verification
evidence is positioning information from a positioning system of
the remote client device.
5. The server system of claim 1, wherein the identity verification
evidence is a unique identifier of the remote client device.
6. The server system of claim 5, wherein the unique identifier is
an IMEI number associated with the remote client device.
7. The server system of claim 5, wherein the unique identifier is
an IP address associated with the remote client device.
8. The server system of claim 5, wherein the unique identifier is a
MAC address associated with the remote client device.
9. The server system of claim 1, wherein the certificate further
includes a transaction rating.
10. The server system of claim 1, wherein the certificate further
includes a verification rating for the user.
11. The server system of claim 1, wherein the context is a
know-your-customer share.
12. The server system of claim 1, wherein the context is a document
update.
13. The server system of claim 1, wherein the context includes a
fraud alert.
14. A server configured to generate an auditable digital
certificate, the server comprising: one or more processors; memory;
one or more programs stored in the memory and configured to be
executed by the one or more processors; a user information database
storing user information associated with a plurality of users,
wherein the user information database is stored in the memory; a
certificate database storing digital certificates associated with
requests for the user information stored in the user information
database, wherein the certificate database is stored in the memory;
request handling instructions stored in the memory and for:
receiving, from a requester at a remote enterprise device, a
request for user information associated with a user of the
plurality of users, wherein the user information corresponds to
user information stored in the user information database; sending,
to a remote client device associated with the user, an
authorization request that requires: consent and identity
verification evidence; receiving, from the remote client device,
the consent and the identity verification evidence; access
management instructions stored in the memory and for determining
whether an authorization from the user is required before granting
the request for user information associated with the user; and
certificate generation instructions stored in the memory and for:
creating a digital certificate comprising: a unique identifier
associated with the requester, a context of the request, and a date
and time associated with the request; in response to receiving the
consent and the identity verification evidence from the remote
client device, adding to the digital certificate: a unique
identifier associated with the user, the consent, and a date and
time associated with receipt of the consent; closing and
tamperproofing the certificate, including (i) digitally signing the
certificate, and (ii) preventing further changes to the
certificate; and storing the digital certificate in the certificate
database.
15. (canceled)
16. The server of claim 14, wherein the identity verification
evidence is positing information from a positioning system of the
remote client device.
17. The server of claim 14, wherein the identity verification
evidence is a unique identifier of the remote client device.
18. The server of claim 14, wherein the certificate further
includes a transaction rating.
19. The server of claim 14, wherein the certificate further
includes a verification rating for the user.
20. The server of claim 14, wherein the context includes a fraud
alert.
21. The server of claim 14, wherein the context includes a know
your-customer share.
22. The server of claim 14, wherein the context includes a travel
confirmation.
Description
TECHNICAL FIELD
[0001] The disclosed implementations relate generally to computer
networks, and more specifically, to systems and methods for
preventing fraudulent transactions in a computer networking
environment.
BACKGROUND
[0002] Online services have greatly expanded the scope and ease of
performing a host of transactions, including banking, travel,
communications, and shopping. Unfortunately, the ease of performing
these transactions online has also led to increased fraudulent
activity. For example, traditionally, users could only make a
credit card purchase if they handed their credit card to a cashier
who could verify the user's signature. Nowadays, a majority of
credit card transactions occur online where the card is not present
to the merchant, which has led to a spike in credit card fraud. To
combat this fraud, banks employ sophisticated algorithms to
determine whether each and every transaction is likely to be a
legitimate transaction or a fraudulent one. These systems, however,
often decline legitimate transactions as they are unable to easily
verify if the customer made the transaction or not. For example,
many credit card users are unpleasantly surprised when their cards
are declined while travelling abroad and where their bank flags
foreign transactions as likely fraudulent. To unlock their card,
the customer typically has to contact their bank, convince the bank
that they are indeed the customer, and then ask the bank to unlock
the card for use abroad. Alternatively, banks try and call their
customers when suspicious activity is detected. Either way,
retailers, credit card processors, and the banks loose valuable
sales and transactions, while at the same time embarrassing and
alienating their customers.
[0003] Furthermore, many online transactions, including sending
documents to financial institutions, "know your customer"
requirements, or simply providing consent, nowadays requires
auditable trails for the transaction. For example, bank customers
are often required to print and sign consent forms and fax or email
them back to their bank, which is then required to store the
document for years. These back-and-forth telephone calls, faxes,
emails, and letters are not only inefficient but also alienate the
bank's customers.
[0004] Accordingly, it is desirable to provide efficient systems
and methods that (i) provide efficient and convenient mechanisms
for preventing fraud by verifying transactions in real-time, and
(ii) automatically providing auditable trails of such
transactions.
SUMMARY
[0005] Accordingly, it would be advantageous to provide systems and
methods that improve upon existing techniques for sharing verified
identity documents of individuals or companies with others.
[0006] In accordance with some implementations, a method for
generating an auditable digital certificate is disclosed. The
method is performed at one or more electronic devices (e.g., a
server system) with one or more processors and memory storing one
or more programs for execution by the one or more processors. The
server receives, from a requester at a remote server, a request for
information associated with a user. The server provides a set of
rules used to determine whether an authorization from a user is
required. The server applies the set of rules to the request to
determine whether the authorization from the user is required. Upon
determining that authorization from the user is required, the
server creates a digital certificate, wherein the certificate
comprises: a unique identifier associated with the requester, a
context of the request, and a date and time associated with the
request. The server sends, to the user at a remote client device,
an authorization request for consent to the request received from
the requester. The server receives, from the remote client device,
the consent. In response to receiving the consent, the server adds
to the digital certificate: a unique identifier associated with the
user, the consent, and a date and time associated with receipt of
the consent. The server closes and tamperproofs the digital
certificate.
[0007] In accordance with some implementations, a method for
sharing verified identity documents is disclosed. The method is
performed at one or more electronic devices (e.g., a client device
and/or a server system) with one or more processors and memory
storing one or more programs for execution by the one or more
processors. The client device obtains identity information of a
user. The client device also obtains a document. The client device
extracts data from the document, the extracted data including
extracted identity information. The client device determines that
the identity information of the user and the extracted identity
information substantially match, and generates at least one
verification rating for the document. The client device sends the
document, the data extracted from the document, and the at least
one verification rating to a server system remote from the client
device. The server system stores the document, the data extracted
from the document, and the at least one verification rating in
association with an account of the user, wherein at least one of
the document, the data extracted from the document, and the at
least one verification rating is stored in one or more encrypted
containers. The server system receives, from a third party, a
request for information associated with the account of the user,
the information including at least one of the document, the data
extracted from the document, and the at least one verification
rating. The server system sends a request to the client device
requesting authorization to release the information to the third
party. In response to receiving, from the client device,
authorization to release the information to the third party, the
server system sends the information to the third party.
[0008] In accordance with some implementations, a computer system
(e.g., a client system or server system) includes one or more
processors, memory, and one or more programs; the one or more
programs are stored in the memory and configured to be executed by
the one or more processors and the one or more programs include
instructions for performing the operations of the method described
above. In accordance with some implementations, a non-transitory
computer readable storage medium has stored therein instructions
which when executed by one or more processors, cause a computer
system (e.g., a client system or server system) to perform the
operations of the methods described above.
[0009] The disclosed systems and methods obviate many logistical
difficulties for both individuals and requesting parties. In
particular, because documents are shared electronically, users do
not need to physically present or mail original copies of documents
to a requestor. Similarly, the requestor does not need to store or
maintain original copies of the documents, reducing overhead and
compliance risks. Moreover, because the documents are subject to
verification tests, requesting entities can forgo independent
verification of the documents, where appropriate, and can be
alerted to potentially fraudulent identity claims quickly and
easily. Finally, because the documents are encrypted and stored
securely, both the individual and the requestor can be assured of
the privacy and security of the information.
[0010] Some embodiments provide a method for preventing fraudulent
transactions in a computer network containing a server with one or
more processors and memory storing one or more programs for
execution by the one or more processors. Initially, the server
receives over the network a query from a remote processor of a
transaction. The server determines whether authorization from a
remote client device is required to complete the transaction. Upon
determining that client authorization is required, the server sends
an authorization request to the remote client over the network. The
server then determines whether authorization has been received from
the remote client. Upon determining that authorization has been
received from the remote client, the server determines if the
transaction can proceed. Upon determining that the transaction can
proceed, the server sends a message to authorize the transaction to
the remote processor over the network.
[0011] In some embodiments, the authorization request includes a
request for a transaction rating and the authorization received
from the client includes the transaction rating. In some
embodiments, the authorization request includes a request for
identity verification evidence. In some embodiments, the identity
verification evidence is obtained from a camera of the client. In
some embodiments, the identity verification evidence is biometrtic
information obtained by an application or a sensor. In some
embodiments, the identity verification evidence is obtained from
positioning system of the client. In some embodiments, the identity
verification evidence is selected from a group consisting of an
IMEI number, an IP address, and a MAC address. In some embodiments,
the identity verification evidence includes challenge
questions.
[0012] In some embodiments, the remote client requests
identification evidence, which it receives. It then compares the
identification evidence to previously stored identification data.
It then generates a transaction rating based on the degree of
similarity between the identification evidence and the previously
stored identification data.
[0013] In some embodiments, the remote client obtains identifying
information from the device, like the device's MAC address. It then
compares the identifying information to previously stored
information, and generates a transaction rating based on the degree
of similarity between the identifying information and the
previously stored information.
[0014] In some embodiments, upon determining that client
authorization is required, the server sends over the network to the
remote processor an instruction to hold the transaction until
further notice. In some embodiments, determining whether
authorization from a remote client device is required comprises
requesting and receiving instructions from a remote agent that
authorization from a remote client device is required. In some
embodiments, upon determining that the transaction cannot proceed,
the server sends a message to deny the transaction to the remote
processor over the network. In some embodiments, the certificate
includes unique identities of counterparties to the transaction, a
transaction context, and one or more event records. In some
embodiments, the certificate further includes a consent or
authorization from the remote client. In some embodiments, the
certificate further includes a transaction rating. In some
embodiments, the certificate further includes a digital signature.
In some embodiments, the certificate further includes verification
ratings for the counterparties of the transaction. In some
embodiments, each event record includes a date and time of the
event and a transaction event description. In some embodiments, the
transaction context may be a fraud alert, a travel confirmation, a
know-your-customer share, a PIN reset, a document update, reporting
a lost or stolen card, or the like.
[0015] Some embodiments provide a system for preventing fraudulent
transactions in a computer network that includes a server with one
or more processors and memory storing one or more programs for
execution by the one or more processors. In these embodiments, the
server is configured to perform any of the methods described
herein.
[0016] Similarly, some embodiments provide a non-transitory
computer readable storage medium that has stored therein
instructions which when executed by a server with one or more
processors and memory storing one or more programs for execution by
the one or more processors, cause the server to perform the any of
the methods described herein.
[0017] The fraud control system and methods described herein reduce
the time taken to verify whether an event is fraudulent or not, and
thus can significantly reduce the costs associated with
administering fraud controls, investigating the fraud, and most
importantly reducing the financial damage of a fraudulent
transaction. The sooner a fraud can be identified, the sooner a
card can be blocked or cancelled. Equally, for non-fraud
events--and where a card has been temporarily blocked--an automated
system reduces time and friction and the associated customer
frustration clearing the transaction inquiry.
[0018] The systems described herein also markedly improve computer
network efficiencies by reducing transaction delay and the need for
additional means of communication, such as telephone calls or
emails.
BRIEF DESCRIPTION OF THE DRAWINGS
[0019] The implementations disclosed herein are illustrated by way
of example, and not by way of limitation, in the figures of the
accompanying drawings. Like reference numerals refer to
corresponding parts throughout the drawings.
[0020] FIG. 1 is a block diagram illustrating a client-server
environment, in accordance with some implementations.
[0021] FIG. 2 is a block diagram illustrating a client computer
device, in accordance with some implementations.
[0022] FIG. 3 is a block diagram illustrating an enterprise
computer device, in accordance with some implementations.
[0023] FIG. 4 is a block diagram illustrating a server computer
device, in accordance with some implementations.
[0024] FIGS. 5A-5D are flow diagrams illustrating a method of
verifying a user's identity, in accordance with some
implementations.
[0025] FIG. 6 is a flow diagram illustrating a method of verifying
a document, in accordance with some implementations.
[0026] FIG. 7 shows a schematic representation of a certificate
data structure, according to some embodiments of the invention.
[0027] FIGS. 8A-8C are flow charts of a fraud alert process flow,
according to some embodiments of the invention.
DETAILED DESCRIPTION
[0028] Attention is now directed to the figures, and in particular
to FIG. 1, which is a block diagram of a client-server environment
100, according to some implementations, in which efficient, secure,
and convenient sharing of verified identity documents is possible.
The client-server environment 100 includes client devices 102-1 . .
. 102-n, a server 104, and enterprise devices 108-1 . . . 108-n,
all connected through a network 110. The network 110 includes any
of a variety of networks, including wide area networks (WAN), local
area networks (LAN), Personal Area Networks, metropolitan area
networks, VPNs, local peer-to-peer, ad-hoc connections, wireless
networks, wired networks, the Internet, or a combination of such
networks.
[0029] In some implementations, the client device 102-1 is
associated with an individual (or any entity that wishes to verify
its identity to another party), and is used to capture and/or
process documents and other information from an individual, as
described herein. In some implementations, the client device 102-1
includes a client application 112 that facilitates the capture
and/or processing of documents and other information (e.g., with an
built-in or attached camera or scanner), and communicates with one
or both of the server 104 and the enterprise device 108-1. In some
implementations, the client application 112 also generates
verification ratings for documents, extracts information from the
documents, and encrypts the documents (as well as the verification
ratings and extracted information) prior to sending the documents
to the server 104. The client device 102-1 and the client
application 112, and the functions and methods that they perform,
are discussed herein. Any description(s) of the client device
102-1, or of the functions or methods performed by the client
device 102-1, apply equally to any or all instances of the client
devices 102-n. (Moreover, in some implementations, functions or
methods described as being associated with or performed by the
client device 102-1 are performed by the enterprise device 108-1,
such as when a bank or other financial institution creates
preliminary accounts for its customers.) Exemplary client devices
include a desktop computer, a laptop computer, a tablet computer, a
mobile electronic device, a mobile phone (e.g., a "smartphone"), a
digital media player, or any other appropriate electronic device
(or a kiosk housing any of the aforementioned devices).
[0030] In some implementations, the enterprise device 108-1 is
associated with an entity that requires identity verification from
individuals or other entities. In some implementations, the
enterprise device 108-1 includes an enterprise application 114 that
facilitates the requesting and receipt of identity verification
information from individuals or entities (e.g., via the server
104). In some implementations, the enterprise device 108-1
communicates with one or both of the server 104 and the client
device 102-1. The enterprise device 108-1 and the enterprise
application 114, and the functions and methods that they perform,
are discussed herein. Any description(s) of the enterprise device
108-1, or of the functions or methods performed by the enterprise
device 108-1, apply equally to any or all instances of the
enterprise devices 108-n. Exemplary enterprise devices include a
desktop computer, a laptop computer, a tablet computer, a mobile
electronic device, a server computer (or server computer system), a
mobile phone, a digital media player, or any other appropriate
electronic device (or a kiosk housing any of the aforementioned
devices).
[0031] In some implementations, the server 104 is associated with a
service provider that can communicate, via the network 110 and/or
other communication means, with multiple client devices (e.g.,
102-n) and multiple enterprise devices (e.g., 108-n) to provide
and/or facilitate document sharing between entities. In some
implementations, the server 104 includes and/or communicates with a
user information database 106. As described herein, the user
information database 106 stores information associated with users,
including, but not limited to, documents (e.g., images or other
digital representations of identification documents, utility bills,
etc.), containers from which documents can be extracted,
information extracted from documents, user account information,
verification ratings, user scores, etc. In some implementations,
any or all of the foregoing information is encrypted such that only
the user with whom the information is associated (and parties
authorized by the user) can access and/or view the information.
[0032] In some implementations, the server 104 includes and/or
communicates with a certificate database 110. As described herein,
the user certificate database 110 stores transaction certificates
that are created for each transaction. An example of the data
structure 700 for a transaction certificate is shown in FIG. 7. An
example of how a certificate is generated is shown in FIGS. 8A-8C.
In some embodiments, certificates are used to verify that a
transaction occurred, provide details for the transaction, and
provide an auditable trail for such transactions.
[0033] Referring to FIG. 7, the certificate data structure 700
includes a unique identifier 702 for a requestor of the
transaction, e.g., a unique identifier for an individual. The
certificate data structure 700 also includes a unique identifier
704 for a recipient of the transaction, e.g., a unique identifier
for a bank. These two identifiers 702, 704 are used to identify the
counterparties to the transaction. Furthermore, while only two
parties are shown and described herein, in some embodiments each
transaction includes multiple parties (e.g., three or more) and
each one has its own unique identifier. For each transaction
certificate, additional details for the requestor and receiver may
be received and stored. For example, the requestor's IMEI, MAC
address, IP address or location 706 may be stored as part of each
certificate. Similarly, the recipient's IMEI, MAC address, IP
address or location 708 may be stored as part of each
certificate.
[0034] As described in more detail below, the requester's
verification rating 710, and the recipient's verification ratings
may also be stored in each transaction certificate. Each
transaction certificate also includes the context 714 for that
transaction, e.g., whether the transaction relates to a credit card
fraud alert (see FIGS. 8A-C), a travel confirmation, a
know-your-customer sharing of information, a personal
identification number (PIN) or password reset; updating a document
(e.g., updating a passport), or the like. Each transaction
certificate also includes one or more transaction events
716(1)-(n). Each transaction event includes the date, time stamp,
identifiers, and nature of the event (e.g., a request, response, or
result) 718(1)-(n). If the transaction relates to receiving consent
or an acknowledgement, then the consent or acknowledgement 720 is
stored in the transaction certificate.
[0035] In some embodiments, a transaction rating 722 is created for
each transaction, as explained in more detail with respect to FIGS.
8A-8C, and stored in each certificate. Also in some embodiments,
when each certificate is closed, the certificate is signed with
tamperproof digital signature 724.
[0036] Returning to FIG. 1, using the client-server environment 100
illustrated in FIG. 1, identity verification documents can be
quickly and efficiently shared between an individual and an
institution or other entity, allowing the identity of the
individual to be quickly and efficiently verified. In particular,
and as described herein, the client device 102-1 is used to capture
images and/or files of documents that can be used for identity
verification, such as government issued photo identification cards
and/or credentials (e.g., drivers' licenses, passports, etc.),
utility bills, and the like. For example, in some implementations,
the client device 102-1 is a smartphone with a digital camera, and
an individual uses the camera to capture a photograph of a drivers'
license and a utility bill. The smartphone then extracts
information from the photographs of the documents, analyzes them,
and generates a verification rating for the documents. Then, the
photographs, the information extracted from the photographs, and
the verification ratings are encrypted and sent to the server 104,
which stores these items in the user information database 106 in a
secure manner.
[0037] A requesting entity then requests identity verification
information from an individual (e.g., using the enterprise device
108-1), and a request is sent to the individual (e.g., via the
server 104). The individual then uses the client device 102-1
and/or the client application 112 to partially or fully approve (or
deny) the request. If the request is approved by the individual
(e.g., the individual authorizes the requesting entity to access to
all or some of the requested information), the requesting entity is
granted access to the authorized information via the server
104.
[0038] In some embodiments, the client-server environment 100
illustrated in FIG. 1 is used for other transactions, like
obtaining consent, authorization or acknowledgments from clients,
as described with reference to FIGS. 8A-8C. For example, an
enterprise, e.g., a bank, using an enterprise device 108(1)-(n) may
request a consent or authorization from a client or customer that
is using client device 102(1)-(n). The server 104 facilitates
obtaining the consent from the customer. In some embodiments,
certificates are created for each transaction.
[0039] The present discussion generally refers to the entity whose
identity is being verified as an individual or a "user." However,
identity verification for other entities is contemplated as well,
such as for companies, trusts, partnerships, businesses, families,
financial institutions, etc. Accordingly, any discussion relating
to an individual or a user also applies to other entities or
parties whose identity and documents are to be verified and/or
shared.
[0040] FIG. 2 is a block diagram illustrating a client device
102-1, in accordance with some implementations. While FIG. 2
illustrates one instance of a client device (i.e., client device
102-1), the figure and associated description applies equally to
any client device (e.g., 102-1-102-n).
[0041] In some implementations, the client device 102-1 is any of:
a desktop computer, a laptop computer, a tablet computer, a mobile
electronic device, a mobile phone, a digital media player, or any
other appropriate electronic device (or a kiosk housing any of the
aforementioned devices).
[0042] The client device 102-1 typically includes one or more CPUs
204, a user interface 206, at least one network communications
interface 212 (wired and/or wireless), an image capture device 214,
a positioning system 216, a biometric capture device 217, memory
218, and at least one communication bus 202 for interconnecting
these components. Each communication bus 202 may include circuitry
(sometimes called a chipset) that interconnects and controls
communications between system components. In some implementations,
the user interface 206 includes a display 208 and input device(s)
210 (e.g., keyboard, mouse, touchscreen, keypads, etc.).
[0043] The image capture device 214 is any device that is capable
of capturing an image of a real-world scene or object. In some
implementations, the image capture device 214 is a digital camera
(including any appropriate lens(es), sensor(s), and other
components). In some implementations, the image capture device is a
scanner (e.g., a flatbed document scanner). In some
implementations, the image capture device 214 is incorporated into
a common housing with the client device 102-1. For example, where
the client device 102-1 is a mobile phone, the image capture device
214 is a digital camera built into the mobile phone. As another
example, where the client device 102-1 is a laptop computer, the
image captured device 214 is a digital camera built into the laptop
computer (e.g., a "webcam"). Other possible image capture devices
include 3-D scanners, 3-D cameras, range cameras, motion sensing
imaging devices, ultrasonic scanners, and the like.
[0044] In some implementations, the image capture device 214 is in
a different housing than the client device 102-1. In one example,
the client device 102-1 is a laptop or desktop computer, and the
image capture device 214 is a separate scanner or camera that is
able to be coupled to the client device 102-1 to provide images to
the client device (e.g., via wired connection, such as a wired
network connection or a Universal Serial Bus connection, or via a
wireless connection, such as WiFi, Bluetooth, or the like).
[0045] The positioning system 216 includes devices and/or
components for determining the location of the client device 102-1,
including but not limited to global positioning system (GPS)
sensors, radio receivers (e.g., for cell-tower triangulation,
WiFi-based positioning, etc.), inertial sensors, and
accelerometers. In some implementations, the client device 102-1
does not include (or does not rely on) a separate positioning
system 216. For example, where the client device 102-1 is connected
to the Internet (e.g., via the network communications interface
212), the location of the client device 102-1 can be determined
using IP address geolocation techniques. Other techniques for
determining the location of the client device, including those that
rely on an inbuilt or connected positioning system and those that
do not, are also contemplated.
[0046] The (optional) biometric capture device 217 includes devices
and/or components for capturing biometric data from a person. In
some implementations, the biometric capture device 217 is a
fingerprint scanner. In some implementations, it is a retinal
scanner. In some implementations, it is a facial scanner. In some
implementations it is a voice recognition scanner. In some
implementations, the biometric capture device 217 is a
multi-purpose capture device that can capture multiple types of
biometric data from a user (e.g., handprints, fingerprints, facial
images, etc.). In some implementations, the biometric capture
device 217 is incorporated with and/or cooperates with the image
capture device 214 (e.g., to capture images of a user's face for
facial recognition). In some implementations, images for biometric
analysis are captured using the image capture device 214, and no
separate biometric capture device is necessary. In such cases, the
biometric analysis may be performed using one or more software
modules (e.g., the biometric analysis module 234, discussed
below).
[0047] Memory 218 includes high-speed random access memory, such as
DRAM, SRAM, DDR RAM, or other random access solid state memory
devices, and may include non-volatile memory, such as one or more
magnetic disk storage devices, optical disk storage devices, flash
memory devices, or other non-volatile solid state storage devices.
Memory 218 may optionally include one or more storage devices
remotely located from the CPU(s) 204 (e.g., a network-connected
storage device or service, such as a "cloud" based storage
service). Memory 218, or alternately the non-volatile memory
device(s) within memory 218, includes a non-transitory computer
readable storage medium. In some implementations, memory 218 or the
computer readable storage medium of memory 218 stores the following
programs, modules and data structures, or a subset thereof: [0048]
an operating system 220 that includes procedures for handling
various basic system services and for performing hardware dependent
tasks; [0049] a communication module 222 that is used for
connecting the client device 102-1 to other computers via the one
or more network communication interfaces 212 (wired or wireless)
and one or more communication networks, such as the Internet, other
Wide Area Networks, Local Area Networks, Personal Area Networks,
Metropolitan Area Networks, VPNs, local peer-to-peer and/or ad-hoc
connections, and so on; [0050] a user interface module 224 that
receives commands and/or inputs from a user via the user interface
206 (e.g., from the input device(s) 210, which may include
keyboard(s), touch screen(s), microphone(s), pointing device(s),
and the like), and provides user interface objects on a display
(e.g., the display 208); [0051] an image capture device module 226
(including, for example, applications, drivers, etc.) that works in
conjunction with the image capture device 214 to capture images,
such as images or scans of physical documents, faces, real-world
scenes, etc.; [0052] a biometric capture device module 227 that
works in conjunction with the biometric capture device 217 (and/or
the image capture device 214) for capturing biometric data of a
user, including data relating to any appropriate physical
characteristic of a user, such as fingerprints, eyes, retinas,
facial features, voiceprints, handprints, etc.; [0053] a
positioning system module 228 that, in conjunction with the
positioning system 216, determines a current location (e.g.,
latitude and longitude, street address, city, state, municipality,
etc.) of the client device 102-1; and [0054] one or more client
application module(s) 230 for enabling the client device 102-1 to
perform the methods and/or techniques described herein, the client
application module(s) 230 including but not limited to: [0055] an
account generation/confirmation module 231 for generating an
account with a service provider, including receiving information
about a user of the client device 102-1 (e.g., name, address,
social security number, password, account recovery
questions/answers, biometric data, login credentials, etc.),
providing this information to a remote device (e.g., the server
104) in order to create a unique user account, and interacting with
the remote device to establish the user's account; the account
generation/confirmation module 231 also facilitates user
confirmation of account information that was provided to a remote
device (e.g., the server 104) by another entity (e.g., a bank), as
described herein; [0056] a data extraction module 232 for
extracting information from documents obtained by the client device
102-1, including extracting computer-readable text from documents,
using optical character recognition to recognize and extract
non-computer readable text from documents, as well as locating and
extracting photographs, images, holograms, laser perforations,
signatures, bar codes, Quick Response (QR) codes, etc., and the
like; [0057] a biometric analysis module 234 for analyzing
biometric data, including determining whether sample biometric data
matches reference biometric data (e.g., for user authentication
purposes), determining whether a photograph of a user extracted
from a document matches a captured photograph of the user (e.g., a
photograph captured by the image capture device 214), determining
whether a voice sample matches a prior approved voiceprint of the
user etc.; [0058] a document analysis module 236 for analyzing
documents (and/or information, photographs, or other content
extracted from documents), for example, to determine whether and/or
to what degree information extracted from the document matches
other information associated with the user (such as the user's
name, date of birth, address, etc.), the quality of content
extracted from the document (e.g., holograms, laser perforations,
etc.), and the like; [0059] a verification rating module 238 for
generating ratings for users, documents, and transactions; [0060]
an encryption/upload module 240 for encrypting documents, biometric
data, verification ratings, extracted data, and the like, and
uploading such information (either encrypted or unencrypted) to a
remote device (such as the server 104); [0061] a request handling
module 242 for receiving requests for information (e.g., from the
server 104, an enterprise device 108-n, and/or another client
device 102-n), providing prompts to a user of the client device
102-1 (e.g., via the user interface 206), receiving partial or full
authorizations or denials of the requests from the user, and
responding to the requests with appropriate responses (e.g., by
communicating with the server 104, an enterprise device 108-n,
and/or another client device 102-n); and [0062] an authorization
management module 244 for enabling a user to view, manage, grant,
change, and/or modify authorizations, including revoking previously
granted authorizations, consents, or acknowledgments.
[0063] In some implementations, the client device 102-1 includes a
subset of the components and modules shown in FIG. 2. Moreover, in
some implementations, the client device 102-1 includes additional
components and/or modules not shown in FIG. 2.
[0064] FIG. 3 is a block diagram illustrating an enterprise device
108-1, in accordance with some implementations. While FIG. 3
illustrates one instance of an enterprise device (i.e., enterprise
device 108-1), the figure and associated description applies
equally to any enterprise device (e.g., 108-1-108-n).
[0065] In some implementations, the enterprise device 108-1 is any
of: a desktop computer, a laptop computer, a tablet computer, a
server computer (or server system), a mobile electronic device, a
mobile phone, a digital media player, or any other appropriate
electronic device (or a kiosk housing any of the aforementioned
devices).
[0066] The enterprise device 108-1 typically includes one or more
CPUs 304, a user interface 306, at least one network communications
interface 312 (wired and/or wireless), an image capture device 314,
memory 318, and at least one communication bus 302 for
interconnecting these components. Each communication bus 302 may
include circuitry (sometimes called a chipset) that interconnects
and controls communications between system components. In some
implementations, the user interface 306 includes a display 308 and
input device(s) 310 (e.g., keyboard, mouse, touchscreen, keypads,
etc.).
[0067] The image capture device 314 is any device that is capable
of capturing an image of a real-world scene or object. In some
implementations, the image capture device 314 is a digital camera
(including any appropriate lens(es), sensor(s), or other
components). In some implementations, the image capture device is a
scanner (e.g., a flatbed scanner). In some implementations, the
image capture device 314 is incorporated into a common housing with
the enterprise device 108-1.
[0068] In some implementations, the image capture device 314 is in
a different housing than the enterprise device 108-1. In one
example, the enterprise device 108-1 is a laptop or desktop
computer, and the image capture device 314 is a separate scanner or
camera that is able to be coupled to the enterprise device 108-1 to
provide images to the enterprise device (e.g., via wired
connection, such as a wired network connection or a Universal
Serial Bus connection, or via a wireless connection, such as WiFi,
Bluetooth, or the like).
[0069] Memory 318 includes high-speed random access memory, such as
DRAM, SRAM, DDR RAM, or other random access solid state memory
devices, and may include non-volatile memory, such as one or more
magnetic disk storage devices, optical disk storage devices, flash
memory devices, or other non-volatile solid state storage devices.
Memory 318 may optionally include one or more storage devices
remotely located from the CPU(s) 304. Memory 318, or alternately
the non-volatile memory device(s) within memory 318, includes a
non-transitory computer readable storage medium. In some
implementations, memory 318 or the computer readable storage medium
of memory 318 stores the following programs, modules and data
structures, or a subset thereof: [0070] an operating system 320
that includes procedures for handling various basic system services
and for performing hardware dependent tasks; [0071] a communication
module 322 that is used for connecting the enterprise device 108-1
to other computers via the one or more network interfaces 312
(wired or wireless) and one or more communication networks, such as
the Internet, other Wide Area Networks, Local Area Networks,
Personal Area Networks, Metropolitan Area Networks, VPNs, local
peer-to-peer and/or ad-hoc connections, and so on; [0072] a user
interface module 324 that receives commands and/or inputs from a
user via the user interface 306 (e.g., from the input device(s)
310, which may include keyboard(s), touch screen(s), microphone(s),
pointing device(s), and the like), and provides user interface
objects on a display (e.g., the display 308); [0073] an image
capture device module 326 (including, for example, applications,
drivers, etc.) that works in conjunction with the image capture
device 314 to capture images, such as images or scans of physical
documents, faces, real-world scenes, etc. [0074] one or more
enterprise application module(s) 328 for enabling the enterprise
device 108-1 to perform the methods and/or techniques described
herein, the enterprise application module(s) 328 including but not
limited to: [0075] one or more account generation module(s) 329 for
generating accounts with a service provider for one or more users
based on information already in possession of the entity operating
the enterprise device 108-1 (e.g., information and documents that a
user has already shared with an institution), the account
generation module(s) 329 including but not limited to: [0076] a
data extraction module 330 for extracting information from
documents obtained by the enterprise device 108-1, including
extracting computer-readable text from documents, using optical
character recognition to recognize and extract non-computer
readable text from documents, as well as locating and extracting
photographs, images, signatures, holograms, laser perforations, bar
codes, Quick Response (QR) codes, etc., and the like; [0077] a
document analysis module 332 for analyzing documents (and/or
information, photographs, or other content extracted from
documents), for example, to determine whether and/or to what degree
information extracted from the document matches other information
associated with the user (such as the user's name, date of birth,
address, etc.), the quality of content extracted from the document
(e.g., holograms, laser perforations, etc.), and the like; [0078] a
verification rating module 334 for generating verification ratings
for documents; and [0079] an encryption/upload module 336 for
encrypting documents, biometric data, verification ratings,
extracted data, user information (e.g., name, address, social
security number, etc.) and the like, and uploading such information
(either encrypted or unencrypted) to a remote device (such as the
server 104); and [0080] one or more information access module(s)
338 for handling requests for user information and handling
information received pursuant to those requests, the information
access module(s) 338 including but not limited to: [0081] a request
handling module 340 for receiving requests from an operator of the
enterprise device 108-1 (and/or automatically generated requests)
for user information, and for communicating the requests for user
information to remote devices (e.g., such as the server 104 and/or
a client device 102-n); [0082] an information receiving module 342
for receiving information associated with a user (e.g., from the
server 104), including but not limited to documents, data extracted
from documents, verification ratings, etc., and for receiving
decryption keys (e.g., from the server 104 and/or a client device
102-n); and [0083] a security/decryption module 344 for determining
access rights to information associated with a user and for
decrypting information associated with a user; and [0084] a user
information database 346 for storing user information (e.g.,
received from the server 104), including but not limited to
documents, data extracted from documents, verification ratings,
decryption keys, etc.
[0085] In some implementations, the enterprise device 108-1
includes a subset of the components and modules shown in FIG. 3.
Moreover, in some implementations, the enterprise device 108-1
includes additional components and/or modules not shown in FIG.
3.
[0086] FIG. 4 is a block diagram illustrating a server 104, in
accordance with some implementations. In some implementations, the
server 104 is any of: a desktop computer, a laptop computer, a
tablet computer, a server computer (or server system), a mobile
electronic device, a mobile phone, a digital media player, or any
other appropriate electronic device (or a kiosk housing any of the
aforementioned devices).
[0087] The server 104 typically includes one or more CPUs 404, a
user interface 406, at least one network communications interface
412 (wired and/or wireless), memory 414, and at least one
communication bus 402 for interconnecting these components. Each
communication bus 402 may include circuitry (sometimes called a
chipset) that interconnects and controls communications between
system components. In some implementations, the user interface 406
includes a display 408 and input device(s) 410 (e.g., keyboard,
mouse, touchscreen, keypads, etc.).
[0088] Memory 414 includes high-speed random access memory, such as
DRAM, SRAM, DDR RAM, or other random access solid state memory
devices, and may include non-volatile memory, such as one or more
magnetic disk storage devices, optical disk storage devices, flash
memory devices, or other non-volatile solid state storage devices.
Memory 414 may optionally include one or more storage devices
remotely located from the CPU(s) 404. Memory 414, or alternately
the non-volatile memory device(s) within memory 414, includes a
non-transitory computer readable storage medium. In some
implementations, memory 414 or the computer readable storage medium
of memory 414 stores the following programs, modules and data
structures, or a subset thereof: [0089] an operating system 416
that includes procedures for handling various basic system services
and for performing hardware dependent tasks; [0090] a communication
module 418 that is used for connecting the server 104 to other
computers via the one or more network interfaces 412 (wired or
wireless) and one or more communication networks, such as the
Internet, other Wide Area Networks, Local Area Networks, Personal
Area Networks, Metropolitan Area Networks, VPNs, local peer-to-peer
and/or ad-hoc connections, and so on; [0091] a user interface
module 420 that receives commands and/or inputs from a user via the
user interface 406 (e.g., from the input device(s) 410, which may
include keyboard(s), touch screen(s), microphone(s), pointing
device(s), and the like), and provides user interface objects on a
display (e.g., the display 408); [0092] one or more server
application module(s) 422 for enabling the server 104 to perform
the methods and/or techniques described herein, the server
application module(s) 422 including but not limited to: [0093] an
account generation module 424 for generating accounts for users
based on information provided (and/or verified) by the users or by
other entities, and storing the accounts (and associated
information) in the user account database 106; [0094] a receiving
module 426 for receiving information from remote devices (e.g.,
client devices 102-n, enterprise devices 108-n), including but not
limited to: documents, verification ratings, data extracted from
documents, account information (e.g., name, address, social
security number, password, account recovery questions/answers,
biometric data, login credentials, etc.), evidence of identity,
etc.; [0095] an optional encryption module 428 for encrypting user
information (including but not limited to transaction data,
documents, verification ratings, data extracted from documents,
account information) for secure storage in the user information
database 106, if the user information was not encrypted before it
was received by the server 104; [0096] a request handling module
430 for receiving and processing requests for information
associated with respective users (e.g., from an enterprise device
108-n), sending authorization requests to the respective users
(e.g., to a client device 102-n), and receiving authorizations from
the respective users (e.g., to allow access to the requested
information or a subset or superset of the requested information);
[0097] an information packaging/encrypting module 432 for
gathering, packaging, and encrypting user information (including
but not limited to documents, verification ratings, data extracted
from documents, account information) to be sent to or otherwise
accessed by a requestor (e.g., an enterprise device 108-n), and for
sending the information to the requestor; [0098] an access
management module 434 for determining whether to allow requesting
entities to access user information (e.g., based on permissions
granted and/or denied by the respective users, time limits imposed
by users and/or regulatory agencies, or any other appropriate
permissions, limits, criteria, etc.); [0099] a user information
database 106 that includes information associated with a plurality
of users; and [0100] a certificate generation module 446 for
generating certificates, such as those described with respect to
FIG. 7.
[0101] FIG. 4 further illustrates a portion of the user information
database 106 relating to a user account 436 for an exemplary user
"n." The user account 436 includes but is not limited to: [0102]
account information 438 associated with the user (e.g., name,
address, social security number, password, account recovery
questions/answers, biometric data, login credentials, etc.); [0103]
document(s) 440 associated with the user, including any appropriate
documents, files, containers, data/content extracted from
documents, etc., as well as archived sets of the above information
and/or documents, enriched sets of documents (e.g., made by
updating existing documents with subsequent updated/revised
versions of the same document); [0104] verification rating(s) 442,
including verification ratings for all or a subset of the
document(s) 440, composite verification ratings (e.g., verification
ratings based on a plurality of tests), a user score, and the like;
and [0105] permission data 444, including active and historical
permissions granted by a user for requesting or authorized
entities.
[0106] In some embodiments, the memory 414 also includes the
certificate database 110 for storing certificates, such as those
described with respect to FIG. 7.
[0107] In some implementations, any or all of the user information
in the user information database 106 and certificate database 110
is encrypted. Moreover, in some implementations, the service
provider does not possess decryption keys for the user information
or certificates. Accordingly, in some implementations the service
provider and/or the server 104 is not able to decrypt, view, read,
or modify user information or certificates. In other embodiments,
users of the system can view certificates but not modify them,
e.g., there is no mechanism for users to edit the original
certificate stored in the certificate database 110.
[0108] In some implementations, the server 104 includes a subset of
the components and modules shown in FIG. 4. Moreover, in some
implementations, the server 104 includes additional components
and/or modules not shown in FIG. 4.
[0109] FIGS. 5A-5D are flow diagrams illustrating a method 500 for
sharing verified identity documents, in accordance with some
implementations. Each of the operations shown in FIGS. 5A-5D may
correspond to instructions stored in a computer memory or computer
readable storage medium. In some implementations, the steps are
performed at an electronic device with one or more processors (or
cores) and memory storing one or more programs for execution by the
one or more processors (or cores). For example, in some
implementations, the steps are performed at any one (or any
combination) of the client device 102-1, the server 104, and the
enterprise device 108-1. Moreover, the individual steps of the
method may be distributed among the multiple electronic devices in
any appropriate manner.
[0110] Any or all of the communications between devices described
with respect to FIGS. 5A-5D are, in some implementations, secured
and/or encrypted using any appropriate security and/or encryption
techniques, including but not limited to Hypertext Transport
Protocol Secure (HTTPS), Secure Sockets Layer (SSL), Transport
Layer Security (TLS), Secure Shell (SSH), Internet Protocol
Security (IPSec), public key encryption, and the like (including
any appropriate yet to be developed security and/or encryption
method).
[0111] An account is created with a service provider (502) (e.g.,
with the account generation/confirmation module 231). In some
implementations, as part of creating the account (i.e., account
enrollment/registration), a user provides to the client device
102-1 identity information, such as a name, gender, date of birth,
address, social security number, residency, etc. In some
implementations, the user provides login information, such as a
username, password, and identity verification questions/responses
(e.g., mother's maiden name, father's middle name, city of birth,
etc.) In some implementations, the user provides other information
as well, such as: a signature (e.g., a photograph/image of a
signature, or a signature input directly into the client device
102-1, such as with a touch-sensitive screen and a stylus), a
photograph, a username, a fingerprint biometric, a voiceprint
biometric, a facial biometric, a zip code, and an account
number.
[0112] The client device 102-1 communicates with the server 104 to
register the user account, which includes the server 104 receiving
and/or storing account information and/or identity information
provided by the user (501) (e.g., with the account generation
module 424).
[0113] The client device 102-1 obtains a document (504). Documents
obtained by the client device 102-1 from a user are provided to
requesting entities to help verify the user's identity. Exemplary
documents include drivers' licenses, national identity cards, birth
certificates, passports, social security cards, marriage
certificates, utility bills, government issued photo identification
cards, and the like. In the present discussion, documents are any
appropriate type of digital file, including computer-readable,
text-based files (e.g., word processing files, spreadsheet files,
computer-generated bills, etc.), or images of physical documents
(e.g., scans, digital photographs, etc.), either of which can be
stored as or represented in any appropriate file type, file format,
etc. (e.g., PDF files, JPEG files, GIF files, TIFF files, DOC
files, etc.). Moreover, where the term "document" is used, the
corresponding discussion may relate to a computer-readable version
of a document, a physical version of a document, or both, depending
on the context of the discussion. One of ordinary skill in the art
will recognize where the discussion relates to computer-readable
versions of a document and where the discussion relates to physical
versions of a document.
[0114] In some implementations, the document is obtained by
capturing a digital image of a physical document (e.g., with the
image capture device 214 and/or the image capture device module
226). For example, where the client device 102-1 is a mobile phone
with a built-in camera, the user takes a snapshot of a document
using the camera. As another example, where the client device 102-1
is a laptop or desktop computer connected to a flatbed scanner, the
user obtains a scan of the document using the scanner.
[0115] In some implementations, the document is obtained by
retrieving it from the memory of an electronic device. For example,
documents may be stored as a digital file in memory associated with
and/or otherwise available to the client device 102-1. Accordingly,
a user can point the client application 230 to a particular
document by navigating to the file via a file browser, or directly
entering a memory location (e.g., file path) of the file. The
client device 102-1 then obtains the document from the specified
location.
[0116] The client device 102-1 extracts data from the document
(506) (e.g., with the data extraction module 232). In some
implementations, extracted data includes identity information
(e.g., name, address, phone number, social security number,
etc.).
[0117] In some implementations, extracted data includes text data.
Text data is extracted either directly from documents having
computer-readable text, or extracted after performing optical
character recognition on an image of a document (or both). In some
implementations, extracted data includes biometric data, for
example, from a photograph contained in the document. Biometric
data is extracted using facial or other biometric
recognition/extraction techniques. Other data may be extracted as
well, including images of a signature, images of the user, other
images, holograms, laser perforations, bar codes, QR codes,
etc.
[0118] The client device 102 then determines that the identity
information extracted from the document substantially matches the
identity information associated with the user's account (508)
(e.g., with the document analysis module 236). For example, the
extracted identity information (e.g., the name extracted from a
drivers' license) is compared to the user's account (e.g., the name
that the user supplied when creating the account) to confirm that
the document is associated with the account holder (i.e., the
information on the two documents matches or substantially matches).
Thus, if a user attempts to upload someone else's drivers' license,
the client device 102-1 recognizes that the document is not
associated with the user, and can reject the document, reduce or
adjust a verification rating for that document, flag the document,
request corroborating or additional information, or take other
remedial actions.
[0119] In some implementations, the client device 102-1 performs
one or more additional tests of the document (e.g., with the
document analysis module 236). For example, in some
implementations, the client device 102-1 determines whether a dated
document (e.g., a utility bill or any other document having an
issue date, mailing date, expiration date, due date, etc.) was
issued within a predetermined recency window with respect to the
current date (e.g., 30, 60, or 90 days, or any other appropriate
window). As another example, in some implementations, the client
device 102-1 identifies, from the data extracted from the document,
an expiration date of the document, and determines whether the
expiration date of the document is after a current date (i.e., the
document has not expired). In these examples, the current date may
be determined by referencing a system date of the client device
102-1, or calling out to a remote device or service (e.g., the
server 104, a telecommunications service) and receiving a current
date. Such tests can help ensure that a user does use old or
outdated documents, which may be an indicator that the information
contained thereon is not accurate. Other tests may also be
performed.
[0120] In some implementations, the client device 102-1 determines
whether a system date of the client device substantially matches a
reference date provided by a remote device. This test can help
identify attempts to tamper with the system date of the client
device 102-1, which may be attempted by users to enable them to
upload a document that is out-of-date or expired. If the system
date of the client device does not substantially match the
reference date, remedial measures can be taken. For example, the
client device 102-1 and/or the server 104 will prevent the user
from uploading the document, adjust a verification rating for the
document, flag the user's account for further review or scrutiny,
or the like.
[0121] In some implementations, if the document meets the criteria
of the additional tests, the document is permitted to be uploaded
to the user's account, and if the document does not meet the
criteria of the additional tests, the document is rejected and
cannot be uploaded to the user's account. In other implementations,
the document is uploaded to the user's account regardless of
whether the criteria are met, but the verification rating
(discussed below) is adjusted or otherwise reflects whether or not
(or the degree to which) the criteria are satisfied.
[0122] The client device 102-1 then generates at least one
verification rating for the document (510) (e.g., with the
verification rating module 238). The verification rating, discussed
in greater detail below, indicates a degree of confidence that the
document is authentic and/or is actually associated with the user.
In particular, the accuracy of identity verification is limited by
the level of trust that can be placed on the authenticity of the
documents. For example, a fraudulent drivers' license or passport
cannot be trusted to accurately identify the person who is
presenting it. Accordingly, the client device 102-1 performs one or
more tests on the document (i.e., the image of the document) to
determine its authenticity and whether it actually identifies the
user. One specific example of such a test is a comparison between
biometric data in a photograph on the document and biometric data
in a photograph of the user captured by the client device 102-1,
which is performed by the biometric analysis module 234. If it is
determined that a face in the photograph from the document matches
the recently captured photograph of the user, there is a higher
likelihood that the drivers' license is associated with the person
in the photograph, and the verification rating will reflect this
higher confidence (e.g., with a relatively higher rating). On the
other hand, if the faces do not match (or if they match to a lesser
degree), then the verification rating will reflect this lower
confidence (e.g., with a relatively lower rating).
[0123] In some implementations, verification ratings are generated
by the client device 102-1 alone. Thus, the documents, which
contain sensitive identity information, do not leave the possession
of the user. In some implementations, if other devices are used to
assist in generating verification ratings (e.g., the server), any
information sent to the other devices is encrypted, obfuscated,
and/or stripped of any identifying information, so that the user's
privacy and the security of the documents is maintained.
[0124] In some implementations, the client device 102-1 encrypts
the document, the extracted data, and the verification rating (512)
(e.g., with the encryption/upload module 240). The client device
102-1 then sends the document, extracted data, and the rating
(e.g., one or more encrypted data files) to the server 104 at step
(514) (e.g., with the encryption/upload module 240).
[0125] In some implementations, the client device 102-1 generates
one or more containers (i.e., containers) including any combination
of the document, the extracted data, and the verification rating,
and sends the container(s) to the server 104 at step (514). In some
implementations, containers are collections of individual files
(e.g., a zip file). In some implementations, containers are complex
data structures that include information from which one or more
different files and/or documents (including, for example, an image
of a document, data extracted from a document, and the like) can be
extracted or constructed, even though the files and/or documents
are not represented in the containers as discrete files.
[0126] In some implementations, the one or more containers include
at least a first file that includes the document and a second file
that includes the information extracted from the document. In some
implementations, the one or more containers include a third file
that includes the at least one verification rating. In some
implementations, the at least one verification rating includes a
plurality of verification ratings (e.g., including a verification
rating for each document in the one or more containers, composite
verification ratings, a user score, etc.). (Where the container is
a complex data type, the container includes data from which such
files and/or information can be extracted/constructed, as discussed
above).
[0127] In some implementations, the client device 102-1 performs
steps (504)-(514), or a subset thereof, for one or more additional
documents. For example, images of multiple documents are captured
(504), and, for each document, the client device 102-1 extracts
data (506), determines that the identity information matches (508),
generates a verification rating (510), encrypts the document,
rating, and extracted data (512), and sends these items to the
server (514). In some implementations, these multiple documents are
combined in the container for sending to the server.
[0128] The server 104 receives the document, extracted data, and
the rating (516) (e.g., with the information receiving module 342,
FIG. 3). In some implementations, these items are received as a
container, as described above.
[0129] In some implementations, user accounts are assigned a
status, which reflects particular information about the account,
and determines how the account and/or the information and documents
associated with the account can be used. In some implementations,
the status of an account reflects whether the account includes a
required amount and/or type of documents and user information, or
whether the account is deficient in one or more areas. In some
implementations, if the account includes the required documents
and/or information, its status is "complete," and if the account is
deficient in one or more ways, its status is "pending." Other
statuses, and other labels for the described statuses, are also
assigned to accounts in various implementations.
[0130] In some cases, an account is considered "complete" if it
includes a government issued photo identification document and a
utility bill, as well as a name and address of the user. In other
implementations, more or fewer documents or items of information
are required in order for an account to be considered complete. The
particular documents and/or information that amount to a "complete"
account is, in some cases, determined based on regulations, laws,
guidelines, or customs of an applicable jurisdiction. In some
implementations, the jurisdiction is a jurisdiction of the account
holder, a jurisdiction of an institution or entity that is
requesting the documents/information, a jurisdiction governing a
transaction between an account holder and a requesting institution
or entity, or any other appropriate jurisdiction or combination of
jurisdictions.
[0131] In some cases, an account is considered "pending" if the
account lacks particular documents or items of information that are
required of a "complete" account. An account can also be assigned a
"pending" status based on other conditions. For example, an account
can be "pending" if a document or item of information is expired or
otherwise out of date. As a specific example, if a passport
associated with a user account becomes expired after it is uploaded
to the user's account, the account is assigned a "pending" status.
As another example, if there is no recent utility bill (e.g.,
mailed/issued within 90 days of a current date) associated with the
account, the account is assigned a "pending" status. Other
conditions can also cause an account to be assigned a "pending"
status, in various implementations.
[0132] In some implementations, only a "complete" account can be
used by a user to share documents with other parties. Thus, if a
user's account is "pending," the user must provide the missing
document(s), information, or perform the required tests (discussed
herein) in order to complete the account before the user can
authorize other parties to access his or her documents and/or
information.
[0133] The foregoing discussion describes how users create accounts
and upload documents with the client device 102-1. In particular,
the client device 102-1, along with one or more modules in the
memory 218, performs steps (502) through (514). In some cases,
however, other users of the system can create accounts for other
users. For example, an institution may decide to use a service
provider to access identity verification information for
individuals or other entities with whom the bank transacts.
Accordingly, the institution may wish to create accounts for some
or all individuals for whom it already has identity information,
identification documents, and the like. Accordingly, in some
implementations, an enterprise device 108-1 includes an account
generation module 329 for creating accounts for multiple users. In
particular, the enterprise device 108-1 uses the account generation
module 329 to perform steps (502-m) through (514-m). Steps (502-m)
through (514-m) are analogous to steps (502) through (514), and are
performed using modules analogous to those modules of the client
device 102-1 that perform those steps on the client device, as
described above (e.g., including the data extraction module 330,
the document analysis module 332, the verification rating module
334, and the encryption/upload module 336, FIG. 3).
[0134] While an institution can create an account for a user, in
some implementations, until the account is complete (i.e., contains
all the information and/or documents required to establish a
complete account), or until the user approves the account and the
information and/or documents associated with the account, the
account is given a "pending" status. Once the institution and/or
the user complete the account (e.g., by providing any missing
information and/or documents, and/or by approving information
and/or documents uploaded by the institution), the account is given
a "complete" status.
[0135] In some implementations, accounts created for users by an
institution are not uploaded to the service provider (i.e., the
server 104) until the user associated with the account has approved
and/or completed the account. This way, the server 104 does not
need to store and/or manage incomplete and/or pending accounts that
will never be completed and/or approved by a user (e.g., because
the user does not wish to or has no need to establish the account,
or any other appropriate reason). Instead, account information for
such accounts is stored in memory associated with the enterprise
device 108-1 (e.g., the user information database 346).
[0136] Turning to FIG. 5B, in implementations where the document,
verification rating, and extracted data were not encrypted by the
client device 102-1 (or the enterprise device 108-1) prior to being
sent to the server 104, they are encrypted by the server 104 for
storage (518) (e.g., with the encryption module 428).
[0137] The server 104 stores the document, extracted data, and the
verification rating (520) (e.g., in the user information database
106). In some implementations, where the information is encrypted
on the client device 102-1 prior to being sent to the server 104,
the server 104 is unable to decrypt the information. Accordingly,
users can be assured of the privacy and security of their
information, while institutions (and other requesting entities) can
be assured that the information has not been tampered with or
otherwise altered (or even viewed) by the service provider.
[0138] When an institution wishes to access the documentation
and/or information necessary in order to verify the identity of an
individual, an operator uses the enterprise device 108-1 to request
information associated with the individual, and the enterprise
device 108-1 receives this request (522) (e.g., with the request
handling module 340). In some implementations, the user requests a
particular set of documents and information (i.e., distinct
information items associated with the user account). For example, a
bank may request information such as the user's name, home address,
social security number (all of which may be stored by the service
provider as part of the user's account information), as well as an
image of the user's drivers' license and a recent utility bill and
verification ratings for those documents.
[0139] In some embodiments, the information requested 522 by the
enterprise device (e.g., a bank) is simply an authorization,
consent or acknowledgment from the client device.
[0140] In some implementations, the request includes access limits
relating to the scope of the access that is to be granted to the
requestor, such as a window of time in which the requestor will be
permitted to access the information, the number of times that the
requestor will be permitted to access the information, etc. In some
implementations, the requestor includes such information in its
request to the server 104. For example, a bank may request a user's
drivers' license and recent utility bill, and specify that it needs
to access this information only once. Alternatively, a bank may
request this information and specify that it needs to access
updated copies of it at any time (and as many times as desired)
while the account remains open and/or for a specified length of
time (e.g., as specified by a user). Other appropriate access
limits or time windows (or any other constraints on access to the
information) are envisioned as well.
[0141] The enterprise device 108-1 then sends the request for the
information to the server 104 at step (524) (e.g., with the request
handling module 340).
[0142] The server 104 receives the request for information
associated with the account of the user (e.g., the information
including at least one of a document, data extracted from a
document, and at least one verification rating; or the information
including a request for authorization) from the enterprise device
108-1 at step (526) (e.g., with the request handling module 430),
and sends a request to the client device 102-1 requesting
authorization (e.g., to release the requested information to the
requestor) (528) (e.g., with the request handling module 430). In
some implementations, the client device 102-1 provides a
notification or alert indicating that a request has been received
or is available to be viewed. In some implementations, the
notification or alert is or is included in an email, text message,
application alert, or any other appropriate message using any
appropriate messaging technique or protocol. In some
implementations, the server 104 sends the notification or alert to
the client device 102-1 before sending the request to the client
device 102-1, and the request is sent to the client device 102-1
once the user logs in to his or her account via the client device
102-1 (e.g., in response to the notification or alert).
[0143] The client device 102-1 receives the authorization request
(530). The user securely logs onto the client device and can then
review the request. The client device 102-1 then prompts the user
to partially or fully authorize or deny access to the requested
information (e.g., with the request handling module 242) or provide
authorization or consent. If the client device 102-1 receives
authorization from the user (532), it sends an authorization to the
server 104 (e.g., to release the authorized information to the
requestor) (534, FIG. 5C) (e.g., with the request handling module
242). In some implementations, the authorization request that is
presented to a user identifies particular documents and/or
information being requested. Furthermore, in some implementations,
the authorization request identifies the access limits (or lack
thereof) requested by the requestor. For example, as described
above, the request may state that a bank has requested access to
the user's drivers' license and a utility bill, and that they want
to be able to view (or download an updated copy of) the documents
at any time while the user has an account with the bank, or for any
other specified time. Thus, in some embodiments, the user is able
to determine whether or not to allow access according to the
request.
[0144] In some implementations, the information requested and/or
the access limits are non-negotiable. For example, a bank may be
required by law to maintain records of certain information of the
entities with which it transacts. Accordingly, should the user deny
access to that information, the bank will be unable to engage in
the subject transaction (e.g., opening a bank account, line of
credit, etc.).
[0145] On the other hand, in some implementations, the information
requested and/or the access limits are negotiable and/or selectable
by the user. For example, a bank may request access to more
information and/or fewer access limits than are strictly necessary
for a particular transaction or relationship. The user can then
refuse to authorize the full scope of the request, and instead
authorize access to fewer or different documents and/or
information, as well as different access limits. In some
implementations, the user is informed of any minimum access
requirements necessary for a particular transaction so that the
user can make an informed decision as to what access limits to
allow.
[0146] In some implementations, a request includes multiple
different authorization request packages, each including a
different combination of requested documents, information,
authorizations, consents, and/or access limits, and the user
selects which authorization request package to approve. Here too,
the user can be informed of the minimum document and access
requirements necessary for the requesting entity to be able to
engage in a particular transaction.
[0147] Continuing on FIG. 5C, the server 104 receives the
authorization to release the information to the third party (536)
(e.g., with the request handling module 430).
[0148] The server 104 then creates an information package including
the requested information (538) (e.g., with the information
packaging/encrypting module 432). For example, the server 104
locates the requested documents, extracted data, verification
ratings, etc., and, if necessary, extracts/constructs these items
from a container. The information package is any appropriate file,
container, composite file, or group of separate files that contain
the requested information.
[0149] In some implementations, the server 104 encrypts the
information package (540) (e.g., with the information
packaging/encrypting module 432). In some implementations, the
information that constitutes the information package is already
encrypted (e.g., having been encrypted by the client device 102-1,
the server 104, or the enterprise device 108-1 prior to being
stored in the user information database 106). In some
implementations, client-based encryption can only be decrypted by a
key generated by and/or known to the client device 102-1.
Accordingly, in some implementations, the server 104 does not
encrypt the information package at this stage.
[0150] However, in some implementations, the server 104 encrypts
the already-encrypted information again at step (540). This
secondary encryption can be used to enable and/or enforce access
limits by providing an encryption layer that is controlled by the
server 104. For example, as described herein, the enterprise device
108-1 may have to receive authorization from the server 104 each
time it wants to view the information that it receives, even if the
information is stored locally on the enterprise device 108-1.
Accordingly, the enterprise device 108-1 communicates with the
server 104 in order to obtain the necessary permissions (and/or
decryption keys or codes) before it can access the information.
[0151] Returning to FIG. 5C, the server 104 sends the information
package to the enterprise device 108-1 (542) (e.g., with the
information packaging/encrypting module 432). In some
implementations where the server 104 encrypted the information
(540), the information package is sent with a first decryption key
that is able to decrypt the information package. On the other hand,
in some implementations, the first decryption key is not included
with the information package even if it was encrypted by the server
at (540). In such cases, the enterprise device 108-1 receives the
decryption key at a later time, such as when an operator of the
enterprise device attempts to access and/or view the
information.
[0152] In some embodiments, the information package merely includes
an authorization or consent together and other optional
information, such as a verification rating, transaction rating,
etc.
[0153] In some embodiments, the enterprise device 108-1 receives
the information package, and the optional first decryption key
(544) (e.g., with the information receiving module 342). In some
implementations, the enterprise device 108-1 stores the information
package in a local database 346, for example, to satisfy record
keeping requirements and regulations. Even when the information is
stored in a local database, in some implementations, the enterprise
device 108-1 cannot view the information without first
communicating with the server 104 to determine whether it is
permitted to do so, as discussed herein.
[0154] As noted above, if the user approves a request for
information, the client device 102-1 sends an authorization message
to the server 104 (534). In some implementations, if the user
approves the request for information (or a subset or superset of
the information), it also generates a second decryption key for
decrypting the requested information (546) (e.g., with the
encryption/upload module 240). In some implementations, the
decryption key is generated prior to receiving the authorization
request.
[0155] In some implementations, the client device 102-1 must
generate the decryption key, because it is the only device that can
do so. That way, view access to the information remains under the
control of the user, and only the user and entities authorized by
the user can decrypt and view the information.
[0156] In some embodiments, the client device 102-1 sends the
second decryption key to the enterprise device 108-1 (e.g., with
the encryption/upload module 240). The enterprise device 108-1
receives the second decryption key (550) (e.g., with the
information receiving module 342).
[0157] In some embodiments, the enterprise device 108-1 then
decrypts the information package (552) (e.g., with the
security/decryption module 344). In some implementations,
decrypting the information includes first decrypting the
information package using the first decryption key (to remove the
encryption applied by the server 104), and then decrypting the
information contained in the information package with the second
decryption key (to remove the encryption applied by the client
device 102-1).
[0158] Turning to FIG. 5D, the enterprise device 108-1 receives,
from an operator, a subsequent request for the information package
(554) (e.g., with the request handling module 338), and sends the
subsequent request for the information package to the server 104
(556) (e.g., with the request handling module 338). In some
implementations, the subsequent request for the information package
is a request for all of the information that was in the original
request. In other implementations, the subsequent request includes
a request for only a subset of the information in the original
request.
[0159] Moreover, requests may also specify that the information
should include the most up-to-date versions of the requested
information. Thus, if the user has uploaded a new drivers' license
or utility bill since the information was previously received, the
new information will be provided (subject to the access permissions
associated with the original request). On the other hand, the
request may also specify that the information should include the
information as it was at the time of the original request. In some
implementations, whether a requesting entity is permitted to access
updated versions of documents and information (or whether they are
only permitted to access the versions available at the time of the
original request) is specified in the access permissions discussed
with respect to steps (524)-(532).
[0160] The server 104 receives the subsequent request for the
information package (558) (e.g., with the request handling module
430), and determines access permissions (560) (e.g., with the
access management module 434). For example, the server 104
determines whether the subsequent request is permitted by the
original authorization from the user. The access permissions
include content permissions (e.g., whether the requestor is
permitted to access a particular document, rating, or other
information), and/or time/frequency permissions (e.g., whether the
request satisfies time window and/or access frequency limits
imposed by the user).
[0161] If access is permitted (562, Yes), then the server 104
provides access to the requested information (564). In some
implementations, providing access (564) includes packaging,
encrypting, and sending the requested information to the enterprise
device 108-1 as in steps (538)-(544). In some implementations,
providing access (564) includes providing a decryption key (or
other access token) to enable the enterprise device 108-1 to
decrypt or otherwise access information that is already stored by
the enterprise device 108-1 (e.g., in the user information database
346). The enterprise device 108-1 then accesses the information
package (566).
[0162] If access is not permitted (563, No), then the server 104
denies access to the requested information (568) (e.g., with the
access management module 434).
[0163] As noted above, verification ratings are generated for
documents obtained by the client device 102-1 or by the enterprise
device 108-1. Verification ratings are based on, derived from, or
otherwise reflect the results of one or more tests. Verification
ratings, in some implementations, indicate a degree to which a
document is authentic and/or actually relates to a particular user.
As an example, a document that appears to be a forgery will likely
have a lower rating than a document that does not appear to be a
forgery. As another example, a document that appears to be expired
will likely have a lower rating than one that is still valid. As
yet another example, a document that appears to indicate an address
that is different than the user's current location will likely have
a lower rating than one that has an address falling at or near the
user's current location. Because verification ratings can reflect
the results of various different tests and/or characteristics, the
foregoing descriptions of how test results affect the verification
rating are merely exemplary, and are not necessarily dispositive of
how any particular verification rating will be affected by the
various results. For example, a document that has a high likelihood
of being a forgery, but all of the information on the document is
otherwise correct (e.g., a name and address on the document match
the user's account information, and a photograph on the document is
a biometric match to a photograph of the user) may actually have a
higher rating than a document that does not appear fraudulent, but
includes information that does not match that of the user's account
(e.g., the name, address, and biometric information indicates that
the document does not relate to the user at all).
[0164] In some implementations, each of a plurality of tests
performed on or for a document results in a distinct verification
rating, and all of the verification ratings for the document are
combined to create a composite verification rating for the
document. The composite verification rating is generated in any
appropriate manner, including using an average (e.g., an arithmetic
mean, weighted mean, etc.) of the verification ratings generated by
each respective verification test, an algorithm, or any other
appropriate combination of verification ratings and/or other
information (e.g., summing the results of each test).
[0165] Verification ratings for each test employ any appropriate
rating or scoring scale. For example, in some implementations,
verification ratings use a numeric scale, such as 1-100, 1-10, 1-5,
or any other appropriate range (e.g., a letter grade range, such as
A-F, A-Z, etc.). Such scales are used for tests that produce a
range of results and/or indicate a level or degree of satisfaction
of one or more criteria. As one specific example, a test that
determines the extent to which a photograph extracted from a
document matches a reference photograph of a user can be rated
using a scale (e.g., based on the matching algorithm, a rating of
100% indicates a good match, 70% indicates a partial match, 0%
indicates a low or zero likelihood of match).
[0166] In some implementations, verification ratings are binary or
"pass/fail" (which may be indicated in any way, such as with a
check mark or green circle for pass, and an "X" or a red circle for
fail). In such cases, whether a document is assigned a pass or a
fail rating is based on any one or more tests of the document
and/or its contents. Specific examples of tests are described
herein.
[0167] In some implementations, tests result in both a "pass/fail"
rating and a numerical rating (e.g., between 1 and 100). In some
implementations, whether a test results in a pass or fail rating is
based on the numerical rating (e.g., lower than 50 out of 100
results in a fail).
[0168] Moreover, in some implementations, composite verification
ratings are generated for documents. The composite verification
rating is based at least partially on a plurality of verification
ratings from a plurality of tests (as described herein). Composite
verification ratings are created from any appropriate combination
of the verification ratings from individual tests. For example, a
composite verification rating can be an average of individual
verification ratings, or an additive rating (e.g., each individual
rating is based on a 0-10 scale, and the composite rating is the
sum of all individual ratings).
[0169] In some implementations, a "user score" is generated for a
user's account, based at least in part on the verification ratings
(and/or composite verification ratings) of the documents associated
with a user. In some implementations, the user score is also or
instead based on other information, such as the completeness of a
user account, third party identity verifications/corroborations,
etc.
[0170] In some implementations, the user score also reflects the
various types of documents that have been provided by a user. For
example, if a user provides documents that were not issued by a
government (e.g., utility bills, student identification cards,
credit cards, etc.), the user score will be lower than if the user
has provided government issued documents (e.g., a passport,
drivers' license, etc.).
[0171] As noted above, various tests can be applied in various
implementations to generate verification ratings. Exemplary tests
are discussed below. Each test may affect the verification rating
in various ways. For example, some tests result in a qualitative
analysis of a document, such as a confidence value, a quality
value, a rating, or the like. In such cases, verification ratings
may be at least partially based on and/or reflect the results of
the qualitative analysis. For example, in some implementations, a
verification rating is scaled based on the results of the
qualitative analysis, such that a lower result reduces the
verification rating for a document, and a higher result increases
(or does not affect) the verification rating.
[0172] Some tests result in a quantitative and/or discrete result,
such as whether or not a match is determined, whether or not an
expected result is found, or the like. Similarly, in some cases,
qualitative analysis results are compared against threshold
conditions, resulting in a discrete result (e.g., the threshold
condition is either satisfied or it is not). In some
implementations, discrete results reduce and/or increase a
verification rating, depending on the result (e.g., a failed test
reduces a verification rating by a predetermined amount). In some
implementations, discrete results act as a threshold for acceptance
of the document. For example, if a document does not satisfy a
particular threshold (e.g., an expected watermark is absent), the
document is rejected and no verification rating is provided for the
document (e.g., because it is likely that the document is
fraudulent).
[0173] The tests described herein can be combined in any
appropriate way. For example, in some implementations, some tests
are used to generate a numerical verification rating, while others
are used to determine whether to accept or reject a document (e.g.,
pass/fail conditions). Moreover, verification ratings for documents
are sometimes described as being "based on" the results of one or
more of the following tests. As used herein "based on" means either
"exclusively based on" (i.e., based only on), or "at least
partially based on."
[0174] Address Confirmation
[0175] In some implementations, residency and/or address
information extracted from documents is compared against location
information of the user. In particular, in order to confirm that a
user actually resides at the address shown on a document, the
address from the document is compared against the current location
of the user's device (e.g., as determined by GPS, cell-tower
triangulation, IP address geolocation, or the like). In such cases,
the verification rating of the document is based at least partially
on whether or the degree to which the address matches the current
location of the user's device.
[0176] Different levels of precision can be used for address
confirmation, depending on the particular application or use case.
For example, in some cases, it is desired to determine the country
of residence of a user. Accordingly, it is not necessary that the
user's address exactly match the user's current location. Rather,
it is enough that the user's current location is anywhere within
the country identified by the user's address. In other cases, it is
desired to determine that the user actually lives at the location
identified by the user's address. In such cases, it is necessary to
determine that the user's current location is within a
predetermined distance of the user's address, such that it is
likely that the user actually lives at that address. For example,
in some implementations, a user's current location is determined to
match a purported address if the current location is within 100
feet of a location associated with the user's address (e.g.,
latitude and longitude values associated with the address). Other
distances are also contemplated (e.g., 500 feet, 1000 feet, 1 mile,
5 miles, 10 miles, or any other appropriate distance).
[0177] In addition to comparing the user's actual location with the
location from a given document, in some implementations, a user
score is based on the consistency of the addresses of multiple of a
user's documents. In particular, if all of the user's documents are
associated with a same location (e.g., a same address, city, state,
region, country, etc.), the user score will be higher. Moreover, in
some implementations, verification ratings of individual documents
reflect whether the address of that document matches addresses of
other documents. For example, if a user's passport and drivers'
license specify one address, and a user's utility bill specify a
different address, then the verification rating for the utility
bill (and/or the passport or drivers' license) will reflect the
discrepancy (e.g., by lowering the rating for that document or
rejecting that document altogether). The client device 102-1 also,
in some implementations, looks up an address associated with the
user in a separate database in order to compare to an address on
one or more documents and/or a current location of the client
device 102-1. For example, the client device 102-1 retrieves an
address for a user from a credit score database, from online
address resources (e.g., yellow or white pages), from a social
media portal, etc.
[0178] FIG. 6 is a flow diagram illustrating a method 600 for
verifying a document based on the user's current location, in
accordance with some implementations. Each of the operations shown
in FIG. 6 may correspond to instructions stored in a computer
memory or computer readable storage medium. In some
implementations, the steps are performed at an electronic device
with one or more processors (or cores) and memory storing one or
more programs for execution by the one or more processors (or
cores). For example, in some implementations, the steps are
performed at any one (or any combination) of the client device
102-1, the server 104, and the enterprise device 108-1. Moreover,
the individual steps of the method may be distributed among the
multiple electronic devices in any appropriate manner.
[0179] The client device 102-1 obtains a document (602) (e.g., with
the image capture device module 226). Additional details related to
obtaining documents are discussed above with respect to step (504)
of FIG. 5A.
[0180] The client device 102-1 extracts data from the document, the
extracted data including extracted location information (604)
(e.g., with the data extraction module 232). Extracted location
information includes, for example, an address included in the
document (e.g., a mailing label, an address field of an
identification document, etc.), country of residence information
(e.g., extracted from a drivers' license or passport number or
country code, etc.), and the like.
[0181] The client device 102-1 determines a current location of the
client device (606) (e.g., with the positioning system module 228).
In some implementations, the current location of the user's device
is determined using GPS, cell-tower triangulation, IP address
geolocation, or the like.
[0182] The client device 102-1 compares the current location of the
client device with the extracted location information (608) (e.g.,
with the document analysis module). The client device 102-1
determines a degree to which the current location of the client
device matches the extracted location information (610) (e.g., with
the document analysis module).
[0183] In some implementations, as described above, the degree to
which the current location of the client device matches the
extracted location information is a pass/fail result: if the
current location is within a predetermined distance of the
extracted location information, the locations are determined to
match; if the current location is beyond the predetermined
distance, the locations are determined not to match. Also, the
resolution of the extracted location information is selected
according to the particular application. For example, in some
cases, it is only necessary or desired to determine that the user
is in the state, region, or country indicated by an address
extracted from a document. In other cases, it is necessary or
desired to determine that the user is within a predetermined
distance of the actual address extracted from the document.
[0184] In some implementations, the client device 102-1 generates a
verification rating based on the degree to which the current
location of the client device matches the extracted location
information (612) (e.g., with the verification rating module 238).
In some implementations, instead of (or in addition to) determining
the degree to which the current location of the client device
matches the extracted location information, the client device 102-1
determines the degree to which a historical record of locations of
the client device 102-1 matches the extracted location information.
For example, the client device 102-1 prompts a user to allow access
to historical location information (e.g., for a certain time
period, such as 1 year), and if the user allows access, the client
device 102-1 determines how long or how frequently the client
device 102-1 was at or near the location identified by the
extracted location information, and generates or adjusts the
verification rating based thereon.
[0185] In some implementations, the client device 102-1 generates a
verification rating based on the degree to which the current
location of the client device matches a historical set of extracted
location information (e.g., the degree to which the current
location matches the address information extracted from a plurality
of previously uploaded documents).
[0186] Photograph Comparison
[0187] Documents that include photographs (e.g., drivers' licenses,
passports, government issued photo identification cards, etc.) are
analyzed to determine whether the photograph in the document
matches a photograph of the user. In some implementations, a user
provides one or more reference photographs of him or herself. The
reference photographs can be captured by an imaging device
associated with a client device (e.g., a smartphone camera, a
webcam or a scanner coupled to a computer, etc.), or uploaded to
the client device (e.g., received as a digital image file in some
other way). In some implementations, references photographs are
captured from different angles, with different facial expressions,
and with different lighting, in order to increase the quality of
the photographic analysis.
[0188] The photograph from the document is then compared to the
reference photograph(s) to determine if they substantially match.
The comparison uses facial recognition techniques, such as
comparing, between the photograph from the document and the
reference photograph biometric information such as: the structure,
shape, and proportions of the face; the absolute and/or relative
location of the nose and eyes; the distance between the eyes, nose,
mouth, and jaw; the upper outlines of the eye sockets; the sides of
the mouth; and the area surrounding the cheek bone. Biometric
information is extracted from the document photograph and the
reference photograph.
[0189] In some implementations, the user captures a photograph that
includes both their face and the document that contains a
photograph. The user's face is then compared to the photograph in
the document using one or more of the above techniques (or a
technique not listed) to determine whether the photograph matches
the user, and the verification rating is based at least in part on
a degree of match between the biometric information from the
photograph of the user and the biometric information from the
reference photograph
[0190] In some implementations, a confidence value that the
individuals in both photographs are the same is calculated based on
one or more photographic analysis techniques, including but not
limited to those listed above. In some implementations, the
confidence value is reflected in a verification rating for a
document that contains the photograph.
[0191] In some implementations, multiple reference photographs of a
user are captured. For example, a client may be asked to capture
photographs of themselves from different angles, under different
lighting conditions, with or without glasses or other obstructions,
with different facial expressions, or the like. In some
implementations, a device walks a user through the process of
obtaining a certain set of photographs, for example, using visual
and/or audio prompts (e.g., showing images or graphics of exemplary
photographs, etc.).
[0192] In some implementations, in order to facilitate comparison
between photographs, a device includes components and/or
application modules for performing imaging techniques, such as
image rectification, creation/calculation of depth maps,
calculation of reflectivity, and the like.
[0193] Security Feature Analysis
[0194] Some documents include security features such as watermarks,
holograms, ghost photos/images, optically variable inks, and/or
pigments that are sensitive to and/or reflect certain types of
illumination and/or radiation. For example, many government issued
photo identification documents (e.g., drivers' licenses, passports,
etc.) include such security features. In order to detect and/or
capture a suitable photograph of these items, the documents need to
be exposed to appropriate types of radiation while the photograph
is captured. In some implementations, users are prompted to capture
one or more photographs of such documents while exposing it to a
particular type of radiation or radiation source.
[0195] In some implementations, users capture an image of a
document while exposing the document to an infrared radiation
source (e.g., a remote control for a television, stereo, DVD
player, or the like). In some implementations, users capture an
image of a document while exposing the document to an ultraviolet
radiation source (e.g., ultraviolet daylight bulbs, ultraviolet
flashlights, "black lights," etc.).
[0196] For documents that include holograms, users capture a series
of photographs or a short video while a camera flash is on (e.g., a
flash incorporated with a cell-phone camera). In some
implementations, the flash is controlled (e.g., by an application
module) so that different flash outputs are used for different
photographs. Reflectivity values for the hologram across the series
of photographs or short video are analyzed to determine that they
satisfy a particular condition (e.g., that the difference in
reflectivity between given images substantially conforms to an
expected value).
[0197] Some documents include text and/or images that must be
viewed through a polarizing filter in order to be successfully
analyzed. In such cases, users capture an image of the document
through a polarizing filter, such as polarized sunglasses or a
polarized photographic filter.
[0198] Some documents include laser perforations. In order to
detect such perforations (which are often so small that they cannot
be detected when the document is front-lit), the user captures a
photograph of the document under back-lit conditions (e.g., held up
to a light bulb) so that the laser perforations can be detected.
The laser perforations are then analyzed to determine their quality
and/or whether they match an expected pattern or content. In some
implementations, the expected content of a laser perforation
depends on the issuing authority of the document (e.g., the country
that issued a passport).
[0199] Some security features do not require special radiation
and/or illumination for accurate photographic analysis, such as
rainbow and/or guilloche printing. In some implementations, a user
captures a photograph of a document that includes rainbow and/or
guilloche printing, and the printing is analyzed to determine its
presence and/or quality. In some implementations, the quality of
rainbow and/or guilloche printing is based on the resolution,
colors, detail, shape, or size of the printing, or whether it
matches an expected pattern and/or content (and/or any other
appropriate metric). In some implementations, verification ratings
are based on and/or reflect the quality and/or presence of the
security features described above.
[0200] Zone Comparison
[0201] Some documents include multiple different zones, where one
zone includes the same and/or a subset of the information in one or
more other zones. For example, passports include a "visual zone"
and a "machine-readable zone." The "visual zone" lists certain
information, such as the user's name, address, passport number, and
the like in a format that is easily readable by a human. The
"machine-readable zone" includes information such as the user's
name, passport number, date of birth, country, etc., in a format
that is easily readable by a machine.
[0202] In some implementations, photographs of documents having
multiple zones are analyzed to determine whether the information in
the various zones match. For example, a user captures a photograph
of a document that includes multiple zones. Optical character
recognition ("OCR") is then performed (using any suitable OCR
technique) on all or a subset of the zones (e.g., the "visual zone"
and the "machine-readable zone" of a passport), and the information
contained in the zones is compared. In some implementations,
verification ratings are based on and/or reflect the degree to
which information in each of the multiple zones match.
[0203] In some implementations, a "machine-readable zone" includes
a bar code or other non-alphanumeric character based content, and,
therefore, is not suited to OCR techniques. In such cases, the
content of the "machine-readable zone" is analyzed using any
appropriate technique, such as decoding a bar code using
appropriate code-reading techniques.
[0204] Document Presence Tests
[0205] Some tests are designed to confirm that the user is in the
presence of the actual document in question. For example, a user
captures a series of photographs of different pages of a document
(e.g., a passport) within a certain time frame. Successfully
providing the requested images of the requested pages within the
time frame corroborates that the user is in the presence of the
actual document.
[0206] As another example, a user captures a photograph of the user
holding the document in front of a mirror. As yet another example,
a user captures a video recording showing the user holding the
document. As yet another example, a user captures a photograph of a
most recent stamp in a passport. The ability of the user to provide
such images/videos corroborates that the user is in the presence of
the actual document (e.g., as opposed to a copy of the document or
only a single page of the document).
[0207] As yet another example, a user is prompted to capture
photographs of a document in accordance with certain criteria.
Specifically, the user is prompted to capture photographs of a
document in certain orientations, positions, angles, and the like.
The ability of the user to capture the requested images suggests
whether the user is in the presence of the actual document.
[0208] In some implementations, a reticle is displayed on a
viewfinder of an imaging device (e.g., on a screen of a smartphone
or digital camera) that specifies an orientation of the document.
The user must then capture an image according to the specified
orientation. For example, the reticle is a trapezoid, and the user
must orient the document and/or the camera such that the document
fits within and/or substantially matches the shape of the reticle.
In some implementations, the specific orientations, positions, or
angles requested are determined in a pseudo-random manner, so that
a user cannot easily predict what photographs will be
requested.
[0209] In some implementations, a user captures photographs of
paper-based documents against a substantially transparent surface
(e.g., a glass window). For paper documents, the light illuminating
the back surface causes the document to appear translucent,
allowing any printing or content on the back of the page to become
at least partially visible. Accordingly, the photograph is analyzed
to determine the content and/or quality of content on the back
surface of the document (i.e., the document surface that is against
the transparent surface), and/or to evaluate the level,
consistency, or quality of translucence of the paper itself.
[0210] Issuing Party Confirmation Tests
[0211] Some tests confirm whether a particular document embodies or
includes parameters or patterns expected of a document issued by a
particular issuing party. For example, passport numbers for a
certain country may conform to a detectable pattern. If the
parameters or patterns do not match expected ones (e.g., based on
the user's self reported information, or based on other information
extracted from the document), then the authenticity of the document
may be suspect.
[0212] In some implementations, a user captures a photograph of the
center pages of a passport, and the threading pattern of the
passport binding (visible in the center pages) is compared against
a known threading pattern for the purported country or issuing
party/jurisdiction of the passport.
[0213] In some implementations, a user captures a photograph of a
portion of a document that contains a unique identifier (e.g., a
passport number, drivers' license number, etc.), and the number is
compared against a known pattern for the purported country, state,
or issuing party/jurisdiction of the document.
[0214] Depth Analysis
[0215] Three-dimensional analysis of a document (and/or a document
in conjunction with one or more other objects) is also used in some
implementations to determine that the document is authentic. For
example, in some implementations, a user captures several
directional point-of-view photographs of a document. As another
example, a user captures one or more photographs of a document with
extraneous objects placed over it. Verification ratings for these
documents reflect a calculation of depth based on image
rectification techniques.
[0216] Physical Trait Tests
[0217] Some documents are made of materials that have unique
properties. For example, drivers' licenses are typically made of a
plastic or composite that has a certain rigidity and/or stiffness.
Accordingly, some tests are designed to determine whether the
document is likely made of an expected material. Specifically, in
some implementations, a user captures a photograph in which he or
she is bending a document (e.g., a drivers' license). The
photograph can be analyzed to determine whether the document
conforms to an expected curvature, or otherwise appears to be made
of an expected material (e.g., a plastic card rather than a slip of
paper).
[0218] Information Corroboration Tests
[0219] In some implementations, a verification rating for a
document is also based on whether or the degree to which
information from the document matches information from another
source. For example, as noted above, the other source of
information can be user-entered information (e.g., information
provided by a user during an account enrollment process). In some
implementations, the other source of information is another
document. For example, a verification rating for a drivers' license
is based at least in part on the degree to which the information in
the drivers' license matches information extracted from a
passport.
[0220] As a specific example, certain drivers' licenses are issued
with both a plastic card and a paper slip (e.g., drivers' licenses
in the United Kingdom and the European Union). In these cases, the
verification rating for a drivers' license is based on whether or
the degree to which the information on the plastic card matches the
information on the paper slip. Moreover, for such two-part
documents, the verification rating is also based on whether or not
the paper slip can be provided. In some implementations, no
verification rating is provided for such document if the second
part of the document cannot be photographed.
[0221] Signature Comparison
[0222] In some implementations, users are required or requested to
sign documents before capturing photographs of them. Such
signatures are then compared to a reference signature associated
with the user. The verification rating is then based on whether or
the degree to which the signature matches the reference signature.
Reference signatures are, for example, provided by the user during
an account enrollment process (e.g., entered by a user via a
touchscreen or touchpad input device), or extracted from another
document (e.g., drivers' license, passport, etc.). In some
implementations, documents that must be signed include utility
bills.
[0223] In some implementations, a video is captured of a user
signing a document. The video is then analyzed to determine whether
the user signed the document within an acceptable time frame (e.g.,
less than 5 seconds, or any other appropriate time frame), and
whether the resulting signature sufficiently matches a reference
signature. This can help detect fraudulent or forged signatures, as
it may be difficult for a user to quickly produce a convincing
forgery.
[0224] Third Party Review
[0225] In some implementations, third parties can verify and/or
corroborate information and/or documents of other users. For
example, notaries, lawyers, or other authorized individuals can
review information submitted by a user and provide an analysis
and/or opinion about the documents and/or the user. In some
implementations, such analysis and/or opinion is reflected in a
verification rating of a document or a user score. In other
implementations, it is independent of a verification rating or user
score (e.g., it is a separate indication that the account has been
verified by a third party). In some implementations, the third
party is provided with physical versions of documents for review
(e.g., copies or originals are delivered to the third party).
[0226] In some implementations, third parties are other users of
the service who personally corroborate the identity claims of other
users. For example, a first user who personally knows a second user
can corroborate the second user's identity, which can increase a
verification rating and/or user score of the second user, or appear
as a separate indication that the account has been corroborated by
another user. In some implementations, the first user's
verification rating(s), account status, and/or user score is
affected if the users and/or accounts that they corroborate turn
out to be falsified, fraudulent, or otherwise suspect. For example,
a user score of the corroborating user can be reduced, their
account can be degraded to a "pending" status, or their account can
be rejected by the service provider altogether.
[0227] Also, where corroboration by a first user affects a
verification rating or user score of a second user, the
verification ratings and/or corroboration history of the first user
can affect the amount by which the second user's verification
rating or user score is changed. For example, if a user with a high
user score (the first user) corroborates the identity of the second
user, the second user's score can be increased more than it would
be if the first user had a lower user score.
[0228] Any of the tests described above can be performed on any
appropriate device, depending on the implementation. For example,
in some implementations, they are performed on a client device
102-1 (e.g., as part of a document upload process performed by a
user). In some implementations, they are performed on an enterprise
device 108-1 (e.g., as part of an account generation process
performed on behalf of individuals by an institution, using
documents already in the possession of the institution). In some
implementations, they are performed on a server 104 (e.g., after
they have been uploaded by a client device 102-n or an enterprise
device 108-n).
[0229] Not all of the tests described above are necessarily applied
to all documents. Rather, one of skill in the art will recognize
that some tests are not applicable to certain documents or types of
documents. For example, a photograph comparison tests (e.g.,
comparing a photograph from a document to a reference photograph of
a user) would not apply to documents that do not include
photographs of the user. Similarly, hologram analysis tests would
not apply to documents that do not include holograms. In some
implementations, the tests that can be performed on a particular
document depend on the type of document.
[0230] Moreover, not all tests that are suitable for a particular
document are necessarily performed on that document. Rather, in
some implementations, when a document is uploaded, a certain subset
of the suitable tests for that document is selected. The user is
then prompted to capture the photographs and/or images required for
the selected tests.
[0231] In some implementations, when a document is obtained from a
user, the subset of tests are selected in a pseudo-random fashion,
such that it is difficult for a user to predict what tests will be
required for any particular document. Accordingly, it is more
difficult for users to create or obtain fraudulent documents (or to
capture photographs of someone else's documents) ahead of time if
they cannot predict what particular photographs they will be
prompted to capture and/or what analysis will be performed on the
document.
[0232] In some implementations, a user can increase the
verification rating for a particular document by electing to
perform one or more additional tests. The verification rating is
then adjusted based on the results of the additional tests.
Specifically, if the results are positive (e.g., support the
validity and/or authenticity of the document), the verification
rating is increased. On the other hand, if the results are negative
(e.g., refute the validity and/or authenticity of the document),
the verification rating is decreased.
[0233] In some implementations, the number of tests performed on a
document is reflected and/or included in the verification rating
itself. For example, a document may be amenable to 10 different
tests, and the results of each test are scored on a 0-10 scale.
Thus, if a document is subjected to 3 tests, and receives a perfect
result for each test, the overall verification rating is 30 of a
possible 100. Subjecting the document to additional tests can then
increase the verification rating, depending on the results of those
tests.
[0234] On the other hand, in some implementations, the number of
tests performed on a document is reflected separately from the
verification rating. For example, a verification rating for a
document may be a certain value (e.g., 80%) based on the results of
a certain number of tests (e.g., 3 of a possible 10), and the
number of tests is reported separately from the verification
rating. Thus, in this example, the rating of 80% reflects a
combined result of the 3 tests that were performed (e.g., an
average rating), and does not indicate the number of tests that
were performed.
[0235] For any of the tests described above, users are prompted
with step-by-step instructions, examples, sample images, and/or any
other information to assist with the successful completion of the
requested tests. Also, any analysis used in any of the tests
described above may be fully automatic (without human
intervention), fully manual, or a combination of automatic and
manual. A facial recognition analysis, for example, can be
performed by a computer (e.g., using a facial recognition and/or
comparison algorithm), or by a human (e.g., a human operator
reviewing a reference photograph and a document photograph and
determining whether they match. In some implementations, a human
operator reviews the results of an automatic analysis process in
order to confirm, reject, and/or modify the results of the
analysis.
[0236] FIGS. 8A-8C are flow charts of a fraud alert process flow,
according to some embodiments of the invention. This flow chart
illustrates one embodiment for addressing a fraud alert issued by a
card processor 803. A card processor, or payment processor, 803 is
any enterprise that is appointed by a merchant to handle credit or
debit card transactions for merchant acquiring banks. The
merchant's point-of-sale or POS terminal 801 connects to the card
processor 803 to both check the details received from the merchant
by forwarding them to the respective card's issuing bank or card
association for verification, and also carry out a series of
anti-fraud measures to protect against fraudulent transactions. In
some embodiments, both the card processor 803 and the POS 801 are
enterprise devices 108(1)-(n) of FIG. 1 that communicate over the
network.
[0237] In FIGS. 8A-8C, the customer 805 is an individual who has an
account with a bank or card issuer. In use, the customer 805 uses
their credit or debit card to purchase goods or services at the
merchant via the merchant's POS 801. In some embodiments, the
client 807, shown in FIGS. 8A-8C, is the client device 102(1)-(n)
of FIGS. 1 and 2. In some embodiments, the database 811 shown in
FIGS. 8A-8C is the certificate database 110 of FIGS. 1 and 4. In
some embodiments, the server 813 shown in FIGS. 8A-8C is the server
104 of FIGS. 1 and 4. The bank or bank agent 815 shown in FIGS.
8A-8C represents a card issuing bank, and, in some implementations,
one or more individuals employed by the card issuing bank or other
authority that are tasked with approving or denying card
transactions.
[0238] In use, the customer 805 attempts to purchase goods or
services from a merchant's POS 801 at 802. The POS 801 then sends
an electronic message to the card processor 803 at 804. This
message may be sent over a private or public network (e.g., network
110 of FIG. 1). This message may include the customer's name, the
card number, the issuing bank's name, the expiry date, the
transaction amount, a merchant or POS identifier, etc. The card
processor 803 receives the message and runs a set of rules against
the data contained in the message at 806. In some embodiments,
these rules are anti-fraud rules designed to detect fraudulent
transactions. The card processor then determines whether to
automatically deny the transaction at 808, e.g., because the
transaction is fraudulent. If it is determined that the transaction
should be denied (808--Yes), then a message is sent to the
merchant's POS 801 denying the transaction at 810. For example, the
transaction is denied because the card has been reported stolen. If
it is determined that the transaction should not be denied
(808--No), then the card processor runs a set of query rules at 812
to determine whether authorization for the transaction should be
requested (e.g., from the issuing bank or from the user). If it is
determined that it is not necessary to query the transaction
(814--No), then a message is sent back to the POS 801 authorizing
the transaction at 816. Although not shown, if a transaction is
authorized, known steps are taken to credit the merchant and debit
the customer for the transaction amount. The query may include the
customer's name, the card number, the issuing bank's name, the
expiry date, the transaction amount, a merchant or POS identifier,
any further acknowledgments required by the card processor, etc.
This query may be sent over a private or public network (e.g.,
network 110 of FIG. 1).
[0239] If it is determined that it is necessary to query the
transaction (814--Yes), then a query is sent from the card
processor 803 to the server 813 at 818. In some embodiments, the
server 813 receives the query and runs its own set of rules at 820.
Based on the contents of the query, these rules determine whether
approval is required, and if so what type of approval is required,
who needs to provide the approval, etc. If approval is not required
(822--No), then the server 813 sends a release to the card
processor at 826. The card processor 803 in turn authorizes the
transaction at 828 based on the received release.
[0240] If issuing bank or card authority approval is required
(822--Yes), then the server 813 sends a request for such approval
to the issuing bank 815 at 824. The bank 815 receives the request,
which in some implementations is generally presented to an
individual for approval. The bank 815 then responds at 830 with
either the necessary approval, or with requirements for what
further action is required, e.g., obtaining authorization for the
transaction directly from the customer. In some embodiments, the
action taken by the bank is completely automated and does not
require review by an individual. The server 813 receives the
response from the bank and sends a temporary hold to the card
processor at 834. The card processor may in turn notify the POS 810
of the temporary hold at 832. In some embodiments, the card is also
blocked at 834, i.e., it is no longer capable of being used for any
transactions.
[0241] At this time, the certificate generation module 446 (FIG. 4)
of the server 813 (104 of FIG. 4) creates a new certificate in the
certificate database 811 (e.g., 110 of FIGS. 1 and 4) at 836. The
sever 813 also adds a transaction request event (e.g., event
715(1)-(n) of FIG. 7) into the new certificate at 838. Then, the
server 813 sends a message to the client 807 (e.g., 102(1)-(n) of
FIGS. 1 and 2) requesting an acknowledgement that the transaction
is valid at 840. This message may be sent over a private or public
network (e.g., network 110 of FIG. 1). In some embodiments, this
message contains a list of evidence required by the bank, e.g., a
photo identification or answers to challenge questions, as well as
a request for acknowledgment that the specific transaction is valid
and authorized by the customer using the client device. In some
embodiments, this message contains a context.
[0242] Turning to FIG. 8B, the client then receives the request for
an acknowledgment of the transaction, and runs its own set of rules
at 842 to determine what is required by the bank. For example, the
client application 230 (FIG. 2) might determine that additional
evidence is required to verify the user's location and/or identity.
The client then displays a request to the customer using the client
device at 844. In some embodiments, the request asks for additional
evidence of identity. In some embodiments, the request asks
challenge questions. In some embodiments, the request simply asks
for an acknowledgment that the transaction is valid and/or
authorized, or that the current location of the customer is valid
and/or authorized for card use.
[0243] In some embodiments, if additional evidence is required
(846--Yes), the customer is asked to provide that evidence at 848.
For example, the client device may request that the customer answer
one or more challenge questions; may require the customer to take a
photograph of themselves, the card, and/or their ID card with a
camera on the client device; the customer's biometric data (e.g., a
fingerprint collected from one or more sensors on the device); or
the like. The customer may then provide the evidence at 850. In
some embodiments, the client will pause the process until such
evidence is provided. In other embodiments, further evidence is
captured by the device either automatically or with customer
approval at 852. For example, the location for the device may be
obtained from the positioning system 216 (FIG. 2) and/or the
device's IMEI, MAC address, and/or IP address may be captured.
[0244] The client also receives an acknowledgement from the
customer that the card transaction is valid and/or authorized at
854. In some embodiments, this acknowledgment may take the form of
a selection of a choice displayed to the customer on a display of
the client, e.g., "approve this transaction" or "decline this
transaction," or "approve this location" or "decline this
location."
[0245] In some embodiments, the client also calculates a
transaction rating for the particular transaction at 856. For
example, the verification rating module 238 (FIG. 2) calculates the
likelihood that the user of the device is the authorized customer
based on the evidence supplied at 850 and captured at 852 by the
client. Generation of the transaction rating is performed in a
similar manner to that of the verification rating described above.
In some embodiments, the transaction rating is based at least
partially on a degree of match between the evidence supplied by the
customer or the device and previously stored data; the amount of
the transaction; the location of the transaction; the type of the
transaction; the customer's verification rating; whether
authorization of concent was received; or the like.
[0246] The client then sends a response to the server at 858. The
response contains the acknowledgment and optionally the transaction
rating and/or evidence. This response is received by the server,
which adds a transaction response event to the previously created
certificate at 860. In some embodiments, the customer
acknowledgement 854 is stored as a consent 720 (FIG. 7) in the
certificate, and the transaction rating is stored in the
certificate as transaction rating 722 (FIG. 7).
[0247] Based on the transaction rating and/or the response received
from the client, the server then determines whether it requires
additional approval from the bank at 862. If no further bank
approval is required (862--No), then the server determines whether
the transaction rating and/or the response from the client meets a
threshold for non-fraudulent activity at 887. If the server
determines that the transaction rating and/or the response from the
client meets a threshold for non-fraudulent activity (887--Yes),
then the server sends a message to the card processor to release
the previously held transaction at 868, and the card processor
authorizes the transaction at 870. This entire process obtaining
approval from the customer preferably occurs while the customer is
still at the POS so that the transaction can still occur with
minimal delay. If at 834 a block or hold was placed on the card,
the server can also send a message to the card processor to unblock
the card at 868.
[0248] If further bank approval is requires (862--Yes), approval is
requested from the bank at 864. For example, if no acknowledgment
is received from the client or the transaction is otherwise
determined to be fraudulent, then approval is sought from the bank
to cancel the card. Once an action response is received back from
the bank at 886, it is determined whether the response from the
bank and/or the client meets a threshold for non-fraudulent
activity at 887. For example, the bank may instruct the server to
release or deny the transaction. If the server determines that the
response from the client meets a threshold for non-fraudulent
activity (887--Yes), then the server sends a message to the card
processor to release the previously held transaction at 868, and
the card processor authorizes the transaction at 870. If at 834 a
block or hold was placed on the card, the server can also send a
message to the card processor to unblock or release the use of the
card at 868.
[0249] If it is determined that the threshold has not been met
(887--No), then the server determines whether the card should be
cancelled at 884. If it is determined that the card should be
cancelled (884--Yes), then the a message is sent to the card
processor denying the transaction and cancelling the card at 888.
In some implementations, the card processor may also then send a
message to the POS denying the transaction at 890.
[0250] An additional event is added to the certificate indicating
the result of the transaction at 874. The certificate is also then
closed at 876. In some embodiments, the certificate is then
digitally signed and no further changes can be made to the
certificate.
[0251] In some embodiments, at any time thereafter, the bank or the
customer (via the client 807) can request a copy of the certificate
tat 902 and 904 respectively. In response to a request, the server
will validate the identity of the request against that on the
certificate, and if a match is made, the certificate is then sent
to the bank or customer at 906 and 908 respectively. In some
embodiments all of the data in the certificate is visible to the
bank or the customer, while in other embodiments only some
information within the certificate is visible. The certificate can
then be used as auditable proof that the customer acknowledged that
the transaction was valid and or authorized.
[0252] It should be appreciated to those of skill in the art that
fewer or more steps than those described above in relation to FIGS.
8A-8C may be performed. Moreover, certain steps may be performed at
different devices, e.g., actions performed by the bank may be
performed by the server. Also, actions performed by one device may
be separated among different devices or actions of different
devices may be consolidated and performed by one device.
[0253] The methods illustrated in FIGS. 5A-6, and 8A-8C may be
governed by instructions that are stored in a computer readable
storage medium and that are executed by at least one processor of
at least one electronic device (e.g., one or more client devices
102-n, one or more enterprise devices 108-n, or a server 104). Each
of the operations shown in these figures may correspond to
instructions stored in a non-transitory computer memory or computer
readable storage medium. In various implementations, the
non-transitory computer readable storage medium includes a magnetic
or optical disk storage device, solid state storage devices, such
as Flash memory, or other non-volatile memory device or devices.
The computer readable instructions stored on the non-transitory
computer readable storage medium may be in source code, assembly
language code, object code, or other instruction format that is
interpreted and/or executable by one or more processors (or
cores).
[0254] Plural instances may be provided for components, operations,
or structures described herein as a single instance. Finally,
boundaries between various components, operations, and data stores
are somewhat arbitrary, and particular operations are illustrated
in the context of specific illustrative configurations. Other
allocations of functionality are envisioned and may fall within the
scope of the implementation(s). In general, structures and
functionality presented as separate components in the example
configurations may be implemented as a combined structure or
component. Similarly, structures and functionality presented as a
single component may be implemented as separate components. These
and other variations, modifications, additions, and improvements
fall within the scope of the implementation(s).
[0255] It will also be understood that, although the terms "first,"
"second," etc. may be used herein to describe various elements,
these elements should not be limited by these terms. These terms
are only used to distinguish one element from another. For example,
a first contact could be termed a second contact, and, similarly, a
second contact could be termed a first contact, which changing the
meaning of the description, so long as all occurrences of the
"first contact" are renamed consistently and all occurrences of the
second contact are renamed consistently. The first contact and the
second contact are both contacts, but they are not the same
contact.
[0256] The terminology used herein is for the purpose of describing
particular implementations only and is not intended to be limiting
of the claims. As used in the description of the implementations
and the appended claims, the singular forms "a", "an" and "the" are
intended to include the plural forms as well, unless the context
clearly indicates otherwise. It will also be understood that the
term "and/or" as used herein refers to and encompasses any and all
possible combinations of one or more of the associated listed
items. It will be further understood that the terms "comprises"
and/or "comprising," when used in this specification, specify the
presence of stated features, integers, steps, operations, elements,
and/or components, but do not preclude the presence or addition of
one or more other features, integers, steps, operations, elements,
components, and/or groups thereof.
[0257] As used herein, the term "if" may be construed to mean
"when" or "upon" or "in response to determining" or "in accordance
with a determination" or "in response to detecting," that a stated
condition precedent is true, depending on the context. Similarly,
the phrase "if it is determined (that a stated condition precedent
is true)" or "if (a stated condition precedent is true)" or "when
(a stated condition precedent is true)" may be construed to mean
"upon determining" or "in response to determining" or "in
accordance with a determination" or "upon detecting" or "in
response to detecting" that the stated condition precedent is true,
depending on the context.
[0258] The foregoing description included example systems, methods,
techniques, instruction sequences, and computing machine program
products that embody illustrative implementations. For purposes of
explanation, numerous specific details were set forth in order to
provide an understanding of various implementations of the
inventive subject matter. It will be evident, however, to those
skilled in the art that implementations of the inventive subject
matter may be practiced without these specific details. In general,
well-known instruction instances, protocols, structures and
techniques have not been shown in detail.
[0259] The foregoing description, for purpose of explanation, has
been described with reference to specific implementations. However,
the illustrative discussions above are not intended to be
exhaustive or to limit the implementations to the precise forms
disclosed. Many modifications and variations are possible in view
of the above teachings. The implementations were chosen and
described in order to best explain the principles and their
practical applications, to thereby enable others skilled in the art
to best utilize the implementations and various implementations
with various modifications as are suited to the particular use
contemplated.
* * * * *