SECURE MOBILE PAYMENT SYSTEM

• US 20180300716A1
• Filed: 06/21/2018
• Published: 10/18/2018
• Est. Priority Date: 06/25/2007
• Status: Active Grant

• Current Assignee: Mark Carlson
• Original Assignee: Mark Carlson
• Inventors: Carlson, Mark
• Granted Patent: US 10,726,416 B2
• Time in Patent Office: Days
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 20/403 Solvency checks
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: G06Q 40/12 Accounting

Abstract

The present invention provides a method for conducting a transaction that includes receiving a pseudo account identifier that corresponds to a primary account identifier. The pseudo account identifier may be received at a portable wireless device and may be generated by a remote server computer. The portable wireless device can receive the pseudo account identifier over a first network and provide the pseudo account identifier to an access device. The access devices generally comprises a reader that can receive the pseudo account identifier, and thereafter send a message to request authorization of a transaction. The authorization request message may include the pseudo account identifier and is sent to a payment processing network. The authorization request message is sent to the payment processing network over a second network. The payment processing network may then process the authorization message and return a response that indicates if the transaction is authorized or not.

Claims

1. A method comprising:

generating, by a server computer, a pseudo account identifier corresponding to an account identifier of an account of a user;

sending, by the server computer, the pseudo account identifier to a portable communication device over a first network, wherein the pseudo account identifier is automatically pushed to the portable communication device, and wherein reception of the pseudo account identifier by the portable communication device is transparent to the user such that the user does not know the pseudo account identifier is received;

receiving, by the server computer, an authorization request message for a transaction that includes the pseudo account identifier over a second network that is different from the first network;

converting, by the server computer, the pseudo account identifier in the authorization request message to the corresponding account identifier;

sending, by the server computer, the converted authorization request message with the account identifier to an issuer associated with the account, wherein the issuer generates an authorization response message including an indication of whether the transaction is approved or not approved;

receiving, by the server computer, the authorization response message; and

forwarding, by the server computer, the authorization response message to a sender of the authorization request message to complete the transaction based on the indication of whether the transaction is approved or not approved.

2. The method of claim 1, wherein the pseudo account identifier is pushed to the portable communication device when the portable communication device is turned on.

3. The method of claim 1, wherein the pseudo account identifier is pushed to the portable communication device when the portable communication device is idle.

4. The method of claim 1, wherein the pseudo account identifier is pushed to the portable communication device periodically.

5. The method of claim 1, wherein the pseudo account identifier is a sequence of numbers, letters, or a combination of numbers and letters.

6. The method of claim 1, wherein the pseudo account identifier expires after a predetermined number of transactions.

7. The method of claim 1, wherein the pseudo account identifier expires after a predetermined time period.

10. The server computer of claim 1, wherein the pseudo account identifier expires after a predetermined number of transactions or after a predetermined time period.

8. A server computer comprising:

a processor; and

a memory coupled to the processor, the memory storing computer code, which when executed by the processor, causes the server computer to perform operations including;

generating a pseudo account identifier corresponding to an account identifier of an account of a user;

sending the pseudo account identifier to a portable communication device over a first network, wherein the pseudo account identifier is automatically pushed to the portable communication device, and wherein reception of the pseudo account identifier by the portable communication device is transparent to the user such that the user does not know the pseudo account identifier is received;

receiving an authorization request message for a transaction that includes the pseudo account identifier over a second network that is different from the first network;

converting the pseudo account identifier in the authorization request message to the corresponding account identifier;

sending the converted authorization request message with the account identifier to an issuer associated with the account, wherein the issuer generates an authorization response message including an indication of whether the transaction is approved or not approved;

receiving the authorization response message; and

forwarding the authorization response message to a sender of the authorization request message to complete the transaction based on the indication of whether the transaction is approved or not approved.

9. The server computer of claim 8, wherein the pseudo account identifier is pushed to the portable communication device when the portable communication device is turned on, when the portable communication device is idle, or periodically.

11. A portable communication device comprising:

a processor; and

a memory coupled to the processor, the memory storing computer code, which when executed by the processor, causes the portable communication device to perform operations including;

receiving a pseudo account identifier that corresponds to an account identifier associated with an account of a user over a first network, the pseudo account identifier being automatically pushed to the portable communication device from a server computer, wherein reception of the pseudo account identifier by the portable communication device is transparent to the user such that the user does not know the pseudo account identifier is received; and

transmitting the pseudo account identifier to an access device to conduct a transaction, wherein the access device thereafter sends an authorization request message comprising the pseudo account identifier to a transaction processor over a second network that is different from the first network, wherein the transaction processor converts the pseudo account identifier in the authorization request message back to the account identifier and sends the authorization request message including the account identifier to an issuer associated with the account, wherein the issuer generates an authorization response message and sends the authorization response message to the transaction processor, and wherein the access device thereafter receives the authorization response message indicating whether the transaction is approved or not approved.

12. The portable communication device of claim 11, wherein the pseudo account identifier is pushed to the portable communication device when the portable communication device is turned on, when the portable communication device is idle, or periodically.

13. The portable communication device of claim 11, wherein the first network is a communications network, and the second network is a transaction processing network.

14. The portable communication device of claim 11, wherein the pseudo account identifier is a sequence of numbers, letters, or a combination of numbers and letters.

15. The portable communication device of claim 11, wherein the pseudo account identifier expires after a predetermined number of transactions or after a predetermined time period.

16. A method comprising:

receiving, by a portable communication device over a first network, a pseudo account identifier that corresponds to an account identifier associated with an account of a user, the pseudo account identifier being automatically pushed to the portable communication device from a server computer, wherein reception of the pseudo account identifier by the portable communication device is transparent to the user such that the user does not know the pseudo account identifier is received; and

transmitting, by the portable communication device, the pseudo account identifier to an access device to conduct a transaction, wherein the access device thereafter sends an authorization request message comprising the pseudo account identifier to a transaction processor over a second network that is different from the first network, wherein the transaction processor converts the pseudo account identifier in the authorization request message back to the account identifier and sends the authorization request message including the account identifier to an issuer associated with the account, wherein the issuer generates an authorization response message and sends the authorization response message to the transaction processor, and wherein the access device thereafter receives the authorization response message indicating whether the transaction is approved or not approved.

17. The method of claim 16, wherein the pseudo account identifier is pushed to the portable communication device when the portable communication device is turned on, when the portable communication device is idle, or periodically.

18. The method of claim 16, wherein the first network is a communications network, and the second network is a transaction processing network.

19. The method of claim 16, wherein the pseudo account identifier is a sequence of numbers, letters, or a combination of numbers and letters.

20. The method of claim 16, wherein the pseudo account identifier expires after a predetermined number of transactions or after a predetermined time period.