Granted Patent B2

US 9,195,981 · App. 12/604,019 · Granted Nov 24, 2015

Inventor: David Annan (Oakville, CA)

Assignee: IMS HEALTH INCORPORATED

G06Q20/322G06Q20/32G06Q20/3674

Abstract

Claims (39)

1. A system for authorizing transactions via mobile devices, comprising:

a mobile device executing a transaction authorization application, said transaction authorization application generating a transaction code for a transaction upon request by a user, said transaction authorization application including:

a presentation module configured to present to the user said transaction code on said mobile device, the transaction code to be entered by the user into a merchant system; and

a communication module configured to communicate at least a predetermined portion of said transaction code over a first channel; and

a server in communication with said mobile device over said first channel configured to receive said predetermined portion of said transaction code, said server being in communication with said merchant system over a second channel configured to receive a transaction request for said transaction, said transaction request including said transaction code entered by the user into the merchant system, said server executing transaction processing software configured to validate said transaction code received via said second channel by determining if said transaction code received via said second channel matches said predetermined portion of said transaction code received via said first channel, said server communicating a transaction response to said merchant system,

wherein said transaction authorization application encrypts said predetermined portion of said transaction code before communication to said server.

2. The system of claim 1 , wherein said first channel comprises a wireless mobile communications network.

3. The system of claim 1 , wherein said server compares said transaction code received from said merchant system to said predetermined portions of transaction codes received from a plurality of said mobile devices to determine if said transaction code is valid.

4. The system of claim 1 , wherein said transaction authorization application modifies said transaction code before presentation of said transaction code on said mobile device.

5. The system of claim 4 , wherein said transaction authorization application reversibly modifies said transaction code before presentation of said transaction code on said mobile device.

6. The system of claim 4 , wherein said transaction authorization application timestamps said transaction code before presentation of said transaction code on said mobile device.

7. The system of claim 6 , wherein said server removes said timestamp from said timestamped transaction code received from said merchant system to recover said transaction code.

8. The system of claim 7 , wherein said server iteratively attempts to recover said transaction code from said timestamped transaction code by modifying the time used to reverse the timestamp.

9. The system of claim 1 , wherein said transaction code comprises a one-time password.

10. The system of claim 9 , wherein said server validates said one-time password to validate said transaction code.

11. The system of claim 1 , wherein said transaction authorization application sends said predetermined portion of said transaction code to said server for validation prior to presentation on said mobile device.

12. The system of claim 11 , wherein said server invalidates said predetermined portion of said transaction code received via said first channel if said predetermined portion of said transaction code received via said first channel matches another of said predetermined portions of transaction codes previously received via said first channel, wherein said previously received predetermined portions of transaction codes represent respective transactions different than a current transaction.

13. The system of claim 1 , wherein said transaction code is deemed invalid after a period of time.

14. A method for authorizing transactions, comprising:

receiving, via a first channel, a predetermined portion of a transaction code generated by a mobile device for a transaction in response to a request by a user of said mobile device;

storing said predetermined portion of the transaction code received from said mobile device in a memory of a server, wherein said predetermined portions of transaction codes from said mobile devices are encrypted;

receiving, via a second channel, a transaction request from a merchant system, said transaction request including said transaction code displayed to said user and manually entered by said user at the merchant system;

determining if said transaction code received via said second channel matches said predetermined portion of said transaction code received via said first channel; and

transferring resources associated with said user for said transaction if said transaction code received via said second channel matches said predetermined portion of said transaction code received via said first channel.

15. The method of claim 14 , further comprising:

comparing said predetermined portion of said transaction code received from said mobile device to other said predetermined portions of transaction codes received from a plurality of other said mobile devices to detect and reject transaction code collisions of codes representing respective separate transactions and the predetermined portion of said transaction code for a present transaction.

16. The method of claim 14 , further comprising:

comparing said transaction code from said merchant system to said predetermined portions of transaction codes received from a plurality of said mobile devices to determine if said transaction code is valid.

17. The method of claim 14 , further comprising:

reversing a modification on said transaction code received from said merchant system.

18. The method of claim 17 , wherein reversing comprises removing a timestamp from said transaction server.

19. The method of claim 18 , further comprising:

determining if said transaction code has expired.

20. The method of claim 18 , wherein said removing a timestamp comprises:

generating a predetermined portion of said transaction code candidate from said timestamped transaction code by reversing said timestamp on said timestamped transaction code;

matching said predetermined portion of said transaction code candidate against said predetermined portions of transaction codes stored in said memory of said server; and

adjusting the time used to reverse said timestamp if said predetermined portion of said transaction code candidate does not match one of said predetermined portions of transaction codes stored in said memory of said server.

21. The method of claim 14 , wherein said transaction code comprises a one-time password, the method further comprising:

validating said one-time password.

Assignments (10)

Priority Claims (1)

Continuity (2)