WO2017041153A1 - Transaction credit and payment method in a cloud payment service, and payment terminal - Google Patents
Transaction credit and payment method in a cloud payment service, and payment terminal Download PDFInfo
- Publication number
- WO2017041153A1 WO2017041153A1 PCT/BR2016/050221 BR2016050221W WO2017041153A1 WO 2017041153 A1 WO2017041153 A1 WO 2017041153A1 BR 2016050221 W BR2016050221 W BR 2016050221W WO 2017041153 A1 WO2017041153 A1 WO 2017041153A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- payment
- buyer
- transaction
- merchant
- cloud
- Prior art date
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/08—Payment architectures
- G06Q20/20—Point-of-sale [POS] network 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/22—Payment schemes or models
- G06Q20/28—Pre-payment schemes, e.g. "pay before"
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
-
- 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
Definitions
- the present invention relates to devices and processes for making and paying purchases at a merchant.
- Document WO2014 / 053584 describes a payment process which is called a "cloud payment process" and is capable of paying a user's purchases at a store cashier.
- the user has a mobile terminal that receives a request for confirmation of the transaction being performed at the cashier. You confirm the transaction on your mobile terminal which could be, for example, your mobile phone where an application has been installed.
- the document states that the transaction does not involve any payment terms, and that the user confirms the transaction on his smartphone phone or similar portable device.
- the described process requires the user to have a smartphone or similar and only allows payment to be made at the store itself, after purchases have been posted to the cashier. It is a payment system that simply uses the user's smartphone or the like to make the payment instead of using a payment terminal belonging to the merchant.
- the purpose of the present invention is to improve known processes and devices for performing transactions more flexibly and securely.
- the invention relates to a transaction reservation and payment process in a cloud payment service, which includes the following steps:
- a merchant is registered with the cloud payment service with a merchant identifier; a buyer consolidates a transaction with the merchant by communicating a buyer identifier to the merchant;
- the merchant communicates to the cloud payment service the buyer identifier, merchant identifier, and transaction data that includes the total transaction price;
- the cloud payment service stores a transaction reservation that is linked to the buyer identifier and where transaction data is recorded;
- the buyer identifies himself at a payment terminal with his buyer identifier
- the payment terminal communicates to the cloud payment service a status request along with the buyer identifier and its own payment terminal identifier;
- the cloud payment service communicates to the payment terminal a list of stored transaction reservations that are linked to this buyer identifier;
- the buyer selects the transaction reservation to pay at the payment terminal
- the payment terminal communicates a payment request directly to a payment authorizer
- the payment authorizer communicates to the payment terminal a payment authorization
- the payment authorizer and cloud payment service communicate to register with the cloud payment service that the transaction reservation has been paid.
- Another object of the invention is a payment terminal that includes a module for connecting to a cloud payment service, and further including:
- an input peripheral fit for a buyer to identify with a buyer identifier a display capable of displaying a list of transaction reservations stored in the cloud payment service with this buyer identifier; a means of payment activation module; and
- a direct connection module to a payment authorizer able to pay at least one transaction reservation selected by the buyer.
- the invention allows for transactions between buyers and merchants in a flexible and secure manner.
- the notion of transaction reserve that opens up more payment possibilities for the buyer is introduced.
- the merchant's already known level of mobile terminal payment security is maintained.
- the process according to the invention does not use any buyer apparatus or applications to be installed by the buyer. These devices and applications owned by the buyer do not achieve the degree of security provided by a certified and professional payment terminal such as that owned by the merchant. In this way, the invention allows great flexibility as to the place and time of payment, with maximum security.
- the buyer may identify and obtain the list of transaction reservations linked to his buyer identifier, that is, the list of payment reservations that were previously held by the buyer. The buyer can thus pay and finalize the transaction reserves he selects.
- a buyer can, for example, make a transaction reservation with a merchant and pay elsewhere where a payment terminal is available.
- Buyer may make a transaction reservation at a physical store. Shortly after booking transaction, buyer can pay directly to a payment terminal from this physical store. The buyer can also choose to pay later at this same store with her payment terminal. The buyer may also pay later at another store that has a payment terminal in accordance with the invention.
- the buyer can make a transaction reservation in an online store. Shortly after the transaction reservation, the buyer can pay directly with a payment terminal if he is in a place that has a payment terminal according to the invention. This is the case, for example, if the buyer is in a "cybercafe" place equipped with payment terminals. The buyer may also pay later at another store that has a payment terminal in accordance with the invention.
- a particular advantage of the invention is obtained if the buyer makes a transaction reservation at a physical store and pays directly with that merchant's payment terminal.
- the integration between the merchant's cash-front device and the merchant's payment terminal is simplified as explained below.
- the invention allows the merchant to have an integration between the cash-front device and the payment terminal without requiring them to be compatible with each other. All it takes is for the payment terminal on the one hand and the cash-front device on the other to communicate with each other over the network with the cloud payment service.
- the payment terminal will be able to communicate with the cash-front device via the cloud payment device.
- the payment terminal is thus capable of displaying the price to pay without being physically linked to the merchant's selling devices.
- the merchant vending device connects with the payment terminal through the cloud payment service, without the need for compatible equipment.
- This integration solution provided by the invention results in cost-effective integrated payment terminals and cash-front devices suitable for both medium and large stores, small stores and independent merchants.
- everyone can thus have a cost-effective integration service that is identical from the buyer's point of view to the best integration services that were previously costly.
- the exchange of a defective device, cash front or payment terminal may be performed by any other equipment that is capable of communicating with the cloud payment service. Switching does not require the use of compatible, branded devices, which makes it easier and cheaper to maintain and upgrade equipment.
- Transaction data also includes a description of the products or services involved in transaction consolidation, and the date and time of transaction consolidation.
- the payment terminal is available at a physical store.
- the payment terminal is an electronic device that accepts payment cards.
- the payment terminal is a mobile communication device.
- Activation of the buyer's payment method is accomplished by reading a buyer's payment card and entering a password.
- the physical store where the payment terminal is available is the merchant, that is, the transaction reservation and the payment are made in the same place.
- the physical store where the payment terminal is available is a different store from the merchant, that is, the transaction reservation and payment are made in different places.
- the buyer communicates his buyer identifier to the merchant by typing or by barcode scanning.
- the buyer identifies himself at the payment terminal with his buyer identifier by typing or by barcode scanning.
- the merchant is a physical store.
- the merchant is a web store.
- Transaction consolidation is performed on a merchant's cloud cash-front system.
- the cash-in-the-box system of the cloud is hosted directly by the cloud payment service.
- the process includes the following additional steps, relating to a transaction query by the merchant:
- the merchant communicates to the cloud payment service a transaction request along with his merchant identifier; - The cloud payment service reports back to the merchant a transaction reservation inventory, which is a list of all transaction reservations that are linked to the merchant identifier.
- the process optionally includes a pre-registration step in which the buyer is registered with the cloud payment service with their buyer identifier.
- Figure 1 schematically depicts the integral parts of a cloud payment service according to the invention
- Figure 2 represents a buyer making a transaction reservation with a merchant according to the invention
- Figure 3 represents the buyer of Figure 2 making the payment of the transaction reservation
- Figure 4 represents a trader performing a status inquiry of a transaction reservation in accordance with the invention.
- the invention relates to the conduct of transactions between a buyer and a merchant.
- Figure 1 schematically depicts a buyer 1, a merchant 2, a payment terminal 3, and a cloud payment service 4.
- a buyer 1 has a buyer identifier 9.
- the buyer identifier 9 is a string that uniquely identifies buyer 1.
- Buyer identifier 9 can be a number generated by cloud payment service 4 or an existing number linked to the buyer, such as an individual registration number generated by the government of the country concerned, or the number of Buyer Phone 1.
- Trader 2 is a natural or legal person who is qualified to sell products or services.
- Trader 2 can be, for example, an individual who sells a product or provides a service, a small store, a supermarket (hereinafter referred to as a "physical store").
- Merchant 2 may also be, for example, an e-commerce website or other type of purchasing device via an electronic network (referred to below as the "e-shop").
- merchant 2 signs up for cloud payment service 4 and receives a merchant identifier 10.
- Merchant identifier 10 is a string that uniquely identifies merchant 2. Trader 2 only needs to register once. Once he receives his merchant identifier 10, merchant 2 is able to make all timely transactions with cloud payment service 4.
- Both merchant and buyer can sign up by any usual means, such as on a web site linked to the cloud payment service 4.
- Fig. 1 two examples of payment terminal 3 are illustrated: an electronic device that accepts payment cards 5 and a mobile communication device 6.
- payment terminal 3 is an electronic device that accepts payment cards 5
- this device 5 is capable of connecting to cloud payment service 4, for example via the fixed telephony, cellular telephony, a cable Internet connection or wifi. That is, similar to the type of classic payment terminal available in merchant stores.
- the payment terminal 3 is a mobile communication device 6, such as a smartphone-type mobile phone or a tablet
- this device 6 includes an application capable of connecting to the cloud payment service 4 via 6. This is a new generation of payment terminals best suited to individual or itinerant merchants.
- any type of payment terminal 3 available at merchant 2 may so that it can be connected to cloud payment service 4 and a payment authorizer.
- Each payment terminal 3 is provided with a payment terminal identifier 11 to identify with the cloud payment service 4.
- Cloud Payment Service 4 is thus able to register
- Payment terminal 3 needs no registration and is provided with a payment terminal identifier 11 which enables cloud payment service 4 to recognize payment terminal 3.
- Cloud Payment Service 4 includes at least one server connected to a network enabling secure communication with merchant 2 and payment terminal 3.
- a network may be, for example, a dedicated private network, a telephone network , or a virtual private network going through a public network such as the Internet.
- each merchant 2 may have one or more payment terminals 3.
- Figure 2 schematically depicts a transaction reservation process involving buyer 1, merchant 2, cloud payment service 4 and a payment authorizer 7.
- Payment authorizer 7 consists of servers of a company responsible for the transmission and financial settlement of payment card transactions.
- the function of this type of company, present in the market is to receive payment requests issued by payment terminals 3 and communicate with financial institutions and payment card brands to transmit payment data in order to obtain the payment information. authorization of the transaction. Such authorization allows the respective Banks transfer the transaction amount from buyer bank account 1 to merchant bank account 2, completing the payment transaction.
- buyer 1 consolidates a transaction at merchant 2 by providing his buyer identifier 9.
- Merchant 2 is a physical store
- consolidating a transaction is the action of registering the items or services chosen by Buyer 1 on a Merchant 2 cash-front device. In a supermarket, this is accomplished when the Buyer 1 passes the cashier. In smaller stores or individual merchants, this can be accomplished by manually registering the items or services on the cash front device.
- a typical cloud-front box system includes a physical box-front device that is networked to a box program that is in the cloud, that is, on a remote server. This enables simplification of the physical cashier device and facilitates the maintenance of the cashier program on the remote server. If a cloud cashier system is used, an advantageous option is to host the cashier program directly on the cloud payment service 4.
- merchant 2 is an online store, consolidating a transaction is that buyer 1 will go to the sales completion page after selecting the desired products or services.
- the buyer communicates to the merchant 2 his buyer identifier 9.
- Such communication may be made orally or electronically, for example by entering the buyer identifier 9, or reading with the forward device.
- an ID card or scanning with the device a two-dimensional bar code (“QR code") that may be stored on the buyer's mobile phone 1.
- Trader 2 thus has, on the one hand, buyer identifier 9 and, on the other hand, transaction data 8 which includes at least the total transaction price.
- transaction data 8 may also include, for example, a description of the items or services chosen with their individual identification numbers and prices, consolidation date and time information, or any other information that may be useful for characterizing the transaction buffer.
- the merchant 2 then communicates to the cloud payment service 4 the buyer identifier 9, the merchant identifier 10, and the transaction data 8. This operation is performed by means of a computer or a front-facing device. cashier belonging to merchant 2 and communicating over the network with cloud payment service 4.
- cloud payment service 4 Upon receiving merchant communication 2, cloud payment service 4 stores a transaction reservation 12 which is linked with buyer identifier 9 and merchant identifier 10 and where transaction data 8 is written.
- Transaction reservation 12 is stored in cloud payment service 4 so that buyer 1 has a choice of time to pay. By the time buyer 1 pays, transaction booking 12 will be converted to a finalized transaction.
- Buyer 1 can then choose to pay shortly after transaction reservation 12 has been created, if he has access to a payment terminal 3, or later, at a place where he will have access to a payment terminal 3.
- Figure 3 illustrates the process steps relating to the consultation and payment of transaction reservation 12, which are initiated by buyer 1.
- Buyer may perform the steps described below at any payment terminal 3 supported by the cloud payment service 4.
- Payment terminal 3 may be, for example, made available at any store, ie the store where the buyer 1 made the transaction reservation or at any other store.
- buyer 1 identifies himself at payment terminal 3 by communicating his buyer identifier 9, for example by directly entering buyer identifier 9 on a payment terminal 3 keyboard, or reading with the payment terminal 3 an identification card, or by scanning with payment terminal 3 a two-dimensional bar code ("QR code") which may be stored in the buyer's mobile phone 1.
- QR code two-dimensional bar code
- payment terminal 3 will communicate to cloud payment service 4 a status requirement 13 along with that buyer identifier 9 and its own payment terminal identifier 1 1.
- Cloud payment service 4 upon receiving payment terminal identifier 11, identifies payment terminal 3 as an accepted payment terminal and is thus authorized to receive payment payment information. cloud 4.
- cloud payment service 4 communicates to payment terminal 3 a list of stored transaction reservations 14 that are linked to buyer identifier 9 communicated to it.
- buyer 1 made only a transaction reservation 12 to simplify the description. However, buyer 1 may have made multiple transaction reservations 12 at different stores, whether they are physical stores or virtual stores.
- the list of stored transaction bookings 14 that is communicated by cloud payment service 4 includes all transaction bookings 12 that were previously made by buyer 1 identified by their buyer identifier 9.
- payment terminal 3 Upon receiving this list of stored transaction reservations 14, payment terminal 3 displays on its screen all transaction reservations 12.
- buyer 1 For each transaction reservation 12 of the stored transaction list 14, buyer 1 can display in payment terminal 3 the details available for that transaction reservation.
- Buyer 1 may also choose to cancel one or several transactions at payment terminal 3, but only if he has payment terminal 3 of a physical store in which he has just consolidated the sale, that is, if the buyer 1 is able to return purchases. If a transaction reservation 12 was previously made at an online store or other physical store than the store at which buyer 1 is paying, the payment terminal will not propose the option to cancel the transaction reservation.
- Buyer 1 may also choose to pay one or several selected transaction reservations 12.
- payment terminal 3 will initiate the payment transaction by communicating directly with the payment authorizer 7.
- Payment terminal 3 will ask buyer 1 to activate their payment method and through cloud payment service 4 , will communicate to payment authorizer 7 a payment request 15 that includes the amount payable (the total transaction price selected) and the buyer payment data 1.
- Activation of buyer 1 payment method refers to any payment method that can be used with a payment terminal 3.
- the most common payment method is a payment card, for example, a debit card. or credit, which is read by payment terminal 3 and eventually with password input by buyer 1.
- a payment card may be, for example, a magnetic card or a chip equipped smart card that may function either contact or non-contact.
- any other technology payment card may be used.
- Other common payment systems may also be used as either voucher or digital wallet systems.
- the payment authorizer 7 receives the elements required to make the payment for the selected transaction reservation 12.
- Payment authorizer 7 authorizes payment based on the elements reported by payment terminal 5. Payment authorizer 7 then communicates a payment authorization 16 to payment terminal 3 via cloud payment service 4, the latter showing in sequence to buyer 1 that the payment has been duly authorized.
- Cloud Payment Service 4 performs a status update based on the information obtained from Payment Authorization 16. The status of Transaction Reserve 12 whose payment has been authorized is thus marked. as paid.
- Payment terminal 3 preferably includes:
- a buyer-fit input peripheral 1 identifies with its buyer identifier 9, for example, a keyboard for entering buyer identifier 9 or a scanner for capturing a barcode; a display, also called a "display", capable of displaying the list of transaction bookings 14 stored in cloud payment service 4 for a given buyer identifier 9;
- a means of payment activation module for example, a payment card reader and a keypad for entering the password
- a direct connection module to a payment authorizer 7 able to pay one or more transaction reservations 12 selected by the buyer 1.
- Figure 4 illustrates a complementary process in which trader 2 performs a transaction query. According to this process, merchant 2 communicates to cloud payment service 4 a transaction request 18 along with its merchant identifier 10.
- This transaction reservation inventory 19 is a list of all transaction reservations that are linked to merchant identifier 10, that is, all transaction bookings that were made with this merchant.
- Transaction booking inventory 19 includes the status of each transaction booking, for example "awaiting payment”, “paid”, “canceled”, etc.
- Transaction reserve inventory 19 is beneficial for trader 2. This data can be used for various functions of trader 2's company or its suppliers, such as inventory management, accounting, establishment of sales, and administrative appraisals that assist retailers in running their business.
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- General Physics & Mathematics (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Finance (AREA)
- Computer Networks & Wireless Communication (AREA)
- Microelectronics & Electronic Packaging (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Cash Registers Or Receiving Machines (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
Description
Claims
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
BR112018004889A BR112018004889A2 (en) | 2015-09-10 | 2016-09-06 | transaction booking and payment process at a cloud payment service and payment terminal |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
BRBR102015022482-6 | 2015-09-10 | ||
BR102015022482-6A BR102015022482A2 (en) | 2015-09-10 | 2015-09-10 | consumer reservation and payment process in a cloud payment service, and payment terminal |
BRBR102015022691-8 | 2015-09-11 | ||
BR102015022691A BR102015022691A2 (en) | 2015-09-11 | 2015-09-11 | transaction booking and payment process at a cloud payment service and payment terminal |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017041153A1 true WO2017041153A1 (en) | 2017-03-16 |
Family
ID=58240445
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/BR2016/050222 WO2017041154A1 (en) | 2015-09-10 | 2016-09-06 | Consumer credit and payment method in a cloud payment service, and payment terminal |
PCT/BR2016/050221 WO2017041153A1 (en) | 2015-09-10 | 2016-09-06 | Transaction credit and payment method in a cloud payment service, and payment terminal |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/BR2016/050222 WO2017041154A1 (en) | 2015-09-10 | 2016-09-06 | Consumer credit and payment method in a cloud payment service, and payment terminal |
Country Status (2)
Country | Link |
---|---|
BR (1) | BR112018004889A2 (en) |
WO (2) | WO2017041154A1 (en) |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050234820A1 (en) * | 2004-04-16 | 2005-10-20 | Mackouse Jack | System and method for bill pay with credit card funding |
US8615439B2 (en) * | 2012-04-16 | 2013-12-24 | Wal-Mart Stores, Inc. | Processing online transactions |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6999569B2 (en) * | 1998-10-28 | 2006-02-14 | Mastercard International Incorporated | System and method for using a prepaid card |
US7204412B2 (en) * | 2003-10-14 | 2007-04-17 | Compucredit Intellectual Property Holdings Corp. Iii | Family stored value card program |
-
2016
- 2016-09-06 BR BR112018004889A patent/BR112018004889A2/en not_active Application Discontinuation
- 2016-09-06 WO PCT/BR2016/050222 patent/WO2017041154A1/en active Application Filing
- 2016-09-06 WO PCT/BR2016/050221 patent/WO2017041153A1/en active Application Filing
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050234820A1 (en) * | 2004-04-16 | 2005-10-20 | Mackouse Jack | System and method for bill pay with credit card funding |
US8615439B2 (en) * | 2012-04-16 | 2013-12-24 | Wal-Mart Stores, Inc. | Processing online transactions |
Non-Patent Citations (1)
Title |
---|
LEITE, P.: "DDA tem mais de 3 milhões de cadastros, mas ainda'sofre' com falta de boletos", Retrieved from the Internet <URL:http://gl.globo.com/Noticias/Economia_Negocios/0..MUL1554326-9356,00-DDA+TEM+MAIS+DE+MILHOES+DE+CADASTROS+MAS+AINDA+SOFRE+COM+FALTA+DE+BOLETOS.html> * |
Also Published As
Publication number | Publication date |
---|---|
WO2017041154A1 (en) | 2017-03-16 |
BR112018004889A2 (en) | 2018-10-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10671996B2 (en) | Systems and methods for providing pre-paid multicards | |
US8108977B1 (en) | Machine, methods, and program product for electronic order entry | |
JP6158843B2 (en) | Mobile payment method and system therefor | |
US20130262309A1 (en) | Method and System for Secure Mobile Payment | |
US20150058145A1 (en) | Universal check-out system for Mobile Payment Applications/Platforms | |
US20120290480A1 (en) | Electronic payment using transaction identity codes | |
CN105593883A (en) | Method for authenticating transactions | |
US20180357636A1 (en) | Point of sale terminal for accepting payment through multiple digital payment techniques | |
JP6502244B2 (en) | Payment system | |
US10387886B2 (en) | Secure transaction processing in a communication system | |
US20240029038A1 (en) | Method and system for digital account management | |
WO2014117122A1 (en) | Retail gift card system with integrated account and sales receipt tracking | |
CN104704520B (en) | Method of payment based on cloud | |
TWM575572U (en) | Cloud payment device | |
JP2019175358A (en) | Non-face-to-face product hand-over system, and non-face-to-face product hand-over method | |
US20140032372A1 (en) | Transaction system and method | |
KR20170099340A (en) | System and method for processing buying and payment of on and off line | |
JP2019114288A (en) | Settlement system | |
US20160098706A1 (en) | Method and apparatus for conducting fund transfer between two entities and its application as a cell phone wallet | |
WO2017041153A1 (en) | Transaction credit and payment method in a cloud payment service, and payment terminal | |
EP2575096A1 (en) | Transaction | |
BR102015022691A2 (en) | transaction booking and payment process at a cloud payment service and payment terminal | |
Damodhar et al. | E-Commerce in India: E-Payment methods, trends and challenges | |
RU103207U1 (en) | CASHLESS PAYMENT SYSTEM USING MOBILE COMMUNICATION DEVICES | |
JP2010044474A (en) | System, method and program for mediating settlement in physical distribution , and communication terminal cooperating with the system |
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: 16843311 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112018004889 Country of ref document: BR |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 16843311 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 112018004889 Country of ref document: BR Kind code of ref document: A2 Effective date: 20180312 |