US20110250866A1 - Conducting a mobile financial transcation using a secure element and sms - Google Patents
Conducting a mobile financial transcation using a secure element and sms Download PDFInfo
- Publication number
- US20110250866A1 US20110250866A1 US13/167,829 US201113167829A US2011250866A1 US 20110250866 A1 US20110250866 A1 US 20110250866A1 US 201113167829 A US201113167829 A US 201113167829A US 2011250866 A1 US2011250866 A1 US 2011250866A1
- Authority
- US
- United States
- Prior art keywords
- communication device
- mobile communication
- transaction
- mobile
- command
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/20—Point-of-sale [POS] network systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/325—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/326—Payment applications installed on the mobile devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/327—Short range or proximity payments by means of M-devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/42—Confirmation, e.g. check or permission by the legal debtor of payment
- G06Q20/425—Confirmation, e.g. check or permission by the legal debtor of payment using two different networks, one for transaction and one for security confirmation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
- H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
Definitions
- the present invention relates to data communications and wireless devices.
- wireless mobile devices that include a near field communication (NFC) device and a smart card (that uses an RFID for identification purposes) allow a person to securely make a simple transaction, such as for example, purchasing a bus ticket.
- NFC near field communication
- the person typically waves the wireless mobile device near a reader installed in a bus, and a price of the bus ticket is deducted from a total amount that is available and stored on the smart card of the wireless mobile device.
- the amount of the bus ticket can be forwarded to a server that can identify the identification code of the particular RFID and then subsequently charge the person for the purchase of the bus ticket.
- references discussed above illustrate that certain transactions are possible using wireless mobile devices
- one problem associated with the references are is that implementations described in the references are not useful in a wide variety of different platforms, but rather are typically tied to a specific platform.
- NFC devices are only usable with NFC readers.
- Another problem is that conventional wireless mobile devices generally have a very limited ability to be used in transactions.
- this specification describes a method and system for transmitting data between a wireless communication and a remote server.
- the method includes running a mobile application on the wireless communication device, in which the mobile application is a rich client application.
- the method further includes transmitting data associated with the mobile application between the wireless communication device and the remote server using short message service (SMS).
- SMS short message service
- the mobile application links corresponding data transmitted through the short message service (SMS) for use by the mobile application.
- FIG. 1 illustrates one implementation of a block diagram of a communication system including a wireless mobile communication device.
- FIG. 2 illustrates one implementation of radio element in the wireless mobile communication device of FIG. 1 .
- FIG. 3 illustrates one implementation of a wireless mobile communication device.
- FIGS. 4A-4C respectively illustrate an implementation of a secure element in the wireless mobile communication device of FIG. 1 .
- FIG. 5 illustrates one implementation of a point of sale terminal.
- FIGS. 6A-6D illustrate a flowchart for conducting a transaction according to one implementation.
- FIG. 7 illustrates one implementation of a secure element that is attachable to a wireless communication device.
- FIG. 8 illustrates a communication system in accordance with one implementation.
- FIG. 9 illustrates a communication system in accordance with one implementation.
- FIGS. 10A-10B illustrate example client user interfaces that are displayable on a display of the mobile communication device of FIG. 9 .
- FIG. 1 illustrates one implementation of a communication system 100 .
- the communication system 100 includes a hand-held, wireless mobile communication device 110 that (in one implementation) includes a radio element 120 and a secure element 130 .
- a display 124 is shown associated with the radio element 120
- antennas (not labeled) are shown as associated with each of the radio element 120 and the secure element 130 .
- Each antenna can physically be implemented in a manner that is different from the wireless antennas shown in FIG. 1 .
- an antenna can comprise a stripe that is passed along a reader, or comprise some suitable transmission mechanism.
- elements 120 and 130 are shown as distinct and separate, and display 124 is shown as connected to the radio element 120 , other configurations are possible. In particular, a combination in which a single processor is used to execute the functions that are currently performed and described herein as being provided by both the radio element 120 and the secure element 130 . Further as illustrated in FIG. 1 , both the radio element 120 and the secure element 130 are internal to the mobile communication device 110 , although in other implementations the secure element 130 can be external to the mobile communication device 110 , as described below. Also, various different functionalities can be included within the radio element 120 and the secure element 130 .
- the mobile communication device 110 has the functionality to communicate with one of many different a point of sale (POS) terminals 150 - 1 to 150 - n —in a contactless manner using a wireless protocol.
- the mobile communication device 110 can also similarly communicate with one or more point of entry (POE) terminals 190 - 1 to 190 - n .
- the point-of-sale terminal 150 receives one of the transaction request signals from the mobile communication device 110 and transmits the one transaction request signal to a transaction server 170 , typically using a communication channel 160 such as the Internet.
- the transaction server 170 verifies the transaction, and forwards a transaction verification signal to the management server 180 .
- the management server 180 identifies the user corresponding to the transaction verification signal, and provides a first transaction response signal back to the mobile communication device 110 as one of the transaction signals.
- the first transaction response signal is communicated back to the mobile communication device 110 using a communication channel that is different from the communication channel used to initiate the transaction.
- different transaction response signals can be communicated back to the mobile communication device 110 using communication channels from the management server 180 to the radio element 120 associated with the device 110 , as well as from the management server 180 to the secure element 130 through the POS ten iinal 150 or the POE terminal 190 . Further detailed descriptions of these implementations are discussed in greater detail below.
- FIG. 2 illustrates one implementation of the radio element 120 associated with the mobile communication device 110 , and illustrates the radio element 120 connected to the display 124 of the mobile communication device 110 .
- the radio element 120 includes a radio transceiver 122 that is adapted to send outgoing voice and data signals and receive incoming voice and data signals over a radio communication channel.
- the radio communication channel can be a digital radio communication channel, such as CDMA or GSM. Such a radio communication channel has the capacity to communicate both voice and data messages using conventional techniques.
- the radio transceiver 122 communicates with a radio processor 123 , which processor has the capability to perform not only the radio communication services necessary to allow for phone and data communications, but can also execute various programs that are stored in the memory 126 , which programs can receive inputs from the user via the display 124 and/or a keypad 125 associated with the mobile communication device 110 .
- application programs running on the radio processor 123 are, e.g., BREW or J2MF applications and can encompass a broad array of application types.
- current applications include games, enterprise applications, and multimedia applications.
- the radio processor 123 runs an application that provides movie and event information.
- Such an application can comprise ticketing applications, content, item and service purchase applications, and/or payment management applications (referred to herein also as “wallet applications”).
- the radio processor 123 also has the capability of recognizing secure communications, and transmits data which must be stored in a secure environment to the secure element driver 128 for transmission to the secure element 130 .
- transmissions to the secure element 130 can take place using an internal wired communication channel.
- the radio processor 123 also has the capability of receiving data from the secure element 130 , e.g., using the internal wired communication channel.
- the secure element 130 and the radio element 120 communicate using signals described in the Java Card 2.1 Platform API Specification.
- both the radio element 120 and the secure element 130 are disposed internally within a body of the mobile communication device 110 .
- the mobile communication device 110 is shown including a slot 400 , which allows for the insertion of a secure element 130 into the slot 400 .
- the secure element 130 can be purchased independently of the mobile communication device 110 .
- the secure element 130 can also be disposed into a slot that only provides for physical insertion and mechanical connection to the body of the mobile communication device 110 .
- the secure element can include a transceiver that allows for the communication with the radio element 130 through a wireless local communication channel.
- the radio element 120 also is illustrated as optionally including another transceiver 129 , such as a Bluetooth or WIFI transceiver, which can transmit and receive signals with an external device and then communicate signals to and from the radio processor 123 .
- This additional communication channel allows for communications between other external devices, such as an external Bluetooth enabled smartcard, and provides an additional communication channel that is useful for certain transactions, as described further herein.
- FIG. 4A illustrates one implementation of the secure element 130 associated with the mobile communication device 110 .
- the secure element 130 can be a smart card.
- the secure element 130 includes a secure processor 132 , a secure memory 133 , and a POS transceiver 134 adapted to send transaction request signals and receive transaction response signals over a first communication channel.
- the secure processor 132 communicates via the secure element driver 128 with the radio processor 123 using signals as described in the Java Card 2.1 Platform API Specification.
- the transaction request signals and the transaction response signals associated with the transaction can include an identification code associated with the user, as well as information relative to the transaction, such as item, quantity, vendor, and so on.
- the POS transceiver 134 is an NFC device, which uses an NFC modem.
- the POS transceiver 134 can also be a Bluetooth, WIFI or other transceiver.
- the POS transceiver is an NFC modem
- such an NFC modem will typically have a set of registers that can be read/written by the secure processor 132 . These registers are in turn available for reading and writing over the RFID communications channel and serve as a shared memory between the secure processor 123 within the secure element 130 and the RFID reader that is associated with the POS terminal 150 .
- This communication is specified, for example, in the ISO 14443A/B standard.
- the secure element can optionally include a radio/Bluetooth/WIFI transceiver 136 , which can communicate with other devices, such as a transceiver associated with the radio processor 120 or for other external devices having those communication capabilities, thus allowing for more flexibility.
- FIG. 4B shows another implementation of a secure element 130 , in which the radio element 120 does not communicate with the secure element 130 through a secure element driver 128 .
- the secure element 130 may be external to the mobile communication device 110 and as such is not connected to the radio element through the secure element driver 128 .
- this communication channel can be used to wirelessly obtain direct communications between the radio element 120 and the secure element 130 .
- This implementation allows for certain bidirectional communications with other devices, as well as with the radio element 120 , and as such more functionality and flexibility is achieved. This implementation is particularly useful since it establishes a direct local communication path with the radio element 120 , since there is not communications with the radio element 120 via the path of driver 128 .
- This implementation allows for certain bidirectional communications with other devices, as well as with the radio element 120 , and as such more functionality and flexibility is achieved.
- This implementation is particularly useful for establishing a direct local communication path with the radio element 120 , since there are no communications with the radio element 120 via the path of driver 128 . If either of the transceivers 129 or 136 are not associated with the respective radio element 120 or secure element 130 , and there is no direct connection between the radio element 120 and the secure element 130 , then a direct communication link between the radio element 120 an the secure element 130 will not exist. As such, while ticketing and many transactions can still exist, data from a real-time transaction performed using the secure element 130 cannot be made directly available to the radio processor and the applications stored thereon.
- a ticketing application can be programmed to provide an alert if a ticket receipt has not been received within a certain period of time. Such an alert would not be possible to program directly (although it could be programmed indirectly via the button panel on the phone).
- FIG. 7 illustrates one implementation of a secure element 130 that can be attached (or affixed) externally to a wireless communication device (e.g., mobile communication device 110 ).
- the secure element 130 has circular shape.
- the secure element 130 can have other suitable shapes—e.g., rectangular, triangular, and so on.
- the secure element 130 includes an embedded smart chip 702 that is capable of executing proximity services (e.g., services related to payments, ticketing, identification, sending coupons, etc.).
- the smart chip 702 is capable of 2-way wireless communication (e.g., RFID, NFC, Bluetooth, etc.) with a supporting 3rdParty terminal.
- the 2-way communication is performed using a communication protocol that is different from a communication protocol through which the mobile communication device sends or receives voice and/or data signals.
- Multiple application protocols NFC, MiFare, etc.
- the smart chip 702 is programmable. Accordingly, different application (for payments, ticketing, identification, coupons, etc.) can be developed, downloaded to the smart chip, and commissioned.
- the terminal in response to the secure element 130 being placed in close proximity with a suitable terminal, the terminal will trigger (via application protocol) an appropriate application stored in the smart chip, and the smart chip will respond appropriately with the terminal.
- the smart chip uses a low-power RF transmitter/receiver to communicate with a terminal.
- the low-power output of the smart chip makes it susceptible to RF interference from neighboring devices. Specifically problematic are components associated with the mobile communication device, e.g., battery, antennae (internal or external), to which the secure element 130 is affixed.
- the secure element 130 includes an RF shield to insulate the smart chip from external interference.
- a lining of the secure element 130 is composed of an RF absorbent material/lining. In general, each phone has different levels of interference, and a material, size and thickness of the RF lining can determine an effectiveness of the RF shield.
- an RF shield can be placed between the secure element 130 and the mobile communication device 110 .
- the secure element includes a ruggedized shell 704 that encases a smart chip (with antennae).
- the shell 704 is formed from a composite plastic or polymer.
- the shell 70 can be hard (and substantially inflexible) or be soft (and pliable).
- the shell 704 provides a protective membrane for the smart chip which prevents damage to internal circuitry, a surface to adhere to an RF lining and/or a mobile communication device with appropriate adhesive, and a surface to print branding and advertising.
- Types of adhesives that can be used to affix the secure element 130 to a mobile communication device include, for example, paper glue, super glue, polymers, and the like.
- the shell 704 has a maximum width (or diameter) of 25 mm, and has a maximum thickness (or depth) of 5 mm.
- FIG. 4C shows another implementation of a secure element 130 , in which the secure element 130 does not include a processor that is capable of bidirectional communications, but instead includes a passive device 138 .
- the passive device 138 can be an RFID sticker or suitable tag that allows for uniquely identifying a user, such that a transaction that is initiated with the passive device 138 will cause the management server 180 to perform transaction details.
- the code received from the POS terminal 150 (or the POE terminal 190 ) is transmitted from the POS terminal 150 (or the POE terminal 190 ) to the management server 190 , which then takes over the transaction.
- This passive device 138 with the identification code stored thereon, can thus be associated with a mobile communication device 110 not otherwise equipped for such communications, and the management server 190 can provide transactional information to the mobile communication device 110 using available channels on the mobile communication device (such as audio, SMS, or other known data transmission methods). While bidirectional communications do not occur with other devices, transactions are possible, because the management server 190 is involved.
- SMS Short Messaging Service
- SMS Short Message Service
- the communication system 800 includes a mobile communication device 802 that communicates with a remote server 804 (e.g., a transaction server) via SMS.
- a remote server 804 e.g., a transaction server
- the mobile communication device 802 includes a mobile application 806 that receives SMS messages from the remote server 804 and organizes the SMS messages (including linking corresponding messages into a pre-determined order) so that data can be stored and displayed to a user in an organized and easily retrievable fashion, unlike a conventional application that implements SMS as a data transmission method in which SMS messages remain in an unstructured format and are unlinked. Such an unstructured format does not allow the user to retrieve, organize, or manage the display of messages.
- the mobile application 806 can be, for example, a J2ME, BREW, Windows Mobile, or other type of application.
- the mobile application 806 is a rich client application (also commonly referred to as a fat client application or thick client application).
- a rich client application is a client application that performs the bulk of any data processing operations itself, and does not necessarily rely on a server (e.g., remote server 804 ).
- the mobile application 806 can also be a thin client application or hybrid client application.
- the mobile application 806 is the Blaze Mobile Wallet Lite application available from Mobile Candy Dish Inc. or Berkeley, Calif.
- the mobile application 806 provides banking and money management transaction services, and transmits data from the wireless communication device 802 via SMS in accordance with a connectionless protocol.
- FIG. 9 illustrates a communication system 900 in accordance with one implementation.
- the communication system 900 includes a mobile communication device 902 , a management server 904 , a user/profile database 906 , and a money management database 908 .
- the management server 904 is a Blaze server.
- the mobile communication device 902 stores a mobile application 910 that uses short message service (SMS) over a connectionless protocol to transmit data to the management server 904 . SMS permits the mobile application 910 to send messages of a fixed size, for example, up to 160 characters, to and from the wireless mobile communication device 902 .
- SMS short message service
- the management server 904 includes an SMS aggregator 912 to aggregate each message received from the wireless mobile communication device 902 and keep track of the ordering of each message, and (in one implementation) also groups each message into a corresponding group.
- the mobile application 910 also includes an SMS aggregator (not shown).
- the mobile application 910 is not browser HTTP based, and delivers banking and money management services.
- the mobile application 910 also leverages a low-end communication infrastructure (also referred to herein as a “bearer service”).
- a bearer service that is universal on all mobile devices is the Short Message Service (SMS). SMS is a means of sending short messages to and from mobile phones to the Application Service Provider (ASP) Server “Server”. It is inherently a connectionless communication protocol, i.e., send and forget. There is no acknowledgement to the Mobile Originating (MO) sender that the message sent was successfully received by the Mobile Terminating (MT) recipient. There is no concept of timeouts, message lost, message not received, etc. Leveraging SMS as a bearer service to support a ‘rich’ client application. The Client will listen to a specific incoming SMS port to be defined based on Network Operator/Carrier, Phone Vendor, etc.
- the mobile application 910 provides banking and money management service, which includes (but is not limited to):
- connection protocol properties over SMS This includes: segmenting complex command and control (C&C) messages into 1 or more SMS messages, and re-constructing one or more SMS messages into complex C&C resultset messages.
- Re-constructing the one or more messages into complex C&C resultset messages can include one or more of the following providing acknowledgement, handling out-of-sequence incoming messages, handling unexpected messages or messages considered lost (due to timeout, etc.), Managing encryption as needed, and so on.
- User uses the mobile application 910 to initiate/trigger appropriate banking service.
- a user can initiate a bill paying service through which a payee (e.g., PG&E) can be paid.
- the display of the bill pay screen can include an advertisement as shown in FIG. 10A .
- the mobile application 910 formulates appropriate banking services commands, for example:
- a Loading Station (Kiosk, etc.) can load funds by sending command to MCD's Loading Shortcode.
- post processing of these multiple messages results in the screen shown in FIG. 10B which displays the account balance and the last five transactions in a transaction history list.
- the list can be cached on the mobile communication device 902 for later use.
- the above description introduced the concept on ⁇ sequenceID> ⁇ message> ⁇ messages>.
- the sequenceID is a rotating pool per Client, issued by the Client, used as a callback mechanism, i.e., match outgoing command messages and incoming resultset messages. Since resultsets can be long and complex, the resultset is broken into pages, where each page can fit with the allowed payload size of an SMS message. Hence, “ ⁇ message> ⁇ messages>” implies “Page 1 of 5”. The Client (or mobile application) then has to wait for all ⁇ messages> to arrive before re-constructing the original resultset. Due to characteristics of SMS, the client has to handle scenarios when a message with an un-expected sequenceID arrives.
- retransmit 36:4:6 1234 which will instruct server to retransmit resultset 36, part 4 of 6.
- the pool size controls the asynchronous aspect of the application.
- the sequenceID is mapped to the command (at least until the sequenceID is re-used).
- SMS messages to and from the mobile communication device has to be acknowledged.
- a simple protocol is necessary, for example, as follows:
- a mobile communication device creates task/objects either while connected with a Server (online-mode) or when no connection is available (offline-mode).
- Tasks/objects are specific to mobile banking service and include for example: schedule (or cancel) a fund transfer transaction, schedule (or cancel) a bill pay transaction, and manage other banking transactions.
- digital artifacts coupled, tickets, etc.
- that possess a state (or status) e.g., Assigned, Saves, Redeemed, Deleted, etc.
- the user can use the mobile communication device (with the Mobile Wallet Client application) to schedules a fund transfer in offline mode.
- the Client in OFFLINE mode
- the task can have an initial state (e.g., “pending”). While the Client is enabled the Client will actively monitor network access. When the user travels into a region where network access is available, the client will identify the network and automatically re-connect to the network.
- the client will then negotiate with a server and any tasks having a “pending” state on the client are then uploaded to server (either in batch mode or one task at a time).
- the client in ONLINE mode) will refresh states of all task from the server (including the recently added tasks) to present to the user the updated status of all tasks managed by the server.
- Other services possible include, for example: request schedule (or cancellation) of Bill Pay transaction, request schedule (or cancellation) of Fund Transfer transaction, request schedule (or cancellation) of Pay Perhaps transaction, any other state-based banking transaction service.
- a user can store digital artifacts (e.g., coupons, tickets, etc.) on a mobile communication device.
- digital artifacts are objects that are consumed by a 3rdParty, e.g., a ticket can be redeemed at a theater, and a coupon can be redeemed at the Point-Of-Sale of a retail merchant.
- this is a 3-way sync: 1) mobile communication device with server, 2. mobile communication device with 3rdParty Merchant, and 3) server with 3rdParty Merchant.
- redemption of digital artifacts by a 3rdParty must be enabled in an environment with or without network access.
- a user with an electronic ticket on a mobile communication device may wish to redeem an eTicket at a theater.
- the user will still need access the eTicket on the client.
- the client In ONLINE mode, the client will cache (local store) the eTicket (and any other digital artifact.)
- the client in OFFLINE mode, the client (in OFFLINE mode) will be able to redeem the eTicket and update the state of the eTicket on the mobile communication device (e.g., change state from ‘valid’ to ‘redeemed’). This prevents the user from re-using the eTicket.
- the client will then negotiate with the server and any artifacts with a state change (e.g., ‘valid’ to ‘redeemed’, etc.) on the client are then uploaded to the server (e.g., either in batch mode or one task at a time).
- a state change e.g., ‘valid’ to ‘redeemed’, etc.
- the client in ONLINE mode will manage and refresh states of all artifacts from the server (including the recently added tasks) to present to the user.
- the server is the master repository.
- the eTicket is uploaded to the merchant (via secondary out-of-band communication link, e.g., RFID/NFC, Bluetooth, etc.). This is necessary for theater to update their inventory systems.
- the 3rdParty may liaise (via an internet connection) with the server to validate eTicket and authenticate the user.
- the point of sale terminal 150 illustrated in FIG. 5 is conventional, in that it has the capability of electronically reading information from a device equipped to transmit information in a format that it reads.
- the reader 152 within the point of sale terminal 150 can be of one or many types. If the point of sale terminal reader 152 includes the provision for NFC communications, then simply bringing the secure element 130 with the NFC transceiver will cause initiation of a transaction and the transmission of the identification code associated with the secure element 130 and thus the user.
- various software that is downloaded into the memory 126 of the radio element 120 and the secure memory 132 of the secure element 130 , along with software resident on the management server 180 , cooperate at a layer that is above the physical layer of the communications, in order for the desired transaction to occur.
- This software is implemented using based upon known knowledge of mobile communication device 110 internals and application platforms, NFC, smartcard internals and application platforms, payment protocols (e.g. PayPass), and the working/workflow associated with POS and POE terminals, and the transaction and management servers.
- the present invention provides for piggybacking a tunneling protocol on top of the payment protocol, so that the secure elements 130 can communicate with the transaction server 170 and/or the management server 180 , without modification to the POS terminal 150 or the POE terminal 190 .
- this includes software within the secure element 130 that embeds the required information in fields which will not adversely affect the performance of the POS terminal 150 and/or the POE terminal 190 , and also software in transaction server 170 that will extract the piggybacked payload, associate the payload with the management server 180 if needed, and then authenticate, authorize, and execute transfers of transaction information to the management server 180 .
- the piggybacked payload is sent, instead of to the transaction server 170 , to the management server 180 , which can then associate the transaction and notify the transaction server 170 , the POS terminal 150 and/or the POE terminal as needed.
- the management server 180 has the capability of storing codes that are from a variety of different mobile communication devices.
- codes that are associated with a smart card having an RFID can be stored, as can be codes stored from an RFID sticker, as well as codes that are associated with a smart card that communicates using a slide reader, Bluetooth, or an NFC channel, for example.
- the management server 180 can store user personal and credit and transactional information and history, including a code associated with the user, for a variety of different mobile communication devices, thereby allowing a system which can scale.
- FIGS. 6A-6D illustrate a flowchart of a transaction in accordance with one implementation, and the various steps that are included in the transaction, with reference to which of the various devices are implementing this step.
- a user first waves a mobile communication device 530 (e.g., a NFC device or device having an attached sticker) across (or near) a POS terminal 540 .
- the POS terminal 540 identifies the technology associated with the mobile communication device, a payment method, user credentials, and payment credentials. Irrespective if t mobile communication device is a NFC-Phone or includes an attached sticker, the mobile communication device sends to the POS Terminal 540 payment credentials including optional credentials (e.g., WalletID). As shown in FIG.
- a security code prompt e.g., a PIN
- PIN security code
- the POS terminal 540 can integrate via the back office to a management server 510 and trigger a PIN prompt on the mobile communication device. In such a case, the user can enter the PIN on the mobile communication device (instead of through the POS terminal 540 ).
- the POS terminal 540 hands processing to a payment broker.
- the POS terminal 540 can write digital artifacts (e.g, eReceipts, eTickets, eCoupons, etc.) to the mobile communication device.
- Non-secure data is stored in the mobile communication device.
- the POS terminal 540 sends optional digital artifacts to the management server 510 .
- the non-secure digital artifacts are downloaded and stored in the mobile communication device. Secure digital artifacts are downloaded to the mobile communication device and stored on a secure element of the mobile communication device (if possible).
- the POS terminal 540 upon successful payment processing and assuming the POS terminal 540 was capable of 2-way communication, if the POS terminal 540 determines that the mobile communication device is not an NFC Phone, the POS terminal 540 triggers the management server 510 of payment processing completion. Note, this can be time delayed due to a difference when a payment is posted and cleared.
- the management server 510 can send a notification to the mobile communication device (via SMS, etc.). Since the mobile communication device could be shutdown, the notification will wake-up the mobile application running on the mobile communication device, and initiate SYNC operations between the management server 510 and the mobile application (or client). Any pending digital artifacts (including notifications, etc.) are displayed on the mobile communication device.
- the present invention allows for various different programs to exist within the memory 126 of the radio element 120 , as well as in the secure memory 132 of the secure element 130 .
- a mobile ticket (also referred to herein as “electronic ticket” or “eTicket”) includes both a unique code that is sent to the consumer's cell phone and a database that allows for the validation of the consumer using their cell phone number and the unique code.
- the mobile ticket can be used at kiosks in addition to interfacing with a ticket agent.
- the mobile ticket may be used with or without cell phones equipped with radio technology (i.e., RFID or NFC).
- RFID or NFC radio technology
- a mobile ticket works when the user is sent a unique code (alpha-numeric, numeric, etc.) to their cell phone.
- the user is validated as a customer by their cell phone number and their code. If these match the information stored in a central database, the user is allowed admission into a venue by either manual validation by a ticket agent or automatically using RFID or NFC technology.
- an electronic ticket can be delivered to a mobile device and allow a consumer admission into a sports venue, entertainment venue (e.g. concert or movies), or other point of sale location either manually if the consumer displays the electronic ticket to an agent who may issue a paper ticket to the consumer or automatically if the consumer waves their cell phone (if equipped with a radio transmitter) over a POS device which contains a radio receiver.
- an electronic ticket (or tickets) is selected by viewing an image of the venue seating map.
- the seating map can be rendered on the mobile device. Users can zoom in/out of the seating map. As User zooms in, additional layers (details, info, etc.) is presented. For example, a user can view Venue->Quadrant->Level->Section->Row.
- the ability to zoom in/out and present additional levels of details can be processed either on the mobile device (Client) or on the Content Server, the end result is an updated image rendered on the mobile device.
- seats are color coded to represent availability and price. In this manner, seat inventory (what's available and at what price) can be illustrated graphically. Once user has navigated to lowest level, the image is granular enough to select individual seats. In one implementation, a seat selection will automatically cause a price to be calculated. Any service fee can be included in the ticket price. Once user confirms purchase, reservation request is sent to ticket inventory system. If reservation is successful, a valid electronic ticket is returned to the mobile device.
- the present invention can also be interfaced with certain known and implanted payment protocols, such as Paypass.
- payment protocols such as Paypass.
- implementation of streaming communication protocols in the full NFC case
- protocols for session setup, and configuration of communications modules and secure data areas as needed is necessary, taking into account the communication protocol used (e.g. NFC, Bluetooth, WIFI, CDMA, 3.sup.rd Generation CDMA for example) as well as file transfer protocols and facilities access protocols.
- the ability to extract transaction information from the POS terminal 150 to the secure element 130 can be provided during the course of the local interaction between the POS terminal 150 and the secure element 130 .
- PayPass within the invention will take note, and alert the application running on the radio processor 123 that a purchase or purchase attempt has occurred, as noted above in the context of the alert discussion.
- a feature is provided that permits information passed via the PayPass protocol to the POS terminal 150 (and thence to the transaction server 170 ) to be augmented with additional fields containing the elements of the tunneling protocol, for subsequent processing by the transaction server 170 , either directly, or through the management server 180 .
- the two transaction workflows that have been specifically discussed above are the credit card and ticketing workflows.
- Other transaction flows can also be implemented.
- Debit card and cash card transactions are similar to credit card transactions, with variations being implemented to account for the differences that exist in those types of transactions, which types of transactions are well understood.
- Coupons can be implemented with the invention, in much the same manner as tickets, though coupons can be transmitted without there being payment.
- Many of the transaction types noted herein will, as is apparent, require communication between the secure element 130 and the radio element 120 . As such, due to that requirement, a significant part of the preceding discussion has been directed to how to implement that communication, particularly for mobile communication devices 110 that are not manufactured to allow for such communications.
- An example of a typical transaction requiring such communication between the secure element 130 and the radio element 120 is one in which the POS terminal 150 allows for the transfer of detailed purchase information from the POS terminal 150 to the secure element 130 , as well as transactional information from the POS terminal 150 and/or the transaction server 170 to the management server 180 .
- the management server 180 can then also communicate with the radio element 120 via the radio channel. This allows for the matching and reconciliation of detailed purchase information and, if the transaction fails, failure details can be matched to the purchase information, and forwarded in real-time to the user via the radio element 120 .
- there is included the provision for different phones to communicate the results of a transaction particularly using the POS transceiver or one of the Bluetooth/Wifi transceivers.
- another mobile communication device 110 b can receive information regarding the transaction completed.
- mobile communication device 110 a purchases two tickets
- one of the tickets can be transmitted to the mobile communication device 110 b by each using a POS transceiver or one of the Bluetooth/Wifi transceivers.
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- General Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Finance (AREA)
- Computer Security & Cryptography (AREA)
- Signal Processing (AREA)
- Telephonic Communication Services (AREA)
- Telephone Function (AREA)
- Cash Registers Or Receiving Machines (AREA)
Abstract
A method for conducting a mobile financial transaction using an NFC secure element and transmitting data associated with the transaction between a wireless communication and a remote server. The method includes running a mobile application on the wireless communication device, in which the mobile application is a rich client application. The method further includes transmitting data associated with the mobile application between the wireless communication device and the remote server using short message service (SMS). The mobile application links corresponding data transmitted through the short message service (SMS) for use by the mobile application.
Description
- This application is a continuation of application Ser. No. 11/933,337 filed on Oct. 31, 2007 which is a continuation-in-part of U.S. patent application Ser. No. 11/467,441, titled “Method and Apparatus for Completing a Transaction Using a Wireless Mobile Communication Channel and Another Communication Channel,” filed Aug. 25, 2006, which claims priority to U.S. Provisional Patent Application Nos. 60/766,171 and 60/766,172, both of which were filed Dec. 31, 2005. All of the above-referenced patent applications are incorporated by reference herein in their entirety
- The present invention relates to data communications and wireless devices.
- Online transactions—e.g., for purchasing goods, receiving downloads, and so on—which involve personal computers and the Internet are well known. Further, wireless mobile communication devices, such as cell phones, blackberries or other personal digital assistants, are also being used for making transactions. For example, U.S. Patent Application No. US/2003/0172028 provides a description of a personal payment system that utilizes a wireless enabled device such as a cell phone. As described, the personal payment system interacts using a Bluetooth protocol with a terminal located nearby the wireless enabled device. In another example, U.S. Pat. No. 7,031,945 describes a system and method that provides an electronic ticket to a smart card or standard wireless device that is identified with a user's account.
- Further, wireless mobile devices that include a near field communication (NFC) device and a smart card (that uses an RFID for identification purposes) allow a person to securely make a simple transaction, such as for example, purchasing a bus ticket. In such an example, the person typically waves the wireless mobile device near a reader installed in a bus, and a price of the bus ticket is deducted from a total amount that is available and stored on the smart card of the wireless mobile device. Optionally, the amount of the bus ticket can be forwarded to a server that can identify the identification code of the particular RFID and then subsequently charge the person for the purchase of the bus ticket.
- While the references discussed above illustrate that certain transactions are possible using wireless mobile devices, one problem associated with the references are is that implementations described in the references are not useful in a wide variety of different platforms, but rather are typically tied to a specific platform. For example, NFC devices are only usable with NFC readers. Another problem is that conventional wireless mobile devices generally have a very limited ability to be used in transactions.
- In general, in one aspect, this specification describes a method and system for transmitting data between a wireless communication and a remote server. The method includes running a mobile application on the wireless communication device, in which the mobile application is a rich client application. The method further includes transmitting data associated with the mobile application between the wireless communication device and the remote server using short message service (SMS). The mobile application links corresponding data transmitted through the short message service (SMS) for use by the mobile application.
- The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features and advantages will be apparent from the description and drawings, and from the claims.
-
FIG. 1 illustrates one implementation of a block diagram of a communication system including a wireless mobile communication device. -
FIG. 2 illustrates one implementation of radio element in the wireless mobile communication device ofFIG. 1 . -
FIG. 3 illustrates one implementation of a wireless mobile communication device. -
FIGS. 4A-4C respectively illustrate an implementation of a secure element in the wireless mobile communication device ofFIG. 1 . -
FIG. 5 illustrates one implementation of a point of sale terminal. -
FIGS. 6A-6D illustrate a flowchart for conducting a transaction according to one implementation. -
FIG. 7 illustrates one implementation of a secure element that is attachable to a wireless communication device. -
FIG. 8 illustrates a communication system in accordance with one implementation. -
FIG. 9 illustrates a communication system in accordance with one implementation. -
FIGS. 10A-10B illustrate example client user interfaces that are displayable on a display of the mobile communication device ofFIG. 9 . - Like reference symbols in the various drawings indicate like elements.
- This disclosure describes a communication system and method for assisting a user to complete a transaction.
FIG. 1 illustrates one implementation of acommunication system 100. Thecommunication system 100 includes a hand-held, wirelessmobile communication device 110 that (in one implementation) includes aradio element 120 and asecure element 130. Adisplay 124 is shown associated with theradio element 120, and antennas (not labeled) are shown as associated with each of theradio element 120 and thesecure element 130. Each antenna can physically be implemented in a manner that is different from the wireless antennas shown inFIG. 1 . For example, an antenna can comprise a stripe that is passed along a reader, or comprise some suitable transmission mechanism. Althoughelements display 124 is shown as connected to theradio element 120, other configurations are possible. In particular, a combination in which a single processor is used to execute the functions that are currently performed and described herein as being provided by both theradio element 120 and thesecure element 130. Further as illustrated inFIG. 1 , both theradio element 120 and thesecure element 130 are internal to themobile communication device 110, although in other implementations thesecure element 130 can be external to themobile communication device 110, as described below. Also, various different functionalities can be included within theradio element 120 and thesecure element 130. - In one implementation, the
mobile communication device 110 has the functionality to communicate with one of many different a point of sale (POS) terminals 150-1 to 150-n—in a contactless manner using a wireless protocol. Themobile communication device 110 can also similarly communicate with one or more point of entry (POE) terminals 190-1 to 190-n. The point-of-sale terminal 150 receives one of the transaction request signals from themobile communication device 110 and transmits the one transaction request signal to a transaction server 170, typically using acommunication channel 160 such as the Internet. The transaction server 170 verifies the transaction, and forwards a transaction verification signal to the management server 180. The management server 180 identifies the user corresponding to the transaction verification signal, and provides a first transaction response signal back to themobile communication device 110 as one of the transaction signals. - In one implementation, the first transaction response signal is communicated back to the
mobile communication device 110 using a communication channel that is different from the communication channel used to initiate the transaction. In one implementation, different transaction response signals can be communicated back to themobile communication device 110 using communication channels from the management server 180 to theradio element 120 associated with thedevice 110, as well as from the management server 180 to thesecure element 130 through the POS ten iinal 150 or thePOE terminal 190. Further detailed descriptions of these implementations are discussed in greater detail below. -
FIG. 2 illustrates one implementation of theradio element 120 associated with themobile communication device 110, and illustrates theradio element 120 connected to thedisplay 124 of themobile communication device 110. In one implementation, theradio element 120 includes aradio transceiver 122 that is adapted to send outgoing voice and data signals and receive incoming voice and data signals over a radio communication channel. The radio communication channel can be a digital radio communication channel, such as CDMA or GSM. Such a radio communication channel has the capacity to communicate both voice and data messages using conventional techniques. Theradio transceiver 122 communicates with aradio processor 123, which processor has the capability to perform not only the radio communication services necessary to allow for phone and data communications, but can also execute various programs that are stored in thememory 126, which programs can receive inputs from the user via thedisplay 124 and/or akeypad 125 associated with themobile communication device 110. - In one implementation, application programs running on the
radio processor 123 are, e.g., BREW or J2MF applications and can encompass a broad array of application types. For example, current applications include games, enterprise applications, and multimedia applications. In one implementation, theradio processor 123 runs an application that provides movie and event information. Such an application can comprise ticketing applications, content, item and service purchase applications, and/or payment management applications (referred to herein also as “wallet applications”). In one implementation, theradio processor 123 also has the capability of recognizing secure communications, and transmits data which must be stored in a secure environment to thesecure element driver 128 for transmission to thesecure element 130. In one implementation, in which both theradio element 120 and thesecure element 130 are internal to themobile communication device 110, transmissions to thesecure element 130 can take place using an internal wired communication channel. In one implementation, theradio processor 123 also has the capability of receiving data from thesecure element 130, e.g., using the internal wired communication channel. In one implementation, thesecure element 130 and theradio element 120 communicate using signals described in the Java Card 2.1 Platform API Specification. - In one implementation, both the
radio element 120 and thesecure element 130 are disposed internally within a body of themobile communication device 110. For example, referring toFIG. 3 , themobile communication device 110 is shown including aslot 400, which allows for the insertion of asecure element 130 into theslot 400. In this configuration, thesecure element 130 can be purchased independently of themobile communication device 110. Thesecure element 130 can also be disposed into a slot that only provides for physical insertion and mechanical connection to the body of themobile communication device 110. In such an implementation, the secure element can include a transceiver that allows for the communication with theradio element 130 through a wireless local communication channel. Theradio element 120 also is illustrated as optionally including anothertransceiver 129, such as a Bluetooth or WIFI transceiver, which can transmit and receive signals with an external device and then communicate signals to and from theradio processor 123. This additional communication channel allows for communications between other external devices, such as an external Bluetooth enabled smartcard, and provides an additional communication channel that is useful for certain transactions, as described further herein. -
FIG. 4A illustrates one implementation of thesecure element 130 associated with themobile communication device 110. Thesecure element 130 can be a smart card. In one implementation, thesecure element 130 includes asecure processor 132, asecure memory 133, and aPOS transceiver 134 adapted to send transaction request signals and receive transaction response signals over a first communication channel. In one implementation, thesecure processor 132 communicates via thesecure element driver 128 with theradio processor 123 using signals as described in the Java Card 2.1 Platform API Specification. The transaction request signals and the transaction response signals associated with the transaction can include an identification code associated with the user, as well as information relative to the transaction, such as item, quantity, vendor, and so on. In one implementation, thePOS transceiver 134 is an NFC device, which uses an NFC modem. ThePOS transceiver 134 can also be a Bluetooth, WIFI or other transceiver. In an implementation in which the POS transceiver is an NFC modem, such an NFC modem will typically have a set of registers that can be read/written by thesecure processor 132. These registers are in turn available for reading and writing over the RFID communications channel and serve as a shared memory between thesecure processor 123 within thesecure element 130 and the RFID reader that is associated with thePOS terminal 150. This communication is specified, for example, in the ISO 14443A/B standard. The secure element can optionally include a radio/Bluetooth/WIFI transceiver 136, which can communicate with other devices, such as a transceiver associated with theradio processor 120 or for other external devices having those communication capabilities, thus allowing for more flexibility. -
FIG. 4B shows another implementation of asecure element 130, in which theradio element 120 does not communicate with thesecure element 130 through asecure element driver 128. In this case, for example, thesecure element 130 may be external to themobile communication device 110 and as such is not connected to the radio element through thesecure element driver 128. In such an implementation, however, if thetransceiver 136 as described above is included, and asimilar transceiver 129 associated with theradio element 130 as described previously with respect toFIG. 2 is included, then this communication channel can be used to wirelessly obtain direct communications between theradio element 120 and thesecure element 130. This implementation allows for certain bidirectional communications with other devices, as well as with theradio element 120, and as such more functionality and flexibility is achieved. This implementation is particularly useful since it establishes a direct local communication path with theradio element 120, since there is not communications with theradio element 120 via the path ofdriver 128. - This implementation allows for certain bidirectional communications with other devices, as well as with the
radio element 120, and as such more functionality and flexibility is achieved. This implementation is particularly useful for establishing a direct local communication path with theradio element 120, since there are no communications with theradio element 120 via the path ofdriver 128. If either of thetransceivers respective radio element 120 orsecure element 130, and there is no direct connection between theradio element 120 and thesecure element 130, then a direct communication link between theradio element 120 an thesecure element 130 will not exist. As such, while ticketing and many transactions can still exist, data from a real-time transaction performed using thesecure element 130 cannot be made directly available to the radio processor and the applications stored thereon. In such an implementation, certain redundancy checks may not occur. For example, a ticketing application can be programmed to provide an alert if a ticket receipt has not been received within a certain period of time. Such an alert would not be possible to program directly (although it could be programmed indirectly via the button panel on the phone). -
FIG. 7 illustrates one implementation of asecure element 130 that can be attached (or affixed) externally to a wireless communication device (e.g., mobile communication device 110). In one implementation, thesecure element 130 has circular shape. Thesecure element 130 can have other suitable shapes—e.g., rectangular, triangular, and so on. In one implementation, thesecure element 130 includes an embeddedsmart chip 702 that is capable of executing proximity services (e.g., services related to payments, ticketing, identification, sending coupons, etc.). In one implementation, thesmart chip 702 is capable of 2-way wireless communication (e.g., RFID, NFC, Bluetooth, etc.) with a supporting 3rdParty terminal. In one implementation, the 2-way communication is performed using a communication protocol that is different from a communication protocol through which the mobile communication device sends or receives voice and/or data signals. Multiple application protocols (NFC, MiFare, etc.) can be supported. In one implementation, thesmart chip 702 is programmable. Accordingly, different application (for payments, ticketing, identification, coupons, etc.) can be developed, downloaded to the smart chip, and commissioned. Thus in operation, in response to thesecure element 130 being placed in close proximity with a suitable terminal, the terminal will trigger (via application protocol) an appropriate application stored in the smart chip, and the smart chip will respond appropriately with the terminal. - In one implementation, the smart chip uses a low-power RF transmitter/receiver to communicate with a terminal. The low-power output of the smart chip makes it susceptible to RF interference from neighboring devices. Specifically problematic are components associated with the mobile communication device, e.g., battery, antennae (internal or external), to which the
secure element 130 is affixed. Thus, in one implementation, thesecure element 130 includes an RF shield to insulate the smart chip from external interference. In one implementation, a lining of thesecure element 130 is composed of an RF absorbent material/lining. In general, each phone has different levels of interference, and a material, size and thickness of the RF lining can determine an effectiveness of the RF shield. In one implementation, an RF shield can be placed between thesecure element 130 and themobile communication device 110. - Given the abuse a mobile communication device can take, components that are affixed externally to a mobile communication device need to be able to withstand some abuse. Thus, in one implementation, the secure element includes a
ruggedized shell 704 that encases a smart chip (with antennae). In one implementation, theshell 704 is formed from a composite plastic or polymer. The shell 70 can be hard (and substantially inflexible) or be soft (and pliable). In one implementation, theshell 704 provides a protective membrane for the smart chip which prevents damage to internal circuitry, a surface to adhere to an RF lining and/or a mobile communication device with appropriate adhesive, and a surface to print branding and advertising. Types of adhesives that can be used to affix thesecure element 130 to a mobile communication device include, for example, paper glue, super glue, polymers, and the like. In one implementation, theshell 704 has a maximum width (or diameter) of 25 mm, and has a maximum thickness (or depth) of 5 mm. -
FIG. 4C shows another implementation of asecure element 130, in which thesecure element 130 does not include a processor that is capable of bidirectional communications, but instead includes apassive device 138. Thepassive device 138 can be an RFID sticker or suitable tag that allows for uniquely identifying a user, such that a transaction that is initiated with thepassive device 138 will cause the management server 180 to perform transaction details. In this implementation, the code received from the POS terminal 150 (or the POE terminal 190) is transmitted from the POS terminal 150 (or the POE terminal 190) to themanagement server 190, which then takes over the transaction. Thispassive device 138, with the identification code stored thereon, can thus be associated with amobile communication device 110 not otherwise equipped for such communications, and themanagement server 190 can provide transactional information to themobile communication device 110 using available channels on the mobile communication device (such as audio, SMS, or other known data transmission methods). While bidirectional communications do not occur with other devices, transactions are possible, because themanagement server 190 is involved. - As discussed above SMS (Short Message Service) can be used as a data transmission method between the
management server 190 and themobile communication device 110. SMS is generally unstructured. Thus, when messages arrive in an inbox of a user inbox, the user cannot easily search, retrieve, or organize the messages. In addition, due to SMS's send-and-forget characteristics, it cannot be assumed that messages are received by the terminating point, or if received, received in a particular sequence.FIG. 8 illustrates acommunication system 800 in accordance with one implementation. Thecommunication system 800 includes a mobile communication device 802 that communicates with a remote server 804 (e.g., a transaction server) via SMS. The mobile communication device 802 includes amobile application 806 that receives SMS messages from theremote server 804 and organizes the SMS messages (including linking corresponding messages into a pre-determined order) so that data can be stored and displayed to a user in an organized and easily retrievable fashion, unlike a conventional application that implements SMS as a data transmission method in which SMS messages remain in an unstructured format and are unlinked. Such an unstructured format does not allow the user to retrieve, organize, or manage the display of messages. Themobile application 806 can be, for example, a J2ME, BREW, Windows Mobile, or other type of application. - In one implementation, the
mobile application 806 is a rich client application (also commonly referred to as a fat client application or thick client application). A rich client application is a client application that performs the bulk of any data processing operations itself, and does not necessarily rely on a server (e.g., remote server 804). Themobile application 806 can also be a thin client application or hybrid client application. In one implementation, themobile application 806 is the Blaze Mobile Wallet Lite application available from Mobile Candy Dish Inc. or Berkeley, Calif. In one implementation, themobile application 806 provides banking and money management transaction services, and transmits data from the wireless communication device 802 via SMS in accordance with a connectionless protocol. -
FIG. 9 illustrates acommunication system 900 in accordance with one implementation. Thecommunication system 900 includes a mobile communication device 902, amanagement server 904, a user/profile database 906, and amoney management database 908. In one implementation, themanagement server 904 is a Blaze server. In one implementation, the mobile communication device 902 stores amobile application 910 that uses short message service (SMS) over a connectionless protocol to transmit data to themanagement server 904. SMS permits themobile application 910 to send messages of a fixed size, for example, up to 160 characters, to and from the wireless mobile communication device 902. In one implementation, themanagement server 904 includes anSMS aggregator 912 to aggregate each message received from the wireless mobile communication device 902 and keep track of the ordering of each message, and (in one implementation) also groups each message into a corresponding group. In one implementation, themobile application 910 also includes an SMS aggregator (not shown). - Thus, in one implementation, the
mobile application 910 is not browser HTTP based, and delivers banking and money management services. Themobile application 910 also leverages a low-end communication infrastructure (also referred to herein as a “bearer service”). A bearer service that is universal on all mobile devices is the Short Message Service (SMS). SMS is a means of sending short messages to and from mobile phones to the Application Service Provider (ASP) Server “Server”. It is inherently a connectionless communication protocol, i.e., send and forget. There is no acknowledgement to the Mobile Originating (MO) sender that the message sent was successfully received by the Mobile Terminating (MT) recipient. There is no concept of timeouts, message lost, message not received, etc. Leveraging SMS as a bearer service to support a ‘rich’ client application. The Client will listen to a specific incoming SMS port to be defined based on Network Operator/Carrier, Phone Vendor, etc. - In one implementation, the
mobile application 910 provides banking and money management service, which includes (but is not limited to): -
- Registration: User creates new MW Lite account with PIN (PIN and user info can be stored in user/profile database 306)
- Security & Encryption: Sensitive information may optionally by encrypted using 3rdParty or native phone tools (Bouncy Castle, etc.). Encryption (Public/Private) keys may be managed or proxy'd by Server which may additionally be out-sourced to 3rdparty Key Management vendor.
- Install & Configuration (I&C): Refers to setting up proxies to
- payment accounts (virtual, credit, debit & banking)
- Payees (BillPay, PayAnyone, etc.) and associated rules
- Specify default payment account to debit fund transfers/unloading
- Specify default payment account to credit fund transfers/loading
- Activation of 3rdParty Services (Account Balance, Bill Pay, Fund Transfer, Funds Loading, Funds Unloading)
- It is assumed Client application is pre-installed or downloaded to mobile device.
- I&C to be performed via Kiosk, ATM, 3rdParty/Carrier Web Portal, MCD Web Portal, on mobile device, or other suitable device.
- Loading Funds
- Banking or financial data
- Account balance
- Transaction history
- Bill Pay—Biller Direct
- Fund Transfer—Intra Bank; Me-2-Me
- Fund Transfer—Inter Bank; Me-2-Me
- Fund Transfer—Inter Bank; Me-2-You (based on Bank Routing/Account#)
- Fund Transfer—Inter Bank; Me-2-You (based on WalletID)
- Fund Transfer—Inter Bank; Me-2-You (based on ACH Check). A.k.a. Bill Pay Anyone
- Load Fund
- Unload Funds (ATM Withdrawal, etc.)
- Sync: Ensures server-side objects are downloaded to client and locally cached. This includes payment accounts, payees, payment rules, server-side cached account info (account balance, Last-N transaction history), etc.
- This info will be cached on Client.
- Users can create transaction either in ONLINE or OFFLINE (no network connectivity) mode
- Initiating/Triggering Banking Services:
- Storage: Storage of Users MiWLite info, User's payment account info (credentials, account balance, history, etc.); Banking Payment History (BillPay, Fund Transfer, Fund Loads, Fund Unloads, etc.)
- 1. Overlaying connection protocol properties over SMS. This includes: segmenting complex command and control (C&C) messages into 1 or more SMS messages, and re-constructing one or more SMS messages into complex C&C resultset messages. Re-constructing the one or more messages into complex C&C resultset messages can include one or more of the following providing acknowledgement, handling out-of-sequence incoming messages, handling unexpected messages or messages considered lost (due to timeout, etc.), Managing encryption as needed, and so on.
- 2. User uses the
mobile application 910 to initiate/trigger appropriate banking service. For example, referring toFIG. 10A a user can initiate a bill paying service through which a payee (e.g., PG&E) can be paid. In one implementation, the display of the bill pay screen can include an advertisement as shown inFIG. 10A . - 3. The
mobile application 910 formulates appropriate banking services commands, for example: -
“<command> <PaymentAccount> <Payee> <$amt> <tarnsferDate> <PIN> <sequenceID> <message> <messages>” billpay MCC-2345 PG&E 110.23 20070328 1234 36 1 1 transfer bofa-1007 jdoe 25.00 20070328 1234 36 1 1#where jdoe is a walletID transfer bofa-1007 8005550001 25.00 20070328 1234 36 1 1#where 8005550001 is the phoneNumber of unloading station. fundstransfer bofa-1007 gwbush 30.00 20070328 1234 36 1 1#gwbush is a payee “<command> <PaymentAccount> <PIN> <sequenceID> <message> <messages>” Balance bofa-1007 1234 36 1 1 - 4. A Loading Station (Kiosk, etc.) can load funds by sending command to MCD's Loading Shortcode.
-
“<command> <PaymentAccount> <Payee> <$amt> <transferDate> <PIN> <sequenceID> <message> <messages>” load CorpBankPayrollAccount-2007 8005550001 4000.00 20070328 0987 43 1 1 (#Debit account CorpBankPayrollAccount-2007 by $4000 and credit account held by user with phone Number 8005550001) - 5. Receive multiple (in/out sequence, missing, lost, etc.) messages to reconstruct a complex messages.
-
<sequenceID>:<message>:<messages>; <body> “36:1:6; acct:Bofa-1007 bal:40123.32 date:20071009” “36:3:6; date:20071009 name:Merchant2 amt:123.81” “36:6:6; date:20071009 name:Merchant5 amt:423.81” “36:4:6; date:20071009 name:Merchant3 amt:223.81” “36:2:6; date:20071009 name:Merchant1 amt:23.81” “36:5:6; date:20071009 name:Merchant4 amt:323.81” - In one implementation, post processing of these multiple messages results in the screen shown in
FIG. 10B which displays the account balance and the last five transactions in a transaction history list. The list can be cached on the mobile communication device 902 for later use. - 6. Cashed data is refreshed upon user request. This in turn invokes a command similar to the following:
-
<command> <account> <PIN> <sequenceID> <message> <messages> Balance Bofa-1007 1234 37 1 1 (# Where 37 is the next <sequenceID>) - The above description introduced the concept on <sequenceID><message><messages>. The sequenceID is a rotating pool per Client, issued by the Client, used as a callback mechanism, i.e., match outgoing command messages and incoming resultset messages. Since resultsets can be long and complex, the resultset is broken into pages, where each page can fit with the allowed payload size of an SMS message. Hence, “<message><messages>” implies “Page 1 of 5”. The Client (or mobile application) then has to wait for all <messages> to arrive before re-constructing the original resultset. Due to characteristics of SMS, the client has to handle scenarios when a message with an un-expected sequenceID arrives. In addition, if a missing page within the expected sequenceID fails to arrive within a specified time interval, the client needs to request retransmission, e.g., “retransmit 36:4:6 1234” which will instruct server to retransmit resultset 36, part 4 of 6.
- The pool size (or range of valid sequenceID's) controls the asynchronous aspect of the application. The sequenceID is mapped to the command (at least until the sequenceID is re-used). Hence, the client will use the sequenceID to determine to command and associate the appropriate display style sheet to best display the resultset to the user. For example, if sequenceID=36 was issued by the command ‘balance’ which determines account balance, it makes sense to leverage the ‘Account Balance & History’ style sheet to present this information.
- SMS messages to and from the mobile communication device has to be acknowledged. A simple protocol is necessary, for example, as follows:
-
- 1. # Mobile Originated (MO) command
- <command><body><sequenceID><message><messages>
- balance Bofa-1007 1234 37 1 1
- 2. # Server, a.k.a., Mobile Terminating (MT) receives and acknowledges receipt of message ‘37 part 1 of 1.”
- ack 37 1 1
- 3. # MT responds with resultset
- 36:1:2; acct:Bofa-1007 bal:40123.32 date:20071009
- 4. # MO receives and acknowledges receipt of message ‘36 part 1 of 2.”
- ack 37 1 2
- 5. # MT responds with resultset (part 2 of 2)
- “36:2:2; date:20071009 name:Merchant1 amt:23.81”
- 6. # MO receives and acknowledges receipt of message ‘36 part 2 of 2.”
- ack 37 2 2
- 7. # MO has received all messages. Reconstruct & store message
- 8. # Next time user view account balance, display cached (local store) information:
- Bank Account Bofa-1007
- Balance: $40,123.32 as of Oct. 9, 2007
- Oct. 9, 2007 Merchant1 $23.81
- 1. # Mobile Originated (MO) command
- In one implementation, a mobile communication device creates task/objects either while connected with a Server (online-mode) or when no connection is available (offline-mode). Tasks/objects are specific to mobile banking service and include for example: schedule (or cancel) a fund transfer transaction, schedule (or cancel) a bill pay transaction, and manage other banking transactions. In addition, digital artifacts (coupons, tickets, etc.) that possess a state (or status) (e.g., Assigned, Saves, Redeemed, Deleted, etc.) can undergo changes on the mobile communication device. Given these tasks/objects associated to Banking Services and Digital Artifacts has ‘states’ that can be changed in either an online-mode or offline-mode, the Server has to be refreshed/updated either in real-time (online-mode) or in batch (offline-mode).
- For example, given a situation in which a user is travelling in a region in which the user's mobile communication device does not have network access and the user needs to transfer funds into a checking account, the user can use the mobile communication device (with the Mobile Wallet Client application) to schedules a fund transfer in offline mode. Since the mobile communication device has no network connectivity, the Client (in OFFLINE mode) creates a ‘task’ to represent the fund transfer (or any other banking service) using banking information (Banks accounts, etc.) previously cached on mobile device. The task can have an initial state (e.g., “pending”). While the Client is enabled the Client will actively monitor network access. When the user travels into a region where network access is available, the client will identify the network and automatically re-connect to the network. The client will then negotiate with a server and any tasks having a “pending” state on the client are then uploaded to server (either in batch mode or one task at a time). The client (in ONLINE mode) will refresh states of all task from the server (including the recently added tasks) to present to the user the updated status of all tasks managed by the server. Other services possible include, for example: request schedule (or cancellation) of Bill Pay transaction, request schedule (or cancellation) of Fund Transfer transaction, request schedule (or cancellation) of Pay Anyone transaction, any other state-based banking transaction service.
- Using the client (or mobile application), a user can store digital artifacts (e.g., coupons, tickets, etc.) on a mobile communication device. These digital artifacts are objects that are consumed by a 3rdParty, e.g., a ticket can be redeemed at a theater, and a coupon can be redeemed at the Point-Of-Sale of a retail merchant. Hence, this is a 3-way sync: 1) mobile communication device with server, 2. mobile communication device with 3rdParty Merchant, and 3) server with 3rdParty Merchant. For user's convenience, redemption of digital artifacts by a 3rdParty must be enabled in an environment with or without network access. For example, a user with an electronic ticket on a mobile communication device may wish to redeem an eTicket at a theater. However, if there is no network access inside the theater, the user will still need access the eTicket on the client. In ONLINE mode, the client will cache (local store) the eTicket (and any other digital artifact.) In the theater, the client (in OFFLINE mode) will be able to redeem the eTicket and update the state of the eTicket on the mobile communication device (e.g., change state from ‘valid’ to ‘redeemed’). This prevents the user from re-using the eTicket. At some point when the mobile communication device re-acquires network connectivity, the client will then negotiate with the server and any artifacts with a state change (e.g., ‘valid’ to ‘redeemed’, etc.) on the client are then uploaded to the server (e.g., either in batch mode or one task at a time).
- The client (in ONLINE mode) will manage and refresh states of all artifacts from the server (including the recently added tasks) to present to the user. In one implementation, the server is the master repository. In the process of redeeming the eTicket, the eTicket is uploaded to the merchant (via secondary out-of-band communication link, e.g., RFID/NFC, Bluetooth, etc.). This is necessary for theater to update their inventory systems. The 3rdParty may liaise (via an internet connection) with the server to validate eTicket and authenticate the user.
- The point of
sale terminal 150 illustrated inFIG. 5 is conventional, in that it has the capability of electronically reading information from a device equipped to transmit information in a format that it reads. Thus, thereader 152 within the point ofsale terminal 150 can be of one or many types. If the point ofsale terminal reader 152 includes the provision for NFC communications, then simply bringing thesecure element 130 with the NFC transceiver will cause initiation of a transaction and the transmission of the identification code associated with thesecure element 130 and thus the user. - In one implementation, various software that is downloaded into the
memory 126 of theradio element 120 and thesecure memory 132 of thesecure element 130, along with software resident on the management server 180, cooperate at a layer that is above the physical layer of the communications, in order for the desired transaction to occur. This software is implemented using based upon known knowledge ofmobile communication device 110 internals and application platforms, NFC, smartcard internals and application platforms, payment protocols (e.g. PayPass), and the working/workflow associated with POS and POE terminals, and the transaction and management servers. In addition, the present invention provides for piggybacking a tunneling protocol on top of the payment protocol, so that thesecure elements 130 can communicate with the transaction server 170 and/or the management server 180, without modification to thePOS terminal 150 or thePOE terminal 190. As such, this includes software within thesecure element 130 that embeds the required information in fields which will not adversely affect the performance of thePOS terminal 150 and/or thePOE terminal 190, and also software in transaction server 170 that will extract the piggybacked payload, associate the payload with the management server 180 if needed, and then authenticate, authorize, and execute transfers of transaction information to the management server 180. In one implementation, the piggybacked payload is sent, instead of to the transaction server 170, to the management server 180, which can then associate the transaction and notify the transaction server 170, thePOS terminal 150 and/or the POE terminal as needed. - In one implementation, the management server 180 has the capability of storing codes that are from a variety of different mobile communication devices. Thus, codes that are associated with a smart card having an RFID can be stored, as can be codes stored from an RFID sticker, as well as codes that are associated with a smart card that communicates using a slide reader, Bluetooth, or an NFC channel, for example. As such, the management server 180 can store user personal and credit and transactional information and history, including a code associated with the user, for a variety of different mobile communication devices, thereby allowing a system which can scale.
-
FIGS. 6A-6D illustrate a flowchart of a transaction in accordance with one implementation, and the various steps that are included in the transaction, with reference to which of the various devices are implementing this step. Referring toFIG. 6A , a user first waves a mobile communication device 530 (e.g., a NFC device or device having an attached sticker) across (or near) aPOS terminal 540. ThePOS terminal 540 identifies the technology associated with the mobile communication device, a payment method, user credentials, and payment credentials. Irrespective if t mobile communication device is a NFC-Phone or includes an attached sticker, the mobile communication device sends to thePOS Terminal 540 payment credentials including optional credentials (e.g., WalletID). As shown inFIG. 6B , using optional credentials (e.g., WalletID), contact is made with atransaction server 510 to request payment credentials. ThePOS terminal 540 determines if a security code prompt (e.g., a PIN) is needed? If yes, a prompt is made for the security code (PIN) on thePOS terminal 540 and the process continues with processing of the payment. Otherwise, thePOS terminal 540 simply proceeds with processing of the payment. As an alternative, thePOS terminal 540 can integrate via the back office to amanagement server 510 and trigger a PIN prompt on the mobile communication device. In such a case, the user can enter the PIN on the mobile communication device (instead of through the POS terminal 540). ThePOS terminal 540 hands processing to a payment broker. - Referring to
FIG. 6C , assuming thePOS terminal 540 was capable of 2-way communication, if thePOS terminal 540 determines that the mobile communication device is a NFC Phone, thePOS terminal 540 can write digital artifacts (e.g, eReceipts, eTickets, eCoupons, etc.) to the mobile communication device. Non-secure data is stored in the mobile communication device. Otherwise, thePOS terminal 540 sends optional digital artifacts to themanagement server 510. As part of an out-of-band sync between themanagement server 510 and the mobile communication device, the non-secure digital artifacts are downloaded and stored in the mobile communication device. Secure digital artifacts are downloaded to the mobile communication device and stored on a secure element of the mobile communication device (if possible). - In
FIG. 6D , upon successful payment processing and assuming thePOS terminal 540 was capable of 2-way communication, if thePOS terminal 540 determines that the mobile communication device is not an NFC Phone, thePOS terminal 540 triggers themanagement server 510 of payment processing completion. Note, this can be time delayed due to a difference when a payment is posted and cleared. Themanagement server 510 can send a notification to the mobile communication device (via SMS, etc.). Since the mobile communication device could be shutdown, the notification will wake-up the mobile application running on the mobile communication device, and initiate SYNC operations between themanagement server 510 and the mobile application (or client). Any pending digital artifacts (including notifications, etc.) are displayed on the mobile communication device. - The present invention, as described previously, allows for various different programs to exist within the
memory 126 of theradio element 120, as well as in thesecure memory 132 of thesecure element 130. - Mobile Tickets (eTickets)
- In one implementation, a mobile ticket (also referred to herein as “electronic ticket” or “eTicket”) includes both a unique code that is sent to the consumer's cell phone and a database that allows for the validation of the consumer using their cell phone number and the unique code. The mobile ticket can be used at kiosks in addition to interfacing with a ticket agent. The mobile ticket may be used with or without cell phones equipped with radio technology (i.e., RFID or NFC). In operation, a mobile ticket works when the user is sent a unique code (alpha-numeric, numeric, etc.) to their cell phone. The user is validated as a customer by their cell phone number and their code. If these match the information stored in a central database, the user is allowed admission into a venue by either manual validation by a ticket agent or automatically using RFID or NFC technology.
- In general, an electronic ticket can be delivered to a mobile device and allow a consumer admission into a sports venue, entertainment venue (e.g. concert or movies), or other point of sale location either manually if the consumer displays the electronic ticket to an agent who may issue a paper ticket to the consumer or automatically if the consumer waves their cell phone (if equipped with a radio transmitter) over a POS device which contains a radio receiver. In one implementation, an electronic ticket (or tickets) is selected by viewing an image of the venue seating map. The seating map can be rendered on the mobile device. Users can zoom in/out of the seating map. As User zooms in, additional layers (details, info, etc.) is presented. For example, a user can view Venue->Quadrant->Level->Section->Row. The ability to zoom in/out and present additional levels of details can be processed either on the mobile device (Client) or on the Content Server, the end result is an updated image rendered on the mobile device. In one implementation, seats are color coded to represent availability and price. In this manner, seat inventory (what's available and at what price) can be illustrated graphically. Once user has navigated to lowest level, the image is granular enough to select individual seats. In one implementation, a seat selection will automatically cause a price to be calculated. Any service fee can be included in the ticket price. Once user confirms purchase, reservation request is sent to ticket inventory system. If reservation is successful, a valid electronic ticket is returned to the mobile device.
- The present invention can also be interfaced with certain known and implanted payment protocols, such as Paypass. For implementing these additional payment protocols, implementation of streaming communication protocols (in the full NFC case), protocols for session setup, and configuration of communications modules and secure data areas as needed is necessary, taking into account the communication protocol used (e.g. NFC, Bluetooth, WIFI, CDMA, 3.sup.rd Generation CDMA for example) as well as file transfer protocols and facilities access protocols. In particular, in implementing such protocols, the ability to extract transaction information from the
POS terminal 150 to thesecure element 130 can be provided during the course of the local interaction between thePOS terminal 150 and thesecure element 130. For instance, the implementation of PayPass within the invention will take note, and alert the application running on theradio processor 123 that a purchase or purchase attempt has occurred, as noted above in the context of the alert discussion. In one implementation, a feature is provided that permits information passed via the PayPass protocol to the POS terminal 150 (and thence to the transaction server 170) to be augmented with additional fields containing the elements of the tunneling protocol, for subsequent processing by the transaction server 170, either directly, or through the management server 180. - The two transaction workflows that have been specifically discussed above are the credit card and ticketing workflows. Other transaction flows can also be implemented. Debit card and cash card transactions are similar to credit card transactions, with variations being implemented to account for the differences that exist in those types of transactions, which types of transactions are well understood. Coupons can be implemented with the invention, in much the same manner as tickets, though coupons can be transmitted without there being payment. Many of the transaction types noted herein will, as is apparent, require communication between the
secure element 130 and theradio element 120. As such, due to that requirement, a significant part of the preceding discussion has been directed to how to implement that communication, particularly formobile communication devices 110 that are not manufactured to allow for such communications. - An example of a typical transaction requiring such communication between the
secure element 130 and theradio element 120 is one in which thePOS terminal 150 allows for the transfer of detailed purchase information from thePOS terminal 150 to thesecure element 130, as well as transactional information from thePOS terminal 150 and/or the transaction server 170 to the management server 180. The management server 180 can then also communicate with theradio element 120 via the radio channel. This allows for the matching and reconciliation of detailed purchase information and, if the transaction fails, failure details can be matched to the purchase information, and forwarded in real-time to the user via theradio element 120. In one implementation, there is included the provision for different phones to communicate the results of a transaction, particularly using the POS transceiver or one of the Bluetooth/Wifi transceivers. In this implementation, after a transaction has been completed with one of the mobile communication devices 110 a, another mobile communication device 110 b can receive information regarding the transaction completed. Thus, for instance, if mobile communication device 110 a purchases two tickets, one of the tickets can be transmitted to the mobile communication device 110 b by each using a POS transceiver or one of the Bluetooth/Wifi transceivers. - Although the present invention has been particularly described with reference to implementations discussed above, various changes, modifications and substitutes are can be made. Accordingly, it will be appreciated that in numerous instances some features of the invention can be employed without a corresponding use of other features. Further, variations can be made in the number and arrangement of components illustrated in the figures discussed above.
Claims (32)
1-4. (canceled)
5. A method for conducting a transaction between a mobile communication device and a remote Point-Of-Sale terminal, the method comprising:
executing a payment application on a processor of a secure element that is coupled to a mobile communication device, the secure element including:
a memory storing the payment application and payment credentials, the execution of the payment application facilitating the transfer of the payment credentials with the remote Point-Of-Sale terminal,
a processor that executes the payment application stored in the memory,
a wireless transceiver that sends transaction data including the payment credentials associated with the executed payment application through a second communication channel to the remote Point-Of-Sale terminal, the second communication channel being different from a first communication channel through which the mobile communication device communicates voice data, the payment application executed in response to a near field communication induction-based trigger from the remote Point-Of-Sale terminal; and
wirelessly transmitting transaction data associated with the executed payment application through the second communication channel to the remote Point-Of-Sale terminal using the wireless transceiver.
receiving manual user authentication at the remote Point-Of-Sale terminal entered by the user if the remote Point-Of-Sale terminal determines authentication is required and prompts the user for authentication wherein authentication is performed by a remote server after the payment application has been triggered by the remote terminal and after payment credentials have been transferred to remote terminal, but prior to the payment being processed
receiving a short message service (SMS) response from the remote server associated with the transaction at a pre-defined port of the mobile communication device, wherein the Point-Of-Sale terminal sends a notification associated with the transaction to the remote server;
storing the SMS response in the memory of the mobile communication device and
assembling the series of SMS messages identified at the pre-defined port into a predetermined order based on the number embedded in the header and as specified by the remote server;
formatting the assembled SMS messages in accordance with a selected style sheet associated with the transaction, wherein the style sheet is selected based on the identifier embedded in the header, formatting of the messages occurring in response to execution of the client application at the mobile communication device; and
displaying the formatted SMS messages on a display of the mobile communication device for the transaction, the display of the formatted SMS messages resulting from the selected style sheet executed by the client application.
6. The method of claim 1, wherein the secure element is affixed externally to the mobile communication device and is not electrically connected to the interior components in the mobile communication device, wherein the secure element includes a lining composed of RF absorbent material to shield the secure element from interference generated by the interior components of the mobile communication device and has sufficient size and thickness to shield the secure element from different levels of interference generated by different mobile communication devices.
7. The method of claim 1, wherein the secure element is permanently integrated within the body of the mobile communication device and is electrically connected to the interior components of the mobile communication device that utilize the NFC channel, and the secure element does not support CDMA or GSM communication.
8. The method of claim 1, wherein the secure element is removable and integrated into a slot within the mobile communication device which is electrically connected to the interior components of the mobile communication device that utilize the NFC channel and the secure element does not support CDMA or GSM communication.
9. The method of claim 1, wherein the number includes an indicator of a total number of messages in a series of SMS messages related to the mobile financial transaction
10. The method of claim 1, further comprising transmitting an acknowledgement of an SMS message from a series of SMS messages to the remote server.
11. The method of claim 1 wherein the number embedded in the header and as specified by the remote server is different from an order of the series of SMS messages as determined by a network operator, and wherein the remote server order overrides that of the network operator.
12. The method of claim 1 wherein one or more of the series of SMS messages are encrypted by the client application for storage at the mobile communication device.
13. The method of claim 1 wherein the client application executing at the mobile communication device is a thin client application.
14. The method of claim 1, wherein the client application executing at the mobile communication device is a rich client application.
15. The method of claim 1 further comprising:
determining that a respective SMS message of the series of SMS messages related to the mobile financial transaction has not arrived at the wireless communication device within a specified time interval; and
transmitting a request to the remote server to retransmit the respective SMS message
16. The method of claim 1, further comprising generating a command for a particular mobile financial transaction function at the client application on the mobile communication device which is transmitted to the remote server
17. The method of claim 12 , wherein command is converted to an SMS message format.
18. The method of claim 13 , wherein the command involves a plurality of SMS messages transmitted to the remote server through a predefined logical port at the mobile communication device.
19. The method of claim 12 , wherein the command is a request for an account balance.
20. The method of claim 12 , wherein the command is a request for transaction history.
21. The method of claim 12 , wherein the command is to add payment accounts.
22. The method of claim 12 , wherein the command is to specific a default payment account.
23. The method of claim 12 , wherein the command is a request for a bill payment transaction.
24. The method of claim 12 , wherein the command is to establish bill payees
25. The method of claim 12 wherein the command is for a transfer of funds.
26. The method of claim 16 , wherein the transfer of funds is based on an account number.
27. The method of claim 16 , wherein the transfer of funds is based on a mobile wallet identification number associated with a user of the mobile communication device.
28. The method of claim 16 , wherein the transfer of funds is based on an ACH transaction code.
29. The method of claim 12 , wherein the command is to load funds into a mobile payment account.
30. The method of claim 12 , wherein the command is to unload funds from a mobile payment account.
31. The method of claim 12 , wherein the command is to synchronized financial data between the remote server and the mobile communication device.
32. The method of claim 12 , wherein the command is to create a later executed financial transaction in an online or an offline mode.
33. The method of claim 12 , wherein the command is to store transaction data.
34. The method of claim 12 , further comprising receiving an acknowledgment of the command from the remote server.
35. The method of claim 12 , wherein the series of SMS messages received at the mobile communication device are in response to one or more commands generated by the client application at the mobile communication device, wherein each different type of mobile financial transaction function is displayed on the client application using a style sheet that is associated with each different identifier
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/167,829 US20110250866A1 (en) | 2005-12-31 | 2011-06-24 | Conducting a mobile financial transcation using a secure element and sms |
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US76617105P | 2005-12-31 | 2005-12-31 | |
US76617205P | 2005-12-31 | 2005-12-31 | |
US11/467,441 US20070156436A1 (en) | 2005-12-31 | 2006-08-25 | Method And Apparatus For Completing A Transaction Using A Wireless Mobile Communication Channel And Another Communication Channel |
US11/933,337 US8019365B2 (en) | 2005-12-31 | 2007-10-31 | Conducting a payment using a secure element and SMS |
US13/167,829 US20110250866A1 (en) | 2005-12-31 | 2011-06-24 | Conducting a mobile financial transcation using a secure element and sms |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/933,337 Continuation US8019365B2 (en) | 2005-12-31 | 2007-10-31 | Conducting a payment using a secure element and SMS |
Publications (1)
Publication Number | Publication Date |
---|---|
US20110250866A1 true US20110250866A1 (en) | 2011-10-13 |
Family
ID=46329684
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/933,337 Expired - Fee Related US8019365B2 (en) | 2005-12-31 | 2007-10-31 | Conducting a payment using a secure element and SMS |
US13/167,829 Abandoned US20110250866A1 (en) | 2005-12-31 | 2011-06-24 | Conducting a mobile financial transcation using a secure element and sms |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/933,337 Expired - Fee Related US8019365B2 (en) | 2005-12-31 | 2007-10-31 | Conducting a payment using a secure element and SMS |
Country Status (1)
Country | Link |
---|---|
US (2) | US8019365B2 (en) |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080183565A1 (en) * | 2007-01-30 | 2008-07-31 | Phil Dixon | Delayed transit fare assessment |
US20100320266A1 (en) * | 2009-06-23 | 2010-12-23 | At&T Mobility Ii Llc | Devices, Systems and Methods for Wireless Point-of-Sale |
US20100325269A1 (en) * | 2008-07-10 | 2010-12-23 | Sk Telecom. Co., Ltd | Personalized service system based on smart card and method thereof, and smart card applied to the same |
US20120047237A1 (en) * | 2009-04-16 | 2012-02-23 | Petter Arvidsson | Method, Server, Computer Program and Computer Program Product for Communicating with Secure Element |
US8538845B2 (en) | 2011-06-03 | 2013-09-17 | Mozido, Llc | Monetary transaction system |
US8783438B2 (en) | 2012-11-30 | 2014-07-22 | Heb Grocery Company, L.P. | Diverter arm for retail checkstand and retail checkstands and methods incorporating same |
US20140274014A1 (en) * | 2013-03-14 | 2014-09-18 | T-Mobile Usa, Inc. | Enhanced device configuration |
US9208488B2 (en) | 2011-11-21 | 2015-12-08 | Mozido, Inc. | Using a mobile wallet infrastructure to support multiple mobile wallet providers |
US10387846B2 (en) | 2015-07-10 | 2019-08-20 | Bank Of America Corporation | System for affecting appointment calendaring on a mobile device based on dependencies |
US10387845B2 (en) | 2015-07-10 | 2019-08-20 | Bank Of America Corporation | System for facilitating appointment calendaring based on perceived customer requirements |
US10438196B2 (en) | 2011-11-21 | 2019-10-08 | Mozido, Inc. | Using a mobile wallet infrastructure to support multiple mobile wallet providers |
US20200059831A1 (en) * | 2008-07-14 | 2020-02-20 | Sony Corporation | Communication apparatus, communication system, notification method, and program product |
Families Citing this family (134)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8571975B1 (en) | 1999-11-24 | 2013-10-29 | Jpmorgan Chase Bank, N.A. | System and method for sending money via E-mail over the internet |
US7509117B2 (en) * | 2002-05-31 | 2009-03-24 | Nokia Corporation | Apparatus, and associated method, for notifying a user in a radio communication system of a commercially-related transaction |
US8846141B1 (en) | 2004-02-19 | 2014-09-30 | Aeris Capital Sustainable Ip Ltd. | High-throughput printing of semiconductor precursor layer from microflake particles |
US7663057B2 (en) * | 2004-02-19 | 2010-02-16 | Nanosolar, Inc. | Solution-based fabrication of photovoltaic cell |
US8559987B1 (en) * | 2005-12-31 | 2013-10-15 | Blaze Mobile, Inc. | Wireless bidirectional communications between a mobile device and associated secure element |
US8275312B2 (en) * | 2005-12-31 | 2012-09-25 | Blaze Mobile, Inc. | Induction triggered transactions using an external NFC device |
US8738517B2 (en) * | 2006-12-29 | 2014-05-27 | Ebay, Inc. | Authentication data-enabled transfers |
US8768778B2 (en) * | 2007-06-29 | 2014-07-01 | Boku, Inc. | Effecting an electronic payment |
US8915447B2 (en) * | 2007-09-12 | 2014-12-23 | Devicefidelity, Inc. | Amplifying radio frequency signals |
US9311766B2 (en) | 2007-09-12 | 2016-04-12 | Devicefidelity, Inc. | Wireless communicating radio frequency signals |
US8070057B2 (en) | 2007-09-12 | 2011-12-06 | Devicefidelity, Inc. | Switching between internal and external antennas |
US9304555B2 (en) * | 2007-09-12 | 2016-04-05 | Devicefidelity, Inc. | Magnetically coupling radio frequency antennas |
US8109444B2 (en) * | 2007-09-12 | 2012-02-07 | Devicefidelity, Inc. | Selectively switching antennas of transaction cards |
TWI398155B (en) * | 2007-12-18 | 2013-06-01 | Inventec Appliances Corp | Portable communication device having matching function and portable communication system and communication method therefor |
SK288721B6 (en) * | 2008-03-25 | 2020-01-07 | Smk Kk | Method, circuit and carrier for perform multiple operations on the keypad of mobile communication equipment |
GB0809383D0 (en) | 2008-05-23 | 2008-07-02 | Vidicom Ltd | Customer to supplier funds transfer |
CN102132457B (en) * | 2008-08-29 | 2016-01-20 | Smk公司 | For the removable card of contactless communication, its purposes and manufacture method |
SK288757B6 (en) * | 2008-09-19 | 2020-05-04 | Smk Kk | System and method for contactless payment authorization |
WO2010128442A2 (en) | 2009-05-03 | 2010-11-11 | Logomotion, S.R.O. | A payment terminal using a mobile communication device, such as a mobile phone; a method of direct debit payment transaction |
SK50862008A3 (en) * | 2008-09-19 | 2010-06-07 | Logomotion, S. R. O. | System for electronic payment applications and method for payment authorization |
US8977567B2 (en) | 2008-09-22 | 2015-03-10 | Visa International Service Association | Recordation of electronic payment transaction information |
US10706402B2 (en) | 2008-09-22 | 2020-07-07 | Visa International Service Association | Over the air update of payment transaction data stored in secure memory |
US9824355B2 (en) | 2008-09-22 | 2017-11-21 | Visa International Service Association | Method of performing transactions with contactless payment devices using pre-tap and two-tap operations |
US20100217709A1 (en) * | 2008-09-22 | 2010-08-26 | Christian Aabye | Apparatus and method for preventing unauthorized access to payment application installed in contactless payment device |
SK288641B6 (en) * | 2008-10-15 | 2019-02-04 | Smk Corporation | Communication method with POS terminal and frequency convertor for POS terminal |
US8689012B1 (en) * | 2008-10-17 | 2014-04-01 | Sprint Communications Company L.P. | Diagnostics for secure elements in a mobile device |
US20100102123A1 (en) * | 2008-10-28 | 2010-04-29 | First Data Corporation | Systems, Methods, and Apparatus for Facilitating Access to Medical Information |
US8550361B2 (en) * | 2008-10-28 | 2013-10-08 | First Data Corporation | Systems, methods, and apparatus to facilitate locating a user of a transaction device |
US20100102131A1 (en) * | 2008-10-28 | 2010-04-29 | First Data Corporation | Systems and Methods for Disabling a Contactless Transaction Device |
US10803515B2 (en) * | 2008-10-31 | 2020-10-13 | First Data Corporation | Systems, methods, and apparatus for using a contactless transaction device reader with a computing system |
US9652761B2 (en) * | 2009-01-23 | 2017-05-16 | Boku, Inc. | Systems and methods to facilitate electronic payments |
EP2211480B1 (en) * | 2009-01-26 | 2013-10-23 | Motorola Mobility LLC | Wireless communication device for providing at least one near field communication service |
US9092772B2 (en) * | 2009-02-16 | 2015-07-28 | Xius Corp. | Integrated system and method for enabling mobile commerce transactions using “contactless identity modules in mobile handsets” |
US8548426B2 (en) * | 2009-02-20 | 2013-10-01 | Boku, Inc. | Systems and methods to approve electronic payments |
SK500092009A3 (en) * | 2009-02-27 | 2010-09-07 | Logomotion, S. R. O. | Computer mouse for data transmission, preferably at electronic payment, method for data transmission |
US9990623B2 (en) * | 2009-03-02 | 2018-06-05 | Boku, Inc. | Systems and methods to provide information |
US20100227605A1 (en) * | 2009-03-09 | 2010-09-09 | Aymon Patrick Fournier | Control Of A Remote Mobile Device |
US8700530B2 (en) * | 2009-03-10 | 2014-04-15 | Boku, Inc. | Systems and methods to process user initiated transactions |
US9230259B1 (en) | 2009-03-20 | 2016-01-05 | Jpmorgan Chase Bank, N.A. | Systems and methods for mobile ordering and payment |
US8224727B2 (en) | 2009-05-27 | 2012-07-17 | Boku, Inc. | Systems and methods to process transactions based on social networking |
US20100280955A1 (en) * | 2009-04-30 | 2010-11-04 | General Electric Company | Systems and methods for verifying identity |
US20100299220A1 (en) * | 2009-05-19 | 2010-11-25 | Boku, Inc. | Systems and Methods to Confirm Transactions via Mobile Devices |
US20100306015A1 (en) * | 2009-05-29 | 2010-12-02 | Boku, Inc. | Systems and Methods to Schedule Transactions |
US9595028B2 (en) * | 2009-06-08 | 2017-03-14 | Boku, Inc. | Systems and methods to add funds to an account via a mobile communication device |
US20100312645A1 (en) * | 2009-06-09 | 2010-12-09 | Boku, Inc. | Systems and Methods to Facilitate Purchases on Mobile Devices |
US8306512B2 (en) * | 2009-07-09 | 2012-11-06 | Cubic Corporation | Transit account management with text messaging |
AU2010271243A1 (en) * | 2009-07-09 | 2012-03-01 | Cubic Corporation | Proxy-based payment system |
AU2010271246A1 (en) * | 2009-07-09 | 2012-03-01 | Cubic Corporation | ID application for NFC-enabled mobile device |
AU2010271244B2 (en) * | 2009-07-09 | 2014-12-11 | Cubic Corporation | Predictive techniques in transit alerting |
CA2768671A1 (en) * | 2009-07-21 | 2011-01-27 | Fair Ticket Solutions Inc. | Systems and methods for reducing the unauthorized resale of event tickets |
US9697510B2 (en) | 2009-07-23 | 2017-07-04 | Boku, Inc. | Systems and methods to facilitate retail transactions |
US9519892B2 (en) * | 2009-08-04 | 2016-12-13 | Boku, Inc. | Systems and methods to accelerate transactions |
US8991699B2 (en) | 2009-09-08 | 2015-03-31 | Cubic Corporation | Association of contactless payment card primary account number |
US8660911B2 (en) | 2009-09-23 | 2014-02-25 | Boku, Inc. | Systems and methods to facilitate online transactions |
US20110078077A1 (en) * | 2009-09-29 | 2011-03-31 | Boku, Inc. | Systems and Methods to Facilitate Online Transactions |
US8224709B2 (en) | 2009-10-01 | 2012-07-17 | Boku, Inc. | Systems and methods for pre-defined purchases on a mobile communication device |
US10074238B2 (en) * | 2009-11-18 | 2018-09-11 | Ncr Corporation | Ticketless system and method of managing casino patron money balances |
US8412626B2 (en) | 2009-12-10 | 2013-04-02 | Boku, Inc. | Systems and methods to secure transactions via mobile devices |
US20110143710A1 (en) * | 2009-12-16 | 2011-06-16 | Boku, Inc. | Systems and methods to facilitate electronic payments |
US8566188B2 (en) * | 2010-01-13 | 2013-10-22 | Boku, Inc. | Systems and methods to route messages to facilitate online transactions |
US10255601B2 (en) * | 2010-02-25 | 2019-04-09 | Visa International Service Association | Multifactor authentication using a directory server |
US20110213671A1 (en) * | 2010-02-26 | 2011-09-01 | Boku, Inc. | Systems and Methods to Process Payments |
US8219542B2 (en) | 2010-03-25 | 2012-07-10 | Boku, Inc. | Systems and methods to provide access control via mobile phones |
US8583504B2 (en) * | 2010-03-29 | 2013-11-12 | Boku, Inc. | Systems and methods to provide offers on mobile devices |
US20110238483A1 (en) * | 2010-03-29 | 2011-09-29 | Boku, Inc. | Systems and Methods to Distribute and Redeem Offers |
US8244609B2 (en) * | 2010-04-02 | 2012-08-14 | Intel Corporation | Payment management on mobile devices |
US8781963B1 (en) | 2010-04-16 | 2014-07-15 | Jpmorgan Chase Bank, N.A. | Systems and methods for providing a mobile financial platform |
CA2808093A1 (en) | 2010-08-11 | 2012-02-16 | Boku, Inc. | Systems and methods to identify carrier information for transmission of premium messages |
US8768252B2 (en) * | 2010-09-02 | 2014-07-01 | Apple Inc. | Un-tethered wireless audio system |
US8856024B2 (en) | 2010-10-26 | 2014-10-07 | Cubic Corporation | Determining companion and joint cards in transit |
RU2571733C2 (en) * | 2010-11-10 | 2015-12-20 | Эйнновейшнз Холдингз Пте. Лтд. | Method of executing financial transaction through insecure public communication infrastructure and device therefor |
US8699994B2 (en) | 2010-12-16 | 2014-04-15 | Boku, Inc. | Systems and methods to selectively authenticate via mobile communications |
US8412155B2 (en) | 2010-12-20 | 2013-04-02 | Boku, Inc. | Systems and methods to accelerate transactions based on predictions |
US8583496B2 (en) | 2010-12-29 | 2013-11-12 | Boku, Inc. | Systems and methods to process payments via account identifiers and phone numbers |
US8700524B2 (en) | 2011-01-04 | 2014-04-15 | Boku, Inc. | Systems and methods to restrict payment transactions |
US10089606B2 (en) | 2011-02-11 | 2018-10-02 | Bytemark, Inc. | System and method for trusted mobile device payment |
US20120296826A1 (en) | 2011-05-18 | 2012-11-22 | Bytemark, Inc. | Method and system for distributing electronic tickets with visual display |
US8494967B2 (en) | 2011-03-11 | 2013-07-23 | Bytemark, Inc. | Method and system for distributing electronic tickets with visual display |
US10360567B2 (en) | 2011-03-11 | 2019-07-23 | Bytemark, Inc. | Method and system for distributing electronic tickets with data integrity checking |
US10375573B2 (en) | 2015-08-17 | 2019-08-06 | Bytemark, Inc. | Short range wireless translation methods and systems for hands-free fare validation |
US10453067B2 (en) | 2011-03-11 | 2019-10-22 | Bytemark, Inc. | Short range wireless translation methods and systems for hands-free fare validation |
US10762733B2 (en) | 2013-09-26 | 2020-09-01 | Bytemark, Inc. | Method and system for electronic ticket validation using proximity detection |
US10769624B1 (en) | 2011-04-15 | 2020-09-08 | United Services Automobile Association (Usaa) | Methods and systems for re-provisioning a mobile wallet |
US8543087B2 (en) | 2011-04-26 | 2013-09-24 | Boku, Inc. | Systems and methods to facilitate repeated purchases |
US9830622B1 (en) | 2011-04-28 | 2017-11-28 | Boku, Inc. | Systems and methods to process donations |
US9191217B2 (en) | 2011-04-28 | 2015-11-17 | Boku, Inc. | Systems and methods to process donations |
US20140067570A1 (en) * | 2011-10-01 | 2014-03-06 | Uttam Sengupta | System and method for mobile point of sale |
US20130166399A1 (en) * | 2011-12-22 | 2013-06-27 | Broadcom Corporation | Method for transferring rich couponing and advertising content at the point of sale initiated by a single nfc tap |
US8800004B2 (en) | 2012-03-21 | 2014-08-05 | Gary Martin SHANNON | Computerized authorization system and method |
US10079435B1 (en) * | 2012-03-27 | 2018-09-18 | The United States Of America, As Represented By The Secretary Of The Army | Reflector |
US10515359B2 (en) | 2012-04-02 | 2019-12-24 | Mastercard International Incorporated | Systems and methods for processing mobile payments by provisioning credentials to mobile devices without secure elements |
WO2014000257A1 (en) * | 2012-06-29 | 2014-01-03 | France Telecom | Mobile payment method and system for scheduled payments |
EP2891120B1 (en) * | 2012-08-30 | 2017-05-17 | Nokia Technologies OY | Method and apparatus for expanding field of near field communication |
US20140108247A1 (en) | 2012-10-17 | 2014-04-17 | Groupon, Inc. | Peer-To-Peer Payment Processing |
US10235692B2 (en) | 2012-10-17 | 2019-03-19 | Groupon, Inc. | Consumer presence based deal offers |
FR2998747B1 (en) * | 2012-11-27 | 2015-01-23 | Oberthur Technologies | METHOD FOR CALLING A MESSAGE |
FR2998694B1 (en) | 2012-11-27 | 2016-01-01 | Oberthur Technologies | ELECTRONIC MODULE FOR MAKING A MESSAGE ACCESSIBLE BY AN OPERATING SYSTEM |
US20140229375A1 (en) | 2013-02-11 | 2014-08-14 | Groupon, Inc. | Consumer device payment token management |
US20140229378A1 (en) * | 2013-02-14 | 2014-08-14 | Desire2Learn Incorporated | Systems and methods for authentication notification |
US9852409B2 (en) | 2013-03-11 | 2017-12-26 | Groupon, Inc. | Consumer device based point-of-sale |
US9576286B1 (en) * | 2013-03-11 | 2017-02-21 | Groupon, Inc. | Consumer device based point-of-sale |
US10192214B2 (en) * | 2013-03-11 | 2019-01-29 | Google Llc | Pending deposit for payment processing system |
US10482511B1 (en) | 2013-03-12 | 2019-11-19 | Groupon, Inc. | Employee profile for customer assignment, analytics and payments |
US20140279107A1 (en) * | 2013-03-14 | 2014-09-18 | William P. Vasquez | Systems and methods for integrated, secure point-of-sale transactions |
AP2015008832A0 (en) | 2013-05-15 | 2015-10-31 | Visa Int Service Ass | Methods and systems for provisioning payment credentials |
US20140379577A1 (en) * | 2013-06-24 | 2014-12-25 | Infosys Limited | Methods, systems, and computer-readable media for providing financial transactions |
US9384478B2 (en) | 2013-07-19 | 2016-07-05 | Bank Of America Corporation | Offline mobile banking system |
US9928493B2 (en) | 2013-09-27 | 2018-03-27 | Groupon, Inc. | Systems and methods for providing consumer facing point-of-sale interfaces |
US11288660B1 (en) | 2014-04-30 | 2022-03-29 | Wells Fargo Bank, N.A. | Mobile wallet account balance systems and methods |
US11461766B1 (en) | 2014-04-30 | 2022-10-04 | Wells Fargo Bank, N.A. | Mobile wallet using tokenized card systems and methods |
US10997592B1 (en) | 2014-04-30 | 2021-05-04 | Wells Fargo Bank, N.A. | Mobile wallet account balance systems and methods |
US11610197B1 (en) | 2014-04-30 | 2023-03-21 | Wells Fargo Bank, N.A. | Mobile wallet rewards redemption systems and methods |
US9652770B1 (en) | 2014-04-30 | 2017-05-16 | Wells Fargo Bank, N.A. | Mobile wallet using tokenized card systems and methods |
US11663599B1 (en) | 2014-04-30 | 2023-05-30 | Wells Fargo Bank, N.A. | Mobile wallet authentication systems and methods |
US11748736B1 (en) | 2014-04-30 | 2023-09-05 | Wells Fargo Bank, N.A. | Mobile wallet integration within mobile banking |
US10783515B2 (en) * | 2014-06-19 | 2020-09-22 | IroFit Technologies Oy | Method and system for conducting wireless electronic credit card transactions |
US10045180B2 (en) * | 2014-08-06 | 2018-08-07 | Sony Interactive Entertainment America Llc | Method and apparatus for beacon messaging point of sale messaging and delivery system |
US10445739B1 (en) | 2014-08-14 | 2019-10-15 | Wells Fargo Bank, N.A. | Use limitations for secondary users of financial accounts |
US20160162842A1 (en) * | 2014-12-04 | 2016-06-09 | Dogpatch Technology, Inc. | Messaging system and method |
US11853919B1 (en) | 2015-03-04 | 2023-12-26 | Wells Fargo Bank, N.A. | Systems and methods for peer-to-peer funds requests |
US11803784B2 (en) | 2015-08-17 | 2023-10-31 | Siemens Mobility, Inc. | Sensor fusion for transit applications |
US11868989B1 (en) | 2015-12-30 | 2024-01-09 | Wells Fargo Bank, N.A. | Mobile wallets and companion smart cards |
US10546289B1 (en) | 2015-12-30 | 2020-01-28 | Wells Fargo Bank, N.A. | Mobile wallets with automatic element selection |
US10902405B1 (en) * | 2016-05-11 | 2021-01-26 | Wells Fargo Bank, N.A. | Transient mobile wallets |
US11468414B1 (en) | 2016-10-03 | 2022-10-11 | Wells Fargo Bank, N.A. | Systems and methods for establishing a pull payment relationship |
CN109905626B (en) * | 2017-12-08 | 2021-02-26 | 华平信息技术股份有限公司 | Remote video assistance method and system for POS machine, video assistance initiating end and receiving end |
US11295297B1 (en) | 2018-02-26 | 2022-04-05 | Wells Fargo Bank, N.A. | Systems and methods for pushing usable objects and third-party provisioning to a mobile wallet |
US11775955B1 (en) | 2018-05-10 | 2023-10-03 | Wells Fargo Bank, N.A. | Systems and methods for making person-to-person payments via mobile client application |
US11074577B1 (en) | 2018-05-10 | 2021-07-27 | Wells Fargo Bank, N.A. | Systems and methods for making person-to-person payments via mobile client application |
US12045809B1 (en) | 2018-08-30 | 2024-07-23 | Wells Fargo Bank, N.A. | Biller consortium enrollment and transaction management engine |
US11551190B1 (en) | 2019-06-03 | 2023-01-10 | Wells Fargo Bank, N.A. | Instant network cash transfer at point of sale |
JP6896813B2 (en) * | 2019-08-30 | 2021-06-30 | 株式会社日立製作所 | Transaction execution method and system |
US11005948B1 (en) * | 2019-12-30 | 2021-05-11 | EMC IP Holding Company LLC | Web content transfer utilizing messages of messaging protocol of cellular voice network |
US11995621B1 (en) | 2021-10-22 | 2024-05-28 | Wells Fargo Bank, N.A. | Systems and methods for native, non-native, and hybrid registration and use of tags for real-time services |
Family Cites Families (84)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5953485A (en) * | 1992-02-07 | 1999-09-14 | Abecassis; Max | Method and system for maintaining audio during video control |
US6771981B1 (en) * | 2000-08-02 | 2004-08-03 | Nokia Mobile Phones Ltd. | Electronic device cover with embedded radio frequency (RF) transponder and methods of using same |
US6199082B1 (en) * | 1995-07-17 | 2001-03-06 | Microsoft Corporation | Method for delivering separate design and content in a multimedia publishing system |
US6141666A (en) * | 1996-01-22 | 2000-10-31 | Internet Consultants Llc | Method and system for customizing marketing services on networks communicating with hypertext tagging conventions |
US7096003B2 (en) * | 1996-08-08 | 2006-08-22 | Raymond Anthony Joao | Transaction security apparatus |
US7357312B2 (en) * | 1998-05-29 | 2008-04-15 | Gangi Frank J | System for associating identification and personal data for multiple magnetic stripe cards or other sources to facilitate a transaction and related methods |
US6128655A (en) * | 1998-07-10 | 2000-10-03 | International Business Machines Corporation | Distribution mechanism for filtering, formatting and reuse of web based content |
DE59915075D1 (en) * | 1998-09-10 | 2009-10-22 | Swisscom Ag | Procedure for buying goods or services with a mobile phone |
US6605120B1 (en) * | 1998-12-10 | 2003-08-12 | International Business Machines Corporation | Filter definition for distribution mechanism for filtering, formatting and reuse of web based content |
KR100296049B1 (en) * | 1999-03-19 | 2001-07-28 | 윤종용 | User data transfering apparatus by using of short messageservice fuction in digital portable terminal and methodthereof |
US6886017B1 (en) * | 1999-04-30 | 2005-04-26 | Elata Limited | System and method for managing distribution of content to a device |
WO2001017298A1 (en) * | 1999-09-02 | 2001-03-08 | Automated Business Companies | Communication and proximity authorization systems |
US6772396B1 (en) * | 1999-10-07 | 2004-08-03 | Microsoft Corporation | Content distribution system for network environments |
US7308254B1 (en) * | 1999-12-15 | 2007-12-11 | Nokia Corporation | Wireless electronic couponing technique |
WO2001065798A1 (en) * | 2000-02-29 | 2001-09-07 | Swisscom Mobile Ag | Transaction confirmation method, authentication server and wap server |
US20030105641A1 (en) * | 2000-03-17 | 2003-06-05 | Woodson Lewis | Electronic ticketing and validation system and method |
US20040006497A1 (en) * | 2001-03-22 | 2004-01-08 | Nestor Tod A. | Entertainment event ticket purchase and exchange system |
US7487112B2 (en) * | 2000-06-29 | 2009-02-03 | Barnes Jr Melvin L | System, method, and computer program product for providing location based services and mobile e-commerce |
US7031945B1 (en) * | 2000-07-24 | 2006-04-18 | Donner Irah H | System and method for reallocating and/or upgrading and/or rewarding tickets, other event admittance means, goods and/or services |
US20020082879A1 (en) * | 2000-08-31 | 2002-06-27 | Brent Miller | Method and system for seat selection and ticket purchasing in a networked computer system |
US7774231B2 (en) * | 2000-09-29 | 2010-08-10 | Nokia Corporation | Electronic payment methods for a mobile device |
US6950939B2 (en) * | 2000-12-08 | 2005-09-27 | Sony Corporation | Personal transaction device with secure storage on a removable memory device |
US20020077918A1 (en) * | 2000-12-14 | 2002-06-20 | Guy Lerner | System & method for purchasing goods or services via the internet |
US20020107756A1 (en) * | 2000-12-18 | 2002-08-08 | Hammons James P. | Method for creating and operating a personalized virtual internet store including "disconnected" purchasing capability |
US20020077974A1 (en) * | 2000-12-19 | 2002-06-20 | Ortiz Luis M. | Wireless point of sale |
US20020169984A1 (en) * | 2001-05-09 | 2002-11-14 | Kumar Gopikrishna T. | Session management for wireless E-commerce |
US20030093695A1 (en) * | 2001-11-13 | 2003-05-15 | Santanu Dutta | Secure handling of stored-value data objects |
CN101482949A (en) * | 2001-12-04 | 2009-07-15 | M概念有限公司 | System and method for facilitating electronic financial transactions using a mobile telecommunications device |
WO2003058391A2 (en) * | 2001-12-26 | 2003-07-17 | Vivotech, Inc. | Wireless network micropayment financial transaction processing |
US20030172028A1 (en) * | 2002-03-07 | 2003-09-11 | International Business Machines Corporation | Authorization of payment for a commercial transaction via a bluetooth enabled device |
US6892052B2 (en) * | 2002-03-26 | 2005-05-10 | Nokia Corporation | Radio frequency identification (RF-ID) based discovery for short range radio communication |
WO2003090102A1 (en) * | 2002-04-22 | 2003-10-30 | Inphonic, Inc. | Method and system for short message service (sms) transactions for wireless devices |
EP1367542A3 (en) * | 2002-05-28 | 2005-05-25 | Siemens Aktiengesellschaft | Electronic ticket, system for issuing electronic tickets, and devices for using and performing operations on electronic tickets |
US20040104268A1 (en) * | 2002-07-30 | 2004-06-03 | Bailey Kenneth Stephen | Plug in credit card reader module for wireless cellular phone verifications |
US7606560B2 (en) * | 2002-08-08 | 2009-10-20 | Fujitsu Limited | Authentication services using mobile device |
US7784684B2 (en) * | 2002-08-08 | 2010-08-31 | Fujitsu Limited | Wireless computer wallet for physical point of sale (POS) transactions |
US7110792B2 (en) * | 2003-05-19 | 2006-09-19 | Einar Rosenberg | Apparatus and method for increased security of wireless transactions |
US20040243519A1 (en) * | 2003-06-02 | 2004-12-02 | Nokia Corporation | Prompted electronic mobile-service information communications with validation |
US8352360B2 (en) * | 2003-06-30 | 2013-01-08 | Toshiba Global Commerce Solutions Holdings Corporation | Method and system for secured transactions over a wireless network |
US8464353B2 (en) * | 2003-10-03 | 2013-06-11 | Hewlett-Packard Development Company, L. P. | Method and system for content downloads via an insecure communications channel to devices |
US20090177584A1 (en) * | 2004-01-05 | 2009-07-09 | Joseba Txomin Osoro Loyola | Digital card cd/dvd with contacless microcomputer chip for transportation systems |
US7828203B2 (en) * | 2004-02-23 | 2010-11-09 | Nec Corporation | Data writing apparatus, method, and program for portable terminal memory |
US7472829B2 (en) * | 2004-12-10 | 2009-01-06 | Qsecure, Inc. | Payment card with internally generated virtual account numbers for its magnetic stripe encoder and user display |
US20070197261A1 (en) * | 2004-03-19 | 2007-08-23 | Humbel Roger M | Mobile Telephone All In One Remote Key Or Software Regulating Card For Radio Bicycle Locks, Cars, Houses, And Rfid Tags, With Authorisation And Payment Function |
US8468093B2 (en) * | 2004-03-25 | 2013-06-18 | International Business Machines Corporation | Method and system for performing a commercial transaction by using a short message service terminal |
NO20041347L (en) * | 2004-03-31 | 2005-10-03 | Telenor Asa | Subscriber identity module |
US7289810B2 (en) * | 2004-12-10 | 2007-10-30 | Cisco Technology, Inc. | Location detection and network awareness for multi-mode/multi-radio mobile devices |
EP3291156B1 (en) * | 2005-03-07 | 2018-12-26 | Nokia Technologies Oy | Method and mobile terminal device including smartcard module and near field communications means |
US20060258397A1 (en) * | 2005-05-10 | 2006-11-16 | Kaplan Mark M | Integrated mobile application server and communication gateway |
CN100364342C (en) * | 2005-04-26 | 2008-01-23 | 华为技术有限公司 | Method for push business |
GB0510255D0 (en) * | 2005-05-19 | 2005-06-29 | Ramakrishna Madhusudana | Method and apparatus to embed distinguishing tags or raw data within existing data |
US7522905B2 (en) * | 2005-06-24 | 2009-04-21 | Visa U.S.A. Inc. | Apparatus and method for preventing wireless interrogation of portable consumer devices |
US7482925B2 (en) * | 2005-06-24 | 2009-01-27 | Visa U.S.A. | Apparatus and method to electromagnetically shield portable consumer devices |
US7819307B2 (en) * | 2005-10-27 | 2010-10-26 | Hewlett-Packard Development Company, L.P. | Method and system for managing monetary value on a mobile device |
US20070108269A1 (en) * | 2005-11-16 | 2007-05-17 | Benco David S | Processing merchant point-of-sale transactions using a mobile subscriber device |
US20090075592A1 (en) * | 2005-12-16 | 2009-03-19 | Sebastian Nystrom | Method and device for controlling and providing indications of communication events |
US7600675B2 (en) * | 2005-12-28 | 2009-10-13 | Compucredit Intellectual Property Holdings Corp. Ii | Method for providing financial instruments to customers of a service provider |
WO2007083319A2 (en) * | 2006-01-20 | 2007-07-26 | Ajay Adiseshann | Method and system for making a payment through a mobile communication device |
WO2007086068A2 (en) * | 2006-01-30 | 2007-08-02 | Fortressgb Ltd. | System for accepting value from closed groups |
BRPI0710021A2 (en) * | 2006-03-30 | 2011-08-02 | Obopay Inc | mobile individualized payment system |
US20070255662A1 (en) * | 2006-03-30 | 2007-11-01 | Obopay Inc. | Authenticating Wireless Person-to-Person Money Transfers |
WO2007120462A2 (en) * | 2006-03-31 | 2007-10-25 | Ontela Inc | Method and system for phone-number discovery and phone-number authentication for mobile communications devices |
US7562813B2 (en) * | 2006-05-10 | 2009-07-21 | First Data Corporation | System and method for activating telephone-based payment instrument |
US8016192B2 (en) * | 2006-06-06 | 2011-09-13 | Motorola Mobility, Inc. | User-configurable priority list for mobile device electronic payment applications |
US8510220B2 (en) * | 2006-07-06 | 2013-08-13 | Qualcomm Incorporated | Methods and systems for viewing aggregated payment obligations in a mobile environment |
US8467766B2 (en) * | 2006-07-06 | 2013-06-18 | Qualcomm Incorporated | Methods and systems for managing payment sources in a mobile environment |
JP2009543493A (en) * | 2006-07-11 | 2009-12-03 | ウルトラ プロイズボドニャ エレクトロンスキー ナプラブ デー.オー.オー. | Customer identification and authentication procedure for online internet payment using mobile phone |
US9418367B2 (en) * | 2006-08-21 | 2016-08-16 | International Business Machines Corporation | Context-aware code provisioning for mobile devices |
US20080208681A1 (en) * | 2006-09-28 | 2008-08-28 | Ayman Hammad | Payment using a mobile device |
US7962369B2 (en) * | 2006-09-29 | 2011-06-14 | Einar Rosenberg | Apparatus and method using near field communications |
WO2008051488A1 (en) * | 2006-10-19 | 2008-05-02 | July Systems, Inc. | Premium mobile service for discovery, payment, personalization and access of mobile content |
US7983646B2 (en) * | 2006-12-07 | 2011-07-19 | Hewlett-Packard Development Company, L.P. | Techniques to reduce radio frequency noise |
US10311427B2 (en) * | 2006-12-29 | 2019-06-04 | Google Technology Holdings LLC | Method and system for monitoring secure application execution events during contactless RFID/NFC communication |
US8014755B2 (en) * | 2007-01-05 | 2011-09-06 | Macronix International Co., Ltd. | System and method of managing contactless payment transactions using a mobile communication device as a stored value device |
US20080177668A1 (en) * | 2007-01-24 | 2008-07-24 | Bruno Delean | Computerized person-to-person payment system and method without use of currency |
US8793184B2 (en) * | 2007-02-12 | 2014-07-29 | Visa U.S.A. Inc. | Mobile payment services |
US20080208762A1 (en) * | 2007-02-22 | 2008-08-28 | First Data Corporation | Payments using a mobile commerce device |
US20080208743A1 (en) * | 2007-02-22 | 2008-08-28 | First Data Corporation | Transfer of value between mobile devices in a mobile commerce system |
US8566239B2 (en) * | 2007-02-22 | 2013-10-22 | First Data Corporation | Mobile commerce systems and methods |
US20080208712A1 (en) * | 2007-02-28 | 2008-08-28 | Phil Yerkes | Computer based systems to conduct sales of products or services over a communication network |
US20080294556A1 (en) * | 2007-05-24 | 2008-11-27 | Jim Anderson | Mobile commerce service |
US20080305769A1 (en) * | 2007-06-08 | 2008-12-11 | Nahum Rubinstein | Device Method & System For Facilitating Mobile Transactions |
US8504450B2 (en) * | 2007-08-31 | 2013-08-06 | Ebay Inc. | Mobile remittances/payments |
US7774076B2 (en) * | 2007-10-29 | 2010-08-10 | First Data Corporation | System and method for validation of transactions |
-
2007
- 2007-10-31 US US11/933,337 patent/US8019365B2/en not_active Expired - Fee Related
-
2011
- 2011-06-24 US US13/167,829 patent/US20110250866A1/en not_active Abandoned
Cited By (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10810594B2 (en) | 2007-01-30 | 2020-10-20 | Visa U.S.A. Inc. | Delayed transit fare assessment |
US20130275245A1 (en) * | 2007-01-30 | 2013-10-17 | Philip B. Dixon | Aggregation of validated transactions for settlement |
US9256875B2 (en) | 2007-01-30 | 2016-02-09 | Visa U.S.A. Inc. | Processing transactions of different payment devices of the same issuer account |
US8973818B2 (en) | 2007-01-30 | 2015-03-10 | Visa U.S.A. Inc. | Processing transactions of different payment devices of the same issuer account |
US9311643B2 (en) * | 2007-01-30 | 2016-04-12 | Visa U.S.A. Inc. | Aggregation of validated transactions for settlement |
US10055735B2 (en) | 2007-01-30 | 2018-08-21 | Visa U.S.A., Inc. | Delayed transit fare assessment |
US20080183565A1 (en) * | 2007-01-30 | 2008-07-31 | Phil Dixon | Delayed transit fare assessment |
US8504685B2 (en) * | 2008-07-10 | 2013-08-06 | SK Planet Co., Ltd | Personalized service system based on smart card and method thereof, and smart card applied to the same |
US20100325269A1 (en) * | 2008-07-10 | 2010-12-23 | Sk Telecom. Co., Ltd | Personalized service system based on smart card and method thereof, and smart card applied to the same |
US20200059831A1 (en) * | 2008-07-14 | 2020-02-20 | Sony Corporation | Communication apparatus, communication system, notification method, and program product |
US11678229B2 (en) * | 2008-07-14 | 2023-06-13 | Sony Corporation | Communication apparatus, communication system, notification method, and program product |
US10856187B2 (en) * | 2008-07-14 | 2020-12-01 | Sony Corporation | Communication apparatus, communication system, notification method, and program product |
US9572025B2 (en) * | 2009-04-16 | 2017-02-14 | Telefonaktiebolaget Lm Ericsson (Publ) | Method, server, computer program and computer program product for communicating with secure element |
US20120047237A1 (en) * | 2009-04-16 | 2012-02-23 | Petter Arvidsson | Method, Server, Computer Program and Computer Program Product for Communicating with Secure Element |
US8955747B2 (en) * | 2009-06-23 | 2015-02-17 | At&T Mobility Ii Llc | Devices, systems and methods for wireless point-of-sale |
US20100320266A1 (en) * | 2009-06-23 | 2010-12-23 | At&T Mobility Ii Llc | Devices, Systems and Methods for Wireless Point-of-Sale |
US11120413B2 (en) | 2011-06-03 | 2021-09-14 | Fintiv, Inc. | Monetary transaction system |
US11295281B2 (en) | 2011-06-03 | 2022-04-05 | Fintiv, Inc. | Monetary transaction system |
US9892386B2 (en) | 2011-06-03 | 2018-02-13 | Mozido, Inc. | Monetary transaction system |
US8538845B2 (en) | 2011-06-03 | 2013-09-17 | Mozido, Llc | Monetary transaction system |
US10438196B2 (en) | 2011-11-21 | 2019-10-08 | Mozido, Inc. | Using a mobile wallet infrastructure to support multiple mobile wallet providers |
US9208488B2 (en) | 2011-11-21 | 2015-12-08 | Mozido, Inc. | Using a mobile wallet infrastructure to support multiple mobile wallet providers |
US11468434B2 (en) | 2011-11-21 | 2022-10-11 | Fintiv, Inc. | Using a mobile wallet infrastructure to support multiple mobile wallet providers |
US8783438B2 (en) | 2012-11-30 | 2014-07-22 | Heb Grocery Company, L.P. | Diverter arm for retail checkstand and retail checkstands and methods incorporating same |
US9331747B2 (en) * | 2013-03-14 | 2016-05-03 | T-Mobile Usa, Inc. | Enhanced device configuration |
WO2014153272A1 (en) * | 2013-03-14 | 2014-09-25 | T-Mobile Usa, Inc. | Enhanced device configuration |
US20140274014A1 (en) * | 2013-03-14 | 2014-09-18 | T-Mobile Usa, Inc. | Enhanced device configuration |
US10387845B2 (en) | 2015-07-10 | 2019-08-20 | Bank Of America Corporation | System for facilitating appointment calendaring based on perceived customer requirements |
US10387846B2 (en) | 2015-07-10 | 2019-08-20 | Bank Of America Corporation | System for affecting appointment calendaring on a mobile device based on dependencies |
Also Published As
Publication number | Publication date |
---|---|
US8019365B2 (en) | 2011-09-13 |
US20080051122A1 (en) | 2008-02-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20210406856A1 (en) | Using a mobile device for an nfc payment and coupon transaction | |
US8019365B2 (en) | Conducting a payment using a secure element and SMS | |
US9009081B2 (en) | Purchasing tickets using an NFC enabled mobile communication device | |
US8190087B2 (en) | Scheduling and paying for a banking transaction using an NFC enabled mobile communication device | |
US20210174325A1 (en) | Nfc mobile payments using tokenization | |
US9684892B2 (en) | Proximity payment with coupon redemption using a server and an identification code | |
US10026076B2 (en) | Systems, methods, and computer readable media for payment and non-payment virtual card transfer between mobile devices | |
AU2009282041B2 (en) | Methods, systems and computer readable media for electronically delivering a prepaid card to a mobile device | |
TW201901552A (en) | Payment system a mobile device selecting a target identification data and inputting an amount to be paid, and a bank end debiting an account according to the target identification data and the amount to be paid |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- INCOMPLETE APPLICATION (PRE-EXAMINATION) |