Systems, methods, and computer readable media for conducting an electronic transaction via a backend server system

A method for conducting an electronic transaction with a backend server system includes interfacing a mobile device with a touch point to wirelessly obtain a backend server system address and an identification code. The touch point is associated with an electronic transaction terminal device to be utilized by a user of the mobile device to conduct an electronic transaction. Communication is established between the mobile device and the backend server system. The identification code and a mobile device identifier associated with the mobile device are received. It is determined whether one or more electronic certificates associated with the mobile device identifier are applicable for use in the electronic transaction. The identification code is used to provide at least one of the applicable electronic certificates to the terminal device and applying the at least one applicable electronic certificate to the electronic transaction.

TECHNICAL FIELD

The subject matter described herein relates to electronic payment and non-payment transactions. More particularly, the subject matter described herein relates to systems, methods, and computer readable media for conducting an electronic transaction via a backend server system.

BACKGROUND

Payments, loyalty transactions, and coupon redemptions are typically conducted at point of sale (POS) environments using paper currency, plastic cards, and/or manual entry of keys via traditional network connections that utilize dial up lines, Internet connections and/or wireless networks provided by merchants or merchant service providers. However, there is a growing trend of conducting these types of transactions using a mobile device (e.g., a smart phone). In order to allow consumers to make payments, send loyalty information, or redeem coupons/offers from mobile devices (at a merchant point of sale (POS), a merchant entity may be compelled to install a near field communications (NFC) reader and/or a barcode reader. Specifically, the merchant entity may integrate the NFC reader with point of sale system to be able to accept payment, loyalty transactions, coupons/offers, and other transactional data. However, this solution not only requires a merchant to incur expensive equipment costs related to the installation of an NFC reader at each POS terminal location, but the merchant may also have to take expensive, disruptive, and time consuming measures to enable their existing POS software to fully function with the NEC reader to wirelessly accept electronic payment, loyalty, coupons/offers, and the like. Although merchants want to accept transactions initiated from mobile devices, the significant investment of time and money required to add an NEC reader is preventing a number of merchant entities from providing better service to mobile device-using customers.

Accordingly, in light of these disadvantages, there exists a need for systems, methods, and computer readable media for conducting an electronic transaction via a backend server system.

SUMMARY

According to one aspect, the subject matter described herein relates to systems, methods, and computer readable media for conducting an electronic transaction via a backend server system. In one embodiment, a method includes interfacing a mobile device with a touch point to wirelessly obtain a backend server system address and an identification code, wherein the touch point is associated with an electronic transaction terminal device to be utilized by a user of the mobile device to conduct an electronic transaction and the identification code is associated with the electronic transaction terminal device or the touch point. The method also includes establishing communication between the mobile device and the backend server system using the backend server system address, receiving, at the backend server system from the mobile device, the identification code and a mobile device identifier associated with the mobile device, and determining, at the backend server system, whether one or more electronic certificates associated with the mobile device identifier are applicable for use in the electronic transaction. The method further includes using, at the backend server system, the identification code to provide at least one of the applicable electronic certificates to the electronic transaction terminal device and applying, at the electronic transaction terminal device, the at least one applicable electronic certificate to the electronic transaction.

DETAILED DESCRIPTION

In accordance with the subject matter disclosed herein, systems, methods, and computer readable media for conducting an electronic transaction via a backend server system are disclosed. The present subject matter provides a low cost solution for conducting near field communications (NEC) based transactions within an existing point of sale (POS) or point of service environment without the utilization of an NFC wireless device reader. NEC may include any wireless communications conducted at, for example, ISO 14443 and ISO 18092 interfaces.

FIG. 1depicts an exemplary system100that includes a touch point102, a mobile device104, a backend server system106, an electronic transaction terminal device108, and a cash register109. Notably, touch point102and electronic transaction terminal device108may be associated with each other and co-located (e.g., in relative close proximity) at a common location or area101(e.g., same store, same point of sale counter, same kiosk, etc.). Cash register109may also be located in common area101. Although the following disclosure describes a point of sale (POS) setting and a payment transaction, the systems and methods described herein may also be utilized to conduct a non-payment transaction (or a combination of a payment and non-payment transaction) without departing from the scope of the present subject matter.

Referring toFIG. 1, mobile device104may comprise a smartphone, a personal digital assistant (PDA), a tablet computer, or any other portable computing device. In some embodiments, mobile device104may include a near field communications (NEC) module or chipset112, a mobile wallet application114, one or more customer mobile applications116, and a local storage including one or more electronic certificates117(or electronic certificate identifiers associated with electronic certificates stored in backend server system106). NEC module112may include any circuit component that enables mobile device104to communicate with passive NEC enabled devices (e.g., an unpowered NEC smart tag) or active NEC enabled devices (e.g., a powered NEC wireless reader) via NEC. In one embodiment, an authentication process to authenticate mobile device104may be conducted between NEC module112and NEC tag110. Mobile wallet application114includes a software based application that may be configured to manage and utilize the one or more customer mobile applications116(e.g., mobile device applications). In some embodiments, customer mobile application116may include a software based application that is configured to enable mobile device104to conduct a transaction with a particular point of sale, point of service, and/or point of interest. For example, an exemplary customer mobile application116(e.g., mobile device applications) may include a retail POS application, a healthcare service point application, a transportation service point application, a government service point application, an enterprise service point application, a support service point application, a kiosk service point application, an access control service point application, a banking service point application, an automatic teller machine (ATM) service point application, a boarding pass service point application, and an entertainment service point application. In one embodiment, an authentication process to authenticate mobile device104may be conducted between consumer mobile application116and NFC tag110.

Similarly, mobile wallet application114may also be configured to manage and utilize the one or more electronic certificates117. In some embodiments, electronic certificates include electronic coupons, electronic loyalty cards, electronic offers, electronic payment cards, electronic credit cards (open loop and/or closed looped), electronic event or ride tickets, electronic rewards, a digital receipt, a payment identifier, a boarding pass, an electronic check-in identifier, an electronic hotel key, a membership card/key, an electronic gift card, an electronic prepaid card, an electronic business card, and the like.

In some embodiments, touch point102may include any device or article configured to provide information (e.g., an identifier or identification code) to an interfacing mobile device (e.g., mobile device104). For example, touch point102can comprise a smart poster that includes a tag110that may be NFC enabled (e.g., an NFC smart tag) and wirelessly provide information to an interfacing mobile device104equipped with an NFC chipset112. Alternatively, tag110on touch point102may include a QR code or a barcode that may be scanned by a camera (not shown) or like device equipped on mobile device104.

In some embodiments, touch point102is positioned in close proximity to an electronic transaction terminal device108and is easily accessible to a customer. Tag110on touch point102may include identification information that is related or associated to electronic transaction terminal device108and/or the specific point of sale location (e.g., area101). Specifically, tag110may be programmed or encoded with an identifier or an identification code that can be directly or indirectly associated with that specific electronic transaction terminal device/location, touch point102itself, and/or a mobile device payment/loyalty/offer application that is supported in a backend server system106that is communicatively connected to the electronic transaction terminal device108. For example, tag110may be configured to contain an identification code or identifier associated with electronic transaction terminal device108. Alternatively, the identification code or identifier may include a touch point identifier that is mapped to an electronic transaction terminal device identifier (e.g., such mappings may be stored in backend server system106), an application identifier (e.g., identifier for customer mobile application116), a banking terminal device identifier, an automatic teller machine (ATM) terminal device identifier, and/or a backend server system identifier.

As mentioned above, tag110may include a passive NEC tag. As used herein, the terms “passive tag” and “NEC passive tag” refers generally to a passive NEC or RF tag device that is powered by an interfacing NFC-enabled device. For example, after an NFC-enabled device is brought in close proximity to create an interface with an NEC passive tag, the NEC passive tag may be activated by obtaining power from the electromagnetic field generated by the NFC-enabled device. For example, an NEC passive tag can be capable of communicating a variety of information that may include, but is not limited to, a location identifier, such as a uniform resource locator (URL), internet protocol (IP) address, or a uniform resource identifier (URI), tag identification number, other identification numbers, or the like. In some embodiments, the communicated information may be associated with or identify touch point102, electronic transaction terminal108, or backend server system106.

Although depicted inFIG. 1as a single entity, backend server system106may comprise one or more computer servers that are configured to help facilitate an electronic transaction conducted between mobile device104and electronic transaction terminal device108. As used herein, an electronic transaction may include a wireless payment and/or non-payment transaction that is conducted in part using a wireless mobile device. To conduct such an electronic transaction, the mobile device may utilize one or more electronic certificates or softcards (e.g., electronic and/or virtual based credit cards, coupons, loyalty cards, etc. that are stored locally in the mobile device or on a backend network server). The electronic transaction may also include, in part, a purchase transaction that occurs when a mobile device user presents, for example, a good for purchase at a physical point of sale (e.g., a cash register).

In some embodiments, backend server system106may include one or more of: a trigger management server (TMS), a content management server (CMS), a content provider server, an electronic certificate repository (e.g., electronic certificate database118), and an over the air (OTA) provisioning server. Backend server system106may include a control module115that is responsible for the management and operation of backend server system106. Control module115may also be configured to authenticate mobile device104prior to conducting a transaction. For example, control module115in backend server system106may use the mobile device identification code (or mobile subscriber number/identifier) to authenticate mobile device104. Backend server system106may also include an electronic certificate database that includes a plurality of various electronic certificate identifiers mapped to a plurality of mobile device identifiers (or mobile subscriber identifiers/numbers). In some embodiments, backend server system106is further configured to include the electronic certificates associated with the plurality of electronic certificate identifiers. In some embodiments, backend server system106may also include a database (not shown) that contains entries of mappings between a plurality of touch point identifiers and a respective plurality of electronic transaction terminal devices. In one embodiment, backend server system106may be communicatively coupled (e.g., either wired or wirelessly) to electronic transaction terminal device108. Similarly, mobile device104may communicate with backend server system106using WiFi, cellular/wireless communications (e.g., 3G, 4G, long term evolution (LTE), etc.), or any other emerging wireless communications.

Referring toFIG. 1, electronic transaction terminal device108may include a point of sale terminal device, a point of service terminal device, a point of interaction (POI) terminal device, a banking terminal device, an automatic teller machine (ATM) terminal device, and the like. In some embodiments, electronic transaction terminal device108may be located at a store, a taxi cab, a vending machine, a kiosk, and the like. Notably, electronic transaction terminal device108may include a POS interface application120and a POS application122. In one embodiment, each of POS interface application120and POS application122includes a special software module or application that is executed by a hardware processor included in electronic transaction terminal device108. When executed, POS interface application120may communicate with customer mobile application116(e.g., mobile device application) using a secured channel directly or indirectly via backend server system106(e.g., over an Internet protocol network). In one embodiment, POS interface application120may reside in a DOS, Windows, or Android/Linux operating system computer that is configured to communicate with backend server system106via an IP network, a cellular/wireless network, or a leased/dedicated line using web services, XML, or a proprietary application programming interface (API).

In addition, POS interface application120may communicate with POS application122using a driver (e.g., UPOS, oPOS or jPOS application software), native mode, or emulation mode to compel electronic transaction terminal device108to communicate with backend server system106to identify whether electronic certificates, loyalty programs, and the like should be applied to an electronic transaction being conducted (see details below). In some embodiments, mobile device104may communicate with electronic transaction terminal device108using WiFi, cellular/wireless communications (e.g., 3G, 4G, long term evolution (LTE), etc.), or other emerging wireless communications.

In one embodiment, a customer (e.g., mobile device user) utilizes mobile device104provisioned with a supported customer mobile application116(e.g., from a retailer, from a service provider, or from companies supporting cloud based payments, like Google, Paypal, Mastercard, etc.) at a point of sale register to initiate a purchase transaction of one or more items. Although the following example describes a purchase and/or payment transaction, other electronic transactions may be conducted without departing from the scope of the present subject matter. For example, the electronic transaction being conducted may include at least one of a loyalty transaction, a coupon redemption transaction, an offer redemption transaction, a digital receipt pickup transaction, an electronic coupon pickup transaction, an electronic coupon pickup transaction, a reward pickup transaction, a one-touch checkout transaction, an order transaction, and a non-payment transaction. Other exemplary electronic transactions includes a combination of payment and non-payment transaction, an electronic certificate delivery transaction, a printing advice transaction, an access control transaction, a boarding pass transaction, and an electronic certificate redemption transaction.

In this example, electronic transaction terminal device108is not equipped with an NEC reader and is located proximate to touch point102within a common area/location101. The mobile device user may interface or “tap” mobile device104with an NFC smart tag110of touch point102in order to obtain, via NEC, an identification code identifying electronic transaction terminal device108and an address (e.g., a URL or IP address) associated with backend server system106. Mobile device104may then be configured to use the address to wirelessly transmit the identification code and a mobile device identifier (or a mobile subscriber identifier) which identifies mobile device104to backend server system106. Specifically, the NEC tap informs backend server system106that a specific customer has interfaced mobile device104with a touch point102associated with a specific electronic transaction terminal device108or point of sale location/area101. Backend server system106may then utilize the identification code to establish communications with electronic transaction terminal device108.

After mobile device104has interfaced with touch point102, a sales clerk may use checkout cash register109to register/scan the items the customer is attempting to purchase. As an item is scanned, POS application122(via POS interface application120) may communicate the item information to backend server system106. In addition, POS application122may compel electronic transaction terminal device108to identify if there are any applicable electronic certificates (e.g., coupons/offers/promotions/etc.) available in backend system server106(e.g., in an online repository or in electronic certificate database118) which can be applied to the purchase transaction based on a mobile device identifier and the type products the mobile device user has presented for purchase.

Specifically, electronic certificates may be stored on the backend in a cloud based manner. For example, electronic certificate database118may include a plurality of electronic certificates and/or a plurality of electronic certificate identifiers. In some embodiments, the electronic certificates and identifiers may be mapped to mobile device identifiers or some other identifier (e.g., a loyalty program identifier/number, a membership identifier, a customer identifier etc.). The terms “tap,” “NFC tap,” and “interface” can be used to mean the same actions. As used herein, the terms “tap” and “NFC tap,” in reference to NFC-enabled devices and wireless transceivers such as device readers or NFC passive tags, means to provide a close or near field interface between an NFC-enabled device and a wireless transceiver.

In some embodiments, mobile device104may be configured to only provide customer identification information (e.g., a mobile device identifier) to backend server system106since payment, loyalty, coupons/offers and other data may be stored in the cloud corresponding to the identification information. Similarly, the electronic certificates and identifiers may also be mapped to identifiers that are associated with goods or services that may be scanned/registered at a point of sale (e.g., cash register109). Thus, when a customer has an item for purchased scanned at the point of sale, electronic transaction terminal device108may provide an associated product identifier to backend server system106. Backend server system106may then query database118to determine if any electronic certificates correspond to the product identifier and/or an identifier corresponding to the customer (e.g., a loyalty membership identifier or a mobile device identifier).

In some embodiments, POS application122may also compel electronic transaction terminal device108to identify if there is a loyalty program that a merchant (e.g., a merchant associated with electronic transaction terminal device108or a manufacturer of a product being purchased) is conducting and/or a loyalty program where the customer is currently a registered member. If either is true, backend server system106may provide the applicable electronic certificates and/or loyalty program information to POS interface application120. Electronic transaction terminal device108may subsequently apply the received electronic certificates and/or loyalty program information to the purchase transaction.

In some embodiments, POS application122may send the resulting payment amount of the purchase transaction to mobile device104for display on the customer's mobile device screen. POS application122may also subsequently request the customer to select a payment option. If the payment amount exceeds a certain value (e.g., a predefined threshold value), customer mobile application116may prompt the mobile device user to enter a PIN or password. In some embodiments, consumer payment information is sent to electronic transaction terminal device108based on the payment type selected by the mobile device user. The payment information may be open loop or closed loop payment information (e.g., track 1 and 2 data, or EMV data) or a payment card identifier that is associated with a cloud based payment card that is stored in backend server system106.

Once payment is received and accepted, POS application122may send a payment confirmation and transaction completion message to mobile device104(e.g., via SMS, email, a wireless signal, and the like). POS application122may also be configured to optionally send a digital receipt to mobile device104in a similar manner. In one embodiment, mobile device104may be configured to provide an email address to backend server system106upon interfacing with touch point102located at or near the electronic transaction terminal device108. Backend server system106may then communicate the email address to the electronic transaction terminal device being used by the mobile device user conducting the electronic purchase transaction. Upon completion of the purchase transaction, electronic transaction terminal device108may utilize the email address (associated with the mobile device user) to deliver a digital receipt to the mobile device user.

In an alternate embodiment, a phone number or a digital receipt repository address/identifier associated with the mobile device user may be provided to electronic transaction terminal device108in lieu of an email address. Similarly, an electronic business card or membership card containing at least one of an email address, mobile phone number, and digital receipt repository address may be provided. In addition, instead of providing the email address to backend server system106communicating with electronic transaction terminal device108, the email address may be provided directly to a mobile or stationary electronic transaction terminal device108.

In an alternate embodiment, POS application108may optionally send electronic certificates (e.g., electronic coupons and/or offers) to the customer while sending a copy of the electronic certificates to database118or an online repository associated with the customer. POS application108may also optionally send an updated loyalty points message and/or a thank you message (e.g., via SMS, email, a wireless signal, etc.) to the mobile device user at the conclusion of the transaction.

In an alternate embodiment, the present subject matter may be utilized in cooperation with an NFC reader. In such a scenario, customer mobile application116on mobile device104may send payment information, optional loyalty card number information, electronic coupons/offers data, and ordering information (e.g., if applicable in a pre-order fast food environment) to electronic transaction terminal device108. Specifically, POS application122at electronic transaction terminal device108may receive this information from NFC enabled mobile device104through an NFC reader (not shown) attached to electronic transaction terminal device108. POS application122may then complete the purchase transaction and confirm the transaction by sending a message to customer mobile application116. In one embodiment, POS application122may send a digital receipt and electronic certificates (e.g., electronic coupons/offers/loyalty points) back to customer mobile application116.

In some embodiments, POS application122may query backend server system106to determine if there is any information previously provided by the customer via mobile device104. If true, then payment, loyalty, and/or coupons/offers will be requested by backend server system106from a third party service provider (not shown) that is responsible for maintaining payment, loyalty, and coupons/offers associated with mobile device104or the mobile device user. The electronic certificate information will then be forwarded to electronic transaction terminal device108to reconcile the customer's shopping basket based on coupons/offers in addition to applying loyalty information and accepting payments. To provide additional security to the payment transaction, a customer may be asked to enter a PIN on mobile device104which is securely transferred to backend server system106to assure that NEC enabled mobile device104is being used by the rightful owner.

In one embodiment, mobile device104may conduct a transaction utilizing one or more electronic certificates117(or electronic certificate identifiers) that are stored locally. In such a scenario, mobile device104may be interfaced with touch point102, which is associated and co-located in area101with electronic transaction terminal device108. Upon interfacing, mobile device104may obtain a touch point identification code (or an identifier associated with electronic transaction terminal device108) from tag110on touch point102. Upon receiving the identification code, customer mobile application116on mobile device104may be selected or triggered to provide (e.g., pushes) the touch point identification code, a mobile device identifier, and an electronic certificate identifier (e.g., a coupon code) to backend server system106. Backend server system106may query a database that maps touch point identification codes to electronic transaction terminal devices to determine the location of electronic transaction terminal device108. Backend server system106subsequently provides the electronic certificate (or electronic certificate identifier) to POS interface application120over IP or a wireless network. POS interface application120provides the electronic certificate to POS application122, which applies the electronic certificate (e.g., a coupon code) to the purchase transaction, adjusts the purchase amount, and prompts the mobile device user (e.g., via mobile device104) for payment. A customer may provide payment by swiping, tapping, or inserting a payment card and/or mobile device at electronic transaction terminal device108. Thus, a coupon redemption based transaction may be completed without requiring an NEC reader. A customer can also complete payment and loyalty transactions using the similar approach along with or without a coupon or offer redemption.

In one embodiment, instead of interfacing with a touch point, mobile device104may utilize WiFi, Bluetooth, GPS, cellular triangulation, WiFi triangulation or some other vicinity determining wireless technology of mobile device104to link its physical presence near a service point (e.g., electronic transaction terminal device108or the point of sale location). For example, a mobile device may enter a specific zone or range designated by a vicinity determining device (e.g., a mobile device detection server that is located in area101, GPS satellites, cellular towers, etc.). The vicinity determining device detects the proximate mobile device and links the mobile device's presence to the service point (e.g., a nearby electronic transaction terminal device108). If this occurs, the vicinity determining device may read the mobile subscriber identifier from mobile device104and provide the information to backend server system106. Alternatively, mobile device104may wirelessly receive, from the vicinity determining device, an identifier associated with the point of sale location/device (e.g., electronic transaction terminal device108) which is provided to backend server system106by mobile device104. After this detection process is conducted, a transaction may be conducted in the same manner described above.

FIG. 2is a flow chart illustrating an exemplary method200for conducting an electronic transaction via a backend server system according to an embodiment of the subject matter described herein. In step202, a mobile device is interfaced with a touch point. In one embodiment, an NFC enabled mobile device is interfaced with a smart poster that includes a smart tag. Notably, the touch point is associated with an electronic transaction terminal device. Both the touch point and the electronic transaction terminal may be located in a common area along with a cash register that the customer (i.e., mobile device user) is conducting a purchase transaction.

In step204, a backend server system address and an identification code are obtained. In one embodiment, upon establishing an NFC communications link with the smart tag, the mobile device may wirelessly obtain a backend server system address and an identification code from the smart tag. In one embodiment, the identification code may identify either the touch point or the related electronic transaction terminal device.

In step206, a communications link is established between the mobile device and the backend server system. In one embodiment, the mobile device utilizes the backend server system address obtained from the touch point to establish a channel of communication with the backend server system.

In step208, an identification code and mobile device identifier is received. In one embodiment, the backend server system receives an identification code and a mobile device identifier from the mobile device via the established communications link.

In step210, the identification code is used to provide an electronic certificate to a terminal device. In one embodiment, the backend server system may utilize the identification code to establish communication with the corresponding electronic transaction terminal device as well as to query a database to locate at least one electronic certificate which may be applicable to an electronic transaction being conducted with the mobile device. For example, the backend service system may receive a product identifier (of a product being purchased) from the electronic transaction terminal device. The backend server system may then use the product identifier and/or the mobile device identifier to query the electronic certificate database for an applicable electronic certificate or electronic certificate identifier (e.g., an electronic certificate that is associated with the product identifier and/or the mobile device identifier). After obtaining an appropriate electronic certificate, the backend server system may provide the electronic certificate to the identified electronic transaction terminal device that is associated with the identification code.

In step212, the electronic certificate is applied to the electronic transaction. In one embodiment, the electronic certificate may be applied to the purchase transaction being conducted at the point of sale (e.g., at a cash register).

It will be understood that various details of the subject matter described herein may be changed without departing from the scope of the subject matter described herein. Furthermore, the foregoing description is for the purpose of illustration only, and not for the purpose of limitation.