WO2012051071A1 - Méthode de paiement avec un service de paiement et des onglets sélectionnés par une première partie et ouverts par une seconde partie à n'importe quel emplacement géographique du dispositif mobile de la première partie - Google Patents

Méthode de paiement avec un service de paiement et des onglets sélectionnés par une première partie et ouverts par une seconde partie à n'importe quel emplacement géographique du dispositif mobile de la première partie Download PDF

Info

Publication number
WO2012051071A1
WO2012051071A1 PCT/US2011/055387 US2011055387W WO2012051071A1 WO 2012051071 A1 WO2012051071 A1 WO 2012051071A1 US 2011055387 W US2011055387 W US 2011055387W WO 2012051071 A1 WO2012051071 A1 WO 2012051071A1
Authority
WO
WIPO (PCT)
Prior art keywords
party
mobile device
card
financial transaction
qualified
Prior art date
Application number
PCT/US2011/055387
Other languages
English (en)
Inventor
Jack Dorsey
William Henderson
Brian Grassadonia
James M. Mckelvey
Original Assignee
Square, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US12/903,753 external-priority patent/US20110084139A1/en
Priority claimed from US12/985,982 external-priority patent/US8573486B2/en
Priority claimed from US13/005,822 external-priority patent/US8870070B2/en
Priority claimed from US13/010,976 external-priority patent/US9016572B2/en
Priority claimed from US13/012,495 external-priority patent/US8500018B2/en
Priority claimed from US13/043,203 external-priority patent/US8573487B2/en
Priority claimed from US13/043,268 external-priority patent/US8302860B2/en
Priority claimed from US13/043,263 external-priority patent/US8876003B2/en
Priority claimed from US13/043,270 external-priority patent/US8235287B2/en
Priority claimed from US13/043,258 external-priority patent/US8870071B2/en
Priority claimed from US13/088,038 external-priority patent/US9619797B2/en
Priority to EP11833173.5A priority Critical patent/EP2628140A4/fr
Priority to JP2013533898A priority patent/JP2014500537A/ja
Priority to CA2812611A priority patent/CA2812611C/fr
Application filed by Square, Inc. filed Critical Square, Inc.
Publication of WO2012051071A1 publication Critical patent/WO2012051071A1/fr

Links

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F7/00—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
    • G07F7/08—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means
    • G07F7/0873—Details of the card reader
    • G07F7/088—Details of the card reader the card reader being part of the point of sale [POS] terminal or electronic cash register [ECR] itself
    • G07F7/0886—Details of the card reader the card reader being part of the point of sale [POS] terminal or electronic cash register [ECR] itself the card reader being portable for interacting with a POS or ECR in realizing a payment transaction
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322—Aspects of commerce using mobile devices [M-devices]
    • G06Q20/3224—Transactions dependent on location of M-devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/347—Passive cards

Definitions

  • the present invention relates generally to payments of a first party to a second party, and more particularly to payments by a first party to a second party using a payment service by the first party opening a tab that is selected by the second party at any geographic location of the first parties mobile device.
  • Plastic cards having a magnetic stripe embedded on one side of the card are prevalent in everyday commerce. These cards are used in various transactions such as to pay for purchases by using a credit card, a debit card, or a gasoline charge card. A charge card or a debit card may also be used to transact business with a bank through use of an automated teller machine (ATM).
  • ATM automated teller machine
  • the magnetic stripe card is capable of storing data by modifying the magnetism of magnetic particles embedded in the stripe.
  • the data stored on the magnetic stripe may be sensed or read by swiping the stripe past a read head.
  • the analog waveform obtained by sensing the magnetic stripe must undergo a process known as decoding to obtain the digital information stored in the magnetic stripe of the card.
  • Platform card readers are traditional card swipers with single rails, which allow a card to be held against the base of the reader by the user and moved across the read head of the reader. Plunge swipers guide a card by two sets of rails and a backstop. Once the user has inserted the card against the backstop, the card is read as it is removed from the plunge swipers. Plunge swipers are common on ATMs and other self-pay devices because they are less prone to hacking.
  • Magnetic stripe cards having standard specifications can typically be read by point- of-sale devices at a merchant's location.
  • an electronic card reader such as a platform card reader
  • the reader will usually use its built-in modem to dial the number of a company that handles credit authentication requests. Once the account is verified and an approval signal will be sent back to the merchant to complete a transaction.
  • magnetic stripe cards are universally used by merchants, there is no way for an individual to take advantage of the card to receive a payment from another individual (who is not a merchant) by swiping the card through a simple reader attached to his/her mobile device.
  • one person may owe another person money for a debt, and the conventional way to pay the debt is to provide cash or a check. It would be convenient to be able to use a credit card or a debit card to pay off the debt.
  • An object of the present invention is to provide methods for a first party to pay a second party using a payment service.
  • Another object of the present invention is to provide methods for a first party to pay a second party using a payment service by the first party opening a tab that is selected by the second party at any geographic location of the first parties mobile device.
  • Yet another object of the present invention is to provide methods for a first party to pay a second party using a payment service by the first party opening a tab that is selected by the second party at any geographic location of the first parties mobile device, but the financial transaction can only be completed when the first party is within a defined geographic area.
  • a first party accesses the names of one or more qualified second parties.
  • the qualified second parties are second parties that, (i) have an association with the payment service, and (ii) second parties that if they do not have an established association with the payment service then they have established one prior to payment.
  • the first party has an association with the payment service.
  • a tab is opened by the first party that can be selected by the qualified second party at any geographic location of a first party's mobile device.
  • the qualified second party is only able to charge a first party's financial account when the first party's mobile device is within a defined geographic area.
  • the tab is a relationship between the first party, the payment service and the qualified second party.
  • the qualified second party can engage in a financial transaction with the first party is within the defined geographic area.
  • a method of paying a second party includes accessing by a first party, with the first party's mobile device, names of one or more qualified second parties. Second parties have an association with the payment service or if not, they established an association with the payment service prior to payment. The first party has an association with the payment service. A tab is opened by the first party that can be selected by the qualified second party at any geographic location of a first party's mobile device. The qualified second party is only able to charge a first party's financial account when the first party's mobile device is within a defined geographic area. The tab is a relationship between the first party, the payment service and the qualified second party. The qualified second party can engage in a financial transaction with the first party within the defined geographic area.
  • FIG. 1 depicts an example of a system diagram to support financial transaction between a payer and a payee through a miniaturized card reader connected to a mobile device.
  • FIG. 2 depicts an example of an external structural diagram of a miniaturized card reader.
  • FIGs. 3(a)-(b) depict examples of actual card reader with miniaturized design.
  • FIGs. 4(a)-(b) depict examples of alignment between read head of the card reader and magnetic stripe of card being swiped.
  • FIG. 5 depicts an example of a TRS connector as a part of card reader.
  • FIGs. 6(a)-(c) depict examples of internal structures of a miniaturized card reader.
  • FIGs. 7(a)-(b) depict examples of waveforms of data read from one track of the magnetic stripe by read head when the card is swiped through the slot of the card reader in the forward and reverse directions, respectively.
  • FIG. 8 depicts a flowchart of an example of a process to support swiping of a card with a magnetic stripe through a miniaturized portable card reader.
  • FIG. 9 depicts an example of schematic diagram of passive ID circuitry embedded in the card reader.
  • FIG. 10 depicts an example of schematic diagram that contains additional components of passive ID circuitry 22 that contribute to the user experience.
  • FIG. 1 1 depicts an example of an implementation for passive ID circuitry 22 depicted in FIG. 10.
  • FIG. 12 depicts a flowchart of an example of a process to deliver the unique ID to mobile device via the passive ID circuitry.
  • FIG. 13 depicts an example of additional encryption and/or decryption systems included in the passive ID circuitry for encrypting and decrypting of unique ID of card reader.
  • FIG. 14 depicts a flowchart of an example of a process to support decoding of incoming signals from swiping of a card with a magnetic stripe through a miniaturized portable card reader.
  • FIG. 15 depicts a flowchart of an example of a process to support financial transaction between a payer and a payee through a miniaturized card reader connected to a mobile device.
  • FIGs. 16(a)-(f) depict screenshots of an example of a financial transaction between a purchaser and a merchant through a miniaturized card reader connected to a mobile device.
  • FIG. 17 illustrates an integrated read head/mobile device embodiment of the present invention.
  • FIG. 18 illustrates one embodiment of a method of making payments using a mobile device where a tab is opened by a first party and is selected by a qualified second party at any geographic location of the first party's mobile device.
  • FIG. 19 illustrates an overall system architecture of a payment service that can be used in various embodiments of the present invention.
  • FIG 20 illustrates an embodiment of the present invention for a method of conducing on-line purchases using a mobile device.
  • FIG 21 illustrates an embodiment of the present invention where a method is provided for transferring funds to and/or from a first party's financial account, and the first party's financial account information is entered with a single initial entry to the payment service and for future payments the information need not be re-entered.
  • a new approach is proposed that contemplates systems and methods to enable an individual to complete a financial transaction by swiping a magnetic stripe card through a card reader connected to a mobile device. It will be appreciated that the systems and methods of the present invention can be used with financial transactions cards
  • the financial transaction can be any transaction that involves receiving or sending payment from one person to another.
  • the magnetic stripe card can be but is not limited to a credit card, a debit card, or other types of payment authenticating pieces capable of carrying out the financial transaction.
  • the size of the card reader is miniaturized to be portable for connection with the mobile device.
  • the card reader is configured to reliably read data encoded in a magnetic strip of the card with minimum error in a single swipe and provide a signal that corresponds to the data read to the mobile device, which then decodes the incoming signal from the card reader and acts as a point-of-sale device to complete the financial transaction.
  • Such an approach enables a person to become either a micro-merchant (payee or second party) or a buyer/customer (payer or first party) without having to purchase expensive card reader devices or software.
  • FIG. 1 depicts an example of a system diagram to support financial transaction between a payer and a payee through a miniaturized card reader connected to a mobile device.
  • the diagrams depict components as functionally separate, such depiction is merely for illustrative purposes. It will be apparent that the components portrayed in this figure can be arbitrarily combined or divided into separate software, firmware and/or hardware components. Furthermore, it will also be apparent that such components, regardless of how they are combined or divided, can execute on the same host or multiple hosts, and wherein multiple hosts can be connected by one or more networks.
  • the system includes a mobile device 100, a miniaturized card reader 10 connected to mobile device 100, a decoding engine 1 10, a user interaction engine 120, and a transaction engine 130, all running on mobile device 100. Additionally, the system may also include one or more of user database 140, product or service database 150, and transaction database 160, all coupled to the transaction engine 130.
  • the term engine refers to software, firmware, hardware, or other component that is used to effectuate a purpose.
  • the engine will typically include software instructions that are stored in non-volatile memory (also referred to as secondary memory).
  • non-volatile memory also referred to as secondary memory
  • the processor executes the software instructions in memory.
  • the processor may be a shared processor, a dedicated processor, or a combination of shared or dedicated processors.
  • a typical program will include calls to hardware components (such as I/O devices), which typically requires the execution of drivers.
  • the drivers may or may not be considered part of the engine, but the distinction is not critical.
  • mobile device 100 to which the portable card reader 10 is connected to can be but is not limited to, a cell phone, such as Apple's iPhone, other portable electronic devices, such as Apple's iPod Touches, Apple's iPads, and mobile devices based on Google's Android operating system, and any other portable electronic device that includes software, firmware, hardware, or a combination thereof that is capable of at least receiving the signal, decoding if needed, exchanging information with a transaction server to verify the buyer and/or seller's account information, conducting the transaction, and generating a receipt.
  • a cell phone such as Apple's iPhone
  • other portable electronic devices such as Apple's iPod Touches, Apple's iPads
  • mobile devices based on Google's Android operating system and any other portable electronic device that includes software, firmware, hardware, or a combination thereof that is capable of at least receiving the signal, decoding if needed, exchanging information with a transaction server to verify the buyer and/or seller's account information, conducting the transaction, and generating a receipt.
  • Typical components of mobile device 100 may include but are not limited to persistent memories like flash ROM, random access memory like SRAM, a camera, a battery, LCD driver, a display, a cellular antenna, a speaker, a Bluetooth circuit, and WIFI circuitry, where the persistent memory may contain programs, applications, and/or an operating system for the mobile device.
  • persistent memories like flash ROM, random access memory like SRAM, a camera, a battery, LCD driver, a display, a cellular antenna, a speaker, a Bluetooth circuit, and WIFI circuitry
  • the persistent memory may contain programs, applications, and/or an operating system for the mobile device.
  • a system is provided with transaction engine 130 running on mobile device 100.
  • the mobile device 100 accepts information selected including but not limited to information from financial transaction or information pertaining to financial transaction card used by the buyer in the transaction.
  • a financial transaction device can be utilized.
  • financial transaction devices include but are not limited to a, wristband, RFID chip, cell phone, biometric marker and the like. At least a portion of this information is communicated with a third party financial institution or payment network to authorize the transaction.
  • the buyer receives confirmation of the payment. Payment confirmation can be in real time by a payment service.
  • Payment confirmation can be made with a communication channel of the buyer's choice.
  • confirmation of payment can be an electronic notification in the form selected from at least one of, email, SMS message, tweet (message delivered via Twitter), instant message, communication within a social network and the like.
  • a confirmation is made that the buyer is authorized to use the financial transaction card in order to prevent fraud.
  • a confirmation is made that the buyer is authorized to use the financial transaction card in order to prevent fraud.
  • miniaturized card reader 10 is configured to read data encoded in a magnetic strip of a card being swiped by a buyer and send a signal that corresponds to the data read to mobile device 100 via a signal plug 18. This signal is at least partially if not fully decoded in the mobile device 100.
  • the size of card reader 10 is miniaturized to be portable for connection with mobile device 100.
  • the size of card reader 10 can be miniaturized to an overall length of less than 1 .5".
  • the miniaturized card reader 10 is also designed to reliably read the card with minimum error via a single swipe by counteracting vendor specific filtering done by mobile device 00.
  • FIG. 2 depicts an example of an external structural diagram of miniaturized card reader 10. Although the diagrams depict components as functionally separate, such depiction is merely for illustrative purposes. It will be apparent that the components portrayed in this figure can be arbitrarily combined or divided into separate software, firmware and/or hardware components.
  • miniaturized card reader 10 is shown to comprise at least a housing 12 having a slot 14, a read head 16 embedded on a wall of slot 14, a signal plug 18 extending out from the housing 12, and an optional passive ID circuit 22.
  • FIG. 3(a) depicts an example of an actual card reader with miniaturized design and FIG. 3(b) depicts other examples of miniaturized card reader with width around 0.5".
  • the card reader 10 includes the slot 14 and is miniaturized relative to the size of the mobile device 100. In some embodiments, the housing 12 is not included.
  • the slot 4 is configured to maintain contact between the read head 16, and the magnetic stripe of the financial transaction card during a swipe.
  • the signal is decoded in the mobile device 100.
  • the decoding includes determining pulses in the signal and converting at least some of the pulses to characters.
  • the slot 14 has a width of no greater than 1 mm. The width of the slot 14 is sufficient to enable a successful swiping of the financial transaction card, while producing the signal. It is sized to enable the successful swipe without creating sufficient torque between the signal plug 18 or output jack and the read head 16 or at the mobile device 100 to cause damage due to excessive torque. If the slot 14 is too wide, then it is more difficult to achieve a successful swipe that produce the signal.
  • the resulting signal is not competent. If the slot 14 is too narrow, then the financial transaction card can not be swiped. The size of the slot 14 is selected to reduce torque as discussed above. Additionally, in one embodiment, the output jack 18 is at least partially if not fully rotatable relative to the port it is coupled to in the mobile device 100.
  • the decoding includes error checking. In one embodiment, the decoding includes detecting that data in the signal is from the financial transaction card, seeing the beginning and ending sentinels and reconstructing data in the signal from a pattern of pulses. [0052] In one embodiment of the present invention, the mobile device 100 has an audio input port and a line input port.
  • a sampling rate of the signal at the audio input port or a line input port of the mobile device is at least 5kHZ.
  • the sample rate of the signal at the audio input port or line import port can be, least 20 kHz; at least 25 kHz, at least 30 kHz, at least 35 kHz or at least 40 kHz.
  • the slot 14 is oriented and sized to reduce torque applied on the read head 10 when the financial transaction card is swiped through the slot 14 in order to maintain accuracy and reliability of the data read by the read head 0.
  • housing 12 of card reader 10 is designed to be
  • the texture side of housing 12 should match with the texture (front) side of the card, so that a user can easily identify the right side of the reader to swipe the card through slot 14 without actually looking at the reader or card. Even a blind person is able to swipe the card correctly by matching the texture side of the reader with the texture side of the card.
  • the slot 14 is wide enough and deep enough to accept a card having a magnetic stripe so that the stripe will fit within the slot 14. More importantly, the slot 14 is configured to reduce the torque applied on the reader 10 when the card is swiped through slot 14 in order to maintain accuracy and reliability of the data read by read head 16. Since the size of card reader 10 is miniaturized, slot 14 also has a length that is significantly less than the length of the card to be inserted into the slot 14.
  • the read head 16 To correctly read the data on the magnetic stripe of the card, the read head 16 must maintain contact with the stripe as the card moves past slot 14. If the card rocks during the swipe, the alignment of the head 12 with the stripe may be compromised. As the length of the slot 14, i.e., the card path through which the card swiped though slot 14, is shortened, rocking and head alignment may become significant issues. As shown in FIG. 4(a), if the magnetic stripe card is swiped through without the base of the card resting against the flat bottom piece, the magnetic stripe will not align with the read head 16 when the card is swiped through slot 14 having a flat base 15.
  • the base 15 of slot 14 can be changed from flat to a curved base with a radius in order to increase contact between the read head 16 and the magnetic stripe to address the rocking problem. As shown in FIG. 4(b), the read head 16 can maintain contact with the magnetic stripe, even with some additional error due to the gradation of contact introduced by the curved base 15.
  • FIG. 5 depicts an example of signal plug 18 as part of card reader 10.
  • signal plug 18 can be but is not limited to a TRS (tip, ring, sleeve) connector also known as an audio plug, phone plug, plug plug, stereo plug, mini-plug, or a mini-stereo audio connector.
  • TRS tip, ring, sleeve
  • the signal plug 18 may be formed of different sizes such as miniaturized versions that are 3.5 mm or 2.5 mm.
  • signal plug 18 may be retractable within the housing 12.
  • signal plug 18 is configured to extend beyond housing 12 of the reader in order to accommodate connection with mobile devices 100 having cases or having a recessed plug-in socket, wherein the socket can be but is not limited to a microphone input socket or a line in audio input of the mobile device.
  • housing 12 of card reader 10 is made of non-conductive material such as plastic so that the reader will not interfere with the function of mobile device 100 it is connected with.
  • non-conductive material such as plastic
  • Such choice of material is important since the outer case of certain mobile devices, such as iPhone 4, is conductive and serves as an antenna for the device, which function could potentially be interfered with if the metal case of the device gets in touch with the housing of a card reader made of conductive material.
  • FIG. 6(a) depicts an example of an internal structural diagram of a miniaturized card reader. Although the diagrams depict components as functionally separate, such depiction is merely for illustrative purposes. It will be apparent that the components portrayed in this figure can be arbitrarily combined or divided into separate software, firmware and/or hardware components.
  • the internal structure inside housing 12 of card reader 10 is shown to comprise at least a read head 16 with embedded circuitry, and a spring structure 20 to support read head 16.
  • FIG. 6(b) depicts an example of an internal structure an actual miniaturized card reader.
  • FIG. 6(c) depicts an example of separated components of read head 16 and spring structure 20 used in the actual miniaturized card reader.
  • read head 16 which for a non-limiting example, can be an inductive pickup head, detects and provides data stored in the magnetic stripe of a card to a connected mobile device 100. More specifically, as the magnetic stripe of a card is swiped through slot 14 and in contact with read head 16, the card reader device 10 reads one or more tracks of data or information stored in the magnetic stripe of the card via the detection circuitry embedded inside the read head.
  • data stored in the magnetic stripe may be in the form of magnetic transitions as described in the ISO 781 standards.
  • read head 16 in card reader is capable of reading only one track of data (either track 1 or 2, but not both) from the magnetic stripe in order to reduce the size and structural complexity of compact read head 16 as only one pin needs to be included in the read head.
  • FIG. 7(a)-(b) depict examples of waveforms of data read from track 1 (instead of both tracks 1 and 2 as by a traditional read head) of the magnetic stripe by read head 16 when the card is swiped through slot 14 in the forward and reverse directions, respectively.
  • the size or thickness of the housing 12 of card reader 10 is configured to be narrow enough to accommodate only a single read head 16. Such design is intended to be tampering-proof so that even if the housing 12 is tampered with, no additional circuitry can be added to the card reader 10 and such tampering will render the card reader non-functional.
  • spring structure 20 is a flexible spring mounting to read head 16 without a screw, causing the read head to be suspended to housing 12 of card reader 10.
  • spring 20 can either be connected to housing 12 via screws or welded to plastic housing 12 without using any screws.
  • Spring 20 allows suspended read head 16 to swivel while maintaining contact pressure to track the stripe of the card being swiped.
  • Spring 20 is designed to be sufficiently small to fit within the miniaturized card reader 10, yet powerful enough to maintain good contact during the stripe.
  • spring 20 positions the supports for read head 20 inside the overall form of the spring, which allows the spring to flex without having to make one support moveable.
  • FIG. 8 depicts a flowchart of an example of a process to support swiping of a card with a magnetic stripe through a miniaturized portable card reader.
  • this figure depicts functional steps in a particular order for purposes of illustration, the process is not limited to any particular order or arrangement of steps.
  • One skilled in the relevant art will appreciate that the various steps portrayed in this figure could be omitted, rearranged, combined and/or adapted in various ways.
  • the flowchart 800 starts at block 802 where a miniaturized card reader is structured to provide sufficient contact between a read head and the magnetic stripe during a swipe of a card.
  • the flowchart 800 continues to block 804 where a card with a magnetic stripe is swiped through a slot of the miniaturized card reader.
  • the flowchart 800 continues to block 806 where the read head reliably reads data stored in the magnetic stripe and generates an analog signal or waveform indicative of data stored in the magnetic stripe.
  • the flowchart 800 continues to block 808 where amplitude of the waveform is set by the circuitry inside the read head.
  • the flowchart 800 ends at block 810 where the set waveform is provided to a mobile device 100 connected with the miniaturized card reader via the signal plug 18.
  • housing 12 of card reader 1 0 may further encapsulate a passive ID circuitry 22 powered by the mobile device 00 through signal plug 18, wherein passive ID circuitry 22 delivers an unique ID of the card reader to mobile device 100 only once upon the card reader being connected to (and powered up by) the mobile device.
  • passive ID circuitry 22 functions independently and separately from read head 18 without interfering with the read head's card swiping functions described above.
  • FIG. 9 depicts an example of schematic diagram of passive ID circuitry embedded in the card reader.
  • passive ID circuitry 22 may comprise at least five main subsystem/components: unique ID storage 24, communication subsystem 26, which reads and transmits the unique ID from unique ID storage 24, power subsystem 28, which provides power to enable communication with mobile device 100, a pathway subsystem 30 to route signals to signal plug 18 through the circuitry, and a control unit 32, to orchestrate the communication between different systems. All of these subsystems can be
  • Communication subsystem 26, power subsystem 28, and read head 16 share the same signal plug 18 for connection with the mobile device.
  • the components portrayed in this figure can be arbitrarily combined or divided into separate software, firmware and/or hardware components.
  • unique ID storage 24 is memory containing the Unique ID of the card reader.
  • the unique ID storage 24 can be any persistent memory containing bytes that can be accessed by the communication subsystem 26.
  • the power subsystem 28 comprises of a modified charge pump, which utilizes a digital circuit to artificially raise the voltage of a power source to a higher level. Normal charge pump operation requires large current which is then fed into several capacitors, and switching logic switches the capacitors between series and parallel configurations.
  • the power source is a bias voltage provided by the mobile device meant for detection of a connected component. It is nominally 1 .5V and is supplied through a 2kD resistor, resulting in a maximum current of 750 ⁇ . Details of how the power subsystem 28 function is described in FIG. 1 1 .
  • the pathway subsystem 30 is configured to direct the mobile device's 100 bias voltage to the power subsystem 28. After the power subsystem converts the bias voltage to a system voltage, the control unit 32 is able to operate. Control unit 32 configures the pathway subsystem 30 to allow the communication subsystem 26 access to the mobile device 00, The communication subsystem 26 relays the unique ID from the unique ID storage 24. The control unit 32 then configures the pathway subsystem 30 to allow the card reader circuit 16 access to the mobile device 100.
  • FIG. 10 depicts an example of schematic diagram that contains additional components of passive ID circuitry 22 that contribute to the user experience. These additional systems prevent the mobile device 100 from perceiving that the card reader 10 has been disconnected during power cycles. These additional systems also ensure that the unique ID sent from unique ID storage 24 is sent as specified by the designer.
  • This extra feature set comprises of a discharge subsystem 34 to force the device to power cycle, a fake load 36 so the mobile device 100 does not perceive a disconnect, and a monitor system 38 to manage card reader 10 behavior between power cycles.
  • communication subsystem 26 comprises a signal driver connected with control unit 32 and unique ID storage 24.
  • communication subsystem 26 will check a status bit in the monitor subsystem 38. The first time this process occurs, the status bit will be not set. When the status bit is not set the ID is sent immediately.
  • Fig. 12 contains a detailed flowchart of a non-limiting example of this process.
  • the control unit 32 will write to the status bit in monitor subsystem 38. It will then use the discharge system 34 to reset itself. During this time the pathway subsystem 30 will be configured to direct the signal path to the fake load preventing the mobile device 100 from detecting a disconnect with the card reader 10.
  • the control unit 32 will read the status bit. Upon seeing that the status bit is cleared it will configure the pathway subsystem 30 to direct the signal path to the card reader circuit 16. The control unit 32 will then put the system into an extremely low power state (from here referred to as a sleep state). Only the monitoring subsystem 38 will remain active. The monitor subsystem 38 will wake the system from the sleep state at some time (time depending on implementation) before a power cycle. The control unit 32 will notified of the system awakening by the monitoring subsystem 38. The control unit 32 will then set the status bit on the monitor subsystem 38 only if there is a voltage detected on the fake load indicating the reader is still connected. The control unit 32 will then force a power cycle.
  • a sleep state Only the monitoring subsystem 38 will remain active. The monitor subsystem 38 will wake the system from the sleep state at some time (time depending on implementation) before a power cycle. The control unit 32 will notified of the system awakening by the monitoring subsystem 38. The control unit 32 will then set the status bit on the monitor subsystem 38 only if there is
  • FIG. 1 1 depicts an example of an implementation for passive ID circuitry 22 depicted in FIG. 10.
  • power subsystem 28 has multiple capacitors in parallel.
  • a voltage breaker e.g., zener diode etc
  • a latch are used to trigger the transition between parallel and series configurations. Once the latch is flipped, power subsystem 28 will remain in series configuration until the combined voltage drops bellow the CMOS trigger gate voltage at about .4V. At this time the passive ID circuitry 22 will reset and the unique ID delivery process will begin again
  • pathway subsystem 30 comprises a plurality of latches controlled by control unit 32 for switching among various subsystems of passive ID circuitry 22.
  • the default configuration allocates the output signal through signal plug 18 to modified charge pump of power subsystem 28.
  • control unit 32 After the latch to turn off modified charge pump 28 is triggered, control unit 32 will route signal plug 18 from read head 16 to communication subsystem 26 and transmit the unique ID through signal plug 18 after checking the status bit in unique ID storage 24.
  • Pathway subsystem 30 will then write to the status bit in unique ID storage 24 and discharge the power subsystem 28.
  • FIG. 12 depicts a flowchart of an example of a process to deliver the unique ID to mobile device 100 via the passive ID circuitry 22.
  • passive ID circuitry 22 may further include additional encryption and/or decryption systems as shown in FIG. 13 for encrypting and decrypting of unique ID of card reader 10.
  • the decoding system 42 and encryption system 40 can both use the control unit 32 from the passive ID circuitry 22 to communicate with the mobile device 100 over the communication subsystem 26.
  • the incoming signals may be amplified, sampled, and converted to a stream of digital values or samples by decoding engine 1 10 running via a microprocessor inside the mobile device.
  • decoding engine 1 10 may comprise a pipeline of software decoding processes (decoders) to decode and process the incoming signals as described below, where each software process in this pipeline can be swapped out and replaced to accommodate various densities of track data read in order to reduce card swipe error rate.
  • the incoming signals may be of low quality due to one or more of: low quality of data read from a single and/or low density track of a magnetic stripe of the card, sampling speed limitations of the microphone input socket of the mobile device, and noise introduced into the mobile device 100 from card reader 10.
  • FIG. 14 depicts a flowchart of an example of a process to support decoding of incoming signals from swiping of a card with a magnetic stripe through a miniaturized portable card reader.
  • the flowchart 1400 starts at block 1402 where decoding engine 110 initializes its internal state by waiting for the system voltage to reach a steady state.
  • decoding engine 110 initializes its internal state by waiting for the system voltage to reach a steady state.
  • the signal is determined to be in a steady state.
  • the DC offset of the incoming signals are computed when the mobile device is first connected to the card reader over signal plug 18.
  • initialization goes through at least the following steps:
  • step 4 If the variance computed in step 4 is less than the variance threshold, 0.06% of full scale or less than the offset percentage, 10% of the offset average computed in step 3, and the DC offset computed in step 1 is less than the noise ceiling, 3% of full scale, of the mobile device 100.
  • decoding engine 110 can proceed to process the incoming signals to detect the swipe of the card. Otherwise, Steps 1-4 need to be repeated.
  • decoding engine 1 10 detects the card swipe once the incoming signals are in a steady state.
  • This signal detection phase processes the incoming signals in steady state in order to detect the presence of a swipe of a card through the card reader.
  • the signal detection phase is a light-weight procedure that operates at near real time. It parses the incoming signals quickly and stitches multiple system buffers of signals together to form a signal of interest.
  • the signal detection process goes through at least the following steps:
  • the incoming signal is appended to a larger buffer until the signal drops below a minimum signal amplitude threshold for a certain period of time, e.g., 10ms.
  • a hardware independent swipe detection process can be utilized to capture the signal of interest via Fast Fourier Transform (FFT), while trimming the front and back of the signal.
  • FFT Fast Fourier Transform
  • the flowchart 1400 continues to block 1406 once a card swipe is detected to be present where decoding engine 1 10 identifies peaks in the incoming signals.
  • Peak detection is the most complex portion of decoding of incoming signals from credit card swipes, and credit card swipe decodes have traditionally not been done on heavily filtered signals like the signal that enters through the TRS plug, since most mobile device manufacturers assume the incoming signal is audio based. This results in a wide variety of signal filtering that peak detection must account for.
  • Reactive peak detection is a heuristics based approach for peak detection, which is well suited for situations where the incoming signals from the card swipe is not excessively distorted by the mobile device's filter circuitry. This approach utilizes at least the following steps to detect signal peaks::
  • Predictive peak detection defers the heavy processing to the digitizing stage of decoding. Predictive peak detection is highly resistant to scratches in the card that could cause low quality or false peak information to manifest in the incoming signals. This approach is more memory intensive than the reactive peak detection approach since more peaks are stored. The approach utilizes at least the following steps to detect signal peaks:
  • Maxima peak detection detects peaks by looking for local maxima and minima within a window of digital samples. If either of these is at the edges of the window of samples, then the approach skips the window and moves to the next window to look for local maxima and minima. These local maxima and minima are then stored into a list of peaks.
  • decoding engine 1 10 identifies the track from which data of the incoming signals are read through the swipe of the card via the card reader.
  • track 1 and track 2 came off of different pins on the read head of a card reader, and so there was no need to guess which track is being read. Since read head 16 in card reader is capable of reading only one track of data from the magnetic stripe, track identification becomes an important issue.
  • This track identification process is run by detection engine 1 10 after peaks are detected to guess and recognize the track (track 1 or track 2) from which the data is read by card reader by inferring a range of peaks to be expected for signals coming from each track.
  • track 1 Since track 1 is known to be much denser in data than track 2, it is thus reasonable to expect more peaks to be identified in data coming from track 1. Although this process is not a definitive guess, it yields the correct track value 99.9% when coupled with the peak detection algorithms described herein in testing.
  • track guessing can be based on the number of bits found in the digital signals after the digitizing stage of decoding. When a decoder fails due to guessing the wrong track (since track identification affects how the bits from the digital signals are framed and matched against character sets), the decoder may simply choose another track type, though this makes the card processing more processor intensive.
  • the flowchart 1400 continues to block 1410 where decoding engine 1 10 digitizes the identified peaks in the incoming signals into bits.
  • the digitizing process takes the given peak information turns them into binary data and appends them to an array of digital bits.
  • Reactive digitizing takes the given peak information as fact, and attempts to convert them into 1s and 0s in the following steps:
  • Tie breaking if the distances are equal and the next two peak amplitudes are smaller than the current peak amplitude, then identify the bit found as a 1 . Otherwise, identify the bit found as a 0.
  • Predictive digitizing of detected peaks in the incoming signals does not treat the list of peaks as facts. It first finds bit length, and then seeks to a point in the peak list where the next relevant peak should be. Once it reaches this location, it then searches before and after the location for the nearest peak. The process then checks the polarity of this peak compared to the previous peak examined. If the polarities are the same, the bit found is identified as a 1. Otherwise, it is identified as a 0. This method of digitizing a peak list is effective in that it simply ignores any information that is likely irrelevant.
  • the flowchart 1400 ends at block 1412 where decoding engine 1 10 converts the array of digitized bits into words of card information. This converting process locates the bit sequence that is the start sentinel in the array. At that point, it takes frames of bits (e.g., 5 bits for track 2, 7 bits for track 1 ) and decodes them based on a symbol table. Along the way, the process constantly checks for parity and the LRC at the end to ensure the data is correct. If there are any errors in parity, LRC, or track length, blocks 1406-1412 may be repeated with a different set of parameters to get the correct signal data.
  • decoding engine 1 10 converts the array of digitized bits into words of card information. This converting process locates the bit sequence that is the start sentinel in the array. At that point, it takes frames of bits (e.g., 5 bits for track 2, 7 bits for track 1 ) and decodes them based on a symbol table. Along the way, the process constantly checks for parity and the LRC at the
  • decoding engine 10 can combine various peak detectors and digitizers discussed above in order to cover various ranges of degradation in quality of the analog input signal generated by card reader 10.
  • different process combinations and parameters can be chosen and optimized depending on the hardware platform of the mobile device. These combinations and parameter values can be pre-determined based on experimentation and testing and initialized upon starting of the decoding process.
  • the decoding then runs through all processes specified and runs certain specific processes multiple times in order to get the correct signal.
  • Such decoding process allows automatic scaling and adjustment during each run to account for different amounts of noise, sampling speed variations, signal ringing, and swipe direction.
  • user interaction engine 120 is a software application running on mobile device 100 associated with a payee (merchant) that enables the payer (buyer) and the merchant to interact with transaction engine 130 to complete a financial transaction. More specifically, it may take input of information related to the financial transaction from the buyer and/or the merchant, provide such input to transaction engine to initiate and complete the transaction, and present the result of the transaction to the buyer and the merchant.
  • the input of information accepted by user interaction engine 120 may include but is not limited to one or more of: amount of the transaction, including list price and optionally tips, additional notes related to the transaction such as written description and/or pictures of the item to be purchased, authorization and/or signature of the buyer.
  • user interaction engine 120 may utilize a touch screen of mobile device 100 to enable the buyer and the merchant to input numbers, characters, and signatures by touching the screen via a stylus or a finger.
  • user interaction engine 120 may also present products or services provided by the merchant to the buyer in combination of one or more of text, pictures, audio, and videos, and enable the buyer to browse through the products and services on the mobile device to choose the one he/she intended to purchase.
  • product information can be stored and managed in product database 150.
  • transaction engine 130 takes as its input the decoded credit card information from decoding engine 0 and transaction amount from user interaction engine 120.
  • Transaction engine 130 then contacts third party financial institutions such as an acquiring bank that handles such authorization request, directly or through a payment system, which may then communicate with the card issuing bank to either authorize or deny the transaction. If the third party authorizes the transaction, then transaction engine 130 will transfer the amount of money deducted from the account of the card holder (e.g., the buyer) to an account of the merchant and provide the transaction results to user interaction engine 120 for presentation to the buyer and the merchant. In this manner, the merchant may accept a payment from the buyer via card reader 0 and mobile device 100. [0140] In the example of FIG.
  • transaction engine 130 running on mobile device 100 protects the privacy of the buyer/payer during the card-present transaction by taking card information from the buyer directly from decoding engine 1 10 and do not share such information with the merchant via user interaction engine 120.
  • the card information that are not shared with the merchant includes but is not limited to, card number, card holder's name, expiration date, security code, etc.
  • transaction engine 130 serves as an intermediary between the buyer and the merchant, so that the buyer does not have to share his/her card information with the merchant as in a typical card-present transaction or an online transaction. Still, the buyer is able obtain an itemized receipt for the transaction completed as discussed later.
  • transaction engine 130 may present identity information of the buyer, such as a picture of the buyer on record in user database 140, with the merchant via user interaction engine 120 so that merchant can reliably confirm the identity of the buyer during the card-present transaction to prevent credit fraud.
  • user database 140, product database 150, and transaction database 160 can be used to store information of buyer and the merchant, products and services provided by the merchant, and transactions performed, respectively. This information can also be stored by the payment system.
  • user information e.g., name, telephone number, e-mail, etc.
  • product information can be provided by the merchant, while transaction database 160 is updated every time a transaction is processed by the transaction engine 130.
  • Information stored can be selectively accessed and provided to the buyer and/or merchant as necessary.
  • transaction engine 130 communicates and interacts with the third party financial institution directly or through the payment system, user database 140, product database 150, and transaction database 160 over a network through the payment system (not shown).
  • the network can be a communication network based on certain communication protocols, such as TCP/IP protocol.
  • TCP/IP protocol such as TCP/IP protocol.
  • Such network can be but is not limited to, internet, intranet, wide area network (WAN), local area network (LAN), wireless network, Bluetooth, WiFi, and mobile communication network.
  • WAN wide area network
  • LAN local area network
  • wireless network Bluetooth, WiFi, and mobile communication network.
  • the physical connections of the network and the communication protocols are well known to those of skill in the art.
  • Dynamic receipt upon the completion of a financial transaction through, for a non-limiting example, card reader 10 connected to mobile device 100 associated with a merchant, transaction engine 130 running on the mobile device 100 can be configured to capture additional data associated with the transaction and incorporate the additional data into a dynamic receipt for the transaction, wherein in addition to transaction information typically included in a conventional receipt, the dynamic receipt may also include additional environmental information of the transaction.
  • the financial transaction can be an electronic transaction conducted over the Internet or a card present point-of-sale transaction where the buyer/payer makes the purchase at a store front, other "brick-and-mortar" location, or simply in presence of a merchant/payee.
  • the additional environmental information included in the dynamic receipt may include information pertaining to the transaction environment.
  • a mobile device equipped with a Global Positioning System (GPS) receiver can be used to capture the coordinates/location of the transaction, and record it as a part of the information on the dynamic receipt. This way, the physical location of the point of sale (which may be different from the merchant/payee's registered address) can be recorded and used by transaction engine 20 to verify the transaction.
  • GPS Global Positioning System
  • a mobile device equipped with a camera and/or audio and/or video recorder can be used to capture a photo and/or a video and/or an audio recording of the product or service involved in the transaction and incorporate such data or link/reference to such data into the dynamic receipt.
  • a mobile device with a biometric scanner can be used to scan the fingerprint or palm print of the buyer/payer and/or merchant/payee and includes at least a portion of such information in the dynamic receipt.
  • the mobile device can record certain information associated with the transaction in the dynamic receipt, wherein such information includes but is not limited to, how quickly the buyer swipes the card, the angle at which the card is swiped.
  • special characteristics of the card being swiped also referred to as the magnetic fingerprint of the card, can be recorded and included in the dynamic receipt.
  • the dynamic receipt can be in electronic form that can be accessed electronically or online and may also include link or reference pointing to multimedia information such as image, video or audio that are relevant to the transaction.
  • transaction engine 130 can use the environmental information included in the dynamic receipt to assess risk associated with a transaction. For a non-limiting example, if the GPS information indicates that the transaction is taking place in a high crime/high risk area, the risk associated with the transaction is adjusted
  • biometric information scanned and included in the dynamic receipt can be used for identity verification purposes to prevent identity theft and credit fraud.
  • transaction engine 130 can use the dynamic receipt can be used as a non-intrusive way to communicate with the buyer and/or the merchant.
  • the additional information included in the dynamic receipt can be used to make offers to the buyer. If a dynamic receipt includes the GPS location of the point of sale of the transaction, coupons or other promotional offers made by vendors at nearby locations can be presented to the buyer when the buyer chooses to view the receipt electronically online.
  • a specific product involved the transaction can be identified by the transaction engine either directly through product description or indirectly by analyzing pictures or videos taken, offers of similar or complementary products can be made by a vendor to the merchant of the product.
  • transaction engine 130 may notify buyer and/or the merchant of the receipt via an electronic message, which can be but is not limited to, an email message, a Short Message Service (SMS) message, Twitter, or other forms of electronic communication.
  • SMS Short Message Service
  • the recipient of the electronic message may then retrieve a complete itemized dynamic receipt online at his/her convenience via a telephone number on his/her record in user database 140 to retrieve his/her electronic receipts stored in transaction database 160.
  • the electronic message may include an indication such as a code that the recipient can use to retrieve the electronic receipt online as an alternative or in combination with the telephone number.
  • FIG. 15 depicts a flowchart of an example of a process to support financial transaction between a payer and a payee through a miniaturized card reader connected to a mobile device.
  • the flowchart 1500 starts at block 1502 where an amount of a financial transaction is provided through an interactive user application launched on the mobile device as shown in FIG. 16(a).
  • the flowchart 1500 continues to block 1504 where a miniaturized card reader structured to minimize swipe error is connected to the mobile device as shown in FIG. 16(b).
  • the flowchart 1500 continues to block 1506 where a card is swiped through the card reader to initiate the financial transaction as shown in FIG. 16(c).
  • the flowchart 1500 continues to block 1508 where the payer confirms the amount of the card-present transaction via a signature signed via the interactive user application on the mobile device to complete the transaction as shown in FIG. 16(d). Payments are made with the use of the payment system which is coupled to the mobile device 100 Note that the signature is required as an additional layer of confirmation for the protection for the payer even when such signature may not be technically required to authorize the transaction.
  • the flowchart 1500 continues to block 1510 where result of the transaction is received and presented to the payer and/or merchant as shown in FIG. 16(e) through the use of the payment system.
  • the flowchart 1500 ends at block 1512 where an electronic receipt of the transaction is provided to the payer in the form of an electronic message as shown in FIG. 16(f).
  • a longitudinal plane of the of the output jack 18 lies within the plane that the card travels in the slot 14 within 5 mm, and in another embodiment within 3mm.
  • an integrated read head system includes mobile device 212 with an audio jack 214 at least one microphone input port 216.
  • a read head 218 is physically coupled to the mobile device 212.
  • the read head 218 has a slot 220 for swiping a magnetic stripe of a financial transaction card to enable a financial transaction between a buyer and seller with the payment system.
  • the read head 218 reads data on the magnetic stripe and produces a signal indicative of data stored on the magnetic stripe.
  • the read head 218 has an output jack 222 that physically connects the read head 218 to at least one of the audio jack 21 or microphone port 216 of the mobile device 212.
  • the read head 218 provides the signal to the mobile device 212.
  • the signal is decoded at the mobile device 212.
  • the decoding includes determining pulses in the signal and converts at least some of the pulses to characters.
  • a method for conducting a financial transaction with a financial transaction card using the integrated read head system 210.
  • a method of paying a second party is provided.
  • a first party views the names of one or more qualified second parties.
  • the qualified second parties are second parties that, (i) have an association with the payment service, and (ii) second parties that if they do not have an established association with the payment service then they have established one prior to payment.
  • the first party has an association with the payment service.
  • a tab is opened by the first party that can be selected by the qualified second party at any geographic location of a first party's mobile device 100.
  • the qualified second party is only able to charge a first party's financial account when the first party's mobile device 100 is within a defined geographic area.
  • the tab is a relationship between the first party, the payment service and the qualified second party,
  • the qualified second party can engage in a financial transaction with the first party is within the defined geographic area.
  • the overall architecture of the payment system is illustrated in Figure 19.
  • the first party's mobile device 100 is configured to communicate with the payment service.
  • the first party views the names of the one or more qualified second parties with the first party's mobile device 100.
  • the first party establishes the first party's financial account.
  • the first party enters financial account information with a single initial entry to the payment service and additional entries of the financial account information to the payment service are not required for future financial transactions between the first party and any qualified second party when the same payment service is used.
  • the financial account is selected from at least one of, a bank account, credit card, debit card, pre-paid card, a second party financial account and the like.
  • the financial account is selected by the first party by at least one of, use of a mobile device 100, from a bank terminal, done on-line and the like.
  • the first party's financial account can be a financial transaction card, and the entering of the first party's financial card information is with a mobile device 100.
  • Entering of the financial card information can be done by, swiping the financial transaction card through a slot of a card reader coupled to the mobile device 100, through a slot of the mobile device 100, by touch of the financial transaction card to the mobile device 100, by typing in information at the mobile device 100, with photos, by selecting a card from an application on a mobile device 100, from an on-line entity and the like.
  • the mobile device 100 is a device as described above.
  • the qualified second party can see a list of first parties that have an association with the payment service.
  • the qualified second party can view a list of first parties with open tabs.
  • the list of first parties seen by the qualified second party has first party identifying information.
  • the identifying information is anything that reliably identifies the first party and can include, but is not limited to, names, photos, cell number, social security number, e-mail address, other personal identifying information for a first party and the like.
  • a method of paying a second party a first party views the names of one or more qualified second parties with a mobile device 100.
  • the mobile device 100 is the first party's mobile device 100.
  • a tab is then opened by the first party as recited above that can be selected by the qualified second party at any geographic location of the first party's mobile device 100, but the qualified second party is only able to charge a first party's financial transaction card when the first party's mobile device 100 is within a defined geographic area
  • the mobile device 100 is coupled to a card reader that includes an output jack adapted to be inserted at least one of the audio input port or microphone input port of the mobile device 100 and delivers a signal to the mobile device 100.
  • the sampling rate of the signal at the audio input port or a line input port of the mobile device 100 is at least 15kHZ, 20 kHz., 30 kHz, 40 kHz and the like.
  • Entering of the financial card information can be achieved by a variety of methods including but not limited to, swiping the financial transaction card through a slot of a card reader coupled to the mobile device 100, through a slot of the mobile device 100, with a touch of the financial transaction card to the mobile device 100, typing in information at the mobile device 100, with photos, selecting a card from an application on a mobile device 100 and from an on-line entity and the like.
  • a confirmation of payment can be made to the first party in response to a transfer of funds from the financial transaction card.
  • the financial transaction card is selected from at least one of, credit financial transaction card, debit financial transaction card, gift financial transaction card, fund transfer financial transaction card, other types of payment authenticating piece capable of carrying out a transfer of funds and the like, as set forth above.
  • a method is provided of conducing on-line purchases using a mobile device 100.
  • a first party visits a second party on-line entity.
  • the first party accesses a second party on-line entity.
  • the first party is already registered with the payment service or becomes registered prior to the conclusion of completing a transaction.
  • the mobile device 100 is configured to
  • the first party considers conducting a transaction with the second party on-line entity.
  • the second party on-line entity is registered with the payment service, or in response to the first party's desire to transact with the second party on-line entity, the second party on-line entity becomes registered with the payment service.
  • the first party enters personal identifying information that is sent to the payment service.
  • the first party receives a push notification to the first party's mobile device 100 that enables the first party to complete the transaction with the second party on-line entity.
  • the first party's personal identifying information is entered by at least one of, use of a mobile device 100, from a bank terminal, done on-line and the like.
  • the first party uses the first party's financial account.
  • the first party enters financial account as recited above, which does not require re-entry with the payment service for future transactions with second parties that are also registered with the payment service.
  • the first party uses the first party's financial transaction card for the transaction where the card information is entered to the payment service as recited above. Additionally, the first party enters it's personal indentifying information with the payment service only once as recited above and need not re-enter for second party transactions.
  • the on-line entity is any second party that can transact business with the payment service including but not limited to, merchants, peers and the like.
  • the first party enters its personal identifying
  • the first party's mobile device 100 is coupled to a card reader that includes an output jack adapted to be inserted at least one of the audio input port or microphone input port of the mobile device 100 and delivers a signal to the mobile device 100.
  • a method for transferring funds to and/or from the first party's financial account is provided with a single initial entry to the payment service. Funds are transferred to and/or from the first party's financial account using the payment service. The funds can be transferred to the first party, or to second parties.
  • the first party's financial account including but not limited to a financial transaction card can be the destination of the funds. A simple swipe of the first party's financial transaction card can make the financial transaction card a funding source.
  • the first party is either registered with the payment service, or becomes registered prior to the transfer of funds to and/or from the financial account using the payment service. For future uses of the first party's financial account, to transfer funds to and/or from the first party's financial account, the first party's financial account information need not be re-entered again with the payment service.
  • funds are transferred from the first party's financial account to a second party using the payment service.
  • the second party is already registered with the payment service or becomes registered with the payment service prior to the transfer of funds from the first party. In another embodiment, the second party is not registered with the payment service.
  • funds are transferred to and/or from the first party's financial account using the payment service, e.g., to the first party or to a second party, where the financial account is a bank account, credit card, debit card, pre-paid card, a third party funding source and the like.
  • the payment service e.g., to the first party or to a second party, where the financial account is a bank account, credit card, debit card, pre-paid card, a third party funding source and the like.
  • the first party's financial card is entered with a single initial entry to the payment service using a mobile device 100. Again, for future uses of the first party's financial transaction card to transfer funds using the payment service to a second party, the first party's financial transaction card information need not be entered again.
  • the entering of the financial card information to the payment service can be achieved by, swiping the financial transaction card through a slot of a card reader coupled to the mobile device 100, through a slot of the mobile device 100, with a touch of the financial transaction card to the mobile device 100, typing in information at the mobile device 100, with photos, selecting a card from an application on a mobile device 100, from an on-line entity and the like.
  • a method of conducting a financial transaction includes the first party's financial account information being entered once, e.g, with a single initial entry to the payment service.
  • the first party's financial account information For future uses of the first party's financial account to transfer funds using the payment service to a second party, the first party's financial account information need not be entered again with the payment service.
  • the second party's personal identifying information is entered. Funds are transferred from the first party's financial account to an account of the second party with the use of the payment service.
  • the first party's financial transaction card information is entered with a single initial entry to the payment service. Again, for future uses of the first party's financial transaction card to transfer funds using the payment service to a second party, the first party's financial account information need not be entered again with the payment service. The second party's personal identifying information is entered and funds are transferred from the first party's financial account to an account of the second party with the use of the payment service.
  • the second party has an association with the payment system
  • the first party and the second party each have an association with the payment system
  • the first party has an association with the payment system but the second party does not.
  • the first party uses a send money mode of the first party's mobile device 100.
  • the second party is (i) anybody on the first party's phone list, (ii) not on the first party's phone list but is added to the first party's phone list in response to a transaction, (iii) the second party has an association with a payment system or is a database of the payment system, (iv) the second party does not have an association but then has one in response to a text message or equivalent sent to the second party, and the like. In response to the text message, the second party either accepts or rejects.
  • the first party's financial transaction card information is entered with a single initial entry to the payment service. Again, for future uses of the first party's financial transaction card information to transfer funds using the payment service to a second party, the first party's financial account information need not be entered again with the payment service.
  • the second party's mobile device 100 number is entered in the first party's mobile device 100. In response, funds are transferred from the first party to an account of the second party.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Finance (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Economics (AREA)
  • Development Economics (AREA)
  • Microelectronics & Electronic Packaging (AREA)
  • Telephonic Communication Services (AREA)
  • Information Transfer Between Computers (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

Une méthode de paiement d'une seconde partie est divulguée. Une première partie accède aux noms d'une ou plusieurs secondes parties qualifiées. Les secondes parties qualifiées sont des secondes parties qui, (i) sont associées avec le service de paiement, et (ii) si elles n'ont pas établi d'association avec le service de paiement en ont établi une avant le paiement. La première partie est associée avec le service de paiement. Un onglet est ouvert par la première partie, qui peut être sélectionné par la seconde partie qualifiée, à n'importe quel emplacement géographique d'un premier dispositif mobile de la première partie. La seconde partie qualifiée est apte à débiter un compte financier de la première partie seulement lorsque le dispositif mobile de la première partie se trouve dans une zone géographique définie. L'onglet est un lien entre la première partie, le service de paiement et la seconde partie qualifiée. La seconde partie qualifiée peut engager une transaction financière avec la première partie lorsqu'elle se trouve dans la zone géographique définie.
PCT/US2011/055387 2010-10-13 2011-10-07 Méthode de paiement avec un service de paiement et des onglets sélectionnés par une première partie et ouverts par une seconde partie à n'importe quel emplacement géographique du dispositif mobile de la première partie WO2012051071A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CA2812611A CA2812611C (fr) 2010-10-13 2011-10-07 Methode de paiement avec un service de paiement et des onglets selectionnes par une premiere partie et ouverts par une seconde partie a n'importe quel emplacement geographique du dispositif mobile de la premiere partie
JP2013533898A JP2014500537A (ja) 2010-10-13 2011-10-07 決済サービスと第一者により選択されて第一者のモバイルデバイスのいずれかの地理的位置で第二者により開かれたタブとを用いる支払方法
EP11833173.5A EP2628140A4 (fr) 2010-10-13 2011-10-07 Méthode de paiement avec un service de paiement et des onglets sélectionnés par une première partie et ouverts par une seconde partie à n'importe quel emplacement géographique du dispositif mobile de la première partie

Applications Claiming Priority (24)

Application Number Priority Date Filing Date Title
US12/903,753 US20110084139A1 (en) 2009-10-13 2010-10-13 Systems and methods for financial transaction through miniaturized card reader
US12/903,823 US8534546B2 (en) 2009-10-13 2010-10-13 Systems and methods for card present transaction without sharing card information
US12/903,823 2010-10-13
US12/903,753 2010-10-13
US12/985,982 US8573486B2 (en) 2010-10-13 2011-01-06 Systems and methods for financial transaction through miniaturized card reader with confirmation of payment sent to buyer
US12/985,982 2011-01-06
US13/005,822 US8870070B2 (en) 2010-10-13 2011-01-13 Card reader device
US13/005,822 2011-01-13
US13/010,976 2011-01-21
US13/010,976 US9016572B2 (en) 2010-10-13 2011-01-21 Systems and methods for financial transaction through miniaturized card with ASIC
US13/012,495 US8500018B2 (en) 2010-10-13 2011-01-24 Systems and methods for financial transaction through miniaturized card reader with decoding on a seller's mobile device
US13/012,495 2011-01-24
US13/043,263 2011-03-08
US13/043,268 2011-03-08
US13/043,268 US8302860B2 (en) 2010-10-13 2011-03-08 Read head device with narrow card reading slot
US13/043,203 2011-03-08
US13/043,258 2011-03-08
US13/043,270 2011-03-08
US13/043,263 US8876003B2 (en) 2010-10-13 2011-03-08 Read head device with selected output jack characteristics
US13/043,203 US8573487B2 (en) 2010-10-13 2011-03-08 Integrated read head device
US13/043,270 US8235287B2 (en) 2010-10-13 2011-03-08 Read head device with slot configured to reduce torque
US13/043,258 US8870071B2 (en) 2010-10-13 2011-03-08 Read head device with selected sampling rate
US13/088,038 2011-04-15
US13/088,038 US9619797B2 (en) 2010-10-13 2011-04-15 Payment methods with a payment service and tabs selected by a first party and opened by a second party at an geographic location of the first party's mobile device

Publications (1)

Publication Number Publication Date
WO2012051071A1 true WO2012051071A1 (fr) 2012-04-19

Family

ID=45938665

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2011/055387 WO2012051071A1 (fr) 2010-10-13 2011-10-07 Méthode de paiement avec un service de paiement et des onglets sélectionnés par une première partie et ouverts par une seconde partie à n'importe quel emplacement géographique du dispositif mobile de la première partie

Country Status (4)

Country Link
EP (1) EP2628140A4 (fr)
JP (2) JP2014500537A (fr)
CA (1) CA2812611C (fr)
WO (1) WO2012051071A1 (fr)

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2014036332A (ja) * 2012-08-08 2014-02-24 Beatrobo Inc 接続デバイス、アプリケーションプログラムおよびコンテンツ取得システム
US9436955B2 (en) 2009-06-10 2016-09-06 Square, Inc. Methods for transferring funds using a payment service where financial account information is only entered once with a payment service and need not be re-entered for future transfers
US9619797B2 (en) 2010-10-13 2017-04-11 Square, Inc. Payment methods with a payment service and tabs selected by a first party and opened by a second party at an geographic location of the first party's mobile device
US9985699B1 (en) 2014-12-16 2018-05-29 Blazer and Flip Flops, Inc. NFC center
US10262318B1 (en) 2014-12-17 2019-04-16 Blazer and Flip Flops, Inc. Eligibility verification for real-time offers
US10262311B1 (en) 2014-12-17 2019-04-16 Blazer and Flip Flops, Inc. NFC-based payments tagging
US10410021B1 (en) 2017-12-08 2019-09-10 Square, Inc. Transaction object reader with digital signal input/output and internal audio-based communication
US10580011B1 (en) 2014-12-17 2020-03-03 Blazer and Flip Flops, Inc. NFC-based options selection
US10679207B1 (en) 2014-12-17 2020-06-09 Blazer and Flip Flops, Inc. Bill splitting and account delegation for NFC
US11062375B1 (en) 2014-12-17 2021-07-13 Blazer and Flip Flops, Inc. Automatic shopping based on historical data
US11087301B1 (en) 2017-12-19 2021-08-10 Square, Inc. Tamper resistant device

Citations (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4609957A (en) * 1982-02-15 1986-09-02 Crouzet Magnetic card reader-encoder apparatus
US5603078A (en) * 1995-09-15 1997-02-11 Spectravision, Inc. Remote control device with credit card reading and transmission capabilities having multiple IR LEDs
US20040087339A1 (en) * 2002-10-30 2004-05-06 Scott Goldthwaite Mobile communication device equipped with a magnetic stripe reader
US20050209719A1 (en) * 1998-01-07 2005-09-22 Microsoft Corporation Vehicle computer system with audio entertainment system
US20050247787A1 (en) * 2002-02-12 2005-11-10 Clay Von Mueller Magnetic stripe reader with power management control for attachment to a PDA device
US20070255620A1 (en) 2006-03-30 2007-11-01 Obopay Inc. Transacting Mobile Person-to-Person Payments
US20080103972A1 (en) * 2006-10-25 2008-05-01 Payfont Limited Secure authentication and payment system
US20080275779A1 (en) * 2007-02-12 2008-11-06 Dhamodharan Lakshminarayanan Mobile payment services
US20090144161A1 (en) * 2007-11-30 2009-06-04 Mobile Candy Dish, Inc. Method and system for conducting an online payment transaction using a mobile communication device
US20090187492A1 (en) * 2007-10-25 2009-07-23 Ayman Hammad Location based authentication
US20100108762A1 (en) 2009-06-10 2010-05-06 Morley Jr Robert E Card reader device for a cell phone and method of use
WO2010111130A2 (fr) 2009-03-25 2010-09-30 George Wallner Lecteur de carte couplé de manière audio/acoustique

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001357337A (ja) * 2000-04-12 2001-12-26 Pioneer Electronic Corp 携帯型端末装置を利用した取引処理装置及び方法、並びに顧客認定装置及び方法
JP2003242428A (ja) * 2002-02-19 2003-08-29 Fujitsu Frontech Ltd カード機能付携帯電話機及び決済機能付携帯電話機
JP2006004264A (ja) * 2004-06-18 2006-01-05 Hitachi Ltd 携帯情報端末及び携帯情報端末を用いた電子決済方法
JP2006127390A (ja) * 2004-11-01 2006-05-18 Glory Ltd 携帯電話端末を利用したデビット決済システム及び方法
US8103022B2 (en) * 2006-11-30 2012-01-24 Broadcom Corporation Method and system for detecting, and controlling power for, an auxiliary microphone
KR101151059B1 (ko) * 2007-05-11 2012-06-01 에스케이플래닛 주식회사 Ｒｆｉｄ를 이용한 원격 주문 방법 및 그 시스템
JP2009205196A (ja) * 2008-02-26 2009-09-10 Nec Corp 通信情報処理端末
US7896248B2 (en) * 2009-06-10 2011-03-01 Rem Holdings 3, Llc Card reader device and method of use

Patent Citations (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4609957A (en) * 1982-02-15 1986-09-02 Crouzet Magnetic card reader-encoder apparatus
US5603078A (en) * 1995-09-15 1997-02-11 Spectravision, Inc. Remote control device with credit card reading and transmission capabilities having multiple IR LEDs
US20050209719A1 (en) * 1998-01-07 2005-09-22 Microsoft Corporation Vehicle computer system with audio entertainment system
US20050247787A1 (en) * 2002-02-12 2005-11-10 Clay Von Mueller Magnetic stripe reader with power management control for attachment to a PDA device
US20040087339A1 (en) * 2002-10-30 2004-05-06 Scott Goldthwaite Mobile communication device equipped with a magnetic stripe reader
US20070255620A1 (en) 2006-03-30 2007-11-01 Obopay Inc. Transacting Mobile Person-to-Person Payments
US20080103972A1 (en) * 2006-10-25 2008-05-01 Payfont Limited Secure authentication and payment system
US20080275779A1 (en) * 2007-02-12 2008-11-06 Dhamodharan Lakshminarayanan Mobile payment services
US20090187492A1 (en) * 2007-10-25 2009-07-23 Ayman Hammad Location based authentication
US20090144161A1 (en) * 2007-11-30 2009-06-04 Mobile Candy Dish, Inc. Method and system for conducting an online payment transaction using a mobile communication device
WO2010111130A2 (fr) 2009-03-25 2010-09-30 George Wallner Lecteur de carte couplé de manière audio/acoustique
US20100108762A1 (en) 2009-06-10 2010-05-06 Morley Jr Robert E Card reader device for a cell phone and method of use

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2628140A4 *

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9436955B2 (en) 2009-06-10 2016-09-06 Square, Inc. Methods for transferring funds using a payment service where financial account information is only entered once with a payment service and need not be re-entered for future transfers
US9619797B2 (en) 2010-10-13 2017-04-11 Square, Inc. Payment methods with a payment service and tabs selected by a first party and opened by a second party at an geographic location of the first party's mobile device
US9609455B2 (en) 2012-08-08 2017-03-28 Beatrobo, Inc. Connective device, application program and content retrieval system
JP2014036332A (ja) * 2012-08-08 2014-02-24 Beatrobo Inc 接続デバイス、アプリケーションプログラムおよびコンテンツ取得システム
US10348368B2 (en) 2014-12-16 2019-07-09 Blazer and Flip Flops, Inc. Managing NFC devices based on downloaded data
US9985699B1 (en) 2014-12-16 2018-05-29 Blazer and Flip Flops, Inc. NFC center
US10944448B2 (en) 2014-12-16 2021-03-09 Blazer and Flip Flops, Inc. Managing NFC devices based on downloaded data
US11004058B2 (en) 2014-12-17 2021-05-11 Blazer and Flip Flops, Inc. Transaction modification based on real-time offers
US10580011B1 (en) 2014-12-17 2020-03-03 Blazer and Flip Flops, Inc. NFC-based options selection
US10679207B1 (en) 2014-12-17 2020-06-09 Blazer and Flip Flops, Inc. Bill splitting and account delegation for NFC
US10262311B1 (en) 2014-12-17 2019-04-16 Blazer and Flip Flops, Inc. NFC-based payments tagging
US10262318B1 (en) 2014-12-17 2019-04-16 Blazer and Flip Flops, Inc. Eligibility verification for real-time offers
US11062375B1 (en) 2014-12-17 2021-07-13 Blazer and Flip Flops, Inc. Automatic shopping based on historical data
US11062288B2 (en) 2014-12-17 2021-07-13 Blazer and Flip Flops, Inc. Securing contactless payment
US10410021B1 (en) 2017-12-08 2019-09-10 Square, Inc. Transaction object reader with digital signal input/output and internal audio-based communication
US11100298B1 (en) 2017-12-08 2021-08-24 Square, Inc. Transaction object reader with analog and digital signal interface
US11087301B1 (en) 2017-12-19 2021-08-10 Square, Inc. Tamper resistant device

Also Published As

Publication number Publication date
CA2812611A1 (fr) 2012-04-19
EP2628140A1 (fr) 2013-08-21
CA2812611C (fr) 2016-06-14
EP2628140A4 (fr) 2014-05-21
JP2014500537A (ja) 2014-01-09
JP2017033603A (ja) 2017-02-09

Similar Documents

Publication Publication Date Title
US8662389B2 (en) Payment methods with a payment service and tabs selected by a first party and opened by a second party at any geographic location of the first party's mobile device
US9436955B2 (en) Methods for transferring funds using a payment service where financial account information is only entered once with a payment service and need not be re-entered for future transfers
US8840024B2 (en) Systems and methods for financial transaction through miniaturized card reader with decoding on a seller's mobile device
US8573487B2 (en) Integrated read head device
US8876003B2 (en) Read head device with selected output jack characteristics
US8302860B2 (en) Read head device with narrow card reading slot
US8573486B2 (en) Systems and methods for financial transaction through miniaturized card reader with confirmation of payment sent to buyer
US8235287B2 (en) Read head device with slot configured to reduce torque
US9454866B2 (en) Method of conducting financial transactions where a payer's financial account information is entered only once with a payment system
US8870071B2 (en) Read head device with selected sampling rate
CA2812251C (fr) Dispositif de tete de lecture a fente configure pour reduire le couple
US20120095871A1 (en) Method for conducting on-line purchases using a mobile device and a payment service
US20110084131A1 (en) Systems and methods for card present transaction without sharing card information
CA2812611C (fr) Methode de paiement avec un service de paiement et des onglets selectionnes par une premiere partie et ouverts par une seconde partie a n'importe quel emplacement geographique du dispositif mobile de la premiere partie

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11833173

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2812611

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 2011833173

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2013533898

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE