Application program and server device

Abstract

To reduce costs for a store while improving convenience to staff of the store.SOLUTION: An application program runs on a store terminal device installed in a store participating in an electronic payment service, and executes processes related to the electronic payment service in collaboration with a server device providing the electronic payment service. The application program enables the store terminal device, in response to inputs to the store terminal device, to activate payment through contactless communications with a credit card of a user of the electronic payment service.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an application program and a server device. [Background technology]

[0002] Conventionally, there are known techniques for processing multiple payment methods in electronic payment services. For example, Patent Document 1 discloses a technique for distributing payment processing requests to each server using an electronic money payment terminal, a credit card reading terminal, and a POS terminal installed in a store. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2020-009199 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the past, a store that accepted multiple payment methods needed to install dedicated terminals for each payment method, and store staff had to use different dedicated terminals depending on the payment method desired by the customer. As a result, the cost for the store increased and the convenience for the store staff was reduced.

[0005] The present invention has been made in consideration of the above circumstances, and one of its objects is to provide an application program and a server device that can reduce costs for a store and improve convenience for the store's staff. [Means for solving the problem]

[0006] One aspect of the present invention is an application program that operates on a store terminal device installed in a store affiliated with an electronic payment service and executes processing related to the electronic payment service in cooperation with a server device that provides the electronic payment service, the application program causing the store terminal device to enable payment via contactless communication with a credit card of a user of the electronic payment service in response to input to the store terminal device. Effect of the Invention

[0007] According to one aspect of the present invention, it is possible to provide an application program and a server device that can reduce costs for a store and improve convenience for store staff at the store. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram showing an example of a configuration for realizing an electronic payment service. [Diagram 2] This is a sequence diagram (part 1) illustrating the general flow of electronic payment. [Diagram 3] This is a sequence diagram (part 2) illustrating the general flow of electronic payment. [Figure 4] FIG. 2 is a configuration diagram of a payment server 100 according to the embodiment. [Diagram 5] FIG. 13 is a diagram showing an example of the contents of user information 172. [Figure 6] FIG. 13 is a diagram showing an example of the contents of affiliated store / store information 176. [Figure 7] 10 is a diagram showing an example of the operation of an application program 72 installed in a second store terminal device 70. FIG. [Figure 8] FIG. 13 is a diagram showing an example of a screen displayed when the payment server 100 permits contactless payment by credit card. [Figure 9] FIG. 13 is a diagram showing an example of a screen displayed when the payment server 100 does not permit contactless payment by credit card. [Figure 10]FIG. 13 is a diagram illustrating contactless payment by credit card via a second store terminal device 70. [Figure 11] FIG. 13 is a diagram illustrating a data flow pattern when contactless payment is made with a credit card via a second store terminal device 70. [Figure 12] 13 is a diagram showing an example of a payment history displayed by a second store terminal device 70. FIG. [Figure 13] 10 is a sequence diagram showing an example of a flow of processes executed by a second store terminal device 70 and a payment server 100. FIG. [Figure 14] FIG. 2 is a diagram showing an example of a process executed by the payment server 100. [Figure 15] FIG. 13 is a diagram showing an example of the operation of an application program 72 installed in a second store terminal device 70 according to a modified example. [Figure 16] FIG. 13 is a diagram showing an example of a screen displayed by an application program 72 installed in a second store terminal device 70 according to a modified example. [Figure 17] FIG. 13 is a diagram illustrating contactless payment by credit card via a second store terminal device 70 according to a modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, an embodiment of the application program and the server device of the present invention will be described with reference to the drawings. An application program installed in a store terminal device, a server device (hereinafter referred to as a "payment server"), and a payment application installed in a user terminal device cooperate to provide an electronic payment service. The electronic payment service is a service that supports payments related to the purchase of goods and services at a store. The store is, for example, a physical store (real store) existing in real space, but may also include a virtual store of electronic commerce. The virtual store may include one provided by an entity different from the operator of the electronic payment service. In that case, when making a payment for shopping at the virtual store, the screen is controlled to transition to an interface screen of the electronic payment service. In the electronic payment service, the store is treated as belonging to, for example, an affiliated store (brand), and processing such as payment when a purchase is made at the store is mainly performed between the user and the affiliated store. Alternatively, processing such as payment may be performed between the user and the store.

[0010] [Electronic payment service] Fig. 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, one or more first store terminal devices 50, and one or more second store terminal devices 70 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.

[0011] 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 reception function, and a program execution function. In the following description, components for realizing these functions are referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), etc. In the user terminal device 10, a processor such as a CPU executes a payment application 20, thereby operating to provide an electronic payment service to a user in cooperation with a payment server 100. The payment application 20 is installed in the user terminal device 10 from, for example, an application store, and controls the camera, communication device, touch panel, etc.

[0012] The first store terminal device 50 is installed, for example, in a store. The first 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 first 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 by the second store terminal device 70, as described later.

[0013] The second store terminal device 70 is used by the operator of the affiliated store. The second store terminal device 70 is a smartphone, a tablet terminal, a personal computer, or the like, and has an NFC (near field communication) function. An application program 72 runs on the second store terminal device 70. The application program 72 may be an application for affiliated stores, or may be a browser. The application program 72 accepts the payment method and coupon settings, etc., from the operator of the affiliated store, and transmits them to the payment server 100. The second store terminal device 70, which is a smartphone or a tablet terminal, has a function of downloading and installing the application program 72 from the payment server 100, and executing the installed application program 72 to display a code image corresponding to a store code image and read the code image displayed by the user terminal device 10. Furthermore, as described later, the second store terminal device 70 enables contactless payment with a credit card held by a user when the affiliated store supports deferred payment. Here, the credit card may be, for example, a physical card made of plastic or the like with a credit payment function implemented, or a terminal device such as a smartphone with a credit payment function implemented as a digital card.

[0014] The payment server 100 realizes electronic payment based on payment information received from the user terminal device 10 or the first store terminal device 50. The first store terminal device 50 may include a POS device and an affiliated store server, in which case the payment information is sent from the POS device via the affiliated store server to the payment server 100. In the following explanation, no distinction is made between these two and it is assumed that the payment information is sent from the first store terminal device 50.

[0015] 2 and 3 are sequence diagrams illustrating the general flow of electronic payment. There may be two patterns of electronic payment: pattern 1 and pattern 2.

[0016] In the case of pattern 1 (hereinafter referred to as user scan) shown in FIG. 2, the user terminal device 10 with the payment application 20 activated decodes the store code image 60 by the optical reading function (S1). The store code image 60 includes store URL (Uniform Resource Locator) information. This store URL is an electronic payment service domain to which store-identifying information is added, and is associated with an affiliated store ID, a store ID, etc. in the payment server 100 (described later). The payment application 20 transmits the first payment information including the store URL and the account ID to the payment server 100 (S2). The payment server 100 searches for store information (described later) from the affiliated store ID and the store ID corresponding to the store URL, acquires the affiliated store name and the store name information (S3), and transmits it to the payment application 20 (S4). The user inputs the payment amount into the user terminal device 10 on the screen on which the affiliated store name and the store name are displayed (S5). Then, the user terminal device 10 generates second payment information including at least the payment amount, and transmits it to the payment server 100 (S6). The payment server 100 performs electronic payment based on the received second payment information (S7). The payment server 100 then transmits a payment completion notice (information for displaying a payment completion screen) to the payment application 20 (S8), and the payment application 20 displays the payment completion screen (S9). Note that when the store code image 60 is displayed on a display installed in the store, the store code image 60 may include not only the store URL but also information on the payment amount. In this case, the step of the user inputting the payment amount is omitted, and the information on the payment amount is included in the first payment information and transmitted to the payment server 100. Information on the affiliated store name and the store name may be included in the payment completion screen and displayed.

[0017] In the case of pattern 2 (hereinafter referred to as store scan) shown in FIG. 3, when the payment application 20 is started, when a payment operation is performed in the payment application 20, when an automatic update timing (e.g., every minute) occurs, and at other timings, the payment application 20 transmits a request for issuing a one-time code to the payment server 100 (S11). The payment server 100 generates a one-time code (S12) and transmits it to the payment application 20 (S13). The payment application 20 displays a code image such as a QR code or a barcode generated based on the one-time code (S14). The user holds (presents) the display surface of the user terminal device 10 over the first store terminal device 50, and the first store terminal device 50 decodes the code image by an optical reading function and obtains the one-time code, etc. (S15). The first store terminal device 50 then generates payment information including the one-time code, payment amount, affiliated store ID, store ID, etc., and transmits it to the payment server 100 (S16). The payment amount information is acquired in advance by reading a barcode or manually entering it. The payment server 100 identifies the user corresponding to the one-time code based on the received information and performs electronic payment (S17). The payment server 100 then transmits a payment completion notice to the payment application 20 (S18), and the payment application 20 displays a payment completion screen (S19).

[0018] Note that electronic payment may be performed using only one of the above patterns. Furthermore, the "account ID" described in FIG. 2 may be other information (e.g., a phone number) that can be used as user identification information. Furthermore, issuance of a one-time code may be omitted in the store scan, and the payment application 20 may display a code image generated based on the user's account ID. In this case, the payment server 100 identifies the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[0019] [Payment server] FIG. 4 is a configuration diagram of the payment server 100 according to the embodiment. The payment server 100 includes, for example, a communication unit 110, a payment content providing unit 120, a payment processing unit 130, an information management 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 (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.

[0020] 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, payment content information 174, and affiliated store / shop information 176.

[0021] 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.

[0022] The payment content providing unit 120 has, for example, a function of a Web server, and provides information (content) for displaying various screens of the electronic payment service to the user terminal device 10. The payment content providing unit 120 appropriately reads necessary content from the payment content information 174 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.

[0023] The payment processing unit 130 performs payment processing based on the payment information transmitted by the user terminal device 10 or the first store terminal device 50. The payment processing unit 130 performs payment processing while referring to the user information 172.

[0024] FIG. 5 is a diagram showing an example of the contents of the user information 172. The user information 172 is an example of the registration information of a user. The user information 172 is, for example, a user URL, an account ID, a telephone number, a password, as well as information associated with an email address, a user ID, a name, an address, a date of birth, a registration date, a charge balance, a post-payment setting, a post-payment limit, a post-payment usage amount, a post-payment available amount, a payment method setting, a bank account, a credit card number, a charge history information, and a payment history information. The user URL is used for a remittance process between users. When registering for the electronic payment service, it is necessary to register a telephone number and a password. The account ID is issued to the user by the payment server 100, and the user ID is an ID that can be set by the user at will (does not have to be set). Similarly, the email address, and the name, address, and date of birth are information that can be set by the user at will (does not have to be set). The registration date is the date on which the user registered for the electronic payment service (the date on which the account was created). Hereinafter, the user's instance (electronic payment account) to which this information is associated will be referred to as an account.

[0025] The charge balance is information indicating the balance of electronic money that is set by a user by transferring money to an 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. Further details of deferred payment will be described later. The payment method setting is setting information indicating whether the user will perform electronic payment using the charge balance or payment by deferred payment at that time. 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. Charge history information is a history of the user's previous transfers to the electronic payment service to increase the charge balance. Payment history information is information that indicates 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, payment method, etc.).

[0026] FIG. 6 is a diagram showing an example of the contents of the affiliated store / store information 176. The affiliated store / store information 176 includes, for example, a first table 176A in which an affiliated store ID and a store ID are associated with a store URL, a second table 176B in which an affiliated store name, sales amount (described above), deferred payment registration, and contactless payment registration are associated with an affiliated store ID, and a third table 176C in which a store name is associated with a store ID. In addition to the above information, the affiliated store / store information 176 may also include information such as the category of the affiliated store or store, the location of the store, and payment patterns. The deferred payment registration is information indicating whether or not the affiliated store has been registered for deferred electronic payment. If the deferred payment registration is "registered," deferred payment can be used at the store operated by the affiliated store, whereas if the deferred payment registration is "not registered," deferred payment cannot be used at the store operated by the affiliated store. The fact that the deferred payment registration is "completed" means that the affiliated store has been certified by the electronic payment service as a business that handles installment transactions (for example, it has been confirmed that the store meets the legal standards related to installment transactions). Prior to introducing deferred payment to the store, the affiliated store uses the second store terminal device 70 to apply for deferred payment in advance to the payment server 100, and when the screening officer of the electronic payment service approves the application, the deferred payment registration is recorded as "completed" in the second table 176B. The contactless payment registration is information that indicates whether the affiliated store has been registered for contactless payment by credit card. If the contactless payment registration is "completed," the use of contactless payment by credit card is possible in the store operated by the affiliated store, whereas if the deferred payment registration is "not completed," the use of contactless payment by credit card is not possible in the store operated by the affiliated store.

[0027] The information management unit 140 manages user information 172 and affiliated store / store information 176 based on information acquired from the user terminal device 10 and the second store terminal device 70. The information management unit 140 adds new records to, edits, and deletes the user information 172 and affiliated store / store information 176.

[0028] [Electronic payment] 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.

[0029] 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 a 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, a credit card provided by the operator of the electronic payment service may be required. 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. In this case, the payment processing unit 130 performs provisional payment by adding the payment 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, or requests the operator of the credit card company to perform such processing. In addition, if the payment amount exceeds the available deferred payment amount at the time of provisional payment, an error notification is returned to the payment application 20.

[0030] [Application Program] Hereinafter, the operation of the application program 72 installed in the second store terminal device 70 will be described in detail with reference to Figures 7 to 9. Figure 7 is a diagram showing an example of a screen displayed by the application program 72 installed in the second store terminal device 70. Figure 7 shows a screen displayed when, for example, a store clerk at a physical store starts the application program 72 of the second store terminal device 70 to make an electronic payment.

[0031] As shown in FIG. 7, the application program 72 displays, for example, an item for selecting user scan as a payment method and an item for selecting contactless credit card payment on the screen of the second store terminal device 70. When a store clerk at the physical store presses the print button B1 on the screen shown in FIG. 7, the application program 72 causes the second store terminal device 70 to transmit a print instruction for a code image CI to be used for the user scan to a printer device (not shown) installed in the physical store, and the printer device that receives the print instruction prints the code image CI. The store clerk at the physical store displays the printed code image CI as a store code image 60 at the storefront. On the other hand, when the store clerk at the physical store presses the display button B2, the application program 72 causes the second store terminal device 70 to display the entire code image CI, and the user performs a user scan using the user terminal device 10.

[0032] On the other hand, when a clerk at a physical store presses the application button B3, the application program 72 causes the second store terminal device 70 to transmit information for applying for the use of contactless payment by credit card together with the affiliated store ID to the payment server 100. When the information management unit 140 of the payment server 100 receives the application information, it refers to the second table 176B using the affiliated store ID as a key and determines whether the deferred payment registration corresponding to the affiliated store ID is "completed". If it is determined that the deferred payment registration is "completed", the information management unit 140 changes the setting of the contactless payment registration corresponding to the affiliated store from "not completed" to "completed" and enables (activates) the use of contactless payment by credit card in the second store terminal device 70. On the other hand, if it is determined that the deferred payment registration is "not completed", the information management unit 140 does not enable the use of contactless payment by credit card in the second store terminal device 70. This is because, as described above, a deferred payment registration being "completed" means that the affiliated store has been authenticated as a business that handles installment transactions, and therefore there is no need to perform another examination to enable the use of contactless payment by credit card. In this way, whether or not to enable the use of contactless payment by credit card is determined based on whether or not the affiliated store has been registered for deferred payment, and if the affiliated store has been registered for deferred payment, the use of contactless payment by credit card is quickly enabled, thereby increasing convenience for the affiliated store and reducing the burden on the examiner of the electronic payment service.

[0033] FIG. 8 is a diagram showing an example of a screen displayed when the contactless payment by credit card is enabled by the payment server 100. As shown in FIG. 8, when the application program 72 receives a notification from the payment server 100 that the use of the contactless payment by credit card is enabled, the application program 72, for example, causes the second store terminal device 70 to display a payment button B4 for executing the contactless payment by credit card. When a store clerk at the actual store presses the payment button B4, the process proceeds to the process shown in FIG. 10, which will be described later. Once the use of the contactless payment by credit card is enabled by the information management unit 140, the application program 72 causes the second store terminal device 70 to display the payment button B4 thereafter without displaying the application button B3 again.

[0034] Fig. 9 is a diagram showing an example of a screen displayed when contactless payment by credit card is not enabled by the payment server 100. As shown in Fig. 9, when a notification that the use of contactless payment by credit card is not enabled is received from the payment server 100, the application program 72, for example, causes the second store terminal device 70 to display a notification that it is under review as to whether or not to enable contactless payment by credit card for the affiliated store (in Fig. 9, as an example, an inactive (unselectable) button is displayed). At this time, the payment server 100 transmits, for example, to the terminal device of the administrator of the payment server 100 a notification that the affiliated store wishes to use contactless payment by credit card, and the administrator examines whether or not to enable the use of contactless payment by credit card for the affiliated store.

[0035] Since permitting the affiliated store to use contactless payment by credit card is synonymous with permitting the affiliated store to use deferred payment, the payment server 100 may inquire again of the second store terminal device 70 as to whether or not to register the use of deferred payment before proceeding to the examination. In this case, when the payment server 100 receives a notification from the second store terminal device 70 that the use of deferred payment will be registered, the administrator may examine whether or not to permit the affiliated store to use deferred payment and contactless payment by credit card.

[0036] Note that Figures 8 and 9 have described, as an example, a case in which the application program 72 enables user scanning and contactless credit card payment in the second store terminal device 70, but in addition to this, the application program 72 may cause the second store terminal device 70 to execute the store scanning function shown in Figure 3.

[0037] FIG. 10 is a diagram for explaining contactless payment by credit card via the second store terminal device 70. The screen shown in FIG. 10 is transitioned when, for example, a store clerk at a real store presses the payment button B4 shown at the bottom of FIG. 8. As shown in FIG. 10, the application program 72 causes, for example, the second store terminal device 70 to display a guide message to perform credit card payment by holding a credit card over the terminal. When a user holds a credit card CD over the second store terminal device 70, the credit card CD and the second store terminal device 70 perform short-range wireless communication to perform credit card payment contactlessly. Although not shown in FIG. 10, the application program 72 causes the second store terminal device 70 to display an input form for inputting the payment amount, and after the store clerk at the real store inputs the payment amount into the input form, the screen transitions to the screen shown in FIG. 10 and performs credit card payment.

[0038] Thus, according to this embodiment, a member store of an electronic payment service downloads and installs the application program 72 on a single second store terminal device 70 such as a smartphone or tablet terminal to activate code payment, and if the member store has registered for deferred payment, activates contactless payment by credit card on the second store terminal device 70 in response to a request from the member store. In other words, the member store does not need to prepare multiple payment devices according to multiple payment methods, and the store clerk does not need to operate multiple payment devices. This reduces the cost for the store and improves convenience for the store clerk.

[0039] FIG. 11 is a diagram for explaining a data flow pattern when a contactless payment is made by a credit card through the second store terminal device 70. FIG. 11(a) and FIG. 11(b) respectively show different patterns of data flow. In the pattern shown in FIG. 11(a), first, when a contactless payment is made by a credit card through the second store terminal device 70, the second store terminal device 70 transmits a payment message to the payment server 100, including information such as the identification information of the card company that issued the credit card used for the payment, the credit card number, the payment amount, and the payment date and time. The payment server 100 transmits the received payment message to the acquiring host 210 (which may be the same as the operator of the electronic payment service), which is a credit card on-behalf payment agent, and acquires information such as the identification information of the card company, the credit card number, the payment amount, and the payment date and time included in the payment message as payment data. The payment server 100 stores the acquired payment data in the storage unit 170 as payment history information, and notifies the second store terminal device 70 of the same. Meanwhile, the acquiring host 210 makes an advance payment of the payment amount based on the received payment message, and also transmits the payment message to the credit card brand or issuer.

[0040] In the pattern shown in FIG. 11(b), first, when a contactless payment is made by a credit card via the second store terminal device 70, the second store terminal device 70 transmits a payment message to the acquiring host 210, including information such as the identification information of the card company that issued the credit card used for the payment, the credit card number, the payment amount, and the payment date and time. The acquiring host 210 makes an advance payment of the payment amount based on the received payment message, and further transmits the payment message to the payment server 100. The payment server 100 further transmits the received payment message to the credit card brand and issuer, and acquires information included in the payment message, such as the identification information of the card company, the credit card number, the payment amount, and the payment date and time, as payment data. The payment server 100 stores the acquired payment data in the storage unit 170 as payment history information, and notifies the second store terminal device 70. Through such processing, a contactless payment is made by a credit card via the second store terminal device 70, and the payment data of the contactless payment can be stored in the payment server 100.

[0041] The application program 72 may cause the second store terminal device 70 to display payment history data for credit cards and non-credit cards (i.e., offline payments such as charge balance payments and code payments including deferred payments at the affiliated store's physical store, and online payments for products or services sold online by the affiliated store) based on the payment data of contactless payments stored by the payment server 100 or notified to the second store terminal device 70. FIG. 12 is a diagram showing an example of a payment history displayed by the second store terminal device 70. In FIG. 12, area A1 shows a summary of payments made at the affiliated store on the day, and area A2 shows details of each payment made at the affiliated store on the day.

[0042] As shown in area A1, the application program 72 may cause the second store terminal device 70 to display the total amount of electronic payments made at the affiliated store on the day, and, of the total amount, the amount of payment made by code payment and the amount of payment made by contactless credit card payment. Also, as shown in area A2, the application program 72 causes the second store terminal device 70 to display the payment ID, store ID, store name, date and time, amount, and type of electronic payments made at the affiliated store on the day. Here, type is information indicating which payment method was used to make the payment, such as charge balance payment, deferred payment, contactless credit card payment, and other payment methods using credit cards and non-credit cards. This allows the operator of the affiliated store to get a detailed understanding of which payment method users prefer at the store.

[0043] In Fig. 12, as an example, information regarding electronic payments at the store on the day is displayed. However, the present invention is not limited to such a configuration, and the application program 72 may cause the second store terminal device 70 to display a transaction summary and transaction details for any period, such as one week or one month. Furthermore, the types of payment methods displayed on the second store terminal device 70 may include information such as "store scan" and "user scan."

[0044] [Processing flow] Next, a flow of processing executed by the second store terminal device 70 and the payment server 100 will be described with reference to Fig. 13. Fig. 13 is a sequence diagram showing an example of the flow of processing executed by the second store terminal device 70 and the payment server 100.

[0045] First, the second store terminal device 70 downloads and installs the application program 72 from the payment server 100 (S21). Next, in response to pressing the application button B3 for contactless credit card payment, the second store terminal device 70 transmits application information for applying for use of contactless credit card payment to the payment server 100 (S22). Next, upon receiving the application information, the payment server 100 determines whether the affiliated store corresponding to the application information has been registered for deferred payment (S23).

[0046] If it is determined that the affiliated store corresponding to the application information is registered for postpaid payment, the payment server 100 transmits a notification to the second store terminal device 70 that the use of contactless credit card payment is permitted (S24). Next, the second store terminal device 70 executes contactless credit card payment in response to pressing of the payment button B4 and holding the credit card CD over the second store terminal device 70 (S25). Next, the second store terminal device 70 transmits a payment message to the payment server 100 in response to the execution of contactless credit card payment (S26).

[0047] Next, when the payment server 100 receives the payment message, it acquires the payment data from the received payment message and transmits it to the second store terminal device 70 (S27). Next, the second store terminal device 70 displays the received payment data (S28). This ends the processing of this sequence diagram.

[0048] In the sequence diagram of Fig. 13, the payment server 100 receives a payment message in S26, and the received payment message includes a credit card number. Therefore, the payment server 100 may refer to the user information 172 using the credit card number included in the received payment message as a key, and send notification information to the payment application 20 of the user linked to the credit card number that a contactless credit card payment has been made. This allows the user to receive notifications regarding both the code payment and the contactless credit card payment via the payment application 20, further improving convenience for the user.

[0049] Fig. 14 is a flowchart showing an example of the flow of processing executed by the payment server 100. The processing of the flowchart shown in Fig. 14 is executed when the payment server 100 receives a payment message in S26 of Fig. 13.

[0050] First, the payment server 100 acquires a payment message for contactless credit card payment from the second store terminal device 70 (S100). Next, the payment server 100 acquires the credit card number from the acquired payment message (S102). Next, the payment server 100 refers to the user information 172 using the acquired credit card number as a key, and determines whether the user information 172 has registered the credit card number (S104).

[0051] If it is determined that the user information 172 does not have a registered credit card number, the payment server 100 ends the process of this flowchart. On the other hand, if it is determined that the user information 172 has a registered credit card number, the payment server 100 transmits a contactless credit card payment completion notification to the user terminal device 10 of the user corresponding to the credit card number (S106). This ends the process of this flowchart.

[0052] According to the embodiment described above, the application program causes the store terminal device to execute both of the following: displaying code information encoded with identification information of the store or affiliated store, which is to be read by the user terminal device of the user who uses the electronic payment service to process the payment, and enabling payment by contactless communication with the user's credit card in response to input to the store terminal device. This reduces costs for the store and improves convenience for store clerks.

[0053] [Variations] In the above embodiment, an example has been described in which the second store terminal device 70 on which the application program 72 is installed is a tablet terminal, and the user makes an electronic payment using a credit card CD as a physical card. As described above, the second store terminal device 70 is not limited to a tablet terminal, and the credit card is not limited to a physical card. In this modified example, a case will be described in which the second store terminal device 70 is a smartphone, and the user makes an electronic payment using a credit card as a digital card installed in the user terminal device 10.

[0054] Fig. 15 is a diagram showing an example of the operation of the application program 72 installed in the second in-store terminal device 70 according to the modified example. The left part of Fig. 15 shows a top screen that is initially displayed when, for example, a store clerk in a real store starts up the application program 72 of the second in-store terminal device 70.

[0055] As shown in the left part of Fig. 15, for example, the application program 72 displays, on the top screen of the second store terminal device 70, an area A3 for displaying a summary of payments made at the affiliated store on that day, and a button B6 for making an electronic payment using the second store terminal device 70. When the user presses button B6, as shown in the right part of Fig. 15, the application program 72 displays, for example, on the screen of the second store terminal device 70, an item for selecting user scan as a payment method, an item for selecting store scan, and an item for selecting contactless credit card payment.

[0056] When a store clerk at the physical store presses the display button B7 on the screen shown in the right part of Fig. 15, the application program 72 causes the second store terminal device 70 to display the code image CI to be used for the user scan, and the user executes the user scan using the user terminal device 10. As in the case of Fig. 7, the application program 72 may also display the print button B1, and when a store clerk at the physical store presses the print button B1, cause the second store terminal device 70 to transmit a print instruction for the code image CI to be used for the user scan to a printer device installed in the physical store.

[0057] When a store clerk at a physical store presses the read button B8, the application program 72 causes the second store terminal device 70 to activate a scan function for reading the code image displayed by the user terminal device 10, and the second store terminal device 70 scans the code image, thereby executing the payment by store scan described above.

[0058] On the other hand, when a clerk at a physical store presses the application button B9, the application program 72 causes the second store terminal device 70 to transmit information for applying for the use of contactless payment by credit card together with the affiliated store ID to the payment server 100. When the information management unit 140 of the payment server 100 receives the application information, it refers to the second table 176B using the affiliated store ID as a key and determines whether the deferred payment registration corresponding to the affiliated store ID is "completed". If it is determined that the deferred payment registration is "completed", the information management unit 140 changes the setting of the contactless payment registration corresponding to the affiliated store from "not completed" to "completed" and enables (activates) the use of contactless payment by credit card in the second store terminal device 70. On the other hand, if it is determined that the deferred payment registration is "not completed", the information management unit 140 does not enable the use of contactless payment by credit card in the second store terminal device 70. When the information management unit 140 enables the second store terminal device 70 to use contactless payment by credit card, the application program 72 proceeds to the process shown in Fig. 17, which will be described later. Although not shown in Fig. 15, if it is determined that the deferred payment registration is "uncompleted," the application program 72 may cause the second store terminal device 70 to display a notice that the application is under review, as in the case of Fig. 9.

[0059] FIG. 16 is a diagram showing an example of a screen displayed by the application program 72 installed in the second store terminal device 70 according to the modified example. The screen shown in FIG. 16 is displayed, for example, when a store clerk at a physical store presses the receive button B6 on the top screen again after the use of contactless payment by credit card is enabled. In this case, unlike the right part of FIG. 15, the application program 72 causes the second store terminal device 70 to display the touch payment button B10 for executing contactless payment by credit card. When the store clerk at the physical store presses the touch payment button B10, the application program 72 proceeds to the process shown in FIG. 17, which will be described later.

[0060] Fig. 17 is a diagram for explaining contactless payment by credit card via the second store terminal device 70 according to the modified example. The flow of contactless payment by credit card shown in Fig. 17 is executed, for example, when the application button B9 is pressed in the scene shown in Fig. 15 to enable the use of contactless payment by credit card, or when the touch payment button B10 is pressed in the scene shown in Fig. 16. As shown in the left part of Fig. 17, the application program 72 causes the second store terminal device 70 to display, for example, an input form A4 for inputting the payment amount and a receive button B11 for transitioning to contactless payment.

[0061] When a store clerk at a physical store inputs the amount to be received and presses the receive button B11, the application program 72 causes the second store terminal device 70 to display a guide A5 to perform credit card payment by holding the credit card over the terminal, and also displays a transition button B12 for returning to the amount input screen. The user operates the user terminal device 10 to display a credit card as a digital card, and holds the credit card over the second store terminal device 70, so that the user terminal device 10 and the second store terminal device 70 perform short-range wireless communication and perform credit card payment contactlessly. When the credit card payment is completed, the application program 72 causes the second store terminal device 70 to display, for example, an area A6 showing the payment amount, an area A7 showing detailed information about the executed electronic payment, and a transition button 13 for returning to the top screen of FIG. 15. The detailed information about the electronic payment may include, in addition to the name of the store where the electronic payment was executed, the store ID, and the affiliated store ID, information that the payment method is a contactless credit card payment, and further information such as the brand name of the credit card.

[0062] According to the above-described modified example, the application program 72 can be operated not only on a tablet terminal, but also, for example, by installing it on a smartphone or the like carried by a salesperson at a physical store. This can reduce costs for the store and improve convenience for the salesperson at the store.

[0063] 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 within the scope that does not deviate from the gist of the present invention. [Explanation of symbols]

[0064] 10 User terminal device 20. Payment App 50 First store terminal device 60 Store Code Image 70 Second store terminal device 72 Application Programs 100 Payment Server 110 Communications Department 120 Payment Contents Provider 130 Payment processing unit 140 Information Management Department 170 Storage section

Claims

1. An application program that operates on a store terminal device, which is a general-purpose computer device with NFC (near-field communication) functionality, installed in a store participating in an electronic payment service, and which works in cooperation with a server device that provides the electronic payment service to execute processing related to the electronic payment service, A code image for processing payments by having a user terminal device of a user using the aforementioned electronic payment service read, the code image containing the identification information of the store or merchant, and an icon indicating the NFC function, to be displayed on the display unit of the store terminal device, Application program.

2. The screen further includes a reception area for receiving operations to enable contactless payment via NFC function with the user's credit card, The application program according to claim 1.

3. The screen further includes a reception area for receiving an operation to perform a payment via contactless communication with the user's credit card via NFC functionality. The application program according to claim 1.

4. The store terminal device is instructed to determine whether the store is registered for the deferred payment service of the electronic payment service in response to an operation on the reception area, and if it is determined that the store is registered for the deferred payment service of the electronic payment service, it is instructed to enable contactless payment via NFC function with the user's credit card. The application program according to claim 2.

5. The store terminal device, in response to an operation on the reception area, enables contactless payment via NFC with the user's credit card without performing a review to enable contactless payment via NFC with the user's credit card, The application program according to claim 2.

6. The store terminal device is configured to display together the payment history information processed by the user terminal device reading the code image and the payment history information processed by contactless communication via NFC function with the user's credit card. The application program according to claim 1.

Images