+

WO2015094265A1 - Transaction de paiement - Google Patents

Transaction de paiement Download PDF

Info

Publication number
WO2015094265A1
WO2015094265A1 PCT/US2013/076451 US2013076451W WO2015094265A1 WO 2015094265 A1 WO2015094265 A1 WO 2015094265A1 US 2013076451 W US2013076451 W US 2013076451W WO 2015094265 A1 WO2015094265 A1 WO 2015094265A1
Authority
WO
WIPO (PCT)
Prior art keywords
merchant
user
payment
electronic device
communication
Prior art date
Application number
PCT/US2013/076451
Other languages
English (en)
Inventor
John T. Brassil
Pratyusa Kumar Manadhata
Original Assignee
Hewlett-Packard Development Company, L.P.
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 Hewlett-Packard Development Company, L.P. filed Critical Hewlett-Packard Development Company, L.P.
Priority to PCT/US2013/076451 priority Critical patent/WO2015094265A1/fr
Publication of WO2015094265A1 publication Critical patent/WO2015094265A1/fr

Links

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/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322—Aspects of commerce using mobile devices [M-devices]
    • G06Q20/3223—Realising banking transactions through 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/08—Payment architectures
    • G06Q20/16—Payments settled via telecommunication systems

Definitions

  • Figure 1 is a schematic illustration of an example of system for facilitating payment transaction processing in accordance with an implementation of the present disclosure.
  • Figure 2 illustrates a flow chart showing an example of a method for facilitating payment transaction processing in accordance with an implementation of the present disclosure.
  • Figure 3 illustrates a flow chart showing an example of an alternative method for facilitating payment transaction processing in accordance with an implementation of the present disclosure.
  • Figure 4 illustrates a flow chart showing an example of yet another alternative method for facilitating payment transaction processing in accordance with an
  • Portable electronic devices e.g., tablets, laptops, smartphones, etc.
  • Different users rely on different type of portable electronic devices for many day-to-day activities and work related tasks.
  • the large number of users that utilize different type of electronic devices stimulates providers to offer devices that can meet the increase in user demand, support the broad array of available services, and provide reliable communication.
  • Portable electronic devices come in different sizes, forms, and may include different technical features. Due to the proliferation of electronic devices, their technological capabilities are continuously increasing. Consequently, these devices also offer expanded services to their users. These electronic devices are often used to access the Internet, purchase various goods and services, and process payments from the users of these electronic devices to various merchants or other parties.
  • Mobile payment transactions have become extremely popular in recent years. It is estimated that the total global mobile transactions may reach $600 billion in 2013.
  • the mobile payment usually involves some type of electronic payment method.
  • credit cards, debit cards, or wire transfers are used as electronic payment methods.
  • Mobile payments are preferred by many consumers because they use the convenience of a credit card payment but there is no need to carry a wallet with the actual physical card. Constantly carrying a wallet with one or more payment cards may be
  • NFC near filed communication
  • special hardware e.g., secure processors
  • special software e.g., secure processors
  • these types of mobile payments require installing special terminals (e.g., NFC capable point of sale terminals). Installing special equipment for processing remote mobile payments on the merchant's side may be costiy.
  • Some of the transactions between the consumers (i.e., users of mobile devices) and merchants may involve small payment amounts and the merchant may not frequently use the instaifed equipment.
  • the merchant may not justify the cost of installing such equipment, in addition, there is always a concern related to security and privacy of the user's information (e.g., credit card numbers, user's address, etc.) exchanged during a mobile payment
  • the user's information e.g., credit card numbers, user's address, etc.
  • the present description is directed to systems, methods, and computer readable media for facilitating payment transaction processing. Specifically, the present description proposes a novel and previously unforeseen approach for processing payments between a user of an electronic device ⁇ i.e., a consumer) and a merchant by using the user's mobile operator and information already available to the mobile operator.
  • the disclosed systems, methods, and computer readable media propose enabling electronic device users, which are authorized credit card holders, to pay merchants for goods or services by using their electronic devices without installing any special hardware or saving credit card information on the devices.
  • the proposed systems, methods, and computer readable media also do not require that a merchant installs a special point of service terminal in order to receive the payment from the user.
  • the disclosure proposes using information (users credit card information, merchant's account information, etc.) that may be stored at the users mobile operator and, therefore, is securely accessible to the mobile operator.
  • information users credit card information, merchant's account information, etc.
  • a payment transaction between the user of the electronic device and the merchant may be processed based on a request from the user, from the merchant, or from both parties.
  • the payment transaction may be processed by the mobile operator or by an independent service provider that has an authorized and secured connection the mobile operator and can receive communication from the user and the merchant.
  • the transaction is conducted over secured data communication channels already implemented and used by the mobile operator and is sent to a backend payment processor that operates in a conventional fashion.
  • Mobile operators also called mobile providers, wireless service providers, wireless operators, etc.
  • eiectronic devices e.g., smart phones, tablets, etc.
  • mobile operators may store name, address, credit card information, and other types of persona! information for the user.
  • Merchants may or may not be subscribed to the services of the mobile operators to participate in the proposed payment transaction, if the merchants are subscribed to the services of the mobile operators, the mobile operator also stores different information for the merchants (e.g., name, identification member, bank account information, address, etc.).
  • mobile operators use various tools to maintain security of the mobile communications on their mobile networks and to ensure privacy of the information that shared via these mobile networks.
  • Mobile operators are required to follow specific security procedures and policies when capture, record, process, store, and destroy such personal information. Therefore, mobile operators have the necessary information and security capabilities to act as trusted parties for processing payments between a user and a merchant. Users already trust mobile operators to maintain and process personal information. Therefore, mobile operators or systems that are in secure communication with the mobile operators may assist users with processing payments to merchants based on a request from the users.
  • these operations can be performed without the need to install any hardware/software or the user's eiectronic device and without requiring the merchants to purchase special payment processing devices, in addition, these payment processing services may be offered by a third party (e.g., a payment processing vendor) that works closely with the mobile operators and can communicate with both consumers and merchants.
  • a third party e.g., a payment processing vendor
  • the proposed payment transaction processing solution offers various advantages to all participants in the electronic payment ecosystem and offers a cost effective way to conduct sales and to receive payments in a timely and secure manner.
  • the payment transaction processing systems, methods, and computer readable media do not require any changes to the exiting electronic payment ecosystem and increases the opportunity to easily initiate payment transactions. This may ultimately lead to more electronic payment transactions.
  • the proposed solution is easy to implement since it does not require special software/hardware on the user's electronic device or special hardware on the merchant's end.
  • the payment transaction processing solution is secured since it uses exiting secured communication channels of the mobile operator and does not store any payment or credit card information on the electronic device.
  • the proposed payment transaction processing solution offers an opportunity to the mobile operator or the system providing the described services to collect various data related to the payment transactions (e.g., amount, merchant, product being purchased, time of purchase, location, etc.).
  • the collected data may be monetized, used for direct targeted advertisement, or used to provide other services to the users.
  • a method for facilitating payment transaction processing is provided.
  • the method can be performed by a processor of the electronic device.
  • a non- transitory machine-readable storage medium may store computer programs or modules, which when executed by the electronic device cause the method to be performed.
  • the method includes receiving, at a mobile operator, a communication from an electronic device.
  • the communication requests a payment transaction to a merchant from a user of the electronic device.
  • the method also includes initiating the payment transaction between the user and the merchant; receiving, at the mobile operator, a verification that the payment transaction between the user and the merchant is accepted: and sending confirmations that the payment transaction between the user and the merchant is accepted to the user of the electronic device and to the merchant.
  • a system for facilitating payment transaction processing includes a computing device having at least one processor.
  • the processor includes a control unit to receive a message from an electronic device, the message requesting a payment to a merchant from a user of the electronic device.
  • the control unit is to retrieve credit card information for the user from a database of a mobile operator, where the credit card information is correlated to at least one telephone number associated with the electronic device.
  • the control unit is further to retrieve account information of the merchant, send a communication to a payment processor to initiate the payment between the user and the merchant, and send confirmations to the user of the electronic device and to the merchant that the payment is accepted after receiving verification from the payment processor.
  • a non-transitory machine-readable storage medium encoded with instructions executable by at least one processor comprises instructions to receive, at the at least one processor, a first communication from an electronic device and a second communication from a merchant, both communications requesting a payment transaction to the merchant from a user of the electronic device.
  • the machine-readable storage medium further comprises instructions to identify the user of the electronic device based on a mobile number of the user, send a third communication to a payment processor to initiate the payment transaction between the user and the merchant, receive a verification after the payment transaction between the user and the merchant is accepted, and send confirmations to the user of the electronic device and to the merchant that the payment transaction is accepted.
  • the terms “electronic device,” “mobile device,” and “wireless device” are to be used interchangeably and refer to any one of various smartphones, cellular telephones, tablets, personal data assistants (PDA's), laptops, computers, servers, and other similar electronic devices that include a processor and are capable of communicating with other electronic devices via wireless or wired communication networks.
  • the terms “merchant” refers to one of various business organizations, stores, online retailers, businesspersons, shops, and other similar entities or individuals that offer goods or services for sale and receive payments in exchange to these goods and services.
  • the principal user of the electronic device may or may not be the owner of the electronic device (e.g., when the device is owned by a corporation and is used by an employee) but is the person who uses the device on a regular basis, can modify the settings of the device, and can use the device to process payments.
  • FIG. 1 is a schematic illustration of an example of a system 5 for facilitating payment transaction processing.
  • the system 5 includes at least one computing device 10 capable of carrying out the techniques described below.
  • the computing device 10 can be a personal computer, a laptop, a server, a mobile device, a plurality of dist imped computing devices, or any other suitable computing device.
  • the computing device 10 may be controlled by a mobile operator (not shown) or by a third party (e.g., a payment processing vendor, not shown) that offers the services described below to users of electronic devices.
  • the computing device 10 includes at least one processing device 30, a memory resource 35, a communication interface 50, and input interface(s) 45.
  • the computing device 10 includes additional, fewer, or different components for carrying out similar functionality described herein.
  • the computing device 10 includes software, hardware, or a suitable combination thereof configured to enable functionality of the computing device 10 and to allow it to carry the techniques described below and to interact with the one or more external systems/devices.
  • the computing device 10 includes communication interfaces ⁇ e.g., a Wi-Fi® interface, a Bluetooth® interface, a 3G interface, a 4G interface, a near filed communication (NFC) interface, etc.) that are used to connect with external devices/systems and/or to a network (not shown).
  • communication interfaces e.g., a Wi-Fi® interface, a Bluetooth® interface, a 3G interface, a 4G interface, a near filed communication (NFC) interface, etc.
  • the computing device 10 can communicate with at least one electronic device 15 to receive a request for a payment transaction from a user of the electronic device 15 and to a payment processor 20 to send information required to complete the payment transaction, it is to be understood that the operations described as being performed by the computing device 10 that are related to this description may, in some implementations, be performed or distributed between the computing device 10 and other computing devices (not shown).
  • the computing device 10 communicates with the electronic device 15 and with the payment processor 20 via a network (not shown).
  • the network may include any suitable type or configuration of network to allow for communication between the computing device 10, the electronic device 15, the payment processor 20, and any other external devices/systems.
  • the network may include a wide area network ⁇ "WAN" (e.g., a TCP/IP based network, a cellular network, such as, for example, a Global System for Mobile Communications (“GSM”) network, a General Packet Radio Service (“GPRS”) network, a Code Division Multiple Access (“CDMA”) network, an Evolution-Data Optimized (“EV-DO”) network, an Enhanced Data Rates for GSM Evolution (“EDGE”) network, a 3GS network, a 4GSM network, a Digital Enhanced Cordiess Telecommunications ⁇ "DECT”) network, a Digital AMPS nS-136/TDMA”) network, or an Integrated Digital Enhanced Network fiDEN”) network, etc.
  • GSM Global System for Mobile Communications
  • GPRS General Packet Radio Service
  • CDMA Code Division Multiple Access
  • EV-DO Evolution-Data Optimized
  • EDGE Enhanced Data Rates for GSM Evolution
  • 3GS a 3GS network
  • 4GSM Digital Enhanced Cordiess Telecommunications ⁇
  • the network 25 can further include a local area network ⁇ "LAN”), a neighborhood area network ⁇ "NAN”), a home area network (“HAN”), a persona! area network (“PAN”), a public switched telephone network (“PSTN”), an intranet, the Internet, or any other suitable network.
  • the electronic device 15 may be a mobile electronic device (e.g., a smartphone), a stationary electronic device (e.g., a desktop computer ⁇ , or a convertible electronic device (e.g., a conversable laptop).
  • the electronic device 15 may be a tablet, a laptop, a personal computer, an all in one computing device, a gaming console, a server, a mobile telephone, a music player, a visual player, a personal digital assistant (PDA), a cellular telephone, an electronic notepad, a plurality of distributed computing devices, or any other suitable electronic device that is capable of communicating with other electronic systems or devices via a network.
  • the electronic device 15 may also include at least one processor, a display screen, a memory resource, a communication interface, and input interface(s), and any other suitable components (the elements of the electronic device 15 are not shown).
  • the processing device 30 of the computing device 10 e.g., a central processing unit, a group of distributed processors, a microprocessor, a microcontroller, an application-specific integrated circuit (ASIC), a graphics processor, a multiprocessor, a virtual processor, a cloud processing system, or another suitable controller or
  • ASIC application-specific integrated circuit
  • the communication interface 50 enables the computing device 10 to communicate with plurality of networks, communication links, and external devices.
  • the input interfaces 45 can receive information from any internal or external devices/systems in communication with the computing device 10.
  • the input interfaces 45 include at least a data interface 60.
  • the input interfaces 45 can include additional interfaces.
  • the data interface 60 receives communications from the electronic device 15.
  • communications may include a request for a payment transaction to a merchant from the user of the electronic device 15.
  • the communications may include at least information about the payment amount to be transferred to the merchant, an
  • the processor 30 includes a controller 33 (also called a control unit) and may be implemented using any suitable type of processing system where at least one processor executes computer-readable instructions stored in the memory 35.
  • the memory resource 35 includes any suitabie type, number, and configuration of volatile or non-transitory machine-readable storage media 37 to store instructions and data.
  • Examples of machine-readable storage media 37 in the memory 35 include read-only memory (“ROM”), random access memory ⁇ '"RAM”) (e.g., dynamic RAM ['"DRAM”], synchronous DRAM ["SDRAM”], etc.), electrically erasable programmable read-oniy memory (“EEPROM”), flash memory, an SD card, and other suitable magnetic, optical, physical, or electronic memory devices.
  • ROM read-only memory
  • RAM random access memory
  • EEPROM electrically erasable programmable read-oniy memory
  • flash memory an SD card
  • the memory resource 35 may also be used for storing temporary variables or other intermediate information ⁇ e.g., information received from users or merchants, etc.) during execution of instructions to by the processor 30.
  • the memory 35 may also store an operating system 70 and network applications 75.
  • the operating system 70 can be multi-user, multiprocessing, multitasking, multithreading, and real-time.
  • the operating system 70 can also perform basic tasks such as recognizing input from input devices, such as a keyboard, a keypad, a mouse, or a touch input object (e.g., a finger); sending output to a projector and a camera; keeping track of files and directories on memory 35; controlling peripheral devices, such as printers, image capture device; and managing traffic on the bus 55.
  • the network applications 75 include various components for establishing and maintaining network connections, such as computer-readable instructions for implementing communication protocols including TCP/IP, HTTP, Ethernet®, USB®, and FireWire®.
  • Software stored on the non-transitory machine-readable storage media 37 and executed by the processor 30 includes, for example, firmware, applications, program data, filters, rules, program modules, and other executable instructions.
  • the control unit 33 retrieves from the machine-readable storage media 37 and executes, among other things, instructions related to the control processes and methods described herein.
  • the instructions stored in the non-transitory machine- readable storage media 37 implement a payment transaction processing module 40 and an information retrieval module 41. in other examples, the instructions can implement more or fewer modules ⁇ e.g., various other modules related to the operation of the system 5).
  • the modules 40 and 41 include, for example, a hardware device including electronic circuitry for implementing the functionality described below, such as control logic and/or memory.
  • the modules 40 and 41 may be implemented as a series of instructions encoded on a machine- readable storage medium and executable by a processor.
  • the payment transaction processing module 40 processes payment transactions to merchants from users of different electronic devices'! 0 that are in communication with the computing device 10. !n addition, the information retrieval module 41 retrieves the necessary information (e.g., user's credit card information, merchant's account information, etc.) related to the users or the merchants to assist with processing of the payment transactions.
  • the necessary information e.g., user's credit card information, merchant's account information, etc.
  • the memory 35 may include at least one database 80.
  • the system 5 may access external database (e.g. , database 82 ⁇ that may be stored remotely of the electronic device 15 (e.g. , can be accessed via a network or a cloud), in one implementation, the external database 82 is a Home Location Register ("HLR") or a Home Subscriber Server (“HSS”) of the mobile operator controlling the computing device 10.
  • the HLR/HSS may be a master user database of permanent subscriber information for a mobile operator or a network.
  • the HLR may contain pertinent user-related information (e.g., name, address, account status, credit card information, preferences, etc.).
  • the HLR/HSS may also be used to perform authentication and authorization of the user, and can provide information about the user's location and IP information.
  • the external database 82 may be another database accessible by the mobile operator or a third party.
  • information about the user and the merchant may be retrieved via different elements of the mobile operator's core network (e.g., Evolved Packet Core).
  • Evolved Packet Core Evolved Packet Core
  • Figure 2 illustrates a flow chart showing an example of a method 100 for facilitating payment transaction processing, in one example, the method 100 can be executed by the control unit 33 of the processor of the electronic device 15.
  • the method 100 can be executed by the control unit 33 of the processor of the electronic device 15.
  • Various elements or blocks described herein with respect to the method 100 are capable of being executed simultaneously, in parallel, or in an order that differs from the illustrated serial manner of execution.
  • the method 100 is also capable of being executed using additional or fewer elements than are shown in the illustrated examples.
  • the method 100 may be executed in the form of instructions encoded on a non-transitory machine-readable storage medium 37 executable by a processor 30 of the electronic device 15.
  • the instructions for the method 100 implement the payment transaction processing module 40 and the information retrieval module 41.
  • the execution of the method 100 may be distributed between the processing device 30 and other processing devices in communication with the processing device 30.
  • the computing device 10 may be a device of a mobile operator and may be controlled by a mobile operator that also provides services to the user of the electronic device 15. As explained in additional details below, the mobile operator may provide secure payment processing services to the users of the electronic devices 10.
  • the method 100 begins at block 110, where the processor 30 receives a communication from an electronic device ⁇ e.g., the device 10). It is to be understood that although the process 100 is described as being executed by the processor 30, some steps in the process 100 may be executed by other computing
  • the communication may be received at another device of the mobile operator.
  • the communication requests a payment transaction to a merchant from a user of the electronic device 15.
  • a user of the electronic device 15 may walk into a merchant's physical location and determine the specific product and/or service that he or she is interested in.
  • the merchant may provide the user with a price of the item/service and an identification of the item/service (e.g., name, item/service ID, etc.).
  • the user may then send a communication to the computing device 10 that may include at least a payment amount for the item/service, an item identification that describes the item/service, and a merchant identification (e.g., name, ID, telephone number etc, of the merchant), in other implementations, additional information may also be included in the communication (e.g., merchant account bank information, user's name, etc.).
  • a communication may include at least a payment amount for the item/service, an item identification that describes the item/service, and a merchant identification (e.g., name, ID, telephone number etc, of the merchant), in other implementations, additional information may also be included in the communication (e.g., merchant account bank information, user's name, etc.).
  • SMS short message service
  • an application instalfed on the user's device 15 a message transmitted via an application instalfed on the user's device 15
  • a phone call from the user to the mobile operator e.g., to a representative or to an automated voice response system
  • the user may provide information to the computing device 15 by entering data via HTTP (e.g., by accessing a website).
  • HTTP HyperText Transfer Protocol
  • the computing device 10 may identify the user of the eiectronic device based on a mobile number of the user (e.g., by using a
  • the control unit 33 initiates the payment transaction between the user and the merchant (at 120). For example, to initiate the payment transaction between the user and the merchant, the control unit 33 sends at least credit card information for the user, the payment amount, and an account information of the merchant to the payment processor 20. In an alternative example, the payment transaction between the user and the merchant may be initiated by another device/processor in communication with the computing device 10. !n order to retrieve the credit card information for the user, the control unit 33 contacts a database of the mobile operator that includes different information associated with the user. That database may be the database 82 that already includes user information, the database 80, or another database.
  • the mobile operator generally stores user's name and credit card information (e.g., in order to process the user's monthly payments, to hold a security deposit, etc.), that information is easily accessible to the computing device 10 and can be quickly retrieved.
  • the control unit 33 initiates the payment transaction between the user and the merchant
  • the controi unit 33 sends a processing confirmation to the electronic device 15.
  • the processing confirmation to the device 15 may include at least a processing identification (i.e., a processing ID or record number of the sent payment transaction request), the payment amount, and the merchant identification.
  • the merchant involved in the payment transaction aiso uses the services of the mobile operator that controls the computing device 10. in that situation, the computing device 10 retrieves the account information (e.g., bank account, etc.) of the merchant based on a merchant identification (ID, telephone number, etc.) from the main database that stores subscriber information for the customers of the mobile operator (e.g., database 82, database 80, etc.).
  • the merchant identification may be available to the user and the user can provide it in the
  • the merchant may not be directly involved with this process.
  • the merchant may provide the account information to the user and the user may include it in the communication to the computing device 10.
  • the merchant may provide account information to ail mobile operators to facilitate this type of payment processing although the merchant may not be using their mobile services.
  • the merchant may also provide a telephone number in order to receive inquires and confirmations related to the payment transactions. In that situation, the merchant may or may not be a customer of the mobile operator.
  • the merchants account information may be stored at the payment processor 20 (e.g., when the merchant provides that information to different payment processors).
  • the control unit 33 initiates the payment transaction, the controi unit may send merchant identification (received from the user or the merchant) to the payment processor 20 and the payment processor 20 may look up the merchant's account information based on the received merchant identification.
  • the control unit 33 receives a verification from the payment processor 20 that the payment transaction between the user and the merchant is accepted ⁇ at 130).
  • the verification from the payment processor 20 may be received at the computing device 10 or any other device /system of the mobile operator that is in communication with the computing device 10.
  • the verification may be any type of communication that includes information (e.g., payment processing number, etc.) that indicates that the payment transaction requested by the uses is accepted.
  • the payment processor 20 is an existing system/service that handles credit card transactions and other types of electronic payments for various parties.
  • the payment processor 20 receives (e.g., via a payment gateway) the payment transaction request from the computing device 10, the payment processor contacts the issuing bank of the user's credit card with both credit card information and the merchant account information.
  • the issuing bank authorizes the payment request if funds are available, and then replies to the payment processor accordingly. If the transaction is authorized, the issuing bank completes the settlement with the merchant's bank directly without involving the payment processor 20.
  • the payment processor 20 completes the payment transaction between the user and the merchant with the user's credit card information and the account information of the merchant.
  • the payment processor 20 cannot authorize the payment transaction, the payment processor 20 sends a payment refusal message to the computing device 10.
  • control unit 33 sends confirmations to the user of the electronic device 15 and to the merchant that the payment transaction between the user and the merchant is accepted. For example, the control unit 33 sends the verification
  • the confirmations that the payment transaction is accepted may be sent by another other device /processor of the mobile operator that is in communication with the computing device 10.
  • the control unit 33 may only send a confirmation that the payment is completed to the user and not to the merchant. The user may the show that confirmation to the merchant in order to receive the desired product/service.
  • the control 33 may send a rejection of the payment to the user of the electronic device and to the merchant after receiving a payment refusal from the payment processor 20,
  • the described process allows a user to purchase a product or a service from a merchant completely anonymously, without involving the merchant at ail.
  • the computing device may retrieve all necessary information to process the payment based only on the communication from the user (i.e., payment amount, merchant identification, etc.).
  • the proposed process does not require any new software and/or hardware at either the user or the merchant, and also does not require any changes to the exiting electronic payment ecosystem.
  • the process is easy to implement and is secured since it uses the already exiting secured communication channels of the mobile operator.
  • Figure 3 illustrates a flow chart showing an example of an alternative method 200 for facilitating payment transaction processing.
  • the method 200 can be executed by the control unit 33 of the processor of the electronic device 15.
  • the execution of the method 100 may be distributed between the processing device 30 and other processing devices in communication with the processing device 30.
  • Various elements or blocks described herein with respect to the method 200 are capable of being executed simultaneously, in parallel, or in an order that differs from the illustrated serial manner of execution.
  • the method 200 may be executed in the form of instructions encoded on a non-transitory machine-readable storage medium 37 executable by a processor 30 of the electronic device 15.
  • the instructions for the method 200 implement the payment transaction processing module 40 and the information retrieval module 41.
  • the computing device 10 is not controlled by a mobile operator but is operated by a third party that offers payment processing services to various users of electronic devices.
  • the computing device 10 communicates with the payment processor 20 and may communicate with one or more mobile operators (i.e., to access information at the database 82),
  • the computing device 10 may be in communication with the HL /HSS to form a strongly integrated, secure infrastructure for exchange of information between the merchant and the consumer, it is to be understood that when the computing device 10 is controlled by a third party, the communication and data exchange between the computing device 10 and the mobile operators may be implemented by using variety of technologies and systems.
  • Some of the steps in the method 200 may be similar to the steps described in relation to the method 100.
  • the method 200 begins at block 205, where the processor 30 receives a message from the electronic device 15.
  • the message requests a payment to a merchant from a user of the electronic device 15.
  • the message is similar to the communication described in step 110 of the method 100 and includes at least a payment amount, an item identification, and a merchant identification, in one example, the message may also include the phone number or an email for the merchant.
  • the computing device 10 may retrieve the merchant's phone number/email based on the provided merchant identification (i.e., from a merchant's database maintained by the third party operating the computing device 10).
  • the controi unit 33 may also a confirmation message to the merchant inquiring whether the merchant is to receive the mobile payment from the user. That way, the control unit 33 may seek a validation from the merchant for the requested payment transaction.
  • the control unit 33 retrieves credit card information for the user from a database of a mobile operator.
  • the computing device 10 the computing device 10
  • the computing device 10 uses the teiephone number of the user identified from the message of the electronic device 15 to retrieve credit card information for that user.
  • the credit card information in the database 82 is correlated to at least one telephone number associated with the electronic device 15.
  • the computing device 10 also retrieves account information of the merchant (at 215).
  • the account information for the merchant is retrieved from the database 82 of a mobile operator when the merchant is a customer of the mobile operator and the message from the electronic device 15 includes a merchant identification and/or a telephone number that are stored in the database 82 of the mobile operator.
  • the account information for the merchant may be retrieved from an internal database to the computing device 10 (e.g., database 80). In that implementation, merchants provide their account information to the third party that controls the computing device 10 in advance.
  • the account information is stored in the database and is associated with a merchant identification ⁇ ID, merchant's telephone number, etc.) that can be provided by a user that requests a payment to be made to that merchant.
  • the third party controlling the computer device 15 has an agreement with the mobile operators that allows the computer device 15 to securely access databases of the mobile operators.
  • the merchant's account information may be stored at the payment processor 20 (e.g., when the merchant provides that information to different payment processors).
  • the control unit 33 may send merchant identification (received from the user or the merchant) to the payment processor 20 and the payment processor 20 may look up the merchant's account information based on the received merchant identification.
  • the control unit 33 sends a communication to the payment processor 20 to initiate the payment between the user and the merchant. This step is similar to step 120 of the method 100.
  • the control unit 33 sends at least the users credit card information, the payment amount, and the account information of the merchant to the payment processor 20.
  • the control unit may send a merchant identification and the payment processor may retrieve the merchant's account information based on the received merchant identification.
  • the payment processor 20 processes the payment between the user and the merchant as previously described.
  • the control unit 33 sends confirmations to the user of the electronic devicel O and to the merchant that the payment is accepted after the computing device 10 receives a verification from the payment processor 20. This step is similar to steps 130 and 140 of the method 100.
  • the control 33 may send a rejection of the payment to the user of the electronic device and to the merchant after receiving a payment refusal from the payment processor 20.
  • Figure 4 illustrates a flow chart showing an example of another alternative method 200 for facilitating payment transaction processing
  • the method 300 can be executed by the control unit 33 of the processor of the electronic device 15.
  • the execution of the method 100 may be distributed between the processing device 30 and other processing devices in communication with the processing device 30.
  • Various elements or blocks described herein with respect to the method 300 are capable of being executed simuitaneousiy, in parallel, or in an order that differs from the illustrated serial manner of execution.
  • the method 300 may be executed in the form of instructions encoded on a non-transitory machine-readable storage medium 37 executable by a processor 30 of the electronic device 15.
  • the instructions for the method 300 implement the payment transaction processing module 40 and the information retrieval module 41.
  • both the user and the merchant send initial payment transaction requests to the computing device 10.
  • the computing device 10 may be controlled either by a mobile operator or by a third party that offers payment processing services.
  • the computing device 10 is controlled by the mobile operator, some of the steps in the method 300 may be similar to the steps of the method 100.
  • the computing device 0 is controlled by a third party, some of the steps in the method 300 may be similar to the steps of the method 200.
  • the method 300 begins at block 305, where the processor 30 receives a first communication from the electronic device 15 and a second communication from a merchant. Both communications request a payment transaction to the merchant from a user of the electronic device.
  • the communications may be similar to the
  • the first communication from the electronic device 15 may include at least a payment amount, item identification, and a merchant identification.
  • the second communication from the merchant may include at least the payment amount, the item identification, the merchant identification, the mobile number of the user, and account information of the merchant, in another example, the merchant may verify the identity of the user (e.g., for security reasons or because the user is purchasing tobacco, iiquor, etc.) by asking for an identification. In thai situation, the second communication may also include the name of the user,
  • the computing device 10 may compare the first communication and the second communication to confirm that at feast one of the user, the merchant identification, the payment amount, and the item identification match. For example, when the merchant provides the user's name to the computing device 10, the device 10 compares the provided user name with the name thai is associated with the user's phone number. In addition, the computing device 10 aiso compares the other information included in the first communication and the second communication. Thai way, the system offers security to both the user and the merchant that the requested payment transaction corresponds to the agreement between these two parties (i.e., that is for the agreed amount) and that the user actualiy owns the electronic device 15 and is authorized to make payments.
  • a user of the electronic device 15 may have several mobile numbers associated with thai device.
  • the user may provide the merchant with a mobile number that she or he uses only to make payments and not for other purposes. That way, the merchant may not use the provided mobile number for collecting data and/or targeted advertising.
  • the control unit 33 identifies the user of the electronic device based on a mobile number of the user (at 310).
  • the computing device 15 may identify the user of the electronic device based on the mobile number of the user ⁇ e.g., when the device 15 is in the network of the mobile operator).
  • the control unit sends a third communication to a payment processor to initiate the payment transaction between the user and the merchant. This step is simiiar io step 120 of the method 100 and to step 220 of the method 200.
  • the coniroi unit 33 receives a verification after the payment transaction between the user and the merchant is accepted ⁇ at 320) and sends confirmations to the user of the electronic device 15 and to the merchant that the payment transaction is accepted (at step 325).
  • Steps 320 and 325 are similar to 130-140 of method 100 and to step 225 of the method 200.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Finance (AREA)
  • Telephonic Communication Services (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

Un procédé est décrit selon un aspect de la présente invention. Le procédé consiste à recevoir, au niveau d'un opérateur mobile, une communication provenant d'un dispositif électronique. La communication sollicite une transaction de paiement, provenant d'un utilisateur du dispositif électronique, à un commerçant. Le procédé consiste également à initier la transaction de paiement entre l'utilisateur et le commerçant, recevoir, au niveau de l'opérateur mobile, une vérification selon laquelle la transaction de paiement entre l'utilisateur et le commerçant est acceptée, et envoyer des confirmations, selon lesquelles la transaction de paiement entre l'utilisateur et le commerçant est acceptée, à l'utilisateur du dispositif électronique et au commerçant.
PCT/US2013/076451 2013-12-19 2013-12-19 Transaction de paiement WO2015094265A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2013/076451 WO2015094265A1 (fr) 2013-12-19 2013-12-19 Transaction de paiement

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2013/076451 WO2015094265A1 (fr) 2013-12-19 2013-12-19 Transaction de paiement

Publications (1)

Publication Number Publication Date
WO2015094265A1 true WO2015094265A1 (fr) 2015-06-25

Family

ID=53403365

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2013/076451 WO2015094265A1 (fr) 2013-12-19 2013-12-19 Transaction de paiement

Country Status (1)

Country Link
WO (1) WO2015094265A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109670958A (zh) * 2018-12-26 2019-04-23 中国银联股份有限公司 一种交易方法及装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20090006831A (ko) * 2006-04-18 2009-01-15 마이크로소프트 코포레이션 온라인 거래 인가 방법, 컴퓨터 시스템, 프로그램, 모바일 모듈 인증 방법, 휴대용 장치, 액세스 방법, 컴퓨팅 프레임워크, 전송 레벨 보안 통신의 설정 방법, 안전 상거래 제공 방법, 안전 상거래 수행 방법, 지불 인가 방법, 지불 인가의 유효성 검사 방법, 자동 지불 배분 방법, 지불 옵션 제시 방법
US20090254440A1 (en) * 2008-04-02 2009-10-08 Pharris Dennis J Ghosting payment account data in a mobile telephone payment transaction system
US20100049615A1 (en) * 2008-01-24 2010-02-25 Qualcomm Incorporated Mobile commerce authentication and authorization system
US20120290415A1 (en) * 2011-05-11 2012-11-15 Riavera Corp. Mobile image payment system
US20120290421A1 (en) * 2011-05-12 2012-11-15 Spenzi, Inc. Enabling a Merchant's Storefront POS (Point of Sale) System to Accept a Payment Transaction Verified by SMS Messaging with Buyer's Mobile Phone
US8583496B2 (en) * 2010-12-29 2013-11-12 Boku, Inc. Systems and methods to process payments via account identifiers and phone numbers

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20090006831A (ko) * 2006-04-18 2009-01-15 마이크로소프트 코포레이션 온라인 거래 인가 방법, 컴퓨터 시스템, 프로그램, 모바일 모듈 인증 방법, 휴대용 장치, 액세스 방법, 컴퓨팅 프레임워크, 전송 레벨 보안 통신의 설정 방법, 안전 상거래 제공 방법, 안전 상거래 수행 방법, 지불 인가 방법, 지불 인가의 유효성 검사 방법, 자동 지불 배분 방법, 지불 옵션 제시 방법
US20100049615A1 (en) * 2008-01-24 2010-02-25 Qualcomm Incorporated Mobile commerce authentication and authorization system
US20090254440A1 (en) * 2008-04-02 2009-10-08 Pharris Dennis J Ghosting payment account data in a mobile telephone payment transaction system
US8583496B2 (en) * 2010-12-29 2013-11-12 Boku, Inc. Systems and methods to process payments via account identifiers and phone numbers
US20120290415A1 (en) * 2011-05-11 2012-11-15 Riavera Corp. Mobile image payment system
US20120290421A1 (en) * 2011-05-12 2012-11-15 Spenzi, Inc. Enabling a Merchant's Storefront POS (Point of Sale) System to Accept a Payment Transaction Verified by SMS Messaging with Buyer's Mobile Phone

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109670958A (zh) * 2018-12-26 2019-04-23 中国银联股份有限公司 一种交易方法及装置

Similar Documents

Publication Publication Date Title
US20250021984A1 (en) Use limitations for secondary users of financial accounts
US10268810B2 (en) Methods, apparatus and systems for securely authenticating a person depending on context
KR102608217B1 (ko) 안전 실시간 결제 거래
US20200019950A1 (en) Systems and methods for transaction pre- authentication
US9852479B2 (en) Mechanism for reputation feedback based on real time interaction
KR102397227B1 (ko) 개인 데이터 공유 앱을 위한 방법 및 시스템
WO2015164022A1 (fr) Fonds à externalisation ouverte à base de localisation
US11386413B2 (en) Device-based transaction authorization
JP2016517983A (ja) 携帯装置融資のためのシステム及び方法
US11908004B2 (en) Method and system for obtaining credit
US20180005210A1 (en) Secure universal two-step payment authorization system
US20140095384A1 (en) Systems and Methods For In Store Shopping With Instant Cash
US11410223B2 (en) Method and system for facilitating e-commerce transactions
US10769631B2 (en) Providing payment credentials securely for telephone order transactions
AU2018203167A1 (en) NFC mobile wallet processing systems and methods
CN105321073A (zh) 一种建立账户间关系的方法、账户管理平台和系统
US9639835B2 (en) Method to enable consumers to make purchases at e-Commerce websites using their mobile number
US20190279196A1 (en) Systems and methods for digitizing payment card accounts
WO2015094265A1 (fr) Transaction de paiement
US12039530B2 (en) System and method for authorizing temporary use of accounts
CA3146619A1 (fr) Systeme et methode d'autorisation de l'utilisation temporaire de comptes
KR20120025022A (ko) 마일리지 포인트를 이용한 모바일 결제 방법 및 그 시스템

Legal Events

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

Ref document number: 13899764

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13899764

Country of ref document: EP

Kind code of ref document: A1

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载