Information processing device, method, and program

Abstract

To perform appropriate refund processing according to settlement means when cancelling at least some settlement after performing settlement processing by a plurality of settlement means.SOLUTION: An information processing device comprises: a settlement execution unit which performs settlement processing of an original amount using first settlement means used for payment of a first amount and second settlement means different from first settlement means; an acquisition unit which acquires a cancellation amount in settlement cancellation for cancelling at least part of the settlement processing; a return unit which performs return processing for returning the cancellation amount to a user by the first settlement means when the cancellation amount is less than or equal to the first amount; and a resettlement execution unit which executes cancellation processing of the settlement processing and resettlement processing associated with the settlement cancellation when the cancellation amount is over the first amount.SELECTED DRAWING: Figure 6

Description

[Technical field]

[0001] The present invention relates to an information processing device, method, and program. [Background technology]

[0002] 2. Description of the Related Art Conventionally, there is known a technique for simultaneously using a plurality of payment methods such as credit cards and points when purchasing a product (see, for example, Patent Document 1).

[0003] Patent document 1 discloses that by storing the payment amounts for each of a plurality of payment methods for each item being purchased, it becomes possible to understand how the plurality of payment methods were used for each purchased item, and if some items are canceled or returned after the product purchase process has been executed, a refund process is executed according to the payment method used to purchase the items. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2018-32247 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, if some products are returned after the product purchase process has been completed, there may be limitations on the refund process depending on the payment method used at the time of purchase. For example, if the payment was made with points, the refund can be made by returning the points corresponding to the returned products. In contrast, if the payment was made with a credit card, the refund must be made by canceling the entire payment and making a repayment for the products that are not returned. Therefore, if a return occurs when a payment is made with multiple payment methods, not to mention a single payment method, the process becomes complicated and it becomes difficult to execute an appropriate refund process.

[0006] The present invention has been made in consideration of the circumstances described above, and aims to provide an information processing device, method, and program that can execute an appropriate refund process according to the payment method when at least a portion of the payment is canceled after payment processing has been performed using multiple payment methods. [Means for solving the problem]

[0007] An information processing device as one embodiment of the present invention includes a payment execution unit that executes payment processing of an initial amount using a first payment means used to pay a first amount and a second payment means different from the first payment means, an acquisition unit that acquires a cancellation amount in a payment cancellation to cancel at least a part of the payment processing, a return unit that executes a refund process to return the cancellation amount to a user using the first payment means when the cancellation amount is less than or equal to the first amount, and a re-payment execution unit that executes a cancellation process of the payment processing and a re-payment process associated with the payment cancellation when the cancellation amount exceeds the first amount.

[0008] An information processing method which is one embodiment of the present invention includes executing a payment process for an initial amount using a first payment means used to pay a first amount and a second payment means different from the first payment means, obtaining a cancellation amount in a payment cancellation to cancel at least a portion of the payment process, executing a refund process to return the cancellation amount to the user by the first payment means when the cancellation amount is less than or equal to the first amount, and executing a cancellation process of the payment process and a re-payment process associated with the payment cancellation when the cancellation amount exceeds the first amount.

[0009] An information processing program which is one embodiment of the present invention causes a computer to execute a payment process for an initial amount using a first payment means used to pay a first amount and a second payment means different from the first payment means, obtain a cancellation amount in a payment cancellation to cancel at least a part of the payment process, and when the cancellation amount is less than or equal to the first amount, execute a refund process to return the cancellation amount to the user using the first payment means, and when the cancellation amount exceeds the first amount, execute a cancellation process of the payment process and a re-payment process associated with the payment cancellation. Effect of the Invention

[0010] According to the present invention, when at least a portion of payments is cancelled after payment processing has been performed using a plurality of payment methods, it is possible to perform an appropriate refund process according to the payment method. [Brief description of the drawings]

[0011] [Figure 1] 1 is a network diagram showing a schematic configuration of a payment management system. [Diagram 2] 11 is a diagram illustrating an example of a database stored in a storage device connected to the payment management server. [Diagram 3] 1 is a table illustrating an example of information stored in a user information database (DB). [Figure 4] 1 is a table illustrating information stored in a transaction information database (DB). [Diagram 5] 2 is a block diagram illustrating main functions of a payment management server (information processing device). FIG. [Figure 6] 13 is a flowchart showing a determination process in an amount change payment. [Figure 7] 13 is a table illustrating a refund scheme according to the cancellation amount and the payment source. [Figure 8] FIG. 11 is a sequence diagram showing a payment process when payment is made through a bank account. [Figure 9] FIG. 13 is a sequence diagram showing a payment process when payment is made with points. [Figure 10] FIG. 11 is a sequence diagram showing a payment process when payment is made by credit card. [Figure 11] FIG. 13 is a sequence diagram showing a payment process when payment is made with a credit card and points (when the cancellation amount does not exceed the point payment). [Figure 12] FIG. 13 is a sequence diagram showing a payment process when payment is made with a credit card and points (when the cancellation amount exceeds the point payment). [Figure 13] 13 is a table showing examples of refunds according to the settings of the payment method. [Figure 14] 13 is a table showing examples of refunds according to the settings of the payment method. [Figure 15] FIG. 13 is a diagram illustrating an example of a usage history screen displayed on a user terminal. [Figure 16] FIG. 13 is a diagram illustrating an example of a usage history details screen displayed on a user terminal. [Figure 17] FIG. 13 is a diagram illustrating an example of a usage history screen displayed on a user terminal. [Figure 18] FIG. 13 is a diagram illustrating an example of a usage history details screen displayed on a user terminal. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. The same elements are given the same reference numerals, and duplicated explanations will be omitted. In the following, a payment process for purchasing a product at a brick-and-mortar store will be described as an example, but the present embodiment can also be applied to a payment process at an electronic commerce site (a so-called online shop).

[0013] [Configuration of payment management system] Fig. 1 is a network diagram showing a schematic configuration of a payment management system including an information processing device according to an embodiment of the present invention. The payment management system (hereinafter also referred to as "this system") 1 is a system for providing and managing a payment service when a user (customer) purchases a product at an affiliated store of this system 1. Here, in this specification, "product" includes not only a product as a physical object but also a service (e.g., provision of a meal at a restaurant), and "purchase" includes not only paying the price for a product but also paying the price for a service. Furthermore, "return" includes not only returning a physical product to a store but also canceling a service that has been ordered.

[0014] As shown in Fig. 1, the payment management system 1 includes a user terminal 10, an affiliated store terminal 20, a payment management server 30, multiple payment servers 50A-50D, and a payment gateway (PGW) server 60. The user terminal 10, the affiliated store terminal 20, the payment management server 30, the payment servers 50A-50D, and the PGW server are connected to a communication network N.

[0015] The communication network N includes a communication network capable of transmitting and receiving information between devices connected to the communication network N. The communication network N may be, for example, the Internet, a LAN, a dedicated line, a telephone line, an in-house network, a mobile communication network, Bluetooth (registered trademark), WiFi (Wireless Fidelity), other communication lines, or a combination thereof, and may be wired or wireless. In addition, the user terminal 10 and the affiliated store terminal 20 may transmit and receive information by near field communication (NFC).

[0016] The user terminal 10 is a terminal device used by a user, and can be configured, for example, by a general-purpose portable computer such as a smartphone, a tablet terminal, etc. The user terminal 10 has, as its physical configuration, a communication interface, an input device, a display device, a memory, and a processor, and functions as the user terminal 10 by the processor executing a program stored in the memory.

[0017] As a specific example, the user terminal 10 communicates with the payment management server 30 and transmits information for user registration and various settings to receive services provided by the payment management server 30. The user terminal 10 also executes a predetermined operation for payment at the affiliated store. For example, the user terminal 10 displays a payment code (barcode or two-dimensional code) on a screen to be read by the affiliated store terminal 20. The user terminal 10 may also have an imaging function, in which case the user terminal 10 can execute payment by reading a two-dimensional code for payment displayed at the affiliated store. Alternatively, the user terminal 10 can execute payment by transmitting and receiving information between the user terminal 10 and the affiliated store terminal 20 via short-range wireless communication.

[0018] Examples of payment methods that can be used in this embodiment include credit cards (hereinafter sometimes abbreviated as "Credit Cards"), electronic money, points, payment from an account at an affiliated bank, and direct debit from an account at a bank other than an affiliated bank (so-called debit cards). These payment methods can be used by the user after completing procedures such as issuing a credit card and opening a bank account in advance, and then registering them in the payment management server 30 via the user terminal 10. Note that payment from an account is a specific payment method that allows for direct payment from a bank account balance.

[0019] The affiliated store terminal 20 is a terminal device used for settlement at an affiliated store, and can be configured using, for example, a general-purpose computer such as a smartphone, a tablet terminal, or a personal computer (PC), or a dedicated cash register terminal. A card reader device, a barcode reader, etc. are connected to the affiliated store terminal 20 as necessary. The affiliated store terminal 20 includes a communication interface, an input device, a display device, a memory, and a processor, and functions as the affiliated store terminal 20 by the processor executing a program stored in the memory.

[0020] As a specific example, the affiliated store terminal 20 communicates with the payment management server 30 and transmits information for affiliated store registration and various settings for using the present system 1. The affiliated store terminal 20 also performs payment with the payment management server 30 by transmitting payment information when a user purchases a product to the payment management server 30. The payment information may include, in addition to the price of the product, user information acquired by the affiliated store terminal 20 reading a payment code displayed on the screen of the user terminal 10 or performing short-range wireless communication with the user terminal 10, and information about the affiliated store.

[0021] In addition, when the user terminal 10 makes a payment by reading a two-dimensional payment code displayed at an affiliated store, payment information is sent from the user terminal 10 to the payment management server 30, and the payment is executed based on this payment information.

[0022] The payment management server 30 is a server device (information processing device) for providing a payment service when a user purchases a product at an affiliated store, and can be configured with a general-purpose computer. The payment management server 30 may be configured with one computer, or may be configured with multiple computers distributed over a communication network N.

[0023] As shown in Fig. 1, the payment management server 30 includes a communication unit 31, a control unit 32, and a storage unit 33. The communication unit 31 is a communication interface for connecting the payment management server 30 to a communication network N and transmitting and receiving information between other devices connected to the communication network N. The control unit 32 is configured using a central processing unit (CPU). The storage unit 33 is configured using memories such as ROM and RAM, and storage devices such as a hard disk drive, and stores programs to be executed by the control unit 32, parameters used during execution of the programs, etc. The payment management server 30 is also connected to a storage device 40 configured using a hard disk drive, etc.

[0024] The payment management server 30 manages the user information received from the user terminal 10 and the affiliated store information received from the affiliated store terminal 20 in a database stored in the storage device 40, and executes various payment-related processes based on this information in response to a request from the affiliated store terminal 20. In addition, the payment management server 30 provides the user terminal 10 with information such as a usage statement, balance, and monthly usage limit in response to a request from the user terminal 10. The detailed functions of the payment management server 30 will be described later.

[0025] Each of the payment servers 50A-50D is a server device that provides a predetermined payment method, and can be configured by a general-purpose computer. Each of the payment servers 50A-50D may be configured by one computer, or may be configured by multiple computers distributed over the communication network N. Each of the payment servers 50A-50D executes various processes related to payment in response to a request from the payment management server 30.

[0026] In this embodiment, the payment servers 50A to 50D provide different payment methods. For example, the payment server 50A executes payment by credit card. The payment server 50B executes payment by electronic money. The payment server 50C executes payment by points. The payment server 50D executes payment by payment to an account at an affiliated bank.

[0027] Each of the PGW servers 60 is a server device that provides a payment agency service, and can be configured with a general-purpose computer. The PGW server 60 executes authorization in response to a request from the payment management server 30. Although only one PGW server is shown in Fig. 1, multiple PGW servers 60 may be provided.

[0028] [Database configuration] Fig. 2 is a diagram illustrating an example of databases stored in storage device 40. As shown in Fig. 2, storage device 40 stores a user information database (DB) 41, an affiliated store information database (DB) 42, and a transaction information database (DB) 43.

[0029] FIG. 3 is a table illustrating information stored in the user information database 41. The user information database 41 is a database that stores information about users (user information) including user registration information, payment method information, and payment method setting information. The user registration information is information about the user himself / herself, and includes information such as the user ID, the user's name, address, and email address. The payment method information includes information such as the user's credit card number, electronic money registration number, and affiliated bank account number. The payment method setting information is information for setting one or more payment methods actually used among multiple payment methods and conditions including the priority order between the payment methods used, and includes information such as the payment method to be used as the payment source, whether or not points are used (all used / partially used / not used), electronic money balance, number of points held, and number of limited-time points held. Here, with regard to whether or not points are used, "partial use" refers to the user specifying the number of points to be used in advance and using the points. The user can set the payment method setting information in the payment process through the user terminal 10. The user can also change the payment method setting information (payment source and whether or not points are used) at any time through the user terminal 10. In addition, the electronic money balance, number of points held, and number of limited-time points held will be updated as changes occur.

[0030] Here, the points may be classified into points with no expiration date (unlimited payment method) and points with a limited time period (limited time payment method). When a user has both points with no expiration date and points with a limited time period, the points with limited time period may be set to be used preferentially.

[0031] The affiliated store information database 42 is a database that stores information about affiliated stores (affiliated store information). The affiliated store information includes the affiliated store ID, the affiliated store name, address, the representative's name, contact information, the bank account number to which the payment amount is to be deposited, and other information.

[0032] FIG. 4 is a table illustrating information stored in transaction information database 43. Transaction information database 43 is a database that stores information (transaction information) relating to transactions conducted between users and affiliated stores. Transaction information includes information such as the transaction type (payment, payment cancellation, repayment), the date and time of the transaction, the affiliated store ID of the affiliated store that conducted the transaction and the user ID of the user, the payment amount, and a breakdown by payment method. Here, when the transaction type is payment or repayment, the payment method in transaction information database 43 is recorded according to the setting information of the user's payment method set in user information database 41 at the time of the transaction.

[0033] [Settlement management server configuration] Fig. 5 is a block diagram illustrating the main functions of the payment management server 30. The functional units realized by the control unit 32 shown in Fig. 1 executing the program stored in the storage unit 33 include a reception unit 320, an information management unit 321, a setting unit 322, a payment execution unit 323, a cancellation amount acquisition unit 324, a determination unit 325, a refund unit 326, a re-payment execution unit 327, and a display control unit 328.

[0034] When an access request is made from a device connected to the payment management server 30 via the communication network N, the reception unit 320 receives the access by performing authentication or the like, and acquires information from the device.

[0035] The information management unit 321 records the information acquired by the reception unit 320 in a database stored in the storage device 40 and manages the information.

[0036] Based on information received from the user terminal 10, the setting unit 322 stores setting information for setting the user's payment method, and changes the stored setting information.

[0037] When a product purchase transaction occurs between a user and an affiliated store, the payment execution unit 323 executes payment processing in accordance with the payment method set in the user information database 41 based on the information received from the user terminal 10 or the affiliated store terminal 20.

[0038] When a payment cancellation (hereinafter also referred to as "amount change payment") occurs between a user and an affiliated store to cancel at least a part of a payment process that has already been executed, the cancellation amount acquisition unit 324 acquires the cancellation amount for the amount change payment based on information received from the user terminal 10 or the affiliated store terminal 20. Here, an amount change payment occurs when a user returns or cancels at least some of the products after purchasing multiple products. The cancellation amount is the difference between the payment amount at the time of the initial payment and the payment amount at the time of the amount change payment, and is the amount (refund amount) corresponding to the returned or canceled products.

[0039] The determination unit 325 determines whether the cancelled amount acquired by the cancelled amount acquisition unit 324 is equal to or less than the payment amount (first amount) paid by the first payment means. Here, the first payment means refers to a payment means that allows the transaction details to be changed afterwards, i.e., a payment means that allows a part of the payment amount to be refunded after the payment, and includes electronic money, points, and payment to an account of an affiliated bank. On the other hand, the second payment means refers to a payment means that does not allow the transaction details to be changed, i.e., a payment means that does not allow a part of the payment amount to be refunded after the payment, and the whole payment must be cancelled and repaid, and includes credit cards and account withdrawals (so-called debit cards) of banks other than the affiliated banks.

[0040] When the cancellation amount is equal to or less than the first amount, the refund unit 326 executes a refund process to refund the cancellation amount to the user by the first payment means used for the original payment.

[0041] When the cancelled amount exceeds the first amount, the re-payment processing unit 327 executes a process for cancelling the payment process executed by the payment execution unit 323, and executes a re-payment process associated with the cancellation of the payment.

[0042] The display control unit 328 executes control to display predetermined screens such as a registration screen, a setting screen, and a usage history screen on the screen of the user terminal 10 or the affiliated store terminal 20.

[0043] Fig. 6 is a flowchart showing the judgment process in the amount change settlement. Fig. 7 is a table showing an example of a refund scheme according to the cancellation amount and the payment source (payment means). Fig. 7 shows a case where the payment amount at the time of the initial settlement is 10,000 yen, and the payment amount at the time of the amount change settlement is 6,000 yen (cancellation amount 4,000 yen).

[0044] When an amount change payment is made, first, the cancellation amount acquisition unit 324 acquires the cancellation amount (step S11). Next, the judgment unit 325 judges whether the cancellation amount is equal to or less than the payment amount by the first payment means (electronic money, points, account payment) (step S12). In examples 1 to 3 shown in FIG. 7, the cancellation amount (4,000 yen) is equal to or less than the payment amount by the first payment means. In contrast, in example 4, the cancellation amount exceeds the payment amount by the first payment means (2,000 yen points).

[0045] If the cancelled amount is equal to or less than the payment amount by the first payment means (step S12: Yes), the refund unit 326 refunds the cancelled amount by the first payment means (step S13). Specifically, if payment is made by direct deposit as in example 1, 4,000 yen is refunded (transferred) to the account. Also, if payment is made with electronic money as in example 2, 4,000 yen worth of electronic money is refunded. If points and limited-time points are used as in example 3, 4,000 yen worth of points or limited-time points is refunded.

[0046] On the other hand, if the cancelled amount exceeds the payment amount by the first payment means (step S12: No), the re-payment execution unit 327 cancels the original payment process and executes the re-payment process (step S14). Specifically, in the case of example 4, the original payment process of 10,000 yen is cancelled, and a re-payment of 6,000 yen, which is 10,000 yen minus the cancelled amount of 4,000 yen, is executed. The re-payment process is executed according to the payment means (re-payment means) set in the setting information at the time of the re-payment process.

[0047] [Operation of payment management system] The operation of the present system 1 will be explained in detail below for each payment method. 8 is a sequence diagram showing the payment process when payment is made by account payment at an affiliated bank. Here, it is assumed that only account payment at an affiliated bank is set as a payment method in the user information database 41.

[0048] When a user purchases a product at an affiliated store and payment processing is executed at the affiliated store terminal 20 (step S101), the affiliated store terminal 20 transmits a request to execute payment processing (e.g., 10,000 yen) to the payment management server 30 (step S102). In response to this, the payment management server 30 executes the payment processing (step S103) and transmits a request for debit processing (e.g., 10,000 yen) from the user's account to the payment server 50D of the affiliated bank (step S104). The payment server 50D debits the specified amount from the account (step S105) and notifies the payment management server 30 of the debit result (step S106). The payment management server 30 notifies the affiliated store terminal 20 of the payment result (step S107). This completes the payment processing.

[0049] When a user returns or cancels a purchased item and an amount change payment (e.g., change to 6,000 yen) occurs at the affiliated store terminal 20 (step S111), the affiliated store terminal 20 sends a request to execute the amount change payment process to the payment management server 30 (step S112). In response, the payment management server 30 executes the judgment and amount change payment process (step S113) and notifies the affiliated store terminal 20 of the amount change acceptance result (step S114).

[0050] In step S113, the settlement management server 30 acquires the cancellation amount and executes processing according to the judgment result for the cancellation amount, as described with reference to Fig. 6. In the example shown in Fig. 8, the cancellation amount (10,000 yen - 6,000 yen = 4,000 yen) is less than the payment amount (10,000 yen) by the direct deposit (first payment means) (step S12 in Fig. 6: Yes). Therefore, the settlement management server 30 returns the cancellation amount and transmits a request for transfer processing of the cancellation amount to the settlement server 50D (step S115). In response to this, the settlement server 50D transfers the specified amount to the user's account (step S116) and notifies the settlement management server 30 of the transfer result (step S117).

[0051] When the settlement management server 30 receives an inquiry about the result from the affiliated store terminal 20 (step S118), it notifies the affiliated store terminal 20 of the amount change result that the refund amount has been transferred (step S119). This completes the partial refund process.

[0052] 9 is a sequence diagram showing a payment process when payment is made with points. Here, it is assumed that only the use of points is set as a payment method in the user information database 41.

[0053] When the payment process is executed in the affiliated store terminal 20 (step S201), the affiliated store terminal 20 transmits a request to execute the payment process (e.g., 10,000 yen) to the payment management server 30 (step S202). In response to this, the payment management server 30 executes the payment process (step S203), and transmits a request for authorization and payment process (e.g., 10,000 yen) to the PGW server 60 (step S204). The PGW server 60 transmits a request for authorization and payment process (same as above) to the points payment server 50C (step S205). In response to this, the payment server 50C executes the authorization, settles the specified amount with points (step S206), and notifies the PGW server 60 of the settlement result (step S207). The PGW server 60 notifies the payment result to the payment management server 30 (step S208), and the payment management server 30 notifies the member store terminal 20 of the payment result (step S209). This completes the payment process.

[0054] When an amount change payment (e.g., change to 6,000 yen) occurs at the affiliated store terminal 20 (step S211), the affiliated store terminal 20 transmits an execution request for amount change payment processing to the payment management server 30 (step S212). In response to this, the payment management server 30 executes judgment and amount change payment processing (step S213) and notifies the affiliated store terminal 20 of the amount change acceptance result (step S214).

[0055] In the example shown in Fig. 9, the cancellation amount (4,000 yen) is less than the payment amount (10,000 yen) by point payment (first payment means) (step S12 in Fig. 6: Yes). Therefore, the payment management server 30 returns the cancellation amount and sends a partial point return request (4,000 yen) to the payment server 50C (step S215). In response, the payment server 50C returns points equivalent to the specified amount (step S216) and notifies the payment management server 30 of the return result (step S217).

[0056] When the settlement management server 30 receives an inquiry about the result from the affiliated store terminal 20 (step S218), it notifies the affiliated store terminal 20 of the amount change result that the points have been returned (step S219). This completes the partial refund process.

[0057] The sequence when electronic money is used at the time of payment is also similar to that shown in Fig. 9. The sequence when points and electronic money are used at the time of payment is also basically similar to that shown in Fig. 9. However, in step S215, the payment management server 30 requests the point payment server 50C to return points so that points are returned first, and if the returned points alone are insufficient to cover the cancellation amount, the payment management server 30 requests the electronic money payment server 50B to return the shortfall.

[0058] 10 is a sequence diagram showing the payment process when payment is made by credit card. Here, it is assumed that only credit cards are set as a payment method in the user information database 41.

[0059] When the member store terminal 20 executes the payment process (step S301), the member store terminal 20 transmits a request to execute the payment process (e.g., 10,000 yen) to the payment management server 30 (step S302). In response to this, the payment management server 30 executes the payment process (step S303), and transmits a request for authorization and payment process (e.g., 10,000 yen) to the PGW server 60 (step S304). The PGW server 60 transmits a request for authorization and payment process (same as above) to the credit card payment server 50A (step S305). In response to this, the payment server 50A executes the authorization, settles the specified amount by credit card (step S306), and notifies the PGW server 60 of the payment result (step S307). The PGW server 60 notifies the payment result to the payment management server 30 (step S308), and the payment management server 30 notifies the member store terminal 20 of the payment result (step S309). This completes the processing at the time of payment.

[0060] When an amount change payment (e.g., change to 6,000 yen) occurs at the affiliated store terminal 20 (step S321), the affiliated store terminal 20 transmits an execution request for amount change payment processing to the payment management server 30 (step S322). In response to this, the payment management server 30 executes judgment and amount change payment processing (step S323) and notifies the affiliated store terminal 20 of the amount change acceptance result (step S324).

[0061] In the example shown in Fig. 10, only a credit card (second payment method) was used at the time of payment, and the cancellation amount (4,000 yen) exceeds the payment amount (0 yen) by the first payment method (step S12: No in Fig. 6). Therefore, the payment management server 30 cancels the original payment process and re-settles with the changed amount.

[0062] When the payment management server 30 transmits a payment cancellation request to the PGW server 60 (step S325), the PGW server 60 transmits a payment cancellation request to the payment server 50A (step S326). In response to this, the payment server 50A cancels the payment (step S327) and transmits the cancellation result to the PGW server 60 (step S328). The PGW server 60 notifies the payment management server 30 of the cancellation result (step S329).

[0063] Next, the payment management server 30 transmits a request for authorization and payment processing to the PGW server 60 with the changed payment amount (6,000 yen) (step S330). The sequence of the re-payment processing (steps S330 to S334) is the same as the sequence of the payment processing (steps S304 to S308) except that the payment amount is different.

[0064] When the payment management server 30 receives an inquiry about the result from the affiliated store terminal 20 (step S335), it cancels the original payment and notifies the affiliated store terminal 20 of the amount change result that the payment has been rescheduled (step S336). This completes the partial refund process.

[0065] 11 is a sequence diagram showing the payment process when payment is made with a credit card and points (when the cancellation amount does not exceed the point payment). Here, it is assumed that a credit card and points (all used) are set as the payment method in the user information database 41, and the number of points held is 8,000 yen.

[0066] When the payment process is executed in the affiliated store terminal 20 (step S401), the affiliated store terminal 20 transmits a request to execute the payment process (for example, 10,000 yen) to the payment management server 30 (step S402). In response to this, the payment management server 30 executes the payment process (step S403), transmits an authorization and payment process request for the point payment amount of 8,000 yen to the PGW server 60 (step S404), and transmits an authorization and payment process request for the credit card payment amount of 2,000 yen to the PGW server 60 (step S409). The sequence of the point payment (steps S404 to S408) is the same as steps S204 to S208 shown in FIG. 9. Moreover, the sequence of the credit card payment (steps S409 to S413) is the same as steps S304 to S308 shown in FIG. 10. The payment management server 30 notifies the affiliated store terminal 20 of the points and the result of the payment by credit card (step S414). This completes the processing at the time of payment.

[0067] When an amount change payment (e.g., change to 6,000 yen) occurs at the affiliated store terminal 20 (step S421), the affiliated store terminal 20 transmits an execution request for amount change payment processing to the payment management server 30 (step S422). In response to this, the payment management server 30 executes judgment and amount change payment processing (step S423) and notifies the affiliated store terminal 20 of the amount change acceptance result (step S424).

[0068] In the example shown in Fig. 11, the cancellation amount (4,000 yen) is less than the payment amount (8,000 yen) by point payment (first payment method) (step S12 in Fig. 6: Yes). Therefore, the payment management server 30 decides to refund the cancellation amount and sends a partial point refund request (4,000 yen) to the payment server 50C (step S425). In response, the payment server 50C refunds points equivalent to the specified amount (step S426) and notifies the payment management server 30 of the refund result (step S427).

[0069] When the settlement management server 30 receives an inquiry about the result from the affiliated store terminal 20 (step S428), it notifies the affiliated store terminal 20 of the amount change result that the points have been returned (step S429). This completes the partial refund process.

[0070] 12 is a sequence diagram showing the payment process when payment is made with a credit card and points (when the cancellation amount exceeds the point payment). Here, it is assumed that a credit card and points (all used) are set as the payment method in the user information database 41, and the number of points held is 2,000 yen.

[0071] Steps S401 to S414 shown in Fig. 12 are the same as steps S401 to S414 shown in Fig. 11. However, it is different from the example in Fig. 11 in that the payment amount using points is 2,000 yen and the payment amount using a credit card is 8,000 yen.

[0072] When an amount change payment (e.g., change to 6,000 yen) occurs at the affiliated store terminal 20 (step S441), the affiliated store terminal 20 transmits an execution request for amount change payment processing to the payment management server 30 (step S442). In response to this, the payment management server 30 executes judgment and amount change payment processing (step S443) and notifies the affiliated store terminal 20 of the amount change acceptance result (step S444).

[0073] In the example shown in Fig. 12, the cancellation amount (4,000 yen) exceeds the payment amount (2,000 yen) by point payment (first payment method) (step S12:Ns in Fig. 6). Therefore, the payment management server 30 cancels the entire original payment process and re-settles with the changed amount.

[0074] When the payment management server 30 transmits a request to cancel the point payment to the payment server 30C, the payment server 30C cancels the payment (step S445) and transmits a cancellation result to the payment management server 30 (step S446). That is, the full amount of points used in the original payment is returned.

[0075] On the other hand, when the payment management server 30 transmits a request to cancel the credit card payment to the PGW server 60 (step S450), the PGW server 60 transmits a request to cancel the credit card payment to the payment server 50A (step S451). The payment server 50A cancels the payment (step S452) and transmits the cancellation result to the PGW server 60 (step S453). The PGW server 60 notifies the payment management server 30 of the cancellation result (step S454).

[0076] Next, the payment management server 30 sends to the PGW server 60 a request for authorization and payment processing with the point payment amount set to 2,000 yen (step S455), and also sends to the PGW server 60 a request for authorization and payment processing with the credit card payment amount set to 4,000 yen (step S460). The sequence of point payment (steps S455 to S459) is the same as steps S204 to S208 shown in FIG. 9. Also, the sequence of credit card payment (steps S460 to S464) is the same as steps S304 to S308 shown in FIG. 10. Note that if the number of points held at the time of repayment has been changed from the number of points held at the time of payment, the processes for point payment and credit card payment are executed based on the number of points held at the time of repayment.

[0077] When the payment management server 30 receives an inquiry about the result from the affiliated store terminal 20 (step S465), it cancels the original payment and notifies the affiliated store terminal 20 of the amount change result that the payment has been rescheduled (step S466). This completes the partial refund process.

[0078] The sequence when electronic money is used instead of points at the time of payment is also similar to that shown in Figures 11 and 12. The sequence when a debit card is used instead of a credit card at the time of payment is also similar to that shown in Figures 11 and 12.

[0079] Here, the user's payment method can be changed between the initial payment and the amount change payment. That is, the payment management server 30 executes the initial payment using the payment method set in the setting information, and executes the repayment using the payment method set in the setting information at the time the repayment process is executed in the amount change payment. Specific examples of refunds are explained below. Figures 13 and 14 are tables showing examples of refunds according to the setting of the payment method.

[0080] In the example shown in Fig. 13, the setting information indicating the payment method for the initial payment has a credit card set as the payment source and point usage set to "Do not use." Therefore, at the time of payment on April 1, a payment of 10,000 yen was made by credit card.

[0081] Then, on May 1st, a cancellation was made with a change in the amount of 4,000 yen. In the settings information at the time of the repayment process, point usage was set to "all used" and the number of points held was 3,000 yen. At this time, in the amount change payment, the original payment of 10,000 yen by credit card is canceled, and in the repayment process, 3,000 yen of the payment amount of 6,000 yen is paid with points, and the remaining 3,000 yen is paid by credit card.

[0082] In the example shown in Figure 14, at the time of payment on April 1, the payment source was a credit card, point usage was set to "all used," and the number of limited-time points held with an expiration date of the last day of April was 2,000 yen. Therefore, on April 1, of the payment amount of 10,000 yen, 2,000 yen was paid with limited-time points, and the remaining 8,000 yen was paid with a credit card.

[0083] Later, when a cancellation of a 4,000 yen change in payment occurred on May 1, the cancellation amount exceeded the points payment amount, so the original payment process was canceled. In other words, the 2,000 yen limited-time points were returned and the 8,000 yen payment made by credit card was canceled. However, since the limited-time points had already expired on May 1, the 2,000 yen limited-time points expired at the same time as they were returned. Therefore, the entire changed payment amount of 6,000 yen is paid by credit card.

[0084] Here, when points without an expiration date and time-limited points are used together at the time of the initial payment, if the amount change payment is to be dealt with by refunding the cancelled amount (see step S13 in FIG. 6), the points without an expiration date may be returned in preference to the time-limited points. Also, when electronic money and points are used together at the time of the initial payment, if the amount change processing is to be dealt with by refunding the cancelled amount (see above), the points may be returned in preference to the electronic money.

[0085] Incidentally, when an initial payment is cancelled in an amount change payment and a repayment process is to be executed, the repayment process is executed immediately in principle. However, there may be a change in the user's payment means usage status between the initial payment and the repayment process, and the repayment process may not be executed with the set payment means. For example, this may occur when the authorization limit of a credit card is insufficient for the repayment amount, or when the balance of a bank account or electronic money is insufficient. In such a case, the repayment process may be executed after the authorization limit is restored, the balance is restored, or the payment becomes possible.

[0086] In addition, if the payment method set in the setting information at the time of the repayment process cannot be used for repayment, and another payment method is available, the repayment process may be executed using the other payment method. For example, if the setting information at the time of the repayment process sets a bank account payment as the payment method, but the account balance is insufficient for the payment amount at the time of the repayment process, and instead the electronic money balance is equal to or exceeds the payment amount, the electronic money can be used for alternative payment.

[0087] Fig. 15 is a diagram illustrating a usage history screen displayed on the user terminal 10. Fig. 16 is a diagram illustrating a usage history detail screen displayed on the user terminal 10, showing a part of the details of the usage statement shown in Fig. 15 in detail. Fig. 17 is a diagram illustrating a usage history screen displayed on the user terminal 10. Fig. 18 is a diagram illustrating a usage history detail screen displayed on the user terminal 10, showing a part of the details of the usage statement shown in Fig. 17 in detail.

[0088] The payment management server 30 can transmit the usage history screen to the user terminal 10 and display it periodically or whenever required by a request from the user terminal 10. As shown in Fig. 15 and Fig. 17, the usage history screens A1 and A3 display the history of payments made within a predetermined period (e.g., one month).

[0089] When an operation (e.g., a tap operation) is performed to select the display field a10, a30 of a desired payment on these usage history screens A1, A3, the user terminal 10 transmits a request for detailed information on the payment to the payment management server 30. In response, the payment management server 30 transmits the usage history detail screens A2, A4 relating to the selected payment to the user terminal 10 for display, as exemplified in Figures 16 and 18. The usage history detail screens A2, A4 corresponding to each payment display detailed information such as the date and time of the payment, the amount, the breakdown, the name of the affiliated store, etc.

[0090] In Figure 15, as shown in display field a11 of the usage history screen A1, the payment for which a later amount change occurred is grayed out and the text "CANCELLED" is displayed. Then, in display field a12 of the amount change payment corresponding to the canceled payment, the text "Amount Changed" is displayed along with the payment amount after the change, "800 yen," and the canceled amount, "700 yen."

[0091] In addition, the usage history details screen for the amount change payment displays information on the original payment process, information on the payment cancellation (amount change payment) corresponding to the payment process, and information on the refund process or repayment process corresponding to the amount change payment as payment history. Of these, the information on the amount change payment may be the final payment amount minus the cancellation amount. When the user selects display column a12 from the display column a10 of the desired payment on the usage history screen A1 illustrated in FIG. 15, the usage history details screen A2 illustrated in FIG. 16 is displayed on the user terminal 10.

[0092] For example, in Fig. 16, display field a21 shows that the original payment amount of "1,500 yen" was paid to an affiliated bank account on November 9th. Display field a22 shows that a change in the amount was made on December 30th, and that the payment of the cancellation amount of "700 yen" of the original payment amount was cancelled (the transaction involved a transfer to the account). Display field a23 shows the final payment amount of "800 yen" after the change in the amount was paid.

[0093] In addition, when multiple amount-change payments occur for an initial payment, as shown in FIG. 17, the display field a31 of the initial payment and the display field a32 of the changed amount-change payment are grayed out and the text "CANCELLED" is displayed on the usage history screen A3. Then, the display field a33 of the final amount-change payment related to these payments displays the final payment amount "280 yen" together with the text "Amount Changed", as well as the amount "420 yen" that was most recently canceled. When the user selects the display field a33 from the display fields a30 of the desired payment on the usage history screen A3 illustrated in FIG. 17, the usage history details screen A4 illustrated in FIG. 18 is displayed on the user terminal 10.

[0094] In the usage history details screen A4 for these payments, the display area a41 shows that the initial payment amount "1,500 yen" was paid on November 9th, with the breakdown being "280 yen" in electronic money, "420 yen" in points, and "800 yen" in credit card. In addition, the display areas a42 and a43 show that the cancellation process and repayment process were executed. The display area a42 shows that a change in the amount was subsequently made at 15:20 on December 30th, and the payment of "800 yen" by credit card was cancelled. Furthermore, the display area a43 shows that at the same time as the cancellation of the payment, a repayment of 700 yen was made using points (420 yen) and electronic money (280 yen).

[0095] Furthermore, display field a44 shows that another change in the amount was made at 4:30 p.m. on the same day, and points of 420 yen were returned. Display field a45 shows the final payment amount of 280 yen after the change in the amount.

[0096] Here, when an amount change settlement occurs, the same slip number as the slip number assigned to the (initial) settlement before the change may be assigned to the refund process of the cancelled amount or the cancellation process of the settlement, and a new slip number may be assigned to the final settlement result after the refund or the re-payment process after the cancellation. For example, the same slip number as the initial payment shown in the display column a41 is assigned to the cancellation process of the card settlement shown in the display column a42. Also, a new slip number is assigned to the re-payment process by points and electronic money shown in the display column a43. On the other hand, the same slip number as the payment process before the refund shown in the display column a43 is assigned to the point refund process shown in the display column a44, and a new slip number is assigned to the final settlement result after the refund. By managing the slip numbers in this way, the link between each process related to the amount change settlement becomes clear, and the user can easily understand the related transaction contents.

[0097] The present invention is not limited to the above-described embodiment, and can be implemented in various other forms without departing from the scope of the present invention. Therefore, the above-described embodiment is merely an example in all respects and should not be interpreted as being restrictive. For example, the order of each of the above-described processing steps can be arbitrarily changed or executed in parallel as long as no contradiction occurs in the processing content. [Explanation of symbols]

[0098] 1...payment management system (this system), 10...user terminal, 20...membered store terminal, 30...payment management server, 31...communication unit, 32...control unit, 33...storage unit, 40...storage device, 41...user information database, 42...membered store information database, 43...transaction information database, 50A to 50D...payment server, 60...payment agent server (PGW server), 320...reception unit, 321...information management unit, 322...setting unit, 323...payment execution unit, 324...cancellation amount acquisition unit, 325...determination unit, 326...return unit, 327...repayment execution unit, 328...display control unit

Claims

1. a payment execution unit that executes a payment process for the initial amount using a first payment means used for paying a first amount and a second payment means different from the first payment means; An acquisition unit that acquires a cancellation amount in a settlement cancellation for canceling at least a part of the settlement process; a refund unit that executes a refund process to refund the cancellation amount to the user by the first settlement means when the cancellation amount is equal to or less than the first amount; a re-payment execution unit that executes a cancellation process of the payment process and a re-payment process associated with the cancellation of the payment when the cancellation amount exceeds the first amount; An information processing device comprising:

2. The re-payment process is a payment process of an amount obtained by subtracting the cancellation amount from the original amount. The information processing device according to claim 1 .

3. A setting unit capable of setting setting information of a payment method, the re-payment execution unit executes the re-payment process using a re-payment means that is a payment means set in the setting information at the time of executing the re-payment process; The information processing device according to claim 1 .

4. the re-payment execution unit, when the re-payment process cannot be executed immediately in the re-payment means, executes the re-payment process after the re-payment means becomes able to execute the payment. The information processing device according to claim 3 .

5. the re-payment execution unit executes the re-payment process using another payment means when the re-payment process cannot be executed in the re-payment means; The information processing device according to claim 3 .

6. The first payment means includes an unlimited time payment means with no time limit and a fixed time limit payment means with a time limit, The refund unit executes the refund process by prioritizing the non-time-limited payment means among the first payment means over the time-limited payment means. The information processing device according to claim 1 .

7. The first payment means includes a time-limited payment means having a fixed term, when the payment execution unit executes the payment process using the fixed-term payment means and the return unit returns at least a portion of the cancelled amount using the fixed-term payment means, if the fixed-term payment means used in the payment process has expired, the fixed-term payment means to be returned is invalidated. The information processing device according to claim 1 .

8. outputting, to a user terminal, information on the payment process, information on a payment cancellation corresponding to the payment process, and information on a refund process or a re-payment process corresponding to the payment cancellation as a payment history; The information processing device according to claim 1 .

9. The first payment means includes points and electronic money, and the payment process includes a payment process using both the points and the electronic money. The information processing device according to claim 1 .

10. executing a payment process for the initial amount using a first payment means used for paying the first amount and a second payment means different from the first payment means; Obtaining a cancellation amount in a settlement cancellation for canceling at least a part of the settlement process; When the cancellation amount is equal to or less than the first amount, executing a refund process to refund the cancellation amount to the user by the first settlement means; When the cancellation amount exceeds the first amount, executing a cancellation process of the settlement process and a re-settlement process associated with the cancellation of the settlement; An information processing method comprising:

11. executing a payment process for the initial amount using a first payment means used for paying the first amount and a second payment means different from the first payment means; Obtaining a cancellation amount in a settlement cancellation for canceling at least a part of the settlement process; When the cancellation amount is equal to or less than the first amount, executing a refund process to refund the cancellation amount to the user by the first settlement means; When the cancellation amount exceeds the first amount, executing a cancellation process of the settlement process and a re-settlement process associated with the cancellation of the settlement; An information processing program that causes a computer to execute the above.

Images