Mobile image payment system using short codes

Abstract

A Mobile Image Payment System for mobile commerce, which enables a Consumer to use a mobile device to make payments for online, Electronic Media, Print Media and POS Transactions, involving the presentment of a short code. In an embodiment, the Consumer scans the short code that is displayed by a merchant, to initiate a transaction. The system completes the transaction by processing information between a Mobile Payment Client residing on the Consumer's mobile device, a Mobile Payment Interface residing on a Transaction Server, and, in a further embodiment, a Mobile Payment Application residing on a merchant's device or POS terminal. The Consumer's mobile device communicates with a Payment Platform, which communicates with a Merchant Transaction Server in order to process and complete the mobile transaction. The short code of the merchant can be displayed on any product or advertising medium.

We claim: 
     
         1 - 14 . (canceled) 
     
     
         15 . A non-transitory computer readable storage medium with an executable transaction application stored thereon, the transaction application configured for generating a transaction request from a mobile device for receipt over a communications network by a transaction interface, a transaction of the transaction request associated with a merchant providing a product to a consumer, wherein the transaction application instructs a computer processor by execution of a set of instructions stored in a memory of the mobile device to perform the following steps of:
 receiving by the computer processor product code data associated with product data stored by the transaction interface in a merchant profile assigned to the merchant;   receiving by the computer processor for the transaction request a transaction type associated with the product data, the transaction type requiring respective input data from a user of the mobile device based on workflow instructions other than payment type instructions;   implementing by the computer processor the workflow instructions by presenting transaction type dependent instructions to the user on a user interface of the mobile device indicating the required input data;   receiving by the computer processor the required input data entered by the user via the user interface in response to the transaction type dependent instructions displayed;   sending by the computer processor the required input data to the transaction interface over the communications network; and   receiving by the computer processor a confirmation of approval or denial of the transaction request from the transaction interface.   
     
     
         16 . The non-transitory computer readable storage medium of  claim 15 , wherein the transaction request sent from the mobile device includes a consumer identifier and the product code data. 
     
     
         17 . The non-transitory computer readable storage medium of  claim 15 , wherein a payment account of the consumer is selected from the group consisting of:
 a credit card account;   a debit card account;   an E-wallet account; and   other electronic stored value account.   
     
     
         18 . The non-transitory computer readable storage medium of  claim 15 , wherein the transaction application is further configured to instruct the computer processor to perform the step of: selecting a payment account from a plurality of available payment accounts such that each of the payment account of the plurality of payment accounts has a respective consumer payment account identifier, wherein the input data includes consumer financial account information for use in settling the financial amount via the transaction processing system, the financial account information selected from a plurality of available consumer financial accounts. 
     
     
         19 . The non-transitory computer readable storage medium of  claim 18 , wherein the payment account identifier also identifies corresponding payment account information of the consumer, wherein payment account information is not included in the transaction request and is instead obtained from a consumer profile stored at the transaction interface via a consumer identifier. 
     
     
         20 . The non-transitory computer readable storage medium of  claim 15 , wherein the product code data is configured as a lookup identifier as a sequence of characters for use in matching the product data stored in the merchant profile. 
     
     
         21 . The non-transitory computer readable storage medium of  claim 15 , wherein the merchant profile is one of a plurality of merchant profiles assigned to respective different merchants stored at the transaction interface. 
     
     
         22 . The non-transitory computer readable storage medium of  claim 15 , wherein the transaction is initiated based on said receiving of the product code data by the mobile device from a consumer environment. 
     
     
         23 . The non-transitory computer readable storage medium of  claim 15 , wherein the transaction type is one of a plurality of different transaction types for the merchant in the merchant profile, each of the transaction types requiring respective different input data from the user for the merchant. 
     
     
         24 . The non-transitory computer readable storage medium of  claim 23 , wherein the transaction type dependent instructions of the identified transaction type are different than other transaction type dependent instructions of another transaction type of the plurality of transaction types. 
     
     
         25 . A transaction system for coordinating processing of a transaction request from a mobile device associated with a transaction between a consumer and a merchant, the transaction associated with the merchant providing a product to the consumer, the system comprising:
 a computer processor coupled to a memory, wherein the computer processor is programmed via a set of instructions stored in the memory to coordinate processing of the transaction request by:   receiving by the computer processor the transaction request from the mobile device including a consumer identifier and product code data, the product code data associated with product data stored in the memory in a merchant profile assigned to the merchant;   accessing by the computer processor a lookup database using the product code data to identify a transaction type for the merchant in the merchant profile, the transaction type associated with the product data, the transaction type requiring respective input data from a user of the mobile device based on workflow instructions other than payment type instructions;   implementing by the computer processor the workflow instructions by sending transaction type dependent instructions for presentation on a user interface of the mobile device indicating the required input data;   receiving by the computer processor the required Input data from the mobile device in response to the transaction type dependent instructions displayed;   creating the transaction request by the computer processor and sending the transaction request to a payment platform;   receiving by the computer processor approval of the transaction request from the payment platform in the event a payment account of the consumer has sufficient funds to cover an amount of the transaction; and   sending by the computer processor a confirmation of the approval of the transaction request.   
     
     
         26 . The transaction system of  claim 25 , wherein the confirmation is sent to the merchant via a merchant interface running on a point of sale terminal as the computer device. 
     
     
         27 . The non-transitory computer readable storage medium of  claim 25 , wherein the payment account of the consumer is selected from the group consisting of:
 a credit card account;   a debit card account;   an E-wallet account; and   other electronic stored value account.   
     
     
         28 . The non-transitory computer readable storage medium of  claim 25 , wherein the transaction application is further configured to instruct the computer processor to perform the step of: selecting the payment account from a plurality of available payment accounts such that each of the payment account of the plurality of payment accounts has a respective consumer payment account identifier, wherein the input data includes consumer financial account information for use in settling the financial amount via the transaction processing system, the financial account information selected from a plurality of available consumer financial accounts. 
     
     
         29 . The non-transitory computer readable storage medium of  claim 28 , wherein the payment account identifier also identifies corresponding payment account information of the consumer, wherein payment account information is not included in the transaction request and is instead obtained from a consumer profile stored at the transaction interface via the consumer identifier. 
     
     
         30 . The non-transitory computer readable storage medium of  claim 25 , wherein the product code data is configured as a lookup identifier for use in matching the product data stored in the merchant profile. 
     
     
         31 . The non-transitory computer readable storage medium of  claim 30 , wherein the product code data includes encoded symbology information encoded using a barcode coding scheme. 
     
     
         32 . The non-transitory computer readable storage medium of  claim 25 , wherein the merchant profile is one of a plurality of merchant profiles assigned to respective different merchants stored at the transaction interface. 
     
     
         33 . The non-transitory computer readable storage medium of  claim 25 , wherein the transaction is initiated based on said receiving of the product code data by the mobile device from a consumer environment. 
     
     
         34 . The non-transitory computer readable storage medium of  claim 25 , wherein the transaction type is one of a plurality of different transaction types for the merchant in the merchant profile, each of the transaction types requiring respective different input data from the user for the merchant. 
     
     
         35 . The non-transitory computer readable storage medium of  claim 34 , wherein the transaction type dependent instructions of the identified transaction type are different than other transaction type dependent instructions of another transaction type of the plurality of transaction types.