US20220067733A1

US20220067733A1 - Systems and methods for authentication of a remote transaction

Info

Publication number: US20220067733A1
Application number: US17/390,233
Authority: US
Inventors: William O. White; Douglas J. Hurst
Original assignee: Stripe Inc
Current assignee: Stripe Inc
Priority date: 2008-01-03
Filing date: 2021-07-30
Publication date: 2022-03-03
Also published as: US20170364902A9; US20150302389A1; US8744940B2; US20130144690A1

Abstract

A method and apparatus for authenticating a transaction between remote systems are described. The method can include authenticating, by a first computer server, a mobile user associated with a mobile device, and transmitting, by the first computer server to the mobile device in response to the authentication, a one-use authorization code in connection with the transaction, the transaction between the mobile user and a second server computer. The method can further include receiving, by the first computer server, the one-use authorization code from the second computer server in connection with one or more transaction parameters, and verifying, by the first server computer, a validity of the one-use authorization code and the one or more transaction parameters. Furthermore, the method can include in response to a successful verification, transmitting, by the first computer server, an authorization of the transaction to the second computer server.

Description

BACKGROUND

Incentives have become increasingly popular in recent years as a way to reward loyal patrons for their business and as a way to entice new patrons to patronize a merchant's business. Most incentives are in a physical form such as a coupon or card that requires the patron to remember the incentive and carry it with them in order to redeem that incentive. For a mobile device user who wishes to conduct all financial transactions via his or her mobile device, carrying additional items in order to redeem incentives is undesirable. Accordingly, there is a need to provide systems and methods for distributing and redeeming mobile incentives.

SUMMARY

Illustrative embodiments of the present invention that are shown in the drawings are summarized below. These and other embodiments are more fully described in the Detailed Description section. It is to be understood, however, that there is no intention to limit the invention to the forms described in this Summary of the Invention or in the Detailed Description. One skilled in the art can recognize that there are numerous modifications, equivalents, and alternative constructions that fall within the spirit and scope of the invention as expressed in the claims
The present invention can provide a system and method for distributing mobile incentives. One illustrative embodiment is a computer-server-based method for distributing a mobile incentive, comprising receiving a selection of a merchant with which to associate the mobile incentive; receiving an indication of a monetary amount for the mobile incentive; receiving an electronic payment for the monetary amount; applying the monetary amount to the mobile incentive; associating the mobile incentive with a recipient's phone number; and transmitting a notification of the mobile incentive to a mobile device associated with the recipient's phone number; wherein the computer server acts as a server-side wallet for the mobile incentive, and the mobile incentive is usable, through interaction with the computer server, by the recipient for the purchase of goods or services, from the merchant associated with the mobile incentive.
Another illustrative embodiment is a system for distributing a mobile incentive, comprising at least one processor; and a memory containing a plurality of program instructions executable by the at least one processor, the plurality of program instructions being configured to cause the at least one processor to receive a request from a merchant to generate a mobile incentive; identify the mobile incentive; associate the mobile incentive with a recipient's phone number; and transmit a notification of the mobile incentive to a mobile device associated with the recipient's phone number; wherein the system acts as a server-side wallet for the mobile incentive, and the mobile incentive is usable, through interaction with the system, by the recipient for the purchase of goods or services from the merchant associated with the mobile incentive.
These and other embodiments are described in further detail herein.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and form part of the specification in which like numerals designate like parts, illustrate embodiments of the present invention and together with the description, serve to explain the principles of the invention. Various objects and advantages and a more complete understanding of the present invention are apparent and more readily appreciated by reference to the following Detailed Description and to the appended claims when taken in conjunction with the accompanying drawings, wherein:

FIG. 1 is a functional block diagram of an environment in which various illustrative embodiments of the invention can be implemented;

FIG. 2 is a diagram showing interactions among various entities involved in the distribution and use of mobile incentives, in accordance with an illustrative embodiment of the invention;

FIG. 3 is a functional block diagram of a server that distributes and manages mobile incentives in accordance with an illustrative embodiment of the invention;

FIG. 4 is a flowchart of a method for distributing a mobile incentive in accordance with an illustrative embodiment of the invention;

FIGS. 5A and 5B are flowcharts of a method for distributing a mobile incentive in accordance with another illustrative embodiment of the invention.

DETAILED DESCRIPTION

In various illustrative embodiments of the invention, the limitations of conventional physical and electronic compensation and incentives are overcome by replacing the physical form factor of plastic, magnetically encoded cards with a mobile device such as a cellular telephone in a manner that leaves intact existing compensation and incentive systems and services operated by card service providers.
From time to time, providers of goods and services wish to provide their customers with incentives. Providers of goods and services may also be referred to as merchants or the “merchant” in the discussion herein. An incentive can be, for example, a percentage discount on a future purchase, a percentage discount to be taken on the current transaction, a free good or service up to a specific dollar amount, a buy one, get one coupon, a specific dollar amount to be provided as ‘cash back’ for future transactions, loyalty point addition, subtraction or redemption, or a specific redeemable dollar amount to be taken on the current transaction. Incentives as described herein as merchant funded and, thus, operate differently from gift cards or other forms of payment cards. One of skill in the art will recognize that an incentive can be in any form that can be transferred as an electronic coupon that pertains to the goods or services provided by the merchant or “merchant.”
A mobile-incentive platform in accordance with these illustrative embodiments provides, among other things, a server-side digital wallet for mobile incentives that overcomes the shortcomings (e.g., risk of loss or theft) associated with virtual incentives or incentive certificates that reside within the mobile device itself. In these illustrative embodiments, no credentials (account numbers, balances, or other sensitive information) associated with the mobile incentive reside in the mobile device itself. Instead, a secure network infrastructure distributes and manages the mobile incentives and their associated credentials, the mobile device acting merely as one means for the user to communicate with the server-side digital wallet to access a variety of flexible services surrounding use of the mobile incentives.
Such flexible services include, without limitation, the ability of a user to view a list of all available mobile incentives in his or her server-side digital wallet, the ability to view the current balance of any particular mobile incentive, the ability to purchase securely goods or services from the merchant associated with a particular incentive using the mobile device at the point of sale (however, the option to use a physical card is not preempted by the mobile-incentive-card platform described herein), and the ability to transfer some or all of the balance of a particular mobile incentive to another person.
Referring now to the drawings, where like or similar elements are designated with identical reference numerals throughout the several views, and referring in particular to FIG. 1, it is a functional block diagram of an environment 100 in which various illustrative embodiments of the invention can be implemented. In environment 100, distributor 105, merchant's agent 110, merchant 115, payment processor 120, wireless carrier 125, and incentive-card service provider 140 are able to communicate with one another via network 135. A user's mobile device 130—e.g., a cellular or Personal Communication Service (PCS) phone—is also able to communicate with nodes connected with network 135 via wireless carrier 125. In some embodiments, network 135 includes, but is not necessarily limited to, the Internet.
The environment 100 in FIG. 1 builds on existing incentive-card systems and payment card systems that can be operated by incentive-card service provider 140 or payment providers such as, without limitation, FIRST DATA and COMDATA. Incentive service provider 140, among other things, can administer the financial aspects of incentives for the merchant or the merchant can facilitate the financial aspects without the use of a service provider, including keeping track of the balance associated with a particular incentive, settlement, reporting to merchants, and other functions.
Merchant 115 sells goods, services, or both and provides mobile incentives to consumers, sometimes with the assistance of merchant's agent 110. That is, merchant's agent 110 can facilitate or merchant can facilitate the distribution and sale of mobile incentives issued by merchant 115 by acting as an intermediary between merchant 115 and any of the following: (1) a incentive-card service provider 140, (2) mobile-incentive-card distributor 105, (3) mobile-incentive-card purchasers (those giving the mobile incentives to others), and (4) mobile-incentive-card recipients (consumers who use the mobile incentives in commerce). It should be noted by one of skill in the art that a merchant's agent is not necessary to the invention but is rather one description of a commercial reality for merchants. A consumer holding such a mobile incentive can use the mobile incentive to redeem goods or services or in connection with the purchase of goods or services from the particular merchant that issued the mobile incentive, as explained above. How the holder of a mobile incentive redeems the mobile incentive from the issuing merchant is discussed further below.
Payment processor 120 processes the source of funds for transactions carried out from a user's mobile device such as the user's application of a mobile incentive or purchase of a mobile incentive on behalf of someone else. In such transactions, payment processor 120 acts as an agent of the merchant to collect funds from the user's credit card or other payment source, should the amount of the transaction exceed the amount associated with the mobile incentive. In some embodiments, an entity acting as a payment processor 120 in certain contexts may also be a distributor 105 in other contexts.
Distributor 105 can take on a variety of different forms, depending on the particular embodiment.
In one embodiment, distributor 105 is an entity (not necessarily a merchant but possibly the merchant) that operates a Web site or other electronic communication channel where mobile incentives for a number of different merchants are offered in an aggregated fashion. In another embodiment, a single merchant markets its mobile incentives via remote distribution channels, local distribution channels, or both. For example, a merchant may market its mobile incentives via a remote distribution channel such as a Web site or other networked electronic communication channel using Application Programming Interfaces (APIs) supplied by merchant's agent 110 or another entity. That is, a merchant may use flexible APIs provided by merchant's agent 110 to customize a Web site or other networked electronic communication channel to offer its mobile incentives in a manner consistent with the merchant's particular brand identify, logos, etc. A merchant may also employ local distribution methods in a store (at the point of sale). In such an embodiment, the mobile incentive can be “mobilized” (made accessible to the recipient via the recipient's mobile device) at the point of sale.
FIG. 2 is a diagram showing interactions among various entities 200 involved in the distribution and use of mobile incentives, in accordance with an illustrative embodiment of the invention. In FIG. 2, incentive system 210 represents a system operated by a conventional incentive-card service provider 140 such as, without limitation, FIRST DATA, Mocapay, or COMDATA. Various embodiments of the invention preserve the existing payments infrastructure supporting the use of incentives and overlay them with a mobile commerce platform 205, which is explained below. Other entities involved are a mobile-payments-enabled merchant (sometimes called simply a “merchant” herein) 225, a mobile user 220, and carriers or other entities (“CARRIERS/OTHERS” in FIG. 2) 215 and their associated distribution systems (see distributor 105 in FIG. 1). In the discussion of FIG. 2 below, interactions among these entities are identified by their corresponding reference numerals in parentheses.
In some embodiments, mobile user 220 can use a variety of different access methods such as, without limitation, Short Message Service (SMS) messages, Multimedia Message Service (MMS) messages, Wireless Access Protocol (WAP), an application, or voice to obtain one-use perishable authorization codes request purchase code 240 from mobile commerce platform 205 in making payments from a variety of different tenders (forms of payment), including mobile incentives. Mobile user 220 can also use a variety of methods, including the above examples, to provide one-use perishable authorization codes to merchant 225 in making electronic purchase 260. Additional details regarding such mobile-payment technology can be found in U.S. patent application Ser. No. 11/624,620, entitled “Systems and Method for Secure Wireless Payment Transactions,” which is incorporated herein by reference in its entirety.
Mobile user 220 may also receive targeted marketing messages 250 before, during, or after a mobile purchase via mobile commerce platform 205 and may purchase 235 mobile incentives from a carrier 215 (e.g., T-MOBILE, AT&T, VERIZON WIRELESS, etc.) or other distributor 105 such as a social networking Web site. The targeted marketing messages are assisted by the ability of merchant 225 to submit marketing rules, content, or both 265 to mobile commerce platform 205.
Merchant 225 receives payment authorization 255 from mobile commerce platform 205 in conjunction with the mobile payments technology mentioned above in connection with U.S. patent application Ser. No. 11/624,620. The mobile payments process is summarized briefly below.
Mobile commerce platform 205 facilitates the activation 230 of mobile incentives sold by a carrier or other entity 215 (or other distributor 105) in cooperation with incentive system 210 via communication link 275. Incentive system 210 also provides, among other things, settlement and reporting services 270 to merchant 225.
When mobile user 220 makes a purchase using a mobile incentive, mobile user 220 contacts mobile commerce platform 205 using any of a variety of access methods (e.g., SMS, MMS, WAP or other browser technology, application, voice) to provide an optional personal identification number (PIN) by which mobile commerce platform 205 authenticates mobile user 220 to request a purchase code 240. Mobile commerce platform 205 provides mobile user 220 with one-time perishable (time-limited) authorization codes and balances for various tenders available to that user, including mobile incentives. In the present example, customer or mobile user 220 selects a specific mobile incentive to be used in making the purchase and a specific payment card to be used to complete the transaction. The mobile-payments-enabled merchant 225 submits the authorization code provided by mobile user 220 and the transaction amount to mobile commerce platform 205 payment authorization 255. Mobile commerce platform 205 routes the transaction parameters to incentive system 210, which ensures that the requested amount is available on the indicated mobile incentive and the payment card has the available funds to complete the transaction. If everything checks out, incentive system 210 informs mobile commerce platform 205, which, in turn, conveys a return authorization to the merchant 225, completing the transaction payment authorization 255.
With this high-level background in place, the remainder of this Detailed Description focuses primarily on the distribution and transfer of mobile incentives, primarily from the merchant to the consumer but the server can be configured to allow the transfer of an incentive from one consumer to another. FIG. 3 is a functional block diagram of a computer server (“server”) 300 that distributes and manages mobile incentives in accordance with an illustrative embodiment of the invention. In this embodiment, server 300 is part of mobile commerce platform 205 (see FIG. 2). In FIG. 3, processor 305 communicates over data bus 310 with input devices 315, display 320, communication interfaces 325 (“COMM. INTERFACES” in FIG. 3), storage devices 330 (e.g., hard disk drives or flash memory), and memory 335. Though FIG. 3 shows only a single processor, multiple processors or a multi-core processor may be present in some embodiments.
Input devices 315 include, for example, a keyboard, a mouse or other pointing device, or other devices that are used to input data or commands to server 300 to control its operation. Communication interfaces 325 may include, for example, various serial or parallel interfaces for communicating with network 135 (see FIG. 1) or one or more peripherals.
Memory 335 may include, without limitation, random access memory (RAM), read-only memory (ROM), flash memory, magnetic storage (e.g., a hard disk drive), optical storage, or a combination of these, depending on the particular embodiment. In FIG. 3, memory 335 includes mobile incentive management platform 340, which distributes and manages mobile incentives. In doing so, mobile incentive management platform 340 accesses and manipulates mobile incentive data 345, which may reside, at least in part, on storage devices 330.
As mentioned above, mobile incentive management platform 340 implements a server-side digital wallet for the mobile incentive data 345. A “mobile incentive” is, thus, a digital construct (stored digital data) that replaces a physical (e.g., plastic, magnetically encoded) incentive. It should be noted that an incentive is a merchant funded device; i.e, the merchant is the entity that provides the financial account for “funding” the incentive. In other words, instead of the consumer's account covering the amount of the transaction, the merchant's account is debited or reduced to cover the amount of the incentive. The mobile incentive is also initiated by the merchant and transmitted to the consumer as part of the consumer registration in the mobile payments platform. The consumer does not initiate the activation of the incentive; rather activation of the incentive is automatic once the merchant initiates and funds the incentive. In this illustrative embodiment, server 300 stores account information for each mobile-incentive holder. That is, each mobile-incentive user initially creates an account on server 300. This account information includes, for each mobile incentive belonging to a particular user, (1) the user's mobile phone number, (2) the account number of the particular mobile incentive (analogous to a bar code of a physical coupon or incentive), and (3) the merchant that issued the mobile incentive. In some embodiments, server 300 stores additional information or different information from that just indicated. Note, however, that, in this particular embodiment, the balance remaining on the mobile incentive is not stored on server 300. Instead, the balance is tracked by the incentive service provider 140 that operates the applicable incentive system 210. As mentioned above, no credentials associated with a mobile incentive reside on the user's mobile device.
In one illustrative embodiment, mobile incentive management platform 340 is implemented as software that is executed by processor 305. Such software may be stored, prior to its being loaded into RAM for execution by processor 305, on any suitable computer-readable storage medium such as a hard disk drive, an optical disk, or a flash memory. In general, the functionality of mobile incentive management platform 340 may be implemented as software, firmware, hardware, or any combination or sub-combination thereof. The methods carried out by mobile incentive management platform 340 are explained more fully below in connection with FIGS. 4-5A and 5B.
A typical application for mobile incentive is a situation in which User A (typically, a merchant or provider of goods and services) wishes to give User B (typically, a customer of the merchant) an incentive (e.g., User B has been a loyal patron and User A wishes to reward User B's loyalty). From a user perspective, User A can communicate with server 300 of mobile commerce platform 205 in a variety of different ways to purchase a mobile incentive for User B. Examples include, without limitation, a Web site hosted by server 300 (or another server elsewhere on the network) and visited by User A using a client personal computer (PC), a Web site or other portal accessed using User A's cellular or PCS phone, a visit by User A at the merchant's store, or other avenues (e.g., User A's wireless carrier or a social networking Web site), as discussed above. User A can employ methods such as, without limitation, SMS, MMS, WAP (a microbrowser on a mobile device), or voice (in person or over the phone) to initiate an incentive for User B. In general, User A simply needs a way to communicate, directly or indirectly, with server 300. The foregoing example of User A providing a mobile incentive for User B will be referred to frequently in the description of FIGS. 4-5 that follows.
FIG. 4 is a flowchart of a method for distributing a mobile incentive in accordance with an illustrative embodiment of the invention. The process may begin when the mobile incentive management platform 340 receives a request, from a merchant, to generate a new mobile incentive. At 410, the mobile incentive management platform 340 receives a request indicating the type of mobile incentive to be created and generated from the merchant, and, at 415, receives a request to associate a specific incentive amount with another person.
At 420, the mobile incentive management platform 340 receives the phone number of the intended recipient of the incentive and, at 425, associates the mobile incentive with User B's (the recipient's) phone number (provided by User A or the merchant). At 430, the mobile incentive management platform 340 transmits or otherwise conveys a notification regarding the mobile incentive to a mobile device (e.g., a cellular or PCS phone) associated with User B's (the recipient's) phone number provided by User A above in Block 425. If the incentive is a free good or service, for example, a free appetizer, User A supplies a monetary value to the free appetizer.
The notification at FIG. 4 may be accomplished in a variety of ways, including, without limitation, an SMS message, an MMS message, a voice message, or an application. The application, in some embodiments, is a WAP browser or other type of Internet browser running on the mobile-gift-card recipient's mobile device. In other embodiments, the application is a specialized application other than a browser.
In some embodiments, the notification to the recipient includes a personalized message created by the merchant such as, “Thank you for your patronage.”
Following receipt of the mobile incentive, User B can use the mobile incentive to purchase goods or services from the merchant associated with the mobile incentive in a variety of different ways, as explained above (see discussion of secure payments in connection with FIG. 2 above).
Activation can also take different forms, depending on the particular embodiment. In some embodiments, for example, the notification User B receives includes instructions to User B for how to activate the mobile incentive. For example, the notification may be an SMS message stating, “Bob, you've received a $100 mobile incentive for SPORTS AUTHORITY. Please visit mocapay.com to activate your mobile incentive.” Note that, in such embodiments, the notification includes a hyperlinked Uniform Resource Locator (URL) for User B to follow to complete the activation process. Alternatively, User B could be provided with a phone number, an e-mail address, or other contact information for accomplishing activation. When User B contacts mobile commerce platform 205 to activate the mobile incentive, User B is directed to create an account, if User B does not already have one. Mobile commerce platform 205 guides User B through this straightforward process.
In another embodiment, if User B already has an account with mobile commerce platform 205, the mobile incentive is activated automatically when the notification is transmitted to User B, which makes the mobile incentive available to User B immediately upon receipt of the notification. To redeem the mobile incentive, User B communicates with the server-side digital wallet supported by mobile incentive management platform 340 in the manner described above in connection with FIG. 2.
In another embodiment, mobile incentive management platform 340 receives a specific activation date from User A (the party providing the mobile incentive). For example, if User B's birthday is still five days in the future, User A would like to postpone notification of the mobile incentive until User B's birthday. In such an embodiment, notification of the mobile incentive is conveyed to User B on the activation date specified by User A.
At 435, the method in FIG. 4 terminates.
FIGS. 5A and 5B are a flowchart of a method for redeeming a mobile incentive in accordance with another illustrative embodiment of the invention. At 510, the mobile incentive management platform 340 receives a customer PIN and, at 515, receives a customer device identification. Based on those two pieces of information, the platform authenticates the customer at 520. Once the customer is authenticated, the platform retrieves the electronic wallet associated with the customer at 525. The platform then receives a merchant selection from the customer at 530. Once a merchant is selected, at 540, the platform identifies whether an incentive is associated with the merchant and the customer's mobile device number. The platform, at 545, then transmits the electronic wallet to the customer and, at 550, queries the customer as to whether the incentive should be used. At 555, the platform receives an account code, input regarding the application of the incentive and a transaction amount. Additional information could be transmitted such as identification of the items purchased and associated monetary values.
As shown in FIG. 5B, if the incentive is to be used, the platform applies the incentive to the transaction amount at 560 and transmits an authorization code to the customer at 565. The customer then provides the authorization code to the merchant. At 570, the platform receives a transaction approval request from the merchant. At 575, the platform authorizes the transaction approval request and transmits an approval code to the merchant at 580. At 585, the platform transmits an electronic receipt to both the merchant and the customer. The receipt provides all the pertinent details of the transaction and also shows that the incentive was used and the value of the incentive. The platform then stores the transaction details at 590 and generates and executes settlement instructions at 595.
In conclusion, the present invention provides, among other things, a system and method for distributing compensation and incentives. Although the present invention and its advantages have been described in detail, it should be understood that various changes, substitutions, and alterations can be made herein without departing from the spirit and scope of the invention as defined by the appended claims. Moreover, the scope of the present application is not intended to be limited to the particular embodiments of the process, machine, manufacture, composition of matter, means, methods, and steps described in the specification. As one of ordinary skill in the art will readily appreciate from the disclosure of the present invention, processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed that perform substantially the same function or achieve substantially the same result as the corresponding embodiments described herein may be utilized according to the present invention. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps. The invention disclosed herein may suitably be practiced in the absence of any element that is not specifically disclosed herein.

Claims

What is claimed is:

1. A computer server-based method for authenticating a transaction between remote systems, comprising:

authenticating, by a first computer server, a mobile user associated with a mobile device;

transmitting, by the first computer server to the mobile device in response to the authentication, a one-use authorization code in connection with the transaction, the transaction between the mobile user and a second server computer;

receiving, by the first computer server, the one-use authorization code from the second computer server in connection with one or more transaction parameters;

verifying, by the first server computer, a validity of the one-use authorization code and the one or more transaction parameters; and

in response to a successful verification, transmitting, by the first computer server, an authorization of the transaction to the second computer server.

2. The computer server-based method of claim 1, wherein authenticating the mobile user associated with the mobile device further comprises:

receiving, by the first computer server from the mobile device, a user identifier and a mobile device identifier, the user identifier comprising a personal identification number (PIN); and

authenticating the mobile user based on an authentication of both the PIN and the mobile device identifier.

3. The method of claim 2, further comprising:

in response to a successful authentication of the mobile user, determining that an incentive is associated with the second computer server and the mobile device; and

transmitting a query to the mobile device as to whether to apply the incentive to the transaction.

4. The computer server-based method of claim 3, further comprising:

in response to receiving a mobile user selection to apply the incentive and a requested amount of the incentive to be applied to the transaction, applying the incentive to the requested amount.

5. The computer server-based method of claim 4, wherein the one-use authorization code is perishable, and wherein verifying the validity of the one-use authorization code and the one or more transaction parameters comprises:

verifying, by the first computer server, the one-use authorization code is associated with the mobile user and the one-use authorization code is valid; and

verifying, by the first computer server, the one or more transaction parameters with a third computer server comprising verifying an availability of funds of the mobile user associated with a payment instrument of the mobile user less the requested amount.

6. The computer server-based method of claim 1, wherein the one-use authorization code is displayed on the mobile device.

7. The computer server-based method of claim 1, further comprising:

transmitting a balance to the mobile device for a tender available to the mobile user in connection with the one-use authorization code, and wherein the tender comprises at least one of: a financial account or an incentive.

8. The computer server-based method of claim 1, further comprising:

after authorization of the transaction, transmitting an electronic receipt of the transaction to the merchant computer server and the mobile device.

9. A first computer server for authenticating a transaction between remote systems, comprising:

at least one processor; and,

a memory containing a plurality of program instructions executable by the at least one processor, the plurality of program instructions being configured to cause the at least one processor to perform operations comprising:

authenticating, by the first computer server, a mobile user associated with a mobile device,

transmitting, by the first computer server to the mobile device in response to the authentication, a one-use authorization code in connection with the transaction, the transaction between the mobile user and a second server computer,

receiving, by the first computer server, the one-use authorization code from the second computer server in connection with one or more transaction parameters,

verifying, by the first server computer, a validity of the one-use authorization code and the one or more transaction parameters, and

10. The first computer server of claim 9, wherein the at least one processor performing operations for authenticating the mobile user associated with the mobile device further comprises the at least one processor performing further operations comprising:

11. The first computer server of claim of claim 10, wherein the at least one processor performing further operations comprising:

12. The first computer server of claim of claim 11, wherein the at least one processor performing further operations comprising:

13. The first computer server of claim of claim 12, wherein the one-use authorization code is perishable, and wherein the at least one processor performing operations for verifying the validity of the one-use authorization code and the one or more transaction parameters comprises the at least one processor performing further operations comprising:

14. The first computer server of claim of claim 9, wherein the one-use authorization code is displayed on the mobile device.

15. The first computer server of claim of claim 9, further comprises the at least one processor performing further operations comprising:

16. The first computer server of claim of claim 9, further comprises the at least one processor performing further operations comprising:

17. A non-transitory computer-readable medium comprising a plurality of program instructions configured to cause at least one processor to perform operations for authenticating a transaction between remote systems, the operations comprising:

18. The non-transitory computer-readable medium of claim 17, wherein authenticating the mobile user associated with the mobile device further comprises:

19. The non-transitory computer-readable medium of claim 18, further comprising:

20. The non-transitory computer-readable medium of claim 19, further comprising: