# US 8,751,394 B2 · System and method for enhanced transaction security > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 8,751,394 B2 - Document ID: US8751394B2 - Status: Granted - Kind: B2 - Application number: 12/276,539 - Filed: 2008-11-24 - Published: 2009-05-28 - Granted: 2014-06-10 - Earliest claimed: 2007-11-28 - Assignees: Sybase 365, Inc. - Applicants: William H. Dudley; Marc R. Landrum; Robert C. Lovell, Jr. - Inventors: William H. Dudley; Marc R. Landrum; Robert C. Lovell, Jr. - Web page: https://patentgrep.com/patent/US8751394B2 ## CPC - G06Q 20/04: Payment circuits - G06Q 20/3255: {using mobile network messaging services for payment, e.g. SMS} - G06Q 20/327: {Short range or proximity payments by means of M-devices} - G06Q 20/4014: {Identity check for transactions} - G06Q 30/04: Billing or invoicing - G06Q 40/00: Finance; Insurance; Tax strategies; Processing of corporate or income taxes - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR ## Abstract As individuals increasingly engage in different types of transactions they face a growing threat from, possibly among other things, identity theft, financial fraud, information misuse, etc. and the serious consequences or repercussions of same. Leveraging the ubiquitous nature of wireless devices and the popularity of (SMS, MMS, etc.) messaging, an infrastructure that enhances the security of the different types of transactions within which a wireless device user may participate. The infrastructure may optionally leverage the capabilities of a centrally-located Messaging Inter-Carrier Vendor. ## Claims ### Claim 1 A method for enhanced transaction security, comprising: at a gateway device, receiving from a wireless device of a mobile subscriber a request message, the request message indicative of a transaction involving a third-party and identifying the third party as a retailer with whom a payment portion of a purchase is to be completed; performing at least one processing step on aspects of the request message, using at least (a) information from the request message, (b) registration information previously supplied by the mobile subscriber, and (c) information previously obtained about the third-party, yielding one or more security policies; generating, based at least on aspects of the one or more security policies, a Personal Identification Number (PIN); preserving at least the PIN in a repository; and generating and sending a response message to the mobile subscriber, the response message containing at least the PIN, wherein the PIN is employed to initiate the transaction involving the third-party. ### Claim 2 (depends on 1) The method of claim 1, wherein the request message and the response message are each one of (a) a Short Message Service message, (b) a Multimedia Message Service message, (c) an IP Multimedia Subsystem message, or (d) an E-Mail message. ### Claim 3 (depends on 1) The method of claim 1, wherein the registration information is defined by the mobile subscriber during a registration process. ### Claim 4 (depends on 3) The method of claim 3, wherein the registration information includes at least one of (a) Identifying Information, (b) Account Information, (c) Security Service Information, and (d) Billing Information. ### Claim 5 (depends on 3) The method of claim 3, wherein the registration process includes a billing component. ### Claim 6 (depends on 1) The method of claim 1, wherein the PIN is developed through one of (a) random generation, (b) a predefined algorithm or formula, or (c) sequential generation. ### Claim 7 (depends on 1) The method of claim 1, further comprising: use by the mobile subscriber of the PIN in the transaction. ### Claim 8 (depends on 4) The method of claim 4, wherein the use involves one of (a) manual entry, (b) Near Field Communication, (c) infrared communication, or (d) BlueTooth communication. ### Claim 9 (depends on 4) The method of claim 4, further comprising: interaction by the third-party with the repository to at least confirm the PIN. ### Claim 10 (depends on 1) The method of claim 1, wherein performing at least one processing step on aspects of the request message further comprises using at least information concerning security policies and procedures of the third party. ### Claim 11 (depends on 1) The method of claim 1, further comprising tracking the usage by the mobile subscriber and offering discounts to the mobile subscriber based on the usage. ### Claim 12 (depends on 1) The method of claim 1, further comprising receiving, from the mobile subscriber, a reply to the response message that activates the PIN. ### Claim 13 (depends on 1) The method of claim 1, further comprising receiving, from the mobile subscriber, a reply message to the response message that confirms the PIN. ### Claim 14 (depends on 1) The method of claim 1, further comprising designating the PIN as single-use. ### Claim 15 (depends on 1) The method of claim 1, further comprising designating the PIN as multi-use. ### Claim 16 (depends on 1) The method of claim 1, wherein the PIN carries a lifetime indicator. ### Claim 17 (depends on 16) The method of claim 16, wherein the lifetime indicator identifies a predetermined period of time during which the PIN is usable. ### Claim 18 (depends on 16) The method of claim 16, wherein the lifetime indicator identifies a specific number of uses. ### Claim 19 (depends on 16) The method of claim 16, wherein the lifetime indicator identifies a cumulative transaction amount beyond which the PIN is not usable.