JP2021196844A - Settlement processing method and settlement processing apparatus - Google Patents

Abstract

To provide a settlement processing method for identifying a service provider which has provided a service to a user, and a settlement processing apparatus.SOLUTION: A settlement processing apparatus 1 includes: an issuance request receiving unit 132 which receives a user ID and a request to issue a settlement code for settling payment for purchase of a user who purchases a commodity or a service, from a user terminal; a token transmission unit 133 which transmits, on receipt of the request to issue a settlement code, a settlement token for generating a settlement code to the user terminal; a settlement information receiving unit 134 which receives a provider ID identifying a provider, settlement information on the purchase of the commodity or the service purchased by the user, and the settlement token, from a provider terminal used by the provider which has provided the commodity or the service to the user and has read a settlement code displayed on the user terminal on the basis of the settlement token; and a settlement processing unit 135 which executes the settlement on the basis of the settlement information received from the provider terminal.SELECTED DRAWING: Figure 2

Description

The present invention relates to a payment processing method and a payment processing device.

Conventionally, a method of making a payment using a two-dimensional bar code has been known. For example, in Patent Document 1, when a user's terminal reads a static two-dimensional bar code to pay a price, a seller identification code, an amount to be paid by the user, and a service provider such as a waiter are identified. A method of making a payment by displaying a page including an input field in which a provider identification code can be entered and accepting an amount input from a user is disclosed. In the method disclosed in Patent Document 1, the user can add a service charge as a tip to the service provider to the payment amount or change the amount of the service charge included in the payment amount.

International Publication No. 2013/068665

By the way, in Patent Document 1, there is a possibility that the user erroneously inputs the service provider code that provided the service, or the payment process is performed without inputting any service provider code. This causes a problem that the service charge cannot be given to an appropriate service provider and a problem that it is unclear which service provider provided the service to whom.

Therefore, the present invention has been made in view of these points, and an object of the present invention is to provide a payment processing method and a payment processing device capable of identifying a service provider who has provided a service to a user.

In the payment processing method according to the first aspect of the present invention, the user identification information for identifying the user and the purchase of the product or service by the user are settled from the user terminal used by the user, which is executed by the computer. A step of receiving a payment code issuance request for the payment code, a step of transmitting a payment token for generating the payment code to the user terminal when the payment code issuance request is received, and the payment. The provider identification information that identifies the provider from the provider terminal used by the provider who provided the product or service to the user who read the payment code displayed by the user terminal based on the token. The user has a step of receiving payment information regarding the purchase of the product or service and the payment token, and a step of executing payment based on the payment information received from the provider terminal.

The payment processing device according to the second aspect of the present invention is a user identification information that identifies the user from a user terminal used by the user, and a payment code for the user to make a payment for the purchase of a product or service. Issuance request receiving unit for receiving the issuance request, a token transmitting unit for transmitting a payment token for generating the payment code to the user terminal when receiving the issuance request for the payment code, and the payment. The provider identification information that identifies the provider from the provider terminal used by the provider who provided the product or service to the user who read the payment code displayed by the user terminal based on the token. , A payment information receiving unit that receives payment information regarding the purchase of the product or service by the user and the payment token, and a payment processing unit that executes payment based on the payment information received from the provider terminal. And have.

According to the present invention, there is an effect that the service provider who provided the service to the user can be specified.

It is a figure which shows the outline of the payment system. It is a figure which shows the functional structure of the payment processing apparatus. It is a figure which shows an example of the provider information by store. It is a figure which shows the functional structure of a user terminal. It is a figure which shows the functional structure of a provider terminal. It is an operation sequence diagram of a payment system. It is an operation sequence diagram following FIG.

[Overview of payment system S]
FIG. 1 is a diagram showing an outline of the payment system S. When the user purchases a product or service at a store or the like, the payment system S displays a payment code on the user terminal in response to a request from the user terminal possessed by the user, and the payment code is read by the store. It is a system that makes payments according to the situation. The payment code is a text or image that can be read by the terminal on the store side used for payment at the store, and is a code used at the time of payment. In the following description, goods or services are collectively referred to as goods. Further, the place where the product or service is purchased is not limited to the store, and may be a place different from the store such as a taxi.

The payment system S includes a payment processing device 1, a user terminal 2, and a provider terminal 3. The payment processing device 1 is a server that setstles the purchase price. The user terminal 2 is an information terminal used by the user, for example, a smartphone, a tablet, or a personal computer. The provider terminal 3 is, for example, a smartphone, a tablet, or a POS terminal. The provider terminal 3 is a terminal used by a service provider who belongs to a store and is a clerk or the like who explains a product to a user or provides a product to the user.
Hereinafter, the flow at the time of settlement will be described with reference to FIG.

The payment processing device 1 receives and stores the provider ID as the provider identification information for identifying the service provider in advance from the service provider or the administrator who manages the service provider ((1) in FIG. 1). ).

After that, the user purchases the product at the store. When performing accounting at a store, the user activates application software for payment and performs an operation for displaying the payment code on the user terminal 2. When the user terminal 2 receives an operation for displaying the payment code, the user terminal 2 transmits a user ID as user identification information for identifying the user and a request for issuing the payment code to the payment processing device 1 (in FIG. 1). (2)).

The payment processing device 1 receives a user ID and a request for issuing a payment code from the user terminal 2. Upon receiving the payment code issuance request, the payment processing device 1 generates a payment token ((3) in FIG. 1). The payment token is a data string used when the user terminal 2 generates a payment code presented by the user at the store. The payment processing device 1 stores the generated payment token in association with the user ID in the storage medium ((4) in FIG. 1).

The payment processing device 1 transmits the generated payment token to the user terminal 2 ((5) in FIG. 1). The payment processing device 1 may transmit the encrypted payment token to the user terminal 2 after encrypting the payment token.

The user terminal 2 generates and displays a payment code based on the received payment token ((6) in FIG. 1). The user presents a payment code when the purchase price of the product is settled at the store. Then, for example, by the operation of the service provider, the provider terminal 3 reads the payment code displayed on the user terminal 2 ((7) in FIG. 1).

The provider terminal 3 has a payment information including a service provider's provider ID, a payment amount indicating the total amount of products purchased by the user, and a store ID as store identification information for identifying the store, and read payment. The payment token indicated by the code is transmitted to the payment processing device 1 ((8) in FIG. 1).

When the payment processing device 1 receives the provider ID, the payment information, and the payment token from the provider terminal 3, whether or not the payment token matches the payment token transmitted to the user terminal 2 and whether or not the payment token matches the payment token. It is determined whether the received provider ID is stored. The payment processing device 1 identifies the user ID associated with the payment token when it is determined that the payment tokens match and the received provider ID is stored ((9) in FIG. 1). ). The payment processing device 1 executes payment processing based on the received payment information, the provider ID, and the specified user ID ((10) in FIG. 1). The payment processing device 1 stores the provider ID and the payment information in association with each other ((11) in FIG. 1).

When the payment system S operates as described above, the provider ID is transmitted from the provider terminal 3 used by the provider. As a result, it is possible to suppress the occurrence of an error in the provider ID at the time of payment, so that it is possible to identify the service provider who provided the service to the user.
Hereinafter, the details of the configurations of the payment processing device 1, the user terminal 2, and the provider terminal 3 will be described.

[Functional configuration of payment processing device 1]
FIG. 2 is a diagram showing a functional configuration of the payment processing device 1. The payment processing device 1 has a communication unit 11, a storage unit 12, and a control unit 13.

The communication unit 11 is a communication interface for transmitting and receiving data to and from the user terminal 2 and the provider terminal 3 via a network such as the Internet.

The storage unit 12 is a storage medium for storing various types of data, and includes a ROM (Read Only Memory), a RAM (Random Access Memory), a hard disk, and the like. The storage unit 12 stores a program executed by the control unit 13. The storage unit 12 stores a payment program that causes the control unit 13 to function as a registration unit 131, an issue request reception unit 132, a token transmission unit 133, a payment information reception unit 134, and a payment processing unit 135.

Further, the storage unit 12 stores the store-specific provider information in which the provider ID and the store ID are associated with each other. FIG. 3 is a diagram showing an example of provider information for each store. As shown in FIG. 3, it can be confirmed that one or more provider IDs are associated with each of the plurality of store IDs.

The control unit 13 is, for example, a CPU (Central Processing Unit). The control unit 13 functions as a registration unit 131, an issue request reception unit 132, a token transmission unit 133, a payment information reception unit 134, and a payment processing unit 135 by executing a payment program stored in the storage unit 12. do. The details of the operation of each part of the control unit 13 will be described later.

[Functional configuration of user terminal 2]
FIG. 4 is a diagram showing a functional configuration of the user terminal 2. The user terminal 2 has an operation unit 21, a communication unit 22, a display unit 23, a storage unit 24, and a control unit 25. The control unit 25 includes an operation reception unit 251, a request transmission unit 252, and a code generation unit 253.

The operation unit 21 is an operation device that accepts user operations, and is, for example, a touch panel provided on the surface of the display unit 23. The operation unit 21 notifies the operation reception unit 251 of a signal indicating the position touched by the user.

The communication unit 22 is, for example, a wireless communication interface for transmitting / receiving data to / from a base station of a mobile phone network. The communication unit 22 inputs the payment token or the like received from the payment processing device 1 into the code generation unit 253.

The display unit 23 is a display that displays various types of information. The display unit 23 displays the payment code based on the control of the code generation unit 253.

The storage unit 24 is a storage medium including a ROM, RAM, and the like. The storage unit 24 stores a program executed by the control unit 25. The storage unit 24 stores a program that causes the control unit 25 to function as an operation reception unit 251, a request transmission unit 252, and a code generation unit 253. Further, the storage unit 24 stores the payment token received from the payment processing device 1, the payment code generated based on the payment token, and the like.

The control unit 25 is, for example, a CPU, and functions as an operation reception unit 251, a request transmission unit 252, and a code generation unit 253 by executing a program stored in the storage unit 24.

The operation reception unit 251 specifies the operation content of the user based on the signal input from the operation unit 21. When the specified operation content is an operation for displaying the payment code on the user terminal 2, the operation reception unit 251 receives the chip amount as the grant amount to be given to the service provider on the display unit 23. Display the reception screen and accept the tip amount. The input of the tip amount may be arbitrary, but in the present embodiment, the description will proceed assuming that the tip amount has been accepted.

When the specified operation content is an operation for displaying the payment code on the user terminal 2, the operation reception unit 251 notifies the request transmission unit 252 of the operation content. When the operation reception unit 251 accepts an operation for displaying the payment code on the user terminal 2 and also receives the tip amount, the request transmission unit 252 includes a user ID, chip information indicating the tip amount, and chip information. A request for issuing a payment code is transmitted to the payment processing device 1.

When the payment token is transmitted from the payment processing device 1, the code generation unit 253 generates a payment code based on the payment token. The code generation unit 253 generates, for example, a payment code based on a predetermined rule. The code generation unit 253 causes the display unit 23 to display the generated payment code.

[Functional configuration of provider terminal 3]
FIG. 5 is a diagram showing a functional configuration of the provider terminal 3. The provider terminal 3 has an operation unit 31, a reading unit 32, a communication unit 33, a display unit 34, a storage unit 35, and a control unit 36.

The operation unit 31 is an operation device that accepts the operation of the service provider, and is, for example, a button for selecting a product or a touch panel provided on the surface of the display unit 34.

The reading unit 32 is, for example, a barcode reader and a camera, and reads a barcode attached to a product purchased by the user or a payment code displayed by the user terminal 2. The reading unit 32 outputs the information indicated by the read barcode and the payment code to the control unit 36.

The communication unit 33 is, for example, a communication interface for transmitting / receiving data to / from the payment processing device 1. The communication unit 33 transmits the payment token and the payment information to the payment processing device 1 according to the control of the control unit 36.

The display unit 34 is a display that displays various types of information. The display unit 34 displays, for example, the settlement amount.

The storage unit 35 is a storage medium including a ROM, RAM, and the like. The storage unit 35 stores a program executed by the control unit 36. The storage unit 35 stores a program that causes the control unit 36 to function as a registration request unit 361, a payment information generation unit 362, a token acquisition unit 363, and a payment information transmission unit 364. Further, the storage unit 35 stores a product DB in which the product ID and the price of the product are associated with each other. Further, the storage unit 35 stores the provider ID of the service provider who uses the provider terminal 3. When there are a plurality of service providers using the provider terminal 3, the storage unit 35 stores the provider IDs of the plurality of service providers in association with each other and the names of the service providers.

The control unit 36 is, for example, a CPU, and by executing a payment processing program stored in the storage unit 35, a registration request unit 361, a payment information generation unit 362, a token acquisition unit 363, and a payment information transmission unit Functions as 364.

The registration request unit 361 transmits the registration request of the store and the service provider to the payment processing device 1. Specifically, when the operation unit 31 receives the registration operation of the store and the service provider from the service provider, the registration request unit 361 provides the store information about the store and the information of the service provider belonging to the store. The registration acceptance screen for accepting the person information is displayed on the display unit 34, and the registration of the store and the provider is accepted. Here, the store information may also include information on the business operator to which the store belongs.

When the registration request unit 361 receives the store information on the registration reception screen, the registration request unit 361 transmits the store registration request including the store information to the payment processing device 1. Further, when the registration request unit 361 receives the provider information on the registration acceptance screen, the registration request unit 361 transmits the provider registration request including the provider information to the payment processing device 1. Here, the store information is information that can identify the store, such as a store name and a store address. The provider information is, for example, the name and date of birth of the service provider.

The registration request unit 361 may accept the registration of the provider terminal 3. In this case, the registration request unit 361 transmits a terminal registration request including a terminal ID that identifies the provider terminal 3 to the payment processing device 1. The terminal ID is, for example, an application ID for identifying a plurality of provider terminals 3 by a payment processing program executed in the provider terminal 3, or a MAC address of the provider terminal 3.

The payment information generation unit 362 identifies one or more products to be settled and generates payment information. Specifically, the payment information generation unit 362 has acquired the product ID input by the service provider in the operation unit 31 or the product ID read by the reading unit 32 from the barcode attached to the product. Identify the product with the product ID as the product to be settled. The settlement information generation unit 362 refers to the product DB stored in the storage unit 35, and specifies the price of the product associated with the acquired product ID. The payment information generation unit 362 acquires one or more product IDs input by the service provider in the operation unit 31 or the product ID read from the barcode attached to the product by the reading unit 32, and the product specified from the product ID. Aggregate the prices of. When the settlement information generation unit 362 receives the settlement operation in the operation unit 31, the settlement information generation unit 362 determines the price of the aggregated product as the settlement amount. The payment information generation unit 362 generates payment information including a payment amount and a store ID as store identification information for identifying a store.

Further, the payment information generation unit 362 specifies the provider ID to be transmitted to the payment processing device 1. For example, the payment information generation unit 362 accepts the input of the provider ID via the operation unit 31, and when the received provider ID is stored in the storage unit 35, the provider ID is stored in the storage unit 35, and the payment processing device 1 Specified as a provider ID to be sent to. The payment information generation unit 362 causes the display unit 34 to display at least one of one or more provider IDs stored in the storage unit 35 and the name of the service provider, and either provider ID or service. By accepting the selection of the name of the provider, the provider ID to be transmitted to the payment processing device 1 is specified.

The token acquisition unit 363 acquires the information extracted from the payment code as a payment token by the reading unit 32 reading the payment code displayed on the user terminal 2.
In the payment information transmission unit 364, when the payment information generation unit 362 generates payment information and the token acquisition unit 363 acquires the payment token, the payment token and the specified provider ID are identified via the communication unit 33. And the payment information are transmitted to the payment processing device 1.

[Operation of each part of control unit 13]
Subsequently, the operation of each unit of the control unit 13 will be described.
The registration unit 131 registers the store and the service provider from the provider terminal 3. For example, the registration unit 131 receives a store information registration request from the provider terminal 3. Upon receiving the store information registration request, the registration unit 131 generates a store ID, associates the store information with the store ID, and stores the store in the storage unit 12, thereby registering the store.

Here, it is assumed that the store ID includes a business ID that identifies the business to which the store belongs. In the present embodiment, the registration unit 131 generates the store ID including the business ID, but the present invention is not limited to this, and the business ID of the business that operates the store may be generated separately from the store ID. good. When the registration unit 131 generates the business ID separately from the store ID, the business ID and the store ID may be associated with each other and stored in the storage unit 12. Further, when the business operator operates only one store, the store ID and the business operator ID may be the same.

Further, the registration unit 131 receives the provider information for identifying the service provider associated with the registered store from the provider terminal 3. Upon receiving the provider information, the registration unit 131 generates the provider ID. The registration unit 131 associates the generated provider ID with the store ID of the registered store and stores it in the storage unit 12. The registration unit 131 may store the terminal ID that identifies the provider terminal 3 and the provider ID in the storage unit 12.

The registration unit 131 decides to register the store and the service provider by receiving the store information and the registration request of the service provider from the provider terminal 3, but the present invention is not limited to this. Unlike the provider terminal 3, the registration unit 131 receives store information and a service provider registration request from a terminal or server used in the store to register the store and the service provider. You may do it. In this case, the provider terminal 3 and the terminal or server used in the store may be the same. Further, in the present embodiment, the terminal ID and the provider ID are different from each other, but the present invention is not limited to this, and the provider ID may be used as the terminal ID.

The issuance request receiving unit 132 receives from the user terminal 2 a user ID, chip information indicating the amount of chips given to the service provider by the user, and a request for issuing a payment code for the user to make a payment at a store. do.

When the issuance request receiving unit 132 receives the issuance request of the payment code, the token transmission unit 133 transmits a payment token for generating the payment code to the user terminal 2. Specifically, the token transmitting unit 133 generates a payment token when the issuance request receiving unit 132 receives a payment code issuance request. When the token transmission unit 133 generates the payment token, the token transmission unit 133 stores the user ID acquired by the issuance request reception unit 132, the chip information, and the generated payment token in the storage unit 12. Further, the token transmission unit 133 transmits the generated payment token to the user terminal 2 that has transmitted the payment code issuance request.

The payment information receiving unit 134 reads the payment code displayed by the user terminal 2 based on the payment token transmitted by the token transmitting unit 133, and the service provider's provider ID and the user's Receives payment information regarding the purchase of goods and payment tokens. It is assumed that the payment information includes the store ID and the payment amount at the user's store.

When the payment processing unit 135 receives the payment information and the payment token from the provider terminal 3, the payment processing unit 135 executes the payment based on the received payment information. When the provider ID received from the provider terminal 3 and the store ID included in the received payment information are associated and stored in the storage unit 12, the payment processing unit 135 makes a payment based on the received payment information. To execute.

Specifically, when the payment processing unit 135 receives the payment information and the payment token, the payment processing unit 135 determines whether or not the payment token matching the payment token is stored in the storage unit 12. Is determined. When the payment processing unit 135 determines that the matching payment token is stored in the storage unit 12, the payment processing unit 135 stores the provider ID received from the provider terminal 3 in association with the store ID included in the received payment information. It is determined whether or not it is stored in the unit 12. When the payment processing unit 135 determines that the received provider ID and the store ID are associated and stored in the storage unit 12, the user ID associated with the received payment token and stored in the storage unit 12 is stored. And the chip information.

The payment processing unit 135 executes a process of deducting the total amount of the payment amount included in the received payment information and the chip amount from the account of the user corresponding to the specified user ID. Further, the payment processing unit 135 executes a process of depositing the payment amount included in the received payment information into the account of the store specified by the store ID included in the received payment information.

The payment processing unit 135 grants the service provider the amount of the chip based on the chip information stored in the storage unit 12 in association with the payment token received from the provider terminal 3. For example, the payment processing unit 135 grants the tip amount to the service provider by executing a process of depositing the tip amount indicated by the specified chip information into the service provider's account indicated by the received provider ID. do.

When the payment is made based on the payment information, the payment processing unit 135 stores the provider ID received from the provider terminal 3 in the storage unit 12 in association with the payment information. By doing so, the payment processing device 1 can specify the service provider who provided the service to the user.

Further, the payment processing unit 135 stores the payment amount related to the purchase of the user's product or service, the provider ID received from the provider terminal 3, and the date and time when the payment token is received in the storage unit 12. You may do so. For example, the payment processing unit 135 stores the provider ID received from the provider terminal 3, the payment amount included in the payment information, the chip information, and the date and time when the payment token is received as payment management information. It may be stored in 12. By doing so, it is possible to manage the sales of each service provider by referring to the payment management information. Further, the payment processing unit 135 may refer to the payment management information to total the amount of chips given to the service provider in a predetermined period, and collectively give the totaled amount of chips to the service provider. good.

When the payment is made based on the payment information, the payment processing unit 135 notifies the user terminal 2 of the payment completion information indicating that the payment has been completed. Further, the payment processing unit 135 provides payment completion information, a provider ID, and information indicating the amount of chips given to the service provider indicated by the provider ID when payment is made based on the payment information. It is transmitted to the provider terminal 3 in association with each other, and the provider terminal 3 is made to display information indicating the amount of the chip given to the service provider. By doing so, the service provider can confirm the amount of chips given to him / her.

The payment processing unit 135 may receive the terminal ID of the provider terminal 3 together with the payment token from the provider terminal 3. In this case, when the received terminal ID is stored in the storage unit 12, the payment processing unit 135 executes payment based on the payment information received from the provider terminal 3, and the terminal ID is stored in the storage unit 12. If it is not remembered, the payment may not be executed. By doing so, payment can be made only when a payment token is received from the pre-registered provider terminal 3, so that a third party can use a terminal that is not pre-registered for fraud. It is possible to prevent the payment from being made.

[Operation sequence]
FIG. 6 is an operation sequence diagram of the payment system S. FIG. 7 is an operation sequence diagram following FIG.
The sequence diagram shown in FIG. 7 starts from the point where the service provider of the provider terminal 3 performs the registration operation of the store and the service provider (S1). The registration request unit 361 transmits a registration request for the store and the service provider, including the store information and the provider information, to the payment processing device 1 (S2).

Upon receiving the registration request from the provider terminal 3, the registration unit 131 of the payment processing device 1 generates a store ID and a provider ID (S3). The registration unit 131 registers the store and the service provider by associating the generated store ID with the provider ID and storing the store ID in the storage unit 12 (S4).

After that, when the user performs a payment code display operation on the user terminal 2 at the store (S5) and receives the chip amount to be given to the service provider (S6), the request transmission unit 252 uses the user ID and the user ID. Chip information including the amount of the chip and a request for issuing a payment code are transmitted to the payment processing device 1 (S7).

When the issue request receiving unit 132 of the payment processing device 1 acquires the user ID, the chip information, and the payment code issuance request from the user terminal 2, the token transmission unit 133 for generating the payment code. Generate a payment token (S8). The token transmission unit 133 stores the received user ID, the chip information, and the generated payment token in the storage unit 12 in association with each other (S9). The token transmission unit 133 transmits the generated payment token to the user terminal 2 that has transmitted the payment code issuance request (S10).

The explanation is transferred to FIG. The code generation unit 253 of the user terminal 2 generates a payment code based on the payment token received from the payment processing device 1, and causes the display unit 23 to display the generated payment code (S11). At the store, the user presents the payment code displayed on the user terminal 2, and the reading unit 32 of the provider terminal 3 reads the payment code (S12).

Further, the payment information generation unit 362 of the provider terminal 3 has a product ID input by the service provider in the operation unit 31 or a product price read by the reading unit 32 from the barcode attached to the product. Is specified, and the settlement amount is calculated (S13). The payment information transmission unit 364 of the provider terminal 3 is included in the payment information including the provider ID of the service provider, the calculated payment amount and the store ID, and the payment code read in S12. The payment token is transmitted to the payment processing device 1 (S14).

Subsequently, the payment information receiving unit 134 of the payment processing device 1 receives the provider ID, the payment information, and the payment token from the provider terminal 3. When the payment token stored in the storage unit 12 and the received payment token match, the payment processing unit 135 identifies the user ID and chip information associated with the payment token (S15). .. Subsequently, the payment processing unit 135 performs payment processing based on the specified user ID and chip information and the store ID included in the received payment information (S16).

Subsequently, the payment processing unit 135 notifies the user terminal 2 of the payment completion information indicating that the payment has been completed (S17), and transfers the payment completion information, the provider ID, and the chip information to the provider terminal 3. Notify (S18).

[Modification example]
In the above description, the payment processing device 1 also receives the chip information at the timing when the user ID and the payment code issuance request are received from the user terminal 2, but the present invention is not limited to this. For example, the tip amount may be accepted at the timing when the user terminal 2 displays the payment code. Then, when the user terminal 2 receives the tip amount, the chip information indicating the chip amount may be transmitted to the payment processing device 1.

[Effect of payment system S according to this embodiment]
As described above, when the payment processing device 1 receives the user ID and the payment code issuance request from the user terminal 2, the payment processing device 1 transmits the payment token to the user terminal 2, and the user terminal is based on the payment token. The provider ID, payment information, and payment token are received from the provider terminal 3 used by the service provider who has read the payment code displayed by 2. Then, the payment processing device 1 executes payment based on the payment information received from the provider terminal 3, and stores the provider ID and the payment information in the storage unit 12. By doing so, the payment processing device 1 can specify the service provider who provided the service to the user.

Although the present invention has been described above using the embodiments, the technical scope of the present invention is not limited to the scope described in the above embodiments, and various modifications and changes can be made within the scope of the gist. be. For example, the specific embodiment of the distribution / integration of the device is not limited to the above embodiment, and all or a part thereof may be functionally or physically distributed / integrated in any unit. Can be done. Also included in the embodiments of the present invention are new embodiments resulting from any combination of the plurality of embodiments. The effect of the new embodiment produced by the combination has the effect of the original embodiment together.

1 Payment processing device 2 User terminal 3 Provider terminal 11 Communication unit 12 Storage unit 13 Control unit 21 Operation unit 22 Communication unit 23 Display unit 24 Storage unit 25 Control unit 31 Operation unit 32 Reading unit 33 Communication unit 34 Display unit 35 Storage unit 36 Control unit 131 Registration unit 132 Issuance request reception unit 133 Token transmission unit 134 Payment information reception unit 135 Payment processing unit 251 Operation reception unit 252 Request transmission unit 253 Code generation unit 361 Registration request unit 362 Payment information generation unit 363 Token acquisition Department 364 Information transmission unit for payment

Claims (14)

Computer runs,
A step of receiving a user identification information that identifies the user and a request for issuing a payment code for the user to make a payment for the purchase of a product or service from a user terminal used by the user.
Upon receiving the payment code issuance request, a step of transmitting a payment token for generating the payment code to the user terminal, and a step of transmitting the payment token to the user terminal.
Provider identification that identifies the provider from the provider terminal used by the provider who provided the product or service to the user by reading the payment code displayed by the user terminal based on the payment token. A step of receiving information, payment information regarding the purchase of the product or service by the user, and a payment token.
A step of executing payment based on the payment information received from the provider terminal, and
Payment processing method with. Further comprising a step of associating the provider identification information with the payment information and storing the payment information in the storage unit, which is executed by the computer.
The payment processing method according to claim 1. When the payment based on the payment information executed by the computer is completed, the computer further includes a step of associating the payment completion information indicating that the payment is completed with the provider identification information and transmitting the payment to the provider terminal.
The payment processing method according to claim 1 or 2. Further comprising a step of storing the provider identification information in the storage unit, which is executed by the computer.
In the step of executing the payment, the computer makes a payment based on the payment information received from the provider terminal when the provider identification information received from the provider terminal is stored in the storage unit. To execute,
The payment processing method according to any one of claims 1 to 3. In the step of storing in the storage unit, the computer associates the business operator identification information for identifying the business operator to which the provider belongs with the provider identification information and stores the information in the storage unit.
In the step of receiving the payment token, the computer receives the payment information including the business identification information from the provider terminal.
In the step of executing the payment, the computer associates the provider identification information received from the provider terminal with the business operator identification information included in the payment information received from the provider terminal. When stored in the storage unit, payment is executed based on the payment information received from the provider terminal.
The payment processing method according to claim 4. In the step of receiving the payment token, the computer receives the terminal identification information that identifies the provider terminal as the provider identification information.
The payment processing method according to any one of claims 1 to 5. Further, the computer has a step of storing the terminal identification information for identifying the provider terminal in the storage unit, which is executed by the computer.
In the step of receiving the payment token, the computer further receives the terminal identification information from the provider terminal.
In the step of executing the payment, the computer makes a payment based on the payment information received from the provider terminal when the terminal identification information received from the provider terminal is stored in the storage unit. Run,
The payment processing method according to any one of claims 1 to 5. In the step of receiving the payment code issuance request, the computer further receives information from the user terminal indicating the amount of money granted by the user to the provider.
Computer runs,
A step of associating a payment token to be transmitted to the user terminal with information indicating the granted amount and storing it in a storage unit.
A step of associating the grant amount stored in the storage unit in association with the payment token received from the provider terminal with the provider identification information received from the provider terminal.
Have more,
The payment processing method according to any one of claims 1 to 7. In the step of executing the payment, when the computer receives the payment token, the computer executes the payment based on the granted amount and the payment amount of the product or service indicated by the payment information received from the provider terminal. do,
The payment processing method according to claim 8. An issuance request receiving unit that receives user identification information that identifies the user and a payment code issuance request for the user to make a payment for the purchase of a product or service from a user terminal used by the user.
Upon receiving the payment code issuance request, a token transmission unit that transmits a payment token for generating the payment code to the user terminal, and a token transmission unit.
Provider identification that identifies the provider from the provider terminal used by the provider who provided the product or service to the user by reading the payment code displayed by the user terminal based on the payment token. A payment information receiving unit that receives information, payment information regarding the purchase of the product or service by the user, and the payment token.
A payment processing unit that executes payment based on the payment information received from the provider terminal, and
Payment processing device with. The payment processing unit associates the provider identification information with the payment information and stores it in a storage unit.
The payment processing device according to claim 10. Further having a registration unit for storing the provider identification information in the storage unit,
When the provider identification information received from the provider terminal is stored in the storage unit, the payment processing unit executes payment based on the payment information received from the provider terminal.
The payment processing device according to claim 10 or 11. The payment information receiving unit receives the terminal identification information that identifies the provider terminal as the provider identification information.
The payment processing device according to any one of claims 10 to 12. The issuance request receiving unit further receives information indicating the amount of grant given by the user to the provider from the user terminal.
The token transmission unit stores the payment token to be transmitted to the user terminal and the information indicating the granted amount in the storage unit in association with each other.
The payment processing unit associates the grant amount stored in the storage unit with the payment token received from the provider terminal with the provider identification information received from the provider terminal.
The payment processing device according to any one of claims 10 to 13.

Images