Patent Publication Number: US-10783515-B2

Title: Method and system for conducting wireless electronic credit card transactions

Description:
TECHNICAL FIELD OF INVENTION 
     The invention relates to the field of electronic payment card transactions. More particularly, the invention relates to providing electronic wireless credit card transactions to small businesses in conditions where the wireless telecommunications network is old and/or underdeveloped. 
     BACKGROUND 
     Almost every adult person on the planet needs a credit card, and almost every business on the planet needs to be able to accept them. Due to this fundamental need, there is a diverse array of technologies that cater for the need to conduct these electronic transactions. The most common method involves the use of dedicated wireless credit card terminals that are connected either to a payment network, like VISA or MASTERCARD, or to an card issuing bank. 
     The dedicated payment network infrastructure and devices are expensive, however, and therefore cheaper mobile phone accessory based technologies have been brought to the market. In these technologies there is a smartphone 3rd party application, aka. an “app”, and an accessory payment card reader. 
       FIG. 1  shows a known prior art method. In this method, the payment amount is entered on the mobile payment app with the user interface of the phone. The transaction amount and other transaction details are transmitted to the card reader via Bluetooth/WiFi. A card (Chip and PIN, magnetic stripe, or NFC) is inserted/swiped/tapped on the card reader that reads the card information. The card reader encrypts all the transaction details including card details, transaction amount and transaction ID, and transmits a single payload (P) to the mobile app via Bluetooth/WiFi. Payload P is about 2,000 characters long. The app sends this data payload to a back-end server via Internet. 
     From the back-end server, transaction details are sent via standard secure protocols (secure socket layer (SSL)) to the issuing bank/payment processor to get authorization for the payment. If everything is ok with the transaction (card is valid and the funds are available), the back-end server gets an ‘authorization ok’ message from the issuing bank/payment processor. The back-end server then sends a message to the mobile app confirming authorization. A ‘capture’ message is sent to the issuing bank to withhold the funds, and then a ‘transaction accepted’ message is sent back to the app, and is displayed for users to know the transaction has been completed. 
     KR2001095371A discloses a method for communicating previously stored payment card details via GSM SMS (Short Message Service). This document is cited here as reference. 
     The prior art has notable disadvantages in emerging economies, e.g. Africa, in that a wireless Internet connection is not readily available in all locations for smartphones. Further, the prior art techniques using SMS for payment card data communication are unsuited to ad-hoc payment card transactions. 
     SUMMARY 
     The invention under study is directed towards a system and a method for effectively providing ad-hoc payment card transactions via a smartphone app in a mix of network conditions that is typical to an emerging economy, e.g. Africa. 
     A further object of the invention is to present a system and a method where the card reader is connected to the smartphone app via Bluetooth, and the smartphone app sends the payment data payload (P) via Internet as a first choice, and if an internet connection is not available, or the bandwidth is insufficient uses SMS and/or USSD as a second choice. 
     In one aspect of the invention the payment data payload is of the standard size, and therefore a plurality of SMS (Short Message Service) and/or USSD (Unstructured Supplementary Services Data) messages are sent each containing an identifying header. The back end server assembles the payment data payload from the plurality of received SMS and/or USSD messages. Then the payment is processed in the usual way. This system and method accrues a number of advantages solving the problems of the prior art. 
     An electronic payment system is in accordance with the invention and comprises a mobile station, a payment card reader, a communication network and a payment processing server, wherein,
         the payment card reader is arranged to be connected into a data port of the mobile station,   the mobile station is arranged to comprise a third party application controlling said payment card reader,   said payment card reader is arranged to read payment details from a payment card,   said third party application is arranged to read and/or receive payment details from the payment card reader and transmit said payment details via a wireless Internet connection if said connection is available as a first choice, or via a plurality of SMS and/or USSD messages as a second choice if said wireless Internet connection is unavailable.       

     An electronic payment method is in accordance with the invention and includes a mobile station, a payment card reader, a communication network and a payment processing server, wherein,
         the payment card reader connects into a data port of the mobile station,   the mobile station comprises a third party application controlling said payment card reader,   said payment card reader reads payment details from a payment card,   said third party application reads and/or receives payment details from the payment card reader and transmits said payment details via a wireless Internet connection if said connection is available as a first choice, or via a plurality of SMS and/or USSD messages as a second choice if said wireless Internet connection is unavailable.       

     A software program product stored in at least one data storage device is in accordance with the invention, said software program facilitating electronic payments in a system comprising a mobile station, a payment card reader, a communication network and a payment processing server, wherein,
         the payment card reader software is arranged to be connected into a data port of the mobile station,   the mobile station is arranged to comprise a third party software application controlling said payment card reader software,   said payment card reader software is arranged to read payment details from a payment card,   said third party software application is arranged to read and/or receive payment details from the payment card reader software and transmit said payment details via a wireless Internet connection if said connection is available as a first choice, or via a plurality of SMS and/or USSD messages as a second choice if said wireless Internet connection is unavailable.       

     The inventive system allows a merchant to accept payment cards wherever only the most basic GSM network is available. The merchant does not need a dedicated Point of Sale terminal to do that. With the smartphone app and the peripheral card reader using the inventive method, a merchant in the middle of a remote location in Africa or Siberia can accept payment cards on the spot, right there and then, if basic GSM network is available, but can also use the same devices in e.g. central London with 4G networks. A further advantage is that the inventive system works with the card reader encryption, providing the same data security as traditional dedicated Point of Sale card terminals. 
     In addition and with reference to the aforementioned advantage accruing embodiments, the best mode of the invention is considered to be a smartphone 3rd party application and a card reader connected thereto, where payment data is transmitted through the wireless Internet connection as the first choice and as a second choice the payment data is transmitted via a plurality of text messages to a payment processing server via the radio devices of the mobile phone controlled by the 3rd party app. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       In the following the invention will be described in greater detail with reference to exemplary embodiments in accordance with the accompanying drawings, in which 
         FIG. 1  demonstrates an embodiment of the prior art. 
         FIG. 2  demonstrates an embodiment 20 of the electronic credit card transaction system in accordance with the invention as a block diagram. 
         FIG. 3  demonstrates an embodiment 30 of the electronic credit card transaction method in accordance with the invention as a schematic flow diagram. 
         FIG. 4  demonstrates a schematic diagram of one or more embodiments of the invention. 
       Some of the embodiments are described in the dependent claims. 
     
    
    
     DETAILED DESCRIPTION OF EMBODIMENTS 
     In  FIG. 2  the smartphone and the card reader form a mobile Point Of Sale (mPOS), as shown. The smartphone is any smartphone, such as iPhone, Android, Sailfish, and/or Windows phone capable of running mobile third party software applications, known as “apps”. The Card reader is connected to mobile station via audio port, Bluetooth wireless, data port, NFC, IrdA, Wifi or any other wireless or wireline communication channel. In some embodiments the mobile phone is replaced by a tablet, e.g. an iPad, Kindle or a similar mobile computer that does not have a conventional phone feature. 
     The smartphone app has an intelligent switch that determines if the Internet connection is available to transmit the transaction payment card details via the traditional Internet-based route. If the Internet connection is of good quality and/or bandwidth, payment card details are transmitted via TCP/IP protocols to at least one back-end server, as shown in  FIG. 4 . Also other communication protocols may be used in accordance with the invention. 
     If, the Internet connection does not have sufficient bandwidth or availability, the payment card data payload is automatically routed through SMS/USSD, as shown in  FIG. 4 . The mobile smartphone app splits the data payload into a fixed number of segments, for example to 14 segments/messages such that each segment contains about 150 characters. Each of these segments (P 1  . . . n) is tagged with a unique serial identification number. 
     Then, in accordance with some embodiments of the invention, it is required that each SMS message segment contains the serial number of the message, and how many messages are in that data payload batch, e.g. (1/14), (2/14) and so on. A random tag is also inserted, which helps the mobile smartphone app validate any confirmatory message as truly coming from the back end server, and not from some other possibly malicious source. 
     Thus, each message has a unique serial identification number where, for instance, the first 8, characters are random, and last 2 characters are serial numbers as shown in the embodiment of  FIG. 3 . The actual 150 character transaction information may be in any part of the SMS and/or USSD message, preferably at the end of the message, as also is shown in  FIG. 3 . This gives a total of 160 characters per message sent from the mobile smartphone app to the back end server. 
     The back end server checks to be sure that all segments are complete. If any segment(s) is/are not delivered to the back end server, the back end server sends a message back to the smartphone app, indicating the particular missing segments so that the smartphone app can send those segments again, until the whole data payload is completely received at the back end server. A confirmatory message from the back end server then indicates to the smartphone app that all SMS and/or USSD segments/messages are delivered, and there is no more a need to send them in some embodiments. 
     In some embodiments, if the app does not receive any message from the back end server within a specified time (T 1 ), the app sends the whole batch of messages again at specified intervals until there is an acknowledgement message from the back end server. 
     In some embodiments if the process is not completed by the end of a specified amount of time (T 2 ) [T 2 &gt;T 1 ], the whole transaction is terminated, and must be started all over again. Exemplary times in some embodiments are T 1 =10s and T 2 =30s, but other values are also possible in accordance with the invention. 
     At the back end server, the segments are identified with the serial identification number, which was tagged on them at the mobile smartphone app. The segments of payment data payload are then recombined at the back end server. The recombination forms a single, still encrypted, data payload P identical to the original payload transmitted from the card reader that read the payment card. 
     It is worth special attention that at NO point during the whole aforementioned inventive method or system (i.e. transmission, splitting, tagging, recombination . . . ) is the original encryption of the card reader broken or decrypted in any way. This ensures that point to point encryption is preserved. This means that while the smartphone is used as a medium for payment card data communication, the data security is the same as in using the conventional far more expensive dedicated Point of Sale card terminal solution. 
     The invention has been explained above with reference to the aforementioned embodiments and several commercial and industrial advantages have been demonstrated. The methods and arrangements of the invention allow the use of economically affordable ad hoc/instant payment card transactions via the means of a card reader accessory and a mobile smartphone app in almost any cellular network that supports the basic SMS and/or USSD. In addition to cheaper cost, data security is maintained at the same level as in more expensive prior art systems. 
     The invention has been explained above with reference to the aforementioned embodiments. However, it is clear that the invention is not only restricted to these embodiments, but comprises all possible embodiments within the spirit and scope of the inventive thought and the following patent claims. 
     REFERENCES 
     
         
         KR2001095371A, HONG SEONG PYO, SAMSUNG ELECTRONICS CO LTD, 2001