Method and apparatus for detecting merchants from payment transactions

Abstract

Aspects relate to a method for detecting a merchant from a payment transaction between a payer and a payee, the method includes receiving, by a payment server of a payment service, from a payer device of a payer, one or more tags of one or more objects in a payment transaction environment in one or more images captured as part of a payment transaction, in one embodiment, payee transaction data for one or more payment transactions of a payee is obtained by a payment server, and a payee location for the one or more payment transactions of the payee is received by the payment server. The method also includes determining, by the payment server, whether the payee is a merchant based on the received one or more tags, the acquired payee transaction data, and the received payee location.

Description

Technical Field

[0001] Various aspects of the present disclosure relate to methods and apparatus for detecting a merchant from a payment transaction between a payer and a payee. Background Art

[0002] A merchant opening a new business may fraudulently masquerade as a regular (non-merchant) user and may accept peer-to-peer (P2P) payments via a Quick Response (QR) code associated with his or her personal account. The merchant may do this to avoid fees and commissions incurred by joining the payment service's merchant platform and / or to skip the time-consuming "know your customer" process that may delay his or her new business. Moreover, the merchant may be trying to gauge interest before signing up for a full merchant account. In addition, P2P payments via QR codes may be a convenient payment method for merchants, unlike payments via credit or debit cards, which may require a point-of-sale machine and associated onboarding activities with the merchant's acquirer.

[0003] Existing solutions to the above problems may rely on location to detect merchants that fraudulently accept P2P payments. However, the location of mobile merchants (e.g., merchants operating pop-up stores or food trucks) may not correspond to any known commercial location that may be associated with the base of business operations, because the location of mobile merchants may be constantly changing, bypassing automatic checks that rely on fixed locations. Therefore, solutions based solely on location may not be effective in detecting fraudulent merchants masquerading as ordinary users. Summary of the invention

[0004] Various embodiments relate to a method for detecting a merchant from a payment transaction between a payer and a payee, the method comprising receiving, by a payment server of a payment service, one or more tags of one or more objects in a payment transaction environment in one or more images captured as part of a payment transaction from a payee device of the payee, the one or more images being captured as part of a payment transaction, obtaining, by the payment server, payee transaction data for one or more payment transactions of the payee, and receiving, by the payment server, a payee location for the one or more payment transactions of the payee. The method also includes determining, by the payment server, whether the payee is a merchant based on the received one or more tags, the obtained payee transaction data, and the received payee location, and sending, by the payment server, payment service information to the payee device of the payee based on the determination that the payee is a merchant, the payment service information being used for the payee to register and / or use the payment service as a merchant.

[0005] The method may also include receiving, by the payment server from the payee device, a payee input indicating whether the payee is a merchant.

[0006] Determining whether the payee is a merchant may include determining, by the payment server, whether the payee is a merchant further based on a received payee input indicating whether the payee is a merchant.

[0007] Payee transaction data may include the amount, frequency, and value of each of one or more transactions of the payee.

[0008] Determining whether the payee is a merchant may include: determining, by the payment server, that the payee is a merchant based on a quantity associated with the merchant in the received one or more tags being greater than or equal to a predetermined quantity.

[0009] Determining whether the payee is a merchant may include: determining, by the payment server, that the payee is not a merchant based on that the acquired transaction data of the payee is heterogeneous.

[0010] Determining whether the payee is a merchant may include: determining, by the payment server, that the payee is a merchant based on the fact that the payee location of one or more transactions received from the payee is the same.

[0011] The method may also include determining, by the payment server, a merchant category of the payee determined to be the merchant based on the received one or more tags, the acquired payee transaction data, and the received payee location.

[0012] The payment service information may include instructions and one or more incentives for the payee to register and / or use the payment service as a merchant.

[0013] The one or more incentives may include an offer to promote the merchant on the payment service and an offer to provide discounts to consumers of the merchant on the payment service in exchange for the payee registering and / or using the payment service as a merchant and accepting favorable commission terms for the payment service.

[0014] The method may also include: receiving, by the payer device, a payer input for initiating a payment transaction, capturing, by the payer device, an image including a payment transaction environment based on receiving the payer input for initiating the payment transaction, and generating, by the payer device, one or more tags of one or more objects in the payment transaction environment in the captured image. The method may also include sending, by the payer device, the generated tags to a payment server.

[0015] The method may further include: outputting, by the payer device, a question asking whether the payee is a merchant based on receiving the payer input for initiating the payment transaction.

[0016] The method may also include receiving, by the payee device, a payee input in response to the output question indicating whether the payee is a merchant.

[0017] The method may also include sending, by the payee device, to the payment server a payee input indicating whether the payee is a merchant.

[0018] The image may be captured when scanning a QR code in a payment transaction environment, and the image may include the QR code.

[0019] The method may also include removing, by the payer device, disabled tags from the generated tags that are not sent to the payment server.

[0020] Sending the generated tag may include sending, by the payer device, to the payment server the generated tag from which the disabled tag has been removed.

[0021] The server may be configured to perform the method.

[0022] The computer program element may comprise program instructions which, when executed by one or more processors, cause the one or more processors to perform the method.

[0023] The computer readable medium may include program instructions that, when executed by one or more processors, cause the one or more processors to perform the method. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The invention will be better understood with reference to the detailed description when considered in conjunction with the non-limiting examples and accompanying drawings, in which:

[0025] Figure 1 A schematic diagram of a system for detecting a merchant from a payment transaction between a payer and a payee according to an embodiment is shown;

[0026] Figure 2 Shows Figure 1 A block diagram of a payer device in a system;

[0027] Figure 3 Shows Figure 1 A block diagram of a payment server in a system;

[0028] Figure 4 A flow chart showing a method for detecting a merchant from a payment transaction between a payer and a payee according to an embodiment, the method being performed by a payer device; and

[0029] Figure 5 A flow chart of a method for detecting a merchant from a payment transaction between a payer and a payee according to an embodiment is shown, the method being executed by a payment server. DETAILED DESCRIPTION

[0030] The following detailed description refers to the accompanying drawings, which show, by way of illustration, specific details and embodiments in which the present disclosure may be practiced. The description of these embodiments is sufficiently detailed to enable those skilled in the art to practice the present disclosure. Other embodiments may be utilized, and structural and logical changes may be made without departing from the scope of the present disclosure. The various embodiments are not necessarily mutually exclusive, as some embodiments may be combined with one or more other embodiments to form new embodiments.

[0031] Embodiments described in the context of one of the devices or methods are equally valid for the other device or method. Similarly, embodiments described in the context of a device are equally valid for a vehicle or method, and vice versa.

[0032] Features described in the context of an embodiment may be correspondingly applicable to the same or similar features in other embodiments. Features described in the context of an embodiment may be correspondingly applicable to other embodiments, even if not explicitly described in these other embodiments. Furthermore, additions and / or combinations and / or substitutions of features described in the context of an embodiment may be correspondingly applicable to the same or similar features in other embodiments.

[0033] In the context of various embodiments, the articles “a,” “an,” and “the” used with respect to features or elements include reference to one or more features or elements.

[0034] As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0035] Hereinafter, embodiments will be described in detail.

[0036] Figure 1 A schematic diagram of a system 100 for detecting a merchant from a payment transaction between a payer and a payee according to an embodiment is shown.

[0037] Reference Figure 1 The system 100 includes a payer device 105 of a payee, a payee device 110 of a payee, a network 115, a payment source 120, and a payment server 125 that provides payment services.

[0038] Each of the payer device 105 and the payee device 110 may include, for example, a smartphone and / or a personal computer. Each of the payment source 120 and the payment server 125 may include a server computer or a group of server computers. The payer device 105, the payee device 110, the payment source 120 and the payment server 125 are connected by a network 115 (usually the Internet), which may be implemented by the arrangement of a communication network, such as a wireless access network, a backhaul network, a backbone network, etc.

[0039] The payee device 105 may contact the payee device 110 to conduct a payment transaction between the payee and the payee for goods or services provided by the payee. For convenience, the payee device 105 and the payee device 110 may use a digital payment service (rather than, for example, performing a cash transfer via the payee's bank), so the payee device 105 sends a request to the payment server 125 to perform the payment transaction, such as performing the payment transaction via a payment application installed in the payee device 105 and hosted by the payment server 125.

[0040] However, the payment transaction may be a P2P payment transaction between two ordinary users, rather than a payment transaction between a consumer and a merchant (e.g., an operator or store owner of a retail business) using a merchant platform of a payment service. As described above, the payee may be a merchant who fraudulently requests a P2P payment transaction, for example, to avoid fees and commissions incurred by joining the merchant platform of the payment service.

[0041] In order to combat merchant fraud, in a P2P payment transaction, the payer is required to use the camera of the payer device 105 to capture an image 106 of the payee's QR code 107, which may include one or more objects in the payment transaction environment, such as a store logo 108. The payer device 105 then uses the captured image 106 of the QR code 107 to generate a request and send it to the payment server 125 to perform the payment transaction between the payer and the payee. In some embodiments, the image 106 may include multiple images that can be arranged in sequence, or a video data file containing multiple image frames.

[0042] The payment server 125 then contacts the payment source 120 (e.g., a bank where the payee has an account) to settle the payment transaction (e.g., to transfer money from the payee's account to the payee's account, which the payee may have at some bank or through a digital payment service). Ideally, the payment transaction can be successfully settled, and in response, the payment server 125 notifies the payee that the payment transaction has been settled. The payee can then typically provide or deliver the goods or provide the service. Payment for services or goods (e.g., a taxi ride or pizza delivery) can also be settled after the service or goods are provided.

[0043] Embodiments described herein include a payment service detecting whether a payee of a P2P payment transaction is a merchant that is not registered on and / or using the merchant platform of the payment service, thereby enabling the payment service to include such merchant before competitors. The detection is performed based on a combination of the payee's location, transaction data and / or payee's usage patterns, and object detection via the payee's payee device 105.

[0044] Object detection may be performed via the payee device 105 before and after the payee captures an image 106 of the payee's QR code 107 using a camera of the payee device 105. In detail, object detection generates labels of objects (e.g., items for sale and store signs 108) in the scene or environment around the QR code 107 and included in the captured image 106. If these labels are always the same (e.g., if "food" is generated for all transactions for the payee), the payee is likely a street food vendor.

[0045] Advantageously, combining object detection with parameters such as the location and usage patterns of the payee can make the embodiments described herein more robust and accurate than existing solutions while avoiding the collection of personal information captured by the camera. That is, the privacy of personal information can be maintained because only the generated tags are sent to the payment service, not the captured image 106.

[0046] Furthermore, by identifying merchants, payment services may gain the following competitive advantages. For example, a payment service may be able to identify emerging merchants and onboard them to the payment service's platform before competitors do. In another example, a payment service may be able to negotiate favorable commission terms with merchants in exchange for promoting the merchant and attracting consumers to it through offers and discounts.

[0047] Figure 2 Shows Figure 1 Block diagram of a payer device 105 in the system 100.

[0048] Reference Figure 2 The payer device 105 includes a user interface 205 , a processor 210 , a sensor 215 , a memory 220 , a communication interface 225 , and an object detector 230 .

[0049] The user interface 205 may include, for example, a touch screen of a smartphone, and / or a display, mouse, and keyboard of a personal computer. The user interface 205 may receive a payer input from a payer for executing a payment application.

[0050] The processor 210 may include one or more of a central processing unit (CPU), a graphics processor unit (GPU), an accelerated processing unit (APU), a multi-integrated core (MIC), a field programmable gate array (FPGA), and / or a digital signal processor (DSP). The processor 210 may be a general controller that performs control of any one component or any other combination of components of the payer device 105, and / or performs communication-related operations or data processing. The processor 210 may execute one or more programs stored in the memory 220.

[0051] The memory 220 may include volatile and / or non-volatile memory. The memory 220 stores information, such as one or more of commands, data, programs (one or more instructions), applications, etc., which are related to at least one other component of the payer device 105 and are used to drive and control the payer device 105. For example, the commands and / or data may constitute an operating system (OS). The information stored in the memory 220 may be executed by the processor 210. The memory 220 may also store information executed by the processor 210 to perform operations related to the payer device 105. Figure 1 , Figure 2 and Figure 4 Describes the functionality and operation.

[0052] Based on receiving the payer input for executing the payment application from the user interface 205, the processor 210 can obtain the payment application data of the payment application from the memory 220, and can execute the payment application based on the obtained payment application data. The user interface 205 receives the payer input for initiating a payment transaction between the payer and the payee from the payer, which can be input into the executed payment application.

[0053] Sensor 215 may include, for example, a camera configured to capture images, a microphone configured to record ambient sounds, and / or any other sensor configured to sense one or more characteristics of the environment of payer device 105 .

[0054] Based on receiving the payee input for initiating a payment transaction from the user interface 205, the processor 210 controls the sensor 215 to capture the image 106 of the QR code 107 and / or the payment transaction environment around the QR code 107, such as Figure 1 The payment transaction environment may include one or more objects, such as Figure 1 In an embodiment, the image 106 may be captured before or after the QR code 107 is captured, and thus, the image 106 may only include the payment transaction environment. In addition, consumers may be reluctant to take photos of the QR code and / or the payment transaction environment, but they may be motivated to do so via reward points.

[0055] In an embodiment, based on receiving payer input from user interface 205 for initiating a payment transaction, processor 210 may control sensor 215 to record ambient sounds and / or sense one or more characteristics of the payment transaction environment.

[0056] Based on receiving the captured image 106 (the recorded ambient sounds and / or the sensed features) from the sensor 215, the object detector 230 generates a label of the object in the payment transaction environment. The label may include a word describing the object. For example, the word "food" may describe the store sign 108. The object detector 230 may include and / or use at least one of various image recognition software and / or neural networks, such as a fast region-based convolutional neural network (R-CNN) and a faster R-CNN.

[0057] Based on the payee input for initiating the payment transaction received from the user interface 205, the processor 210 may also control the user interface 205 to output a question to the payee asking whether the payee is a merchant (or whether the payment transaction is for goods or services). The question may be output as text displayed on a display and / or a touch screen, for example. The user interface 205 may then receive a payee input from the payee in response to the output question, the input indicating whether the payee is a merchant (or whether the payment transaction is for goods or services). The payee input may be input as text typed into a text box displayed on the display and / or the touch screen, for example.

[0058] The communication interface 225 can be used as a hardware and / or software interface that can, for example, transmit commands and / or data between the payer device 105 and / or external devices and other components of the payer device 105. The communication interface 225 can also be used to communicate between the payer device 105 and external devices (such as Figure 1 The communication interface 225 can communicate with the payment server 125 through a wireless or wired communication architecture. Figure 1 The communication interface 225 may be connected to the network 115 to communicate with external devices. The communication interface 225 may be a wired or wireless transceiver or any other component for sending and receiving signals.

[0059] The communication interface 225 may receive the generated tags from the object detector 230, and may receive a payee input indicating whether the payee is a merchant from the user interface 205 and / or the processor 210. The processor 210 may control the communication interface 225 to send the received tags and / or the payee input indicating whether the payee is a merchant to the payment server 125. The communication interface 225 and / or the processor 210 may maintain a list of disabled tags (e.g., names of family members or friends) that are not sent to the payment server 125, thereby ensuring stricter privacy protection. The communication interface 225 and / or the processor 210 may remove the disabled tags from the received tags, and then send the received tags from which the disabled tags have been removed to the payment server 125.

[0060] Figure 3 Shows Figure 1 1. Block diagram of payment server 125 in system 100.

[0061] Reference Figure 3 The payment server 125 includes a payer interface 305 , a processor 310 , a payment source interface 315 , a memory 320 , a payee interface 325 and a location service interface 330 .

[0062] Each of the payer interface 305, the payment source interface 315, the payee interface 325, and the location service interface 330 can be used as a hardware and / or software interface, for example, which can transmit commands and / or data between the payment server 125 and / or external devices and other components of the payment server 125. Each of the interfaces 305, 315, 325, and 330 can also be used between the payment server 125 and the external device (e.g. Figure 1 Each of the interfaces 305, 315, 325 and 330 can communicate with the payer device 105 via a wireless or wired communication architecture. Figure 1 The interfaces 305, 315, 325, and 330 may each be a wired or wireless transceiver or any other component for sending and receiving signals.

[0063] The payee interface 305 may receive a tag and / or payee input from the payee device 105 indicating whether the payee is a merchant.

[0064] The processor 310 may include one or more of a CPU, a GPU, an APU, a MIC, an FPGA, and / or a DSP. The processor 310 may be a general controller that performs control of any one component or any other combination of components of the payment server 125, and / or performs communication-related operations or data processing. The processor 310 may execute one or more programs stored in the memory 320.

[0065] The processor 310 controls the payment source interface 315 to send payment transaction information for settling the payment transaction to the payment source 120. The payment transaction information may include payer information, payee information, and information about goods or services provided by the payee to the payer.

[0066] The memory 320 may include volatile and / or non-volatile memory. The memory 320 stores information, such as one or more of commands, data, programs (one or more instructions), applications, etc., which are related to at least one other component in the payment server 125 and are used to drive and control the payment server 125. For example, the commands and / or data may constitute an OS. The information stored in the memory 320 may be executed by the processor 310. The memory 320 may also store information executed by the processor 310 to perform operations related to the payment server 125. Figure 1 , Figure 3 and Figure 5 Describes the functionality and operation.

[0067] Processor 310 may retrieve transaction data and / or usage patterns of the payee from memory 320. The transaction data and / or usage patterns may include transaction volume, transaction frequency, and / or value for each transaction performed by the payee.

[0068] The location service interface 330 may receive the payee location from, for example, a global positioning system (GPS) and / or a location-based service.The payee location may be received for each transaction performed by the payee.

[0069] The processor 310 may determine whether the payee is a merchant that is not registered on the merchant platform of the payment service and / or does not use the platform based on the received tag, the received payee input indicating whether the payee is a merchant, the obtained payee transaction data for each payee transaction, and / or the received payee location for each payee transaction. The memory 320 may include a machine learning model and / or a neural network, and the processor 310 may input the above parameters into it to output whether the payee is a merchant.

[0070] For example, if the number of received merchant-related tags (e.g., "food," "store," "clothing") is greater than or equal to a predetermined number, the processor 310 may determine that the payee is a merchant. In another example, if the received payee input indicates that the payee is a merchant, the processor 310 may determine that the payee is a merchant. In yet another example, if the payee transaction data obtained for each payee transaction is heterogeneous (e.g., different or changing), the processor 310 may determine that the payee is not a merchant. In yet another example, if the payee location for each payee transaction is the same, the processor 310 may determine that the payee is a merchant, such as a fixed stall.

[0071] In addition, the processor 310 may determine a merchant category of the payee determined to be the merchant based on the received tag, the received payee input indicating whether the payee is a merchant, the acquired payee transaction data for each payee transaction, and / or the received payee location for each payee transaction. The merchant category may include a merchant category code (MCC): "food" indicates a food merchant, "apparel / textiles" indicates an apparel merchant, and so on.

[0072] Based on the payee being determined to be a merchant, the processor 310 controls the payee interface 325 to send information about the payment service to the payee device 110. The payment service information may include instructions for the payee to register and / or use the payment service as a merchant. In addition, the payment service information may include one or more incentives for the payee to register and / or use the payment service as a merchant. These incentives may include offers to promote merchants on the merchant platform, and / or may include offers to provide discounts to consumers of merchants on the merchant platform in exchange for the payee registering and / or using the payment service as a merchant and accepting favorable commission terms for the payment service.

[0073] Figure 4 A flowchart of a method 400 for detecting a merchant from a payment transaction between a payer and a payee according to an embodiment is shown, wherein the method 400 is performed by a payer device (e.g., Figure 2 The payee device 105) is executed.

[0074] Reference Figure 4 At operation 405 , method 400 includes receiving, by a payer device, a payer input for initiating a payment transaction.

[0075] In operation 410, method 400 includes capturing, by a payer device, an image including a payment transaction environment based on a received payer input for initiating a payment transaction. The image may be captured when scanning a QR code in the payment transaction environment, and the image may include the QR code.

[0076] At operation 415 , method 400 includes generating, by the payer device, one or more labels of one or more objects in the payment transaction environment in the captured image.

[0077] At operation 420 , method 400 includes outputting, by a payer device, a question asking whether a payee is a merchant based on the received payer input for initiating a payment transaction.

[0078] At operation 425 , method 400 includes receiving, by the payee device, a payee input in response to the output question indicating whether the payee is a merchant.

[0079] In operation 430, method 400 includes sending, by the payer device, the generated tag to the payment server. Method 400 may also include sending, by the payer device, a payer input indicating whether the payee is a merchant to the payment server.

[0080] The method 400 may further include removing, by the payer device, a disabled tag from the generated tag, the disabled tag not being sent to the payment server. Sending the generated tag may include sending, by the payer device, the generated tag with the disabled tag removed to the payment server.

[0081] Figure 5 A flowchart of a method 500 for detecting a merchant from a payment transaction between a payer and a payee according to an embodiment is shown, wherein the method 500 is performed by a payment server (eg, Figure 3 The payment server 125) is executed.

[0082] Reference Figure 5 In operation 505, method 500 includes receiving, by a payment server of a payment service, one or more labels of one or more objects in a payment transaction environment in an image captured as part of a payment transaction from a payee device of a payee. Method 500 may also include receiving, by the payment server, from the payee device, a payee input indicating whether the payee is a merchant. In some embodiments, the image may be captured before or during the payment transaction.

[0083] In operation 510, method 500 includes obtaining, by a payment server, payee transaction data for one or more payment transactions of a payee. The payee transaction data may include the amount, frequency, and value of each of the one or more transactions of the payee.

[0084] At operation 515 , method 500 includes receiving, by the payment server, a payee location for one or more payment transactions of a payee.

[0085] In operation 520, method 500 includes determining, by the payment server, whether the payee is a merchant based on the received one or more tags, the obtained payee transaction data, and the received payee location. Determining whether the payee is a merchant may include: determining, by the payment server, whether the payee is a merchant based on the received payer input indicating whether the payee is a merchant. Based on the payee being determined to be a merchant, method 500 proceeds to operation 525. Otherwise, method 500 ends.

[0086] Determining whether the payee is a merchant may include: determining, by the payment server, that the payee is a merchant based on the number of one or more tags related to the merchant received being greater than or equal to a predetermined number. Determining whether the payee is a merchant may include: determining, by the payment server, that the payee is not a merchant based on the fact that the acquired payee transaction data is heterogeneous. Determining whether the payee is a merchant may include: determining, by the payment server, that the payee is a merchant based on the fact that the payee location of one or more transactions received from the payee is the same.

[0087] In operation 525, method 500 includes: based on the payee being determined as a merchant, sending payment service information to a payee device of the payee for the payee to register and / or use the payment service as a merchant. The payment service information may include instructions and one or more incentives for the payee to register and / or use the payment service as a merchant. The one or more incentives may include an offer to promote the merchant on the payment service and an offer to provide discounts to consumers of the merchant on the payment service in exchange for the payee registering and / or using the payment service as a merchant and accepting favorable commission terms for the payment service.

[0088] The method 500 may also include determining, by the payment server, a merchant category of the payee determined to be the merchant based on the received one or more tags, the acquired payee transaction data, and the received payee location.

[0089] The methods described herein may be performed by one or more circuits, and the various processing or computing units and devices and computing entities described herein may be implemented. In one embodiment, a "circuit" may be understood as any type of logic implementation entity, which may be hardware, software, firmware, or any combination thereof. Thus, in one embodiment, a "circuit" may be a hardwired logic circuit or a programmable logic circuit, such as a programmable processor (e.g., a microprocessor). A "circuit" may also be software implemented or executed by a processor, such as any kind of computer program (e.g., a computer program using virtual machine code). Any other kind of implementation of the corresponding functions described herein may also be understood as a "circuit" according to an alternative embodiment.

[0090] Although the present disclosure has been specifically shown and described with reference to specific embodiments, it will be understood by those skilled in the art that various changes may be made in form and detail without departing from the spirit and scope of the present invention as defined in the appended claims. Therefore, the scope of the present invention is indicated by the appended claims, and therefore, all changes within the meaning and scope of the equivalents of the claims are intended to be accepted.

Claims

1. A method for detecting a merchant from a payment transaction between a payer and a payee, the method comprising: receiving, by a payment server of the payment service from a payer device of the payer, one or more labels of one or more objects in a payment transaction environment in one or more images, the one or more images being captured as part of the payment transaction; The payment server obtains payee transaction data of one or more payment transactions of the payee; receiving, by the payment server, a payee location of the one or more payment transactions of the payee; The payment server determines whether the payee is a merchant based on the received one or more tags, the acquired payee transaction data, and the received payee location; as well as The payment server sends payment service information to a payee device of the payee based on the payee being determined as the merchant, where the payment service information is used for the payee to register and / or use the payment service as the merchant.

2. The method according to claim 1, further comprising: A payee input is received by the payment server from the payee device indicating whether the payee is a merchant.

3. The method according to claim 2, wherein: The determining whether the payee is a merchant includes: the payment server further determining whether the payee is a merchant based on the received payee input indicating whether the payee is a merchant.

4. The method according to any one of claims 1 to 3, wherein: The payee transaction data includes the amount, frequency and value of each of one or more transactions of the payee.

5. The method according to any one of claims 1 to 4, wherein: The determining whether the payee is a merchant includes: the payment server determining that the payee is a merchant based on the fact that the amount associated with the merchant in the received one or more tags is greater than or equal to a predetermined amount.

6. The method according to any one of claims 1 to 5, wherein: The determining whether the payee is a merchant includes: the payment server determining that the payee is not a merchant based on that the acquired payee transaction data is heterogeneous.

7. The method according to any one of claims 1 to 6, wherein: The determining whether the payee is a merchant includes: the payment server determining that the payee is a merchant based on the fact that the payee location of one or more transactions received from the payee is the same.

8. The method according to any one of claims 1 to 7, further comprising: A merchant category of the payee determined to be the merchant is determined by the payment server based on the received one or more tags, the acquired payee transaction data, and the received payee location.

9. The method according to any one of claims 1 to 8, wherein: The payment service information includes instructions and one or more incentives for the payee to register and / or use the payment service as the merchant.

10. The method according to claim 9, wherein: The one or more incentives include an offer to promote the merchant on the payment service and an offer to provide discounts to consumers of the merchant on the payment service in exchange for the payee registering and / or using the payment service as the merchant and accepting favorable commission terms for the payment service.

11. The method according to any one of claims 1 and claims 4 to 10, further comprising: receiving, by the payer device, a payer input for initiating the payment transaction; capturing, by the payer device, the image including the payment transaction environment based on receiving the payer input for initiating the payment transaction; generating, by the payer device, one or more of the labels of the one or more objects in the payment transaction environment in the captured image; as well as The generated tag is sent by the payer device to the payment server.

12. The method according to claim 11, further comprising: A question asking whether the payee is a merchant is output by the payee device based on receiving the payee input for initiating the payment transaction.

13. The method according to claim 12, further comprising: A payee input is received by the payee device in response to the outputted question indicating whether the payee is a merchant.

14. The method according to claim 13, further comprising: The payer input indicating whether the payee is a merchant is sent by the payer device to the payment server.

15. The method according to any one of claims 11 to 14, wherein: The image is captured when scanning a Quick Response (QR) code in the payment transaction environment, and the image includes the QR code.

16. The method according to any one of claims 11 to 15, further comprising: Disabled tags that are not sent to the payment server are removed from the generated tags by the payer device.

17. The method according to claim 16, wherein: Sending the generated tag includes: sending, by the payer device, the generated tag from which the disabled tag has been removed to the payment server.

18. A server configured to execute the method according to any one of claims 1 to 17.

19. A computer program element comprising program instructions which, when executed by one or more processors, cause the one or more processors to perform the method of any one of claims 1 to 17.

20. A computer readable medium comprising program instructions, which, when executed by one or more processors, cause the one or more processors to perform the method of any one of claims 1 to 17.

Images