| WO/2008/127967 | MOBILE COMMERCE INFRASTRUCTURE SYSTEMS AND METHODS |
| JP2006243809 | PORTABLE TERMINAL DEVICE |
| WO/2002/003342 | METHOD AND APPARATUS FOR A PAYMENT CARD SYSTEM |
ELDAR, Isaac (4 HaShaked Street, Even Yehuda, 40500, IL)
| CLAIMS What is claimed is: 1. A system comprising: a computer-based payment coordinator configured to receive a unique payment- coordination-identifier (PCI); based on said PCI, to identify a mobile device associated with a user, which is to approve a transaction of monetary value; to transmit to said mobile device an approval request message including transaction information identifying said transaction, and payment information identifying at least one payment account to facilitate said transaction; to receive from said mobile device an approval message indicating an approved payment account of said at least one payment account; and to provide an output including payment details sufficient to facilitate said transaction using said approved payment account. 2. The system of claim 1, wherein said PCI identifies a phone number associated with said mobile device. 3. The system of claim 2, wherein said PCI includes said phone number. 4. The system of claim 1, wherein said PCI comprises a PCI string having a string structure of a payment-account identifier. 5. The system of claim 4, wherein said PCI string comprises a pseudo payment-account identifier, and wherein said output includes a real payment-account identifier corresponding to said approved payment account. 6. The system of claim 4, wherein said PCI string has a string structure of a Primary Account Number (PAN). 7. The system of claim 6, wherein said PCI string includes an identifier of at least one of said payment coordinator and a payment-account manager, and wherein said PCI string includes a phone number associated with said mobile device. 8. The system of claim 1, wherein said payment information identifies a plurality of payment accounts. 9. The system of claim 1, wherein said payment coordinator is to identify, based on said PCI, at least one benefit corresponding to said transaction and said at least one payment account, and wherein said approval request message indicates said benefit. 10. The system of claim 1, wherein said output includes a payment-card number of a payment card associated with said approved payment account. 11. The system of claim 1 , wherein said payment coordinator is to receive said PCI from a payment-account manager of said payment account, and to transmit said payment details to said payment-account manager. 12. The system of claim 1, wherein said payment coordinator is to receive said PCI from a point-of-sale (POS) interacting in said transaction, and to transmit said payment details to said POS. 13. The system of claim 1 including a point-of-sale (POS) device to transmit said PCI to said payment coordinator, to receive said payment details, and to execute said transaction using said payment details. 14. A system comprising: a point-of-sale (POS) device to transmit to a predefined destination a unique payment- coordination-identifier (PCI), which is sufficient to allow said predefined destination to identify a mobile device associated with a user, which is to approve a transaction of monetary value with said POS device; and to receive from said destination payment details sufficient to facilitate said transaction using a payment account associated with said user. 15. The system of claim 14, wherein said PCI identifies a phone number associated with said mobile device. 16. The system of claim 15, wherein said PCI includes said phone number. 17. The system of claim 15, wherein said PCI comprises a PCI string having a string structure of a payment-account identifier. 18. The system of claim 17, wherein said PCI string has a string structure of a Primary Account Number (PAN). 19. The system of claim 18, wherein said PCI string includes an identifier of said destination, and wherein said PCI string includes a phone number associated with said mobile device. 20. The system of claim 15, wherein said PCI string comprises a pseudo payment-account identifier, and wherein said payment details include a real payment-account identifier corresponding to said payment account. 21. The system of claim 15, wherein said payment details include a payment-card number. 22. A system comprising: a mobile device to receive from a payment coordinator an approval request message including transaction information identifying a transaction of monetary value to be approved by a user of said mobile device, and payment information identifying at least one payment account associated with the user of said mobile device and at least one benefit corresponding to said transaction and said at least one payment account; to receive from said user an indication of an approved payment account of said at least one payment account; and to transmit to said payment coordinator an approval message indicating said approved payment account. 23. The system of claim 22, wherein said payment information identifies a plurality of payment accounts. 24. The system of claim 22, wherein said approval request message indicates at least one benefit corresponding to said transaction and said at least one payment account. 25. A method of facilitating a transaction of monetary value based on approval by a user of a mobile device, the method comprising: receiving a unique payment-coordination-identifier (PCI); based on said PCI, identifying said mobile device; transmitting to said mobile device an approval request message including transaction information identifying said transaction, and payment information identifying at least one payment account to facilitate said transaction; receiving from said mobile device an approval message indicating an approved payment account of said at least one payment account; and providing an output including payment details sufficient to facilitate said transaction using said approved payment account. 26. The method of claim 25, wherein said PCI identifies a phone number associated with said mobile device. 27. The method of claim 26, wherein said PCI includes said phone number. 28. The method of claim 25, wherein said PCI comprises a PCI string having a string structure of a payment-account identifier. 29. The method of claim 28, wherein said PCI string comprises a pseudo payment-account identifier, and wherein said output includes a real payment-account identifier corresponding to said approved payment account. 30. The method of claim 28, wherein said PCI string has a string structure of a Primary Account Number (PAN). 31. The method of claim 30, wherein said PCI string includes an identifier of at least one of a payment coordinator and a payment-account manager, and wherein said PCI string includes a phone number associated with said mobile device. 32. The method of claim 25, wherein said payment information identifies a plurality of payment accounts. 33. The method of claim 25 comprising identifying, based on said PCI, at least one benefit corresponding to said transaction and said at least one payment account, and wherein said approval request message indicates said benefit. 34. The method of claim 25, wherein said output includes a payment-card number of a payment card associated with said approved payment account. 35. The method of claim 25, wherein receiving said PCI comprises receiving said PCI from a payment-account manager of said payment account, and wherein providing said output comprises transmitting said payment details to said payment-account manager. 36. The method of claim 25, wherein receiving said PCI comprises receiving said PCI from a point-of-sale (POS) interacting in said transaction, and wherein providing said output comprises transmitting said payment details to said POS. 37. The method of claim 25 including transmitting said PCI from a point-of-sale (POS) to a payment coordinator, receiving said payment details at said POS, and executing said transaction using said payment details. |
CROSS-REFERENCE
[001] This application claims the benefit of, and priority from, US Provisional Patent application No. 61/365,379, entitled "Device, System and Method of Cardless Payment", filed July 19, 2010, and US Provisional Patent application No. 61/378,016, entitled "Device, System and Method of Cardless Payment", filed August 30, 2010, the entire disclosures of both of which are incorporated herein by reference.
BACKGROUND
[002] The majority of consumers in the developed countries own at least one payment card, e.g., credit card, debit card, bank card, prepaid card, and the like (collectively referred to as "credit cards" or "payment cards"), which is used for conducting everyday financial transactions.
[003] A payment card based purchase transaction of an item at a merchant's point of sale (POS) is divided into 3 processes, namely, providing information of the item to the POS; scanning a plastic payment card for retrieving payment details into the POS, or manually keying in the card's details into a payment system of the merchant; and performing an online communication transaction between the POS and a payment card provider for approving the payment's account details and amount, and completing the purchase transaction.
[004] Consumers are carrying fully loaded wallets with multiple plastic credit cards, each containing personal information, authentication information, and specific payment account details provisioned to merchants for completing a purchase transaction.
[005] However, physical plastic payment cards are inconvenient, insecure and are subject to fraud when lost or stolen. In addition, plastic cards are not friendly to the environment due to their non-recyclable nature.
SUMMARY
[006] Some demonstrative embodiments include methods, devices and systems of mobile- device approval of payment.
[007] Some demonstrative embodiments include a computer-based payment coordinator configured to receive a unique payment-coordination-identifier (PCI); based on the PCI, to identify a mobile device associated with a user, which is to approve a transaction of monetary value; to transmit to the mobile device an approval request message including transaction information identifying the transaction, and payment information identifying at least one payment account to facilitate the transaction; to receive from the mobile device an approval message indicating an approved payment account of the at least one payment account; and to provide an output including payment details sufficient to facilitate the transaction using the approved payment account.
[008] In some demonstrative embodiments, the PCI identifies a phone number associated with the mobile device. In some demonstrative embodiments, the PCI includes the phone number.
[009] In some demonstrative embodiments, the PCI includes a PCI string having a string structure of a payment-account identifier. In some demonstrative embodiments, the PCI string includes a pseudo payment-account identifier, and wherein the output includes a real payment- account identifier corresponding to the approved payment account.
[0010] In some demonstrative embodiments, the PCI string has a string structure of a Primary Account Number (PAN). In some demonstrative embodiments, the PCI string includes an identifier of at least one of the payment coordinator and a payment-account manager, and wherein the PCI string includes a phone number associated with the mobile device.
[0011] In some demonstrative embodiments, the payment information identifies a plurality of payment accounts.
[0012] In some demonstrative embodiments, the payment coordinator is to identify, based on the PCI, at least one benefit corresponding to the transaction and the at least one payment account, and wherein the approval request message indicates the benefit.
[0013] In some demonstrative embodiments, the output includes a payment-card number of a payment card associated with the approved payment account.
[0014] In some demonstrative embodiments, the payment coordinator is to receive the PCI from a payment-account manager of the payment account, and to transmit the payment details to the payment-account manager. [0015] In some demonstrative embodiments, the payment coordinator is to receive the PCI from a point-of-sale (POS) interacting in the transaction, and to transmit the payment details to the POS.
[0016] In some demonstrative embodiments, a point-of-sale (POS) device is to transmit the PCI to the payment coordinator, to receive the payment details, and to execute the transaction using the payment details.
[0017] Some demonstrative embodiments include a system including a POS device to transmit to a predefined destination a unique PCI, which is sufficient to allow the predefined destination to identify a mobile device associated with a user, which is to approve a transaction of monetary value with the POS device; and to receive from the destination payment details sufficient to facilitate the transaction using a payment account associated with the user.
[0018] Some demonstrative embodiments include a system including a mobile device to receive from a payment coordinator an approval request message including transaction information identifying a transaction of monetary value to be approved by a user of the mobile device, and payment information identifying at least one payment account associated with the user of the mobile device and at least one benefit corresponding to the transaction and the at least one payment account; to receive from the user an indication of an approved payment account of the at least one payment account; and to transmit to the payment coordinator an approval message indicating the approved payment account.
[0019] In some demonstrative embodiments, the payment information identifies a plurality of payment accounts.
[0020] In some demonstrative embodiments, the approval request message indicates at least one benefit corresponding to the transaction and the at least one payment account.
[0021] Some demonstrative embodiments include a method of facilitating a transaction of monetary value based on approval by a user of a mobile device. The method may include receiving a unique PCI; based on the PCI, identifying the mobile device; transmitting to the mobile device an approval request message including transaction information identifying the transaction, and payment information identifying at least one payment account to facilitate the transaction; receiving from the mobile device an approval message indicating an approved payment account of the at least one payment account; and providing an output including payment details sufficient to facilitate the transaction using the approved payment account.
[0022] Other embodiments are described and claimed. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] For simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity of presentation. Furthermore, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. The figures are listed below.
[0024] Fig. 1 is a schematic illustration of a system, in accordance with some demonstrative embodiments.
[0025] Fig. 2 is a schematic flow-chart illustration of a method of payment, in accordance with some demonstrative embodiments.
[0026] Figs. 3A, 3B, 3C, 3D, 3E and 3F are exemplary mobile device screen shots, in accordance with some demonstrative embodiments.
[0027] Fig. 4 is a schematic illustration of an article of manufacture, in accordance with some demonstrative embodiments.
[0028] Fig. 5 is a schematic illustration of a first payment process, in accordance with some demonstrative embodiments.
[0029] Fig. 6 is a schematic illustration of a second payment process, in accordance with some demonstrative embodiments.
[0030] Fig. 7 is a schematic illustration of a payment-coordination-identifier (PCI) string structure, in accordance with some demonstrative embodiments.
[0031] Fig. 8 is a schematic illustration of a process of approving a transaction using a mobile device, in accordance with some demonstrative embodiments.
DETAILED DESCRIPTION
[0032] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of some embodiments. However, it will be understood by persons of ordinary skill in the art that some embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, units and/or circuits have not been described in detail so as not to obscure the discussion.
[0033] Discussions herein utilizing terms such as, for example, "processing", "computing", "calculating", "determining", "establishing", "analyzing", "checking", or the like, may refer to operation(s) and/or process(es) of a computer, a computing platform, a computing system, or other electronic computing device, that manipulate and/or transform data represented as physical (e.g., electronic) quantities within the computer's registers and/or memories into other data similarly represented as physical quantities within the computer's registers and/or memories or other information storage medium that may store instructions to perform operations and/or processes.
[0034] The terms "plurality" and "a plurality" as used herein include, for example, "multiple" or "two or more". For example, "a plurality of items" includes two or more items.
[0035] The term "item" as used herein may refer to any suitable product or service. The product may include, for example, any suitable commodity, merchandise, and/or goods. The service may include, for example, any economic activity, operation and/or action relating to non-material goods, e.g., one or more benefits delivered by a service provider. The service may also include the allowing or providing the possibility and/or right to enter and/or visit a public and/or private place, site, location, and the like.
[0036] The term "transaction" as used herein may refer to a selling action, operation or activity; a buying action, operation or activity; an exchange; a trade; a commercial action, operation or activity; an activity, for example, a physical activity, e.g., arriving at, visiting, and/or entering a place, site, location, and the like; a deal; a purchase, a donation, a gift, a contribution, and/or a sale performed with relation to an item. The transaction may be performed online and/or offline, e.g., using an Interactive Voice Response (IVR) system, via a call to a representative of the item, a face-to-face operation, e.g., in store, using an e-commerce system, using a coupon, and the like.
[0037] The phrase "payment account" as used herein may refer to any suitable financial account capable of facilitating a transaction of monetary value, e.g., for making a payment and/or transferring money. In one example, the payment account may include or may be associated with any suitable payment card. In another example, the payment account may include any suitable bank account, savings account, credit account, checking account, billing account, an electronic account, for example, a web-based payment account, e.g., a Paypal account, and the like.
[0038] The phrase "payment account manager" may include any suitable entity having access to and/or authorize to manage and/or control a payment account. For example, the payment account manager may include any suitable card issuer, e.g., a credit card issuer, a financial institute, e.g., a bank, a financial service provider, e.g., Paypal, another service provider, e.g., a mobile operator, a cellular operator, an internet-service provider, and the like.
[0039] The phrases "payment card" and/or "credit card" as used herein include, for example, any suitable physical or electronic card suitable for facilitating a transaction of monetary value, e.g., a credit card, a bank card, a debit card, a prepaid card, and the like, which may be used for performing a transaction, e.g., at a point of sale.
[0040] The phrase "payment account identifier" may include any suitable information and/or data, e.g., in the form of a value, a string, a number, graphic, and the like, configured to identify at least one payment account. In one example, the payment account identifier may include a suitable credit card number, e.g., having a structure of a suitable Primary Account Number (PAN). For example, the payment account identifier may include a numeral string including sixteen digits, e.g., including a first set of digits, e.g., four digits, identifying a payment account manager of the payment account, a second set of digits, e.g., 11 digits, uniquely identifying a user and/or owner of the payment account, and/or at least one control digit. In another example, the payment account identifier may include an identifier of a bank account, savings account, credit account, checking account, billing account, an electronic account, for example, a web- based payment account, e.g., a Paypal account, and the like.
[0041] The phrase "point of sale" (POS) as used herein may refer to a location, e.g., a physical location, a remote location, an online location, and/or a virtual location, at which a transaction occurs.
[0042] The phrase "wireless communication device", "mobile device" and/or "mobile phone" as used herein includes, for example, a device capable of wireless communication, a communication device capable of wireless communication, a communication station capable of wireless communication, a portable or non-portable device capable of wireless communication, or the like. In some demonstrative embodiments, a wireless device may be or may include a peripheral that is integrated with a computer, or a peripheral that is attached to a computer. In some demonstrative embodiments, the term "wireless device" may optionally include a wireless service. In one example, the mobile device may include any suitable cellular device, e.g., a cellular phone and/or a device performing the functionality of a cellular phone. [0043] The phrase "payment-coordination-identifier" (PCI) as used herein may refer to any suitable data, information, value, string, and the like, which is sufficient to allow a predefined destination to identify a mobile device, e.g., uniquely identifying the mobile device. The predefined destination may include any suitable element for communicating with the mobile device, e.g., in order to approve a transaction. In one example, the destination may include a mobile operator, a cellular operator, and the like. In another example, the destination may include a payment account manager of a payment account associated with a user and/or one owner of the mobile device. For example, the PCI may identify the mobile device using a unique phone number associated with the mobile device, e.g., a cellular phone number, an voice-over- internet-protocol (VoIP) number, e.g., a Skype number, a landline phone number and/or any other suitable phone number associated with the mobile device. In one example, the PCI may include the phone number. In another example, the PCI may include any suitable information, e.g., a unique user code, a unique customer code, and the like, which may be associated with, and/or sufficient for determining, the phone number. The PCI may have any suitable format and/or structure. In one example, the PCI may include a string having a structure compatible with a structure of a suitable payment card identifier, e.g., as described below. In other embodiments, the PCI may have any other suitable structure.
[0044] The term "message" as used herein may refer to any suitable element and/or object suitable for communication and/or conveying information between at least first and second elements. The message may have any suitable form and/or format. For example, the message may include a text message, a video message, an audio message, a graphic message, an electronic message, a message application, and the like. In one example, the message may include a suitable mobile communication message, e.g., a Short Message Service (SMS) message, an Unstructured Supplementary Service Data (USSD) message, a Multimedia Message Service (MMS) message, and the like. In another example, the message may include a suitable electronic mail (E-mail) message, e.g., in accordance with the Simple Mail Transfer Protocol (SMTP), the Hyper Text Transfer Protocol (HTTP), and the like. In another example, the message may include a suitable Instant Message (IM), an ICQ message, an America-Online Instant Messenger (AIM) message, a Windows Live Messenger (WLM) message, a QQ message, a Skype message, an Extensible Messaging and Presence Protocol (XMPP) message, a Mobile Instant Messaging (MIM) message, an Enterprise Instant Messaging (EIM) message, an IVR message, an iPhone application and the like.
[0045] Some embodiments may be used in conjunction with various devices and systems, for example, a Personal Computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, a Personal Digital Assistant (PDA) device, a handheld PDA device, an on-board device, an off-board device, a hybrid device, a vehicular device, a non-vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a Personal Media Player (PMP), a data source, a data sink, a wired or wireless network, a wireless area network, a Local Area Network (LAN), a Wireless LAN (WLAN), a Personal Area Network (PAN), a Wireless PAN (WPAN), devices and/or networks operating in accordance with existing IEEE 802.11 {IEEE 802.11-2007, IEEE Standard for Information Technology— Telecommunications and information exchange between systems— Local and metropolitan area networks— Specific requirements, Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications), 802.16 (IEEE-Std 802.16, 2004 Edition, Air Interface for Fixed Broadband Wireless Access Systems), collectively referred to as "the IEEE 802 standards", and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing Wireless- Gigabit- Alliance (WGA) specifications and/or future versions and/or derivatives thereof, units and/or devices which are part of the above networks, one way and/or two-way radio communication systems, cellular radio-telephone communication systems, a cellular telephone, a wireless telephone, a Personal Communication Systems (PCS) device, a PDA device which incorporates a wireless communication device, a mobile or portable Global Positioning System (GPS) device, a device which incorporates a GPS receiver or transceiver or chip, a device which incorporates an RFID element or chip, a Multiple Input Multiple Output (MIMO) transceiver or device, a Single Input Multiple Output (SIMO) transceiver or device, a Multiple Input Single Output (MISO) transceiver or device, a device having one or more internal antennas and/or external antennas, a wired or wireless handheld device (e.g., BlackBerry, Palm Treo), a Wireless Application Protocol (WAP) device, or the like.
[0046] Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems, for example, Near Field Communication (NFC), Radio Frequency (RF), Infra Red (IR), Frequency-Division Multiplexing (FDM), Orthogonal FDM (OFDM), Time-Division Multiplexing (TDM), Time-Division Multiple Access (TDM A), Extended TDMA (E-TDMA), General Packet Radio Service (GPRS), extended GPRS, Code- Division Multiple Access (CDMA), Wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, Multi-Carrier Modulation (MDM), Discrete Multi-Tone (DMT), Bluetooth®, Global Positioning System (GPS), Wi-Fi, Wi-Max, ZigBee™, Ultra- Wideband (UWB), Global System for Mobile communication (GSM), 2G, 2.5G, 3G, 3.5G, Enhanced Data rates for GSM Evolution (EDGE), or the like. Other embodiments may be used in various other devices, systems and/or networks.
[0047] Some demonstrative embodiments may be used in conjunction with suitable limited- range or short-range wireless communication networks, for example, NFC technology, a wireless area network, a "piconet", a WPAN, a WVAN and the like.
[0048] For example, in some demonstrative embodiments a mobile device may perform wireless communication in accordance with any suitable NFC protocol, WiFi protocol, WiGig protocol, and the like. The NFC protocol may include a communication protocol in accordance with ISO/IEC 14443 Parts 1-4: Identification cards - Contactless integrated circuit(s) cards, 1999, ISO/IEC 18092: Information technology — Telecommunications and information exchange between systems— Near Field Communication— Interface and Protocol (NFCIP-1), SO/IEC 21481:2005: Information technology— Telecommunications and information exchange between systems— Near Field Communication Interface and Protocol -2 (NFCIP-2), and/or NFC Forum Data Exchange Format (NDEF) Technical Specification Version 1.0, July 24, 2006 ("the NFC specifications") and/or future versions and/or derivatives thereof.
[0049] The WiFi protocol may include a communication protocol in accordance with the IEEE 802.11 specifications and/or future versions and/or derivatives thereof.
[0050] The WiGig protocol may include a communication protocol in accordance with IEEE P802.1 lad/Dl.O Draft Standard for Information Technology - Telecommunications and Information Exchange Between Systems - Local and Metropolitan Area Networks - Specific Requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications - Amendment 5: Enhancements for Very High Throughput in the 60GHz Band, and/or Wireless Gigabit Alliance WiGig Mac and PHY specification Versionl.O, April 2010 ("the WiGig specifications") and/or future versions and/or derivatives thereof.
[0051] Reference is now made to Fig. 1, which schematically illustrates a block diagram of a system 100, in accordance with some demonstrative embodiments.
[0052] As shown in Fig. 1, in some demonstrative embodiments, system 100 may include two or more devices and/or systems, e.g., at least one mobile device ("client device") 102, which may be used by a user ("client") 101, at least one payment coordinator (also referred to as "controller" and/or "operator") 104, and at least one POS device 106.
[0053] In some demonstrative embodiments, system 100 may also include, and/or one or more elements of system 100 may be implemented as part of and/or in association with one or more additional suitable elements and/or entities. [0054] In some demonstrative embodiments, system 100 may include at least one payment account manager 107 capable of managing at least one payment account associated with and/or owned by client 101, e.g., a described below. In some demonstrative embodiments, payment account manager 107 may include any device operated and/or supervised by one or more payment technology companies, payment card service providers, and/or credit card companies, including for example, Visa, Isracard, Diners, American Express, a financial institue, a bank, and the like. In one example, payment account manager 107 may include and/or may be associated with a suitable Card Provider or Card Acquirer (CP).
[0055] In some demonstrative embodiments, payment coordinator 104 may be implemented as part of payment account manager 107. In other embodiments, payment coordinator 104 and payment account manager 107 may be implemented as separate elements of system 100.
[0056] In some demonstrative embodiments, device 102, controller 104, POS device 106 and/or manager 107 may communicate with one another via any suitable wired and/or wireless link, e.g., utilizing any suitable a radio channel, IR channel, RF channel, and the like. The wireless links may include wireless links according to any suitable protocol, e.g., the NFC, WIFi and/or WiGig protocols. According to some demonstrative embodiments, data and/or required information may be indirectly and/or manually provided from a first device of system 100, e.g., client device 102, to a second device of system 100, e.g., POS device 106, by manually feeding the required information into the second device. For example, an operator of POS device 106 may manually feed to POS device 106 information associated with client device 102.
[0057] In some demonstrative embodiments, mobile device 102 may communicate with POS device 106 via a suitable communication link 119; mobile device 102 may communicate with payment coordinator 104 via a suitable communication link 123; payment coordinator 104 may communicate with POS device 106 via a suitable communication link 121A; POS device 106 may communicate with manager 107 via a suitable communication link 125; and/or controller 1004 may communicate with manager 107 via a suitable communication link 12 IB. In one example, link 119 may include a suitable wireless link, e.g., a WiFi link, an NFC link and the like; link 123 may include a suitable wireless link, e.g., a WiFi link, a cellular link, and the like; and/or links 121A, 121B and/or 125 may include any suitable wired and/or wireless links.
[0058] In some demonstrative embodiments, at least one of devices 102, 104, 106 and/or 107, e.g., client device 102, may include a wireless communication unit 108 capable of transmitting and/or receiving wireless communication transmissions to and/or from one or more other devices of system 100, e.g., payment coordinator 104. [0059] In some demonstrative embodiments, one or more of devices 102, 104, 106 and/or 107 may include, for example, an enterprise computing system, a mainframe computer, a PC, a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a non-mobile or non-portable device, a cellular telephone, a Smartphone, an iPhone, a BlackBerry device, a PCS device, a PDA device which incorporates a wireless communication device, a mobile or portable GPS device, a relatively small computing device, a non-desktop computer, a "Carry Small Live Large" (CSLL) device, an Ultra Mobile Device (UMD), an Ultra Mobile PC (UMPC), a Mobile Internet Device (MID), an "Origami" device or computing device, a device that supports Dynamically Composable Computing (DCC), a context-aware device, a data source, a data sink, a media player, a Smartphone, a television, a music player, or the like.
[0060] In some demonstrative embodiments, one or more of devices 102, 104, 106 and/or 107 may include, for example, one or more of a processor 120, an input unit 112, an output unit 114, a memory unit 118 and a storage unit 116. Devices 102, 104, 106 and/or 107 may optionally include other suitable hardware components and/or software components. In some demonstrative embodiments, some or all of the components of devices 102, 104, 106 and/or 107 may be enclosed in a common housing or packaging, and may be interconnected or operably associated using one or more wired or wireless links. In other embodiments, components of devices 102, 104, 106 and/or 107 may be distributed among multiple or separate devices or locations.
[0061] Processor 120 includes, for example, a Central Processing Unit (CPU), a Digital Signal Processor (DSP), one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, one or more circuits, circuitry, a logic unit, an Integrated Circuit (IC), an Application-Specific IC (ASIC), or any other suitable multi-purpose or specific processor or controller. Processor 120 executes instructions, for example, of an Operating System (OS) of client device 102, and/or of one or more suitable applications.
[0062] Input unit 112 includes, for example, a keyboard, a keypad, a mouse, a touch-pad, a track-ball, a stylus, a microphone, a scanner or other suitable pointing device or input device. Output unit 114 includes, for example, a monitor, a screen, a flat panel display, a Cathode Ray Tube (CRT) display, a Liquid Crystal Display (LCD), an LED display, a plasma display unit, one or more audio speakers or earphones, or other suitable output devices. [0063] Memory unit 118 includes, for example, a Random Access Memory (RAM), a Read Only Memory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM (SD-RAM), a flash memory, a volatile memory, a non-volatile memory, a cache memory, a buffer, a short term memory unit, a long term memory unit, or other suitable memory units. Storage unit 116 includes, for example, a hard disk drive, a floppy disk drive, a Compact Disk (CD) drive, a CD- ROM drive, a DVD drive, or other suitable removable or non-removable storage units. Memory unit 118 and/or storage unit 116, for example, store data processed by client device 102.
[0064] In some demonstrative embodiments, wireless communication unit 108 includes or may be part of, for example, one or more wireless transmitters, receivers and/or transceivers able to send and/or receive wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, specific data items, and/or any other type of communication data. For example, wireless communication unit 108 may include or may be implemented as part of a suitable wireless communication unit, for example, a suitable wireless Network Interface Card (NIC), and the like. In one example, wireless communication unit 108 may include a cellular communication unit capable of communicating with payment coordinator 104 via a cellular link.
[0065] In some demonstrative embodiments, wireless communication unit 108 may include, or may be associated with, at least one antenna 110. Antenna 110 may include, for example, an internal and/or external RF antenna, a dipole antenna, a monopole antenna, an omni-directional antenna, an end fed antenna, a circularly polarized antenna, a micro-strip antenna, a diversity antenna, or other type of antenna suitable for transmitting and/or receiving wireless communication signals, blocks, frames, transmission streams, packets, messages and/or data.
[0066] In some demonstrative embodiments, payment coordinator 104 may include and/or be part of a mobile network operator (MNO), a mobile phone operator (also known as a mobile operator or a mobo), e.g., a Customer Relationship Management (CRM) of the mobile operator, a carrier service provider (CSP), a wireless service provider, a wireless carrier, and/or any cellular company or telephone company that is capable of providing services for mobile phone subscribers. In one example, when client device 102 is a mobile phone, payment coordinator 104 may be a mobile phone operator, e.g., Globalstar.
[0067] In other embodiments, payment coordinator 104 may include and/or be part of any other suitable service provider, for example, a card acquirer, a card issuer, a card processor, a bank, a mobile operator, a payment processing company, an internet provider, a web service, a payment service provider, a financial service provider, a credit service provider, and the like.
[0068] In some demonstrative embodiments, POS device 106 may include any device capable of conducting and/or mediating a transaction; and/or any device located where a transaction may occur, including, for example, a physical POS, a remote payment system and/or an online payment system. In some demonstrative embodiments, POS device 106 may be operated and/or supervised by retailers and/or merchants, including, for example, physical retailers, online retailers, telephone retailers and/or any other merchant accepting card payments from consumers.
[0069] In some demonstrative embodiments, client 101 may be a user and/or owner of client device 102. For example, device 102 may be a cellular phone, and client 101 may be the owner of the cellular phone. In some embodiments, details of a payment account of client 101 may be maintained by payment coordinator 104, e.g., in association with identification details of device 102, e.g., a cellular phone number associated with device 102.
[0070] In conventional payment systems, a transaction, e.g., a purchase of groceries, may be conducted by debiting a suitable payment account, e.g., using a payment card. Usually, the credit card is passed and/or scanned through a POS device, and an online communication transaction between the POS device and a payment card provider/acquirer takes place. After the card provider/acquirer approves the payments' account details and amount, the purchase transaction is completed. In another example, a monetary web-based transaction may be facilitated by providing to a web-based service a payment account identifier, e.g., a payment card number, associated with a payment account.
[0071] In some demonstrative embodiments, system 100 may enable a user and/or owner of device 102, e.g., client 101, to approve and/or conduct financial transactions without using common means for conducting financial transactions, e.g., cash and/or payment card. For example, device 102 may interact with POS device 106 and/or payment coordinator 104 to conduct one or more financial transactions, e.g., without requiring the use of a payment card, as described in detail below.
[0072] In some demonstrative embodiments, device 102 may be utilized by client 101 to approve a transaction with POS device 106, e.g., as described in detail below.
[0073] In one example, client 101 may be the user and/or owner of device 102 as well as being the person interacting in a transaction with POS device 106. For example, client 101 may interact with POS device 106 to perform a transaction of monetary value, and client 101 may use device 102 to approve a payment account to be used for facilitating the transaction, e.g., as described below.
[0074] In another example, client 101 may be different from a person interacting in a transaction with POS device 106. For example, a first person may interact in a transaction with POS device 106, and client 101 may approve a payment account to facilitate the transaction. In one example, a child may interacting in a transaction with POS device 106, while client 101 may include a parent of the child, which may utilize device 102 to approve a payment account to be used for facilitating the transaction, e.g., as described below.
[0075] In some demonstrative embodiments, POS device 106 may be capable of defining and/or generating a transaction, e.g., by calculating prices and/or total amounts required for payment.
[0076] In some demonstrative embodiments, client device 102 may provide POS device 106 with details regarding client 101 and/or regarding client device 102, e.g., when client 101 wishes to conduct the transaction.
[0077] In some demonstrative embodiments, payment coordinator 104 and/or payment account manager 107 may include a benefit database including discounts and/or special offers associated with various payment accounts, which may be offered to client 101, e.g., as described below. These benefits may result, e.g., from marketing agreements between a store, a retail chain or any other merchant and one or more payment account managers.
[0078] In some demonstrative embodiments, POS device 106 may be configured to communicate with payment coordinator 104, e.g., for sending to payment coordinator 104 the details regarding client 101 and/or regarding client device 102.
[0079] In some demonstrative embodiments, POS device 106 may not be configured to directly communicate with payment coordinator 104, e.g., via link 121A. For example, POS device 106 may communicate with payment account manager 107, e.g., via link 125, while payment account manager 107 communicates with payment coordinator 104.
[0080] In some demonstrative embodiments, applicable benefits may transmitted from payment coordinator 104 to device 102, e.g., as part of an approval request, e.g., as described below.
[0081] In some demonstrative embodiments, payment coordinator 104 may have access to a database; and/or be configured to communicate with POS device 106 and/or client device 102, for example, in order to send client device 102 a request for approval of the transaction, e.g., including one or more payment options relating to client 101, e.g., as described below.
[0082] In some demonstrative embodiments, client 101 may review the request for approval and/or payment option and/or benefits and send back an approval to payment coordinator 104 via client device 102, e.g., as described below.
[0083] In some demonstrative embodiments, payment coordinator 104 may be configured to receive a unique PCI, which is sufficient to allow payment coordinator 104 to identify device 102, which is to be utilized for approving a transaction of monetary value with POS device 106.
[0084] In some demonstrative embodiments, payment coordinator 104 may identify mobile device 102, based on the PCI. Payment coordinator 104 may identify mobile device 102 based directly on the PCI and/or using any other suitable information, which may be accessible by coordinator 104.
[0085] In one embodiment, payment coordinator 104 may receive the PCI from POS device 106, e.g., via link 119. For example, POS device 106 may transmit the PCI to payment coordinator 104 based on information received from device 102 and/or client 101. For example, POS device 106 may receive from device 102 and/or client 101 the PCI and/or other information sufficient for POS device 106 to determine the PCI. In one example, device 102 may transfer to POS device 106 the PCI via link 119, e.g., via a NFC link. In another example, device 102 may transfer to POS device 106 a customer number via link 119, e.g., via a NFC link, and POS device may utilize any suitable database to determine the PCI based on the customer number. In another example, the PCI and/or other information sufficient for POS device 106 to determine the PCI may be provided to POS device 106 manually.
[0086] In some demonstrative embodiments, the PCI may identify a phone number associated with mobile device 102.
[0087] In some demonstrative embodiments, the PCI may include the phone number.
[0088] In some demonstrative embodiments, the PCI may include a PCI string having a string structure of a payment-account identifier. For example, the PCI string may have a string structure of a Primary Account Number (PAN). In one example, the PCI string may include an identifier of at least one of payment coordinator 104 and payment-account manager 107, and a phone number associated with mobile device 102, e.g., as described below with reference to Fig. 7.
[0089] In some demonstrative embodiments, payment coordinator 104 may transmit to mobile device 102 an approval request message including transaction information identifying the transaction with POS 106, and payment information identifying at least one payment account associated with the PCI to facilitate the transaction, e.g., as described below.
[0090] In some demonstrative embodiments, payment coordinator 104 may receive from mobile device 104 an approval message indicating an approved payment account of the at least one payment account.
[0091] For example, client 101 may use input 112 to select and/or approve a payment account from the one or more payment accounts included in the request message, and device 102 may transmit to payment coordinator the approval message indicating the approved payment account.
[0092] In one example, the request message may include a single payment account and client 101 may approve the payment account. In another example, the payment information identifies a plurality of payment accounts, e.g., to which client 101 has authorization, and client 101 may select to approve one of the plurality of payment accounts.
[0093] In some demonstrative embodiments, payment coordinator 104 may provide an output including payment details sufficient to facilitate the transaction with POS device 106 using the approved payment account, e.g., as described below. In one example, the output may include a payment-card number of a payment card associated with the approved payment account, e.g., as described below.
[0094] In some demonstrative embodiments, payment coordinator 104 may receive the PCI from payment-account manager 107, e.g., via link 12 IB, and may transmit the payment details to payment-account manager 107, for example, if POS device 106 is not in direct contact with payment coordinator 104.
[0095] In some demonstrative embodiments, payment coordinator 104 may receive the PCI from POS device 106, and may transmit the payment details to POS device 106, e.g., via link 121A, for example, if POS device 106 is in direct contact with payment coordinator 104.
[0096] In some demonstrative embodiments, payment coordinator 104 may identify, based on the PCI, at least one benefit corresponding to the transaction and to the at least one payment account. For example, payment coordinator 104 may have access to any suitable storage and/or database storing benefits, e.g., discounts, special offers, and the like. The benefits may be associated with and/or customized for one or more types of transactions, one or ore retailers, one or more stores, one or more payment accounts, one or more people, and the like.
[0097] In some demonstrative embodiments, payment coordinator 104 may generate the approval request message indicating the at least one benefit, e.g., as described below.
[0098] In some demonstrative embodiments, POS device 106 may execute the transaction using the approved payment account. For example, POS device 106 may receive an approval from payment account manager 107 to utilize the approved payment account for facilitating the transaction. The financial transaction may proceed as is done in conventional systems, e.g., POS device 106 may finalize payment details and proceedings with payment account manager 107, e.g., based on the payment information of the approved payment account.
[0099] In some demonstrative embodiments, the PCI string may include a pseudo payment- account identifier, for example, the PCI string may be structured in compliance with a suitable payment account identifier structure, e.g., as described in detail below.
[00100] In some demonstrative embodiments, payment coordinator 104 may generate the output including a real payment-account identifier corresponding to the approved payment account, e.g., a real payment card number. [00101] In some demonstrative embodiments, one or more devices of system 100 may include one or more applications, e.g., to perform one or more of the operations described herein. For example, client device 102, payment coordinator 104, payment account manager 107 and/or POS device 106 may include a user application 122, an operator application 126, a manager application 117, and/or a POS application 124, respectively.
[00102] In some demonstrative embodiments, user application 122, operator application 126, manager application 117 and/or POS application 124 may include or utilize any suitable software and/or hardware to perform one or more of the operations described herein, for example, to generate, display, process, acknowledge and/or approve interacting messages sent between the devices of system 100 and/or to interface between the devices of system 100 and/or client 101. For example, user application 122 may include an iPhone application to enable client 101 to interact with device 102 and/or other devices of system 100, e.g., payment coordinator 104.
[00103] Reference is made to Fig. 2, which schematically illustrates a method of payment using a wireless communication device, in accordance with some demonstrative embodiments. One or more of the operations of the method of Fig. 2 may be performed by one or more elements of a system, e.g., system 100 (Fig. 1), a wireless communication device e.g., client device 102 (Fig. 1), a POS, e.g., POS device 106 (Fig. 1), a payment account manager, e.g., payment account manager 107 (Fig. 1) and/or a payment coordinator, e.g., payment coordinator 104 (Fig. 1).
[00104] As indicated at block 202, the method may include creating one or more transactions at a POS, for example, a POS device of a merchant and/or retailer, e.g., POS device 106 (Fig. 1), may calculate the amount for payment after processing one or more items to be purchased by client 101 (Fig. 1).
[00105] As indicated at block 203, the method may include receiving a unique PCI, which is sufficient to identify a mobile device associated with a user, which is to approve a transaction of monetary value with the POS.
[00106] As indicated at block 204, receiving the PCI may include receiving the PCI from the POS.
[00107] For example, POS 106 (Fig. 1) may send payment coordinator 104 (Fig. 1) one or more client details, e.g., a mobile phone number, a name and/or personal details of client 101. POS 106 (Fig. 1) may send payment coordinator 104 (Fig. 1) one or more transaction details relating to the transaction, e.g., an amount for payment, an address of the merchant, a merchant's code, a time of the transaction, and the like. [00108] As indicated at block 205, receiving the PCI may include receiving the PCI from a payment account manager. For example, POS 106 (Fig. 1) may send payment account manager 107 (Fig. 1) one or more client details, e.g., a mobile phone number, a name and/or personal details of client 101. POS 106 (Fig. 1) may send payment account manager 107 (Fig. 1) one or more transaction details relating to the transaction, e.g., an amount for payment, an code and/or address of the merchant, a merchant's code, a time of the transaction, and the like.
[00109] In some embodiments, the POS may determine client details of client 101 and/or device 102 (Fig. 1). For example, the mobile number of client 101 (Fig. 1) may be fed, for example, manually and/or reading a magnetic strip of a member card including the client's details and/or using a scanner, e.g., a barcode scanner, using a NFC link, and the like, into POS device 106 (Fig- 1).
[00110] In some demonstrative embodiments, POS device 106 (Fig. 1) may already possess one or more client details before the transaction is initiated, or during the process of creating the transaction. For example, client 101 (Fig. 1) may provide a member card and/or details of the member card to POS device 106 (Fig. 1), and POS device 106 may determine the mobile number of client 101 (Fig. 1), e.g., based on the member card and/or details of the member card.
[00111] Some demonstrative embodiments may be utilized, for example, to avoid the need for software changes in merchants' (e.g. physical, on-line and alike) software. According to these embodiments, the PCI may be provided in a structure compatible with conventional payment card detail structures. For example, the PCI may be provided to POS 106 (Fig. 1) and or transmitted from POS 106 (Fig. 1) in the form of a payment account identifier having a structure compatible with a Primary Account Number (PAN) structure, e.g., as shown in Fig. 7. The PAN structure is globally accepted by payment systems and card acquirers. As shown in Fig. 7, the payment account identifier may include a numeral string including sixteen digits, e.g., including a first set of digits, e.g., four digits, denoted "UN" identifying a code representing payment coordinator 104 (Fig. 1) and/or a payment account manager associated with payment coordinator 104 (Fig. 1); a second set of digits, e.g., 11 digits, denoted "LAI", uniquely identifying a user and/or owner of the payment account, and/or at least one check/control digit, denoted "CD".
[00112] As indicated in block 206, the method may include identifying the mobile device base don the PCI. For example, payment coordinator 104 (Fig. 1) may identify device 102 (Fig. 1), e.g., as described above.
[00113] As indicated in block 206, the method may include determining one or more payment accounts associated with the mobile device. For example, payment coordinator 104 (Fig. 1) may identify one or more payment accounts associated with client 101 (Fig. 1), for example, based on the PCI, e.g., as described above.
[00114] As indicated at block 208, the method may include determining one or more benefits based on the transaction and/or one or more of the payment accounts. For example, payment coordinator 104 (Fig. 1) may determine and/or receive from payment account manager 107 (Fig. 1) one or more benefits corresponding to the transaction and/or to each of one or more of the payment accounts.
[00115] As indicated at block 209, the method may include transmitting to the mobile device an approval request message including transaction information identifying the transaction, and payment information identifying the at least one payment account associated with the PCI to facilitate the transaction. For example, payment coordinator 104 (Fig. 1) may send client device 102 (Fig. 1) an approval request, to approve, for example, one or more details of the transaction. In some demonstrative embodiments, the approval request may include one or more payment options for payment for the transaction. The approval request may include additional details of discounts retrieved, e.g., from the payment account manager 107 (Fig. 1), applicable for each payment account for the particular transaction. For example, payment coordinator 104 (Fig. 1) may locate, e.g., based on the mobile number of client device 102 (Fig. 1), one or more possible payment methods, cards and/or options for client 101 (Fig. 1).
[00116] In some demonstrative embodiments, the one or more payment options may be stored at a central database of payment coordinator 104 (Fig. 1), payment account manager 107 (Fig. 1), and the like. For example, a "payment cards' details library" may be stored, for example, at the CRM system of a mobile operator, e.g., payment coordinator 104 (Fig. 1).
[00117] In some demonstrative embodiments, sending the request to approve the transaction may include sending a notification from payment coordinator 104 (Fig. 1) to client 101 (Fig. 1) via device 102 (Fig. 1).
[00118] In some demonstrative embodiments, the notification may include a mobile communication message, e.g., a Short Message Service (SMS) message, an Unstructured Supplementary Service Data (USSD), a Multimedia Message Service (MMS) message, and the like. In another example, the notification may include an electronic mail (E-mail) message, e.g., in accordance with the Simple Mail Transfer Protocol (SMTP), the Hyper Text Transfer Protocol (HTTP), and the like. In another example, the notification may include an Instant Message (IM), an ICQ message, an America-Online Instant Messenger (AIM) message, a Windows Live Messenger (WLM) message, a QQ message, a Skype message, an Extensible Messaging and Presence Protocol (XMPP) message, a Mobile Instant Messaging (MIM) message, an Enterprise Instant Messaging (EIM) message, an IVR message, an iPhone application and the like.
[00119] In some demonstrative embodiments, the notification, sent to device 102 (Fig. 1) may be encrypted and/or may include one or more details regarding the transaction, for example, the purchase amount and/or calculated payment amount, merchant's name and/or one or more payment options which have been retrieved, for example, from the "payment cards' details library".
[00120] As indicated at block 210, the method may include receiving an approval from the client device at the payment coordinator. For example, client 101 (Fig. 1) may select a payment option and send payment coordinator 104 (Fig. 1) via client device 102 (Fig. 1), an approval message indicating the selected option.
[00121] In some demonstrative embodiments, client 101 (Fig. 1) may select the payment option from one or more options sent by payment coordinator 104 (Fig. 1), e.g., as described below with reference to Figs. 3A, 3B, 3C, 3D, 3E and 3F.
[00122] In some demonstrative embodiments, the selected payment option may be transmitted from client device 102 (Fig. 1) together with or without a password and/or a personal security code, for example, a Personal Identification Number (PIN), e.g., as used by a card holder when performing a Automated Teller Machine (ATM) transaction. According to some embodiments, client 101 (Fig. 1) may provide the selected payment option together with or without the PIN to enhance the security of the transaction and/or avoid or diminish fraud.
[00123] In some demonstrative embodiments, the person approving the transaction, e.g., client 101 (Fig. 1), may be a different person from the person actually making the purchase and/or transaction. For example, the transaction may be approved by a parent of a child making the actual transaction. In some demonstrative embodiments, client 101 (Fig. 1) may be located at a different location than the location of the actual transaction, for example, a child may conduct a transaction at a store and the parent of the child may approve the transaction while sitting at home.
[00124] As indicated at block 212, the method may include sending encrypted or non-encrypted payment details from the payment coordinator.
[00125] As indicated at block 213, sending the payment details may include sending the payment details to the POS. For example, payment coordinator 104 (Fig. 1) may send POS device 106 (Fig. 1) the payment information corresponding to the selected payment option, e.g., a credit card number, an expiration date of the credit card number, a name of a holder of the credit card, an identification number of the holder, a PIN code associated with the credit card, and the like, and/or additional details regarding the selected payment option, e.g., passwords, security codes, details of confirmation and/or approval of the transaction.
[00126] As indicated at block 214, sending the payment details may include sending the payment details to the payment account manager. For example, payment coordinator 104 (Fig. 1) may send payment account manager 107 (Fig. 1) the payment information corresponding to the selected payment option, e.g., a credit card number, an expiration date of the credit card number, a name of a holder of the credit card, an identification number of the holder, a PIN code associated with the credit card, and the like, and/or additional details regarding the selected payment option, e.g., passwords, security codes, details of confirmation and/or approval of the transaction. Payment account manager 107 (Fig. 1) may receive the client's card details, complete the approval process of the payment and may send POS 106 (Fig. 1) an approval of the payment for completing the sale transaction and provide the customer with a receipt for payment.
[00127] As indicated at block 216, the method may include executing the transaction at the POS, e.g., by processing the transaction between POS device and card provider. For example, POS device 106 (Fig. 1) may transfer the payment information of the selected payment option and/or one or more of the additional details to a card provider, e.g., payment account manager 107 (Fig. 1); and/or receive authorization from payment account manager 107 for the transaction, e.g., in order to provide the customer, e.g., client 101 (Fig. 1), with a receipt for payment.
[00128] In one example, client 101 (Fig. 1) may purchase one or more products at a store. Upon processing a transaction corresponding to the products, POS device 106 (Fig. 1), e.g., the cashier at the store, calculates the amount for payment for the one or more products. Client 101 (Fig. 1) may possess a blackberry mobile device operated by payment coordinator 104, e.g., Globalstar. Client 101 (Fig. 1) may provide the mobile phone number of the blackberry device to POS device 106 (Fig. 1), for example, by manually entering the number into POS device 106 (Fig. 1), via a NFC link, and/or in any other suitable manner. POS device 106 (Fig. 1) may send the phone number to payment coordinator 104 (Fig. 1), e.g., the CRM of Globalstar, which may access a database to retrieve payment options for client 101 (Fig. 1). Payment coordinator 104 (Fig. 1) may send client 101 (Fig. 1) an MMS message with one or more options for payment and a request to enter a PIN code corresponding to a payment option selected by client 101 (Fig. 1). Client 101 (Fig. 1) may select the preferred option for payment, e.g., payment via a Diners credit card held by client 101 (Fig. 1), and may enter the PIN code corresponding to the selected payment option. Client device 102 (Fig. 1) may send back a message to payment coordinator 104 (Fig. 1) indicating the selected option and PIN code. Payment coordinator 104 (Fig. 1) may then provide POS device 106 (Fig. 1) with the payment details of the selected option for payment and any other required information, e.g., a number of the Diners card, an expiration date of the Diners card, PIN code, a name of client 101 (Fig. 1), and the like. POS device 106 (Fig. 1) may complete the transaction by contacting payment account manager 107 (Fig. 1), e.g., the Diners company, and providing the Diners company with the Diners card number and optionally the card's PIN code for client 101 (Fig. 1) and any suitable additional details.
[00129] Reference is now made to Figs. 3A, 3B, 3C, 3D, 3E and 3F which include exemplary mobile device screen shots, in accordance with some demonstrative embodiments.
[00130] In some demonstrative embodiments, Figs. 3 A, 3B and 3C may demonstrate exemplary outputs presented to client 101 (Fig. 1) by output 114 (Fig. 1).
[00131] In some demonstrative embodiments, Fig. 3 A demonstrates an MMS option (also referred to herein as "payment MMS"), for example, sent by payment coordinator 104 (Fig. 1), e.g., to be received by client device 102 (Fig. 1).
[00132] In some demonstrative embodiments, Fig 3D, 3E and 3F demonstrate SMS options (also referred to herein as "payment MMS"), for example, sent by payment coordinator 104 (Fig. 1), e.g., to be received by client device 102 (Fig. 1), including discounts information for the specific purchase by the specific cards.
[00133] In some demonstrative embodiments, the payment MMS may include one or more payment options, e.g., by displaying different images of one or more credit cards, and/or include one or more fields for entering a security password and/or code, e.g., the PIN corresponding to a selected card.
[00134] In some demonstrative embodiments, upon receiving a payment MMS from the mobile operator, client 101 (Fig. 1) may use one or more scroll options, e.g., Up-Down-Left-Right functions, of input 112 (Fig. 1), e.g., a mobile device keyboard (physical or soft touch), to select the desired payments card's symbol.
[00135] In some demonstrative embodiments, client 101 (Fig. 1) may also enter the appropriate PIN number of the selected card and/or reply to the mobile operator, e.g., payment coordinator 104 (Fig. 1). In some demonstrative embodiments, device 102 (Fig. 1) may transmit the selection and/or PIN number to the mobile operator by sending one or more messages, e.g., SMS and/or MMS messages.
[00136] According to other embodiments, when interactive MMS is not available, client 101 (Fig. 1) may choose a reply function, e.g., by entering the number of the selected card and next to it the PIN number and send a response to the mobile operator, e.g., payment coordinator 104 (Fig- 1). [00137] Fig. 3B demonstrates an SMS option (also referred to herein as "payment SMS"), for example, sent by payment coordinator 104 (Fig. 1) e.g., to be received by client device 102 (Fig.
1).
[00138] In some demonstrative embodiments, the payment SMS may include one or more payment options, e.g., by displaying different textual descriptions of one or more credit card options, and/or include one or more fields for entering a security password and/or code, e.g., the PIN.
[00139] In some demonstrative embodiments, upon receiving a notification, e.g., payment SMS, from the mobile operator, e.g., payment coordinator 104 (Fig. 1), client 101 (Fig. 1) may choose the desired payment card's text; and/or may enter the appropriate PIN number of the selected card. In some demonstrative embodiments, device 102 (Fig. 1) may transmit the selection and/or PIN number to the mobile operator by sending one or more messages, e.g., SMS and/or MMS messages.
[00140] According to other embodiments, when interactive SMS is not available, client 101 (Fig. 1) may choose a reply function, e.g., by entering the number of the selected card and next to it the PIN number and send a response to the mobile operator, e.g., payment coordinator 104 (Fig- 1).
[00141] Reference is made to Fig. 4, which schematically illustrates an article of manufacture 400, in accordance with some demonstrative embodiments. Article 400 may include a machine - readable storage medium 402 to store logic 404, which may be used, for example, to perform at least part of the functionality of client device 102 (Fig. 1), POS device 106 (Fig. 1), payment coordinator 104 (Fig. 1); and/or to perform one or more operations of the method of Fig. 2.
[00142] In some demonstrative embodiments, article 400 and/or machine -readable storage medium 402 may include one or more types of computer-readable storage media capable of storing data, including volatile memory, non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and the like. For example, machine -readable storage medium 402 may include, RAM, DRAM, Double-Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), Compact Disk ROM (CD-ROM), Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), flash memory (e.g., NOR or NAND flash memory), content addressable memory (CAM), polymer memory, phase-change memory, ferroelectric memory, silicon-oxide-nitride- oxide-silicon (SONOS) memory, a disk, a floppy disk, a hard drive, an optical disk, a magnetic disk, a card, a magnetic card, an optical card, a tape, a cassette, and the like. The computer- readable storage media may include any suitable media involved with downloading or transferring a computer program from a remote computer to a requesting computer carried by data signals embodied in a carrier wave or other propagation medium through a communication link, e.g., a modem, radio or network connection.
[00143] In some demonstrative embodiments, logic 404 may include instructions, data, and/or code, which, if executed by a machine, may cause the machine to perform a method, process and/or operations as described herein. The machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware, software, firmware, and the like.
[00144] In some demonstrative embodiments, logic 404 may include, or may be implemented as, software, a software module, an application, a program, a subroutine, instructions, an instruction set, computing code, words, values, symbols, and the like. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. The instructions may be implemented according to a predefined computer language, manner or syntax, for instructing a processor to perform a certain function. The instructions may be implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language, such as C, C++, Java, BASIC, Matlab, Pascal, Visual BASIC, assembly language, machine code, and the like.
[00145] Reference is now made to Fig. 5, which schematically illustrates a first payment process, in accordance with some demonstrative embodiments.
[00146] As demonstrated in Fig. 5, upon completing the retrieval of the goods into the POS of the merchant (1), instead of providing a payment card for scan, the consumer provides a PCI, e.g., his mobile telephone number (2) (3), The PCI is entered to the POS either manually or automatically by barcode scanning, NFC, and the like (4). The POS generates a transaction containing the merchant code, consumer's PCI and purchase amount (5), and transmits it online to a payment coordinator (6). Upon receiving the transaction by the payment coordinator, the payment coordinator automatically retrieves the payment option/s from the consumer/subscriber's record, searches the discount database for payment cards discounts applicable for the merchant and generates a message including the purchase amount, merchant name and all payments options which have been located in "payment cards' details library" at the subscriber's record (7). The payment coordinator may include, or may be implemented as part of, for example a mobile operator, a web service provider, and the like, e.g., a described above. The payment coordinator then generates a message including all details and discounts and sends it to the consumer's mobile device (8). The consumer receives the message, e.g., as demonstrated in Figs. 3A, 3B, 3C, 3D, 3E and 3F above (9), selects the payment method he wants to use for the purchase, optionally enters his PIN and replies (10). A message is then transmitted, to the payment coordinator (11). Upon receiving the reply, the payment coordinator automatically generates a transaction that contains the details of the selected payment method and the PIN (12), and transmits the transaction back to the sending POS (13). Upon receiving the transmission, the POS transfers the account details, PIN and amount to the appropriate payment provider's system (same as it does after scanning a card) (14), continues with the payment processing same as if card was scanned (15) and provides the Consumer with an invoice/receipt upon process completion. In some demonstrative embodiments, steps (1) and (15) may exist in all POS systems. Steps (2) - (14) may replace the cards scanning or manually card details entry existing procedures.
[00147] Reference is now made to Fig. 6, which schematically illustrates a second payment process, in accordance with some demonstrative embodiments.
[00148] As demonstrated in Fig. 6, upon completing the retrieval of the goods into the POS of the merchant (1), instead of providing a payment card for scan, the consumer provides his PCI, e.g., in the form of a mobile telephone number and a payment manager code or a member card with the PAN of Fig. 7 (2) (3), the POS either selects a mobile payment function, or may avoid this step, e.g., if the mobile payment's PAN exists (4). The client's mobile details are entered to the POS either manually or automatically by barcode scanning, or by scanning the magnetic strip of the consumer's member card or by using NFC device, and the alike (5). The POS generates a payment transaction containing the PCI, e.g., in a standard structure of a payment transaction including PCI, a merchant code, and purchase amount, and transmits it online to a card acquirer for payment approval (6). Card acquirer recognizes the mobile payment transaction (7), identifies transaction destination and sends it to the payment coordinator (8). Upon receiving the transaction by the payment coordinator, the payment coordinator automatically retrieves the payment option/s from the consumer/subscriber's record, searches the discount database for payment cards discounts applicable for the merchant (9) and generates a message including the purchase amount, merchant name and all payments options which have been located in "payment cards' details library" at the subscriber's record and the related discounts. The payment coordinator then transmits the message to the consumer's mobile device (11). The consumer receives the message (12), e.g., as demonstrated in Figs. 3A, 3B, 3C, 3D, 3E and 3F above, selects the payment method he wants to use for the purchase, optionally enters his PIN if required, and replies (13). The response message is then transmitted, to the payment coordinator (14). Upon receiving the reply, the payment coordinator automatically generates (15) a transaction that contains the details of the selected payment method and optionally the PIN, and transmits the transaction back to the sending card acquirer (16). Upon receiving the transmission, the card acquirer performs transaction validation and approval process with the card issuer (in some instances the transaction validation and approval process will be completed directly between the payment coordinator and the payment manager) (17) and sends to the POS an approval/denial (same as when scanning an ordinary credit card) (18), and then the POS continues with the payment processing, e.g., in the same manner as if a conventional payment card was used (19) and provides the consumer with an invoice/receipt upon process completion.
[00149] Reference is now made to Fig. 8, which schematically illustrates a process of approving a transaction using a mobile device, in accordance with some demonstrative embodiments. As shown in Fig. 8, a PCI may be utilized to facilitate approval of a payment account for facilitating a monetary transaction between a POS and a consumer.
[00150] As shown in Fig. 8, the PCI may optionally be provided to the POS by the consumer (1). Alternatively, the PCI may be determined by the POS based on any suitable information corresponding to the consumer, e.g., based on a customer number, and the like, as described above.
[00151] As shown in Fig. 8, the POS may request approval for the transaction using the PCI (2), e.g., in the form of a pseudo payment account identifier. In one example, the POS may transmit the PCI to a payment account manager, e.g., in a similar manner to transmitting a conventional payment account number. For example, the PCI may have a structure compatible with a conventional PAN structure. In another example, the POS may transmit the PCI to a payment coordinator, e.g., as described above.
[00152] As shown in Fig. 8, the consumer may receive a request message, via a mobile device of the consumer, requesting the consumer to select and approve a payment account to facilitate the transaction. For example, payment coordinator 104 (Fig. 1) may transmit the request message to device 102 (Fig. 1), e.g., as described above.
[00153] As shown in Fig. 8, the consumer may respond with an approved payment account. For example, client 101 (Fig. 1) may use input 112 (Fig. 1) to approve a payment account of the one or more payment accounts indicated by the request message, and device 102 (Fig. 1) may transmit an approval message indicating the approved payment account, e.g., as described above.
[00154] As sown in Fig. 8, the POS may receive a payment confirmation with real payment account details identifying the approved payment account. For example, payment controller 104 (Fig. 1) and/or payment account manger 107 (Fig 1) may provide the payment account details to POS 106 (Fig. 1), e.g., as described above.
[00155] Functions, operations, components and/or features described herein with reference to one or more embodiments, may be combined with, or may be utilized in combination with, one or more other functions, operations, components and/or features described herein with reference to one or more other embodiments, or vice versa.
[00156] While certain features of the invention have been illustrated and described herein, many modifications, substitutions, changes, and equivalents may occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the invention.
Next Patent: LAP FORMING DEVICE FOR A LAP-WINDER