JP7471381B1 - Payment system, payment method, payment service providing device, and program - Google Patents

Abstract

[Problem] To allow a reward to be conveniently paid within the flow of electronic payment at a physical store. [Solution] A payment system comprising an application program running on a user terminal device and a payment service providing device that cooperates with the application program to allow a user to make an electronic payment at a physical store belonging to an affiliated store, the application program causes the user terminal device to accept operations for the electronic payment performed by the user and to accept an instruction to remit the reward to the affiliated store related to the electronic payment, the payment service providing device having a payment processing unit that performs processing for the electronic payment based on payment information acquired from the user terminal device, and a remittance processing unit that performs processing to remit the reward from the user's account to the affiliated store's account in accordance with the contents of the remittance instruction accepted by the application program. [Selected Figure] Figure 3

Description

The present invention relates to a payment system, a payment method, a payment service providing device, a program, and an application program.

A server invention has been disclosed in which a first terminal held by a tip recipient outputs the recipient's recipient identification information to a second terminal of the tip recipient located within a specified distance, obtains from the second terminal the payer identification information of the tip payer and tip amount information indicating the tip amount, performs a charging process of electronic money equivalent to the tip amount to an account corresponding to a first payment method specified by the payer identification information, and performs a transfer process of electronic money equivalent to the tip amount to an account corresponding to a second payment method specified by the recipient identification information.

JP 2021-174162 A

Conventional technology requires short-range wireless communication between terminals, making it difficult to apply to current electronic payments.

The present invention has been made in consideration of these circumstances, and one of its objectives is to provide a payment system, a payment method, a payment service providing device, a program, and an application program that enable the efficient payment of a tip within the flow of electronic payments at a brick-and-mortar store.

One aspect of the present invention is a payment system comprising an application program that runs on a user terminal device, and a payment service providing device that cooperates with the application program to allow a user to make an electronic payment at a physical store belonging to an affiliated store, in which the application program causes the user terminal device to accept operations for the electronic payment performed by the user and to accept an instruction to remit a reward to the affiliated store related to the electronic payment, and the payment service providing device has a payment processing unit that performs processing for the electronic payment based on payment information acquired from the user terminal device, and a remittance processing unit that performs processing to remit the reward from the user's account to the affiliated store's account in accordance with the content of the remittance instruction accepted by the application program.

According to one aspect of the present invention, it is possible to provide a payment system, a payment method, a payment service providing device, a program, and an application program that enable the payment of a reward to be conveniently performed within the flow of electronic payments at a physical store.

FIG. 1 is a diagram showing an example of a configuration for realizing an electronic payment service. FIG. 1 is a diagram illustrating an example of a general flow of electronic payment. FIG. 2 is a configuration diagram of a payment server 100. FIG. 11 is a diagram showing an example of the contents of user information 172. FIG. 13 is a diagram showing an example of the contents of tip payment settings 172A. FIG. 13 is a diagram showing an example of the contents of store information 174. FIG. 13 is a sequence diagram showing an example of a process flow including the payment of a tip when settlement according to pattern 1 is performed. FIG. 8 is a diagram showing an example of a payment completion notification screen IM1 that is displayed when the store's tip acceptance setting information is set to "accepted" in S8 of FIG. 7. FIG. 8 is a diagram showing an example of a payment completion notification screen IM2 that is displayed when the store's tip acceptance setting information is set to "rejected" in S8 of FIG. 7. FIG. 13 is a sequence diagram showing an example of a process flow including the payment of a tip when settlement according to pattern 2 is performed. FIG. 13 is a diagram showing an example of a reception screen IM3 for receiving a tip remittance instruction. FIG. 13 is a diagram showing an example of a tip setting display screen IM4. A figure showing an example of a payment screen IM5 including a second code image.

The following describes the payment system, payment method, payment service providing device, program, and application program of the present invention with reference to the drawings. The payment system includes a payment service providing device and an application program. The payment service providing device is realized by one or more processors. The payment service providing device is a device that provides services such as electronic payment services. In the following description, the payment service providing device is referred to as a "payment server." An electronic payment service is a service that supports payments related to the purchase of goods and services at a store. A store is a physical store (real store) that exists in real space. The application program runs on a user terminal device. The application program communicates with the payment service providing device to obtain user balance information, etc., and functions as an interface when the user makes an electronic payment. In the following description, the application program is referred to as a "payment app."

[Electronic payment service]
1 is a diagram showing an example of a configuration for realizing an electronic payment service. The electronic payment service is realized mainly by a payment server 100. The payment server 100 communicates with, for example, one or more user terminal devices 10 and one or more store terminal devices 50 via a network NW. The network NW includes, for example, the Internet, a LAN (Local Area Network), a wireless base station, a provider device, and the like.

The user terminal device 10 is, for example, a portable terminal device such as a smartphone or a tablet terminal. The user terminal device 10 is a computer device having at least an optical reading function, a communication function, a display function, an input acceptance function, and a program execution function. In the following description, the components for realizing these functions are respectively referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), etc. In the user terminal device 10, a payment app 20 is executed by a processor such as a CPU, and the user terminal device 10 operates in cooperation with the payment server 100 to provide electronic payment services to users. The payment app 20 controls the camera, communication device, touch panel, etc.

The store terminal device 50 is installed, for example, in a store. The store terminal device 50 is a computer device having at least a product price acquisition function, an optical reading function, a program execution function, and a communication function. The store terminal device 50 includes a so-called POS (Point of Sale) device, and the product price acquisition function and the optical reading function may be realized by the POS device. The store code image 60 is placed in the store, and is a code image such as a QR code (registered trademark) printed on a paper or plastic medium. The store code image 60 may be displayed on a display placed in the store.

The payment server 100 realizes electronic payment based on payment information received from the user terminal device 10 or the store terminal device 50. The payment server 100 performs electronic payment, for example, by increasing or decreasing the charge balance managed in association with the user ID (in other words, by depositing or withdrawing electronic money). Electronic payment may include a method that allows purchases of a larger amount than the charge balance at the time of purchase, such as revolving payment or credit payment.

Figure 2 is a diagram illustrating the general flow of electronic payment. There may be two patterns for electronic payment: pattern 1 and pattern 2. In the case of pattern 1, the payment application 20 is first launched on the user terminal device 10, and a code image such as a QR code or a barcode is displayed. The user holds (presents) the display surface of the user terminal device 10 over the store terminal device 50. The store terminal device 50 decodes the code image using an optical reading function and acquires information that can recognize the account ID (for example, a one-time code issued by the payment server 100 in association with the account ID). The store terminal device 50 then generates payment information including information that can recognize the account ID, the payment amount, the store ID, etc., and transmits it to the payment server 100. The payment amount information has been acquired in advance by reading a barcode, manually entering, etc. The payment server 100 transfers the payment amount from the user's electronic payment account to the store's electronic payment account based on the received information, and completes the payment process.

In the case of pattern 2, the user terminal device 10 with the payment app 20 running uses an optical reading function to decode the store code image 60. The store code image 60 contains information such as the store name. The user inputs the payment amount into the user terminal device 10 on the screen displaying the store name, etc. The user terminal device 10 then generates payment information including the account ID, payment amount, store ID, etc., and transmits it to the payment server 100. The payment server 100 performs payment processing based on the received information. Note that electronic payment may be performed only in one of the above patterns. The "account ID" described in FIG. 2 may also be other information (e.g., a phone number) that can be used as user identification information.

[Payment server]
FIG. 3 is a configuration diagram of the payment server 100. The payment server 100 includes, for example, a communication unit 110, a payment content providing unit 120, a payment processing unit 130, a remittance processing unit 140, and a storage unit 170. The components other than the communication unit 110 and the storage unit 170 are realized by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuitry) such as an LSI (Large Scale Integration), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a GPU (Graphics Processing Unit), or may be realized by cooperation between software and hardware. The program may be stored in advance in a storage device (a storage device having a non-transient storage medium) such as an HDD (Hard Disk Drive) or a flash memory, or may be stored in a removable storage medium (non-transient storage medium) such as a DVD or a CD-ROM, and may be installed in the storage device by mounting the storage medium in a drive device.

The storage unit 170 is a HDD, a flash memory, a RAM (Random Access Memory), etc. The storage unit 170 may be a NAS (Network Attached Storage) device that the payment server 100 can access via a network. The storage unit 170 stores information such as user information 172, store information 174, and payment content information 176.

The communication unit 110 is a communication interface for connecting to the network NW. The communication unit 110 is, for example, a network interface card.

The payment content providing unit 120 has, for example, a web server function, and provides the user terminal device 10 with information (content) for displaying various screens of the electronic payment service. The payment content providing unit 120 reads out the necessary content from the payment content information 176 as appropriate and provides it to the user terminal device 10. The user terminal device 10 accepts various inputs by the user while the content is being played by the payment application 20, and transmits the above-mentioned payment information and the like to the payment server 100. Note that the content based on the payment content information 176 includes content provided in a logged-in state and content provided in a non-logged-in state. In the content in the non-logged-in state, the payment server 100 provides various guidance information and accepts applications for new registrations and changes to phone numbers.

The payment processing unit 130 performs payment processing based on the payment information sent by the user terminal device 10 or the store terminal device 50. The payment processing unit 130 performs payment processing while referring to the user information 172.

Figure 4 is a diagram showing an example of the contents of user information 172. User information 172 is an example of user registration information. For example, user information 172 is an account ID (which may be omitted) associated with information such as a phone number and password, which are the minimum required for new registration, as well as an email address, user ID, name, address, date of birth, registration date, charge balance, tip payment setting 172A, bank account, credit card number, charge history information, and payment history information. Information other than the phone number, password, registration date, charge balance, charge history information, and payment history information is optional information. Hereinafter, a user instance (electronic payment account) associated with this information is referred to as an account. The registration date is the date on which the user registered with the electronic payment service (the date on which the account was created).

The charge balance is information indicating the balance of electronic money that is set by the user by transferring money to the account in advance. The means of transfer include transfer from an ATM (Automatic Teller Machine) of a designated company (bank) and transfer from a registered bank account. The deferred payment setting is information indicating whether or not the setting for enabling electronic payment by deferred payment has been completed, and is set to either "completed" or "not completed". The deferred payment limit is the limit of deferred payment that can be used each month, the deferred payment usage amount is the amount of deferred payment that has already been used in the current month, and the deferred payment available amount is the amount of deferred payment that can be used in the current month, which is calculated by subtracting the deferred payment usage amount from the deferred payment limit. Although only one deferred payment limit is shown in the figure, in reality, there is also a daily upper limit, and the lower of these may be set as the deferred payment limit. The payment method setting is setting information indicating whether the user will make electronic payment using the charge balance or payment by deferred payment at that time. The tip payment setting 172A will be explained with reference to another figure. The bank account and credit card number are information on a bank account or credit card number (account number, card number) that can be used to deposit funds into an electronic payment service. The charge history information is a history of the user transferring funds to the electronic payment service in advance to increase the charge balance. The payment history information is information that shows the details of payments made by the user for each payment (date and time, store ID of the store where the purchase was made, payment amount, etc.).

Figure 5 is a diagram showing an example of the contents of tip payment settings 172A. Tip payment settings 172A are an example of "gratuity remittance settings." Tip payment settings 172A include, for example, information specifying a tip payment target and information specifying a tip payment excluded target. Information specifying a tip payment target includes, for example, information specifying a store category, information specifying a store that meets generalized conditions, information directly specifying a store, and the like. Store categories are described below. The desired condition is, for example, information about a store that has been used "a certain number of times within the past year." The "within the past year" and "a certain number of times" parts may be selectable by the user. These conditions may be treated as AND conditions or OR conditions.

Similarly, the information specifying the items not eligible for tipping also includes information specifying the store category and information specifying the stores that meet generalized conditions. These conditions may also be treated as AND conditions or OR conditions. For example, a user who does not want to pay tips at drugstores or convenience stores can specify those categories as items not eligible for tipping. Note that tip payment settings 172A may only include information specifying the items not eligible for tipping.

Tip payment settings 172A are information that is set by the user asynchronously with the electronic payment (although it is not excluded that it may happen to be immediately before or after the electronic payment) on the interface screen provided by the payment application 20.

Information about stores is managed as store information 174. FIG. 6 is a diagram showing an example of the contents of store information 174. As shown in the upper diagram of FIG. 6, store information 174 is, for example, information such as a store URL (Uniform Resource Locator), store category, location, and payment pattern associated with a store ID. The store category may be one-level information, or may be information having a hierarchical structure of two or more levels. For example, information such as "Japanese food," "restaurant," or "eatery" may be added as a higher-level concept of "sushi" as shown in the figure. The location may be represented by a hierarchical code image such as a JIS code. The payment pattern is information indicating whether payment can be made using pattern 1 or pattern 2 described above.

As shown in the lower diagram of Figure 6, store information 174 may also include information indicating the relationship between affiliated stores and stores. Stores that use electronic payment services belong to one of the affiliated stores (brands). Store information 174 associates one or more store IDs, tip acceptance setting information, wallet information, etc. with an affiliated store ID. In the diagram, only one store ID is associated with the affiliated store indicated by the affiliated store ID B002, which indicates that there is only one store that makes up the affiliated store.

The tip acceptance setting information is information indicating whether or not the affiliated store will accept a reward (hereinafter, "tip") from a user. The tip remittance process will be described in detail later. The tip acceptance setting information is, for example, obtained in advance via an interface provided to the operator of the affiliated store. The tip acceptance setting information may be accepted collectively for each affiliated store, or may be set so that acceptance differs for each store depending on the affiliated store. The wallet information is information on the payment balance and remittance balance associated with the store. The wallet information may also have a list for each store ID. The payment balance indicates the balance of the amount paid to the store through the payment process, and the remittance balance indicates the balance of the amount remitted to the store through the remittance process, including the payment of the tip.

When payment information is acquired from the user terminal device 10 or the first store terminal device 50, the payment processing unit 130 refers to the user information 172 to acquire the "payment method setting" of the user. For a user whose "payment method setting" is set to "charge balance", the payment processing unit 130 performs electronic payment as follows. For example, the payment processing unit 130 performs electronic payment by decreasing the charge balance managed in association with the user ID and increasing the item value of the affiliated store's sales. The item value of the affiliated store's sales is not used as electronic money itself, for example, and an amount corresponding to the item value of the sales is transferred to a bank account in a cycle according to an agreement between the affiliated store and the electronic payment service.

The payment processing unit 130 performs electronic payment for users whose "setting information" is set to "deferred payment" as follows. Deferred payment is set separately from "credit payment" in cooperation with a credit card company, which is a separate entity from the operator of the electronic payment service, and the operator of the electronic payment service acts as the creditor and allows electronic payment that is not dependent on the charge balance within the deferred payment limit. In order to receive the deferred payment service, it may be required to obtain a credit card provided by the operator of the electronic payment service. The amount used for deferred payment is settled on the payment date of the following month, for example, by debiting from a bank account, for one month's worth. In this case, the payment processing unit 130 performs provisional payment by adding the settlement amount to the deferred payment amount and subtracting the same amount from the available deferred payment amount, and when the closing date comes, it performs processing to debit the payment for the current month on the payment date of the following month as described above. In addition, if the settlement amount exceeds the available deferred payment amount at the time of provisional payment, an error notification is returned to the payment application 20.

The remittance processing unit 140 realizes the payment of tips from the user to the affiliated store, which is associated with electronic payment. The remittance processing unit 140 performs processing to remit tips from the user's account to the affiliated store's account (the remittance balance in the wallet information of the store information 174) in accordance with the contents of the remittance instruction accepted by the payment application 20. Here, the remittance processing unit 140 may subtract the amount related to the tip from the charge balance of the user 172 and add it to the affiliated store's account, or may perform processing for settlement by later payment such as the aforementioned deferred payment or credit card linkage (processing to add to the deferred payment amount, or processing to notify the credit card company of the amount) and add it to the affiliated store's account. In the following explanation, it is assumed that the tip is paid from the charge balance.

[Process flow]
FIG. 7 is a sequence diagram showing an example of the flow of processing including tip payment when a payment of pattern 1 is made. It is assumed that the setting operation of tip payment setting 172A is completed at the time when the processing of this figure is started. First, the user operates the user terminal device 10 to start the payment application 20 (S1). In parallel with this, on the store side, the store terminal device 50 acquires the payment amount by barcode reading, manual input, etc. (S2). The payment application 20 transmits a payment request to the payment server 100 in response to the user's payment operation (operation to instruct the start of electronic payment) or in response to its own automatic update (S3). In response to this, the payment server 100 transmits a one-time code to the user terminal device 10 (S4). The payment application 20 causes the user terminal device 10 to display a code image (second code image) based on the one-time code. The user holds this code image over the store terminal device 50 (S5).

The store terminal device 50 decodes the code image, generates payment information including the one-time code, the payment amount, and the store ID (S6), and transmits the payment information to the payment server 100 (S7).

In the payment server 100, the payment processing unit 130 obtains the account ID from the one-time code and performs the payment process (S8). When the payment process is completed, the process proceeds to the tip remittance process, but if the payment process fails due to insufficient balance or other reasons, the tip to be remitted is discarded.

When the payment process is completed, the remittance processing unit 140 refers to the store information 174 and checks whether the tip acceptance setting information of the affiliated store ID (store ID if set for each store) corresponding to the store related to the store ID is set to "accepted" (S9). If the tip acceptance setting information is set to "accepted", the remittance processing unit 140 refers to the tip payment setting 172A and determines whether the store related to the store ID is eligible for tip payment (S10). If it is eligible for tip payment, the remittance processing unit 140 transfers the amount equivalent to the tip from the charge balance of the user related to the account ID to the remittance balance in the store wallet information of the store related to the store ID (S11).

Then, a payment completion notification is sent from the payment server 100 to the user terminal device 10 (S12). In response to this, the user terminal device 10 displays a payment completion notification screen. FIG. 8 is a diagram showing an example of a payment completion notification screen IM1 displayed when the tip acceptance setting information of the affiliated store or store is set to "accepted" in S8. The payment completion notification screen IM1 includes, for example, an area A1 where information about the store where the payment was made is displayed, an area A2 where the payment amount, etc. are displayed, an area A3 where points given to the user as a result of the payment are displayed, and an area A4 where the tip payment result is displayed. The area A4 of the payment completion notification screen IM1 displays information indicating that the tip payment has been completed. FIG. 9 is a diagram showing an example of a payment completion notification screen IM2 displayed when the tip acceptance setting information of the affiliated store or store is set to "not accepted" in S8. The area A4 of the payment completion notification screen IM2 displays information indicating that the tip payment was not realized (the tip was not accepted). In addition, if the store associated with the store ID is not eligible for tip payment, it is assumed that the user is aware that this is not the case, so information regarding tips does not need to be displayed on the payment completion notification screen.

In this way, in pattern 1, by accepting input operations related to tip payment asynchronously with electronic payment, tip payment can be conveniently performed within the flow of electronic payment at a physical store. Also, within the flow of the process, processing related to affiliated stores or stores that do not accept tips can be executed seamlessly.

Figure 10 is a sequence diagram showing an example of the process flow including the payment of a tip when a payment of pattern 2 is made. First, the user operates the user terminal device 10 to launch the payment app 20 (S21). Next, the user uses the user terminal device 10 to capture an image of the store's code and obtain the encoded information (S22). The payment app 20 obtains the store URL by decoding the store's code image (S23). Next, the store URL is an example of "store-related information." The user inputs the electronic payment amount and information regarding instructions to send a tip into the payment app 20 (S24).

11 is a diagram showing an example of a reception screen IM3 for receiving a tip remittance instruction. The reception screen IM3 is provided with, for example, an area A11 for displaying store information and the payment amount input by the user, an area A12 for displaying the user's charge balance, switches S1 and S2 for specifying the tip ratio to the payment amount, a slide switch S3 for specifying whether to pay a tip, a button B1 for confirming the payment of the payment amount and the tip after they are confirmed, and a key K1 for inputting the payment amount. The user can switch whether to pay a tip in the electronic payment by sliding the slide switch S3 left and right. Instead of a slide operation, whether to pay a tip may be switched by another predetermined operation such as tapping. The amount of the tip may be directly input using the key K1 instead of being specified as a ratio to the payment amount. The amount of the tip may be set to a fixed amount regardless of the payment amount, or may be uniformly determined as a certain percentage of the payment amount.

When the state of the slide switch S3 is set to "Pay a tip," the payment application 20 sends a tip acceptance inquiry, including the store ID, to the payment server 100 (S25).

The remittance processing unit 140 of the payment server 100 refers to the store information 174 and checks whether the tip acceptance setting information of the affiliated store ID (store ID if set for each store) corresponding to the store related to the store ID is set to "acceptable" (S26), and transmits information responding to the confirmation result to the payment application 20 (S27). If the confirmation result is "not accepted", the payment application 20 displays information indicating that the tip payment was not realized (the tip was not accepted) on the user terminal device 10.

If the answer to the question about whether or not a tip can be received is "yes," the payment application 20 generates payment information including the account ID, payment amount, tip amount, and store ID; otherwise, it generates payment information including the account ID, payment amount, and store ID (S28) and transmits the payment information to the payment server 100 (S29).

In the payment server 100, the payment processing unit 130 performs payment processing (S30), and if the payment information includes the amount of the tip, the remittance processing unit 140 transfers the amount equivalent to the tip from the charge balance of the user related to the account ID to the remittance balance in the store wallet information of the store related to the store ID (S31). Then, a payment completion notice is sent from the payment server 100 to the payment application 20 (S32).

In this way, in pattern 2, by accepting input operations related to tip payment after reading the store's code image, tip payment can be conveniently performed within the flow of electronic payment at a physical store. Also, within the series of processing flows, processing related to affiliated stores or stores that do not accept tips can be performed seamlessly.

In pattern 2, instead of (or in addition to) accepting input operations related to tip payment after scanning the store's code image, the tip may be automatically paid based on the tip payment settings 172A accepted asynchronously with the electronic payment. In this case, instead of the acceptance screen IM3 for accepting tip transfer instructions, a tip setting display screen IM4 (which is also a payment instruction screen) is displayed. FIG. 12 is a diagram showing an example of the tip setting display screen IM4. On the tip setting display screen IM4, area A13 displays the tip settings for the affiliated store with which electronic payment is about to be made. In this case, the slide switch S3 may be set in the same way as in FIG. 11. This eliminates the need for the user to perform the tip payment operation every time electronic payment is made.

In addition, in pattern 2, it was assumed that confirmation as to whether or not the tip acceptance setting information of the affiliated store ID (store ID if set for each store) corresponding to the store related to the store ID is set to "accepted" is performed before the electronic payment, but this processing may be performed together with the electronic payment, and the user may be notified of whether or not the tip has been accepted on the payment completion notification screen. In this case, the processing of S25 and S26 in the flowchart of FIG. 10 may be omitted, and the payment server 100 may perform the electronic payment and at the same time, refer to the affiliated store's tip acceptance setting shown in the payment information to determine whether or not to pay a tip.

In addition, in pattern 1, when the payment server 100 transmits a one-time code to the user terminal device 10 and the payment application 20 causes the user terminal device 10 to display a code image (second code image) based on the one-time code (S4 in FIG. 7 and subsequent processing), the payment server 100 may transmit information related to tip payment settings 172A together with the one-time code to the user terminal device 10, and the user terminal device 10 may display information related to tip payment settings 172A together with the second code image. FIG. 13 is a diagram showing an example of a payment screen IM5 including the second code image. In the payment screen IM5, the second code image is displayed in area A21, and information related to tip payment settings 172A is displayed in area A22. This allows the user to check the current tip payment settings before making a payment even in the case of pattern 1.

In the above embodiment, the option to accept or reject tips is set for each affiliated store (or each store), but this can be omitted and all stores can accept tips.

[Transferring the amount equivalent to tips to employees]
The remittance processing unit 140 may perform a process of remitting the amount paid to the affiliated store as a tip to the employee's personal account. This process is performed asynchronously with the electronic settlement and the payment of tips, for example, once a month or once a week. In response to a request from the affiliated store or store, the remittance processing unit 140 performs a process of remittance from the remittance balance in the store wallet information of the store information 174 to the charge balance in the employee's user information 172. The remittance processing unit 140 may automatically perform remittance processing according to a rule such as "transmit a predetermined percentage of the increase in the remittance balance due to tips in the current month to the employee's personal account."

According to the embodiment described above, the payment of the reward (tip) can be conveniently performed within the flow of electronic payment at a physical store.

The above describes the form for carrying out the present invention using an embodiment, but the present invention is not limited to such an embodiment, and various modifications and substitutions can be made without departing from the spirit of the present invention.

REFERENCE SIGNS LIST 10 User terminal device 20 Payment application 50 Shop terminal device 60 Shop code image 100 Payment server 110 Communication unit 120 Payment content providing unit 130 Payment processing unit 140 Remittance processing unit 170 Storage unit 172 User information 174 Shop information 176 Payment content information

Claims (10)

an application program that runs on a user terminal device;
A payment service providing device that cooperates with the application program to allow a user to make an electronic payment at a physical store belonging to an affiliated store;
A payment system comprising:
The application program is installed in the user terminal device.
Accepting an operation for the electronic payment performed by the user and accepting an instruction to remit a reward to the affiliated store related to the electronic payment;
The payment service providing device,
a payment processing unit that processes the electronic payment based on payment information acquired from the user terminal device;
a remittance processing unit that performs processing for remittance of the reward money from the user's account to the affiliated store's account in accordance with the content of the remittance instruction received by the application program,
the remittance processing unit stores setting information in a storage unit, the setting information indicating whether or not the reward money is to be received for each of the plurality of affiliated stores, and performs processing for remittance of the reward money from the user's account to the affiliated store's account based on the content of the remittance instruction and the setting information;
Payment system. The remittance processing unit, as a process for remittance of the reward money, subtracts the amount of the reward money from the charge balance of the user and adds it to a remittance balance different from the settlement balance of the affiliated store, or performs a process for settling the amount of the reward money at a later date and adds it to a remittance balance different from the settlement balance of the affiliated store.
The payment system according to claim 1. The application program is installed in the user terminal device.
After scanning the first code image presented by the brick-and-mortar store to obtain store-related information, an input of a payment amount by the user is accepted, and an input of the remittance instruction by the user is accepted;
transmitting the store-related information, the payment amount, and the remittance instruction to the payment service providing device;
the payment processing unit of the payment service providing device performs processing for the electronic payment based on the payment information acquired from the user terminal device,
the remittance processing unit of the payment service providing device performs processing for remittance of the reward money from the account of the user to the account of the affiliated store in accordance with the content of the remittance instruction acquired from the user terminal device;
3. A payment system according to claim 1 or 2. The application program is installed in the user terminal device.
After the store-related information is acquired by scanning a first code image presented by the brick-and-mortar store, the store-related information is acquired by communicating with the payment service providing device, and the setting information of the affiliated store related to the store-related information is acquired;
When the input of the remittance instruction by the user is accepted, if the affiliated store related to the store-related information is set to not accept the reward money, information indicating that the reward money cannot be accepted is displayed.
The payment system according to claim 3. The application program is installed in the user terminal device.
Accepting a remittance setting of a reward money to the physical store of the affiliated store related to the electronic payment made by the user, and transmitting the remittance setting to the payment service providing device;
After scanning a first code image presented by the physical store to obtain store-related information, an input of a payment amount by the user is accepted;
transmitting the store-related information and the payment amount to the payment service providing device;
the payment processing unit of the payment service providing device performs processing for the electronic payment based on the payment information acquired from the user terminal device,
A payment system as described in claim 1 or 2, wherein the remittance processing unit of the payment service providing device performs processing to remit the reward money from the user's account to the affiliated store's account in accordance with the contents of the remittance settings previously received from the user terminal device. the application program causes the user terminal device to display an interface screen on which a user can switch whether or not to instruct remittance of the reward money by a predetermined operation, and accepts input of the remittance instruction by the user based on the operation performed on the interface screen.
3. A payment system according to claim 1 or 2. the interface screen accepts an operation for designating a ratio of the reward to a payment amount;
The payment system according to claim 6. A payment method executed by a payment system including an application program that runs on a user terminal device, and a payment service providing device that cooperates with the application program to allow a user to make an electronic payment at a physical store belonging to an affiliated store, the payment method comprising:
The application program is installed in the user terminal device.
Accepting an operation for the electronic payment performed by the user and accepting an instruction to remit a reward to the affiliated store related to the electronic payment;
The payment service providing device,
performing processing for the electronic payment based on the payment information acquired from the user terminal device;
storing setting information indicating whether or not the reward money is to be received for each of the plurality of affiliated stores in a storage unit, and performing a process for transferring the reward money from the user's account to the affiliated store's account based on the contents of the remittance instruction received by the application program and the setting information;
Payment Method. A payment service providing device that cooperates with an application program running on a user terminal device to allow a user to make an electronic payment at a physical store belonging to an affiliated store,
a payment processing unit that processes the electronic payment based on payment information acquired from the user terminal device;
a remittance processing unit that receives an operation for the electronic payment from the user by the application program and performs processing for remittance of the reward money from the user's account to the affiliated store's account in accordance with the content of the received remittance instruction;
Equipped with
the remittance processing unit stores setting information in a storage unit, the setting information indicating whether or not the reward money is to be received for each of the plurality of affiliated stores, and performs processing for remittance of the reward money from the user's account to the affiliated store's account based on the content of the remittance instruction and the setting information;
A payment service providing device. A processor of a payment service providing device that cooperates with an application program running on a user terminal device to allow a user to make an electronic payment at a brick-and-mortar store belonging to an affiliated store,
performing processing for the electronic payment based on the payment information acquired from the user terminal device;
the application program receives an operation for the electronic payment from the user, and performs a process for transferring the reward money from the user's account to the account of the affiliated store related to the electronic payment in accordance with the contents of the received remittance instruction and setting information indicating whether or not to receive a reward money for each of the plurality of affiliated stores, which is stored in advance in a storage unit;
program.

Images