Settlement device and settlement method

Abstract

To accept specific settlement in a store even when the store permits a settlement method not requiring personal identification.SOLUTION: The processing device 31 includes a management unit 311, an acquisition unit 312, and a settlement unit 313. The management unit 311 manages the first identification information and the second identification information in association with the store. The store can support both the first payment method and the second payment method, and can support a specific payment. The acquiring unit 312 acquires a settlement request from the user terminal 10. The settlement request includes code information obtained by reading either the first code image IM1 or the second code image IM2 with the user terminal 10 of the user U. The payment unit 313 permits the first payment method and the second payment method when the first identification information is included in the payment request, and does not permit the first payment method and permits the second payment method when the second identification information is included in the payment request.SELECTED DRAWING: Figure 15

Description

[Technical Field]

[0001] The present invention relates to a payment device, a terminal device, and a payment method. [Background technology]

[0002] Electronic payment services include payment methods that require identity verification and payment methods that do not. For example, Patent Document 1 discloses a payment system in which a user registers a payment method and makes a payment using the payment method registered in the automatic payment system by presenting or touching a payment device that has recorded access information to a payment method registration server to a counterpart terminal. [Prior art documents] [Patent documents]

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

[0004] Since identity verification is required when making certain payments related to donations, donations, and other gifts, when making certain payments using an electronic payment service, a payment method that requires identity verification must be selected. However, stores that offer electronic payment services often accept payment methods that do not require identity verification. For example, the payment system disclosed in Patent Document 1 had a problem in that if a store accepted a payment method that did not require identity verification, the store would not be able to accept certain payments.

[0005] The present invention has been made to solve the above-mentioned problems, and aims to enable a store to accept specific payments even if the store allows a payment method that does not require identity verification. [Means for solving the problem]

[0006] A preferred embodiment of the present invention provides a payment device that is compatible with both a first payment method that does not require identity verification and a second payment method that does require identity verification, and includes: a management unit that manages first identification information that identifies the store and second identification information that identifies the store, associating them with stores that can handle specific payments; an acquisition unit that acquires from the user's terminal device a payment request that includes code information obtained by reading, with the user's terminal device, either a first code image that is presented to the user at the store and that includes the first identification information, or a second code image that is used for the specific payment and that includes the second identification information; and a payment unit that allows both the first payment method and the second payment method when the payment request includes the first identification information, but does not allow the first payment method and allows the second payment method when the payment request includes the second identification information.

[0007] A preferred embodiment of the present invention provides a payment method that is compatible with both a first payment method that does not require identity verification and a second payment method that does require identity verification, and manages first identification information that identifies the store and second identification information that identifies the store, by associating them with a store that can handle a specific payment. The method obtains a payment request from the user's terminal device, the payment request including code information obtained by reading, with the user's terminal device, either a first code image that is presented to the user at the store and is used for general payments and includes the first identification information, or a second code image that is used for the specific payment and includes the second identification information. If the payment request includes the first identification information, the method executes a payment that accepts both the first payment method and the second payment method. If the payment request includes the second identification information, the method does not accept the first payment method and executes a payment that accepts the second payment method. [Effects of the Invention]

[0008] According to the payment device and payment method of the present invention, even if a store allows a payment method that does not require identity verification, donations can be accepted at the store. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram showing the overall configuration of an electronic payment system including a payment device according to a first embodiment. [Figure 2] 2 is a block diagram showing an example of the configuration of a user terminal device in FIG. 1. FIG. [Figure 3] 2 is a block diagram showing an example of the configuration of the in-store device of FIG. 1. FIG. [Figure 4] 2 is a block diagram showing an example of the configuration of the payment server of FIG. 1. FIG. [Figure 5] 10 is a diagram showing an example of the relationship between the payment acceptance status by the payment unit and type information and identification information. FIG. [Figure 6] 10 is an example of a first code image displayed on a display device of a store device. [Figure 7] 10 is an example of a second code image displayed on a display device of a store device. [Figure 8] FIG. 10 is a diagram illustrating an example of a reading screen of an application program when the application program is started. [Figure 9] FIG. 10 is a diagram showing an example of a screen that is displayed after a two-dimensional code is read on the reading screen and into which the user inputs a payment amount. [Figure 10] FIG. 10 is a diagram showing an example of a screen for confirming payment details. [Figure 11] FIG. 10 is a diagram showing an example of a screen for changing a payment method. [Figure 12] FIG. 10 is a diagram showing an example of a payment confirmation screen displayed after the payment method is changed. [Figure 13] FIG. 10 is a diagram showing an example of a payment completion screen displayed after payment is completed. [Figure 14] 2 is a sequence chart showing a first operation of the electronic payment system of FIG. 1; [Figure 15] 10 is a sequence chart showing a second operation of the electronic payment system of FIG. DETAILED DESCRIPTION OF THE INVENTION

[0010] 1. First embodiment The configuration of the payment device according to the first embodiment of the present invention will be described below with reference to FIGS.

[0011] 1.1. Configuration of the First Embodiment 1.1.1. Overall structure Figure 1 is a diagram showing the overall configuration of an electronic payment system 1 including a payment device according to the first embodiment. The electronic payment system 1 includes a user terminal device 10, a store device 20, a payment server 30, and a communication network NET. Although Figure 1 illustrates one user terminal device 10 and one store device 20, this number is merely an example, and the electronic payment system 1 can include any number of user terminal devices 10 and any number of store devices 20.

[0012] A user U possesses a user terminal device 10. The user U uses the user terminal device 10 to use the electronic payment service provided by the electronic payment system 1. A store clerk C is a store clerk at a store that has an in-store device 20. The store clerk C provides the user U with the electronic payment service by operating the in-store device 20.

[0013] The user terminal device 10 includes a personal computer, a tablet terminal, a smartphone, a smart watch, and the like.

[0014] The in-store device 20 is a device installed in a store where code payment is available. The in-store device 20 includes a POS register, a personal computer, a tablet terminal, a smartphone, and the like.

[0015] The payment server 30 is a server managed by a service provider. An example of a service provider is a code payment provider. In this embodiment, an example will be described in which the payment server 30 is a server managed by a code payment provider. In other words, in this embodiment, a code payment service is provided by the payment server 30.

[0016] The payment server 30 performs identity authentication of code payment users, code management, transaction management, etc. More specifically, identity authentication of code payment users includes basic authentication and authentication at the time of use. Basic authentication is authentication performed for the purpose of limiting users, including user U, when they use code payment for the first time. Basic authentication manages the link between the user's terminal device and the "code payment app."

[0017] Authentication at the time of use is performed to verify whether the person attempting to make a code payment is the same as the user registered in advance. Examples include entering a PIN (Personal Identification Number), fingerprint authentication, or facial authentication.

[0018] The "code payment app" is an application that uses a two-dimensional code such as a QR code (registered trademark) to make payments for goods, services, etc. In this embodiment, the use of a merchant-presented mode (MPM) is particularly assumed. In the merchant-presented mode code payment, a QR code (registered trademark) posted in a store is scanned using a user terminal device 10, and the amount of payment is input by the user U. The scanned store information, input amount information, user information read from the user terminal device 10, etc. are transmitted from the user terminal device 10 to the payment server 30. The store information includes an ID unique to the store, the store name, the store location, etc.

[0019] The store-presented payment method includes static code payment using a static QR code (registered trademark) and dynamic code payment using a dynamic QR code (registered trademark). In static code payment, a static QR code (registered trademark) that is pre-printed and installed in the store is read by the user terminal device 10. In dynamic code payment, a dynamic QR code (registered trademark) displayed on the store device 20 is read by the user terminal device 10. In dynamic code payment, a different code is generated for each payment, making dynamic code payment more difficult to counterfeit than static code payment. In the first embodiment, dynamic code payment will be described as an example.

[0020] The communication network NET is a telecommunications line such as a mobile communication network managed by a telecommunications carrier that provides communication services. The communication network NET includes one or both of a wired communication network and a wireless communication network. For example, the communication network NET may be connected via the Internet to another network (not shown) managed by another telecommunications carrier.

[0021] In the electronic payment system 1, a user terminal device 10, a store device 20, and a payment server 30 are communicably connected to one another via a communication network NET. The electronic payment system 1 is a system that provides electronic payment services to any user who possesses a user terminal device 10. A user U is an example of a user.

[0022] 1.1.2. User terminal device configuration Fig. 2 is a block diagram showing an example of the configuration of the user terminal device 10 of Fig. 1. As shown in Fig. 2, the user terminal device 10 includes a processing device 11, a storage device 12, a communication device 13, a display device 14, an input device 15, and an imaging device 16. The elements included in the user terminal device 10 are connected to each other by one or more buses for communicating information. The user terminal device 10 is an example of a terminal.

[0023] The processing device 11 is a processor that controls the entire user terminal device 10, and is configured using, for example, one or more chips. The processing device 11 is configured using, for example, a central processing unit (CPU) including an interface with peripheral devices, an arithmetic unit, a register, etc. Note that some or all of the functions of the processing device 11 may be realized by hardware such as a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field Programmable Gate Array). The processing device 11 executes various processes in parallel or sequentially.

[0024] The storage device 12 is a recording medium that can be read and written by the processing device 11. The storage device 12 includes, for example, a nonvolatile memory and a volatile memory. The nonvolatile memory is, for example, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), and an electrically erasable programmable read-only memory (EEPROM). The volatile memory is, for example, a random access memory (RAM).

[0025] The storage device 12 stores a plurality of programs including a control program PR1 and an application program PRA to be executed by the processing device 11. The storage device 12 also functions as a work area for the processing device 11.

[0026] The control program PR1 is a program that controls the entire processing device 11. The application program PRA is a two-dimensional code payment application used for two-dimensional code payment. The two-dimensional code payment application is an application that uses a two-dimensional code such as a QR code (registered trademark) to pay for goods, services, etc. In this embodiment, a store-presented payment system is particularly assumed. The application program PRA is provided, for example, by a code payment business operator and pre-installed in the user terminal device 10 by the user U.

[0027] The communication device 13 is hardware serving as a transmitting / receiving device for communicating with other devices. The communication device 13 is also called, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 13 may include a connector for wired connection and an interface circuit corresponding to the connector. The communication device 13 may also include a wireless communication interface. Examples of the connector and interface circuit for wired connection include products that comply with wired LAN, IEEE1394, and USB. Examples of the wireless communication interface include products that comply with wireless LAN, Bluetooth (registered trademark), etc.

[0028] The display device 14 is a device that displays images and text information. The display device 14 displays various images under the control of the processing device 11. For example, various display panels such as a liquid crystal panel and an organic EL (Electro Luminescence) panel are suitably used as the display device 14.

[0029] The input device 15 receives operations from the user U. For example, the input device 15 includes a keyboard, a touchpad, a touch panel, and a pointing device such as a mouse. Here, if the input device 15 includes a touch panel, it may also serve as the display device 14.

[0030] The imaging device 16 outputs imaging information obtained by capturing an image of the external world. The imaging device 16 includes, for example, a lens, an imaging element, an amplifier, and an AD converter. Light collected through the lens is converted into an imaging signal, which is an analog signal, by the imaging element. The amplifier amplifies the imaging signal and outputs it to the AD converter. The AD converter converts the amplified imaging signal, which is an analog signal, into imaging information, which is a digital signal. The converted imaging information is output to the processing device 11.

[0031] The processing device 11 functions as a communication unit 111, a reading unit 112, a receiving unit 113, and a display control unit 114, for example, by reading and executing a control program PR1 from the storage device 12.

[0032] The communication unit 111 transmits a payment request to the payment server 30 via the communication device 13. The payment request includes, for example, type information indicating the type of payment method. Types of payment methods include payment by prepaid value, payment by cash value, and payment by credit card. The type of payment method is selected by the user U using the input device 15 at the time of payment. Note that the type of payment method may be set in advance by the user U.

[0033] The communication unit 111 receives a signal relating to the transaction result from the settlement server 30 via the communication device 13.

[0034] The reading unit 112 reads the two-dimensional code included in the imaging information captured by the imaging device 16. The reading unit 112 acquires code information obtained by reading the two-dimensional code. As will be described later, the two-dimensional code includes either a first code image or a second code image.

[0035] The reception unit 113 receives various operations by the user U on the application program PRA via the input device 15. For example, the reception unit 113 receives an operation to start the application program PRA by the user U. The reception unit 113 receives an operation to start the two-dimensional code reading function of the reading unit 112 via the input device 15. The reception unit 113 receives an operation to input an amount via the input device 15.

[0036] The display control unit 114 controls the display on the display device 14 based on various functions of the application program PRA.

[0037] 1.1.3. Store equipment configuration Fig. 3 is a block diagram showing an example configuration of the in-store device 20 in Fig. 1. As shown in Fig. 3, the in-store device 20 includes a processing device 21, a storage device 22, a communication device 23, a display device 24, and an input device 25. The elements included in the in-store device 20 are connected to each other by one or more buses for communicating information.

[0038] The processing device 21 is a processor that controls the entire in-store device 20, and is configured, for example, using one or more chips. The processing device 21 is configured, for example, using a central processing unit (CPU) that includes an interface with peripheral devices, an arithmetic unit, and a register. Note that some or all of the functions of the processing device 21 may be realized by hardware such as a DSP, ASIC, PLD, or FPGA. The processing device 21 executes various processes in parallel or sequentially.

[0039] The storage device 22 is a recording medium that can be read and written by the processing device 21. The storage device 22 includes, for example, a nonvolatile memory and a volatile memory. The nonvolatile memory is, for example, a ROM, an EPROM, and an EEPROM. The volatile memory is, for example, a RAM.

[0040] The storage device 22 stores a plurality of programs including a control program PR2 to be executed by the processing device 21. The storage device 22 also functions as a work area for the processing device 21.

[0041] The communication device 23 is hardware serving as a transmitting / receiving device for communicating with other devices. The communication device 23 is also called, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 23 may include a connector for wired connection and an interface circuit corresponding to the connector. The communication device 23 may also include a wireless communication interface. Examples of the connector and interface circuit for wired connection include products that comply with wired LAN, IEEE1394, and USB. Examples of the wireless communication interface include products that comply with wireless LAN, Bluetooth (registered trademark), etc.

[0042] The processing device 21 functions as a communication unit 211, a reception unit 212, a request unit 213, and a display control unit 214, for example, by reading and executing a control program PR2 from the storage device 22.

[0043] The communication unit 211 communicates with the payment server 30 via the communication device 23. When the application program PRA is started by the operation of the store clerk C, the communication unit 211 transmits a "payment code generation request" to the payment server 30 via the communication device 23.

[0044] The reception unit 212 receives operations on the input device 25 by the store clerk C or the user U. The operations by the store clerk C or the user U are operations for selecting whether to use general payment or specific payment. General payment is payment related to the purchase of goods at a store. Specific payment is payment related to a gift. Payment related to a gift is payment that legally requires identity verification. Payment related to a gift is an example of specific payment.

[0045] Payments related to gifts include payments related to donations, payments related to contributions, payments related to relief funds, and payments related to crowdfunding. In the present embodiment, payments related to donations will be described as an example of payments related to gifts. Payments related to gifts are not limited to payments related to donations, payments related to contributions, payments related to relief funds, and payments related to crowdfunding, and may be any payment that is classified as a gift.

[0046] The request unit 213 generates a payment code generation request to the payment server 30 based on the result of the accepted operation.

[0047] The display control unit 214 displays either the first code image or the second code image on the display device 24 in accordance with the operation received by the receiving unit 212. The first code image is used for general payments. The second code image is used for payments related to donations.

[0048] 1.1.4. Payment Server Configuration Fig. 4 is a block diagram showing an example of the configuration of the payment server 30 in Fig. 1. As shown in Fig. 4, the payment server 30 includes a processing device 31, a storage device 32, and a communication device 33. The elements included in the payment server 30 are connected to each other by one or more buses for communicating information. The payment server 30 is an example of a payment device.

[0049] The processing device 31 is a processor that controls the entire payment server 30, and is configured using, for example, one or more chips. The processing device 31 is configured using, for example, a central processing unit (CPU) including an interface with peripheral devices, an arithmetic unit, and a register. Note that some or all of the functions of the processing device 31 may be realized by hardware such as a DSP, ASIC, PLD, or FPGA. The processing device 31 executes various processes in parallel or sequentially.

[0050] The storage device 32 is a recording medium that can be read and written by the processing device 31. The storage device 32 includes, for example, a nonvolatile memory and a volatile memory. The nonvolatile memory is, for example, a ROM, an EPROM, and an EEPROM. The volatile memory is, for example, a RAM.

[0051] The storage device 32 stores a plurality of programs including a control program PR3 to be executed by the processing device 31. The storage device 32 also functions as a work area for the processing device 31.

[0052] The communication device 33 is hardware serving as a transmitting / receiving device for communicating with other devices. The communication device 33 is also called, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 33 may include a connector for wired connection and an interface circuit corresponding to the connector. The communication device 33 may also include a wireless communication interface. Examples of the connector and interface circuit for wired connection include products that comply with wired LAN, IEEE1394, and USB. Examples of the wireless communication interface include products that comply with wireless LAN, Bluetooth (registered trademark), etc.

[0053] The processing device 31 functions as a management unit 311, an acquisition unit 312, a settlement unit 313, and a notification unit 314, for example, by reading and executing a control program PR3 from the storage device 32.

[0054] The management unit 311 manages first identification information and second identification information in association with a store. A store is a store that can accept both the first payment method and the second payment method and can accept electronic payments for donations. The first identification information and the second identification information are information that identify the store. The first identification information is information that indicates that the store can accept the first payment method. The second identification information is information that indicates that the store can accept the second payment method.

[0055] The first payment method is a payment method that does not require identity verification. An example of the first payment method is payment by prepaid value. Prepaid value can be used for general shopping, but cannot be withdrawn as cash. With prepaid value, electronic money can be purchased at affiliated stores and deposited into an electronic payment account, or electronic money can be transferred and deposited into an electronic payment account.

[0056] The second payment method is a payment method that requires identity verification. An example of the second payment method is payment by cash value. Cash value can be used not only for general shopping but also for withdrawal as cash to a pre-registered bank account. Cash value can be used for donations, fundraising, etc., which legally require identity verification.

[0057] Identity verification involves verifying the user U's name, address, date of birth, occupation, etc. Identity verification usually needs to be performed in advance by the user U through the application program PRA. If identity verification is not completed, the user U can use the first payment method through the application program PRA, but cannot use the second payment method. Once identity verification is completed, the user U can use both the first and second payment methods through the application program PRA. Cash value, like prepaid value, can be used by depositing it in advance into a dedicated electronic payment account.

[0058] In this embodiment, both prepaid value and cash value are balance payments that are made within the deposited balance. If identity verification has not been completed, the balance payment is used as prepaid value. If identity verification has been completed, the balance value is used as cash value.

[0059] In order to enable a store to accept payments related to donations, fundraising, etc., i.e., to enable the use of the second payment method, the store information of the store stored in the storage device 32 of the payment server 30 needs to be updated. More specifically, the store device 20 requests the payment server 30 to update the value of the "donation flag" in the store information of the store from "0" to "1." In response to the request from the store, the payment server 30 updates the value of the "donation flag" from "0" to "1."

[0060] The first code image IM1 is an image containing a two-dimensional code that can be used with the first payment method. The second code image IM2 is an image containing a two-dimensional code that can be used with the second payment method. The first payment method cannot be used for payments using the second code image IM2. Therefore, the store can accommodate both the first and second payment methods by making the second payment method available and acquiring a new two-dimensional code that can be used with the first payment method.

[0061] Furthermore, in a registration process performed in advance in the application program PRA, the management unit 311 manages association information that associates the user terminal device 10 with the application program PRA installed in the user terminal device 10. This prevents a third party from illegally obtaining the ID and password of the application program PRA.

[0062] The acquisition unit 312 acquires a payment request from the user terminal device 10, the payment request including code information obtained by reading either the first code image or the second code image presented to the user U in the store with the user terminal device 10 of the user U. The payment request includes type information indicating the type of payment method and one of the first identification information and the second identification information.

[0063] The first code image is a code image including first identification information. The first code image is used for general payments. The second code image is a code image including second identification information. The second code image is used for payments related to donations.

[0064] When the payment request includes the first identification information, the payment unit 313 allows both the first and second payment methods. On the other hand, when the payment request includes the second identification information, the payment unit 313 does not allow the first payment method and only allows the second payment method.

[0065] Fig. 5 is a diagram showing an example of the relationship between the payment acceptance status of the payment unit 313 and the type information and identification information. As shown in Fig. 5, the type information includes a first payment method and a second payment method as types of payment methods. The identification information includes a first identification information and a second identification information.

[0066] When the payment request includes first identification information, the payment unit 313 allows both payment using the first payment method that does not require identity verification and payment using the second payment method that requires identity verification. On the other hand, when the payment request includes second identification information, the payment unit 313 does not allow payment using the first payment method that does not require identity verification, but allows payment using the second payment method that requires identity verification.

[0067] As described above, payment related to donations is legally required to be verified by personal identification. Therefore, if the payment request includes second identification information and the payment method indicated by the type information is the first payment method, the payment unit 313 will not execute the payment related to the donation. The type information is information included in the payment request. On the other hand, if the payment request includes second identification information and the payment method indicated by the type information is the second payment method, the payment unit 313 executes the payment related to the donation.

[0068] The notification unit 314 notifies the user terminal device 10 of the result of the payment. More specifically, if the payment unit 313 does not execute the payment for the donation, the notification unit 314 notifies the user terminal device 10 that the payment for the donation has not been made. Furthermore, if the payment unit 313 does not execute the payment for the donation, the notification unit 314 notifies the user terminal device 10 of information prompting the user to switch the payment method from the first payment method to the second payment method.

[0069] The generation unit 315 generates a payment code based on a payment code generation request from the in-store device 20. The payment code includes information such as a dynamic flag, a store-specific ID, the store name, and the store location.

[0070] When a payment code is generated in the generation unit 315 based on a payment code generation request from the in-store device 20, the communication unit 316 transmits code information regarding the generated payment code to the in-store device 20 via the communication device 33.

[0071] 1.2. Operation of User Terminal Device and Store Device According to First Embodiment 1.2.1. Operation from scanning the 2D code to payment The following example describes the operation of the user terminal device 10 and the in-store device 20 when a user U makes a payment related to a donation by following instructions on a screen displayed on the display device 24 of the in-store device 20. It is assumed that identity verification has been performed in the application program PRA and that both the first and second payment methods are available.

[0072] FIG. 6 is an example of a first code image IM1 displayed on the display device 24 of the in-store device 20. FIG. 7 is an example of a second code image IM2 displayed on the display device 24 of the in-store device 20. When the two-dimensional code payment menu is selected by the store clerk C or the user U on the in-store device 20, the screen switches to one that allows the user to select whether to make a regular payment or a donation payment. A regular payment is, for example, a payment made when purchasing a product in a store. A regular payment does not include a donation payment.

[0073] When the store clerk C or the user U operates the input device 25 to select to purchase a product from the store, a first code image IM1 used to purchase the product from the store is displayed on the display device 24, as shown in Fig. 6. On the other hand, when the store clerk C or the user U operates the input device 25 to select to make a payment related to a donation, a second code image IM2 used for the donation is displayed on the display device 24, as shown in Fig. 7.

[0074] Fig. 8 is a diagram showing an example of a reading screen SC1 of the application program PRA when it is launched. As shown in Fig. 8, the display control unit 114 displays the reading screen SC1 on the display device 14. The reading screen SC1 shows an image of the display device 24 of the in-store device 20 captured by the imaging device 16 of the user terminal device 10. A second code image IM2 is displayed on the reading screen SC1.

[0075] FIG. 9 is a diagram showing an example of a screen SC2 that is displayed after a two-dimensional code is read on the reading screen SC1 and on which the user U inputs the payment amount. Store information is acquired by reading the two-dimensional code. As shown in FIG. 9, the display control unit 114 displays the store name STN on the display device 14 based on the acquired store information. The user U inputs the donation amount in the payment amount field B11 using the input device 15. In this example, "1,000" is input as the donation amount. The display control unit 114 displays "1,000 yen" as the donation amount and displays a payment details confirmation button B12 at the bottom of the display device 14.

[0076] FIG. 10 is a diagram showing an example of a screen SC3 for confirming payment details. As shown in FIG. 10, the display control unit 114 displays the donation amount at the top of the display device 14 and the payment method at the center of the display device 14. In this example, it is assumed that the donation amount will be paid with an "XX card." However, in FIG. 10, the display control unit 114 displays a message M01 saying, "This payment method cannot be used at this store. Please change your payment method." In other words, payment with an "XX card" is not compatible with the second payment method.

[0077] In this case, the user U can transition to a screen for changing the payment method by tapping the "Another Method" button B13. The screen SC3 for confirming the payment details can be said to be a screen that notifies the user terminal device 10 that the donation settlement has not been made. Note that if the message M01 is not displayed and payment is possible, the payment can be processed by tapping the "Pay" button B14.

[0078] FIG. 11 is a diagram showing an example of a screen SC4 for changing the payment method. As shown in FIG. 11, the display control unit 114 displays the screen SC4 for changing the payment method superimposed on the screen for confirming the payment details. At this time, the display control unit 114 grays out the screen SC3 for confirming the payment details. The graying out indicates an inactive state that is no longer subject to operation by the user U. The display control unit 114 displays selection buttons for payment methods available in the application program PRA on the screen SC4 for changing the payment method. In this example, the display control unit 114 displays buttons for two payment methods.

[0079] The first payment method selection button B15 is the same as the payment method shown in Fig. 10. Because the first payment method cannot be used for payments related to donations, the display control unit 114 grays out the first payment method selection button B15, disabling operation by the user U. The display control unit 114 displays a message M02 on the screen SC4, superimposed on the first payment method selection button B15, stating "This payment method cannot be used at this store."

[0080] The second payment method selection button B17 indicates the payment method by "balance payment." In this example, since identity verification has been completed, "balance payment" is a cash value. Therefore, "balance payment" can be used for payments related to donations. Therefore, the second payment method selection button B16 is active. The user U selects the second payment method by tapping the second payment method selection button B16. The screen SC4 for changing the payment method can be said to be a screen that notifies the user terminal device 10 of information prompting the user to switch the payment method from the first payment method to the second payment method.

[0081] 12 is a diagram showing an example of a payment confirmation screen SC5 that is displayed after the payment method has been changed. As shown in FIG. 12, the display control unit 114 displays the donation name "●● Donation", the donation amount, and the payment method on the payment confirmation screen SC5. When the user U taps the "Pay" button B18, a payment request is sent to the payment server 30.

[0082] 13 is a diagram showing an example of a payment completion screen SC6 that is displayed after the payment is completed. As shown in Fig. 13, the display control unit 114 displays the store name, donation amount, transaction date and time, etc. on the payment completion screen SC6.

[0083] According to this embodiment, when a payment request is sent to the payment server 30 while a payment confirmation screen is displayed on the display device 14 of the user terminal device 10, and an error is notified from the payment server 30, a screen SC3 prompting the user to change the payment method is displayed on the display device 14. Therefore, the user U recognizes that the payment procedure has been completed in one go, improving the convenience for the user U.

[0084] 1.3. Operation of the Electronic Payment System According to the First Embodiment 1.3.1. First Operation of Electronic Payment System 1 Figure 14 is a sequence chart showing a first operation of the electronic payment system 1 of Figure 1. The first operation of the electronic payment system 1 will be explained below with reference to Figure 14. The first operation is an operation performed when no payment error related to the donation occurs because the payment method is a payment method compatible with the donation.

[0085] In response to an operation of the input device 15 by the user U, the user terminal device 10 starts the application program PRA in step S11.

[0086] In response to the user U's operation of the input device 15, the user terminal device 10 starts up a reading screen for reading the payment code in step S12.

[0087] In step S13, the in-store device 20 selects a payment method related to a donation through operation of the input device 25 by the user U or the store clerk C.

[0088] In step S14, the in-store device 20 requests the payment server 30 to generate a payment code. That is, in step S14, the in-store device 20 transmits a payment code generation request to the payment server 30.

[0089] When the payment server 30 receives the payment code generation request, in step S15, the payment server 30 generates a payment code.

[0090] In step S16, the payment server 30 transmits to the in-store device 20 code information indicating the generated payment code.

[0091] In step S17, the in-store device 20 displays the payment code image on the display device 24.

[0092] In step S18, the user U operates the user terminal device 10, causing the user terminal device 10 to read the payment code.

[0093] In step S19, the user U operates the user terminal device 10 to input the donation amount.

[0094] In step S20, the user U operates the user terminal device 10 to select the type of payment method. As described above, types of payment methods include payment by prepaid value, payment by cash value, payment by credit card, etc. In this example, payment by cash value corresponding to the donation is selected.

[0095] In step S21, the user terminal device 10 transmits a payment request to the payment server 30.

[0096] In step S22, the payment server 30 determines whether the payment is possible. In the example of Fig. 14, since the payment method is a payment method corresponding to a donation, the payment server 30 determines that the payment is possible.

[0097] In step S23, the payment server 30 transmits information about the transaction result to the user terminal device 10. The information about the transaction result is information indicating whether the donation transaction has been approved. In this example, the donation transaction is approved.

[0098] In step S24, the settlement server 30 transmits information about the transaction result to the in-store device 20.

[0099] In step S25, the user terminal device 10 displays the transaction result on the display device 14.

[0100] In step S26, the in-store device 20 displays the transaction result on the display device 24.

[0101] In step S27, the payment server 30 executes the payment process. In the payment process, the validity of the transaction is confirmed. If the validity of the transaction is confirmed and the transaction is approved, the payment server 30 retains information about the donation amount until the money is transferred to the account of the organization hosting the donation.

[0102] 1.3.2. Second Operation of Electronic Payment System 1 Figure 15 is a sequence chart showing a second operation of the electronic payment system 1 of Figure 1. The second operation of the electronic payment system 1 will be described below with reference to Figure 15. The second operation is performed when a payment error related to a donation occurs because the payment method is not compatible with the donation. Note that the processing from step S11 to step S21 is the same as the processing in the first operation shown in Figure 14, and therefore a description thereof will be omitted.

[0103] In step S22, the payment server 30 determines whether or not the payment is possible. In the example of Fig. 15, the payment server 30 determines that the payment is not possible because the payment method is not a payment method compatible with donations.

[0104] In step S28, the payment server 30 transmits an error notification to the user terminal device 10. The error notification includes information indicating that the payment for the donation has not been made, as well as information urging the user to switch the payment method to another payment method.

[0105] In step S29, the user terminal device 10 displays an error on the display device 14. The error message displayed on the display device 14 is, for example, "This payment method cannot be used at this store. Please change your payment method," as shown in Fig. 10. In this way, the error message not only notifies the user U that the payment for the donation has not been made, but also includes a message urging the user U to switch to a different payment method.

[0106] In step S30, a payment method different from the payment method selected in step S20 is selected by operation of the user U. Here, the different payment method is a payment method compatible with donations.

[0107] In step S31, the user terminal device 10 transmits a payment request to the payment server 30.

[0108] In step S32, the payment server 30 determines whether the payment is possible. In this case, since the selected payment method is a payment method that corresponds to the donation, the payment server 30 determines that the payment is possible.

[0109] In step S23, the payment server 30 transmits information about the transaction result to the user terminal device 10. In this case, the donation transaction is approved.

[0110] In step S24, the settlement server 30 transmits information about the transaction result to the in-store device 20.

[0111] In step S25, the user terminal device 10 displays the transaction result on the display device 14.

[0112] In step S26, the in-store device 20 displays the transaction result on the display device 24.

[0113] In step S27, the payment server 30 executes the payment process. In the payment process, the validity of the transaction is confirmed. If the validity of the transaction is confirmed and the transaction is approved, the payment server 30 retains information about the donation amount until the money is transferred to the account of the organization hosting the donation.

[0114] 1.4. Advantages of the First Embodiment As explained above, the payment server 30 according to the first embodiment includes a management unit 311, an acquisition unit 312, and a payment unit 313. The management unit 311 manages first identification information and second identification information in association with a store. The first identification information and second identification information are information for identifying a store. A store can support both the first payment method and the second payment method, and can support specific payments. The first payment method is a payment method that does not require identity verification. The second payment method is a payment method that requires identity verification.

[0115] The acquisition unit 312 acquires a payment request from the user terminal device 10. The payment request includes code information obtained by reading either the first code image IM1 or the second code image IM2 with the user terminal device 10 of the user U. The first code image IM1 is used for general payments and includes first identification information. The second code image IM2 is used for specific payments and includes second identification information. If the payment request includes the first identification information, the payment unit 313 allows both the first payment method and the second payment method, whereas if the payment request includes the second identification information, the payment unit 313 does not allow the first payment method but allows the second payment method.

[0116] According to this aspect, one store is assigned first identification information corresponding to a general payment that does not require identity verification, and second identification information corresponding to a specific payment that requires identity verification. Therefore, one store is provided with a first code image IM1 including the first identification information and a second code image IM2 including the second identification information. By reading the first code image IM1, the user U can use the general payment method, but cannot use the specific payment method. However, by reading the second code image IM2, the user U can use the specific payment method. Therefore, even if the store allows a payment method that does not require identity verification, the store can accept the specific payment method.

[0117] The payment request also includes type information and one of the first and second identification information. If the payment request includes the second identification information and the payment method indicated by the type information included in the payment request is the first payment method, the payment unit 313 does not execute the specific payment.

[0118] According to this embodiment, if the user U selects the first payment method that does not require identity verification for a particular payment, the payment can be made invalid.

[0119] Furthermore, if the payment request includes second identification information and the payment method indicated by the type information included in the payment request is the second payment method, the payment unit 313 executes a specific payment.

[0120] According to this embodiment, if the user U selects the second payment method that requires identity verification for a particular payment, the payment can be executed.

[0121] The payment server 30 also includes a notification unit 314. The notification unit 314 notifies the user terminal device 10 of the result of the payment. If the payment unit 313 does not execute a specific payment, the notification unit 314 notifies the user terminal device 10 that the specific payment has not been made.

[0122] According to this embodiment, the user U can recognize that a particular payment cannot be made.

[0123] Furthermore, if the settlement unit 313 does not execute the settlement related to the identification, the notification unit 314 notifies the user terminal device 10 of information urging the user to switch the payment method from the first payment method to the second payment method.

[0124] According to this embodiment, it is possible to prevent the user U from abandoning a particular payment.

[0125] The specific payment includes at least one of a payment related to fundraising, a payment related to donations, a payment related to relief funds, and a payment related to crowdfunding.

[0126] According to this aspect, the specific payment may include any payment related to a gift that requires identity verification.

[0127] The in-store device 20 also includes a communication unit 211, a reception unit 212, and a display control unit 214. The communication unit 211 communicates with the payment server 30. The reception unit 212 receives an operation from a store clerk C or a user U. The display control unit 214 displays either a first code image IM1 or a second code image IM2 on the display device 24 in accordance with the operation received by the reception unit 212.

[0128] According to this embodiment, either the first code image IM1 or the second code image IM2 can be displayed on one display device 24, eliminating the need for a display device dedicated to donations.

[0129] The user terminal device 10 also includes a communication unit 111 and a reading unit 112. The communication unit 111 communicates with the payment server 30. The payment server 30 manages first identification information and second identification information. The reading unit 112 is presented to the user U in a store and reads either a first code image IM1 or a second code image IM2. The first code image IM1 is used for general payments and is an image including first identification information. The second code image IM2 is used for specific payments and is an image including second identification information. The communication unit 111 transmits a payment request to the payment server 30, including code information obtained by reading either the first code image IM1 or the second code image IM2 with the reading unit 112.

[0130] According to this embodiment, the user U can use the user terminal device 10 to make both specific payments and general payments in a store that can handle specific payments.

[0131] A payment method according to a first embodiment is compatible with both a first payment method that does not require identity verification and a second payment method that does require identity verification, and includes a method for managing first identification information for identifying a store and second identification information for identifying a store, in association with a store that supports specific payments. The payment method includes a method for acquiring, from a user terminal device (10), a payment request including code information obtained by reading, with the user terminal device (10) of the user U, either a first code image (IM1) that is used for general payments and includes the first identification information, or a second code image (IM2) that is used for specific payments and includes second identification information, presented to the user U at the store. The payment method includes a method for executing a payment that allows both the first and second payment methods when the payment request includes the first identification information. The payment method also includes a method for executing a payment that does not allow the first payment method but allows the second payment method when the payment request includes the second identification information.

[0132] According to this aspect, one store is assigned first identification information corresponding to a general payment that does not require identity verification, and second identification information corresponding to a specific payment that requires identity verification. Therefore, one store is provided with a first code image IM1 including the first identification information and a second code image IM2 including the second identification information. By reading the first code image IM1, the user U can use the general payment method, but cannot use the specific payment method. However, by reading the second code image IM2, the user U can use the specific payment method. Therefore, even if the store allows a payment method that does not require identity verification, the store can accept the specific payment method.

[0133] 2. Variations The present disclosure is not limited to the above-described exemplary embodiments. Specific modified embodiments are exemplified below. Two or more embodiments selected from the following examples may be combined. Furthermore, the above-described exemplary embodiments and the following modified embodiments may be combined in any combination as long as they are not mutually inconsistent.

[0134] 2.1. Variation 1 In the first embodiment, the first code image IM1 and the second code image IM2 are dynamic QR codes (registered trademark), but the first code image IM1 and the second code image IM2 may be static QR codes (registered trademark). In this case, a first notice on which the first code image IM1 is printed and a second notice on which the second code image IM2 is printed are prepared in advance in the store. When the user U wishes to make a payment related to a donation, the store clerk C simply presents the second notice to the user U. The first notice and the second notice may be installed in the store in advance.

[0135] 2.2. Variation 2 In the first embodiment, when a payment request is sent to the payment server 30 while a payment confirmation screen is displayed on the display device 14 of the user terminal device 10, and an error is notified from the payment server 30, a screen SC3 prompting the user to change the payment method is displayed on the display device 14. However, the present invention is not limited to this. For example, when a payment request is sent to the payment server while a payment execution screen is displayed on the display device 14, and an error is notified from the payment server 30, a screen prompting the user to change the payment method may be displayed on the display device 14. In this aspect, when an error is notified, the user U is informed that he or she should execute the payment process again.

[0136] 2.3. Variation 3 In the first embodiment, screen SC4 shown in Fig. 11 and screen SC5 shown in Fig. 12 are displayed by graying out inactive screens and superimposing them on the inactive screens. However, this is merely an example, and the present invention is not limited to this. Screens SC4 and SC5 may be displayed over the entire display device 14. Furthermore, the display modes of messages M01 and M02 notifying an error are not limited to the modes shown in Figs. 10 and 11, and may be displayed in various modes.

[0137] 3.Other (1) In the above-described embodiment, storage device 12, storage device 22, and storage device 32 are exemplified by ROM and RAM, but may be a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory device (e.g., a card, a stick, a key drive), a CD-ROM (Compact Disc-ROM), a register, a removable disk, a hard disk, a floppy (registered trademark) disk, a magnetic strip, a database, a server, or any other suitable storage medium. The program may also be transmitted from a network via a telecommunications line. The program may also be transmitted from a communications network NET via a telecommunications line.

[0138] (2) In the above-described embodiments, the described information, signals, etc. may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0139] (3) In the above-described embodiment, input and output information may be stored in a specific location (for example, a memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be transmitted to another device.

[0140] (4) In the above-described embodiment, the determination may be made by a value (0 or 1) represented using one bit, by a Boolean value (true or false), or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0141] (5) The order of the process procedures, sequences, flowcharts, etc. illustrated in the above-described embodiments may be rearranged unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0142] (6) Each function illustrated in Figures 1 to 15 is realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device that is physically or logically coupled, or may be realized by using two or more devices that are physically or logically separated and connected directly or indirectly (for example, by wire, wirelessly, etc.). A functional block may also be realized by combining software with the one device or the multiple devices.

[0143] (7) The programs exemplified in the above-described embodiments should be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., regardless of whether they are called software, firmware, middleware, microcode, hardware description language, or by other names.

[0144] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0145] (8) In each of the foregoing embodiments, the terms "system" and "network" are used interchangeably.

[0146] (9) The information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or corresponding other information.

[0147] (10) In the above-described embodiments, the user terminal device 10 may be a mobile station (MS). A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate term. In this disclosure, terms such as "mobile station," "user terminal," "user equipment (UE)," and "terminal" may be used interchangeably.

[0148] (11) In the above-described embodiments, the terms "connected," "coupled," or any variations thereof refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be a physical coupling or connection, a logical coupling or connection, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0149] (12) In the above embodiments, the phrase "based on" does not mean "based only on," unless otherwise specified. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0150] (13) As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0151] (14) In the above embodiments, when "include," "including," and variations thereof are used, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, the term "or" as used in this disclosure is not intended to be an exclusive or.

[0152] (15) In this disclosure, where articles are added by translation, such as a, an, and the in English, this disclosure may include that the nouns following these articles are plural.

[0153] (16) In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combined" may also be interpreted in the same way as "different."

[0154] (17) Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0155] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure. [Explanation of symbols]

[0156] 1...electronic payment system, 10...user terminal device, 20...store device, 24...display device, 30...payment server, 31...processing device, 211...communication unit, 212...reception unit, 214...display control unit, 311...management unit, 312...acquisition unit, 313...payment unit, 314...notification unit, C...store clerk, IM1...first code image, IM2...second code image, U...user.

Claims

1. a management unit that is capable of supporting both a first payment method that does not require identity verification and a second payment method that does require identity verification, and that manages first identification information that identifies the store and second identification information that identifies the store, in association with a store that is capable of supporting a specific payment; an acquisition unit that acquires, from the terminal device of the user, a payment request including code information obtained by reading, with the terminal device of the user, either a first code image that is presented to the user at the store and is used for general payment and includes the first identification information, or a second code image that is used for the specific payment and includes the second identification information; a payment unit that allows the first payment method and the second payment method when the payment request includes the first identification information, and does not allow the first payment method and allows the second payment method when the payment request includes the second identification information; A payment device comprising:

2. the payment request includes type information indicating a type of payment method and one of the first identification information and the second identification information; The settlement unit If the second identification information is included in the payment request and the payment method indicated by the type information included in the payment request is the first payment method, the specific payment is not executed. The payment device according to claim 1 .

3. the payment unit executes the specific payment when the second identification information is included in the payment request and the payment method indicated by the type information included in the payment request is the second payment method. The payment device according to claim 2 .

4. a notification unit that notifies the terminal device of a settlement result; the notification unit notifies the terminal device that the specific payment was not made when the payment unit does not execute the specific payment; The payment device according to claim 1 .

5. The payment device according to claim 4 , wherein the notification unit notifies the terminal device of information prompting the terminal device to switch the payment method from the first payment method to the second payment method if the payment unit does not execute the specific payment.

6. The specific payment includes at least one of a payment related to fundraising, a payment related to donations, a payment related to relief funds, and a payment related to crowdfunding, The payment device according to claim 1 .

7. a communication unit that communicates with a payment device that is compatible with both a first payment method that does not require identity verification and a second payment method that does require identity verification, and that manages first identification information that identifies the store and second identification information that identify the store, in association with a store that is compatible with a specific payment; a reading unit that is presented to a user at the store and reads either a first code image used for general payment and including the first identification information, or a second code image used for the specific payment and including the second identification information; Equipped with the communication unit transmits to the payment device a payment request including code information obtained by reading either the first code image or the second code image with the reading unit; Terminal device.

8. The system is capable of supporting both a first payment method that does not require identity verification and a second payment method that requires identity verification, and manages first identification information that identifies the store and second identification information that identifies the store in association with a store that is capable of supporting a specific payment; a payment request including code information obtained by reading, with a terminal device of the user, either a first code image that is presented to the user at the store and is used for general payment and includes the first identification information, or a second code image that is used for the specific payment and includes the second identification information; and If the payment request includes the first identification information, a payment is made that allows the first payment method and the second payment method; If the second identification information is included in the payment request, the first payment method is not accepted and the second payment method is accepted. A payment method using a processing device.

Images