Smart node to node payment systems

Abstract

Methods for smartwatch-to-smartwatch payment systems is provided. Methods include receiving a transfer of funds initiation at a first smartwatch. The transfer of funds initiation may include an identifier, an amount and a personal identification number (“PIN”). Methods include transmitting the transfer of funds initiation from the first smartwatch to a second smartwatch. Methods may include receiving a notification on the second smartwatch. The notification may include a first smartwatch telephone number and the transfer of funds initiation. Methods may include transmitting a transfer of funds request from the second smartwatch to an entity. The transfer of funds request may include the first smartwatch telephone number, the transfer of funds initiation and the second smartwatch telephone number. Methods may include retrieving a first account and a second account from the entity. Methods may include transferring funds from the first account to the second account.

Claims

1. A method for smartwatch-to-smartwatch transactions, the method comprising: generating a transaction initiation at a first smartwatch; triggering, by the transaction initiation, transmission, from the first smartwatch to a second smartwatch, a request for a second smartwatch telephone number, said second smartwatch telephone number associated with the second smartwatch; transmitting, from the second smartwatch to the first smartwatch, the second smartwatch telephone number; requesting a transaction amount and a personal identification number at the first smartwatch; receiving, at the first smartwatch, the transaction amount and the personal identification number via tap gestures to one or more portions of the first smartwatch, said tap gestures including receiving a series of taps, each series of taps corresponds to a numerical value, each series of taps being separated from another series of taps with a delimiter; generating a transaction request at the first smartwatch, said transaction request comprising: a first smartwatch telephone number, said first smartwatch telephone number associated with the first smartwatch; the second smartwatch telephone number; the transaction amount; and the personal identification number; transmitting the transaction request to a processing entity; processing the transaction request at the processing entity; and receiving, at the first smartwatch and at the second smartwatch, a transaction confirmation from the entity.

2. The method of claim 1, wherein: the first smartwatch comprises a first near field communication (“NFC”) component; the second smartwatch comprises a second NFC component; and the first smartwatch and the second smartwatch communicate with each other via the first NFC component and the second NFC component.

3. A method for smartwatch-to-smartwatch transactions, the method comprising: generating a transaction initiation at a first smartwatch; triggering, by the transaction initiation, transmission, from the first smartwatch to a second smartwatch, a request for a second smartwatch telephone number, said second smartwatch telephone number associated with the second smartwatch; transmitting, from the second smartwatch to the first smartwatch, the second smartwatch telephone number; transmitting the second smartwatch telephone number, from the first smartwatch to an entity; receiving at the first smartwatch, an account number associated with the second smartwatch telephone number; requesting a transaction amount and a personal identification number at the first smartwatch; receiving, at the first smartwatch, entry of the transaction amount; receiving, at the first smartwatch, entry of the personal identification number via a touch-based musical pattern, the touch-based musical pattern includes a user tapping the touch screen with a predetermined number of fingers a predetermined number of times; generating a transaction request at the first smartwatch, said transaction request comprising: an account associated with a first smartwatch telephone number; the account associated with the second smartwatch telephone number; the transaction amount; and the personal identification number; transmitting the transaction request to the entity; processing the transaction request at the entity; receiving, at the first smartwatch and at the second smartwatch, a transaction confirmation from the entity.

4. The method of claim 3, wherein: the first smartwatch comprises a first near field communication (“NFC”) component; the second smartwatch comprises a second NFC component; and the first NFC component and the second NFC component execute the transmissions between the first smartwatch and the second smartwatch.

5. The method of claim 3, wherein the transaction is a transfer of funds transaction.

6. The method of claim 5, wherein: a beneficiary of the transfer of funds transaction is the account associated with the second smartwatch telephone number; and a benefactor of the transfer of funds transaction is the account associated with the first smartwatch telephone number.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) The objects and advantages of the invention will be apparent upon consideration of the following detailed description, taken in conjunction with the accompanying drawings, in which like reference characters refer to like parts throughout, and in which:

(2) FIG. 1 shows an illustrative diagram in accordance with principles of the disclosure;

(3) FIG. 2 shows another illustrative diagram in accordance with principles of the disclosure;

(4) FIG. 3 shows yet another illustrative diagram in accordance with principles of the disclosure;

(5) FIG. 4 shows still another illustrative diagram in accordance with principles of the disclosure; and

(6) FIG. 5 shows still yet another illustrative diagram in accordance with principles of the disclosure.

DETAILED DESCRIPTION OF THE DISCLOSURE

(7) Apparatus and methods for smartwatch-to-smartwatch payment systems is provided.

(8) A smartwatch may include a plurality of hardware components and software components, such as those described in detail in the summary of the disclosure. The hardware components may include a watch face and a band. The watch face may rest on a user's wrist. The band may wrap around the user's wrist and secure the watch face relative to the user's wrist.

(9) The hardware components may also include one or more microprocessors. At least one of the microprocessors may be operable to initiate a transaction.

(10) The hardware components may also include one or more displays. At least one of the displays may display software displays. The microprocessor may instruct the display regarding the software displays.

(11) The hardware components may also include a battery. The battery may power the display and/or the microprocessor.

(12) The hardware components may also include a nano wireless network interface card (“NIC”). The nano wireless NIC may establish communication with a wireless network.

(13) The hardware components may also include an active NFC reader. The active NFC reader may detect one or more other smartwatches within a predetermined proximity to the smartwatch. The active NFC reader may establish communication with the one or more other smartwatches.

(14) The smartwatch may also include a plurality of software components.

(15) The plurality of software components may include a digital number pad. The digital number pad may display numerical digital software selections to the user. The digital number pad may also receive numerical input from the user. In some embodiments, the digital number pad may not operate as a typical digital number pad. For example, the digital number pad may accept tap gesture input and/or musical patterns that correspond to one or more numerals.

(16) The plurality of software components may also include an information controller module. The information controller module may capture data via the digital number pad. The captured data may include a transaction amount and/or a PIN. As such, the received numerical input may correspond to the transaction amount and/or the PIN.

(17) The plurality of software components may also include an NFC controller module. The NFC controller module may operate as the software for the active NFC reader. As such, the NFC controller module may activate NFC communication via the NFC reader.

(18) The NFC controller module may also send and/or receive user data, payment data and/or authentication data. As such, the NFC controller module may receive the captured data from the information controller module. The captured data may include the transaction amount and/or the PIN. The NFC controller module may transmit the captured data to a wireless controller module.

(19) The NFC controller module may communicate with the one or more other smartwatches. As such, the NFC controller module may communicate with a second smartwatch. The second smartwatch may be one of the one or more other smartwatches. The communication from the smartwatch to the second smartwatch may include a request for a second smartwatch mobile telephone number.

(20) The NFC controller module may receive the second smartwatch mobile telephone number from the second smartwatch.

(21) The plurality of software components may also include the wireless controller module. The wireless controller module may interface between the nano wireless NIC and an external Wi-Fi device. The external Wi-Fi device may be included in the wireless network. The Wi-Fi device may be within sufficient proximity to the smartwatch to communicate with the software and hardware components included in the Wi-Fi device.

(22) The wireless controller module may also transmit the captured data to an external entity. The transmission of the captured data may be communicated over the wireless network.

(23) The NFC controller module and/or the wireless controller module may include multiple modes. The modes may include discoverable mode and non-discoverable mode. In a discoverable mode, the smartwatch may be actively searching for other devices. In a non-discoverable mode, the smartwatch may not be actively searching for devices.

(24) The plurality of software components may also include a telephone number to account number resolver module. In such embodiments, the telephone number to account number resolver module may be internal to the smartwatch. The telephone number to account number resolver module may receive a telephone number from the NFC controller module.

(25) The telephone number to account number resolver module may communicate with the external entity and/or internal storage location to identify an account number associated with a received telephone number. The telephone number may be a mobile telephone number.

(26) The mobile telephone number may be associated with one of the one or more other smartwatches. The mobile telephone number may be associated with the second smartwatch. As such, the telephone number to account number resolver module may identify an account number associated with the mobile telephone number associated with the second smartwatch.

(27) In some embodiments, the smartwatch may be associated with multiple mobile telephone numbers. The multiple mobile telephone numbers may be stored in a storage location included in the smartwatch. The smartwatch may also be associated with multiple account numbers. In certain embodiments, each telephone number may be associated with an account number. As such, in order to generate a transaction, the wearer of the smartwatch may select a telephone number. The telephone number to account number resolver module may identify the account number associated with the selected telephone number. As such, the telephone number to account number resolver module may identify the account number associated with the smartwatch.

(28) The plurality of software components may also include an amount and PIN verification module. The amount and PIN verification module may verify the transaction amount and/or the PIN with the external entity.

(29) As stated above, the microprocessor, included in the smartwatch, may initiate a transaction. The microprocessor may generate a transaction request. The transaction request may be a transfer of funds instruction. A benefactor account of the transaction request may be the account associated with the telephone number of the initiating smartwatch. A beneficiary account of the transaction request may be the account associated with the second smartwatch mobile telephone number.

(30) The transaction request may include an account number associated with the initiating smartwatch. The transaction request may include the transaction amount. The transaction request may include the PIN. The transaction request may include the smartwatch account number associated with the second smartwatch mobile telephone number.

(31) The microprocessor may transmit the generated transaction request to the entity. The entity may process the transaction request.

(32) Upon completion of processing the transaction request at the entity, the entity may transmit a confirmation to the initiating smartwatch and/or to the second smartwatch. The confirmation(s) may notify regarding the completion of the transaction request processing.

(33) The confirmations may also include details relating to the transaction. Such details may include one or more account numbers and/or a portion of one or more account numbers. Such details may also include a transaction amount. Such details may also include a date-time stamp.

(34) At times, a smartwatch may be unable to connect to a wireless network, such as the internet. As such, one or more smartwatches involved in a transaction may communicate with one another using NFC, Bluetooth® or another suitable technology. The transaction may be completed offline—i.e., without communicating with a wireless network. The transaction data may be stored within the smartwatches. The transaction data may include the following: user information (may be the benefactor and/or beneficiary), transaction amount, counterparty user information (may be the benefactor and/or beneficiary), authentication information, location information, past payment information, past purchase information and any other suitable information. The transaction data may be stored in a blockchain using an immutable cryptographic signature which cannot be altered. When one or both of the smartwatches are reconnected to a network, the transactions can be picked from the blockchain and forwarded for processing at one or more financial institutions.

(35) In some embodiments, in order to facilitate smartwatch to smartwatch transactions, currency may be stored on the smartwatch. For example, digital currency can be stored in currency form on the smartwatch for offline, or online, transactions.

(36) Apparatus and methods described herein are illustrative. Apparatus and methods in accordance with this disclosure will now be described in connection with the figures, which form a part hereof. The figures show illustrative features of apparatus and method steps in accordance with the principles of this disclosure. It is to be understood that other embodiments may be utilized and that structural, functional and procedural modifications may be made without departing from the scope and spirit of the present disclosure.

(37) The steps of methods may be performed in an order other than the order shown or described herein. Embodiments may omit steps shown or described in connection with illustrative methods. Embodiments may include steps that are neither shown nor described in connection with illustrative methods.

(38) Illustrative method steps may be combined. For example, an illustrative method may include steps shown in connection with another illustrative method.

(39) Apparatus may omit features shown or described in connection with illustrative apparatus. Embodiments may include features that are neither shown nor described in connection with the illustrative apparatus. Features of illustrative apparatus may be combined. For example, an illustrative embodiment may include features shown in connection with another illustrative embodiment.

(40) FIG. 1 shows an illustrative diagram. The illustrative diagram shows smartwatch-to-smartwatch communication. Smartwatch 104 may be worn by user 102. Smartwatch 110 may be worn by user 108. Smartwatch 104 and 110 may include capabilities such as those described above. Smartwatch 104 and smartwatch 110 may communicate with each other, as shown at communication 106. The communication may be an NFC-based communication. The communication may be a Wi-Fi-based communication. The communication may utilize any other suitable technology.

(41) FIG. 2 shows an illustrative diagram. The illustrative diagram shows communication between a first smartwatch (smartwatch A), shown at 202, a second smartwatch (smartwatch B), shown at 204 and a plurality of financial institutions, shown at 206. The communications included in FIG. 2 show retrieving account data associated with another smartwatch's mobile telephone number.

(42) It should be appreciated that the communications between smartwatch A and smartwatch B may be NFC-enabled or Bluetooth®-enabled communications. It should be further appreciated that the communications between smartwatch B and financial institutions 206 may be Wi-Fi®-enabled communications.

(43) Smartwatch A may be associated with mobile telephone number XXX-XXX-0023. Smartwatch B may be associated with mobile telephone number XXX-XXX-6789 (not shown).

(44) Step 1 of an exemplary communication is shown at 208. Step 1 may include initiation of a communication. The communication may be an NFC-enabled communication. The communication may be a payment communication. The payment communication may be transmitted from smartwatch A to smartwatch B and/or from smartwatch B to smartwatch A. In some embodiments, the initial communication between smartwatch A and smartwatch B may be a handshake communication.

(45) The communication may include a transfer of funds instruction. The intent of the transfer of funds instruction may be to transfer funds from an account associated with smartwatch A to an account associated with smartwatch B. Each account may be linked to its respective smartwatch via the associated mobile telephone number. The payment communication that is transferred from smartwatch A to smartwatch B may include the mobile telephone number associated with smartwatch A.

(46) Step 2 of the exemplary communication is shown at 210. In response to receiving the payment communication, smartwatch A may transmit its associated mobile telephone number to smartwatch B. The smartwatch A mobile telephone number may be received at the phone to bank resolver module within smartwatch B.

(47) Step 3 of the exemplary communication is shown at 212. The phone to bank resolver module may communicate with each financial institution included in plurality of financial institutions 206. The communication may include attempting to identify account data associated with the smartwatch A mobile phone number. The phone to bank resolver may transmit the smartwatch A mobile phone number to each financial institution included in plurality of financial institutions 206. The response from each financial institution 206 may include either account data or a null response.

(48) Financial institutions that do not have account data associated with the transmitted phone number may transmit null responses. In some embodiments, null responses may not be transmitted to smartwatch B. Rather, only responses with account data may be transmitted to the phone to bank resolver module.

(49) Step 4 of the exemplary communication is shown at 214. The response, including the account data, may be received at the phone to bank resolver module. The phone to bank resolver module may link the received account data to the mobile phone number associated with smartwatch A.

(50) FIG. 3 shows an illustrative diagram. The illustrative diagram shows a completion of a transaction between smartwatch A, shown at 302, and smartwatch B, shown at 304 and financial institutions, shown at 306. It should be appreciated that the steps (1-12) shown in FIG. 3 commence after the smartwatch A account data was transmitted to smartwatch B.

(51) Step 1 shows that the smartwatch A account data is stored in local memory of smartwatch B. The local memory may be any suitable memory included in the smartwatch.

(52) Step 2 shows that smartwatch B may prompt, via NFC communication, smartwatch A to request user entry of PIN.

(53) Step 3 shows smartwatch A request user entry of a PIN. The request may be presented to the user of smartwatch A. As such, the user of smartwatch A may authenticate the transaction by entering the PIN.

(54) Step 4 shows smartwatch A receiving PIN entry from the user. It should be appreciated that the PIN may be entered via tap gestures or musical pattern gestures.

(55) The tap gestures may be received at one or more portions of the smartwatch. Tap gestures may include receiving a series of taps. Each series of taps may correspond to a different value, such as a numerical value. Each series of taps may be separated from another series of taps with a delimiter.

(56) A user of the smartwatch may enter a PIN using tap gestures. The numerical value of the PIN may be 6543. As such, the user of the smartwatch may tap six times, enter a delimiter, tap five times, enter a delimiter, tap four times, enter a delimiter and tap three times.

(57) Examples of delimiters may include pausing for a predetermined time period, swiping, squeezing, holding a tap for a predetermined time period and any other suitable delimiter.

(58) A touch-based musical pattern may include a user, of the smartwatch, tapping the touch screen with a predetermined number of fingers for a predetermined number of times. It should be appreciated that each tap may utilize a different number of fingers. For example, a musical pattern may include a two finger tap three times followed by a one finger tap two times followed by a four finger tap one time. As such, the PIN may not be a numerical PIN, rather a touch-based musical pattern PIN.

(59) Step 5 shows smartwatch A transmits the received PIN to smartwatch B.

(60) Step 6-10 are included in a transaction initiation module being executed on smartwatch B. Step 6 shows that the transaction initiation module may link the received PIN from smartwatch A to the smartwatch A account data.

(61) Step 7 shows that the transaction initiation module may prompt the smartwatch B user for an amount of the transaction and a PIN associated with a smartwatch B account data. It should be appreciated that the smartwatch B account data may be stored on local memory included in smartwatch B.

(62) Step 8 shows that the transaction initiation module may link the PIN, entered by the smartwatch B user, to the smartwatch B account data.

(63) Step 9 shows that the transaction initiation module may generate a payment instruction. The payment instruction may be a payment instruction shown at 308. The payment instruction may include a benefactor account, such as smartwatch A account. The payment instruction may also include a PIN associated with the smartwatch A account. The payment instruction may include a beneficiary account, such as smartwatch B account. The payment instruction may also include a PIN associated with the smartwatch B account. The payment instruction may include an amount of the transaction.

(64) It should be appreciated that although FIG. 3 shows smartwatch A as the benefactor and smartwatch B as the beneficiary, in other embodiments, the payment instruction may include smartwatch A as the beneficiary and smartwatch B as the benefactor.

(65) Step 10 shows that the transaction initiation module may transmit the generated payment instruction to one or more financial institutions included in the plurality of financial institutions, shown at 306. The one or more financial institutions may be associated with the smartwatch A account and/or the smartwatch B account. In some instances, the payment instruction may be transmitted to a financial institution associated with both the smartwatch A account and the smartwatch B account. In other instances, the payment instruction may be transmitted to both a financial institution associated with the smartwatch A account and a financial institution associated with the smartwatch B account. In yet other instances, the payment instruction may be transmitted to either a financial institution associated with the smartwatch A account or a financial institution associated with the smartwatch B account. In such instances, the financial institution that receives the payment instruction may communicate with a financial institution that did not receive the payment instruction.

(66) Step 11 shows that the transaction is completed between the one or more involved financial institutions. Step 12 shows that, once the transaction is completed, an alert indicating the completion of the transaction is transmitted to both smartwatch A and smartwatch B.

(67) FIG. 4 shows an exemplary diagram. The exemplary diagram includes a portion of the exemplary components included in smartwatch 402. The components may include two sets of components, hardware components, shown at 404 and software components, shown at 416.

(68) Hardware components may include component A, a battery, shown at 408. The battery may power other components of the smartwatch, such as the display and the microprocessor.

(69) Hardware components may include component B, a microprocessor, shown at 406. The microprocessor may execute the processes within the smartwatch. The microprocessor may also initiate transactions.

(70) Hardware components may include component C, shown at 410, a nano wireless NIC. The nano wireless NIC may establish communication between the smartwatch and a nearby wireless network. The wireless network may enable the smartwatch to communicate with a financial institution.

(71) Hardware components may include component D, shown at 414, an active NFC reader. The active NFC reader may detect the proximity of other smartwatches. The active NFC reader may establish communication between the smartwatch and the other smartwatches.

(72) Hardware components may include component E, shown at 412, a display. The display may display software-based displays to the user.

(73) Software components, shown at 416, may include a telephone number to account number resolver module. The telephone number to account number resolver module may communicate with the financial institution to identify an account number associated with a telephone number.

(74) Software components may include an amount and PIN verification module. The amount and PIN verification module may verify the amount of the transaction and the PIN with the financial institution.

(75) Software components may include a digital number pad module. The digital number pad module may display a digital number pad to the smartwatch user. The digital number pad module may also receive user input.

(76) In some embodiments, the digital number pad may include selectable numbers. In other embodiments, the digital number pad may appear as an empty entry screen. An empty entry screen may accept tap gestures or a musical pattern, such as those described above.

(77) In some embodiments, the digital number pad may accept scripted numbers as user input. The user input may be entered via a stylus, finger or other suitable input medium.

(78) Software components may include an NFC controller module. The NFC controller module may activate NFC with the active NFC reader. The NFC controller module may send and/or receive user data, payment data and/or authentication data.

(79) Software components may include an information controller module. The information controller module may capture amount and PIN information from the user.

(80) Software components may include a wireless controller module. The wireless controller module may interface between the nano wireless NIC and an external Wi-Fi device.

(81) FIG. 5 shows a payment system where funds can be transferred from an account associated with a first smartwatch (502) to an account associated with a second smartwatch (504).

(82) Smartwatch 502 may include microprocessor 522. Battery 528 may power microprocessor 522. Microprocessor 522 may initiate a transaction.

(83) Smartwatch 502 may also include digital number pad 524. Digital number pad 524 may be displayed on display 526. Digital number 524 pad may receive numerical user input. The numerical user input may be received in tap gestures, touch gestures, musical patterns or any other suitable user input.

(84) Smartwatch 502 may also include nano wireless NIC card 516. Nano wireless NIC card 516 may be responsible for establishing communication with a nearby wireless network.

(85) Smartwatch 502 may also include an active NFC reader 512. NFC reader 512 may detect smartwatches in a predetermined vicinity. NFC reader 512 may establish communication with the detected smartwatch, such as smartwatch 504.

(86) Smartwatch 502 may also include a telephone number to account number resolver 518. Telephone number to account number resolver 518 may identify financial institution account information associated with a telephone number.

(87) Telephone number to account number resolver 518 may communicate with an entity, such as a financial institution. The financial institution may store account information. The financial institution may process transactions.

(88) Smartwatch 502 may also include an amount and PIN verification module 520. Amount and PIN verification module 520 may capture user input relating to an amount and a PIN. Amount and PIN verification module 520 may capture the tap-gesture-based user input.

(89) Active NFC reader 512 may communicate with NFC controller 510. NFC controller 510 may activate NFC communication. NFC controller 510 may send and receive a user's payment and authentication data.

(90) Smartwatch 502 may also include information controller 508. Information controller 508 may communicate with amount and PIN verification module 520. Information controller 508 may capture amount and PIN information. Information controller 508 may transfer the captured amount and PIN information to NFC controller 510.

(91) NFC controller 510 and nano wireless NIC card 516 may communicate with wireless controller 514. Wireless controller 514 may communicate with external Wi-Fi device 506.

(92) Wireless controller 514 may communicate with microprocessor 522. Microprocessor 522 may communicate with a receiver's financial institution 530 and a sender's financial institution 532.

(93) Thus, smartwatch-to-smartwatch payment systems are provided. Persons skilled in the art will appreciate that the present invention can be practiced by other than the described embodiments, which are presented for purposes of illustration rather than of limitation. The present invention is limited only by the claims that follow.