CUSTOMER IDENTIFICATION VERIFICATION PROCESS

• US 20190122220A1
• Filed: 10/23/2017
• Published: 04/25/2019
• Est. Priority Date: 10/23/2017
• Status: Active Grant

• Current Assignee: Capital One Services LLC (Capital One Financial Corporation)
• Original Assignee: Capital One Services LLC (Capital One Financial Corporation)
• Inventors: PHILLIPS, Jeremy, LIU, Zhe, BOUSQUET, Catherine
• Granted Patent: US 10,318,957 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 21/33 using certificates
• CPC Class Codes: G06F 21/335 for accessing specific resources, e.g. using Kerberos tickets
• CPC Class Codes: G06F 21/34 involving the use of external additional devices, e.g. dongles or smart cards
• CPC Class Codes: G06F 21/35 communicating wirelessly
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 2221/2111 Location-sensitive, e.g. geographical location, GPS
• CPC Class Codes: G06K 19/06037 multi-dimensional coding
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/24 Credit schemes, i.e. "pay after"
• CPC Class Codes: G06Q 20/26 Debit schemes, e.g. "pay now"
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 20/3224 Transactions dependent on location of M-devices
• CPC Class Codes: G06Q 20/3274 using a pictured code, e.g. barcode or QR-code, being displayed on the M-device
• CPC Class Codes: G06Q 20/38215 Use of certificates or encrypted proofs of transaction rights
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 20/4015 using location information
• CPC Class Codes: G06Q 2220/00 Business processing using cryptography postage metering system using cryptography G06Q2250/05
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 2209/80 Wireless network architectures or network communication protocols for wireless network security H04W12/00
• CPC Class Codes: H04L 9/3213 : using tickets or tokens, e.g. Kerberos network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807
• CPC Class Codes: H04L 9/3226 : using a predetermined code, e.g. password, passphrase or PIN network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083

Abstract

An example device may include one or more processors to receive a request for a service from a requestor user device; provide transaction information associated with the service to a provider user device, where the transaction information may include location information corresponding to a location at which the service may be provided; obtain verification information from the requestor user device based on an interaction associated with the requestor user device or the provider user device at the location, where the verification information may include one or more characteristics of the requestor user device; generate a verification token based on the one or more characteristics of the requestor user device; provide the verification token to the requestor user device; and provide the verification information to the provider user device to permit the provider user device to verify the requestor user device, in connection with performance of the service, based on receiving the verification information and obtaining the verification token from the requestor user device.

Claims

1. A system, comprising:

a device including;

a first memory; and

one or more first processors, operatively connected to the first memory, configured to;

receive a request for a service from a requestor user device;

obtain, from the requestor user device, one or more real-time characteristics of the requestor user device based on an interaction between the requestor user device and a provider user device,

the real-time characteristics of the requestor user device being based on at least one of;

 

a time associated with the interaction, or

 

a location of the requestor user device associated with the interaction;

generate a verification token by encrypting verification information associated with the requestor user device using the one or more real-time characteristics of the requestor user device as encryption information;

provide the verification token to the requestor user device; and

provide the verification information to the provider user device; and

the provider user device including;

a second memory; and

one or more second processors, operatively connected to the second memory, configured to;

receive the verification information from the device;

receive the verification token from the requestor user device that was generated by the device;

decrypt the verification token using one or more real-time characteristics of the provider user device to obtain decrypted verification information, the real-time characteristics of the provider user device being based on at least one of;

the time associated with the interaction, or

a location of the provider user device associated with the interaction; and

verify the requestor user device, in connection with performance of the service, based on whether the decrypted verification information matches the verification information received from the device.

2. The system of claim 1, where the one or more first processors, when generating the verification token, are to:

generate the verification token by encrypting the verification token using one or more other characteristics of the requestor user device as encryption information.

3. The system of claim 2, where the one or more other characteristics of the requestor user device identify at least one of:

a device type of the requestor user device;

identification information of the requestor user device;

or

an application, on the requestor user device, that is associated with the service.

4. The system of claim 1, where the service includes a currency delivery.

5. The system of claim 1, where the one or more first processors are further to:

receive a verification confirmation from the provider user device; and

process a transaction associated with the service based on the verification confirmation.

6. The system of claim 5, where the verification confirmation from the provider user device indicates that the provider user device has verified that the requestor user device requested the service based on determining the one or more real-time characteristics indicated by the verification token substantially match the one or more real-time characteristics included in the verification information.

7. The system of claim 1, where the one or more first processors are further to:

receive a notification that the requestor user device cannot be verified;

receive additional verification information after the requestor user device could not be verified based on the verification information and the verification token,

the additional verification information including one or more other characteristics associated with the requestor user device after the requestor user device could not be verified;

generate another verification token based on the additional verification information;

provide the other verification token to the requestor user device; and

provide the additional verification information to the provider user device to permit the provider user device to verify the requestor user device, in connection with the performance of the service and after the requestor user device could not be verified based on the verification information and the verification token, based on receiving the additional verification information and obtaining the other verification token from the requestor user device.

8. A non-transitory computer-readable medium storing instructions, the instructions comprising:

one or more instructions that, when executed by one or more first processors of a device, cause the one or more first processors to;

receive a request for a service from a requestor user device;

obtain, from the requestor user device, one or more real-time characteristics of the requestor user device based on an interaction between the requestor user device and provider user device,

the real-time characteristics of the requestor user device being based on at least one of;

a time associated with the interaction, or

a location of the requestor user device associated with the interaction;

generate a verification token by encrypting verification information associated with the requestor user device using the one or more real-time characteristics of the requestor user device as encryption information;

provide the verification token to the requestor user device;

provide the verification information to the provider user device; and

one or more instructions that, when executed by one or more second processors of the provider user device, cause the one or more second processors to;

receive the verification information from the device;

receive the verification token from the requestor user device that was generated by the device;

decrypt the verification token using one or more real-time characteristics of the provider user device to obtain decrypted verification information, the real-time characteristics of the provider user device being based on at least one of;

the time associated with the interaction, or

a location of the provider user device associated with the interaction; and

verify the requestor user device, in connection with performance of the service, based on whether the decrypted verification information matches the verification information received from the device.

9. The non-transitory computer-readable medium of claim 8, where the one or more instructions, when executed by the one or more first processors, further cause the one or more first processors to:

receive a verification confirmation from the provider user device; and

process a transaction associated with the service based on the verification confirmation.

10. The non-transitory computer-readable medium of claim 8, where the one or more instructions, that cause the one or more first processors to obtain the verification information, cause the one or more first processors to:

receive a notification of the interaction between the provider user device and the requestor user device; and

determine that the provider user device and the requestor user device are within a threshold distance of the location based on receiving the notification of the interaction between the provider user device and the requestor user device.

11. The non-transitory computer-readable medium of claim 8, where the one or more real-time characteristics of the requestor user device identify the time associated with the interaction.

12. The non-transitory computer-readable medium of claim 8, where the one or more instructions, that cause the one or more first processors to generate the verification token, cause the one or more first processors to:

generate a quick response (QR) code using the one or more real-time characteristics of the requestor user device as the encryption information to encrypt the verification information to generate the QR code.

13. The non-transitory computer-readable medium of claim 8, where the service includes at least one of:

delivering currency,

delivering a cashier'"'"'s check,

delivering a transaction card, or

providing a banking service.

14. The non-transitory computer-readable medium of claim 8, where the one or more instructions, when executed by the one or more first processors, further cause the one or more first processors to:

provide transaction information associated with the service to the provider user device, and

where the transaction information associated with the service to be provided to the requestor user device identifies at least one of;

a transaction identifier,

a time associated with providing the service,

one or more instructions for providing the service, or

account information associated with a user of the requestor user device.

15. A method, comprising:

receiving, by a server device, a request for a service from a requestor user device;

obtaining, by the server device and from the requestor user device, one or more real-time characteristics of the requestor user device based on an interaction between the requestor user device and provider user device,

the real-time characteristics of the requestor user device being based on at least one of;

a time associated with the interaction, or

a location of the requestor user device associated with the interaction;

providing, by the server device, verification information to the provider user device to facilitate providing the service;

generating, by the server device, a verification token by encrypting the verification information associated with the requestor user device using the one or more real-time characteristics of the requestor user device as encryption information;

providing, by the server device, the verification token to the requestor user device;

receiving, by the provider user device, the verification information from the server device;

receiving, by the provider user device, the verification token from the requestor user device that was generated by the server device;

decrypting, by the provider user device, the verification token using one or more real-time characteristics of the provider user device to obtain decrypted verification information, the real-time characteristics of the provider user device being based on at least one of;

the time associated with the interaction, or

a location of the provider user device associated with the interaction;

receiving, by the server device, a verification confirmation from the provider user device indicating that the provider user device verified the requestor user device based on whether the decrypted verification information matches the verification information received from the server device; and

processing, by the server device, a transaction associated with the service based on receiving the verification information.

16. The method of claim 15, where the verification confirmation indicates that the verification token was received, from the requestor user device, by the provider user device.

17. The method of claim 15, where the one or more real-time characteristics of the requestor user device identify the location of the requestor user device associated with the interaction.

18. The method of claim 15, where generating the verification token comprises:

generating a quick response (QR) code using the one or more real-time characteristics of the requestor user device as the encryption information to encrypt the verification information to generate the QR code.

19. The method of claim 15, where processing the transaction associated with the service comprises at least one of:

debiting an account of a user associated with the requestor user device;

or

crediting an account of a user associated with the provider user device.

20. The method of claim 15, where the service involves at least one of:

delivering currency,

delivering a cashier'"'"'s check,

delivering a transaction card, or

providing a banking service.