Abstract:
Techniques for credit card processing are provided. A credit card with a wireless interface wirelessly connects with a mobile device of a consumer that possesses the credit card. The mobile device is a relay between the credit card and a transaction processing device for a transaction to prove the credit card is present for the transaction and obtain Card Present rates for a retailer of the transaction.

Description:
BACKGROUND 
       [0001]    Automation for goods and services has reached record levels in society. Examples are everywhere from online banking and purchasing to a wide-range of devices and physical appliances that include computing and networking capabilities, which were just wishful dreams only a decade ago. For the most part, these advances have occurred because of breakthroughs in electronics and wireless communications, which have allowed complex processing and network connectivity to be achieved in the smallest of physical devices, such as a smart phone or other handheld computing devices, for relatively small cost and effort. 
         [0002]    In addition, many retailers now gear services and promotions toward these devices for purposes of interacting with, attracting, and keeping customers at the retailer. 
         [0003]    One aspect of business transacting that is evolving with the technology advancements is payment processing. Payment processing affects not just the consumer but the retailer (seller) as well. In order to have a most favorable credit card processing rate, consumers typically have to present their physical credit card to the merchants for purposes of achieving what is referred to as “Card Present” rates in the industry. 
         [0004]    A credit card that can be validated as being present and in the possession of the consumer is viewed as less risky than when one is not in possession of the consumer during a purchase. So, consumers performing self-service purchases (mobile pay or online ordering) have no what of demonstrating that their card is present; as a result, the merchant (seller) pays a higher transaction processing fee to the credit card company (referred to as “Card Not Present” (CNP) rates). The CNP rates can be 30 to 50 basis points of a transaction total price. 
         [0005]    In an attempt to overcome this problem, smartphone manufacturers have tried to include smart card hardware (so called “secure element”) as well as other hardware that emulates the behavior of a wireless card (ISO or Near Field Communication (NFC) standards). Using these solutions, consumers can get specific phones that can be linked to specific accounts; essentially, making the phone pretend to be the credit card when it is “tapped” or placed within a configured proximity of a card reader. The tapping process is inconvenient and usually proprietary to a specific bank and phone manufacturer combination due to the complexity of provisioning (the process of loading an account onto a phone), which is inflexible because linking to new accounts is not easily achieved and being forced to use certain smart phone apps with certain credit cards is inconvenient as well. 
       SUMMARY 
       [0006]    In various embodiments, techniques for credit card processing are presented. According to an embodiment, a method for credit card processing is provided. 
         [0007]    Specifically, an indication is received from a mobile device that the mobile device is in wireless communication with a payment card of a consumer. Next, the payment card is queried via interactions with the mobile device to complete a transaction with the consumer. Finally, the transaction is completed on behalf of the consumer and a retailer based on the information and transaction details associated with the transaction. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0008]      FIG. 1  is a diagram of a method for credit card processing, according to an example embodiment. 
           [0009]      FIG. 2  is a diagram of another method for credit card processing, according to an example embodiment. 
           [0010]      FIG. 3  is a diagram of a credit card processing system, according to an example embodiment. 
       
    
    
     DETAILED DESCRIPTION 
       [0011]      FIG. 1  is a diagram of a method  100  for credit card processing, according to an example embodiment. The method  100  (hereinafter “Point-Of-Sale (POS) transaction manager”) is implemented as instructions programmed and residing within memory and/or a non-transitory computer-readable (processor-readable) storage medium and executed by one or more processors. The processors are specifically configured and programmed to process the POS transaction manager. The POS transaction manager operates over a network. The network is wired, wireless, or a combination of wired and wireless. 
         [0012]    In an embodiment, the POS transaction manager processes on processors of a server of cloud processing environment. In some instances, the POS transaction manager processes on a Point-Of-Sale (POS) terminal of a retailer (such as a restaurant). The POS terminal can be, in some embodiments, a thin client that interacts with a remote server having the POS transaction manager. Moreover, the POS transaction manager can process on a Virtual Machine (VM) where the underlying physical processing environment and physical processors can vary depending upon the installation of the VM. In still other cases, the POS transaction manager operates on a client-based POS terminal. 
         [0013]    Consumers will continue to carry payment cards and government identification cards as a backup to power failure or technology break-downs. The POS transaction manager leverages the payment cards in conjunction with smartphone/mobile device (including wearable device) hardware to provide a novel way of applying mobile payment for a credit card transaction. 
         [0014]    Banks will re-issue all payment cards using the European MasterCard and Visa (EMV) format as part of the Visa and MasterCard mandate by 2015. These cards will be provisioned with account information in a secure domain when they are manufactured. This is standard operation. 
         [0015]    According to an embodiment herein, a Bluetooth Low Energy (BLE) circuit on the smartcard is introduced with the EMV mandated cards. This BLE interface is capable of being paired (using the consumer&#39;s Personal Identification Number (PIN), which is issued with the card) with a consumer&#39;s smartphone (mobile or wearable device), allowing the device to become a relay point between the smartcard and a brick-and-mortar Point-Of-Sale (POS) terminal or online purchasing outlets. When a consumer is using his/her smartphone for payments within the personal area network (PAN) radius of the BLE interface, the phone is able to activate the payment card and serve as a bidirectional conduit for the smartcard to communicate with a central processor collecting or handling the credit card transaction. 
         [0016]    It is noted that the smartphone (mobile or wearable device) is never responsible for decryption or storage of the payment; it is simply acting as a reader (via the Bluetooth interface) as well as a communication gateway to the processing engine. It does these actions in addition of course to running the payment application itself, which may display items for sale, up-sell based on purchases, allow confirmation of purchases, application of coupons, the ability to provide feedback, etc. 
         [0017]    NFC, Wi-Fi and Cellular Communications are other radio options, each with limitations in their practical reach and power requirement. Other radio options can apply as well without departing from the beneficial teachings provided herein and below. 
         [0018]    It is within this context that the processing of the POS transaction manager is now discussed with reference to the  FIG. 1 . 
         [0019]    At  110 , the POS transaction manager receives an indication from a mobile device that the mobile device is in wireless communication with a payment card of a consumer. The payment card can be a credit or debit card and it is a smart card having processing capabilities and as discussed herein also having wireless communication capabilities. The indication can be prompted unsolicited by the payment card or can be prompted by the mobile device. 
         [0020]    According to an embodiment, at  111 , the POS transaction manager identifies the mobile device as a registered device with the retailer on receipt of the indication. In other words and for security purposes, the consumer&#39;s mobile device is registered with the POS transaction manager. A registration process can be initiated in cases where no registration exists. 
         [0021]    In an embodiment, at  112 , the POS transaction manager acquires with the indication, the transaction details for the transaction. That is, the consumer is purchasing something (a good or a service from the retailer) and details of that purchase (item identification, price, discounts, loyalty information, etc.) are sent with the indication from the mobile device. 
         [0022]    In still another situation, at  113 , the POS transaction manager instructs the mobile device to pass an encryption key to the payment card for use in transferring information. That is, the mobile device of the consumer is acting as a proxy for the transaction and the payment mechanism, which is the payment card, so transferring payment details can be made more secure via an encryption-based approach. 
         [0023]    Continuing with the embodiment of  113  and in another embodiment at  114 , the POS transaction manager generates the encryption key as a temporary key that is tied to the transaction. 
         [0024]    At  120 , the POS transaction manager queries information from the payment card via interactions with the mobile device to complete the transaction with the consumer. Again, the mobile device is acting as a conduit or proxy for the payment card and the POS transaction manager. 
         [0025]    In an embodiment, at  121 , the POS transaction manager obtains from the information a payment card number (credit or debit card account usually listed on the face of the card distributed to the consumer). 
         [0026]    Continuing with the embodiment of  121  and in another embodiment at  122 , the POS transaction manager acquires from the information additional details that include one or more of: an expiration date for the payment card, a billing zip code for the consumer of the payment card, and a security code associated and tied to the payment card. 
         [0027]    In yet another situation, at  123 , the POS transaction manager decrypts the information received from the payment card where the payment card initially encrypts the information before supplying to the mobile device, and the mobile device passes the encrypted information through to the POS transaction manager for handling. So, the mobile device in this embodiment is unaware of how to decrypt the information provided by the payment card. 
         [0028]    Continuing with the embodiment of  123  and in another embodiment at  124 , the POS transaction manager uses a key that is registered to the consumer to decrypt the encrypted information. 
         [0029]    At  130 , the POS transaction manager completes the transaction on behalf of the consumer and the retailer based on the information and transaction details for the transaction. 
         [0030]    According to an embodiment, at  131 , the POS transaction manager sends receipt details back to the mobile device to display on completion of the transaction for viewing by the consumer and/or for storage by the consumer. 
         [0031]      FIG. 2  is a diagram of another method  200  for credit card processing, according to an example embodiment. The method  200  (hereinafter “mobile transaction app”) is implemented as instruction and programmed within memory and/or a non-transitory computer-readable (processor-readable) storage medium that executes on one or more processors of a handheld device; the processors of the handheld device are specifically configured to execute the mobile transaction app. The mobile transaction app is operational over a network; the network is wired, wireless, or a combination of wired and wireless. 
         [0032]    Whereas the POS transaction manager (the  FIG. 1  above) describes processing associated with credit card transaction processing from one or more devices controlled by or accessible to a retailer, the mobile transaction app describes processing associated with credit card transactions from the perspective of a consumer&#39;s mobile device that interacts with the retailer&#39;s devices (POS devices). 
         [0033]    At  210 , the mobile transaction app recognizes a wireless connection request from a payment card that is in proximity to a handheld device (smart phone, tablet, wearable device, etc.). 
         [0034]    In an embodiment, at  211 , the mobile transaction app pings (contacts) the payment card to initiate the wireless communication request. Another words, the consumer is completing a transaction and selects a payment option via an app on the consumer&#39;s handheld device, and the app (mobile transaction app) triggers the payment card to request a wireless connection. 
         [0035]    According to an embodiment, at  212 , the mobile transaction app identifies the wireless communication request as one of: a NFC request, a Bluetooth request, a BLE request, a Wi-Fi request, and a RF request. 
         [0036]    At  220 , the mobile transaction app establishes a wireless communication session for a transaction of a consumer. 
         [0037]    According to an embodiment, at  221 , the mobile transaction app creates a second communication session with the transaction server to facilitate the proxying ( 230 ) between the payment card and the transaction server. 
         [0038]    In an embodiment, at  222 , the mobile transaction app interacts with the consumer to authenticate the wireless communication session with the payment card. 
         [0039]    At  230 , the mobile transaction app proxies communications between the payment card and a transaction server during the wireless communication session to complete the transaction between the consumer and a retailer. 
         [0040]    According to an embodiment, at  231 , the mobile transaction app encrypts details passed from the payment card to the transaction server based on an encryption key acquired for the transaction from the transaction server. 
         [0041]    In an embodiment, at  240 , the mobile transaction app scrubs any transaction details remaining in memory or in storage of the handheld device when the transaction completes. 
         [0042]      FIG. 3  is a diagram of a credit card processing system  300 , according to an example embodiment. The components of the credit card processing system  300  are programmed and resided within memory and/or a non-transitory computer-readable medium and execute on one or more processors of one or more devices. The credit card processing system  300  is operational over a network and the network can be wired, wireless, or a combination of wired and wireless. 
         [0043]    The credit card processing system  300  includes a POS transaction manager  301  and a mobile transaction app  302 . Each of these will be discussed in turn. 
         [0044]    The credit card processing system  300  includes a transaction device having the POS transaction manager  301  programmed within memory and/or a non-transitory computer-readable storage media. The transaction device executes the POS transaction manager  301 . Example processing associated with the POS transaction manager  301  was presented above in detail with reference to the  FIG. 1 . 
         [0045]    The POS transaction manager  301  is configured to interact with a mobile device of a consumer for a transaction to acquire payment card details from the mobile transaction agent  302 . That is, the POS transaction manager  301  communicates indirectly with the mobile transaction agent  302  via a mobile device of a consumer that processes a mobile transaction manager, such as the mobile transaction manager described above with reference to the  FIG. 2 . 
         [0046]    The credit card processing system  300  also includes a payment card device having a mobile transaction agent  302  programmed within memory and/or a non-transitory computer-readable storage media. The payment card device executes the mobile transaction agent  302 . Some aspects of the mobile transaction agent  302  were presented above with reference to the  FIGS. 1 and 2 . 
         [0047]    The mobile transaction agent  302  is configured to interact with the mobile device to process requests sent from the POS transaction manager  301  and return information to the POS transaction manager  301  via the mobile device. Again, the payment card device, via the mobile transaction agent  302 , does not directly communicate with the POS transaction manager; rather, the mobile device, via a mobile transaction manager, acts as a conduit or proxy for communications between the POS transaction manager  301  and the mobile transaction agent  302 . 
         [0048]    According to an embodiment, the payment card device is a credit card equipped with processing abilities and wireless communication abilities. In one case, the payment card device is European MasterCard and Visa compliant with added wireless communication capabilities, such as but not limited to: BLE, Bluetooth, NFC, RF, and/or Wi-Fi. 
         [0049]    The above description is illustrative, and not restrictive. Many other embodiments will be apparent to those of skill in the art upon reviewing the above description. The scope of embodiments should therefore be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled. 
         [0050]    The Abstract is provided to comply with 37 C.F.R. §1.72(b) and will allow the reader to quickly ascertain the nature and gist of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. 
         [0051]    In the foregoing description of the embodiments, various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting that the claimed embodiments have more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Description of the Embodiments, with each claim standing on its own as a separate exemplary embodiment.