US20150324777A1 - Payment system and method - Google Patents

Payment system and method Download PDF

Info

Publication number
US20150324777A1
US20150324777A1 US14/442,036 US201314442036A US2015324777A1 US 20150324777 A1 US20150324777 A1 US 20150324777A1 US 201314442036 A US201314442036 A US 201314442036A US 2015324777 A1 US2015324777 A1 US 2015324777A1
Authority
US
United States
Prior art keywords
mobile device
fee
code
server
identifier
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US14/442,036
Inventor
Martin Paul Moshal
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Gelliner Ltd
Original Assignee
Gelliner Ltd
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
Application filed by Gelliner Ltd filed Critical Gelliner Ltd
Priority claimed from PCT/GB2013/052978 external-priority patent/WO2014072751A1/en
Assigned to GELLINER LIMITED reassignment GELLINER LIMITED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MOSHAL, MARTIN PAUL
Publication of US20150324777A1 publication Critical patent/US20150324777A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/20—Point-of-sale [POS] network systems
    • G06Q20/208—Input by product or record sensing, e.g. weighing or scanner processing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
    • G06F16/9554—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL] by using bar codes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
    • G06F16/9566—URL specific, e.g. using aliases, detecting broken or misspelled links
    • G06F17/30879—
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G06F21/313—User authentication using a call-back technique via a telephone network
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K19/00—Record carriers for use with machines and with at least a part designed to carry digital markings
    • G06K19/06—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code
    • G06K19/06009—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code with optically detectable marking
    • G06K19/06037—Record carriers for use with machines and with at least a part designed to carry digital markings characterised by the kind of the digital marking, e.g. shape, nature, code with optically detectable marking multi-dimensional coding
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K7/00—Methods or arrangements for sensing record carriers, e.g. for reading patterns
    • G06K7/10—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation
    • G06K7/14—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation using light without selection of wavelength, e.g. sensing reflected white light
    • G06K7/1404—Methods for optical code recognition
    • G06K7/1408—Methods for optical code recognition the method being specifically adapted for the type of code
    • G06K7/1417—2D bar codes
    • 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
    • G06Q20/102—Bill distribution or payments
    • 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/12—Payment architectures specially adapted for electronic shopping 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/08—Payment architectures
    • G06Q20/14—Payment architectures specially adapted for billing 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/08—Payment architectures
    • G06Q20/14—Payment architectures specially adapted for billing systems
    • G06Q20/145—Payments according to the detected use or quantity
    • 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/22—Payment schemes or models
    • G06Q20/223—Payment schemes or models based on the use of peer-to-peer networks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322—Aspects of commerce using mobile devices [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/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/325—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks
    • G06Q20/3255—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks using mobile network messaging services for payment, e.g. SMS
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/326—Payment applications installed on the mobile devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/327—Short range or proximity payments by means of M-devices
    • G06Q20/3276—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being read by the M-device
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of 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/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/387—Payment using discounts or coupons
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4014—Identity check for transactions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/42—Confirmation, e.g. check or permission by the legal debtor of payment
    • G06Q20/425—Confirmation, e.g. check or permission by the legal debtor of payment using two different networks, one for transaction and one for security confirmation
    • 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
    • G06Q30/00—Commerce
    • G06Q30/018—Certifying business or products
    • G06Q30/0185—Product, service or business identity fraud
    • 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
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • 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
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
    • G06Q30/0225—Avoiding frauds
    • 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
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • 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
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0609—Buyer or seller confidence or verification
    • 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
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
    • H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0861—Generation of secret information including derivation or calculation of cryptographic keys or passwords
    • 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
    • G06Q2220/00—Business processing using cryptography
    • G06Q2220/10—Usage protection of distributed data files

Definitions

  • a parking lot (e.g., a parkade) is an area where motor vehicles may be parked.
  • a parking lot may be fee-based such that a motor vehicle may be permitted to park in the lot in exchange for payment of a fee.
  • this fee is based on a time period in which the vehicle is parked in the lot.
  • a driver of the vehicle may receive a time-stamped ticket from an entry terminal. Before the driver leaves the lot with the vehicle, the driver may be required to insert the ticket into a payment terminal, which may determine a fee (e.g., based on the amount of time that has passed since the driver received the ticket). The driver may then pay the fee, either by providing cash or a payment instrument such as a credit card or debit card into the payment terminal. The payment terminal may then validate the ticket and return it to the driver. To exit the parking lot, the driver may drive up to an exit terminal and insert the validated ticket into the exit terminal. The exit terminal may confirm that the ticket has been validated, and in response, the exit terminal may cause a boom to rise so as to allow the driver's vehicle to exit the parking lot.
  • a fee e.g., based on the amount of time that has passed since the driver received the ticket.
  • the driver may then pay the fee, either by providing cash or a payment instrument such as a credit card or debit card into the payment terminal.
  • the payment terminal
  • the payment terminal may be located at or near a pedestrian entrance to the parking lot.
  • queues at the payment terminal may be lengthy, particularly at peak times, thus causing delay and leading to driver impatience and frustration.
  • the payment terminal may be out of service or may have insufficient cash to provide correct change, thereby further exacerbating these problems.
  • the need for the driver to handle cash or payment instruments in a public environment may cause safety concerns.
  • a payment terminal may be integrated with the exit terminal, which may allow a driver to pay the fee while sitting in the vehicle just before exiting the parking lot.
  • a payment terminal may be integrated with the exit terminal, which may allow a driver to pay the fee while sitting in the vehicle just before exiting the parking lot.
  • the lengthy queues of vehicles can cause high levels of emissions in a relatively small area, which may be undesirable for health reasons.
  • an example embodiment takes the form of a method comprising (i) a mobile device capturing a code disposed on a medium, wherein the code encodes an identifier; (ii) the mobile device decoding the captured code to recover the identifier; (iii) the mobile device transmitting to a server via a communication network the recovered identifier; (iv) the mobile device receiving from the server via the communication network a fee associated with the transmitted identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time; and (v) the mobile device transmitting authorization to pay the received fee.
  • an example embodiment takes the form of a mobile device.
  • the mobile device is configured for: (i) capturing a code disposed on a medium, wherein the code encodes an identifier; (ii) decoding the captured code to recover the identifier; (iii) transmitting to a server via a communication network the recovered identifier; (iv) receiving from the server via the communication network a fee associated with the transmitted identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time; and (v) transmitting authorization to pay the received fee.
  • an example embodiment takes the form of a non-transitory computer-readable medium having stored thereon program instructions that, when executed by a processor, cause performance of a set of functions comprising: (i) a mobile device capturing a code disposed on a medium, wherein the code encodes an identifier; (ii) the mobile device decoding the captured code to recover the identifier; (iii) the mobile device transmitting to a server via a communication network the recovered identifier; (iv) the mobile device receiving from the server via the communication network a fee associated with the transmitted identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time; and (v) the mobile device transmitting authorization to pay the received fee.
  • an example embodiment takes the form of a method comprising (i) a server receiving from a mobile device via a communication network the identifier; (ii) responsive to the server receiving the identifier, the server determining a fee associated with the identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time; (iii) the server transmitting to the mobile device via the communication network the determined fee; (iv) the server receiving from the mobile device via the communication network authorization to pay the determined fee; (v) the server determining that the determined fee has been paid; and (vi) responsive to the server determining that the determined fee has been paid, the server transmitting an indication that the determined fee has been paid.
  • an example embodiment takes the form of a server.
  • the server is configured for: (i) receiving from a mobile device via a communication network the identifier; (ii) responsive to receiving the identifier, determining a fee associated with the identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time; (iii) transmitting to the mobile device via the communication network the determined fee; (iv) receiving from the mobile device via the communication network authorization to pay the determined fee; (v) determining that the determined fee has been paid; and (vi) responsive to determining that the determined fee has been paid, transmitting an indication that the determined fee has been paid.
  • an example embodiment takes the form of a non-transitory computer-readable medium having stored thereon program instructions that, when executed by a processor, cause performance of a set of functions comprising: (i) a server receiving from a mobile device via a communication network the identifier; (ii) responsive to the server receiving the identifier, the server determining a fee associated with the identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time; (iii) the server transmitting to the mobile device via the communication network the determined fee; (iv) the server receiving from the mobile device via the communication network authorization to pay the determined fee; (v) the server determining that the determined fee has been paid; and (vi) responsive to the server determining that the determined fee has been paid, the server transmitting an indication that the determined fee has been paid.
  • an example embodiment takes the form of a method comprising (i) a mobile device capturing a code disposed on a medium, wherein the code encodes an identifier; (ii) the mobile device decoding the captured code to recover the identifier; (iii) the mobile device transmitting to a server via a communication network the recovered identifier; (iv) the mobile device receiving from the server via the communication network a fee associated with the transmitted identifier, wherein the fee is a function of at least a distance between a first location and a second location that is different than the first location; and (v) the mobile device transmitting authorization to pay the received fee.
  • an example embodiment takes the form of a mobile device.
  • the mobile device is configured for: (i) capturing a code disposed on a medium, wherein the code encodes an identifier; (ii) decoding the captured code to recover the identifier; (iii) transmitting to a server via a communication network the recovered identifier; (iv) receiving from the server via the communication network a fee associated with the transmitted identifier, wherein the fee is a function of at least a distance between a first location and a second location that is different than the first location; and (v) transmitting authorization to pay the received fee.
  • an example embodiment takes the form of a non-transitory computer-readable medium having stored thereon program instructions that, when executed by a processor, cause performance of a set of functions comprising: (i) a mobile device capturing a code disposed on a medium, wherein the code encodes an identifier; (ii) the mobile device decoding the captured code to recover the identifier; (iii) the mobile device transmitting to a server via a communication network the recovered identifier; (iv) the mobile device receiving from the server via the communication network a fee associated with the transmitted identifier, wherein the fee is a function of at least a distance between a first location and a second location that is different than the first location; and (v) the mobile device transmitting authorization to pay the received fee.
  • an example embodiment takes the form of a method comprising (i) a server receiving from a mobile device via a communication network the identifier; (ii) responsive to the server receiving the identifier, the server determining a fee associated with the identifier, wherein the fee is a function of at least a distance between a first location and a second location that is different than the first location; (iii) the server transmitting to the mobile device via the communication network the determined fee; (iv) the server receiving from the mobile device via the communication network authorization to pay the determined fee; (v) the server determining that the determined fee has been paid; and (vi) responsive to the server determining that the determined fee has been paid, the server transmitting an indication that the determined fee has been paid.
  • an example embodiment takes the form of a server.
  • the server is configured for: (i) receiving from a mobile device via a communication network the identifier; (ii) responsive to receiving the identifier, determining a fee associated with the identifier, wherein the fee is a function of at least a distance between a first location and a second location that is different from the first location; (iii) transmitting to the mobile device via the communication network the determined fee; (iv) receiving from the mobile device via the communication network authorization to pay the determined fee; (v) determining that the determined fee has been paid; and (vi) responsive to determining that the determined fee has been paid, transmitting an indication that the determined fee has been paid.
  • an example embodiment takes the form of a non-transitory computer-readable medium having stored thereon program instructions that, when executed by a processor, cause performance of a set of functions comprising: (i) a server receiving from a mobile device via a communication network the identifier; (ii) responsive to the server receiving the identifier, the server determining a fee associated with the identifier, wherein the fee is a function of at least a distance between a first location and a second location that is different than the first location; (iii) the server transmitting to the mobile device via the communication network the determined fee; (iv) the server receiving from the mobile device via the communication network authorization to pay the determined fee; (v) the server determining that the determined fee has been paid; and (vi) responsive to the server determining that the determined fee has been paid, the server transmitting an indication that the determined fee has been paid.
  • an example embodiment takes the form of a method comprising (i) scanning, using a mobile device, a quick response (QR) code that encodes a unique ticket code that identifies a parking ticket for using a parkade; (ii) decoding, using the mobile device, the QR code to recover the unique ticket code; (iii) transmitting from the mobile device to an application server the unique ticket code; (iv) receiving, at the mobile device, a parking fee for using the parkade, and displaying, on the mobile device, the parking fee; (v) selecting, using the mobile device, a payment instrument for paying the parking fee, and authorizing the parking fee for payment; (vi) transmitting from the mobile device to the application server data pertaining to the payment instrument; and (vii) receiving, at the mobile device from an application server, status data indicating whether the parking fee was successfully or unsuccessfully paid.
  • QR quick response
  • an example embodiment takes the form of a mobile device comprising: (i) a processor; (ii) a camera configured to capture a quick response (QR) code that encodes a unique ticket code that identifies a parking ticket for using a parkade; (iii) a non-transitory computer-readable data storage device comprising computer-readable program instructions, wherein the program instructions are executable by the processor to decode the QR code; (iv) a user interface configured to display a parking fee for using the parkade and to allow a user to select a payment instrument for an attempt at paying the parking fee and to authorize a parking fee for payment; and (v) a network interface; (vi) wherein the network interface is configured to transmit, to an application server, the unique ticket code and data pertaining to the payment instrument; and (vii) wherein the network interface is configured to receive, from an application server, status data indicating whether the initial attempt at paying the fee was successful or unsuccessful.
  • QR quick response
  • an example embodiment takes the form of a method comprising: (i) receiving, at an application server from a mobile device, a unique ticket code that identifies a parking ticket for using a parkade; (ii) determining, at the application server, a parking fee for using the parkade; (iii) transmitting, from the application server to the mobile device, the parking fee; (iv) receiving, at the application server from the mobile device, data pertaining to a payment instrument selected for an attempt at paying the fee; (v) determining, at the application server, whether processing the data pertaining to the parking fee and the data pertaining to the first payment instrument results in successful or unsuccessful payment of the parking fee; and (vi) transmitting, from the application server to the mobile device, status data indicating whether the attempt at paying the parking fee was successful or unsuccessful.
  • an example embodiment takes the form of an application server system comprising: (i) a processor; (ii) a non-transitory computer-readable data storage device comprising computer-readable program instructions; and (iii) a network interface; (iv) wherein the network interface is configured to receive, from a mobile device, (1) a unique ticket code that identifies a parking ticket for using a parkade, and, (2) data pertaining to a payment instrument selected for an attempt at paying a parking fee for using the parkade; and (iv) wherein the program instructions are executable by the processor to determine whether processing the parking fee and the data pertaining to the payment instrument results in successful or unsuccessful payment of the parking fee; (v) wherein the program instructions are executable by the processor to cause the network interface to transmit status data to the mobile device; and (vi) wherein the status data indicates whether the attempt at paying the parking fee was successful or unsuccessful.
  • an example embodiment takes the form of a method comprising: (i) providing, at a parkade, a parking ticket for using the parkade; and (ii) providing, at the parkade, a quick response (QR) code that encodes a unique ticket number that identifies the parking ticket.
  • QR quick response
  • FIG. 1 is a schematic representation of a system for paying a fee in accordance with an example embodiment
  • FIG. 2 illustrates an example quick response (QR) code
  • FIG. 3 is a block diagram of a mobile device in accordance with an example embodiment
  • FIG. 4 is a block diagram of an application server in accordance with an example embodiment
  • FIG. 5A is a first part of a flow chart of functions of a method in accordance with an example embodiment
  • FIG. 5B is a second part of the flow chart of FIG. 5A ;
  • FIG. 5C is a third part of the flow chart of FIG. 5A ;
  • FIG. 6 illustrates a display of a mobile device in accordance with an example embodiment
  • FIG. Figure
  • FIGS. Figures
  • FIG. 1 is a schematic representation of a system 100 for paying a fee in accordance with an example embodiment.
  • the system 100 is described in connection with a parking lot. However, as described further below, the system 100 may be used in connection with other environments as well.
  • the system 100 includes an application server 102 , an entry or dispenser terminal 104 , a mobile device 106 , an exit terminal 108 , a payment processing server 110 , and a parking record database 112 .
  • the dispenser terminal 104 may be configured to dispense a medium to a user, such as a driver of a vehicle. In some instances, in response to a vehicle entering the parking lot, the dispenser terminal 104 may dispense the medium.
  • the medium may take a variety of forms. For example, the medium may take the form of a paper ticket or a token.
  • the medium may have disposed thereon a code that encodes a session identifier.
  • the code may take a variety of forms.
  • the code may take the form of a one-dimensional code such as a linear barcode, or a two-dimensional code such as a QR code.
  • the session identifier may uniquely identify a particular parking session, that is, a given instance of a vehicle parking in the parking lot.
  • the session identifier can take a variety of forms.
  • the session identifier may be a numeric or an alphanumeric code.
  • the code can also encode other data, including for example a time or a parking lot identifier.
  • the dispenser terminal 104 may be configured to print the code on the medium (or otherwise cause the code to be disposed on the medium) proximate (i.e., at or about) the time that the medium is dispensed.
  • an event is proximate a time if the event and the time are within a threshold number of seconds of each other.
  • the threshold may be, for example, five seconds, ten seconds, or twenty seconds.
  • the medium may already have a code disposed thereon when it is loaded into the dispenser terminal 104 .
  • the dispenser terminal 104 may be operatively connected to the application server 102 , and may further be configured to transmit to the application server 102 the session identifier encoded in the code and/or a time that generally indicating a time the vehicle entered the parking lot.
  • time refers to a time and/or date.
  • the application server 102 may be configured to store the received session identifier and the time in a parking record database 112 as described in greater detail below.
  • the exit device 108 may be configured to regulate the exiting of vehicles out of the parking lot and may include or be integrated with an access control device, which may take a variety of forms.
  • the access control device may take the form of a boom mechanism that is configured to move between a low position, thereby obstructing vehicles from exiting the lot, and a high position, thereby permitting vehicles to exit the lot.
  • the exit device 108 may raise and lower the boom.
  • control access device may be used to regulate the entry of vehicles into the lot and the exiting of vehicles out of the lot.
  • separate control access devices may be used for each purpose.
  • the exit terminal 108 may be operatively connected to the application server 102 .
  • the application server 102 , the mobile device 106 and the payment processing server 110 can communicate with each other by means of a communication network 116 .
  • the communication network 116 can take a variety of forms.
  • the communication network 116 may take the form of a local-area network or a wide-area network, such as the world-wide web or the Internet.
  • the communication network 116 may be supported by wired or wireless interfaces (e.g., interfaces configured to communicate using a Wi-Fi or Bluetooth protocol, for instance).
  • other devices in the system 100 may also communicate with each other via a communication network. Communication between any such devices may be facilitated by corresponding network interfaces.
  • Communication between the application server 102 , the mobile device 106 and the payment processing server 110 can be facilitated by using a server-hosted program that is installed on the application server 102 , a payment application program (a “payment app”) that is installed and executed on the mobile device 106 , and a processing application program (a “processing app”) that is installed and executed on the payment processing server 110 .
  • a server-hosted program that is installed on the application server 102
  • a payment application program (a “payment app”) that is installed and executed on the mobile device 106
  • processing application program a “processing app”
  • a user can download a copy of the payment app from a download repository, for example, from a data storage device 188 of the application server 102 ( FIG. 4 ) and install the payment app on the mobile device 106 .
  • the payment app may create a user profile 114 on the mobile device 106 and prompt the user to manually provide certain attributes such as, the user's first name, the user's last name, an e-mail address, a physical address and particulars of one or more payment instruments such as credit cards, debit cards, e-wallets and the like.
  • the user profile 114 may be stored locally on the mobile device 106 and not passed to the application server 102 .
  • the payment app may facilitate the performance of a variety of functions, including but not limited to the functions of capturing a code that encodes a session identifier, decoding the captured code to recover the session identifier, transmitting to a server the recovered session identifier, receiving from the server a fee associated with the recovered session identifier, and providing to the server authorization to pay the fee.
  • FIG. 2 illustrates an example QR code 200 .
  • a QR code is a two-dimensional code.
  • the example embodiments may use any of a variety of two-dimensional codes, such as an Aztec barcode, a codablock F code, a code16K barcode, a code49 barcode, a data-matrix barcode, a micro PDF417 barcode, a QR code, a micro QR code or some other two-dimensional code.
  • the example embodiments may use a one-dimensional code, such as a barcode in which only a width of each bar is used to decode the barcode.
  • FIG. 3 is a block diagram depicting an example embodiment of mobile device 106 .
  • the mobile device 106 includes (i) a processor 150 , (ii) a network interface 152 for transmitting data to and receiving data from communication network 116 , (iii) a user interface 154 , (iv) a camera (or other capture device) 156 configured to capture a code such as a QR code, and (v) a data storage device 158 , all of which can be linked together via a system bus or other connection mechanism 160 .
  • Data storage device 158 includes computer-readable program instructions (CRPI) 162 , the payment app 164 , and a user profile 114 .
  • CRPI 162 can include the payment app 164 .
  • Data storage device 158 can comprise a non-transitory computer-readable storage medium readable by processor 150 .
  • Each computer-readable storage medium described herein can comprise volatile and/or non-volatile storage components, such as optical, magnetic, organic or other memory or disc storage, which can be integrated in whole or in part with a processor.
  • Each processor described herein can comprise one or more general purpose processors (for example, INTEL single core microprocessors or INTEL multicore microprocessors) or one or more special purpose processors (for example, digital signal processors).
  • Processor 150 is configured to execute CRPI 162 and the payment app 164 .
  • Mobile device 106 can be configured as or comprise a cellular phone, a smartphone, a tablet device, or some other device arranged to carry out cellular communications.
  • communication network 116 can comprise a cellular communication network, such as a network for carrying out communications according to the 4G Long Term Evolution (LTE) standard developed by the 3 rd Generation Partnership Project (3GPP), or some other communication standard developed for a cellular communication network.
  • LTE Long Term Evolution
  • 3GPP 3 rd Generation Partnership Project
  • FIG. 4 is a block diagram depicting an example embodiment of the application server 102 .
  • application server 102 can include (i) a processor 182 , (ii) a network interface 184 for transmitting data to and receiving data from communication network 116 , (iii) a user interface 186 , and (iv) a data storage device 188 , all of which can be linked together via a system bus or other connection mechanism 190 .
  • Data storage device 188 can include (i) CRPI 192 , and (ii) the payment app 194 (which may be the same as the payment app 164 ) to be downloaded by the mobile device 106 .
  • CRPI 192 can include the payment app 194 .
  • Data storage device 188 can comprise a non-transitory computer-readable storage medium readable by processor 182 .
  • Processor 182 is configured to execute CRPI 192 .
  • the system 100 can be used to pay a fee.
  • the following example describes an example use of the system 100 in connection with a user who wishes to pay a parking lot fee.
  • the system 100 may be used in connection with users who wish to pay other types of fees as well.
  • FIGS. 5A-5C shows a flow chart depicting a set of functions of a method in accordance with an example embodiment.
  • the set of functions are shown within blocks 502 through 548 . A description of those blocks now follows.
  • the method may involve the dispenser terminal 104 dispensing a medium having a code disposed thereon, wherein the code encodes a session identifier.
  • the method may involve the mobile device 106 capturing the code disposed on the medium. This may involve the mobile device 106 using the camera 156 and the payment app 164 to capture the code.
  • the method may involve the mobile device 106 decoding the captured code to recover the session identifier. This may involve the mobile device 106 using the payment app 164 to decode the captured code and to recover the session identifier.
  • the mobile device 106 may determine that the captured code has a particular property, and in responsive the mobile device 106 may automatically launch an application, such as the payment app 164 .
  • the captured code having the particular property may involve the capture code having a particular set of data (e.g., the string “launch_payment_app” encoded therein.
  • the method may involve the mobile device 106 transmitting to the application server 102 via the communication network 116 the recovered session identifier.
  • the method may involve the application server 102 receiving from the mobile device 106 via the communication network 116 the transmitted session identifier.
  • the method may involve the application server 102 determining a fee associated with the received session identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time.
  • the first time is proximate a time when the vehicle enters the parking lot.
  • the application server 102 may determine the first time in a variety of ways. For example, the dispenser terminal 104 may determine the first time to be a time when the dispenser terminal 104 dispenses the medium. The dispenser terminal 104 may then transmit the first time to the application server 102 together with the session identifier. In another example, the application server 102 may determine the first time to be a time when the application server 102 receives the session identifier from the dispenser terminal 104 . In either of the two examples described above, the application server 102 may store in the parking record database 112 the received session identifier together with the received first time. Therefore, the act of the application server 102 determining the fee associated with the received session identifier may involve the application server 102 using the received session identifier to retrieve the corresponding first time from the parking record database 112 .
  • the second time is proximate a time when the driver is in the process of paying the fee and/or exiting the parking lot.
  • the application server 102 may determine the second time in a variety of ways. For example, the mobile device 106 may determine the second time to be a time when the mobile device 106 (i) captures the code, (ii) decodes the captured code to recover the session identifier, or (iii) transmits to the application server 102 the recovered session identifier. The mobile device 106 may then transmit the second time to the application server 102 together with the session identifier. In another example, the application server 102 may determine the second time to be a time when the application server 102 receives the session identifier from the mobile device 106 .
  • the application server 102 may store in the parking record database 112 the received session identifier together with the received second time.
  • the act of the application server 102 determining the fee associated with the received session identifier may involve the application server 102 using the received session identifier to retrieve the corresponding second time from the parking record database 112 .
  • the fee may be a function of at least the time period.
  • the application server 102 may use a look-up table (e.g., that is stored in a data storage of the application server 102 ) to determine the fee based on the time period.
  • the data in the look-up table may be set via a user interface by, e.g., a manager of the parking lot.
  • the fee may further be a function of other factors, including but not limited to a location of the parking lot, a time of day, week, month, or year in which the time period falls within, and the user profile.
  • the dispenser terminal 104 , the mobile device 106 , and/or another device may provide such data to the application server 102 so that the application server 102 can determine the fee by using such factors.
  • the method may involve the application server 102 transmitting to the mobile device 106 via the communication network 116 the determined fee.
  • the method may involve the mobile device 106 receiving the transmitted fee.
  • the method may involve the mobile device 106 displaying the received fee.
  • FIG. 6 shows an example screenshot 600 of a display of the mobile device 106 at block 518 .
  • the mobile device 106 may further display the first time and the second time. This allows the user to review details relating to a parking session before authorizing payment of the fee for the parking session.
  • the user may provide such authorization via the user interface 154 of the mobile device 106 .
  • the method may involve the mobile device 106 transmitting to the application server 102 via the communication network 116 authorization to pay the received fee.
  • the mobile device 106 may further transmit payment data to the application server 102 .
  • Payment data may include at least a portion of at least one of a credit card number, a debit card number, a cardholder name, a card expiry date, a card verification code, a PIN, and a mailing code associated with the cardholder, among other things.
  • the user may provide such payment data to the mobile device 106 via the user interface 154 .
  • the mobile device 106 may transmit to the application server 102 a user profile identifier, which the application server 102 may use to retrieve payment data associated with the user (e.g., stored in the user profile 114 ).
  • the application server 102 may transmit to the mobile device at least a portion of the retrieved payment data such that the mobile device 106 may display payment data options to the user. This may allow the user to select payment data (e.g., a particular payment instrument) from among the payment data options being displayed. In turn, the mobile device 106 may select such payment data and transmit the selection to the application server 102 .
  • the method may involve responsive to the application server 102 receiving authorization to pay the determined fee, the application server 102 transmitting the particulars of the fee transaction (for example the parking fee and details relating to a selected payment instrument to the payment processing server 110 for processing).
  • the application server 102 transmitting the particulars of the fee transaction (for example the parking fee and details relating to a selected payment instrument to the payment processing server 110 for processing).
  • the method may involve the application server 102 determining that the fee was paid. In some examples, the application server 102 may determine this based on the payment processing server 110 transmitting a payment status indicator to the application server 102 , for example, either successful or unsuccessful.
  • the method may involve responsive to the application server 102 determining that the fee was paid, the application server 102 updating a status of the session identifier in the parking record database 112 as paid. Further in response, at block 528 , the method may involve the application server 102 transmitting to the mobile device 106 an indication that the fee was paid.
  • the method may involve the mobile device 106 receiving the indication that the fee was paid. And in response, at block 532 , the method may involve the mobile device 106 displaying an indication that the fee was paid.
  • the application server 102 may initiate a countdown timer that indicates how much time remains until the vehicle must exit the parking lot (e.g., before incurring an additional fee). For example, the countdown timer may start at 10 or 15 minutes once initiated. In one example, the application server 102 may also communicate with the mobile device 106 to cause the mobile device 106 to display the value of the countdown timer in a dynamic or live manner.
  • the application server 102 may notify the mobile device 106 accordingly, such that the mobile device 106 may re-authorize payment of the fee, perhaps after selecting alternate payment data.
  • the driver of the vehicle may provide the code to the exit terminal 108 to gain permission to leave the parking lot with the vehicle.
  • the driver may do this by providing to the exit terminal 108 , the medium with the code disposed thereon.
  • the mobile device 106 may be configured to display the code, and therefore, the driver may provide to the exit terminal 108 the mobile device 106 with the code displayed thereon.
  • the method may involve the exit terminal 108 capturing the code. This may involve the exit terminal 108 using a camera and a payment app to capture the code.
  • the method may involve the exit terminal 108 decoding the captured code to recover the session identifier. This may involve the exit terminal 108 using a payment app to decode the captured code and to recover the session identifier.
  • the method may involve the exit terminal 108 transmitting the recovered session identifier to the application server 102 .
  • the method may involve the application server 102 receiving the transmitted session identifier.
  • the method may involve, responsive to the application server 102 receiving the transmitted session identifier, the application server 102 determining that the fee associated with the received session identifier has been paid. This may involve the application server 102 using the received session identifier to perform a lookup in the parking record database 112 to retrieve the session identifier's corresponding status.
  • the method may involve the application server 102 transmitting to the exit terminal 108 an indication that the fee has been paid.
  • the method may involve the exit terminal 108 receiving the indication that the fee has been paid.
  • the method may involve responsive to the exit terminal 108 receiving the indication that the fee has been paid, the exit terminal 108 causing an action to be performed.
  • the method may involve responsive to (i) the exit terminal 108 receiving the indication that the fee has been paid, and (ii) the exit terminal 108 determining that the countdown timer has not expired, the exit terminal causing the action to be performed.
  • the application server 102 may determine and transmit to the mobile device 106 an additional fee, and the mobile device 106 may authorize payment of that fee in a manner similar to that described above in connection with the original fee.
  • the exit terminal 108 causing an action to be performed may involve the exit terminal 108 causing an access control device to be moved.
  • the exit terminal 108 may cause the boom to be raised thereby permitting vehicles to exit the parking lot.
  • the exit terminal 108 may cause other actions to be performed.
  • the exit terminal 108 may cause tire spikes to be retracted, thereby permitting vehicles to exit the parking lot.
  • the user profile 114 may be stored on the mobile device 106 and on the application server 102 .
  • the capturing app 164 on the mobile device 106 may synchronize changes to the user profile 114 with the copy of the profile on the application server 102 as the changes occur, or periodically, or explicitly under user command.
  • the copy of the user profile on the application server 102 can then be imported to a different mobile device 106 , for example when the user changes mobile devices or in the event the user loses or damages the mobile device 106 .
  • transmission of any of the data described herein can be encrypted.
  • the application server 102 instead of the application server 102 sending the particulars of the financial transaction (for example, the fee and the payment details) to the payment processing server 110 for processing, the application server 102 can process the payment itself.
  • the only user action required to effect payment of the fee is selecting a payment instrument from the payment data associated with the user profile 114 or otherwise entering information regarding a payment instrument.
  • codes such as QR codes can enable payment of a parking lot fee to be conducted more efficiently than is possible by means of known prior art methods.
  • the user need only capture, by means of the mobile device 106 , a code disposed on a medium in order to effect payment of the parking lot fee.
  • the user is spared the tedium of having to locate a payment terminal in the parking lot, having to wait in line to use the payment terminal, and having to tender cash or a physical payment instrument such as a credit or debit card for payment.
  • the user does not face the risk of the payment terminal being out of order or out of change.
  • the user can pay the parking fee just before arriving back at the user's vehicle in the parking lot or, alternatively, when safely seated in the user's vehicle, with a clear indication of how much time remains before expiry of a countdown timer within which to exit the parking lot without an additional payment. It is anticipated that the disclosed system and method for paying parking lot fees will reduce the tedium of such payments.
  • the application server 102 can provide the exit terminal 108 , prior to the exit terminal 108 receiving the code or medium with the code for a driver to exit the parking lot, the session identifier, an indication the fee has been paid, and data identifying the countdown timer associated with the fee payment for the session identifier. Providing those items to the exit terminal 108 in this manner can allow the exit terminal 108 to confirm successful payment and timely provision of the code or the medium for the parking session more quickly.
  • an example application of the system 100 allows a user to pay a parking lot fee.
  • the system 100 may be used in connection with users who wish to pay other types of fees as well.
  • the system may allow a user to pay a fee for a travel session associated with a toll road.
  • the fee may be a function of at least a distance between a first location (e.g., where a dispenser terminal is located) and a second location (e.g., where an exit terminal is located).
  • the application server 102 may determine the first and/or second locations based on a location of the dispenser terminal 104 , a location of the exit terminal 108 , and/or a location of the mobile device 106 , any of which may transmit such locations to the application server 102 for use in determining the fee.
  • a method comprising:
  • a mobile device ( 106 ) capturing a code disposed on a medium, wherein the code encodes an identifier
  • the mobile device ( 106 ) decoding the captured code to recover the identifier
  • the mobile device ( 106 ) transmitting to a server ( 102 ) via a communication network ( 116 ) the recovered identifier;
  • the mobile device ( 106 ) receiving from the server ( 102 ) via the communication network ( 116 ) a fee associated with the transmitted identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time;
  • the mobile device ( 106 ) decoding the code to recover the first time
  • FIGS. 1 , 3 , 4 , and 5 A- 5 C the mobile device ( 106 ) transmitting to the server ( 102 ) via the communication network ( 116 ) the first time.
  • FIGS. 1 , 3 , 4 , 5 A- 5 C, and 6 the mobile device ( 106 ) displaying the received fee.
  • the mobile device ( 106 ) transmitting to the server ( 102 ) via the communication network ( 116 ) a second identifier
  • the mobile device ( 106 ) selecting payment data to facilitate payment of the received fee, wherein the payment data is associated with the second identifier.
  • the payment data comprises at least a portion of at least one of a credit card number, a debit card number, a cardholder name, a card expiry date, a card verification code, a personal identification number, and a mailing code associated with the cardholder.
  • the mobile device ( 106 ) receiving from the server ( 102 ), an indication that the fee was paid;
  • FIGS. 1 , 3 , 4 , and 5 A- 5 C responsive to the mobile device ( 106 ) receiving the indication that the fee was paid, the mobile device ( 106 ) displaying an indication that the fee was paid.
  • FIGS. 1 , 3 , 4 , and 5 A- 5 C provide the code displayed on the medium to an exit terminal.
  • FIGS. 1 , 3 , 4 , and 5 A- 5 C provide the code displayed on the medium to a capturing device.
  • the mobile device ( 106 ) determining that the captured code has a particular property
  • a mobile device ( 106 ) configured for performing the functions recited in one of examples 1-23. ( FIGS. 1 , 3 , 4 , and 5 A- 5 C).
  • a non-transitory computer-readable medium having stored thereon program instructions ( 162 ) that, when executed by a processor ( 150 ), cause performance of the functions recited in one of examples 1-23. ( FIGS. 1 , 3 , 4 , and 5 A- 5 C).
  • a method comprising:
  • a server ( 102 ) receiving from a mobile device ( 106 ) via a communication network ( 116 ) the identifier
  • the server ( 102 ) responsive to the server ( 102 ) receiving the identifier, the server ( 102 ) determining a fee associated with the identifier, wherein the fee is a function of at least a time period between a first time and a second time;
  • the server ( 102 ) transmitting to the mobile device ( 106 ) via the communication network ( 116 ) the determined fee;
  • the server ( 102 ) receiving from the mobile device ( 106 ) via the communication network ( 116 ) authorization to pay the determined fee;
  • the server ( 102 ) determining that the determined fee has been paid
  • the server ( 102 ) responsive to the server ( 102 ) determining that the determined fee has been paid, the server ( 102 ) transmitting an indication that the determined fee has been paid. ( FIGS. 1 , 3 , 4 , and 5 A- 5 C).
  • FIGS. 1 , 3 , 4 , and 5 A- 5 C the server ( 102 ) receiving from the mobile device ( 106 ) via the communication network ( 116 ) the first time.
  • the server ( 102 ) receiving from the mobile device ( 106 ) via the communication network ( 116 ) payment data to facilitate payment of the determined fee;
  • the server ( 102 ) receiving from the mobile device ( 106 ) via the communication network ( 116 ) a second identifier
  • the server ( 102 ) transmitting to the mobile device ( 106 ) via the communication network ( 116 ) an indication that the fee was paid.
  • the server ( 102 ) transmitting to an exit terminal ( 108 ) an indication that the fee was paid, wherein the exit terminal ( 108 ) is configured for: (i) receiving from the server ( 102 ) the indication that the fee was paid, and (ii) responsive to receiving from the server ( 102 ) the indication that the fee was paid, causing an action to be performed.
  • FIGS. 1 , 3 , 4 , and 5 A- 5 C FIGS. 1 , 3 , 4 , and 5 A- 5 C).
  • causing the action to be performed comprises causing the action to be performed so as to permit a vehicle to exit a parking lot.
  • causing the action to be performed comprises causing an access control device in the parking lot to be moved. ( FIGS. 1 , 3 , 4 , and 5 A- 5 C).
  • a server ( 102 ) configured for performing the functions recited in one of examples 24-41. ( FIGS. 1 , 3 , 4 , and 5 A- 5 C).
  • a method comprising:
  • a mobile device ( 106 ) capturing a code disposed on a medium, wherein the code encodes an identifier
  • the mobile device ( 106 ) decoding the captured code to recover the identifier
  • the mobile device ( 106 ) transmitting to a server ( 102 ) via a communication network ( 116 ) the recovered identifier;
  • the mobile device ( 106 ) receiving from the server ( 102 ) via the communication network ( 116 ) a fee associated with the transmitted identifier, wherein the fee is a function of at least a distance between a first location and a second location that is different from the first location;
  • the mobile device ( 106 ) decoding the code to recover the first location
  • FIGS. 1 , 3 , 4 , 5 A- 5 C, and 6 the mobile device ( 106 ) displaying the received fee.
  • the mobile device ( 106 ) transmitting to the server ( 102 ) via the communication network ( 116 ) a second identifier
  • the mobile device ( 106 ) selecting payment data to facilitate payment of the received fee, wherein the payment data is associated with the second identifier.
  • the payment data comprises at least a portion of at least one of a credit card number, a debit card number, a cardholder name, a card expiry date, a card verification code, a personal identification number, and a mailing code associated with the cardholder.
  • FIGS. 1 , 3 , 4 , and 5 A- 5 C The method of example 60 or 61, wherein the payment data comprises at least a portion of at least one of a credit card number, a debit card number, a cardholder name, a card expiry date, a card verification code, a personal identification number, and a mailing code associated with the cardholder.
  • the mobile device ( 106 ) receiving from the server ( 102 ), an indication that the fee was paid;
  • FIGS. 1 , 3 , 4 , and 5 A- 5 C responsive to the mobile device ( 106 ) receiving the indication that the fee was paid, the mobile device ( 106 ) displaying an indication that the fee was paid.
  • FIGS. 1 , 3 , 4 , and 5 A- 5 C provide the code displayed on the medium to an exit terminal.
  • FIGS. 1 , 3 , 4 , and 5 A- 5 C provide the code displayed on the medium to a capturing device.
  • the mobile device ( 106 ) determining that the captured code has a particular property
  • a mobile device ( 106 ) configured for performing the functions recited in one of examples 44-66. ( FIGS. 1 , 3 , 4 , and 5 A- 5 C).
  • a method comprising:
  • a server ( 102 ) receiving from a mobile device ( 106 ) via a communication network ( 116 ) the identifier
  • the server ( 102 ) responsive to the server ( 102 ) receiving the identifier, the server ( 102 ) determining a fee associated with the identifier, wherein the fee is a function of at least a distance between a first location and a second location that is a different from the first location;
  • the server ( 102 ) transmitting to the mobile device ( 106 ) via the communication network ( 116 ) the determined fee;
  • the server ( 102 ) receiving from the mobile device ( 106 ) via the communication network ( 116 ) authorization to pay the determined fee;
  • the server ( 102 ) determining that the determined fee has been paid
  • the server ( 102 ) responsive to the server ( 102 ) determining that the determined fee has been paid, the server ( 102 ) transmitting an indication that the determined fee has been paid. ( FIGS. 1 , 3 , 4 , and 5 A- 5 C).
  • the server ( 102 ) receiving from the mobile device ( 106 ) via the communication network ( 116 ) payment data to facilitate payment of the determined fee;
  • the server ( 102 ) receiving from the mobile device ( 106 ) via the communication network ( 116 ) a second identifier
  • the server ( 102 ) transmitting to the mobile device ( 106 ) via the communication network ( 116 ) an indication that the fee was paid.
  • the server ( 102 ) transmitting to an exit terminal ( 108 ) an indication that the fee was paid, wherein the exit terminal ( 108 ) is configured for: (i) receiving from the server ( 102 ) the indication that the fee was paid, and (ii) responsive to receiving from the server ( 102 ) the indication that the fee was paid, causing an action to be performed.
  • FIGS. 1 , 3 , 4 , and 5 A- 5 C FIGS. 1 , 3 , 4 , and 5 A- 5 C).
  • causing the action to be performed comprises causing the action to be performed so as to permit a vehicle to exit a toll booth.
  • causing the action to be performed comprises causing an access control device in the toll booth lot to be moved. ( FIGS. 1 , 3 , 4 , and 5 A- 5 C).
  • a server ( 102 ) configured for performing the functions recited in one of examples 69-83. ( FIGS. 1 , 3 , 4 , and 5 A- 5 C).
  • a mobile device ( 106 ) comprising:
  • a processor ( 150 );
  • a capturing device ( 156 ) configured to capture a code
  • a network interface ( 152 ) configured for facilitating communication between the mobile device ( 106 ) and a server ( 102 );
  • FIGS. 1 , 3 , 4 , and 5 A- 5 C a non-transitory computer-readable medium having stored thereon program instructions ( 162 ) that, when executed by the processor ( 150 ), cause performance of the functions recited in one of examples 1-23 or 44-66.
  • FIGS. 1 , 3 , 4 , and 5 A- 5 C FIGS. 1 , 3 , 4 , and 5 A- 5 C).
  • a server ( 102 ) comprising:
  • a processor ( 150 );
  • a network interface configured for facilitating communication between the server ( 102 ) and another device;
  • FIGS. 1 , 3 , 4 , and 5 A- 5 C a non-transitory computer-readable medium having stored thereon program instructions ( 192 ) that, when executed by the processor ( 182 ), cause performance of the functions recited in one of examples 26-41 or 69-83.
  • each step, block and/or communication can represent a processing of information and/or a transmission of information in accordance with example embodiments.
  • Alternative embodiments are included within the scope of these example embodiments.
  • functions described as steps, blocks, transmissions, communications, requests, responses, and/or messages can be executed out of order from that shown or discussed, including in substantially concurrent or in reverse order, depending on the functionality involved.
  • more or fewer steps, blocks and/or functions can be used with any of the message flow diagrams, scenarios, and flow charts discussed herein, and these message flow diagrams, scenarios, and flow charts can be combined with one another, in part or in whole.
  • a step or block that represents a processing of information can correspond to circuitry that can be configured to perform the specific logical functions of a herein-described method or technique.
  • a step or block that represents a processing of information can correspond to a module, a segment, or a portion of program code (including related data).
  • the program code can include one or more instructions executable by a processor for implementing specific logical functions or actions in the method or technique.
  • the program code and/or related data can be stored on any type of computer-readable medium such as a storage device including a disk or hard drive or other storage media.
  • the computer-readable medium can include non-transitory computer-readable media such as computer-readable media that stores data for short periods of time like register memory, processor cache, and/or random access memory (RAM).
  • the computer-readable media can include non-transitory computer-readable media that stores program code and/or data for longer periods of time, such as secondary or persistent long term storage, like read only memory (ROM), optical or magnetic disks, and/or compact-disc read only memory (CD-ROM), for example.
  • the computer-readable media can be any other volatile or non-volatile storage systems.
  • a computer-readable medium can be considered a computer-readable storage medium, for example, or a tangible storage device. Any data identified as being stored within a data storage device or transmitted to a device for storage within a data storage device can comprise a computer data signal embodied in a carrier wave.
  • a step or block that represents one or more information transmissions can correspond to information transmissions between software and/or hardware modules in the same physical device.
  • other information transmissions can be between software modules and/or hardware modules in different physical devices.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Computer Security & Cryptography (AREA)
  • Marketing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Game Theory and Decision Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Data Mining & Analysis (AREA)
  • Computing Systems (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Electromagnetism (AREA)
  • Health & Medical Sciences (AREA)
  • Artificial Intelligence (AREA)
  • Toxicology (AREA)
  • General Health & Medical Sciences (AREA)
  • Software Systems (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Cash Registers Or Receiving Machines (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Telephonic Communication Services (AREA)
  • Information Transfer Between Computers (AREA)
  • Devices For Checking Fares Or Tickets At Control Points (AREA)

Abstract

Disclosed is a payment system and method. In one example, a method involves: (i) a mobile device capturing a code disposed on a medium, wherein the code encodes an identifier; (ii) the mobile device decoding the captured code to recover the identifier; (iii) the mobile device transmitting to a server via a communication network (116) the recovered identifier; (iv) the mobile device receiving from the server via the communication network (116) a fee associated with the transmitted identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time; and (v) the mobile device transmitting authorization to pay the received fee.

Description

    PRIORITY CLAIM
  • This application claims the benefit of PCT application number PCT/GB2012/052802 filed 12 Nov. 2012, PCT application number PCT/GB2012/052804 filed 12 Nov. 2012, and PCT application number PCT/GB2012/052805 filed 12 Nov. 2012, all of which are incorporated by reference herein in their entirety.
    • BACKGROUND
  • Unless otherwise indicated herein, the elements described in this section are not prior art to the claims and are not admitted to be prior art by inclusion in this section.
  • A parking lot (e.g., a parkade) is an area where motor vehicles may be parked. In some instances, a parking lot may be fee-based such that a motor vehicle may be permitted to park in the lot in exchange for payment of a fee. Typically, this fee is based on a time period in which the vehicle is parked in the lot.
  • Upon a motor vehicle entering a fee-based parking lot, a driver of the vehicle may receive a time-stamped ticket from an entry terminal. Before the driver leaves the lot with the vehicle, the driver may be required to insert the ticket into a payment terminal, which may determine a fee (e.g., based on the amount of time that has passed since the driver received the ticket). The driver may then pay the fee, either by providing cash or a payment instrument such as a credit card or debit card into the payment terminal. The payment terminal may then validate the ticket and return it to the driver. To exit the parking lot, the driver may drive up to an exit terminal and insert the validated ticket into the exit terminal. The exit terminal may confirm that the ticket has been validated, and in response, the exit terminal may cause a boom to rise so as to allow the driver's vehicle to exit the parking lot.
  • This process of paying a fee for a parking lot can be inconvenient and can present safety and health concerns. In some arrangements, the payment terminal may be located at or near a pedestrian entrance to the parking lot. In such arrangements, queues at the payment terminal may be lengthy, particularly at peak times, thus causing delay and leading to driver impatience and frustration. Furthermore, the payment terminal may be out of service or may have insufficient cash to provide correct change, thereby further exacerbating these problems. In addition, the need for the driver to handle cash or payment instruments in a public environment may cause safety concerns.
  • In alternative arrangements, a payment terminal may be integrated with the exit terminal, which may allow a driver to pay the fee while sitting in the vehicle just before exiting the parking lot. However, such arrangements can lead to lengthy queues of vehicles waiting to reach the payment/exit terminal. In addition, the lengthy queues of vehicles can cause high levels of emissions in a relatively small area, which may be undesirable for health reasons.
  • It is therefore desirable to improve the process by which a parking lot fee (or another type of fee) is paid.
    • Overview
  • Example embodiments are described herein. In one respect, an example embodiment takes the form of a method comprising (i) a mobile device capturing a code disposed on a medium, wherein the code encodes an identifier; (ii) the mobile device decoding the captured code to recover the identifier; (iii) the mobile device transmitting to a server via a communication network the recovered identifier; (iv) the mobile device receiving from the server via the communication network a fee associated with the transmitted identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time; and (v) the mobile device transmitting authorization to pay the received fee.
  • In another respect, an example embodiment takes the form of a mobile device. The mobile device is configured for: (i) capturing a code disposed on a medium, wherein the code encodes an identifier; (ii) decoding the captured code to recover the identifier; (iii) transmitting to a server via a communication network the recovered identifier; (iv) receiving from the server via the communication network a fee associated with the transmitted identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time; and (v) transmitting authorization to pay the received fee.
  • In another respect, an example embodiment takes the form of a non-transitory computer-readable medium having stored thereon program instructions that, when executed by a processor, cause performance of a set of functions comprising: (i) a mobile device capturing a code disposed on a medium, wherein the code encodes an identifier; (ii) the mobile device decoding the captured code to recover the identifier; (iii) the mobile device transmitting to a server via a communication network the recovered identifier; (iv) the mobile device receiving from the server via the communication network a fee associated with the transmitted identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time; and (v) the mobile device transmitting authorization to pay the received fee.
  • In another respect, an example embodiment takes the form of a method comprising (i) a server receiving from a mobile device via a communication network the identifier; (ii) responsive to the server receiving the identifier, the server determining a fee associated with the identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time; (iii) the server transmitting to the mobile device via the communication network the determined fee; (iv) the server receiving from the mobile device via the communication network authorization to pay the determined fee; (v) the server determining that the determined fee has been paid; and (vi) responsive to the server determining that the determined fee has been paid, the server transmitting an indication that the determined fee has been paid.
  • In another respect, an example embodiment takes the form of a server. The server is configured for: (i) receiving from a mobile device via a communication network the identifier; (ii) responsive to receiving the identifier, determining a fee associated with the identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time; (iii) transmitting to the mobile device via the communication network the determined fee; (iv) receiving from the mobile device via the communication network authorization to pay the determined fee; (v) determining that the determined fee has been paid; and (vi) responsive to determining that the determined fee has been paid, transmitting an indication that the determined fee has been paid.
  • In another respect, an example embodiment takes the form of a non-transitory computer-readable medium having stored thereon program instructions that, when executed by a processor, cause performance of a set of functions comprising: (i) a server receiving from a mobile device via a communication network the identifier; (ii) responsive to the server receiving the identifier, the server determining a fee associated with the identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time; (iii) the server transmitting to the mobile device via the communication network the determined fee; (iv) the server receiving from the mobile device via the communication network authorization to pay the determined fee; (v) the server determining that the determined fee has been paid; and (vi) responsive to the server determining that the determined fee has been paid, the server transmitting an indication that the determined fee has been paid.
  • In another respect, an example embodiment takes the form of a method comprising (i) a mobile device capturing a code disposed on a medium, wherein the code encodes an identifier; (ii) the mobile device decoding the captured code to recover the identifier; (iii) the mobile device transmitting to a server via a communication network the recovered identifier; (iv) the mobile device receiving from the server via the communication network a fee associated with the transmitted identifier, wherein the fee is a function of at least a distance between a first location and a second location that is different than the first location; and (v) the mobile device transmitting authorization to pay the received fee.
  • In another respect, an example embodiment takes the form of a mobile device. The mobile device is configured for: (i) capturing a code disposed on a medium, wherein the code encodes an identifier; (ii) decoding the captured code to recover the identifier; (iii) transmitting to a server via a communication network the recovered identifier; (iv) receiving from the server via the communication network a fee associated with the transmitted identifier, wherein the fee is a function of at least a distance between a first location and a second location that is different than the first location; and (v) transmitting authorization to pay the received fee.
  • In another respect, an example embodiment takes the form of a non-transitory computer-readable medium having stored thereon program instructions that, when executed by a processor, cause performance of a set of functions comprising: (i) a mobile device capturing a code disposed on a medium, wherein the code encodes an identifier; (ii) the mobile device decoding the captured code to recover the identifier; (iii) the mobile device transmitting to a server via a communication network the recovered identifier; (iv) the mobile device receiving from the server via the communication network a fee associated with the transmitted identifier, wherein the fee is a function of at least a distance between a first location and a second location that is different than the first location; and (v) the mobile device transmitting authorization to pay the received fee.
  • In another respect, an example embodiment takes the form of a method comprising (i) a server receiving from a mobile device via a communication network the identifier; (ii) responsive to the server receiving the identifier, the server determining a fee associated with the identifier, wherein the fee is a function of at least a distance between a first location and a second location that is different than the first location; (iii) the server transmitting to the mobile device via the communication network the determined fee; (iv) the server receiving from the mobile device via the communication network authorization to pay the determined fee; (v) the server determining that the determined fee has been paid; and (vi) responsive to the server determining that the determined fee has been paid, the server transmitting an indication that the determined fee has been paid.
  • In another respect, an example embodiment takes the form of a server. The server is configured for: (i) receiving from a mobile device via a communication network the identifier; (ii) responsive to receiving the identifier, determining a fee associated with the identifier, wherein the fee is a function of at least a distance between a first location and a second location that is different from the first location; (iii) transmitting to the mobile device via the communication network the determined fee; (iv) receiving from the mobile device via the communication network authorization to pay the determined fee; (v) determining that the determined fee has been paid; and (vi) responsive to determining that the determined fee has been paid, transmitting an indication that the determined fee has been paid.
  • In another respect, an example embodiment takes the form of a non-transitory computer-readable medium having stored thereon program instructions that, when executed by a processor, cause performance of a set of functions comprising: (i) a server receiving from a mobile device via a communication network the identifier; (ii) responsive to the server receiving the identifier, the server determining a fee associated with the identifier, wherein the fee is a function of at least a distance between a first location and a second location that is different than the first location; (iii) the server transmitting to the mobile device via the communication network the determined fee; (iv) the server receiving from the mobile device via the communication network authorization to pay the determined fee; (v) the server determining that the determined fee has been paid; and (vi) responsive to the server determining that the determined fee has been paid, the server transmitting an indication that the determined fee has been paid.
  • In another respect, an example embodiment takes the form of a method comprising (i) scanning, using a mobile device, a quick response (QR) code that encodes a unique ticket code that identifies a parking ticket for using a parkade; (ii) decoding, using the mobile device, the QR code to recover the unique ticket code; (iii) transmitting from the mobile device to an application server the unique ticket code; (iv) receiving, at the mobile device, a parking fee for using the parkade, and displaying, on the mobile device, the parking fee; (v) selecting, using the mobile device, a payment instrument for paying the parking fee, and authorizing the parking fee for payment; (vi) transmitting from the mobile device to the application server data pertaining to the payment instrument; and (vii) receiving, at the mobile device from an application server, status data indicating whether the parking fee was successfully or unsuccessfully paid.
  • In another respect, an example embodiment takes the form of a mobile device comprising: (i) a processor; (ii) a camera configured to capture a quick response (QR) code that encodes a unique ticket code that identifies a parking ticket for using a parkade; (iii) a non-transitory computer-readable data storage device comprising computer-readable program instructions, wherein the program instructions are executable by the processor to decode the QR code; (iv) a user interface configured to display a parking fee for using the parkade and to allow a user to select a payment instrument for an attempt at paying the parking fee and to authorize a parking fee for payment; and (v) a network interface; (vi) wherein the network interface is configured to transmit, to an application server, the unique ticket code and data pertaining to the payment instrument; and (vii) wherein the network interface is configured to receive, from an application server, status data indicating whether the initial attempt at paying the fee was successful or unsuccessful.
  • In another respect, an example embodiment takes the form of a method comprising: (i) receiving, at an application server from a mobile device, a unique ticket code that identifies a parking ticket for using a parkade; (ii) determining, at the application server, a parking fee for using the parkade; (iii) transmitting, from the application server to the mobile device, the parking fee; (iv) receiving, at the application server from the mobile device, data pertaining to a payment instrument selected for an attempt at paying the fee; (v) determining, at the application server, whether processing the data pertaining to the parking fee and the data pertaining to the first payment instrument results in successful or unsuccessful payment of the parking fee; and (vi) transmitting, from the application server to the mobile device, status data indicating whether the attempt at paying the parking fee was successful or unsuccessful.
  • In another respect, an example embodiment takes the form of an application server system comprising: (i) a processor; (ii) a non-transitory computer-readable data storage device comprising computer-readable program instructions; and (iii) a network interface; (iv) wherein the network interface is configured to receive, from a mobile device, (1) a unique ticket code that identifies a parking ticket for using a parkade, and, (2) data pertaining to a payment instrument selected for an attempt at paying a parking fee for using the parkade; and (iv) wherein the program instructions are executable by the processor to determine whether processing the parking fee and the data pertaining to the payment instrument results in successful or unsuccessful payment of the parking fee; (v) wherein the program instructions are executable by the processor to cause the network interface to transmit status data to the mobile device; and (vi) wherein the status data indicates whether the attempt at paying the parking fee was successful or unsuccessful.
  • In another respect, an example embodiment takes the form of a method comprising: (i) providing, at a parkade, a parking ticket for using the parkade; and (ii) providing, at the parkade, a quick response (QR) code that encodes a unique ticket number that identifies the parking ticket.
  • These as well as other aspects and advantages will become apparent to those of ordinary skill in the art by reading the following detailed description, with reference where appropriate to the accompanying drawings. Further, it should be understood that the embodiments described in this overview and elsewhere are intended to be examples only and do not limit the scope of the disclosure.
    • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a schematic representation of a system for paying a fee in accordance with an example embodiment;
  • FIG. 2 illustrates an example quick response (QR) code;
  • FIG. 3 is a block diagram of a mobile device in accordance with an example embodiment;
  • FIG. 4 is a block diagram of an application server in accordance with an example embodiment;
  • FIG. 5A is a first part of a flow chart of functions of a method in accordance with an example embodiment;
  • FIG. 5B is a second part of the flow chart of FIG. 5A;
  • FIG. 5C is a third part of the flow chart of FIG. 5A; and
  • FIG. 6 illustrates a display of a mobile device in accordance with an example embodiment
    •  DETAILED DESCRIPTION I. Introduction
  • This description describes, among other things, example embodiments of the disclosed system and method. In this description the terms “user” and “driver” can be used interchangeably depending on the context. The articles “a” or “an” are used to introduce elements of the example embodiments, and the intent of using those articles is that there is one or more of the elements. The intent of using the conjunction “or” within a described list of at least two terms is to indicate that any of the listed terms or any combination of the listed terms. The use of ordinal numbers such as “first,” “second,” “third” and so on is to distinguish respective elements rather than to denote a particular order of those elements.
  • The following abbreviations or acronyms are used in the description:
  • FIG. —Figure;
  • FIGS. —Figures;
  • PIN—Personal Identification Number;
  • QR—Quick Response;
    • II. Example Architecture
  • FIG. 1 is a schematic representation of a system 100 for paying a fee in accordance with an example embodiment. To illustrate one example use case of the system 100, the system 100 is described in connection with a parking lot. However, as described further below, the system 100 may be used in connection with other environments as well.
  • The system 100 includes an application server 102, an entry or dispenser terminal 104, a mobile device 106, an exit terminal 108, a payment processing server 110, and a parking record database 112.
  • The dispenser terminal 104 may be configured to dispense a medium to a user, such as a driver of a vehicle. In some instances, in response to a vehicle entering the parking lot, the dispenser terminal 104 may dispense the medium. The medium may take a variety of forms. For example, the medium may take the form of a paper ticket or a token.
  • The medium may have disposed thereon a code that encodes a session identifier. The code may take a variety of forms. For example, the code may take the form of a one-dimensional code such as a linear barcode, or a two-dimensional code such as a QR code. The session identifier may uniquely identify a particular parking session, that is, a given instance of a vehicle parking in the parking lot. The session identifier can take a variety of forms. For example, the session identifier may be a numeric or an alphanumeric code. In some embodiments, the code can also encode other data, including for example a time or a parking lot identifier.
  • In some embodiments, the dispenser terminal 104 may be configured to print the code on the medium (or otherwise cause the code to be disposed on the medium) proximate (i.e., at or about) the time that the medium is dispensed. In one example, an event is proximate a time if the event and the time are within a threshold number of seconds of each other. The threshold may be, for example, five seconds, ten seconds, or twenty seconds.
  • In other embodiments, the medium may already have a code disposed thereon when it is loaded into the dispenser terminal 104. The dispenser terminal 104 may be operatively connected to the application server 102, and may further be configured to transmit to the application server 102 the session identifier encoded in the code and/or a time that generally indicating a time the vehicle entered the parking lot. As used herein, the term “time” refers to a time and/or date. The application server 102 may be configured to store the received session identifier and the time in a parking record database 112 as described in greater detail below.
  • The exit device 108 may be configured to regulate the exiting of vehicles out of the parking lot and may include or be integrated with an access control device, which may take a variety of forms. In one example, the access control device may take the form of a boom mechanism that is configured to move between a low position, thereby obstructing vehicles from exiting the lot, and a high position, thereby permitting vehicles to exit the lot. The exit device 108 may raise and lower the boom.
  • In some instances, the same control access device may be used to regulate the entry of vehicles into the lot and the exiting of vehicles out of the lot. However, in other embodiments, separate control access devices may be used for each purpose. The exit terminal 108 may be operatively connected to the application server 102.
  • The application server 102, the mobile device 106 and the payment processing server 110 can communicate with each other by means of a communication network 116. The communication network 116 can take a variety of forms. For instance, the communication network 116 may take the form of a local-area network or a wide-area network, such as the world-wide web or the Internet. The communication network 116 may be supported by wired or wireless interfaces (e.g., interfaces configured to communicate using a Wi-Fi or Bluetooth protocol, for instance). Notably, in some embodiments, other devices in the system 100 may also communicate with each other via a communication network. Communication between any such devices may be facilitated by corresponding network interfaces.
  • Communication between the application server 102, the mobile device 106 and the payment processing server 110 can be facilitated by using a server-hosted program that is installed on the application server 102, a payment application program (a “payment app”) that is installed and executed on the mobile device 106, and a processing application program (a “processing app”) that is installed and executed on the payment processing server 110.
  • A user can download a copy of the payment app from a download repository, for example, from a data storage device 188 of the application server 102 (FIG. 4) and install the payment app on the mobile device 106. During or after installation, the payment app may create a user profile 114 on the mobile device 106 and prompt the user to manually provide certain attributes such as, the user's first name, the user's last name, an e-mail address, a physical address and particulars of one or more payment instruments such as credit cards, debit cards, e-wallets and the like. In accordance with at least some example embodiments, the user profile 114 may be stored locally on the mobile device 106 and not passed to the application server 102. The payment app may facilitate the performance of a variety of functions, including but not limited to the functions of capturing a code that encodes a session identifier, decoding the captured code to recover the session identifier, transmitting to a server the recovered session identifier, receiving from the server a fee associated with the recovered session identifier, and providing to the server authorization to pay the fee.
  • As noted above, one example of a code is a QR code. FIG. 2 illustrates an example QR code 200. A QR code is a two-dimensional code. The example embodiments may use any of a variety of two-dimensional codes, such as an Aztec barcode, a codablock F code, a code16K barcode, a code49 barcode, a data-matrix barcode, a micro PDF417 barcode, a QR code, a micro QR code or some other two-dimensional code. Alternatively, the example embodiments may use a one-dimensional code, such as a barcode in which only a width of each bar is used to decode the barcode.
  • Next, FIG. 3 is a block diagram depicting an example embodiment of mobile device 106. As shown in FIG. 3, the mobile device 106 includes (i) a processor 150, (ii) a network interface 152 for transmitting data to and receiving data from communication network 116, (iii) a user interface 154, (iv) a camera (or other capture device) 156 configured to capture a code such as a QR code, and (v) a data storage device 158, all of which can be linked together via a system bus or other connection mechanism 160. Data storage device 158 includes computer-readable program instructions (CRPI) 162, the payment app 164, and a user profile 114. CRPI 162 can include the payment app 164. Data storage device 158 can comprise a non-transitory computer-readable storage medium readable by processor 150. Each computer-readable storage medium described herein can comprise volatile and/or non-volatile storage components, such as optical, magnetic, organic or other memory or disc storage, which can be integrated in whole or in part with a processor.
  • Each processor described herein can comprise one or more general purpose processors (for example, INTEL single core microprocessors or INTEL multicore microprocessors) or one or more special purpose processors (for example, digital signal processors). Processor 150 is configured to execute CRPI 162 and the payment app 164.
  • Mobile device 106 can be configured as or comprise a cellular phone, a smartphone, a tablet device, or some other device arranged to carry out cellular communications. In this regard, communication network 116 can comprise a cellular communication network, such as a network for carrying out communications according to the 4G Long Term Evolution (LTE) standard developed by the 3rd Generation Partnership Project (3GPP), or some other communication standard developed for a cellular communication network.
  • Next, FIG. 4 is a block diagram depicting an example embodiment of the application server 102. As shown in FIG. 4, application server 102 can include (i) a processor 182, (ii) a network interface 184 for transmitting data to and receiving data from communication network 116, (iii) a user interface 186, and (iv) a data storage device 188, all of which can be linked together via a system bus or other connection mechanism 190. Data storage device 188 can include (i) CRPI 192, and (ii) the payment app 194 (which may be the same as the payment app 164) to be downloaded by the mobile device 106. CRPI 192 can include the payment app 194. Data storage device 188 can comprise a non-transitory computer-readable storage medium readable by processor 182. Processor 182 is configured to execute CRPI 192.
    • III. Example Operation
  • The system 100 can be used to pay a fee. The following example describes an example use of the system 100 in connection with a user who wishes to pay a parking lot fee. However, as described further below, the system 100 may be used in connection with users who wish to pay other types of fees as well.
  • FIGS. 5A-5C shows a flow chart depicting a set of functions of a method in accordance with an example embodiment. The set of functions are shown within blocks 502 through 548. A description of those blocks now follows.
  • At block 502, the method may involve the dispenser terminal 104 dispensing a medium having a code disposed thereon, wherein the code encodes a session identifier. At block 504, the method may involve the mobile device 106 capturing the code disposed on the medium. This may involve the mobile device 106 using the camera 156 and the payment app 164 to capture the code. At block 506, the method may involve the mobile device 106 decoding the captured code to recover the session identifier. This may involve the mobile device 106 using the payment app 164 to decode the captured code and to recover the session identifier.
  • In some embodiments, the mobile device 106 may determine that the captured code has a particular property, and in responsive the mobile device 106 may automatically launch an application, such as the payment app 164. In one example, the captured code having the particular property may involve the capture code having a particular set of data (e.g., the string “launch_payment_app” encoded therein.
  • At block 508, the method may involve the mobile device 106 transmitting to the application server 102 via the communication network 116 the recovered session identifier. At block 510, the method may involve the application server 102 receiving from the mobile device 106 via the communication network 116 the transmitted session identifier.
  • At block 512, the method may involve the application server 102 determining a fee associated with the received session identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time.
  • Generally, the first time is proximate a time when the vehicle enters the parking lot. The application server 102 may determine the first time in a variety of ways. For example, the dispenser terminal 104 may determine the first time to be a time when the dispenser terminal 104 dispenses the medium. The dispenser terminal 104 may then transmit the first time to the application server 102 together with the session identifier. In another example, the application server 102 may determine the first time to be a time when the application server 102 receives the session identifier from the dispenser terminal 104. In either of the two examples described above, the application server 102 may store in the parking record database 112 the received session identifier together with the received first time. Therefore, the act of the application server 102 determining the fee associated with the received session identifier may involve the application server 102 using the received session identifier to retrieve the corresponding first time from the parking record database 112.
  • Generally, the second time is proximate a time when the driver is in the process of paying the fee and/or exiting the parking lot. The application server 102 may determine the second time in a variety of ways. For example, the mobile device 106 may determine the second time to be a time when the mobile device 106 (i) captures the code, (ii) decodes the captured code to recover the session identifier, or (iii) transmits to the application server 102 the recovered session identifier. The mobile device 106 may then transmit the second time to the application server 102 together with the session identifier. In another example, the application server 102 may determine the second time to be a time when the application server 102 receives the session identifier from the mobile device 106. In either of the two examples described above, the application server 102 may store in the parking record database 112 the received session identifier together with the received second time. As such, the act of the application server 102 determining the fee associated with the received session identifier may involve the application server 102 using the received session identifier to retrieve the corresponding second time from the parking record database 112.
  • As noted above, the fee may be a function of at least the time period. As such, the application server 102 may use a look-up table (e.g., that is stored in a data storage of the application server 102) to determine the fee based on the time period. The data in the look-up table may be set via a user interface by, e.g., a manager of the parking lot.
  • In some instances, the fee may further be a function of other factors, including but not limited to a location of the parking lot, a time of day, week, month, or year in which the time period falls within, and the user profile. As such, in some embodiments, the dispenser terminal 104, the mobile device 106, and/or another device may provide such data to the application server 102 so that the application server 102 can determine the fee by using such factors.
  • At block 514, the method may involve the application server 102 transmitting to the mobile device 106 via the communication network 116 the determined fee. At block 516, the method may involve the mobile device 106 receiving the transmitted fee.
  • At block 518, the method may involve the mobile device 106 displaying the received fee. FIG. 6 shows an example screenshot 600 of a display of the mobile device 106 at block 518. As shown, in addition to displaying the determined fee, the mobile device 106 may further display the first time and the second time. This allows the user to review details relating to a parking session before authorizing payment of the fee for the parking session.
  • If the user wishes to authorize payment of the fee, the user may provide such authorization via the user interface 154 of the mobile device 106. In turn, at block 520, the method may involve the mobile device 106 transmitting to the application server 102 via the communication network 116 authorization to pay the received fee. In addition to transmitting such authorization, the mobile device 106 may further transmit payment data to the application server 102. Payment data may include at least a portion of at least one of a credit card number, a debit card number, a cardholder name, a card expiry date, a card verification code, a PIN, and a mailing code associated with the cardholder, among other things. In one example, the user may provide such payment data to the mobile device 106 via the user interface 154.
  • In another example, the mobile device 106 may transmit to the application server 102 a user profile identifier, which the application server 102 may use to retrieve payment data associated with the user (e.g., stored in the user profile 114). In some instances, the application server 102 may transmit to the mobile device at least a portion of the retrieved payment data such that the mobile device 106 may display payment data options to the user. This may allow the user to select payment data (e.g., a particular payment instrument) from among the payment data options being displayed. In turn, the mobile device 106 may select such payment data and transmit the selection to the application server 102.
  • At block 522, the method may involve responsive to the application server 102 receiving authorization to pay the determined fee, the application server 102 transmitting the particulars of the fee transaction (for example the parking fee and details relating to a selected payment instrument to the payment processing server 110 for processing).
  • At block 524, the method may involve the application server 102 determining that the fee was paid. In some examples, the application server 102 may determine this based on the payment processing server 110 transmitting a payment status indicator to the application server 102, for example, either successful or unsuccessful. At block 526, the method may involve responsive to the application server 102 determining that the fee was paid, the application server 102 updating a status of the session identifier in the parking record database 112 as paid. Further in response, at block 528, the method may involve the application server 102 transmitting to the mobile device 106 an indication that the fee was paid. At block 530, the method may involve the mobile device 106 receiving the indication that the fee was paid. And in response, at block 532, the method may involve the mobile device 106 displaying an indication that the fee was paid.
  • In some instances, further in response to the application server 102 determining that the fee was paid, the application server 102 may initiate a countdown timer that indicates how much time remains until the vehicle must exit the parking lot (e.g., before incurring an additional fee). For example, the countdown timer may start at 10 or 15 minutes once initiated. In one example, the application server 102 may also communicate with the mobile device 106 to cause the mobile device 106 to display the value of the countdown timer in a dynamic or live manner.
  • Notably, if the payment processing server 110 is unsuccessful at processing the payment, the application server 102 may notify the mobile device 106 accordingly, such that the mobile device 106 may re-authorize payment of the fee, perhaps after selecting alternate payment data.
  • Once payment has been successfully completed, the driver of the vehicle may provide the code to the exit terminal 108 to gain permission to leave the parking lot with the vehicle. In one example, the driver may do this by providing to the exit terminal 108, the medium with the code disposed thereon. In another example, the mobile device 106 may be configured to display the code, and therefore, the driver may provide to the exit terminal 108 the mobile device 106 with the code displayed thereon.
  • At block 534, the method may involve the exit terminal 108 capturing the code. This may involve the exit terminal 108 using a camera and a payment app to capture the code. At block 536, the method may involve the exit terminal 108 decoding the captured code to recover the session identifier. This may involve the exit terminal 108 using a payment app to decode the captured code and to recover the session identifier.
  • At block 538, the method may involve the exit terminal 108 transmitting the recovered session identifier to the application server 102. At block 540, the method may involve the application server 102 receiving the transmitted session identifier.
  • At block 542, the method may involve, responsive to the application server 102 receiving the transmitted session identifier, the application server 102 determining that the fee associated with the received session identifier has been paid. This may involve the application server 102 using the received session identifier to perform a lookup in the parking record database 112 to retrieve the session identifier's corresponding status.
  • At block 544, the method may involve the application server 102 transmitting to the exit terminal 108 an indication that the fee has been paid. At block 546, the method may involve the exit terminal 108 receiving the indication that the fee has been paid.
  • At block, 548, the method may involve responsive to the exit terminal 108 receiving the indication that the fee has been paid, the exit terminal 108 causing an action to be performed. In an alternative example, the method may involve responsive to (i) the exit terminal 108 receiving the indication that the fee has been paid, and (ii) the exit terminal 108 determining that the countdown timer has not expired, the exit terminal causing the action to be performed. In the event that the application server 102 determines that the fee has been paid, and that the countdown timer has expired, the application server 102 may determine and transmit to the mobile device 106 an additional fee, and the mobile device 106 may authorize payment of that fee in a manner similar to that described above in connection with the original fee.
  • In one example, the exit terminal 108 causing an action to be performed may involve the exit terminal 108 causing an access control device to be moved. For instance, where the access control device takes the form of a boom, the exit terminal 108 may cause the boom to be raised thereby permitting vehicles to exit the parking lot. However, the exit terminal 108 may cause other actions to be performed. For instance, the exit terminal 108 may cause tire spikes to be retracted, thereby permitting vehicles to exit the parking lot.
    • IV. Variations and Benefits of Example Embodiments
  • Clearly, numerous variations and permutations are possible to the embodiments without departing from the scope of this disclosure: Some of these variations and permutations are described below.
  • 1. In accordance with one or more of the disclosed embodiments, the user profile 114 may be stored on the mobile device 106 and on the application server 102. In this embodiment, the capturing app 164 on the mobile device 106 may synchronize changes to the user profile 114 with the copy of the profile on the application server 102 as the changes occur, or periodically, or explicitly under user command. The copy of the user profile on the application server 102 can then be imported to a different mobile device 106, for example when the user changes mobile devices or in the event the user loses or damages the mobile device 106.
  • 2. In accordance with one or more of the disclosed embodiments, in order to improve security of the system 100, transmission of any of the data described herein can be encrypted.
  • 3. In accordance with one or more of the disclosed embodiments, instead of the application server 102 sending the particulars of the financial transaction (for example, the fee and the payment details) to the payment processing server 110 for processing, the application server 102 can process the payment itself.
  • 4. In accordance with at least one example embodiment, after establishing the user profile 114 and capturing the code, the only user action required to effect payment of the fee is selecting a payment instrument from the payment data associated with the user profile 114 or otherwise entering information regarding a payment instrument.
  • 5. The use of codes such as QR codes, as described in the example embodiments, can enable payment of a parking lot fee to be conducted more efficiently than is possible by means of known prior art methods. In one example, once a user has established a user profile 114, the user need only capture, by means of the mobile device 106, a code disposed on a medium in order to effect payment of the parking lot fee. The user is spared the tedium of having to locate a payment terminal in the parking lot, having to wait in line to use the payment terminal, and having to tender cash or a physical payment instrument such as a credit or debit card for payment. Furthermore, the user does not face the risk of the payment terminal being out of order or out of change. Still further, the user can pay the parking fee just before arriving back at the user's vehicle in the parking lot or, alternatively, when safely seated in the user's vehicle, with a clear indication of how much time remains before expiry of a countdown timer within which to exit the parking lot without an additional payment. It is anticipated that the disclosed system and method for paying parking lot fees will reduce the tedium of such payments.
  • 6. In accordance with one or more of the example embodiments, the application server 102 can provide the exit terminal 108, prior to the exit terminal 108 receiving the code or medium with the code for a driver to exit the parking lot, the session identifier, an indication the fee has been paid, and data identifying the countdown timer associated with the fee payment for the session identifier. Providing those items to the exit terminal 108 in this manner can allow the exit terminal 108 to confirm successful payment and timely provision of the code or the medium for the parking session more quickly.
  • 7. As noted above, an example application of the system 100 allows a user to pay a parking lot fee. However, the system 100 may be used in connection with users who wish to pay other types of fees as well. For instance, the system may allow a user to pay a fee for a travel session associated with a toll road. In this example, rather than the fee being a function of at least a time period between a first time and a second time, the fee may be a function of at least a distance between a first location (e.g., where a dispenser terminal is located) and a second location (e.g., where an exit terminal is located). In such instances, the application server 102 may determine the first and/or second locations based on a location of the dispenser terminal 104, a location of the exit terminal 108, and/or a location of the mobile device 106, any of which may transmit such locations to the application server 102 for use in determining the fee.
    • V. Additional Example Embodiments
  • The following examples are offered as further description of the disclosed invention.
  • 1. A method comprising:
  • a mobile device (106) capturing a code disposed on a medium, wherein the code encodes an identifier;
  • the mobile device (106) decoding the captured code to recover the identifier;
  • the mobile device (106) transmitting to a server (102) via a communication network (116) the recovered identifier;
  • the mobile device (106) receiving from the server (102) via the communication network (116) a fee associated with the transmitted identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time; and
  • the mobile device (106) transmitting authorization to pay the received fee. (FIGS. 1, 3, 4, and 5A-5C).
  • 2. The method of example 1, wherein the medium comprises a paper ticket. (FIGS. 1, 3, 4, and 5A-5C).
  • 3. The method of example 1 or 2, wherein the code comprises a one-dimensional code. (FIGS. 1, 3, 4, and 5A-5C).
  • 4. The method of one of examples 1-3, wherein the code comprises a two-dimensional matrix code. (FIGS. 1, 3, 4, and 5A-5C).
  • 5. The method of example 4, wherein the code comprises a Quick Response (QR) code (200). (FIGS. 1, 2-4, and 5A-5C).
  • 6. The method of one of examples 1-5, wherein the identifier comprises a unique identifier of a parking session associated with a parking lot, and wherein the fee comprises a fee for the parking session. (FIGS. 1, 3, 4, and 5A-5C).
  • 7. The method of one of examples 1-6, wherein the mobile device (106) capturing the code comprises a camera (156) of the mobile device (106) capturing the code. (FIGS. 1, 3, 4, and 5A-5C).
  • 8. The method of one of examples 1-7, wherein the mobile device (106) capturing the code comprises the mobile device (106) scanning the code. (FIGS. 1, 3, 4, and 5A-5C).
  • 9. The method of one of examples 1-8, wherein the communication network (116) comprises a local-area network. (FIGS. 1, 3, 4, and 5A-5C).
  • 10. The method of one of examples 1-9, wherein the communication network (116) comprises a wide-area network. (FIGS. 1, 3, 4, and 5A-5C).
  • 11. The method of example 10, wherein the wide-area network comprises the world-wide web. (FIGS. 1, 3, 4, and 5A-5C).
  • 12. The method of example 10, wherein the wide-area network comprises the Internet. (FIGS. 1, 3, 4, and 5A-5C).
  • 13. The method of one of examples 1-12, wherein the code further encodes the first time, the method further comprising:
  • the mobile device (106) decoding the code to recover the first time; and
  • the mobile device (106) transmitting to the server (102) via the communication network (116) the first time. (FIGS. 1, 3, 4, and 5A-5C).
  • 14. The method of one of examples 1-13, wherein the first time is proximate a time when the medium was dispensed from a dispenser terminal (104). (FIGS. 1, 3, 4, and 5A-5C).
  • 15. The method of one of examples 1-14, wherein the second time is proximate a time of the mobile device (106) transmitting to the server (102) via the communication network (116) the recovered identifier. (FIGS. 1, 3, 4, and 5A-5C).
  • 16. The method of one of examples 1-15, further comprising:
  • the mobile device (106) displaying the received fee. (FIGS. 1, 3, 4, 5A-5C, and 6).
  • 17. The method of one of examples 1-16, the method further comprising:
  • the mobile device (106) transmitting to the server (102) via the communication network (116) payment data to facilitate payment of the received fee. (FIGS. 1, 3, 4, and 5A-5C).
  • 18. The method of one of examples 1-16, wherein the identifier is a first identifier, the method further comprising:
  • the mobile device (106) transmitting to the server (102) via the communication network (116) a second identifier; and
  • the mobile device (106) selecting payment data to facilitate payment of the received fee, wherein the payment data is associated with the second identifier. (FIGS. 1, 3, 4, and 5A-5C).
  • 19. The method of example 17 or 18, wherein the payment data comprises at least a portion of at least one of a credit card number, a debit card number, a cardholder name, a card expiry date, a card verification code, a personal identification number, and a mailing code associated with the cardholder. (FIGS. 1, 3, 4, and 5A-5C).
  • 20. The method of one of examples 1-19, the method further comprising:
  • the mobile device (106) receiving from the server (102), an indication that the fee was paid; and
  • responsive to the mobile device (106) receiving the indication that the fee was paid, the mobile device (106) displaying an indication that the fee was paid. (FIGS. 1, 3, 4, and 5A-5C).
  • 21. The method of one of examples 1-20, the method further comprising:
  • providing the code displayed on the medium to an exit terminal. (FIGS. 1, 3, 4, and 5A-5C).
  • 22. The method of one of examples 1-21, the method further comprising:
  • the mobile device (106) displaying the captured code; and
  • providing the code displayed on the medium to a capturing device. (FIGS. 1, 3, 4, and 5A-5C).
  • 23. The method of one of examples 1-21, further comprising:
  • the mobile device (106) determining that the captured code has a particular property; and
  • responsive to the mobile device (106) determining that the captured code has the particular property, the mobile device (106) launching an application to facilitate payment of the received fee. (FIGS. 1, 3, 4, and 5A-5C).
  • 24. A mobile device (106) configured for performing the functions recited in one of examples 1-23. (FIGS. 1, 3, 4, and 5A-5C).
  • 25. A non-transitory computer-readable medium having stored thereon program instructions (162) that, when executed by a processor (150), cause performance of the functions recited in one of examples 1-23. (FIGS. 1, 3, 4, and 5A-5C).
  • 26. A method comprising:
  • a server (102) receiving from a mobile device (106) via a communication network (116) the identifier;
  • responsive to the server (102) receiving the identifier, the server (102) determining a fee associated with the identifier, wherein the fee is a function of at least a time period between a first time and a second time;
  • the server (102) transmitting to the mobile device (106) via the communication network (116) the determined fee;
  • the server (102) receiving from the mobile device (106) via the communication network (116) authorization to pay the determined fee;
  • the server (102) determining that the determined fee has been paid; and
  • responsive to the server (102) determining that the determined fee has been paid, the server (102) transmitting an indication that the determined fee has been paid. (FIGS. 1, 3, 4, and 5A-5C).
  • 27. The method of example 26, wherein the identifier comprises a unique identifier of a parking session associated with a parking lot, and wherein the fee comprises a fee for the parking session. (FIGS. 1, 3, 4, and 5A-5C).
  • 28. The method of example 26 or 27, wherein the communication network (116) comprises a local-area network. (FIGS. 1, 3, 4, and 5A-5C).
  • 29. The method of one of examples 26-28, wherein the communication network (116) comprises a wide-area network. (FIGS. 1, 3, 4, and 5A-5C).
  • 30. The method of example 29, wherein the wide-area network comprises the world-wide web. (FIGS. 1, 3, 4, and 5A-5C).
  • 31. The method of example 29, wherein the wide-area network comprises the Internet. (FIGS. 1, 3, 4, and 5A-5C).
  • 32. The method of one of examples 26-31, further comprising:
  • the server (102) receiving from the mobile device (106) via the communication network (116) the first time. (FIGS. 1, 3, 4, and 5A-5C).
  • 33. The method of one of examples 26-32, wherein the first time is proximate a time when a medium was dispensed from a dispensing device, wherein a code is disposed on the medium, and wherein the code encodes the identifier. (FIGS. 1, 3, 4, and 5A-5C).
  • 34. The method of example 33, further comprising:
  • the server (102) receiving from the dispenser terminal the first time. (FIGS. 1, 3, 4, and 5A-5C).
  • 35. The method of one of examples 26-34, wherein the second time is proximate a time of the server (102) receiving from the mobile device (106) via the communication network (116) the identifier. (FIGS. 1, 3, 4, and 5A-5C).
  • 36. The method of one of examples 26-35, further comprising:
  • the server (102) receiving from the mobile device (106) via the communication network (116) payment data to facilitate payment of the determined fee; and
  • the server (102) causing the determined fee to be paid using the payment data. (FIGS. 1, 3, 4, and 5A-5C).
  • 37. The method of one of examples 26-35, wherein the identifier is a first identifier, the method further comprising:
  • the server (102) receiving from the mobile device (106) via the communication network (116) a second identifier;
  • the server (102) causing the determined fee to be paid using payment data associated with the second identifier. (FIGS. 1, 3, 4, and 5A-5C).
  • 38. The method of one of examples 26-37, further comprising:
  • the server (102) transmitting to the mobile device (106) via the communication network (116) an indication that the fee was paid. (FIGS. 1, 3, 4, and 5A-5C).
  • 39. The method of one of examples 26-38, further comprising:
  • the server (102) transmitting to an exit terminal (108) an indication that the fee was paid, wherein the exit terminal (108) is configured for: (i) receiving from the server (102) the indication that the fee was paid, and (ii) responsive to receiving from the server (102) the indication that the fee was paid, causing an action to be performed. (FIGS. 1, 3, 4, and 5A-5C).
  • 40. The method of example 39, wherein causing the action to be performed comprises causing the action to be performed so as to permit a vehicle to exit a parking lot. (FIGS. 1, 3, 4, and 5A-5C).
  • 41. The method of example 40, wherein causing the action to be performed comprises causing an access control device in the parking lot to be moved. (FIGS. 1, 3, 4, and 5A-5C).
  • 42. A server (102) configured for performing the functions recited in one of examples 24-41. (FIGS. 1, 3, 4, and 5A-5C).
  • 43. A non-transitory computer-readable medium having stored thereon program instructions (192) that, when executed by a processor (182), cause performance of the functions recited in one of examples 24-41. (FIGS. 1, 3, 4, and 5A-5C).
  • 44. A method comprising:
  • a mobile device (106) capturing a code disposed on a medium, wherein the code encodes an identifier;
  • the mobile device (106) decoding the captured code to recover the identifier;
  • the mobile device (106) transmitting to a server (102) via a communication network (116) the recovered identifier;
  • the mobile device (106) receiving from the server (102) via the communication network (116) a fee associated with the transmitted identifier, wherein the fee is a function of at least a distance between a first location and a second location that is different from the first location; and
  • the mobile device (106) transmitting authorization to pay the received fee. (FIGS. 1, 3, 4, and 5A-5C).
  • 45. The method of example 44, wherein the medium comprises a paper ticket. (FIGS. 1, 3, 4, and 5A-5C).
  • 46. The method of example 44 or 45, wherein the code comprises a one-dimensional code. (FIGS. 1, 3, 4, and 5A-5C).
  • 47. The method of one of examples 44-46, wherein the code comprises a two-dimensional matrix code. (FIGS. 1, 3, 4, and 5A-5C).
  • 48. The method of example 47, wherein the code comprises a Quick Response (QR) code (200). (FIGS. 1, 2-4, and 5A-5C).
  • 49. The method of one of examples 44-48, wherein the identifier comprises a unique identifier of a travel session associated with a toll road, and wherein the fee comprises a fee for the travel session. (FIGS. 1, 3, 4, and 5A-5C).
  • 50. The method of one of examples 44-49, wherein the mobile device (106) capturing the code comprises a camera (156) of the mobile device (106) capturing the code. (FIGS. 1, 3, 4, and 5A-5C).
  • 51. The method of one of examples 44-50, wherein the mobile device (106) capturing the code comprises the mobile device (106) scanning the code. (FIGS. 1, 3, 4, and 5A-5C).
  • 52. The method of one of examples 44-51, wherein the communication network (116) comprises a local-area network. (FIGS. 1, 3, 4, and 5A-5C).
  • 53. The method of one of examples 44-52, wherein the communication network (116) comprises a wide-area network. (FIGS. 1, 3, 4, and 5A-5C).
  • 54. The method of example 53, wherein the wide-area network comprises the world-wide web. (FIGS. 1, 3, 4, and 5A-5C).
  • 55. The method of example 53, wherein the wide-area network comprises the Internet. (FIGS. 1, 3, 4, and 5A-5C).
  • 56. The method of one of examples 44-55, wherein the code further encodes the first location, the method further comprising:
  • the mobile device (106) decoding the code to recover the first location; and
  • the mobile device (106) transmitting to the server (102) via the communication network (116) the first location. (FIGS. 1, 3, 4, and 5A-5C).
  • 57. The method of one of examples 44-56, wherein the first location is proximate a location when the medium was dispensed from a dispenser terminal (104). (FIGS. 1, 3, 4, and 5A-5C).
  • 58. The method of one of examples 44-57, wherein the second location is proximate a location of the mobile device (106) when transmitting to the server (102) via the communication network (116) the recovered identifier. (FIGS. 1, 3, 4, and 5A-5C).
  • 59. The method of one of examples 44-58, further comprising:
  • the mobile device (106) displaying the received fee. (FIGS. 1, 3, 4, 5A-5C, and 6).
  • 60. The method of one of examples 44-59, the method further comprising:
  • the mobile device (106) transmitting to the server (102) via the communication network (116) payment data to facilitate payment of the received fee. (FIGS. 1, 3, 4, and 5A-5C).
  • 61. The method of one of examples 44-59, wherein the identifier is a first identifier, the method further comprising:
  • the mobile device (106) transmitting to the server (102) via the communication network (116) a second identifier; and
  • the mobile device (106) selecting payment data to facilitate payment of the received fee, wherein the payment data is associated with the second identifier. (FIGS. 1, 3, 4, and 5A-5C).
  • 62. The method of example 60 or 61, wherein the payment data comprises at least a portion of at least one of a credit card number, a debit card number, a cardholder name, a card expiry date, a card verification code, a personal identification number, and a mailing code associated with the cardholder. (FIGS. 1, 3, 4, and 5A-5C).
  • 63. The method of one of examples 44-62, the method further comprising:
  • the mobile device (106) receiving from the server (102), an indication that the fee was paid; and
  • responsive to the mobile device (106) receiving the indication that the fee was paid, the mobile device (106) displaying an indication that the fee was paid. (FIGS. 1, 3, 4, and 5A-5C).
  • 64. The method of one of examples 44-63, the method further comprising:
  • providing the code displayed on the medium to an exit terminal. (FIGS. 1, 3, 4, and 5A-5C).
  • 65. The method of one of examples 44-64, the method further comprising:
  • the mobile device (106) displaying the captured code; and
  • providing the code displayed on the medium to a capturing device. (FIGS. 1, 3, 4, and 5A-5C).
  • 66. The method of one of examples 44-65, further comprising:
  • the mobile device (106) determining that the captured code has a particular property; and
  • responsive to the mobile device (106) determining that the captured code has the particular property, the mobile device (106) launching an application to facilitate payment of the received fee. (FIGS. 1, 3, 4, and 5A-5C).
  • 67. A mobile device (106) configured for performing the functions recited in one of examples 44-66. (FIGS. 1, 3, 4, and 5A-5C).
  • 68. A non-transitory computer-readable medium having stored thereon program instructions (162) that, when executed by a processor (150), cause performance of the functions recited in one of examples 1-23. (FIGS. 1, 3, 4, and 5A-5C).
  • 69. A method comprising:
  • a server (102) receiving from a mobile device (106) via a communication network (116) the identifier;
  • responsive to the server (102) receiving the identifier, the server (102) determining a fee associated with the identifier, wherein the fee is a function of at least a distance between a first location and a second location that is a different from the first location;
  • the server (102) transmitting to the mobile device (106) via the communication network (116) the determined fee;
  • the server (102) receiving from the mobile device (106) via the communication network (116) authorization to pay the determined fee;
  • the server (102) determining that the determined fee has been paid; and
  • responsive to the server (102) determining that the determined fee has been paid, the server (102) transmitting an indication that the determined fee has been paid. (FIGS. 1, 3, 4, and 5A-5C).
  • 70. The method of example 69, wherein the identifier comprises a unique identifier of a travel session associated with a toll road, and wherein the fee comprises a fee for the travel session. (FIGS. 1, 3, 4, and 5A-5C).
  • 71. The method of example 69 or 70, wherein the communication network (116) comprises a local-area network. (FIGS. 1, 3, 4, and 5A-5C).
  • 72. The method of one of examples 69-71, wherein the communication network (116) comprises a wide-area network. (FIGS. 1, 3, 4, and 5A-5C).
  • 73. The method of example 72, wherein the wide-area network comprises the world-wide web. (FIGS. 1, 3, 4, and 5A-5C).
  • 74. The method of example 72, wherein the wide-area network comprises the Internet. (FIGS. 1, 3, 4, and 5A-5C).
  • 75. The method of one of examples 69-74, further comprising:
  • the server (102) receiving from the mobile device (106) via the communication network (116) the first location. (FIGS. 1, 3, 4, and 5A-5C).
  • 76. The method of one of examples 69-75, wherein the first location is proximate a location when a medium was dispensed from a dispensing device, wherein a code is disposed on the medium, and wherein the code encodes the identifier. (FIGS. 1, 3, 4, and 5A-5C).
  • 77. The method of example 76, further comprising:
  • the server (102) receiving from the dispenser terminal the first location. (FIGS. 1, 3, 4, and 5A-5C).
  • 78. The method of one of examples 69-76, further comprising:
  • the server (102) receiving from the mobile device (106) via the communication network (116) payment data to facilitate payment of the determined fee; and
  • the server (102) causing the determined fee to be paid using the payment data. (FIGS. 1, 3, 4, and 5A-5C).
  • 79. The method of one of examples 69-78, wherein the identifier is a first identifier, the method further comprising:
  • the server (102) receiving from the mobile device (106) via the communication network (116) a second identifier;
  • the server (102) causing the determined fee to be paid using payment data associated with the second identifier. (FIGS. 1, 3, 4, and 5A-5C).
  • 80. The method of one of examples 69-79, further comprising:
  • the server (102) transmitting to the mobile device (106) via the communication network (116) an indication that the fee was paid. (FIGS. 1, 3, 4, and 5A-5C).
  • 81. The method of one of examples 69-80, further comprising:
  • the server (102) transmitting to an exit terminal (108) an indication that the fee was paid, wherein the exit terminal (108) is configured for: (i) receiving from the server (102) the indication that the fee was paid, and (ii) responsive to receiving from the server (102) the indication that the fee was paid, causing an action to be performed. (FIGS. 1, 3, 4, and 5A-5C).
  • 82. The method of example 81, wherein causing the action to be performed comprises causing the action to be performed so as to permit a vehicle to exit a toll booth. (FIGS. 1, 3, 4, and 5A-5C).
  • 83. The method of example 82, wherein causing the action to be performed comprises causing an access control device in the toll booth lot to be moved. (FIGS. 1, 3, 4, and 5A-5C).
  • 84. A server (102) configured for performing the functions recited in one of examples 69-83. (FIGS. 1, 3, 4, and 5A-5C).
  • 85. A non-transitory computer-readable medium having stored thereon program instructions (192) that, when executed by a processor (182), cause performance of the functions recited in one of examples 69-83. (FIGS. 1, 3, 4, and 5A-5C).
  • 86. A mobile device (106) comprising:
  • a processor (150);
  • a capturing device (156) configured to capture a code;
  • a network interface (152) configured for facilitating communication between the mobile device (106) and a server (102); and
  • a non-transitory computer-readable medium having stored thereon program instructions (162) that, when executed by the processor (150), cause performance of the functions recited in one of examples 1-23 or 44-66. (FIGS. 1, 3, 4, and 5A-5C).
  • 87. A server (102) comprising:
  • a processor (150);
  • a network interface (184) configured for facilitating communication between the server (102) and another device; and
  • a non-transitory computer-readable medium having stored thereon program instructions (192) that, when executed by the processor (182), cause performance of the functions recited in one of examples 26-41 or 69-83. (FIGS. 1, 3, 4, and 5A-5C).
    • VI. Conclusion
  • Example embodiments have been described above. Those skilled in the art will understand that changes and modifications can be made to the described embodiments without departing from the true scope and spirit of the present invention, which is defined by the claims.
  • This detailed description describes various features and functions of the disclosed systems, devices, and methods with reference to the accompanying figures. In the figures, similar symbols typically identify similar components, unless context dictates otherwise. The illustrative embodiments described in the detailed description, figures, and claims are not meant to be limiting. Other embodiments can be used, and other changes can be made, without departing from the spirit or scope of the subject matter presented herein. It will be readily understood that the aspects of the present disclosure, as generally described herein, and illustrated in the figures, can be arranged, substituted, combined, separated, and designed in a wide variety of different configurations, all of which are explicitly contemplated herein.
  • With respect to any or all of the message flow diagrams, scenarios, and flow charts in the figures and as discussed herein, each step, block and/or communication can represent a processing of information and/or a transmission of information in accordance with example embodiments. Alternative embodiments are included within the scope of these example embodiments. In these alternative embodiments, for example, functions described as steps, blocks, transmissions, communications, requests, responses, and/or messages can be executed out of order from that shown or discussed, including in substantially concurrent or in reverse order, depending on the functionality involved. Further, more or fewer steps, blocks and/or functions can be used with any of the message flow diagrams, scenarios, and flow charts discussed herein, and these message flow diagrams, scenarios, and flow charts can be combined with one another, in part or in whole.
  • A step or block that represents a processing of information can correspond to circuitry that can be configured to perform the specific logical functions of a herein-described method or technique. Alternatively or additionally, a step or block that represents a processing of information can correspond to a module, a segment, or a portion of program code (including related data). The program code can include one or more instructions executable by a processor for implementing specific logical functions or actions in the method or technique. The program code and/or related data can be stored on any type of computer-readable medium such as a storage device including a disk or hard drive or other storage media.
  • The computer-readable medium can include non-transitory computer-readable media such as computer-readable media that stores data for short periods of time like register memory, processor cache, and/or random access memory (RAM). The computer-readable media can include non-transitory computer-readable media that stores program code and/or data for longer periods of time, such as secondary or persistent long term storage, like read only memory (ROM), optical or magnetic disks, and/or compact-disc read only memory (CD-ROM), for example. The computer-readable media can be any other volatile or non-volatile storage systems. A computer-readable medium can be considered a computer-readable storage medium, for example, or a tangible storage device. Any data identified as being stored within a data storage device or transmitted to a device for storage within a data storage device can comprise a computer data signal embodied in a carrier wave.
  • Moreover, a step or block that represents one or more information transmissions can correspond to information transmissions between software and/or hardware modules in the same physical device. However, other information transmissions can be between software modules and/or hardware modules in different physical devices.
  • While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting.

Claims (30)

1. A method comprising:
a mobile device capturing a code disposed on a medium, wherein the code encodes an identifier;
the mobile device decoding the captured code to recover the identifier;
the mobile device transmitting to a server via a communication network the recovered identifier;
the mobile device receiving from the server via the communication network a fee associated with the transmitted identifier, wherein the fee is a function of at least a time period between a first time and a second time that is after the first time; and
the mobile device transmitting authorization to pay the received fee.
2-4. (canceled)
5. The method of claim 1, wherein the code comprises a Quick Response code.
6-12. (canceled)
13. The method of claim 1, wherein the code further encodes the first time, the method further comprising:
the mobile device decoding the code to recover the first time; and
the mobile device transmitting to the server via the communication network the first time.
14. The method of claim 1, wherein the first time is proximate a time when the medium was dispensed from a dispenser terminal.
15. The method of claim 1, wherein the second time is proximate a time of the mobile device transmitting to the server via the communication network the recovered identifier.
16. The method of claim 1, further comprising:
the mobile device displaying the received fee.
17-20. (canceled)
21. The method of claim 1, further comprising:
providing the code displayed on the medium to an exit terminal.
22. The method of claim 1, further comprising:
the mobile device displaying the captured code; and
providing the code displayed on the medium to a capturing device.
23. The method of claim 1, further comprising:
the mobile device determining that the captured code has a particular property; and
responsive to the mobile device determining that the captured code has the particular property, the mobile device launching an application to facilitate payment of the received fee.
24-25. (canceled)
26. A method comprising:
a server receiving from a mobile device via a communication network the identifier;
responsive to the server receiving the identifier, the server determining a fee associated with the identifier, wherein the fee is a function of at least a time period between a first time and a second time;
the server transmitting to the mobile device via the communication network the determined fee;
the server receiving from the mobile device via the communication network authorization to pay the determined fee;
the server determining that the determined fee has been paid; and
responsive to the server determining that the determined fee has been paid, the server transmitting an indication that the determined fee has been paid.
27-43. (canceled)
44. A method comprising:
a mobile device capturing a code disposed on a medium, wherein the code encodes an identifier;
the mobile device decoding the captured code to recover the identifier;
the mobile device transmitting to a server via a communication network the recovered identifier;
the mobile device receiving from the server via the communication network a fee associated with the transmitted identifier, wherein the fee is a function of at least a distance between a first location and a second location that is different from the first location; and
the mobile device transmitting authorization to pay the received fee.
45-47. (canceled)
48. The method of claim 11, wherein the code comprises a Quick Response code.
49-55. (canceled)
56. The method of claim 11, wherein the code further encodes the first location, the method further comprising:
the mobile device decoding the code to recover the first location; and
the mobile device transmitting to the server via the communication network the first location.
57. The method of claim 11, wherein the first location is proximate a location of a dispenser terminal.
58. The method of claim 11, wherein the second location is proximate a location of the mobile device when transmitting to the server via the communication network the recovered identifier.
59. The method of claim 11, further comprising:
the mobile device displaying the received fee.
60-63. (canceled)
64. The method of claim 11, further comprising:
providing the code displayed on the medium to an exit terminal.
65. The method of claim 11, further comprising:
the mobile device displaying the captured code; and
providing the code displayed on the medium to a capturing device.
66. The method of claim 11, further comprising:
the mobile device determining that the captured code has a particular property; and
responsive to the mobile device determining that the captured code has the particular property, the mobile device launching an application to facilitate payment of the received fee.
67-68. (canceled)
69. A method comprising:
a server receiving from a mobile device via a communication network the identifier;
responsive to the server receiving the identifier, the server determining a fee associated with the identifier, wherein the fee is a function of at least a distance between a first location and a second location that is a different from the first location;
the server transmitting to the mobile device via the communication network the determined fee;
the server receiving from the mobile device via the communication network authorization to pay the determined fee;
the server determining that the determined fee has been paid; and
responsive to the server determining that the determined fee has been paid, the server transmitting an indication that the determined fee has been paid.
70-87. (canceled)
US14/442,036 2011-11-10 2013-11-12 Payment system and method Abandoned US20150324777A1 (en)

Applications Claiming Priority (9)

Application Number Priority Date Filing Date Title
GB201119375A GB201119375D0 (en) 2011-11-10 2011-11-10 Financial transaction processing system and method
US201261587416P 2012-01-17 2012-01-17
PCT/GB2012/052805 WO2013068768A1 (en) 2011-11-10 2012-11-12 Payment system and method
GBPCT/GB2012/052804 2012-11-12
GBPCT/GB2012/052805 2012-11-12
PCT/GB2012/052804 WO2013068767A1 (en) 2011-11-10 2012-11-12 Invoice payment system and method
GBPCT/GB2012/052802 2012-11-12
PCT/GB2012/052802 WO2013068765A1 (en) 2011-11-10 2012-11-12 Bill payment system and method
PCT/GB2013/052978 WO2014072751A1 (en) 2012-11-12 2013-11-12 Payment system and method

Publications (1)

Publication Number Publication Date
US20150324777A1 true US20150324777A1 (en) 2015-11-12

Family

ID=45421539

Family Applications (10)

Application Number Title Priority Date Filing Date
US14/356,558 Active 2034-06-22 US9679281B2 (en) 2011-11-10 2012-10-09 Online purchase processing system and method
US14/356,552 Active 2033-04-30 US10528935B2 (en) 2011-11-10 2012-11-12 Payment system and method
US14/356,568 Abandoned US20140289107A1 (en) 2011-11-10 2012-11-12 Invoice payment system and method
US14/356,563 Abandoned US20140310117A1 (en) 2011-11-10 2012-11-12 Bill payment system and method
US14/442,036 Abandoned US20150324777A1 (en) 2011-11-10 2013-11-12 Payment system and method
US14/682,660 Active 2033-07-05 US9679283B2 (en) 2011-11-10 2015-04-09 Online purchase processing system and method
US14/682,704 Active 2033-07-15 US9799024B2 (en) 2011-11-10 2015-04-09 Online purchase processing system and method
US14/682,744 Active 2032-11-16 US10346821B2 (en) 2011-11-10 2015-04-09 Online purchase processing system and method
US14/682,775 Active 2033-08-06 US9659287B2 (en) 2011-11-10 2015-04-09 Online purchase processing system and method
US15/292,273 Active US10475016B2 (en) 2011-11-10 2016-10-13 Bill payment system and method

Family Applications Before (4)

Application Number Title Priority Date Filing Date
US14/356,558 Active 2034-06-22 US9679281B2 (en) 2011-11-10 2012-10-09 Online purchase processing system and method
US14/356,552 Active 2033-04-30 US10528935B2 (en) 2011-11-10 2012-11-12 Payment system and method
US14/356,568 Abandoned US20140289107A1 (en) 2011-11-10 2012-11-12 Invoice payment system and method
US14/356,563 Abandoned US20140310117A1 (en) 2011-11-10 2012-11-12 Bill payment system and method

Family Applications After (5)

Application Number Title Priority Date Filing Date
US14/682,660 Active 2033-07-05 US9679283B2 (en) 2011-11-10 2015-04-09 Online purchase processing system and method
US14/682,704 Active 2033-07-15 US9799024B2 (en) 2011-11-10 2015-04-09 Online purchase processing system and method
US14/682,744 Active 2032-11-16 US10346821B2 (en) 2011-11-10 2015-04-09 Online purchase processing system and method
US14/682,775 Active 2033-08-06 US9659287B2 (en) 2011-11-10 2015-04-09 Online purchase processing system and method
US15/292,273 Active US10475016B2 (en) 2011-11-10 2016-10-13 Bill payment system and method

Country Status (8)

Country Link
US (10) US9679281B2 (en)
EP (4) EP2776995A1 (en)
JP (4) JP6160001B2 (en)
KR (5) KR20140093985A (en)
GB (1) GB201119375D0 (en)
IL (5) IL232376B (en)
WO (4) WO2013068719A1 (en)
ZA (2) ZA201403236B (en)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150170166A1 (en) * 2013-12-17 2015-06-18 Jvl Ventures, Llc Systems, methods, and computer program products for managing transaction data
US20150213529A1 (en) 2011-11-10 2015-07-30 Gelliner Limited Online Purchase Processing System and Method
US20150221140A1 (en) * 2014-02-04 2015-08-06 Gilbert Eid Parking and tollgate payment processing based on vehicle remote identification
US20150309156A1 (en) * 2014-04-25 2015-10-29 Palo Alto Research Center Incorporated Computer-Implemented System And Method For Tracking Objects Via Identifier-Tracker Pairings
US20170094514A1 (en) * 2015-09-29 2017-03-30 Morphotrust Usa, Llc System and method for using a symbol as instruction for a mobile identity to initiate transfer of authenticated identity information to a target system
US20180341932A1 (en) * 2017-05-29 2018-11-29 Mastercard International Incorporated Method for setting up a recurring payment
CN109118271A (en) * 2018-07-17 2019-01-01 成都宜泊信息科技有限公司 A kind of electronics is of use voucher delivery system
US20190199691A1 (en) * 2017-12-22 2019-06-27 Mastercard International Incorporated Method and system for trusted notifications

Families Citing this family (118)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9047601B2 (en) 2006-09-24 2015-06-02 RFCyber Corpration Method and apparatus for settling payments using mobile devices
US9010646B2 (en) 2010-04-01 2015-04-21 Coin, Inc. Optical contact loaded magnetic card
US8998096B2 (en) 2010-04-01 2015-04-07 Coin, Inc. Magnetic emissive use of preloaded payment card account numbers
US8984276B2 (en) * 2012-01-10 2015-03-17 Jpmorgan Chase Bank, N.A. System and method for device registration and authentication
US20130346176A1 (en) * 2012-06-20 2013-12-26 Zachery Alolabi System and method for payment incentivizing
US8639619B1 (en) 2012-07-13 2014-01-28 Scvngr, Inc. Secure payment method and system
WO2014031888A1 (en) * 2012-08-23 2014-02-27 Gcs Investments, Ltd. Business to business invoice generation and payment system and method using mobile phones
US20140101036A1 (en) * 2012-10-10 2014-04-10 Mastercard International Incorporated Methods and systems for conducting remote point of sale transactions
US20160155112A1 (en) * 2012-10-10 2016-06-02 Mastercard International Incorporated Barcode-triggered payment method and system
US20140108247A1 (en) 2012-10-17 2014-04-17 Groupon, Inc. Peer-To-Peer Payment Processing
US10235692B2 (en) 2012-10-17 2019-03-19 Groupon, Inc. Consumer presence based deal offers
US9852417B2 (en) 2012-11-05 2017-12-26 Mfoundry, Inc. QR code-enabled P2P payment systems and methods
US20140229375A1 (en) 2013-02-11 2014-08-14 Groupon, Inc. Consumer device payment token management
US20230196328A1 (en) * 2013-02-14 2023-06-22 Advanced New Technologies Co., Ltd. Data interaction method and device, and offline credit payment method and device
US9953286B2 (en) 2013-03-06 2018-04-24 United Parcel Service Of America, Inc. Shipping preferences population systems and related methods
US9852409B2 (en) 2013-03-11 2017-12-26 Groupon, Inc. Consumer device based point-of-sale
US9576286B1 (en) 2013-03-11 2017-02-21 Groupon, Inc. Consumer device based point-of-sale
US10482511B1 (en) 2013-03-12 2019-11-19 Groupon, Inc. Employee profile for customer assignment, analytics and payments
US9613348B2 (en) * 2013-05-20 2017-04-04 Vega LLC Methods, systems, and media for conducting transactions using transaction codes
CN103236935B (en) * 2013-05-21 2016-04-13 北京梅泰诺电子商务有限公司 A kind of two-dimension code user registration certification system and method thereof
JP5578256B1 (en) * 2013-07-01 2014-08-27 富士ゼロックス株式会社 Information processing apparatus and program
GB201312398D0 (en) * 2013-07-10 2013-08-21 Powa Technologies Ltd Electronic transaction validation
US8770478B2 (en) 2013-07-11 2014-07-08 Scvngr, Inc. Payment processing with automatic no-touch mode selection
KR20150021306A (en) * 2013-08-20 2015-03-02 (주)인스타페이 Shopping payment systme and method of using graphical code including bar code or qr code
US9756056B2 (en) * 2013-09-04 2017-09-05 Anton Nikolaevich Churyumov Apparatus and method for authenticating a user via multiple user devices
US11886952B2 (en) 2013-09-17 2024-01-30 Integrated Solutions International, Llc Systems and methods for point of sale age verification
EP3637301B1 (en) 2013-09-17 2023-04-05 Integrated Solutions International LLC Systems and methods for decoding and using data on cards
US10867143B2 (en) 2013-09-17 2020-12-15 Integrated Solutions International, Llc Systems and methods for age-restricted product registration
US10867144B2 (en) 2013-09-17 2020-12-15 Integrated Solutions International Llc Systems and methods for point of sale age verification
US9928493B2 (en) 2013-09-27 2018-03-27 Groupon, Inc. Systems and methods for providing consumer facing point-of-sale interfaces
TWI654863B (en) 2013-10-18 2019-03-21 新力股份有限公司 Communication control device, communication control method, and terminal device
US9721314B2 (en) * 2013-10-28 2017-08-01 Square, Inc. Apportioning shared financial expenses
US10491587B2 (en) * 2013-10-28 2019-11-26 Singou Technology Ltd. Method and device for information system access authentication
US9652137B2 (en) * 2013-10-31 2017-05-16 Tencent Technology (Shenzhen) Company Limited Method and device for confirming and executing payment operations
US9467828B2 (en) * 2013-11-08 2016-10-11 Gogo Llc Systems and methods for configuring an electronic device for cellular-based communications
US9916577B1 (en) * 2013-11-26 2018-03-13 Wells Fargo Bank, N.A. Multi channel purchasing for interoperable mobile wallet
US10410196B1 (en) 2013-11-29 2019-09-10 Intuit Inc. System and method to enable payment using mark generation and mobile device
CN104753911B (en) * 2013-12-31 2019-03-15 腾讯科技（深圳）有限公司 A kind of information processing method based on social application, relevant apparatus and system
US9928547B2 (en) 2014-01-03 2018-03-27 The Toronto-Dominion Bank Systems and methods for providing balance notifications to connected devices
US10296972B2 (en) 2014-01-03 2019-05-21 The Toronto-Dominion Bank Systems and methods for providing balance notifications
US9916620B2 (en) 2014-01-03 2018-03-13 The Toronto-Dominion Bank Systems and methods for providing balance notifications in an augmented reality environment
WO2015105688A1 (en) * 2014-01-09 2015-07-16 @Pay Ip Holdings, Llc Email based e-commerce with qr code barcode, image recognition alternative payment method and biometrics
JP5720811B1 (en) 2014-01-30 2015-05-20 富士ゼロックス株式会社 Document management system, document management apparatus, and program
FI20145247L (en) * 2014-03-17 2015-09-18 Lvi Wabek Oy Order system and method for online shopping
GB201407639D0 (en) 2014-04-30 2014-06-11 Ecrebo Ltd A method and system for payment with confirmation via code image
US11100571B1 (en) 2014-06-10 2021-08-24 Wells Fargo Bank, N.A. Systems and methods for payee identification via camera
SG10201403766QA (en) * 2014-07-01 2016-02-26 Mastercard Asia Pacific Pte Ltd A Method For Conducting A Transaction
US20160036828A1 (en) * 2014-08-01 2016-02-04 Larry Hughes Secure two-dimensional barcodes
CN105337950B (en) * 2014-08-14 2019-02-19 阿里巴巴集团控股有限公司 A kind of form filling method and associated terminal
US20160055576A1 (en) * 2014-08-22 2016-02-25 Ian Reddy System and method for a two-step negotiation process
US9628270B2 (en) 2014-09-09 2017-04-18 Microsoft Technology Licensing, Llc Cryptographically-verifiable attestation label
WO2016100480A1 (en) * 2014-12-16 2016-06-23 Passtask, Llc Whophoto message system
US10147094B2 (en) * 2014-12-17 2018-12-04 Mastercard International Incorporated Method to enable consumers to make purchases at point of sale devices using their mobile number
CN104732380A (en) * 2015-02-16 2015-06-24 小米科技有限责任公司 Method and device for conducting account transfer processing
US10373226B1 (en) 2015-06-16 2019-08-06 Amazon Technologies, Inc. Interactive parking facilities
CN106487859B (en) * 2015-09-01 2019-08-30 北京国双科技有限公司 Monitor method, apparatus, terminal device and the system of user access activity
US10685317B2 (en) * 2015-09-22 2020-06-16 United States Postal Service Trackable postage
GB2545889A (en) 2015-11-17 2017-07-05 Gelliner Ltd Payment confirmation system and method
CN105511915A (en) * 2015-12-01 2016-04-20 小米科技有限责任公司 Information processing method and device
DE102015225792B3 (en) * 2015-12-17 2017-04-13 Volkswagen Aktiengesellschaft A method and system for secure communication between a mobile device coupled to a smartphone and a server
WO2017137979A1 (en) * 2016-02-14 2017-08-17 Ronen Levy Information system
JP7296723B2 (en) * 2016-02-24 2023-06-23 ソニーグループ株式会社 Information processing device and method, and information processing system
US11341495B2 (en) * 2016-02-29 2022-05-24 Paypal, Inc. Electronic method for instantly creating an account with a service provider during point of sale
US10776838B2 (en) * 2016-03-01 2020-09-15 Mx Technologies, Inc. Item level data aggregation
US11720983B2 (en) 2016-03-02 2023-08-08 Up N' Go System to text a payment link
US10242377B2 (en) 2016-03-02 2019-03-26 Mastercard International Incorporated Systems and methods for analyzing businesses based on gratuities
US20170256007A1 (en) * 2016-03-02 2017-09-07 Touradj Barman Text payment system
US10108412B2 (en) 2016-03-30 2018-10-23 Square, Inc. Blocking and non-blocking firmware update
US11068899B2 (en) 2016-06-17 2021-07-20 Visa International Service Association Token aggregation for multi-party transactions
US10341267B2 (en) * 2016-06-20 2019-07-02 Microsoft Technology Licensing, Llc Anonymized identifiers for secure communication systems
US10817869B2 (en) 2016-06-29 2020-10-27 Square, Inc. Preliminary enablement of transaction processing circuitry
US11010765B2 (en) 2016-06-29 2021-05-18 Square, Inc. Preliminary acquisition of payment information
US10158834B2 (en) * 2016-08-30 2018-12-18 Hand Held Products, Inc. Corrected projection perspective distortion
US10445571B1 (en) * 2016-09-01 2019-10-15 United Services Automobile Association Document data capture
US10445709B2 (en) 2016-09-28 2019-10-15 The Toronto-Dominion Bank Real time virtual draft system and method
CA2970088C (en) 2016-09-30 2022-02-08 The Toronto-Dominion Bank Device lock bypass on selectable alert
GB2570825A (en) * 2016-11-07 2019-08-07 Walmart Apollo Llc Reducing cybersecurity risks when purchasing products over a network
US10915881B2 (en) 2017-01-27 2021-02-09 American Express Travel Related Services Company, Inc. Transaction account charge splitting
US20180225649A1 (en) * 2017-02-06 2018-08-09 American Express Travel Related Services Company, Inc. Charge splitting across multiple payment systems
US11107061B2 (en) * 2017-03-10 2021-08-31 Jpmorgan Chase Bank, N.A. System and method for implementing payment via quick response (QR) code
US11334869B2 (en) * 2017-03-29 2022-05-17 Innoviti Payment Solutions Private Limited Method and system for establishing secure communication between terminal device and target system
CH714700B1 (en) * 2017-04-10 2020-02-14 Ringler Informatik Ag Methods and apparatus for recording a person's data and documents.
CN111340498B (en) * 2017-06-23 2024-03-12 创新先进技术有限公司 Method and device for realizing off-line transaction
US10445487B2 (en) * 2017-07-20 2019-10-15 Singou Technology (Macau) Ltd. Methods and apparatus for authentication of joint account login
KR102023173B1 (en) * 2017-07-31 2019-09-19 주식회사 찹스틱스와이드 QR Code Integration Platform
US11107556B2 (en) * 2017-08-29 2021-08-31 Helix OpCo, LLC Authorization system that permits granular identification of, access to, and recruitment of individualized genomic data
EP3454277A1 (en) 2017-09-07 2019-03-13 Mastercard Asia/Pacific Pte. Ltd Transaction system architecture and methods
US11587054B2 (en) * 2017-09-22 2023-02-21 Mastercard International Incorporated Optical-scan triggered electronic funds transfer for purchase transaction
JP7035434B2 (en) * 2017-10-02 2022-03-15 株式会社デンソーウェーブ Payment system
US11093475B2 (en) * 2017-11-03 2021-08-17 Salesforce.Com, Inc. External change detection
CN113126935A (en) * 2017-12-04 2021-07-16 西安艾润物联网技术服务有限责任公司 Taxi invoice acquisition method and system and computer readable storage medium
US10950088B2 (en) * 2017-12-21 2021-03-16 Igt System and method for utilizing virtual ticket vouchers
US10595073B2 (en) * 2018-06-03 2020-03-17 Apple Inc. Techniques for authorizing controller devices
US20190392063A1 (en) * 2018-06-25 2019-12-26 Microsoft Technology Licensing, Llc Reducing data loss in remote databases
FR3082978B1 (en) * 2018-06-25 2021-04-23 Reacteur COMMUNICATION PROCESS BETWEEN A USER AND A SERVER
CA3009685C (en) 2018-06-27 2023-08-08 The Toronto-Dominion Bank Automatic generation and population of digital interfaces based on adaptively processed image data
CN109040072B (en) * 2018-08-06 2021-03-12 武汉斗鱼网络科技有限公司 Method, system, server and storage medium for client to authorize login of webpage
US10664848B2 (en) * 2018-10-10 2020-05-26 Capital One Services, Llc Methods, mediums, and systems for document authorization
US11880438B2 (en) 2018-10-17 2024-01-23 Integrated Solutions International, Llc Systems and methods for age restricted product activation
GB2581315A (en) * 2018-10-30 2020-08-19 Barclays Execution Services Ltd Secure data communication
SG10201810001YA (en) 2018-11-09 2020-06-29 Mastercard International Inc Payment methods and systems by scanning qr codes already present in a user device
US10990969B2 (en) 2018-12-21 2021-04-27 Square, Inc. Point of sale (POS) systems and methods for dynamically processing payment data based on payment reader capability
US11049095B2 (en) 2018-12-21 2021-06-29 Square, Inc. Point of sale (POS) systems and methods with dynamic kernel selection
US10762196B2 (en) * 2018-12-21 2020-09-01 Square, Inc. Point of sale (POS) systems and methods with dynamic kernel selection
CN109857351A (en) * 2019-02-22 2019-06-07 北京航天泰坦科技股份有限公司 The Method of printing of traceable invoice
US11853997B2 (en) * 2019-02-27 2023-12-26 International Business Machines Corporation Using quick response (QR) codes to collect recurring payments
CN111709006A (en) 2019-03-01 2020-09-25 开利公司 Unlocking method and system for air conditioning unit
CN110119973A (en) * 2019-05-14 2019-08-13 李成 A kind of virtual assets tripartite rent method and its system based on two dimensional code
US10839369B1 (en) * 2019-07-22 2020-11-17 Capital One Services, Llc Dynamic electronic communication with variable messages using encrypted quick response codes
CN110443659A (en) * 2019-08-07 2019-11-12 北京微电票技术服务有限公司 A kind of invoice generation method and system
RU2738949C1 (en) * 2020-01-17 2020-12-18 Роман Олегович Бондарь Classification system of participants of public event for purposes of searching common areas of technologies for development and exchange of messages between participants
US20220012697A1 (en) * 2020-07-07 2022-01-13 Up N' Go Intermediary advanced payment processes
KR20220005097A (en) * 2020-11-30 2022-01-12 베이징 바이두 넷컴 사이언스 테크놀로지 컴퍼니 리미티드 Product handling methods and components, electronic devices, computer readable media
JP2022091577A (en) * 2020-12-09 2022-06-21 株式会社リコー Information processing device, information processing method, program, and information process system
US11983756B2 (en) * 2021-10-27 2024-05-14 Qi Technologies, Llc Quick information portal
CN114611541A (en) * 2022-03-11 2022-06-10 平安科技（深圳）有限公司 Invoice image recognition method, device, equipment and storage medium
US20230367979A1 (en) * 2022-05-10 2023-11-16 Rory James QR Code Application Device
JP7471381B1 (en) 2022-12-20 2024-04-19 ＰａｙＰａｙ株式会社 Payment system, payment method, payment service providing device, and program

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120095791A1 (en) * 2010-10-14 2012-04-19 Xerox Corporation Computer-Implemented System And Method For Offering Merchant And Shopper-Friendly Parking Reservations
US20120265585A1 (en) * 2010-04-13 2012-10-18 Quickpay Corp. Location based systems for entry and exit

Family Cites Families (122)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS61133455A (en) 1984-12-04 1986-06-20 Sanyo Electric Co Ltd Transmission system
US6968319B1 (en) 1996-10-18 2005-11-22 Microsoft Corporation Electronic bill presentment and payment system with bill dispute capabilities
WO1998020411A1 (en) * 1996-11-08 1998-05-14 Neomedia Technologies, Inc. Automatic access of electronic information through machine-readable codes on printed documents
WO1999004326A2 (en) 1997-07-15 1999-01-28 Neomedia Technologies, Inc. Printed coupons with embedded discounts for online purchases
US6144959A (en) 1997-08-18 2000-11-07 Novell, Inc. System and method for managing user accounts in a communication network
US7083087B1 (en) * 2000-09-18 2006-08-01 E-Micro Corporation Method and apparatus for associating identification and personal data for multiple magnetic stripe cards or other sources
US6131811A (en) * 1998-05-29 2000-10-17 E-Micro Corporation Wallet consolidator
US6151426A (en) * 1998-10-01 2000-11-21 Hewlett-Packard Company Click and select user interface for document scanning
US6577861B2 (en) 1998-12-14 2003-06-10 Fujitsu Limited Electronic shopping system utilizing a program downloadable wireless telephone
EP1183613A4 (en) * 1999-04-05 2006-06-21 Neomedia Tech Inc System and method of using machine-readable or human-readable linkage codes for accessing networked data resources
US8479012B1 (en) 1999-10-19 2013-07-02 Harris Technology, Llc Using biometrics as an encryption key
US20010037297A1 (en) * 2000-03-09 2001-11-01 Mcnair Edward Parry Bill paying with the aid of a scanner
JP2001266055A (en) * 2000-03-17 2001-09-28 Hitachi Information Technology Co Ltd Method and system for slip processing
AU2001253030A1 (en) 2000-03-31 2001-10-15 Neomedia Technologies, Inc. System for accessing internet via wireless device using linkage url bar-code
JP4243411B2 (en) 2000-05-09 2009-03-25 日本電気株式会社 Settlement method for transactions of goods or services
JP3683787B2 (en) * 2000-07-28 2005-08-17 和弘 永田 Fully reproducible articulator
US8825535B2 (en) 2000-08-24 2014-09-02 Martin Herman Weik, III Management and control system for a designated functional space having at least one portal
EP1195973A1 (en) 2000-10-05 2002-04-10 Digital Rum Ltd. Method for registering a user into new services by sending a permanent PIN via SMS or e-mail
US6993507B2 (en) 2000-12-14 2006-01-31 Pacific Payment Systems, Inc. Bar coded bill payment system and method
JP2002207838A (en) 2001-01-09 2002-07-26 Advance Design Corp Personal authentication service method using portable telephone
US20120173387A1 (en) * 2011-01-04 2012-07-05 Albert Talker E-Commerce electronic data centrally distributed and collected
US7363388B2 (en) 2001-03-28 2008-04-22 Siebel Systems, Inc. Method and system for direct server synchronization with a computing device
US7349884B1 (en) 2001-03-29 2008-03-25 Gsc Enterprises, Inc. Method and apparatus for electronic commerce services at a point of sale
JP2003006611A (en) 2001-06-21 2003-01-10 Hitachi Ltd Image fetching method for automatic machine
JP3770812B2 (en) * 2001-06-22 2006-04-26 日立オムロンターミナルソリューションズ株式会社 Branch terminal for financial institutions
BR0117159A (en) * 2001-10-17 2004-10-19 Primeselections Com Inc Digital interactive network appliance and system
JP2003141689A (en) 2001-11-07 2003-05-16 Ntt Communications Kk Parking lot management system and parking lot management program
US7080327B1 (en) * 2001-11-09 2006-07-18 Cypress Semiconductor Corporation Multi-level quick click icon hierarchy and/or activation
US20030177090A1 (en) 2002-03-12 2003-09-18 Guy Eden System and method for automatic bill payment
KR100459270B1 (en) * 2002-03-21 2004-12-03 송정준 The method using credit card in mobile phone
US8331907B2 (en) 2003-02-18 2012-12-11 Roamware, Inc. Integrating GSM and WiFi service in mobile communication devices
JP2004280626A (en) 2003-03-18 2004-10-07 Matsushita Electric Ind Co Ltd Mediation service system on information communication network
JP2005056333A (en) 2003-08-07 2005-03-03 Seiko Epson Corp Check processor, program, electronic settlement system, and method for controlling check processing
JP2005135093A (en) 2003-10-29 2005-05-26 Fujitsu Ltd Electronic payment support system and electronic payment support apparatus
US7707039B2 (en) 2004-02-15 2010-04-27 Exbiblio B.V. Automatic modification of web pages
JP4305847B2 (en) 2004-03-26 2009-07-29 富士通株式会社 Store settlement method, system and program
US20070300142A1 (en) 2005-04-01 2007-12-27 King Martin T Contextual dynamic advertising based upon captured rendered text
EP1587014A1 (en) 2004-04-16 2005-10-19 Pitney Bowes Inc. Method and system for using a camera cell phone in transactions
FR2870067B1 (en) * 2004-05-05 2006-06-16 Radiotelephone Sfr METHOD OF RECHARGING A SUBSCRIPTION CARD BY WIRELESS EQUIPMENT
CA2568160A1 (en) 2004-05-17 2005-11-24 Dexrad (Proprietary) Limited Document creation and authentication system
US20060002614A1 (en) * 2004-06-30 2006-01-05 Alliances Artquest International Inc. Raster-to-vector conversion process and apparatus
JP4898101B2 (en) 2004-07-02 2012-03-14 株式会社リコー Printing apparatus, printing method, printing program, and recording medium
US20060047725A1 (en) 2004-08-26 2006-03-02 Bramson Steven J Opt-in directory of verified individual profiles
CN1598881A (en) 2004-09-17 2005-03-23 深圳市博思高科技有限公司 Intelligent timing fee collecting system of parking lot
JP2005100429A (en) 2004-10-12 2005-04-14 Fujitsu Ltd Portable device
JP2006186564A (en) 2004-12-27 2006-07-13 Ntt Communications Kk User information collection system, information input terminal, and program
JP2006251944A (en) 2005-03-09 2006-09-21 E Bank Corp Account opening system, account opening method and program
JP2006268446A (en) 2005-03-24 2006-10-05 Ntt Comware Corp Settlement intermediary system, settlement intermediary device, settlement request terminal, settlement intermediary method, settlement intermediary request method and computer program
US7594189B1 (en) 2005-04-21 2009-09-22 Amazon Technologies, Inc. Systems and methods for statistically selecting content items to be used in a dynamically-generated display
US20060283935A1 (en) * 2005-05-16 2006-12-21 Henry Scott P Systems and methods for processing commercial transactions
US20080189185A1 (en) * 2005-08-10 2008-08-07 Ebank Corporation Account Opening Method
JP2007086915A (en) 2005-09-20 2007-04-05 Toshiba Corp Facility use notification system
KR20070055069A (en) 2005-11-25 2007-05-30 윤석주 A toll collection system and method for using rfid tag
KR20070108315A (en) * 2005-12-07 2007-11-09 한국전자통신연구원 Appartus and method for privacy information sharing service using signed callback url message
JP4842631B2 (en) * 2005-12-12 2011-12-21 ソニー・エリクソン・モバイルコミュニケーションズ株式会社 Information sharing system, portable information terminal, information management server, and information sharing method
KR100820356B1 (en) * 2005-12-16 2008-04-10 (주) 이토프 Settlement device using mobile and the peocedure thereof
US7949609B2 (en) 2006-01-06 2011-05-24 Brian Colella System for secure online selling, buying and bill pay in an electronic commerce setting
US7625392B2 (en) * 2006-02-03 2009-12-01 James Coleman Wound closure devices and methods
JP4886365B2 (en) 2006-06-01 2012-02-29 ヤフー株式会社 Method for verifying identity and server for realizing the method
US20070299775A1 (en) 2006-06-02 2007-12-27 Kenneth Algiene Systems and methods for associating a second source of funds with an electronic check transaction
JP2007323613A (en) 2006-06-05 2007-12-13 Media Portal Japan Co Ltd Method for providing public utility charge collection service using mobile
JP2007328695A (en) 2006-06-09 2007-12-20 Index:Kk Authentication device, authentication method, and program for authentication
US8249350B2 (en) 2006-06-30 2012-08-21 University Of Geneva Brand protection and product autentication using portable devices
US9911114B2 (en) 2006-07-06 2018-03-06 Qualcomm Incorporated Methods and systems for making a payment via a stored value card in a mobile environment
KR101290989B1 (en) * 2006-08-09 2013-07-30 삼성전자주식회사 Method and apparatus for providing financial service using mobile station in packet data system and system thereof
KR20080020153A (en) 2006-08-31 2008-03-05 주식회사 아이캐시 System and method for taking an electronic voucher from the off-line media via a mobile phone
US7958081B2 (en) 2006-09-28 2011-06-07 Jagtag, Inc. Apparatuses, methods and systems for information querying and serving on mobile devices based on ambient conditions
JP2008129635A (en) 2006-11-16 2008-06-05 Dainippon Printing Co Ltd Settlement method and proxy settlement server
US20080189208A1 (en) * 2007-02-06 2008-08-07 Xerox Corporation Optical character reading machine having bill payment capability
US8935187B2 (en) 2007-03-07 2015-01-13 Playspan, Inc. Distributed payment system and method
US20090319425A1 (en) 2007-03-30 2009-12-24 Obopay, Inc. Mobile Person-to-Person Payment System
JP2008257540A (en) 2007-04-06 2008-10-23 Toyo Business Engineering Corp Settlement system
SG147345A1 (en) * 2007-05-03 2008-11-28 Ezypay Pte Ltd System and method for secured data transfer over a network from a mobile device
US20080284185A1 (en) 2007-05-14 2008-11-20 Steven Joseph Pixley Harbormaster
JP2008305292A (en) 2007-06-11 2008-12-18 Cfj Kk Automatic contract system and computer program
DE102007048976A1 (en) 2007-06-29 2009-01-02 Voice.Trust Ag Virtual prepaid or credit card and method and system for providing such and for electronic payments
KR101404606B1 (en) * 2007-08-21 2014-06-10 삼성전자주식회사 A method of providing menus by using a touchscreen and a multimedia apparatus thereof
JP5403895B2 (en) * 2007-10-31 2014-01-29 株式会社東芝 Information providing server and information providing method
JP5238229B2 (en) * 2007-11-21 2013-07-17 株式会社エヌ・ティ・ティ・データ Account transfer acceptance system, acceptance device, terminal device, and computer program
KR100905315B1 (en) * 2007-12-20 2009-07-02 피씨닥터 주식회사 Authentication service method using public certification in mobile environment
US7802720B2 (en) * 2008-01-04 2010-09-28 Intuit Inc. Method and system for performing a card-present transaction using image capture on a portable device
US20110184843A1 (en) 2008-01-31 2011-07-28 Bill.Com, Inc. Enhanced electronic anonymous payment system
JP5223372B2 (en) * 2008-02-27 2013-06-26 富士電機株式会社 Information collection device
JP5603539B2 (en) 2008-03-03 2014-10-08 セイコーエプソン株式会社 Liquid crystal device and electronic device
US20090265231A1 (en) 2008-04-22 2009-10-22 Xerox Corporation Online discount optimizer service
US8031207B2 (en) * 2008-06-04 2011-10-04 Mastercard International, Inc. Card image description format to economize on data storage
JP5226408B2 (en) * 2008-07-15 2013-07-03 株式会社エヌ・ティ・ティ・データ Continuation card payment registration system and computer program
WO2010013296A1 (en) * 2008-08-01 2010-02-04 ギルネット株式会社 Settlement method and settlement system using portable terminal
ATE524897T1 (en) * 2008-09-17 2011-09-15 Gmv Soluciones Globales Internet S A METHOD AND SYSTEM FOR AUTHENTICATING A USER USING A MOBILE TELEPHONE DEVICE
KR101036681B1 (en) 2008-10-24 2011-05-23 손두식 Payment service method and its system using mobile phone
JP2010128736A (en) 2008-11-27 2010-06-10 Toppan Printing Co Ltd Server, method, and program for registering participation in campaign
KR20100062255A (en) 2008-12-01 2010-06-10 해태제과식품주식회사 System for managing point and method thereof
JP2010157153A (en) * 2008-12-29 2010-07-15 It Cars Co Ltd Order information management device, order information management system configured by using the same and program for managing order information
US9536238B2 (en) * 2008-12-31 2017-01-03 Peter Garrett Hand-held electronics device for aggregation of and management of personal electronic data
US8645383B2 (en) 2009-01-27 2014-02-04 Stephen J. Brown Content management system using sources of experience data and modules for quantification and visualization
JP2010277580A (en) * 2009-04-30 2010-12-09 Alpha Japan Co Ltd Server device, content distribution system, and gateway server device
CA2665832C (en) 2009-05-11 2015-12-29 Diversinet Corp. Method and system for authenticating a user of a mobile device
US20110089233A1 (en) 2009-05-29 2011-04-21 Aixum Ag Device and process for the authentication of authorizations or enablement of a person with the use of a mobile communication device
US8955747B2 (en) 2009-06-23 2015-02-17 At&T Mobility Ii Llc Devices, systems and methods for wireless point-of-sale
WO2011003467A1 (en) * 2009-07-10 2011-01-13 Tomtom International B.V. Touchscreen input on a multi-view display screen
KR101429618B1 (en) * 2009-10-08 2014-08-12 에스케이플래닛 주식회사 Payment System, Mobile used therein and Method therefor
US20110137742A1 (en) 2009-12-09 2011-06-09 Ebay Inc. Payment using unique product identifier codes
KR101068022B1 (en) * 2009-12-11 2011-09-28 아라정보(주) Authentication processing system for mobile payments and how to process mobile payments
US20110270751A1 (en) 2009-12-14 2011-11-03 Andrew Csinger Electronic commerce system and system and method for establishing a trusted session
JP2011141785A (en) 2010-01-08 2011-07-21 Girunetto Kk Member registration system using portable terminal and authentication system
JP2011141849A (en) 2010-01-09 2011-07-21 Girunetto Kk Prepaid and postpaid payment system using mobile terminal, small-amount transfer method, point service system, and escrow service system
KR101145377B1 (en) 2010-02-26 2012-05-15 세종대학교산학협력단 System for calculating order and method thereby
US20110210922A1 (en) * 2010-02-26 2011-09-01 Research In Motion Limited Dual-screen mobile device
JP2011210171A (en) 2010-03-30 2011-10-20 Japan Research Institute Ltd Settlement server, settlement system, settlement method, and settlement program
KR20110112142A (en) * 2010-04-06 2011-10-12 주식회사 훈솔루션 Mobile e-payment service using a reference string and method
US8380177B2 (en) * 2010-04-09 2013-02-19 Paydiant, Inc. Mobile phone payment processing methods and systems
US20110251910A1 (en) 2010-04-13 2011-10-13 James Dimmick Mobile Phone as a Switch
EP2585996A4 (en) * 2010-06-28 2014-08-20 Mastercard International Inc Methods, systems, and computer readable media for registering in a merchant sponsored program using a near field communication (nfc) device
KR101476228B1 (en) 2010-09-09 2014-12-30 에스케이텔레콤 주식회사 System and method for managing parking lot using nfc tag
US7992773B1 (en) 2010-09-15 2011-08-09 Reagan Inventions, Llc System and method for presenting information about an object on a portable electronic device
KR20120097789A (en) 2011-02-25 2012-09-05 최민석 Apparatus guiding position of car and method using the same
JP2012190308A (en) 2011-03-11 2012-10-04 Mitsubishi Precision Co Ltd Parking ticket authentication system
US20120234906A1 (en) 2011-03-14 2012-09-20 Hariraam Varun Ganapathi Parking system and method
US10402898B2 (en) * 2011-05-04 2019-09-03 Paypal, Inc. Image-based financial processing
JP2013003678A (en) * 2011-06-13 2013-01-07 Canon Inc Information processing apparatus, information processing method, and program
US9173090B2 (en) * 2011-09-15 2015-10-27 Teletech Holdings, Inc. Method for activating services associated with a product via a service center supporting a variety of products
GB201119375D0 (en) 2011-11-10 2011-12-21 Merburn Ltd Financial transaction processing system and method

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120265585A1 (en) * 2010-04-13 2012-10-18 Quickpay Corp. Location based systems for entry and exit
US20120095791A1 (en) * 2010-10-14 2012-04-19 Xerox Corporation Computer-Implemented System And Method For Offering Merchant And Shopper-Friendly Parking Reservations

Cited By (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10346821B2 (en) 2011-11-10 2019-07-09 Gelliner Limited Online purchase processing system and method
US20150213529A1 (en) 2011-11-10 2015-07-30 Gelliner Limited Online Purchase Processing System and Method
US10528935B2 (en) 2011-11-10 2020-01-07 Gelliner Limited Payment system and method
US10475016B2 (en) 2011-11-10 2019-11-12 Gelliner Limited Bill payment system and method
US20150170166A1 (en) * 2013-12-17 2015-06-18 Jvl Ventures, Llc Systems, methods, and computer program products for managing transaction data
US20150221140A1 (en) * 2014-02-04 2015-08-06 Gilbert Eid Parking and tollgate payment processing based on vehicle remote identification
US10634760B2 (en) 2014-04-25 2020-04-28 Palo Alto Research Center Incorporated Computer-implemented system and method for object tracking via identifier-tracker pairings
US10955520B2 (en) 2014-04-25 2021-03-23 Palo Alto Research Center Incorporated Computer-implemented system and method for object tracking via identifier-tracker pairings
US11867825B2 (en) 2014-04-25 2024-01-09 Xerox Corporation Computer-implemented system and method for object tracking via identifier-tracker pairings
US20150309156A1 (en) * 2014-04-25 2015-10-29 Palo Alto Research Center Incorporated Computer-Implemented System And Method For Tracking Objects Via Identifier-Tracker Pairings
US9638787B2 (en) * 2014-04-25 2017-05-02 Palo Alto Research Center Incorporated Computer-implemented system and method for tracking objects via identifier-tracker pairings
US9801065B2 (en) * 2015-09-29 2017-10-24 Morphotrust Usa, Llc System and method for using a symbol as instruction for a mobile identity to initiate transfer of authenticated identity information to a target system
US10200863B2 (en) 2015-09-29 2019-02-05 Morphotrust Usa, Llc System and method for using a symbol as instruction for a target system to request identity information and authentication from a mobile identity
US20170094514A1 (en) * 2015-09-29 2017-03-30 Morphotrust Usa, Llc System and method for using a symbol as instruction for a mobile identity to initiate transfer of authenticated identity information to a target system
US9801064B2 (en) 2015-09-29 2017-10-24 Morphotrust Usa, Llc System and method for using a symbol as instruction for a target system to request identity information and authentication from a mobile identity
US20180341932A1 (en) * 2017-05-29 2018-11-29 Mastercard International Incorporated Method for setting up a recurring payment
US20190199691A1 (en) * 2017-12-22 2019-06-27 Mastercard International Incorporated Method and system for trusted notifications
US11146539B2 (en) * 2017-12-22 2021-10-12 Mastercard International Incorporated Method and system for trusted notifications
US11855969B2 (en) 2017-12-22 2023-12-26 Mastercard International Incorporated Method and system for trusted notifications
CN109118271A (en) * 2018-07-17 2019-01-01 成都宜泊信息科技有限公司 A kind of electronics is of use voucher delivery system

Also Published As

Publication number Publication date
KR20140093985A (en) 2014-07-29
WO2013068719A1 (en) 2013-05-16
WO2013068768A1 (en) 2013-05-16
EP2776997A1 (en) 2014-09-17
WO2013068765A1 (en) 2013-05-16
US20150213530A1 (en) 2015-07-30
US10475016B2 (en) 2019-11-12
US20150213528A1 (en) 2015-07-30
IL261822A (en) 2018-10-31
GB201119375D0 (en) 2011-12-21
IL232377B (en) 2018-12-31
US9679283B2 (en) 2017-06-13
EP2776996A1 (en) 2014-09-17
US20140316991A1 (en) 2014-10-23
IL232376A0 (en) 2014-08-31
JP2015506004A (en) 2015-02-26
US9799024B2 (en) 2017-10-24
US9659287B2 (en) 2017-05-23
ZA201507645B (en) 2022-03-30
US20170032350A1 (en) 2017-02-02
US20140310117A1 (en) 2014-10-16
IL232377A0 (en) 2014-06-30
KR20140093710A (en) 2014-07-28
JP2015501965A (en) 2015-01-19
IL232375A0 (en) 2014-06-30
IL261822B (en) 2020-03-31
JP6214544B2 (en) 2017-10-18
IL232378B (en) 2019-05-30
KR20180107276A (en) 2018-10-01
US10346821B2 (en) 2019-07-09
ZA201403236B (en) 2021-05-26
EP2776995A1 (en) 2014-09-17
JP2015503147A (en) 2015-01-29
KR20140089597A (en) 2014-07-15
JP2015504197A (en) 2015-02-05
WO2013068767A1 (en) 2013-05-16
US20140289107A1 (en) 2014-09-25
US10528935B2 (en) 2020-01-07
JP6172609B2 (en) 2017-08-09
US20150213527A1 (en) 2015-07-30
KR101954477B1 (en) 2019-03-05
EP2776998A1 (en) 2014-09-17
IL232378A0 (en) 2014-06-30
US20150213529A1 (en) 2015-07-30
IL232376B (en) 2018-10-31
IL232375B (en) 2019-03-31
KR20140102673A (en) 2014-08-22
US20150178757A1 (en) 2015-06-25
US9679281B2 (en) 2017-06-13
JP6160001B2 (en) 2017-07-12
JP6168367B2 (en) 2017-07-26

Similar Documents

Publication Publication Date Title
US20150324777A1 (en) Payment system and method
CN102509364B (en) Automobile fee payment system and method capable of barrier-free access
WO2014072751A1 (en) Payment system and method
US20130073347A1 (en) Vehicular citation management method and system
US10152759B2 (en) Systems and methods for promotional validation of travel expenses
JP6383249B2 (en) Parking lot electronic payment system, parking lot electronic payment method, program
WO2009062330A1 (en) System and method for operation and/or for control of service terminals and apparatus suitable therefor
CN1912907A (en) Safety payoff system and safety payoff method
RU2656960C2 (en) Transport system user checking
AU2013343236B2 (en) Payment system and method
CA2890815C (en) Payment system and method
US10062077B2 (en) Automatic data transfer
KR101861720B1 (en) Method, device and system for managing parking area
WO2017069700A1 (en) Method and system for managing payment transactions
CN108109214B (en) Automatic gate opening method, settlement device, storage medium and computer equipment
TWI536290B (en) Management devices, management methods, and programs
KR20150084948A (en) Payment system and method
CA2914175C (en) Method for avoiding the misuse of access authorisations of an id-based access control system
JP2009230216A (en) Use charge calculation method and use charge calculation system
WO2017146565A1 (en) System and method of processing gaming machine payout wirelessly
RU2016120753A (en) Method of payment for travel in public transport
US20180122151A1 (en) Place management method and place management system
CN114399846A (en) Parking fee payment method, payment device and storage medium
LT6632B (en) An automated method to pay for a car in a car park
KR20190063262A (en) Rewards managing system

Legal Events

Date Code Title Description
AS Assignment

Owner name: GELLINER LIMITED, ISLE OF MAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MOSHAL, MARTIN PAUL;REEL/FRAME:035851/0568

Effective date: 20150604

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION