Payment agency server, payment agency method, payment agency program, and payment agency system
The payment agent server addresses double payments by allowing users to select from multiple payment methods and prohibiting re-selection, improving convenience by ensuring single-method payments.
Patent Information
- Application Number
- JP2022067142
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2022-04-14
- Publication Date
- 2024-11-01
- Estimated Expiration
- 2042-04-14
AI Technical Summary
Existing product sales processing systems face the issue of double payments, leading to increased time and effort in processing refunds, which decreases convenience for both businesses and consumers.
A payment agent server that communicates with user terminals to collect uncollected fees, presents multiple payment method candidates, allows user selection, and prohibits re-selection of the confirmed payment method to prevent double payments.
Prevents double payments, enhancing convenience for both businesses and consumers by ensuring payments are made using a single confirmed method.
Smart Images

Figure 0007577086000001 
Figure 0007577086000002 
Figure 0007577086000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a payment agency server, a payment agency method, a payment agency program, and a payment agency system related to payment for products or services. [Background technology]
[0002] Conventionally, a product sales processing system has been proposed as an example of a system for handling settlement (payment) of the price of a product or service on behalf of another customer (see Patent Document 1). The product sales processing system described in Patent Document 1 stores a plurality of pieces of identification information (such as credit card identification information) related to the purchasing behavior of a consumer in association with terminal identification data of the user terminal owned by the consumer, selects identification information that is valid for settlement of the price of a product or service from the identification information associated with the terminal identification data of the user terminal, and uses the selected identification information to execute processing related to the product that has been sold.
[0003] In the product sales processing system described in Patent Document 1, the convenience is improved because the consumer can select valid identification information when paying for the price of the product or service, but there is a risk of so-called double payment occurring, where the price of the same product or service is paid for by multiple payment methods. When double payment occurs, the business operator and the consumer have to work harder to process the refund, and the convenience is reduced as a result. For this reason, it is desirable to prevent double payment and thereby improve the convenience. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] Patent Publication No. 2021-033588 Summary of the Invention [Problem to be solved by the invention]
[0005] In view of the above-mentioned problems, the present invention aims to provide a payment agency server, a payment agency method, a payment agency program, and a payment agency system that can prevent double payments and improve convenience for both businesses and consumers. [Means for solving the problem]
[0006] The present invention is characterized in that it provides a payment agency server, a payment agency method, a payment agency program, and a payment agency system that are capable of communicating with a user terminal used by a user who receives goods or services from a business, and that, upon receiving a collection request process for collection of an uncollected balance related to the goods or service from the business, a candidate setting means for setting a plurality of candidate payment methods which are candidate payment methods that can be used to pay the uncollected balance, a presentation means for receiving a payment request process for payment of the uncollected balance from the user terminal and transmitting the plurality of candidate payment methods to the user terminal to present them to the user, a selection accepting means for accepting a user's selection of a payment method from among the plurality of candidate payment methods to be actually used to pay the uncollected balance, a confirmation means for confirming the payment method accepted by the selection accepting means as the final payment method to be used to pay the uncollected balance, and a prohibition means for prohibiting re-selection of a payment method related to the final payment method for payment of the uncollected balance after the final payment method has been confirmed. Effect of the Invention
[0007] This invention makes it possible to prevent duplicate payments and improve convenience for both businesses and consumers. [Brief description of the drawings]
[0008] [Figure 1] FIG. 1 is an explanatory diagram showing an example of the configuration of a payment system according to the present invention. [Diagram 2] FIG. 2 is a block diagram showing an example of the configuration of a user terminal. [Diagram 3] FIG. 4 is a block diagram showing an example of the configuration of a business server. [Figure 4] FIG. 2 is a block diagram showing an example of the configuration of a settlement institution server. [Diagram 5] FIG. 2 is a block diagram showing an example of the configuration of a payment agent server. [Figure 6] FIG. 11 is a flow diagram of a notification process for notifying a user regarding the settlement of an unpaid amount. [Figure 7] FIG. 11 is an explanatory diagram showing an example of a screen layout of a notification email. [Figure 8] FIG. 11 is an explanatory diagram showing an example of notification data embedded in a payment link of a notification email. [Figure 9] FIG. 4 is a flow diagram of a payment method setting process according to the present invention. [Figure 10] FIG. 13 is an explanatory diagram of the screen layout of a payment method selection screen. [Figure 11] An explanatory diagram of the screen layout of the destination information input screen in the payment slip method. [Figure 12] An explanatory diagram of the screen layout of the destination information confirmation screen in the payment slip method. [Figure 13] An explanatory diagram of the screen layout of the procedure completion screen using the payment slip method. [Figure 14] FIG. 13 is an explanatory diagram of the screen layout of a destination information input screen in an electronic payment method. [Figure 15] FIG. 13 is an explanatory diagram of the screen layout of a destination information confirmation screen in an electronic payment method. [Figure 16] FIG. 13 is an explanatory diagram showing an example of the screen layout of a notification email in an electronic payment method. [Figure 17] FIG. 13 is an explanatory diagram of the screen layout of a selection confirmation screen for a credit card method. [Figure 18] FIG. 13 is an explanatory diagram of a screen layout for inputting card information in a credit card method. [Figure 19] FIG. 13 is an explanatory diagram of the screen layout of a selection confirmation screen for the combined transfer method. [Figure 20] FIG. 13 is an explanatory diagram of the screen layout of an error screen. [Figure 21] FIG. 13 is an explanatory diagram of a screen configuration of a payment method selection screen according to a modified example. [Figure 22] FIG. 13 is an explanatory diagram of a screen configuration of a payment method selection screen according to another modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0009] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. <System configuration>
[0010] 1 is a block diagram showing an example of the system configuration of a payment system 1 of the present invention. The payment system 1 of the present invention is a system for providing a payment agency service (payment agency service) that performs payment (payment) on behalf of a user for a product or service.
[0011] As shown in Fig. 1, the payment system 1 has a user terminal 2, a business operator server 3, a payment institution server 4, and a payment agency server 5. The user terminal 2, the business operator server 3, the payment institution server 4, and the payment agency server 5 are each connected to each other so as to be able to communicate with each other via a public line (public network) 6 such as the Internet.
[0012] The user terminal 2 is a terminal used by a user (consumer) who receives a product or service from a business operator. The business operator server 3 is a server managed by a business operator (company) that provides the product or service to the user. The payment institution server 4 is a server managed by an institution (payment institution) for settling the price (value) of the product or service. Payment institutions include, for example, financial institutions such as banks, post offices, code payment service operating companies, and electronic payment service operating companies, as well as retail stores (convenience stores, drug stores, supermarkets, etc.) that are affiliated with financial institutions.
[0013] The payment methods for a product or service include one-time payment, which is used to pay for a product or service that is provided temporarily, and recurring payment, which is used to pay for a product or service that is provided continuously. In recent years, various payment methods (payment methods) have been proposed as alternatives to cash payment for both one-time payment and recurring payment. In other words, the payment methods that users can choose from are becoming more diverse. Under these circumstances, the payment agency server 5 is a server for providing a payment agency service that allows users to select any payment method from a variety of payment methods and make a payment.
[0014] For ease of explanation, one user terminal 2, one business server 3, and one payment institution server 4 are shown in the figure, however, the payment system 1 of the present invention can be used by multiple users, multiple businesses, and multiple payment institutions, and may have multiple user terminals 2, multiple business servers 3, and multiple payment institution servers 4.
[0015] Fig. 2 is a block diagram showing an example of the configuration of the user terminal 2. Fig. 3 is a block diagram showing an example of the configuration of the business operator server 3. Fig. 4 is a block diagram showing an example of the configuration of the payment institution server 4. Fig. 5 is a block diagram showing an example of the configuration of the payment agency server 5.
[0016] The user terminal 2 is a general-purpose computer (user terminal) used by a user. For example, it is a desktop PC, a notebook (laptop) PC, a tablet PC, a smartphone, a feature phone, etc. Each of the business operator server 3, the settlement institution server 4, and the settlement agency server 5 is configured as a general-purpose server computer (computing device). Each of the business operator server 3, the settlement institution server 4, and the settlement agency server 5 may be configured as one (single) computing device or multiple computing devices. Also, each of the business operator server 3, the settlement institution server 4, and the settlement agency server 5 may be a cloud server in part or in whole. For example, the settlement agency server 5 may be configured as a computing device that functions as a Web server, a computing device that functions as a file server (data server), and a computing device that functions as a payment server. Also, the settlement agency server 5 may be configured as a computing device that mainly exchanges data with the user terminal 2, and a computing device that mainly exchanges data with the business operator server 3.
[0017] 2, the user terminal 2 includes a control unit 21, an input unit 22, a display unit 23, a communication unit 24, and an auxiliary storage unit 25. The input unit 22, the display unit 23, the communication unit 24, and the auxiliary storage unit 25 are each connected to the control unit 21.
[0018] 3, the business entity server 3 includes a control unit 31, a communication unit 32, and an auxiliary storage unit 33. The communication unit 32 and the auxiliary storage unit 33 are each connected to the control unit 31.
[0019] 4, the payment institution server 4 includes a control unit 41, a communication unit 42, and an auxiliary storage unit 43. The communication unit 42 and the auxiliary storage unit 43 are each connected to the control unit 41.
[0020] 5, the payment agent server 5 includes a control unit 51, a communication unit 52, and an auxiliary storage unit 53. The communication unit 52 and the auxiliary storage unit 53 are each connected to the control unit 51.
[0021] As shown in Figures 2 to 5, the control unit 21 of the user terminal 2 includes a calculation unit 26 and a main memory unit 27, and executes various calculations and control operations in the user terminal 2. The control unit 31 of the business operator server 3 includes a calculation unit 34 and a main memory unit 35, and executes various calculations and control operations in the business operator server 3. The control unit 41 of the payment institution server 4 includes a calculation unit 44 and a main memory unit 45, and executes various calculations and control operations in the payment institution server 4. The control unit 51 of the payment agency server 5 includes a calculation unit 56 and a main memory unit 57, and executes various calculations and control operations in the payment institution server 4.
[0022] Each of the calculation units (26, 34, 44, 54) is a calculation processing unit including a CPU or an MPU, etc. Each of the main storage units (27, 35, 45, 55) has a RAM (DRAM), etc. The RAM is used as a work area and a buffer area for the calculation units (26, 34, 44, 54).
[0023] The input unit 22 has input components that accept operation inputs from the user, and an input detection circuit that is interposed between the input components and the control unit 21. The input components are, for example, a touch panel and / or hardware operation buttons or operation keys. The touch panel may be of any type, such as a capacitance type, an electromagnetic induction type, a resistive film type, or an infrared type. The input detection circuit outputs an operation signal or operation data (operation input data) corresponding to the operation of each input component to the control unit 21.
[0024] The display unit 23 has a display and a display control circuit interposed between the display and the control unit 21. For example, an LCD (liquid crystal display) or an organic EL display can be used as the display. The display control circuit has a GPU and a VRAM. Under the instruction of the control unit 21, the GPU generates display image data in the VRAM for displaying various screens on the display using image generation data stored in the RAM, and outputs the generated display image data to the display.
[0025] The communication units (24, 32, 42, 52) have a communication circuit for connecting to the public line 6. The communication circuit is a wired communication circuit or a wireless communication circuit, and communicates with an external computer via the public line 6 according to instructions from the calculation units (37, 47). In addition, the communication units (24, 32, 42, 52) of the user terminal 2, the business server 3, the payment institution server 4, and the payment agency server 5 can also communicate directly with each other via a dedicated line or the like, without going through the public line 6.
[0026] The auxiliary memory units (25, 33, 43, 53) are composed of non-volatile memory such as an HDD, SSD, flash memory, and EEPROM, and store programs for each calculation unit (26, 34, 44, 54) to control the operation of the user terminal 2, the business operator server 3, the payment institution server 4, and the payment agency server 5, as well as various data necessary for using the system.
[0027] 2, the auxiliary storage unit 25 of the user terminal 2 stores a user program 25a for executing various operations of the user terminal 2 in the system in response to operational inputs by the user, and user data 25b necessary for using the system. The user program 25a and user data 25b are read out from the auxiliary storage unit 25 as necessary and stored (expanded) in the main storage unit 27. The operation of the user terminal 2 is realized by the calculation unit 26 executing the user program 25a expanded in the main storage unit 27.
[0028] The user program 25a includes at least a communication program for accessing (establishing communication with) an external computer (such as the business server 3, the settlement agency server 4, and the settlement agent server 5), a display program for displaying various screens on the display unit 23, and a program for selecting and executing various functions of the user terminal 2. The user data 25b includes at least data of the user required in this system.
[0029] As shown in FIG. 3, the auxiliary storage unit 33 of the business server 3 stores a business program 33a for executing various operations of the business server 3, and business data 33b required for using the system.
[0030] The business program 33a includes a communication program for accessing (establishing communication with) an external computer (such as the user terminal 2, the settlement agency server 4, and the settlement agent server 5, etc.), an uncollected amount notification program for notifying the settlement agent server 5 of data on the amount (uncollected amount) that has not been settled among the amounts for the provision of goods or services, a collection request (collection request) program for performing a process (collection request process) for requesting (requesting) the collection of the uncollected amount, a confirmation program for confirming the selection result of the settlement method and the deposit data, and a program for selecting and executing various functions provided in the business server 3. The business program 33a and the business data 33b are read out from the auxiliary storage unit 33 as necessary and stored (expanded) in the main storage unit 35. The operation of the business server 3 is realized by the calculation unit 34 executing the business program 33a expanded in the main storage unit 35.
[0031] As shown in FIG. 4, the auxiliary storage unit 43 of the payment institution server 4 stores a payment institution program 43a for executing various operations of the payment institution server 4, and payment institution data 43b required for using the system.
[0032] The settlement institution program 43a includes a communication program for accessing (establishing communication with) an external computer (such as the user terminal 2, the business server 3, and the settlement agency server 5), a settlement program for making a settlement by an appropriate settlement method selected by the user, a deposit data notification program for notifying the settlement agency server 5 of data indicating that a settlement has been made (deposit data), and a program for selecting and executing various functions provided in the settlement institution server 4. The settlement institution program 43a and the settlement institution data 43b are read out from the auxiliary storage unit 43 as necessary and stored (expanded) in the main storage unit 45. The operation of the settlement institution server 4 is realized by the calculation unit 44 executing the settlement institution program 43a expanded in the main storage unit 45.
[0033] As shown in Figure 5, the auxiliary memory unit 53 of the payment agency server 5 stores a payment agency program 54 for executing various operations of the payment agency server 5, and payment agency data 55 necessary for using this system.
[0034] The payment agency program 54 includes a main processing program 54a for selecting and executing various functions equipped in the payment agency server 5, a payment method candidate setting program 54b for setting multiple payment method candidates to be presented to the user when paying for outstanding amounts related to the provision of goods or services, a payment method selection program 54c for allowing the user to select the payment method to be actually used for payment from the multiple payment method candidates, a payment data management program 54d for managing payment data, which is data related to the payment method selected by the user (confirmed payment method) and is data necessary for payment, and a deposit data management program 54e for managing deposit data notified from the payment institution server 4.
[0035] The payment agency data 55 includes business operator data 55a, which is data on business operators using this system, user data 55b, which is data on users using this system, payment method data 55c, which is detailed data on each payment method, uncollected balance data 55d, which is data on uncollected balances, payment method candidate data 55e, which is data on payment methods (payment method candidates) that can be set for each uncollected balance among the payment methods available in this system, confirmed payment method data 55f, which is data on the payment method selected by the user (confirmed payment method), payment data 55g, which is data necessary for payment, and deposit data 55h notified from the payment institution server 4.
[0036] The business data 55a includes data on payment methods selectable for each business (that the business allows for use). The user data 55b includes data on preregistered bank accounts (transfer accounts) for direct debit, payment data used in past payments, etc. The payment method data 55c includes data necessary for processing each payment method, as well as data on the maximum payment amount for each payment method.
[0037] The uncollected balance data 55d is stored as the uncollected balance data 55d when the uncollected balance data is acquired from the business operator's server 3. When the finalized payment method is determined, the uncollected balance data 55d is linked to the finalized payment method data 55f. The uncollected balance data 55d is also erased when the corresponding deposit data 55h is notified from the settlement institution server 4, that is, when the settlement of the uncollected balance is completed. Although not shown in the figure, the data for which the settlement has been completed may be stored as collected balance data (stored as part of the settlement agent data 55) so that the business operator or user can check it later.
[0038] The above-mentioned configurations of the user terminal 2, the business server 3, the payment agency server 4, and the payment agent server 5 are merely examples, and are not limited thereto. For example, the user terminal 2 may be capable of capturing a code image from an image captured by a camera and the camera, and decoding the captured image to obtain data embedded in the code. The code is a one-dimensional code (barcode) or a two-dimensional code. The two-dimensional code may be a matrix type two-dimensional code such as QR Code (registered trademark), micro QR Code, Aztec, DataMATRIX, MaxiCODE, and VeriCODE, or a stack type two-dimensional code such as PDF417 and CODE49. The user terminal 2 may have a calling function and may be equipped with components related to this calling function (such as a speaker and a microphone). <System operation example>
[0039] An example of the operation of the payment system 1 will be described below with reference to Figs. 6 to 20. First, a brief description will be given of the generation of uncollected payment data 55d, which is a premise for describing an example of the operation of the payment system 1. When a business provides a product or service to a user and the payment is not immediately settled, the business notifies the payment agent server 5 of the uncollected payment data from the business server 3. The payment agent server 5 stores the uncollected payment data 55d notified from the business server 3. At this time, the uncollected payment data notified from the business server 3 and the uncollected payment data 55d based thereon contain data (billede data) of the user (billede) to whom the uncollected payment is billed, data (billede data) of the business (biller) from which the uncollected payment is billed, data (billede data) of the billing details of the uncollected payment (products or services provided to the user), data of the amount of the uncollected payment (uncollected amount data), and data of the payment deadline for the uncollected payment (payment deadline data). <Notification process>
[0040] Fig. 6 is a flow diagram of a notification process for notifying a user regarding the settlement of an outstanding balance. Fig. 7 is an explanatory diagram showing an example of the screen configuration of a notification email 100. Fig. 8 is an explanatory diagram showing an example of notification data embedded in the settlement link 102 of the notification email 100. The notification process for notifying a user regarding the settlement of an outstanding balance will be described below with reference to Figs. 6 to 8.
[0041] The notification process shown in Fig. 6 is a process performed by the payment agency server 5 (control unit 51) in cooperation with the user terminal 2, the business operator server 3, the payment institution server 4, etc. As shown in Fig. 6, when the business operator server 3 requests (requests) the payment agency server 5 to collect the uncollected balance, the payment agency server 5 accepts the request to collect the uncollected balance (step S1) and identifies the uncollected balance data to be notified (step S2). Note that the data related to the collection request process from the business operator server 3 includes data for identifying the uncollected balance data, such as biller data, billing content data, and uncollected amount data.
[0042] Next, the payment agent server 5 judges whether the payment method of the uncollected fee data to be notified has been determined (confirmed) (step S3). If the payment method of the uncollected fee data to be notified has not been determined (step S3: NO), it judges whether there is a payment method that cannot be set (non-settable payment method) for the uncollected fee data to be notified (step S4). If there is a payment method that cannot be set (non-settable) for the uncollected fee data to be notified (step S4: YES), it performs a payment method exclusion process by business operator (step S5) and a payment method exclusion process by payment amount (step S6), and proceeds to step S7. Specifically, the payment agent server 5 that performs the payment method exclusion process by business operator (step S5) excludes a specific payment method from the payment method candidates for the uncollected fee data of all the people to be notified when the business operator has made the specific payment method unselectable. The payment agent server 5 that performs the payment method exclusion process by payment amount (step S6) excludes the payment method from the payment method candidates for the uncollected fee data to be notified, for which the amount of the uncollected fee to be notified exceeds the upper limit set for the payment method. Therefore, after performing both the process of excluding payment methods by business operator and the process of excluding payment methods by payment amount, the payment methods that the business operator has made unselectable are excluded from all types of payment methods in each uncollected payment data, and payment methods that exceed the upper limit amount are excluded, and only the remaining payment methods are set as selectable payment methods. In other words, unsettable payment methods are excluded from the payment method candidates.
[0043] On the other hand, if there is no payment method that cannot be set for the unpaid balance data to be notified (step S4: NO), the process proceeds to step S7 without going through steps S5 and S6. The payment agent server 5 sets all payment methods that can be set (if some have been excluded in steps S5 and S6, all remaining payment methods) as payment method candidates (step S7), and creates notification data regarding the payment of the unpaid balance to be notified (step S8). Here, the payment agent server 5 creates notification data that includes data on the payment method candidates to be presented to the user, billed party data, biller data, billing content data, unpaid amount data, and payment deadline data.
[0044] Next, the payment agent server 5 notifies the user terminal 2 of the relevant user (billing recipient) of the notification data using appropriate means such as email or an SNS message (step S9), and ends the notification process.
[0045] For example, in step S8, the payment agent server 5 notifies the user terminal 2 of the user (billed party) of a notification email 100 having contents as shown in Fig. 7. The notification email 100 includes a notification text 101 and a payment link 102.
[0046] The notification message 101 is the main text of the notification email 100, and is composed of text encouraging the payment of the outstanding amount. The notification message 101 includes information such as the name of the billed party (user name), the name of the biller (business name), and the details of the bill. In the example shown in FIG. 7, the notification message 101 also includes information on the expiration date of the payment link 102. Here, by matching the expiration date of the payment link 102 with the payment deadline, it is also possible to indirectly notify the user of the payment deadline in the body of the notification email 100.
[0047] The payment link 102 is a hyperlink for accessing the payment agent server 5 and displaying a web page for making a payment for the outstanding balance. The payment link 102 may be a text link that displays text such as a URL for displaying a web page, or may be an image link or a button-type link.
[0048] Also, notification data 10 regarding the unpaid balance to be notified is embedded in the payment link 102, as shown in Fig. 8. The notification data 10 includes biller data 11, billing content data 12, unpaid amount data 13, payment deadline data 14, candidate payment method data 15, etc.
[0049] In addition, even if it is the second or subsequent collection request for the same uncollected balance, if the payment method for the uncollected balance data to be notified has not been determined (step S3: NO), the payment agency server 5 will perform processing of steps S4 to S8.
[0050] On the other hand, if the payment method for the uncollected payment data to be notified has been confirmed (step S3: YES), the payment agency server 5 notifies the business operator (again) that the payment method has been confirmed (step S10) and terminates the notification process. <Payment method setting process>
[0051] When the payment link 102 is operated on the user terminal 2, the user terminal 2 executes a payment request process and automatically accesses the payment agency server 5, displays a web page on the display unit 23 for making payment of the outstanding balance, and starts the payment method setting process.
[0052] Fig. 9 is a flow diagram of the payment method setting process of the present invention. Fig. 10 is an explanatory diagram of the screen configuration of the payment method selection screen 110. The payment method setting process shown in Fig. 9 is a process performed by the payment agent server 5 (control unit 51) in cooperation with the user terminal 2, the business server 3, the payment institution server 4, etc.
[0053] As shown in Fig. 9, when the payment method setting process is started, the payment agent server 5 judges whether the payment method for the uncollected balance data to be notified has been confirmed (step S11). If the payment method for the uncollected balance data to be notified has not been confirmed (step S11: NO), the display unit 23 (display) of the user terminal 2 displays a payment method selection screen 110 (Fig. 10) for allowing the user to select a payment method (step S12). Each screen shown in Figs. 10 to 22 below is displayed on the display unit 23 of the user terminal 2 that has accessed the payment agent server 5.
[0054] The payment method selection screen 110 has a notification content display section 111 and a payment method selection section 112. The notification content display section 111 is provided to display various information about the uncollected balance that is the subject of the notification. The notification content display section 111 has a basic information display section 111a that displays characters indicating basic information such as the name of the billee (the user who uses the user terminal 2 on which the payment method selection screen 110 is displayed) and "Payment instructions," and a billing content display section 111b that displays characters indicating the billing content. The billing content display section 111b displays the name of the biller (business operator), the billing content of the uncollected balance (the name of the product or service that is the price of the uncollected balance), the billing amount, the payment deadline, etc.
[0055] The payment method selection unit 112 is provided to present to the user a plurality of payment method candidates that can be used for the payment of the outstanding amount, and to allow the user to select a payment method to be actually used for the payment from among the payment method candidates. The payment method candidates presented by the payment method selection unit 112 are set according to the payment method candidate data 15 included in the notification data 10. In this embodiment, when a payment method using a payment slip (payment slip method), a payment method using electronic payment from the Internet (electronic payment method), a payment method using a credit card (or debit card) (credit card method), or a bank account for transfer (transfer account) is registered, a method for paying all together in the next account transfer (combined transfer method) can be selected. That is, the payment agent server 5 receives the payment request process, transmits a plurality of payment method candidates to the user terminal 2, and presents them to the user.
[0056] A payment slip is a form for making payments at stores such as convenience stores, post offices, other financial institutions, etc. A payment slip may be in any format, and may, for example, have the name of the claimant, the name of the claimant, the payment amount, the payment deadline, and a one-dimensional code (barcode) or two-dimensional code printed on it. For example, a payment slip is sent to a user by mail.
[0057] The one-dimensional code (barcode) or two-dimensional code contains information necessary for payment, such as a payment ID that uniquely identifies each payment, a biller ID that identifies the payee (biller), the payment amount, and the payment deadline.
[0058] The deposit slip does not have to be printed on paper, but may be displayed electronically on a screen. In this case, the deposit slip may be sent to the user as an electronic file and printed by the user. Furthermore, payment may be made electronically using the electronic data of the deposit slip. In this case, the user can make payment at home without going to a store or the like. This method of electronic payment using the electronic data of the deposit slip is sometimes called paperless payment.
[0059] Electronic payment is a payment made by sending and receiving electronic monetary value data using a computer. The electronic monetary value data that can be used in electronic payment can be of any type, such as electronic money, points, or virtual currency (cryptocurrency).
[0060] In the example shown in FIG. 10, the payment method selection unit 112 has a first payment method selection unit 113 for selecting a payment slip method (first payment method), a second payment method selection unit 114 for selecting an electronic payment method (second payment method), a third payment method selection unit 115 for selecting a credit card method (third payment method), and a fourth payment method selection unit 116 for selecting a combined transfer method (fourth payment method). That is, by displaying the payment method selection screen 110, at least one or more payment method candidates that can be used to pay the outstanding balance are presented to the user. Note that the payment methods presented as payment method candidates in FIG. 10 are merely examples, and other payment methods may be presented.
[0061] The first payment method selection unit 113, the second payment method selection unit 114, the third payment method selection unit 115, and the fourth payment method selection unit 116 each have selection buttons 113a to 116a for selecting a payment method. The selection buttons 113a to 116a function as so-called software keys (operation buttons). Hereinafter, software keys are simply referred to as "buttons." When the selection buttons 113a to 116a are operated (selected), various input screens are displayed for inputting the necessary items for each payment method and for confirming the payment method. That is, the selection buttons 113a to 116a provided on the first payment method selection unit 113, the second payment method selection unit 114, the third payment method selection unit 115, and the fourth payment method selection unit 116 each are for accepting the user's selection of a payment method to be actually used for payment of the outstanding balance from among a plurality of payment method candidates.
[0062] Returning to FIG. 9, the payment agent server 5 determines whether or not the payment method has been selected and the necessary information has been entered, and then the payment method has been confirmed (step S13). If the payment method has not been confirmed (step S13: NO), the process returns to the same step S13. On the other hand, if the payment method has been confirmed (step S13: YES), the confirmed payment method (confirmed payment method) is stored (step S14), and the payment method setting process ends. Below, a specific example of the operation when the payment method is confirmed for each of the first to fourth payment methods will be described. <Payment method>
[0063] Fig. 11 is an explanatory diagram of the screen configuration of the destination information input screen 120 in the first payment method (deposit slip method). Fig. 12 is an explanatory diagram of the screen configuration of the destination information confirmation screen 130 in the payment slip method. Fig. 13 is an explanatory diagram of the screen configuration of the procedure completion screen 140 in the payment slip method.
[0064] First, an example of operation when the selection button 113a of the first payment method selection section 113 on the payment method selection screen 110 is operated, that is, when the first payment method (deposit slip method) is selected, will be described.
[0065] When the first payment method (payment slip method) is selected, a destination information input screen 120 is displayed as shown in Fig. 11. The destination information input screen 120 is a screen for allowing the user to input information related to the destination (payment slip destination information) required for mailing the payment slip to the user. The destination information input screen 120 has a notification message 121 for prompting the user to input destination information, a destination information input section 122 for accepting input of destination information, a back button 123, and a proceed button 124.
[0066] The destination information on the payment slip includes, for example, a postal code, an address, a telephone number, and a recipient's name. The destination information input unit 122 has a postal code input unit 122a that accepts input of a postal code, an address input unit 122b that accepts input of an address, a telephone number input unit 122c that accepts input of a telephone number, and a recipient input unit 122d that accepts input of a recipient's name. Each of the postal code input unit 122a, the address input unit 122b, the telephone number input unit 122c, and the recipient input unit 122d has a text box (input field) that accepts input of text corresponding to each item.
[0067] The back button 123 is a button for canceling (deleting) the items input on the destination item input screen 120 and returning to the payment method selection screen 110. Note that a back button 153, which will be described later, also has a function of canceling the items input on each input screen and returning to the payment method selection screen 110, similar to the back button 123.
[0068] The proceed button 124 is a button for confirming the destination information of the payment slip entered in the destination information input screen 120 and proceeding to the next step. When the proceed button 124 is operated, the destination information of the payment slip is decided based on the contents entered in the destination information input section 122, and the destination information confirmation screen 130 as shown in Figure 12 is displayed. Note that the proceed button 154, which will be described later, also has the function of confirming the information entered on each input screen and proceeding to the next step, similar to the proceed button 124.
[0069] The destination information confirmation screen 130 is a screen for prompting the user to confirm the destination information of the payment slip entered on the destination information input screen 120 and for confirming the payment method as the payment slip method. The destination information confirmation screen 130 has a notification message 131 for prompting the user to confirm the destination information of the payment slip, a destination information display section 132 that displays the destination information of the payment slip, a warning section 133, a back button 134 for returning to the destination information input screen 120, and a confirm button 135 for determining the destination information of the payment slip and confirming the payment method as the payment slip method.
[0070] The destination information display section 132 displays the destination information of the payment slip entered on the previous destination information input screen 120. In detail, the destination information display section 132 has a postal code display section 132a that displays the postal code, an address display section 132b that displays the address, a telephone number display section 132c that displays the telephone number, and a destination name display section 132d that displays the destination name. By looking at the destination information display section 132, the user can check whether the destination information of the payment slip that he or she entered is correct.
[0071] The warning section 133 is provided to inform the user that the payment method is confirmed as the deposit slip method by operating (pressing) the confirmation button 135, and the payment method cannot be changed thereafter, and to call the user's attention. For example, the warning section 133 has a warning message indicating that the payment method cannot be changed by pressing the confirmation button 135. By providing such a warning section 133, the user recognizes that the payment method is confirmed by pressing the confirmation button 135 and that the payment method cannot be changed thereafter, and operates the confirmation button 135 carefully. Therefore, it is possible to suppress or prevent the selection of an unintended payment method due to an operation error or the like. In addition, the back button 134 allows the user to return to the destination information input screen 120, and since the destination information input screen 120 also has a back button 123, the user can return from the destination information confirmation screen 130 to the payment method selection screen 110 and reselect an appropriate payment method. Therefore, it is possible to improve the convenience of both the business operator and the user (consumer).
[0072] When the Confirm button 135 is operated, the destination information of the payment slip is determined, and the payment method is confirmed as the payment slip method (step S13: YES). When the payment method is confirmed as the payment slip method, a procedure completion screen 140 as shown in FIG. 13 is displayed. The procedure completion screen 140 is a screen for notifying the user that the procedure for selecting the payment method has been confirmed. The procedure completion screen 140 has a notification message 141 for notifying the user that the procedure for selecting the payment method has been confirmed, a billing content display section 142 for displaying the billing content, and a close button 143. The billing content display section 142 displays the content corresponding to the billing content display section 111b (see FIG. 10), i.e., the name of the biller, the name of the billing content for the unpaid amount, the billing amount, the payment deadline, etc. When the close button 143 is operated, the procedure completion screen 140 is hidden. <Electronic payment method>
[0073] Fig. 14 is an explanatory diagram of the screen configuration of a destination information input screen 150 in an electronic payment method. Fig. 15 is an explanatory diagram of the screen configuration of a destination information confirmation screen 160 in an electronic payment method. Fig. 16 is an explanatory diagram showing an example of the screen configuration of a notification email 170 in an electronic payment method.
[0074] Next, an example of operation when the selection button 114a of the second payment method selection section 114 on the payment method selection screen 110 is operated, that is, when the second payment method (electronic payment method) is selected, will be described.
[0075] When the second payment method (electronic payment method) is selected, a destination information input screen 150 as shown in Fig. 14 is displayed. The destination information input screen 150 is a screen for allowing the user to input information required for making an electronic payment, i.e., information to which a notification email for making an electronic payment will be sent (destination information for electronic payment). The destination information input screen 150 has a notification message 151 for prompting the user to input destination information for electronic payment, a destination information input section 152 for accepting input of destination information for electronic payment, a back button 153, and a proceed button 154.
[0076] Destination items related to electronic payment include, for example, email addresses and telephone numbers. Destination item input unit 152 has email address input unit 152a that accepts input of email addresses and telephone number input unit 152b that accepts input of telephone numbers. Email address input unit 152a and telephone number input unit 152b each have a text box that accepts input of text corresponding to the destination items.
[0077] When proceed button 124 is operated, the destination information for electronic payment is determined based on the contents entered in destination information input section 122, and a destination information confirmation screen 160 as shown in Fig. 15 is displayed. Destination information confirmation screen 160 is a screen for prompting the user to confirm the destination information for electronic payment entered in destination information input screen 150, and for confirming the payment method as the electronic payment method. Destination information confirmation screen 160 has a notification message 161 for prompting the user to confirm the destination information for electronic payment, a destination information display section 162 for displaying the destination information for electronic payment, a warning section 163, a back button 164 for returning to destination information input screen 150, and a confirmation button 165 for determining the destination information for electronic payment and confirming the payment method as the electronic payment method.
[0078] Destination information display section 162 displays the destination information related to electronic payment that was entered on the previous destination information input screen 150. In detail, destination information display section 162 has an email address display section 162a that displays an email address, and a phone number display section 162b that displays a phone number. By looking at destination information display section 162, the user can check whether the destination information related to electronic payment that he or she entered is correct.
[0079] The warning section 163 is provided to notify the user that the payment method is confirmed as an electronic payment method by operating (pressing) the Confirm button 165, and the payment method cannot be changed thereafter, and to call the user's attention. For example, the warning section 163 has a warning message indicating that the payment method cannot be changed by pressing the Confirm button 165. By providing such a warning section 163, the user recognizes that the payment method is confirmed by pressing the Confirm button 165 and that the payment method cannot be changed thereafter, and operates the Confirm button 165 carefully. Therefore, it is possible to suppress or prevent the selection of an unintended payment method due to an operational error or the like. In addition, the user can operate the back button 164 to return to the payment method selection screen 110 and reselect an appropriate payment method.
[0080] When the Confirm button 165 is operated, the destination information for the electronic payment is determined, and the payment method is confirmed as the electronic payment method (step S13: YES). When the payment method is confirmed as the electronic payment method, a notification email 170 with contents as shown in Fig. 16 is sent to the user terminal 2 of the user (billed party). The notification email 170 includes a notification text 171 and a link 172 for electronic payment.
[0081] The notification message 171 is the main text of the notification email 170, and is composed of a message encouraging the user to complete the electronic payment procedure. The notification message 171 includes information on the expiration date of the electronic payment link 172 (the deadline for electronic payment).
[0082] The electronic payment link 172 is a hyperlink for accessing the payment agent server 5 and displaying an appropriate web page for performing electronic payment. The electronic payment link 172 may be a text link displaying text such as a URL for displaying a web page, or may be an image link or a button-type link. The electronic payment link 172 may be a hyperlink for directly accessing the payment institution server 4 that handles electronic payments. In this case, an appropriate web page for performing electronic payment provided by the payment institution server 4 is displayed on the display unit 23 of the user terminal 2. <Credit card method>
[0083] Fig. 17 is an explanatory diagram of the screen configuration of a selection confirmation screen 180 in the credit card method. Fig. 18 is an explanatory diagram of the screen configuration of a card information input screen 190 in the credit card method.
[0084] Next, an example of the operation when the selection button 115a of the third payment method selection section 115 on the payment method selection screen 110 is operated, that is, when the third payment method (credit card method) is selected, will be described.
[0085] When the third payment method (credit card method) is selected, a selection confirmation screen 180 as shown in Fig. 17 is displayed. Selection confirmation screen 180 is a screen for allowing the user to confirm that the credit card method has been selected and for finalizing the payment method. Selection confirmation screen 180 has a notification 181 for notifying the user that the credit card method has been selected, a billing details display section 182 for displaying the details of the billing, a warning section 183, a back button 184 for returning to the payment method selection screen 110, and a confirmation button 185 for finalizing the payment method. The billing details display section 182 displays the name of the biller, the name of the billing details for the unpaid amount, the billing amount, etc., in correspondence with billing details display section 111b (see Fig. 10) etc.
[0086] The warning section 183 is provided to notify the user that the payment method is confirmed as the credit card method by operating (pressing) the Confirm button 185, and the payment method cannot be changed thereafter, and to call the user's attention. For example, the warning section 183 has a warning message indicating that the payment method cannot be changed when the Confirm button 185 is pressed. By providing such a warning section 183, the user recognizes that the payment method is confirmed by pressing the Confirm button 185 and that the payment method cannot be changed thereafter, and operates the Confirm button 185 carefully. Therefore, it is possible to suppress or prevent the selection of an unintended payment method due to an operational error or the like. In addition, the user can operate the back button 184 to return to the payment method selection screen 110 and reselect an appropriate payment method.
[0087] When the Confirm button 185 is operated, the payment method is confirmed as the credit card method (step S13: YES). When the payment method is confirmed as the credit card method, a card information input screen 190 as shown in Fig. 18 is displayed. The card information input screen 190 has a notification message 191 prompting the input of information (card information) required for payment by credit card, a card information input section 192 for accepting the input of card information, and a payment execution button 193 for executing the payment.
[0088] The card information includes, for example, a card number, a card expiration date, and a security code. The card information input unit 192 has a card number input unit 192a for inputting a card number, a card expiration date input unit 192b for inputting a card expiration date, and a security code input unit 192c for inputting a security code. When correct card information is input to the card information input unit 192 and a payment execution button 193 is operated, payment is executed by credit card. <Combined transfer method>
[0089] 19 is an explanatory diagram of the screen configuration of the selection confirmation screen for the combined transfer method. Next, an operation example will be described when the selection button 116a of the fourth payment method selection section 116 on the payment method selection screen 110 is operated, that is, when the fourth payment method (combined transfer method) is selected.
[0090] When the fourth payment method (combined transfer method) is selected, a selection confirmation screen 200 as shown in FIG. 19 is displayed. The selection confirmation screen 200 is a screen for prompting the user to confirm that the combined transfer method for paying all at once in the next account transfer has been selected, and for finalizing the payment method. The selection confirmation screen 200 has a notification 201 for notifying the user that the combined transfer method has been selected, a billing details display section 202 for displaying the billing details, a warning section 203, a back button 204 for returning to the payment method selection screen 110, and a confirmation button 205 for finalizing the payment method. The billing details display section 202 displays the name of the biller, the name of the billing details for the unpaid amount, the billing amount, etc., corresponding to the billing details display section 111b (see FIG. 10) etc.
[0091] The warning section 203 is provided to notify the user that the payment method is confirmed as the combined transfer method by operating (pressing) the Confirm button 205, and the payment method cannot be changed thereafter, and to call the user's attention. For example, the warning section 203 has a warning message indicating that the payment method cannot be changed by pressing the Confirm button 205. By providing such a warning section 203, the user recognizes that the payment method is confirmed by pressing the Confirm button 205 and that the payment method cannot be changed thereafter, and operates the Confirm button 205 carefully. Therefore, it is possible to suppress or prevent the selection of an unintended payment method due to an operation error or the like. In addition, the user can operate the back button 204 to return to the payment method selection screen 110 and reselect an appropriate payment method.
[0092] When the confirm button 205 is operated, the payment method is confirmed as the combined transfer method (step S13: YES). When the payment method is confirmed as the combined transfer method, the unpaid amount is paid at the preset account transfer timing.
[0093] In the above manner, when the first to fourth payment methods are confirmed (step S13: YES), the confirmed payment method (confirmed payment method) is stored (step S14), and the payment method setting process ends. <Prohibition of reselection after final payment method setting>
[0094] On the other hand, returning to FIG. 9, if the payment method for the unpaid bill data to be notified has been confirmed (step S11: YES), an error screen 210 as shown in FIG. 20 is displayed and the payment method setting process is terminated.
[0095] The error screen 210 is a screen for notifying the user that the payment method for the uncollected balance data has already been confirmed. The error screen 210 has a notification message 211 for notifying the user that the payment method for the uncollected balance data has already been confirmed (a confirmed payment method has been set), and a close button 212. When the close button 212 is operated, the error screen 210 is hidden. In other words, when the payment method for the uncollected balance data that is the subject of the notification has been confirmed, the payment agency server 5 notifies the user by sending confirmed information indicating that the payment method for the uncollected balance has been confirmed to the user terminal 2.
[0096] In other words, when the payment method for the unpaid bill data to be notified has been finalized, the payment method cannot be reselected (reselection of the payment method is prohibited).
[0097] With the above configuration and operation, in the payment system 1 of the present invention, when the payment method for the unpaid bill data to be notified has been confirmed, selecting a payment method again is prohibited, and a notification is given that the payment method for the unpaid bill data has already been confirmed. Therefore, in the payment system 1 of the present invention, once a confirmed payment method is set, payment is only possible using the confirmed payment method, and it is possible to prevent so-called double payment, where the same product or service is paid for using multiple payment methods. Therefore, it is possible to prevent the consumer from having to go through additional work in refund processing when double payment occurs, and to improve convenience.
[0098] The payment agency server of the present invention corresponds to the payment agency server 5 of the above embodiment, the user terminal corresponds to the user terminal 2, the candidate setting means corresponds to the payment method candidate setting program 54b and the control unit 51 operating in accordance with the program, the presentation means corresponds to the payment method selection unit 112, the selection acceptance means corresponds to the first payment method selection unit 113, the second payment method selection unit 114, the third payment method selection unit 115, the fourth payment method selection unit 116 and the selection buttons 113a to 116a, and the confirmation means corresponds to the confirmation button 135. , 165, 185, 205, the prohibition means corresponds to step S3, step S9 and the control unit 51 which executes these, the warning means corresponds to the warning units 133, 163, 183, 203, step S3, step S10 and the payment method selection program 54c and the control unit 51 which operates in accordance with this, the notification means corresponds to the notification text 211 (error screen 210), and the storage means corresponds to the auxiliary storage unit 53, but this invention is not limited to this embodiment and can be various other embodiments. Also, the screens and specific configurations etc. listed in the above embodiment are merely examples and can be appropriately changed according to the actual product.
[0099] FIG. 21 is an explanatory diagram of the screen configuration of the payment method selection screen 110A of the modified example. For example, an upper limit of the payment amount may be set for each payment method. In this case, the selection button corresponding to the payment method that exceeds the upper limit of the payment amount is disabled so that it cannot be selected. In the example shown in FIG. 21, among the selection buttons of the first payment method selection section 113 of the payment method selection screen 110A, the selection button 113a corresponding to the first payment method (payment slip method) and the selection button 113b corresponding to the second payment method (electronic payment method) are disabled. This is because the upper limit of the payment amount of the payment slip method and the electronic payment method is 300,000 yen, while the payment amount is 350,000 yen, which exceeds the upper limit of the payment amount of the payment slip method and the electronic payment method. In this way, only the payment methods that can be used at the time when the payment method selection screen 110A is displayed can be presented to the user.
[0100] 22 is an explanatory diagram of the screen configuration of the payment method selection screen 110B of another modified example. Also, the payment methods that can be selected may be limited for each business operator. In this case, the selection button corresponding to the payment method restricted by the business operator that bills the unpaid amount that is the subject of the notification is disabled so that it cannot be selected.
[0101] In the example shown in Fig. 22, among the selection buttons in the first payment method selection section 113 of the payment method selection screen 110B, the selection button 113b corresponding to the second payment method (electronic payment method) is disabled. That is, in the example shown in Fig. 22, the business operator restricts (does not permit) payment using the second payment method (electronic payment method). In this way, it is possible to provide an optimal payment system customized for each business operator.
[0102] In addition, the progress buttons 124, 154 (see Figures 11 and 14) may be disabled so that they cannot be operated until all destination information has been entered (until all destination information is complete) on each input screen (destination information input screen 120, destination information input screen 150).
[0103] Furthermore, instead of the selection buttons 113a to 116a on the payment method selection screen 110 as shown in Fig. 10, a switching button for switching between displaying and hiding detailed information of the candidate payment methods (detailed information on the candidate payment methods) presented in the payment method selection section 112 may be provided. For example, the detailed information on the candidate payment methods may be information on stores that accept payment by deposit slips, information on the types of data of electronic monetary value that can be used for electronic payment, and information on brands of credit cards that can be used for payment by credit card method. In this case, each of the selection buttons 113a to 116a may be displayed on the payment method selection screen 110 when the detailed information on the candidate payment methods is displayed. [Industrial Applicability]
[0104] The present invention can be used in industries related to payment agents for products or services. [Explanation of symbols]
[0105] 1. Payment system 2. User terminal 3. Business server 4. Payment institution server 5. Payment processing server 51...Control unit
Claims
1. A payment agent server capable of communicating with a user terminal used by a user who receives a product or service from a business operator, a candidate setting means for receiving a collection request process for collection of the uncollected amount for the product or service from the business operator and setting a plurality of candidate payment methods that are available for the payment of the uncollected amount; a presentation means for receiving a payment request process for the payment of the outstanding balance from the user terminal, transmitting the plurality of payment method candidates to the user terminal and presenting them to the user; a selection receiving means for receiving a selection by a user of a payment method to be actually used for settling the outstanding balance from among the plurality of candidate payment methods; a determination means for determining the payment method accepted by the selection acceptance means as the final payment method to be used for settling the outstanding balance; and a prohibition means for prohibiting reselection of the payment method for the unpaid amount related to the confirmed payment method after the confirmed payment method is confirmed. Payment processing server.
2. The payment method is determined by the selection receiving means, and before the selection receiving means receives the user's selection and determines the payment method, the payment method is not changeable if the payment method is determined. The payment method is notified to the user by transmitting, to the user terminal, warning information to alert the user. The payment agent server according to claim 1.
3. The payment method selection device further includes a notification device for, when the payment request process is accepted from the user terminal after the prohibition device has prohibited reselection of the payment method, sending confirmation information indicating that the payment method related to the uncollected amount has been confirmed to the user terminal to notify the user. The payment agent server according to claim 1 or 2.
4. A storage means for storing a payment method that can be used at each of the plurality of businesses, The candidate setting means sets the plurality of payment method candidates according to payment methods that can be used by a business entity related to the uncollected amount. The payment agent server according to claim 1.
5. Using a user terminal used by a user who receives a product or service from a business operator and a payment agency server that can communicate with the user terminal, receiving a collection request process for collection of an uncollected amount for the product or service from the business operator, and setting a plurality of payment method candidates that are available for payment of the uncollected amount; receiving a payment request process for the payment of the outstanding balance from the user terminal, transmitting the plurality of payment method candidates to the user terminal and presenting them to the user; Accepting a user's selection of a payment method to be actually used for settling the outstanding balance from among the plurality of candidate payment methods; confirming the accepted payment method as the confirmed payment method to be used for settling the outstanding amount; After the confirmed payment method is confirmed, reselection of the payment method for the uncollected amount related to the confirmed payment method is prohibited. Payment agency method.
6. A computer-readable program for controlling a payment agent server capable of communicating with a user terminal used by a user who receives a product or service from a business operator, The computer, a candidate setting means for receiving a collection request process for collection of the uncollected amount for the product or service from the business operator and setting a plurality of candidate payment methods that are available for the payment of the uncollected amount; a presentation means for receiving a payment request process for the payment of the outstanding balance from the user terminal, transmitting the plurality of payment method candidates to the user terminal and presenting them to the user; a selection receiving means for receiving a selection by a user of a payment method to be actually used for settling the outstanding balance from among the plurality of candidate payment methods; a determination means for determining the payment method accepted by the selection acceptance means as the final payment method to be used for settling the outstanding balance; After the finalized payment method is finalized, the method functions as a prohibition means for prohibiting reselection of the payment method for the uncollected amount related to the finalized payment method. Payment agency program.
7. A user terminal used by a user who receives a product or service from a business operator, and a payment agent server capable of communicating with the user terminal, The payment agent server includes: a candidate setting means for receiving a collection request process for collection of the uncollected amount for the product or service from the business operator and setting a plurality of candidate payment methods that are available for the payment of the uncollected amount; a presentation means for receiving a payment request process for the payment of the outstanding balance from the user terminal, transmitting the plurality of payment method candidates to the user terminal and presenting them to the user; a selection receiving means for receiving a selection by a user of a payment method to be actually used for settling the outstanding balance from among the plurality of candidate payment methods; a determination means for determining the payment method accepted by the selection acceptance means as the final payment method to be used for settling the outstanding balance; and a prohibition means for prohibiting reselection of the payment method for the unpaid amount related to the confirmed payment method after the confirmed payment method is confirmed. Payment agency system.
Citation Information
Patent Citations
Commodity price settlement system, its terminal device, and program of management server
JP2004086429A
Method for electronic bill settlement of gas charge
JP2009288921A
Processing device for performing settlement proxy between purchaser and seller
JP2019106095A
Commodity sales processing system, commodity sales processing apparatus and method, and control program
JP2021033588A
Information processing system, information processing method, information processing device, and program
JP2022013845A
