Transaction authentication with a variable-type user-stored account identifier

• US 9,898,738 B2
• Filed: 11/13/2013
• Issued: 02/20/2018
• Est. Priority Date: 02/14/2012
• Status: Active Grant

• Current Assignee: Boku Incorporated
• Original Assignee: Boku Incorporated
• Inventors: Yoo, David
• Primary Examiner(s): Champagne, Luna
• Application Number:
  US14/078,987
• Publication Number:
  US 20140074633A1
• Time in Patent Office: 1,560 Days
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/227 characterised in that multiple accounts are available, e.g. to the payer
• CPC Class Codes: G06Q 20/3255 using mobile network messaging services for payment, e.g. SMS
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction

Abstract

Each of a plurality of consumer accounts in a data store has a first consumer account identifier. Login information is received from a consumer device over the network interface device. The first consumer account identifier is received from the consumer device and stored in association the consumer account. The first consumer account identifier is storable as one of at least two types of identifiers and the storing by the consumer device of the first consumer account identifier is only permitted upon successful login based on the login information. The charge request is received over a network interface device, the charge request including the amount and the second consumer account identifier. A selected one of the consumer accounts is identified by associating one of the first consumer account identifiers with the second consumer account identifier, and the charge request is processed based on an account detail of the selected consumer account.

Claims

1. A computer system for managing electronic transactions, comprising:

a server computer system including;

a processor;

a computer-readable medium connected to the processor;

a network interface device connected to the processor; and

a set of instructions on the computer-readable medium, the set of instructions being executable by the processor and including;

a data store;

a plurality of consumer accounts stored in the data store;

a login module receiving login information from a consumer device over the network interface device;

an identifier storing module receiving a plurality of first consumer account identifiers, each first consumer account identifier being received from a respective consumer device, and storing each first consumer account identifier in association with a respective consumer account, wherein the first consumer account identifier is selectably and interchangeably storable as one of at least first and second types of identifiers and the storing by the consumer device of the first consumer account identifier only being permitted upon successful login based on the login information;

a communication and routing module that receives a charge request over the network interface device, the charge request including an amount and a second consumer account identifier, wherein the communication and routing module is configured to receive the second consumer account identifier in the charge request when the second consumer account identifier in the charge request is of the first type and when the second consumer account identifier in the charge request is of the second type and the communication and routing module identifies a selected one of the consumer accounts by associating one of the plurality of first consumer account identifiers with the second consumer account identifier in the charge request, wherein the communication and routing module is configured to identify the selected consumer account by associating the first consumer account identifier with the second consumer account identifier in the charge request when the second consumer account identifier in the charge request is of the first type or when the second consumer account identifier is of the second type, wherein if the first consumer account identifier is stored as the first type of consumer account identifier then the second consumer account identifier only identifies the first consumer account identifier if the second consumer account identifier has the first type but not if the second consumer account identifier has the second type; and

a transaction processing system that processes the charge request based on an account detail of the selected consumer account.

2. The computer system of claim 1, wherein the two types of identifiers have different lengths, wherein the first consumer account identifier is variable to be one of at least two of a PAN, an MSISDN, an email address, a social security number, and a driver'"'"'s license number.

3. The computer system of claim 1, wherein the second consumer account identifier is not a PAN.

4. The computer system of claim 3, wherein each consumer account has a respective first PIN and the charge request includes a second PIN, the processing of the charge request only being permitted upon a favorable comparison of the first PIN and the second PIN.

5. The computer system of claim 3, wherein the second consumer account identifier is not an MSISDN.

6. The computer system of claim 5, further comprising:

an authorization module transmitting an authorization request over the network interface device to a consumer device and receiving a response to the authorization request over the network interface device from the consumer device, wherein the charge request is processed if the response is an authorization response.

7. The computer system of claim 6, wherein the authorization module extracts an MSISDN from the consumer account, wherein the consumer device is a mobile phone having the MSISDN that is extracted from the account to contact the mobile phone.

8. The computer system of claim 1, further comprising:

a point-of-sale device receiving the second consumer account identifier.

9. The computer system of claim 8, wherein the point-of-sale device transmits the charge request to a merchant acquirer computer system, which routes the charge request to the processor.

10. The computer system of claim 1, wherein the set of instructions further includes:

a stored value in the consumer account;

a funding module receiving a top-up instruction from a consumer account funding infrastructure, and increasing the stored value based on the top-up instruction, wherein the transaction processing system includes;

an account lookup and debit module that reduces the stored value based on the amount.

11. The computer system of claim 10, wherein the transaction processing system includes:

a transaction validation module that compares the stored value with the amount, wherein the account lookup and debit module reduces the stored value with the amount, wherein the stored value is (i) only reduced if the stored value is at least as much as the amount and (ii) not reduced if the stored value is less than the amount, and transmits a confirmation over the network interface device (i) to accept the charge request if the stored value is at least as much as the amount and (ii) to deny the charge request if the stored value is less than the amount.

12. The computer system of claim 1, wherein the set of instructions further includes:

a payment source storing module storing a plurality of payment sources associated with the respective consumer account having the respective consumer account identifier; and

a payment source selector set upon receiving a payment source selection over the network interface device to indicate a selected one of the payment sources, the payment source selector indicating a selected one of the payment sources based on the payment source selection, the transaction processing system determining a payment source selected with the payment source selector, wherein the charge request is processed based on the payment source selected by the payment source selector.

13. The computer system of claim 12, wherein a first of the payment sources is a stored value in the consumer account, wherein the charge request is processed by reducing the stored value if the payment selector is set to use the first payment source.

14. The computer system of claim 13, wherein a second of the payment sources includes routing information for a bank account, wherein the charge request is processed by transmitting a pass-through request over the network interface device based on the routing information if the payment selector is set to use the second payment source.

15. The computer system of claim 14, wherein the transaction processing system includes:

a transaction bypass module that either (i) reduces the stored value if the payment selector is set to use the first payment source, or (ii) transmits the pass-through request over the network interface device based on the routing information if the payment selector is set to use the second payment source.

16. The computer system of claim 12,

access to the payment source storing module by the consumer device to store the plurality of payment sources is only permitted upon successful login based on the login information.

17. A computer-based method of managing electronic transactions, further comprising:

storing, by a processor, a plurality of consumer accounts in a data store;

receiving, by the processor, a plurality of first consumer account identifiers, each first consumer account identifier being received from a respective consumer device;

receiving, by the processor, login information from a consumer device over the network interface device;

storing each first consumer account identifier in association with a respective consumer account, wherein the first consumer account identifier is selectably and interchangeably storable as one of at least first and second types of identifiers and the storing by the consumer device of the first consumer account identifier only being permitted upon successful login based on the login information;

receiving, by the processor executing a communication and routing module, a charge request over a network interface device, the charge request including an amount and a second consumer account identifier, wherein the communication and routing module is configured to receive the second consumer account identifier in the charge request when the second consumer account identifier in the charge request is of the first type and when the second consumer account identifier in the charge request is of the second type;

identifying, by the processor executing the communication and routing module, a selected one of the consumer accounts by associating one of the plurality of first consumer account identifiers with the second consumer account identifier in the charge request, wherein the communication and routing module is configured to identify the selected consumer account by associating the first consumer account identifier with the second consumer account identifier in the charge request when the second consumer account identifier in the charge request is of the first type or when the second consumer account identifier is of the second type, wherein if the first consumer account identifier is stored as the first type of consumer account identifier then the second consumer account identifier only identifies the first consumer account identifier if the second consumer account identifier has the first type but not if the second consumer account identifier has the second type; and

processing, with the processor, the charge request based on an account detail of the selected consumer account.

18. The method of claim 17, wherein the two types of identifiers have different lengths.

19. The method of claim 17, wherein the first consumer account identifier is variable to be at least two of a PAN, an MSISDN, an email address, a social security number, and a driver'"'"'s license number.

20. The method of claim 17, wherein the second consumer account identifier is not a PAN.

21. The method of claim 20, wherein each consumer account has a respective a first PIN and the charge request includes a second PIN, the processing of the charge request only being permitted upon a favorable comparison of the first PIN and the second PIN.

22. The method of claim 20, wherein the second consumer account identifier is not an MSISDN.

23. The method of claim 22, further comprising:

transmitting, by the processor, an authorization request over the network interface device to a consumer device; and

receiving, by the processor, a response to the authorization request over the network interface device from the consumer device, wherein the charge request is processed if the response is an authorization response.

24. The method of claim 23, further comprising:

extracting an MSISDN from the consumer account, wherein the consumer device is a mobile phone having the MSISDN that is extracted from the account to contact the mobile phone.

25. The method of claim 17, further comprising:

receiving the second consumer account identifier in a point-of-sale device.

26. The method of claim 24, further comprising:

transmitting, with the point-of-sale device, the charge request to a merchant acquirer computer system, which routes the charge request to the processor, further comprising;

saving, by the processor, a stored value in the consumer account;

receiving, by the processor, a top-up instruction from a consumer account funding infrastructure;

increasing, by the processor, the stored value based on the top-up instruction;

reducing, by the processor, the stored value based on the amount, further comprising;

comparing, by the processor, the stored value with the amount, wherein the stored value is (i) reduced if the stored value is at least as much as the amount and (ii) not reduced if the stored value is less than the amount; and

transmitting, by the processor, a confirmation over the network interface device (i) to accept the charge request if the stored value is at least as much as the amount and (ii) to deny the charge request if the stored value is less than the amount.

27. The method of claim 17, further comprising:

storing, by the processor, a plurality of payment sources associated with the respective consumer account having the respective consumer account identifier;

receiving, by the processor, a payment source selection over the network interface device to indicate a selected one of the payment sources;

setting, by the processor, a payment source selector to indicate a selected one of the payment sources based on the payment source selection; and

determining, by the processor, a payment source selected with the payment source selector, wherein the charge request is processed based on the payment source selected by the payment source selector.

28. The method of claim 27, wherein a first of the payment sources is a stored value in the consumer account, wherein the charge request is processed by reducing the stored value if the payment selector is set to use the first payment source.

29. The method of claim 27, wherein a second of the payment sources includes routing information for a bank account, wherein the charge request is processed by transmitting a pass through request over the network interface device based on the routing information if the payment selector is set to use the second payment source.

30. The method of claim 27, wherein:

the storing by the consumer device of the plurality of payment sources is only permitted upon successful login based on the login information.