JP5117072B2 - Payment processing system, payment processing method, and payment processing program - Google Patents

Description

  The present invention relates to a payment processing system, a payment processing method, and a payment processing program for performing processing related to fee payment using a multi-payment service.

  Payment of utility bills, etc. may be made using a bill at a bank counter. In this case, it may be necessary to wait in turn at the user's window. In addition, financial institutions had to perform window processing, which was troublesome and inefficient. Therefore, a payment method capable of improving the efficiency of such fee payment has been studied (for example, see Patent Document 1).

  In the invention described in Patent Document 1, the financial institution center accepts a payment request including a designation of a payee, a customer identification code, and a confirmation code from a communication device such as a user terminal, and makes an inquiry according to the payment request. To the payee's storage center. If the inquiry result received from the storage center is appropriate, the financial institution center accepts the payment instruction by presenting the payment details to the payer. The financial institution center transfers funds from the payer's account in accordance with the user's payment instruction. In this technique, since the user can pay the fee through his / her user terminal, convenience for the user is improved.

Such a payment method is currently realized as a multi-payment service. In this multi-payment service, a storage institution that is a fee payment destination and a financial institution that is a fee payment port are connected via a dedicated network. Via this network, the payment information of the user in the financial institution is immediately transmitted to the storage institution. Therefore, the consumption operation can be automatically performed immediately in the storage engine. In addition, there is an advantage that financial offices can reduce the storage work and the sending work.
Japanese Patent Laid-Open No. 2002-92323 (FIGS. 1, 5 and 6)

  By the way, when using a multi-payment service, identification information (multi-payment identifier) for specifying payment is required. This multi-payment identifier includes a storage institution number for specifying a payee, and a customer number and a confirmation number for specifying a payer and payment contents in the storage institution. Here, the storage organization number is a 5-digit number, the customer number is a maximum 20-digit number, and the confirmation number is a 6-digit number.

  For this reason, when using a multi-payment service, it is necessary to input a maximum of 31 numbers. As described above, it is troublesome for the user to input a large number of numbers, and it may cause an input error.

  The present invention has been made in view of the above-described problems, and its purpose is to simplify the input of identification information used in payment processing, thereby improving the convenience of the user, the payment processing method, and the payment processing method. To provide a payment processing program.

In order to solve the above-mentioned problems, the invention described in claim 1 includes a storage institution identifier for specifying a payment destination in a multi-payment service in association with a user identifier for specifying a user and a payment specifying code for specifying payment contents. A system including a usage history data storage unit that records usage history, and a control unit that accepts payment using a multi-payment service, wherein the control unit uses a multi-payment service from a user terminal. A payee information acquiring means for acquiring a user identifier and a storage institution identifier as a payee, and a use history record associated with the acquired user identifier and storage institution identifier from the use history data storage means. , This usage history record is broken down into the elements that make up the payment specific code, And output processing means for displaying on said user terminal also allows screen change part, paying specific code to obtain a payment identification code by reconstructing the acquired element using the screen from the user terminal The gist of the invention is that it includes an acquisition unit and a payment process execution unit that executes a payment process using the payment identification code and records a usage history record including the payment identification code in the usage history data storage unit.

The invention according to claim 2 is the payment processing system according to claim 1, wherein the output processing means includes a payment identification code included in a plurality of usage history records associated with the user identifier and the storage institution identifier. The gist is to identify a fixed element that is common to each other and to display a variable element other than the fixed element at least on a screen that can be changed, and to identify the fixed element and display it on the user terminal.

The invention according to claim 3 is a usage history data in which a usage history including a storage institution identifier for specifying a payment destination in a multi-payment service in association with a user identifier for specifying a user and a payment specification code for specifying payment contents is recorded. Among the elements constituting the payment identification code, the storage means, the fixed element data storage means in which fixed elements used in common in the user identifier and the storage institution identifier are recorded, and payment using the multi-payment service A receiving means for acquiring a user identifier of a user who uses the multi-payment service and a storage institution identifier serving as a payee, from a user terminal. The fixed element associated with the acquired user identifier and storage institution identifier is fixed. Obtained from the element data storing means, and the variables other than the fixing element in at least modifiable screen, and an output processing means for displaying on the user terminal to identify the fixed element, from the user terminal, wherein Payment specific code acquisition means for acquiring a payment specific code by reconstructing an element acquired using a screen , payment processing is executed using the payment specific code, and a usage history record including the payment specific code is In the usage history record in which the payment processing execution means to record in the usage history data storage means and the user identifier and the storage institution identifier are common, the common fixed element among the elements constituting the payment identification code is specified, and the fixed element The gist of the present invention is that it comprises update means for recording in the data storage means.

  According to a fourth aspect of the present invention, in the payment processing system according to any one of the first to third aspects, the payee information acquiring unit is specified by user authentication based on data acquired from a user terminal. The storage institution identifier associated with the user identifier is acquired from the usage history data storage means, and the acquired storage institution identifier is displayed on the user terminal in a state where it can be individually selected, and the user identifier and the storage The gist is to obtain an institution identifier.

The invention according to claim 5 is a use history data in which a use history including a storage institution identifier for specifying a payment destination in a multi-payment service and a payment specification code for specifying payment contents in association with a user identifier for specifying a user is recorded. A method for performing payment processing using a storage means and a control means for accepting payment using a multi-payment service, wherein the control means uses a user identifier of a user who uses the multi-payment service from a user terminal. And a payment destination information acquisition stage for acquiring a storage organization identifier as a payment destination, and a usage history record associated with the acquired user identifier and storage organization identifier is acquired from the usage history data storage means, and this usage history Break down into the elements that make up the payment specific code of the record and change at least some of the elements An output processing step of displaying to the user terminal in the ability of the screen, and payment identification code acquisition step of acquiring a payment identification code by reconstructing the acquired element using the screen from the user terminal, wherein The gist is to execute a payment process using a payment identification code, and to execute a payment process execution stage of recording a usage history record including the payment identification code in the usage history data storage means.

The invention according to claim 6 is a usage history data in which a usage history including a storage institution identifier for specifying a payment destination in a multi-payment service in association with a user identifier for specifying a user and a payment specifying code for specifying payment contents is recorded. Among the elements constituting the payment identification code, the storage means, the fixed element data storage means in which fixed elements used in common in the user identifier and the storage institution identifier are recorded, and payment using the multi-payment service A method for performing payment processing using a receiving control means, wherein the control means acquires a user identifier of a user who uses a multi-payment service and a storage organization identifier as a payment destination from a user terminal. A prior information acquisition stage and a fixed association associated with the acquired user identifier and storage institution identifier. Gets an element from the fixed element data storing means, wherein the variables other than the fixed element and at least modifiable screen, and an output processing stage to be displayed on the user terminal to identify the fixed element, the user A payment identification code acquisition stage for acquiring a payment identification code by reconfiguring an element acquired using the screen from a terminal, and a payment process using the payment identification code, and use including the payment identification code In the payment processing execution stage for recording the history record in the usage history data storage means, and in the usage history record in which the user identifier and the storage institution identifier are common, the common fixed element among the elements constituting the payment identification code is specified. The update stage recorded in the fixed element data storage means is executed.

The invention according to claim 7 is a usage history data in which a usage history including a storage institution identifier for specifying a payment destination in a multi-payment service in association with a user identifier for specifying a user and a payment specifying code for specifying payment contents is recorded. A program for performing payment processing using a storage means and a control means for receiving payment using a multi-payment service, wherein the control means is connected to a user identifier of a user who uses a multi-payment service from a user terminal. And a payment destination information acquisition means for acquiring a storage organization identifier as a payment destination, a usage history record associated with the acquired user identifier and storage organization identifier from the usage history data storage means, and this usage history record Is broken down into the elements that make up the payment specific code, and at least some of the elements are Output processing means and to a further possible screen to be displayed on the user terminal, paying specific code acquiring means acquires payment identification code by reconstructing the acquired from the user terminal using the screen element, and the The gist of the invention is to execute a payment process using a payment identification code and to function as a payment process execution unit that records a usage history record including the payment identification code in the usage history data storage unit.

The invention according to claim 8 is a usage history data in which a usage history including a storage institution identifier for specifying a payment destination in a multi-payment service in association with a user identifier for specifying a user and a payment specification code for specifying payment contents is recorded. Among the elements constituting the payment identification code, the storage means, the fixed element data storage means in which fixed elements used in common in the user identifier and the storage institution identifier are recorded, and payment using the multi-payment service A program for performing a payment process using a receiving control means, wherein the control means acquires from the user terminal a user identifier of a user who uses the multi-payment service and a storage institution identifier as a payment destination. Associated with the acquired user identifier and the storage institution identifier. Get the fixing element from the fixed element data storing means, wherein the variables other than the fixed element and at least changeable screen output processing means for displaying on the user terminal to identify the fixed element, the user Payment specific code acquisition means for acquiring a payment specific code by reconfiguring an element acquired using the screen from the terminal, a payment history using the payment specific code, and a usage history including the payment specific code In the payment processing execution means for recording the record in the usage history data storage means, and in the usage history record in which the user identifier and the storage institution identifier are common, the common fixed element among the elements constituting the payment identification code is specified, The gist is to function as update means for recording in the fixed element data storage means.

(Function)
According to the invention described in claim 1, 5 or 7, the control means breaks down into elements constituting the payment identification code of the usage history record associated with the user identifier and the storage institution identifier, and at least one of the elements. parts to the changeable screen to be displayed on the user terminal. The control means acquires the payment identification code by reconstructing the elements acquired using this screen . In the payment using the multi-payment service, the payment specifying code can be determined by the storage organization. In this case, the storage organization may share the elements of the payment identification code used for the same user. Therefore, by using a screen that allows the user to change at least some of the elements that make up the payment identification code used in past payments, the payment identification code used for the current payment is based on the past payment identification code. Can be entered. For this reason, when the current element is common, the user can omit inputting the common element. Therefore, it is possible to easily input the payment specific code as compared with the case of inputting from the beginning, and the convenience for the user can be improved.

According to the second aspect of the present invention, the control means specifies a common fixed element in the payment specifying code included in the usage history record, sets at least a variable element other than the fixed element to a changeable screen , and Identify it as an element and display it on the user terminal. For this reason, the user can easily grasp the variable elements that are not commonly used by the storage engine, and therefore can easily input the variable elements. Moreover, when the payment specific code used for the current payment is configured using a fixed element, the input of the fixed element can be omitted, so that the input can be simplified.

According to the invention of claim 3, 6 or 8, the control means obtains a fixed element associated with the user identifier and the storage institution identifier, and makes a variable element other than the fixed element a screen that can be changed at least. Then, it is identified as the fixed element and displayed on the user terminal. The control means acquires the payment identification code by reconstructing the elements acquired using this screen . In the payment using the multi-payment service, the payment specifying code can be determined by the storage organization. In this case, the storage organization may share the elements of the payment identification code used for the same user. Therefore, for example, a fixed element that is commonly used by the same user in the same storage organization is specified, and a variable element other than the fixed element is displayed at least on a changeable screen so as to be identified and displayed as the fixed element. Therefore, since the user can grasp and input the variable element, the user can easily input the payment specific code, and the convenience for the user can be improved. In addition, when the payment specifying code is configured using a fixed element, the input of the fixed element can be omitted, so that the payment specifying code can be further easily input.

  Further, the control means records the payment identification code used for the payment process in the usage history data storage means. The control means specifies a fixed element having a common user identifier and storage organization identifier, and records it in the fixed element data storage means. For this reason, it is possible to verify whether or not it is a fixed element from the actually used payment identification code, and to automatically update the fixed element recorded in the fixed element data storage means. Therefore, since the updated fixed element is used, it can be expected to further save the user's input.

According to the invention described in claim 4, the control means acquires the storage organization identifier associated with the user identifier specified by the user authentication from the usage history data storage means, and individually acquires the acquired storage organization identifier. Display on the user terminal in a selectable state. For this reason, when paying again for a storage institution that has paid using a multi-payment service in the past, it is only necessary to select the storage institution identifier displayed on the user terminal, and the storage institution identifier is input. There is no need. Therefore, it is possible to save the user's input, and the convenience can be further improved.

  ADVANTAGE OF THE INVENTION According to this invention, the input of the identification information used in payment processing can be simplified, and a user's convenience can be improved.

(First embodiment)
Hereinafter, a payment processing system according to a first embodiment of the present invention will be described with reference to FIGS. The payment processing in the present invention is a payment processing system using a multi-payment service, and the bank system 10 is connected to a system that provides a multi-payment service. Here, the multi-payment service is a publicly known method in which a user can pay various charges using various channels such as an automatic teller machine, a telephone, and a personal computer by connecting a storage institution and a financial institution through a network. It is a service. Furthermore, in the present embodiment, it is assumed that processing is performed using a bank Internet banking scheme.

  The bank system 10 of this embodiment is connected to the user terminal 20 via the Internet N1. The user terminal 20 is a computer that includes a display, a pointing device, and a keyboard (not shown). The user terminal 20 displays on the display, obtains user instructions and data via a pointing device and a keyboard, and transmits and receives data to and from the bank system 10.

On the other hand, the bank system 10 includes a web server 11, an accounting host system 16, and an MPN communication server 17.
The web server 11 is a server used for Internet banking processing, and is connected to the user terminal 20. The web server 11 includes a control unit 12, a user database 13, and a transaction history database 14 as control means.

  The control unit 12 includes a CPU, a RAM, a ROM, and the like (not shown), and performs processing described later (processing including a payment destination information acquisition stage, an output processing stage, a payment specific code acquisition stage, a payment processing execution stage, and the like). And the control part 12 functions as a payment destination information acquisition means, an output processing means, a payment specific code acquisition means, a payment process execution means, etc. by executing the payment processing program for this. Further, the control unit 12 is connected to the user database 13 and the transaction history database 14 and controls reading and writing of data with respect to these databases (13, 14).

  As shown in FIG. 2, a user record 130 for specifying a user is recorded in the user database 13. This user record 130 is used for user authentication in Internet banking. This user record 130 is recorded when the user makes a contract for Internet banking. The user record 130 includes data related to a user identifier, a login password, a first password, and a second password.

In the user identifier data area, data relating to an identifier for specifying a user is recorded.
In the login password data area, data relating to the login password of the user is recorded.

Data relating to the user's first personal identification number is recorded in the first personal identification number data area. This first personal identification number is a personal identification number used for setting a login password.
Data relating to the user's second personal identification number is recorded in the second personal identification number data area. This second personal identification number is a personal identification number used for carrying out the withdrawal process from the account.

  On the other hand, as shown in FIG. 3, a transaction history record 140 relating to a transaction history of payment using a multi-payment service is recorded for each user in the transaction history database 14. The transaction history record 140 is recorded when a payment processing request using the multi-payment service is received from the user terminal 20. The transaction history record 140 includes data relating to a transaction date, a multi-payment identifier, and transaction contents corresponding to the user identifier.

In the user identifier data area, data relating to an identifier for specifying a user of the multi-payment service is recorded.
In the transaction date data area, data relating to the date (year / month / day) of payment by the user is recorded.

  The multi-payment identifier is an identifier for specifying payment when using the multi-payment service, and includes a storage institution number, a customer number, and a confirmation number. In the case of national treasury and local government funds, a payment number is given as the customer number.

  In the storage organization number data area, an identifier number for specifying a storage organization that is a payment destination of payment using the multi-payment service is recorded. A 5-digit number is used as the storage engine number.

In the customer number data area, the customer number for the storage organization to identify the transaction content is recorded. A maximum 20-digit number is used as the customer number.
In the confirmation number data area, a confirmation number for the storage organization to identify the transaction content is recorded. A 6-digit number is used as the confirmation number. In the present embodiment, the confirmation number and the customer number constitute a payment specific code.

The transaction content data is the content of the payment transaction specified based on the multi-payment identifier, and includes data related to each item of the payee, payment content, payer name, and amount.
In the payee data area, data relating to the name of the storage organization that is the payee of this payment is recorded.

In the payment content data area, data regarding the object (content) of the payment is recorded. This payment content includes, for example, “○ Monthly Gas Charge”.
In the payer name data area, data relating to the name of the obligor who makes the payment is recorded.

Data relating to the amount of payment is recorded in the amount data area.
The web server 11 is connected to a billing host system 16 as shown in FIG. The account host system 16 includes a deposit account data storage unit (not shown). In this deposit account data storage unit, a record relating to the deposit account associated with the user identifier is recorded. The account host system 16 performs banking processing by managing the user's deposit account data using the deposit account data storage unit.

Further, the billing host system 16 is connected to the MPN communication server 17. The MPN communication server 17 is a server used when using a multi-payment service. The MPN communication server 17 is connected to the storage institution system 30 via a multi-payment network that is a dedicated line.

  Each storage institution system 30 includes an MPN communication server 31 used when using a multi-payment service. The MPN communication server 31 includes a billing data storage unit (not shown). In this billing data storage unit, data relating to a multi-payment identifier, a transaction content, and a status of the bill given to each bill is stored in association with each other. This multi-payment identifier is registered by a backbone system (not shown) of the storage institution system 30.

Next, a processing procedure for performing payment using the multi-payment service using this system will be described with reference to FIGS.
When paying using a multi-payment service, a user first prepares a bill or the like on which a multi-payment identifier for specifying payment is recorded. Then, the user causes the user terminal 20 to access the web server 11 of the bank system 10. In this case, the control unit 12 of the web server 11 receives the login request (step S1-1). Specifically, in response to this login request, the control unit 12 returns login screen data to the user terminal 20. The user terminal 20 displays a login screen on the display based on the login screen data. This login screen includes an input field for inputting a user identifier and a login password, and a send button.

  Therefore, the user inputs his / her user identifier and login password using the keyboard, and selects a transmission button using the pointing device. Thereby, the user terminal 20 transmits the input user identifier and login password data to the web server 11. The web server 11 acquires the user identifier and login password of the user.

  Then, the web server 11 performs user authentication processing (step S1-2). Specifically, the control unit 12 of the web server 11 compares the user identifier and login password received from the user terminal 20 with the user record 130 recorded in the user database 13. If the user identifier and the login password received from the user terminal 20 are recorded in the user database 13 as a result of the comparison, the user authentication is completed.

  When the user authentication is completed, the control unit 12 of the web server 11 transmits banking menu screen data to the user terminal 20. This banking menu screen includes a multi-payment payment selection button. Here, when the multi-payment payment is selected, the user terminal 20 transmits a use request for the multi-payment payment service to the web server 11.

  The web server 11 that has received the usage request for the multi-payment payment service executes a usage history acquisition process for the user (step S1-3). Specifically, the control unit 12 extracts the transaction history record 140 from the transaction history database 14 using the user identifier that has completed the user authentication.

Next, the control unit 12 executes a payee candidate output process (step S1-4). Specifically, the control unit 12 first acquires the storage institution number included in the extracted transaction history record 140 and data related to the payee corresponding thereto. Then, the control unit 12 generates storage organization selection screen data including the acquired data, and transmits it to the user terminal 20. User terminal 2
0 displays the storage organization selection screen 200 shown in FIG. 5 on the display based on the received data.

  The storage organization selection screen 200 includes candidate displays relating to payees and storage organization numbers, a selection button for selecting each payee candidate, and an execution button. By using this selection button, the payee can be selected individually. Further, the storage organization selection screen 200 includes a selection button for “others”. This “other” button is used when paying to a payee other than the payee candidates displayed on the storage institution selection screen 200.

  Here, when the payee who pays is not displayed on the storage institution selection screen 200, the user selects the “other” selection button and then selects the execution button. In this case, the user terminal 20 transmits a new payment destination request to the web server 11.

  When the new payee request is received and the payee identification information is not received (in the case of “NO” in step S1-5), the control unit 12 of the web server 11 outputs the input screen for the new payee Is executed (step S1-6). Specifically, the control unit 12 transmits input screen data for inputting a multi-payment identifier to the user terminal 20 and displays the input screen.

  This input screen includes an input field for inputting a storage institution number, a customer number, and a confirmation number, and a send button. And a user inputs each number into each input field using a keyboard, and selects a transmission button using a pointing device. Thereby, the user terminal 20 acquires the storage organization number, the customer number, and the confirmation number input in the input field, and transmits them to the web server 11.

  On the other hand, when the payee who pays is displayed on the storage organization selection screen 200, the user selects the execute button after selecting the select button corresponding to the payee. In this case, the user terminal 20 transmits the storage organization number, which is the corresponding payee identification information, to the web server 11. The payment destination specifying information includes data related to the selected storage institution number.

  When the payee identification information is received (in the case of “YES” in step S1-5), the control unit 12 of the web server 11 performs a customer number and confirmation number acquisition process (step S1-7). Specifically, the control unit 12 extracts a record including the received storage organization number from the transaction history database 14 in the transaction history record 140 associated with the user identifier of the user. When a plurality of corresponding transaction history records 140 can be extracted, in the present embodiment, the control unit 12 specifies the transaction history record 140 with the newest transaction date.

  Next, the control part 12 performs the output process of the input screen which displayed each element so that change was possible using transaction history (step S1-8). Specifically, the control unit 12 disassembles the customer number and confirmation number included in the acquired transaction history record 140 into its constituent elements. Then, the numbers of the respective constituent elements are set as initial values, and screen data in which the constituent elements can be individually changed are generated and transmitted to the user terminal 20.

  The user terminal 20 displays the input screen 210 shown in FIG. 6 on the display based on the received screen data. The input screen 210 includes a display relating to the storage institution number, customer number, and confirmation number. In this display, each number can be changed as an initial value together with the components of the customer number and the confirmation number. Specifically, each number constituting the customer number and the confirmation number is displayed in association with a count-up button for individually increasing the number and a count-down button for decreasing the number.

  Here, the user operates the count-up button and the count-down button on the input screen 210 so that the customer number and the confirmation number recorded in the bill or the like are obtained. Then, the user sets numbers so that the customer number and confirmation number recorded on the invoice or the like are the same as the number displayed on the input screen 210, and selects the send button. As a result, the user terminal 20 transmits a storage institution number, a customer number, and a confirmation number configured from each element displayed on the input screen 210 to the web server 11.

  And the web server 11 which acquired the customer number and confirmation number which were set on the input screen of step S1-6, S1-8 performs a storage process (step S1-9). Specifically, the control unit 12 of the web server 11 transmits a multi-payment processing request to the account host system 16. This multi-payment processing request includes data regarding multi-payment identifiers (storage organization number, customer number, and confirmation number).

  The billing host system 16 transmits an inquiry request in the multi-payment service using the MPN communication server 17 in the same manner as the known multi-payment process. This inquiry request includes a multi-payment identifier. The billing host system 16 receives an inquiry response corresponding to the inquiry request from the MPN communication server 31 of the storage institution system 30 via the multi-payment network and the MPN communication server 17. This inquiry response includes information related to the transaction content (payee, payment content, payer name, and amount) specified from the multi-payment identifier. The account host system 16 transmits the received transaction content information to the web server 11. The control unit 12 of the web server 11 generates payment confirmation screen data including transaction content information, and transmits it to the user terminal 20 via the Internet N1.

  In the user terminal 20, a payment confirmation screen is displayed on the display. This payment confirmation screen includes information on transaction contents (payee, payment contents, payer name, and amount), a second password input field, and an execution button. Here, the user confirms that there is no mistake in the transaction content displayed on the payment confirmation screen, inputs the number of the second password in the second password input field, and selects the execution button. In this case, the user terminal 20 transmits a confirmation notification to the web server 11.

  The web server 11 that has received the confirmation notification executes the account withdrawal process using the account host system 16. Specifically, the web server 11 specifies data of the user's deposit account associated with the user identifier, and issues a withdrawal instruction for the user's account. This withdrawal instruction includes a multi-payment identifier, user account identification information, and information regarding the amount of money in the transaction content. In this case, the account host system 16 subtracts the amount included in the transaction contents from the balance of the user's account, and records this amount as a new balance.

  Next, the billing host system 16 transmits an application request via the MPN communication server 17 using the multi-payment identifier acquired from the web server 11. This application request includes a multi-payment identifier. Then, the accounting host system 16 receives the application response from the MPN communication server 31 of the storage institution system 30 via the multipayment network and the MPN communication server 17. The accounting host system 16 notifies the web server 11 that the application process has been completed.

  The control unit 12 of the web server 11 generates payment completion screen data indicating that the storage process is completed, and transmits the payment completion screen data to the user terminal 20 via the Internet N1. The user terminal 20 displays a process completion notification screen. This processing completion notification screen includes contents indicating that payment processing is completed and a reception number used at the time of inquiry.

  And the control part 12 of the web server 11 carries out the customer number and confirmation number which were set in the input screen of step S1-6, S1-8, and the transaction content (payee, payment content, payer name, and amount), Recorded in the transaction history database 14 as a transaction history record 140 associated with the user identifier and the storage institution number. Thus, the storage process ends and the multi-payment payment process is completed.

According to this embodiment, the following effects can be obtained.
(1) In the present embodiment, when the control unit 12 of the web server 11 acquires the storage organization number from the user terminal 20, the customer number associated with the storage organization number and the user identifier from the transaction history database 14. And a confirmation number is acquired (step S1-7). The control unit 12 includes the customer number and the confirmation number of the acquired transaction history record 140, generates screen data that can individually change each element of these numbers, and transmits it to the user terminal 20 (step S1-8). . Using the customer number and confirmation number displayed on the user terminal 20, the user inputs the customer number and confirmation number used in the current payment, and selects the send button. Thereby, the user terminal 20 acquires the storage organization number, the customer number, and the confirmation number, and transmits them to the web server 11. The control unit 12 of the web server 11 executes storage processing using a multi-payment service based on the acquired customer number and confirmation number (step S1-9). In payment using the multi-payment service, the customer number and confirmation number can be determined by the storage organization. In this case, the storage organization may use the elements of the customer number and the confirmation number used for the same user in common. Therefore, the control unit 12 displays the number based on the customer number and confirmation number of the acquired transaction history record 140 on the user terminal 20 and prompts the customer number and confirmation number used for the current payment to be input. For this reason, when the elements of the customer number and confirmation number included in the input screen 210 are common to the elements of the numbers used by the user for the current payment, the user inputs the common elements. Can be omitted. Therefore, the customer number and the confirmation number can be input more easily than when inputting from the beginning, and the convenience for the user can be improved.

  (2) In the present embodiment, the control unit 12 of the web server 11 acquires the transaction history record 140 that includes the received storage organization number and is associated with the user identifier of the user. And the control part 12 produces | generates the screen data which made each component element changeable while setting the number of each component element of the customer number and confirmation number contained in the acquired transaction history record 140 as an initial value, It transmits to the user terminal 20. In this case, if payment has been made to the payee's storage in the past, it can be expected that input of the customer number and confirmation number will be reduced.

  (3) In this embodiment, the control part 12 of the web server 11 performs a user authentication process using the data acquired from the user terminal 20 (step S1-2), and when this user authentication is completed, The user's usage history is acquired (step S1-3). And the control part 12 produces | generates screen data using the storage institution number contained in the transaction log record 140 of the acquired usage history and the data regarding a payment destination corresponding to this, and performs the output process of a usage payment destination candidate (Step S1-4). For this reason, when paying again to a storage institution that has paid using a multi-payment service in the past, it is only necessary to select a use payee candidate displayed on the user terminal 20, and the storage institution number is selected. There is no need for input, and convenience can be improved.

(Second Embodiment)
Next, a second embodiment of the payment processing system embodying the present invention will be described with reference to FIGS. In the following embodiments, the same parts as those in the above-described embodiments are denoted by the same reference numerals, and detailed description thereof is omitted. In this embodiment, a fixed element and a variable element are specified from the usage history, and the fixed element and the variable element are identified and input is performed. here,
The fixed element refers to an element used in common when the user and the storage organization are the same among the elements constituting the customer number and the confirmation number. In the present embodiment, it is assumed that the user has made payment using the multi-payment service at the same storage organization twice or more.

  Also in this embodiment, the same system as that in the first embodiment is used. In the present embodiment, the control unit 12 of the web server 11 performs processing described later (processing including a payment destination information acquisition stage, an output processing stage, a payment specific code acquisition stage, a payment processing execution stage, and the like). And the control part 12 functions as a payment destination information acquisition means, an output processing means, a payment specific code acquisition means, a payment process execution means, etc. by executing the payment processing program for this.

Next, a processing procedure using the system according to the present embodiment will be described with reference to FIGS.
Similarly to step S1-1 of the first embodiment, the control unit 12 receives a login request from the user terminal 20 (step S2-1). And a user identifier and a login password are acquired similarly to step S1-2, and a user authentication process is performed (step S2-2). Next, the control part 12 performs a user's usage history acquisition process similarly to step S1-3 (step S2-3). And the control part 12 performs the output process of a payee candidate similarly to step S1-4 (step S2-4).

  In this output process, when the payee who pays is not displayed on the storage organization selection screen 200, the user selects the “other” selection button and then selects the execution button. In this case, the user terminal 20 transmits a new payment destination request to the web server 11.

  When a new payee request is received and no payee identification information is received (in the case of “NO” in step S2-5), the control unit 12 of the web server 11 makes a new payment in the same manner as in step S1-6. The output process of the previous input screen is executed (step S2-6). Thereafter, the user terminal 20 acquires the storage institution number, the customer number, and the confirmation number input on the input screen, and transmits them to the web server 11.

  On the other hand, when the payee who pays is displayed on the storage organization selection screen 200, the user selects the execute button after selecting the select button corresponding to the payee. In this case, the user terminal 20 transmits the storage organization number, which is the corresponding payee identification information, to the web server 11. The payment destination specifying information includes data related to the selected storage institution number.

  When the payee identification information is received (in the case of “YES” in step S2-5), the control unit 12 of the web server 11 performs a customer number and confirmation number acquisition process (step S2-7). Specifically, the control unit 12 acquires a transaction history record 140 including the received storage organization number and the user identifier of the user from the transaction history database 14. In this embodiment, when there are a plurality of corresponding transaction history records 140, the control unit 12 acquires all the corresponding transaction history records 140.

  Next, the control part 12 specifies the component (fixed element) which has not changed (step S2-8). Here, the control part 12 compares the data of each element of the customer number or confirmation number of the transaction history record 140. Specifically, in the customer number or the confirmation number, it is compared whether or not the numbers of each digit constituting them are the same. As a result of comparison, if the same digit number is common in the customer number or the confirmation number, this digit and this digit number are specified as a component (fixed element) that does not change.

For example, as shown in FIG. 8, the multi-payment identifier paid on July 15, 2006 and the multi-payment identifier paid on August 15, 2006 are the first digit from the right and the second digit from the right of the confirmation number. Assume that the numbers are different and the other digits of the customer number and the confirmation number are the same. In this case, the control unit 12 compares each element of the customer number and each element of the confirmation number, and determines whether or not the numbers in the same digit (position) are the same. Here, since all of the customer number and the third to sixth digits from the right of the confirmation number are the same number, the control unit 12 specifies that each is a fixed element. Since the first digit and the second digit from the right of the confirmation number are different numbers, it is a variable element.

  Next, the control part 12 performs the output process of the input screen which displayed the variable element so that change was possible (step S2-9). Specifically, the control unit 12 generates input screen data for displaying the fixed element and the variable element as different objects in the customer number and confirmation number input fields, and transmits the input screen data to the user terminal 20.

  The user terminal 20 displays an input screen based on the received screen data. This input screen includes a storage institution number, a customer number, a confirmation number, and a send button. In the input screen of the present embodiment, the fixed element number is displayed as it is in the fixed element digits of the customer number and the confirmation number, and the blank is displayed in the variable element digits. The input screen may include an all clear button that allows the customer number and the confirmation number to be entered.

  Here, the user selects a blank and inputs a number using a pointing device or a keyboard. When the numbers are entered in all the blanks and the input of the multi-payment identifier is finished, the user selects the send button. Thereby, the user terminal 20 acquires a customer number and a confirmation number that are configured from each element displayed on the input screen, and transmits them to the web server 11.

  And the web server 11 which acquired the customer number and confirmation number which were set on the input screen of step S2-6, S2-9 performs a storage process similarly to said step S1-9 (step S2-10). . Thus, the multi-payment payment process of the present embodiment is completed.

According to this embodiment, the same effects as described in the above (1) and (3) can be obtained, and the following effects can be obtained.
(4) In this embodiment, if the control part 12 of the web server 11 performs the acquisition process of a customer number and a confirmation number (step S2-7), the component which has not changed is specified (step S2-8). ). And the output process of the input screen which displayed variable elements other than the component (fixed element) which has not changed so that change is possible is performed (step S2-9). In this input screen, the fixed element number is displayed as it is in the fixed element digit of the customer number and the confirmation number, and a blank is displayed in the variable element digit. Therefore, the user can easily grasp the variable elements to be input. Further, the user can save the input of the fixed elements common to the customer number and the confirmation number used in the past.

(Third embodiment)
Next, a third embodiment of the payment processing system embodying the present invention will be described with reference to FIGS. In the present embodiment, as in the second embodiment, the fixed element and the variable element are identified and input is performed. Unlike the second embodiment, the specified fixed element is recorded in the data storage unit. Assume a case.

In the present embodiment, the web server 11 of the present embodiment further includes a fixed element database 15 shown in FIG. In the fixed element database 15, fixed element records relating to fixed elements are recorded for each user and storage organization. This fixed element record is recorded when specified as a fixed element. This fixed element record is configured by associating fixed elements (digits and numbers) with a user identifier and a storage institution number. In this embodiment, in this fixed element record, a fixed element in the customer number and a fixed element in the confirmation number are recorded.

  In the present embodiment, the control unit 12 of the web server 11 performs processing described later (processing including a payment destination information acquisition stage, an output processing stage, a payment specific code acquisition stage, a payment processing execution stage, an update stage, and the like). And the control part 12 functions as a payment destination information acquisition means, an output processing means, a payment specific code acquisition means, a payment process execution means, an update means, etc. by executing the payment processing program for this.

Next, a processing procedure using the system in this embodiment will be described with reference to FIG.
Similarly to step S1-1 of the first embodiment, the control unit 12 receives a login request from the user terminal 20 (step S3-1). And a user identifier and a login password are acquired similarly to step S1-2, and a user authentication process is performed (step S3-2). Next, the control part 12 performs a user's usage history acquisition process similarly to step S1-3 (step S3-3). And the control part 12 performs the output process of a payee candidate similarly to step S1-4 (step S3-4).

  In this output process, when the payee who pays is not displayed on the storage organization selection screen 200, the user selects the “other” selection button and then selects the execution button. In this case, the user terminal 20 transmits a new payment destination request to the web server 11.

  When the new payee request is received and the payee identification information is not received (in the case of “NO” in step S3-5), the control unit 12 of the web server 11 performs the new payment as in step S1-6. The output process of the previous input screen is executed (step S3-6). Thereafter, the user terminal 20 acquires the storage institution number, the customer number, and the confirmation number input on the input screen, and transmits them to the web server 11.

  On the other hand, when the payee who pays is displayed on the storage organization selection screen 200, the user selects the execute button after selecting the select button corresponding to the payee. In this case, the user terminal 20 transmits the storage organization number, which is the corresponding payee identification information, to the web server 11. The payment destination specifying information includes data related to the selected storage institution number.

  When the payee identification information is received (in the case of “YES” in step S3-5), the control unit 12 of the web server 11 performs the acquisition process of the customer number and the confirmation number, and displays the variable element so that the variable element can be changed. A screen output process is executed (step S3-7). Specifically, the control unit 12 acquires a fixed element associated with the user identifier and the storage organization number from the fixed element database 15. And the control part 12 produces | generates the input screen data which displays a fixed element and a variable element with a respectively different object among the input fields of a customer number and a confirmation number, and transmits to the user terminal 20.

  The user terminal 20 displays an input screen based on the received screen data. As in the second embodiment, the input screen includes a storage institution number, a customer number, a confirmation number, and a send button. On this input screen, the fixed element numbers are displayed as they are in the fixed element digits of the customer number and the confirmation number, and blanks are displayed in the variable element digits.

Here, as in the second embodiment, numbers are entered in all the blanks, the input of the multi-payment identifier is completed, and the send button is selected. In this case, the user terminal 20 acquires a customer number and a confirmation number configured from each element displayed on the input screen, and transmits them to the web server 11.

  And the web server 11 which acquired the customer number and confirmation number which were set in the input screen of step S3-6, S3-7 performs a storage process similarly to said step S1-9 (step S3-8). .

  Next, the control part 12 performs the identification process of the component which has not changed (step S3-9). Specifically, the control unit 12 specifies the user identifier used in the storage process and the storage institution number included in the transaction history record 140 recorded in the transaction history database 14 by the storage process. Further, the control unit 12 extracts all transaction history records 140 including the specified user identifier and storage organization number. And the control part 12 compares the data of each element of the customer number or confirmation number of the transaction history record 140 similarly to the process of step S2-8 of the said 2nd Embodiment. Specifically, in the customer number or the confirmation number, it is compared whether or not the numbers of each digit constituting them are the same. As a result of comparison, if the same digit number is common in the customer number or the confirmation number, this digit and this digit number are specified as a component (fixed element) that does not change.

  Next, the control unit 12 records the identified fixed element in the fixed element database 15 (step S3-10). Specifically, the control unit 12 records the identified fixed elements (numbers and digits) in association with the user identifier and the storage organization number for each customer number or confirmation number. Thus, the multi-payment payment process of the present embodiment is completed.

According to this embodiment, the same effects as described in the above (3) can be obtained, and the following effects can be obtained.
(5) In this embodiment, the control part 12 of the web server 11 will perform the output process of the input screen which displayed the variable element so that change was possible, if the data regarding a storage organization number were received (step S3-7). In this case, the control unit 12 acquires the fixed element associated with the user identifier and the storage organization number from the fixed element database 15. And the control part 12 which acquired the customer number and the confirmation number via the input screen performs a storing process (step S3-8), specifies the component which has not changed (step S3-9), and this The component is recorded in the fixed element database 15 as a fixed element. In payment using the multi-payment service, the customer number and confirmation number can be determined by the storage organization. In this case, the storage organization may share the elements of the customer number and the confirmation number used for each user. Therefore, the fixed elements that are commonly used for each user in the storage organization are recorded, and the output process of the input screen is performed using the fixed elements. Therefore, since the user can omit the input of the fixed element, the customer number and the confirmation number can be easily input compared with the case of inputting from the beginning, and the convenience of the user is improved. Can do.

  (6) In the present embodiment, when the control unit 12 of the web server 11 executes the storage process (step S3-8), the component that has not changed is identified (step S3-9), and the identified component Are recorded in the fixed element database 15 as fixed elements. For this reason, it is possible to automatically update the identified fixed element by verifying the fixed element from the customer number and confirmation number actually used.

Moreover, you may change the said embodiment as follows.
In the first embodiment, the control unit 12 outputs an input screen 210 that includes a count-up button that increases or decreases a number of each element as an input screen that displays each element in a changeable manner. Not only this but the input screen which displayed each element so that change is possible, for example like 2nd and 3rd embodiment, choose the part in which the variable element of a customer number or a confirmation number is displayed, and a keyboard is used. It may be used to change the number.

  In the second and third embodiments, on the input screen, the fixed element numbers are displayed as they are in the fixed element digits of the customer number and the confirmation number, and blanks are displayed in the variable element digits. Not limited to this, the fixed element may be displayed in a changeable manner with the count-up button and the count-down button attached as in the first embodiment. In this case, since the fixed element and the variable element can be distinguished, the user can easily grasp the variable element to simplify the input, and even when the fixed element is not common, The change can be easily performed.

  In each of the above-described embodiments, the processing when the inquiry request including the information regarding the transaction content (payee, payment content, payer name, and amount) specified from the multi-payment identifier is received from the storage institution system 30 has been described. . Here, when the information regarding the multi-payment identifier to be processed is not registered in the storage institution system 30, the storage institution system 30 transmits an error message as an inquiry response. The control unit 12 of the web server 11 that has received this error message can store the storage institution number and the input customer number and confirmation number in the internal memory and re-display them. . Thereby, the user can confirm the input content and correct the input content. It is also possible to configure such that all the input contents are cleared and input again from the beginning.

  In the first embodiment, the control unit 12 specifies the customer number and confirmation number paid last time to the storage institution by specifying the transaction history record 140 having the latest transaction date. Instead of this, it is also possible to use a plurality of transaction history records paid in the past as well as the previous time. Then, the user may be allowed to select a customer number and a confirmation number included in the identified transaction history record. For example, in the case of payment of a mobile phone usage fee, a user may make multiple payments (for example, own payment and family payment) to the same storage organization using the same account. In this case, the multi-payment identifier of the user and the multi-payment identifier of the family are different. Therefore, it is configured such that multi-payment identifiers included in a plurality of past transaction history records are acquired and displayed on the input screen 210 on the display of the user terminal 20 for selection. In this case, for example, it may be displayed by pull-down. As a result, even when payments with different usage contents have been made in the past, the user can select an appropriate multi-payment identifier and input efficiently.

  In the third embodiment, the fixed element database 15 records the fixed element specified from the transaction history record 140 that is associated with the user identifier and includes the storage organization number. Not only this but the fixed element notified from the storage organization may be recorded. In this case, the web server 11 may acquire information on elements that are commonly used in each storage organization. Furthermore, fixed information data storage means for recording fixed element data associated with the storage engine may be provided. For example, when the information that the third to fifth digits from the right constituting the customer number are constant for each user is acquired, this information is stored in the fixed information data storage means in association with the storage institution identifier. When the multi-payment identifier used for the user's first payment to the storage organization is acquired, the control unit 12 compares the information with the information in the fixed information data storage means, and determines the fixed element (here, from the right of the customer number). 3rd to 5th position information and each number) are specified. Then, the control unit 12 records the identified fixed element in the fixed element database 15 in association with the usage identifier of the user.

In the second and third embodiments, the fixed element specifies an element that is common to all the transaction history records 140 of the user. Instead, an element common to the transaction history record 140 for a predetermined period may be used as a fixed element. Specifically, the control unit 12 extracts a transaction history record 140 including a transaction date within a predetermined period with respect to a date acquired from the user terminal 20 for the use request for the multi-payment payment service. The predetermined period is stored in the control unit 12. And the control part 12 pinpoints a common fixed element from the payment specific code | cord | chord of these extracted transaction history records 140. FIG. In this case, even when the common element of the user is changed on the way, the fixed element can be specified using the recent transaction history record 140.

  In each of the above embodiments, payment using the multi-payment service has been described using Internet banking. The payment means (payment channel) used by the user is not limited to this. For example, mobile banking, telephone banking, television banking, or an ATM terminal may be used.

  In each of the above embodiments, the payment history using the multi-payment identifier is recorded in the transaction history database of the web server 11. The payment history using the multi-payment identifier may be recorded in a database other than the web server, such as a database provided in the account host system. Thereby, the payment history using the multi-payment identifier can be recorded in association with the user or the user's account. For this reason, even if the payment channel which a user uses, such as an internet banking and an ATM terminal, differs, a user's payment history can be collected. Therefore, it is possible to acquire more information about the storage organization that the user has paid for using the multi-payment service.

  In the above embodiments, the customer number and confirmation number of the multi-payment identifier have been described as the payment specific code. Payment specific code is not limited to customer number and confirmation number. For example, when the payment category is also included in the multi-payment identifier, the above-described processing may be performed using the customer number, confirmation number and payment category as the payment identification code.

1 is a schematic diagram of a system in an embodiment. Explanatory drawing for demonstrating the structure of the data recorded on the user database. Explanatory drawing for demonstrating the structure of the data recorded on the transaction history database. The flowchart for demonstrating the process sequence in 1st Embodiment. Explanatory drawing of the storage organization selection screen displayed by the payment candidate output process. Explanatory drawing of the input screen which displayed the variable element so that change was possible. The flowchart for demonstrating the process sequence in 2nd Embodiment. Explanatory drawing for pinpointing the component which has not changed as a fixed element. Explanatory drawing for demonstrating the structure of the data recorded on the fixed element database. The flowchart for demonstrating the process sequence in 3rd Embodiment.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 12 ... Control part as a control means, 14 ... Transaction history database as a use history data storage means, 15 ... Fixed element database as a fixed element data storage means, 20 ... User terminal.

Claims (8)

A usage history data storage means for recording a usage history including a storage institution identifier for specifying a payment destination in a multi-payment service in association with a user identifier for specifying a user and a payment specifying code for specifying payment contents, and a multi-payment service And a control means for accepting payments,
The control means is
Payment destination information acquisition means for acquiring a user identifier of a user who uses the multi-payment service and a storage organization identifier to be a payment destination from the user terminal;
A usage history record associated with the acquired user identifier and storage institution identifier is acquired from the usage history data storage means, decomposed into elements constituting a payment identification code of the usage history record, and at least one of the elements Output processing means for displaying the user terminal on a changeable screen ,
Payment specific code acquisition means for acquiring a payment specific code by reconstructing the element acquired using the screen from the user terminal;
A payment processing system comprising payment processing executing means for executing payment processing using the payment specific code and recording a usage history record including the payment specific code in the usage history data storage means. The output processing means can identify a common fixed element in a payment identification code included in a plurality of usage history records associated with the user identifier and the storage institution identifier, and at least change a variable element other than the fixed element payment processing system according to claim 1, such the screen, and wherein the to be displayed on the user terminal to identify the fixed element. A usage history data storage unit that records a usage history including a storage institution identifier that specifies a payment destination in a multi-payment service in association with a user identifier that specifies a user and a payment specification code that specifies payment details, and the payment specification code Among the constituent elements, a system including a fixed element data storage means in which fixed elements used in common in the user identifier and the storage institution identifier are recorded, and a control means for accepting payment using a multi-payment service There,
The control means is
Payment destination information acquisition means for acquiring a user identifier of a user who uses the multi-payment service and a storage organization identifier to be a payment destination from the user terminal;
A fixed element associated with the acquired user identifier and storage organization identifier is acquired from the fixed element data storage means, and a variable element other than the fixed element is made at least a screen that can be changed to identify the fixed element. Output processing means to be displayed on the user terminal;
Payment specific code acquisition means for acquiring a payment specific code by reconstructing an element acquired using the screen from the user terminal;
Payment processing execution means for executing payment processing using the payment identification code and recording a usage history record including the payment identification code in the usage history data storage means;
An update means for specifying a common fixed element among the elements constituting the payment specifying code in the use history record having a common user identifier and storage institution identifier, and recording it in the fixed element data storage means; Feature payment processing system.   The payment destination information acquisition unit acquires a storage organization identifier associated with a user identifier specified by user authentication based on data acquired from a user terminal from the usage history data storage unit, and acquires the storage organization identifier The payment processing system according to any one of claims 1 to 3, wherein the user identifier and the storage institution identifier are acquired by displaying the user identifier in a state where the user identifier can be individually selected. A usage history data storage means for recording a usage history including a storage institution identifier for specifying a payment destination in a multi-payment service in association with a user identifier for specifying a user and a payment specifying code for specifying payment contents, and a multi-payment service A method of performing payment processing using a control means for receiving payments,
The control means is
A payment destination information acquisition stage for acquiring a user identifier of a user who uses the multi-payment service and a storage organization identifier as a payment destination from the user terminal;
A usage history record associated with the acquired user identifier and storage institution identifier is acquired from the usage history data storage means, decomposed into elements constituting a payment identification code of the usage history record, and at least one of the elements An output processing stage for displaying the user terminal on a changeable screen , and
A payment specific code acquisition step of acquiring a payment specific code by reconfiguring an element acquired using the screen from the user terminal;
A payment processing method comprising: executing a payment process using the payment specific code, and executing a payment process execution step of recording a usage history record including the payment specific code in the usage history data storage means. A usage history data storage unit that records a usage history including a storage institution identifier that specifies a payment destination in a multi-payment service in association with a user identifier that specifies a user and a payment specification code that specifies payment details, and the payment specification code Among the constituent elements, payment is made using fixed element data storage means in which fixed elements that are commonly used in the user identifier and the storage institution identifier are recorded, and control means that accepts payment using a multi-payment service. A method of performing processing,
The control means is
A payment destination information acquisition stage for acquiring a user identifier of a user who uses the multi-payment service and a storage organization identifier as a payment destination from the user terminal;
A fixed element associated with the acquired user identifier and storage organization identifier is acquired from the fixed element data storage means, and a variable element other than the fixed element is made at least a screen that can be changed to identify the fixed element. An output processing stage to be displayed on the user terminal;
Payment specific code acquisition stage for acquiring a payment specific code by reconstructing the element acquired using the screen from the user terminal;
A payment process executing step of executing a payment process using the payment identification code and recording a usage history record including the payment identification code in the usage history data storage means;
In a usage history record having a common user identifier and storage institution identifier, a common fixed element among the elements constituting the payment identification code is specified, and an updating step is performed for recording in the fixed element data storage means. A characteristic payment processing method. A usage history data storage means for recording a usage history including a storage institution identifier for specifying a payment destination in a multi-payment service in association with a user identifier for specifying a user and a payment specifying code for specifying payment contents, and a multi-payment service A program for performing payment processing using a control means for receiving payments,
The control means;
Payment destination information acquisition means for acquiring a user identifier of a user who uses a multi-payment service and a storage organization identifier as a payment destination from a user terminal,
A usage history record associated with the acquired user identifier and storage institution identifier is acquired from the usage history data storage means, decomposed into elements constituting a payment identification code of the usage history record, and at least one of the elements Output processing means for causing the user terminal to display a changeable screen on the user terminal,
A payment identification code acquisition means for acquiring a payment identification code by reconfiguring an element acquired from the user terminal using the screen ; and a payment process using the payment identification code; A payment processing program that functions as a payment processing execution unit that records a usage history record including the usage history record in the usage history data storage unit. A usage history data storage unit that records a usage history including a storage institution identifier that specifies a payment destination in a multi-payment service in association with a user identifier that specifies a user and a payment specification code that specifies payment details, and the payment specification code Among the constituent elements, payment is made using fixed element data storage means in which fixed elements that are commonly used in the user identifier and the storage institution identifier are recorded, and control means that accepts payment using a multi-payment service. A program for processing,
The control means;
Payment destination information acquisition means for acquiring a user identifier of a user who uses a multi-payment service and a storage organization identifier as a payment destination from a user terminal,
A fixed element associated with the acquired user identifier and storage organization identifier is acquired from the fixed element data storage means, and a variable element other than the fixed element is made at least a screen that can be changed to identify the fixed element. Output processing means to be displayed on the user terminal;
Payment specific code acquisition means for acquiring a payment specific code by reconstructing an element acquired using the screen from the user terminal,
Payment processing execution means for executing payment processing using the payment specific code and recording a usage history record including the payment specific code in the usage history data storage means, and a usage history in which a user identifier and a storage institution identifier are common A payment processing program characterized in that, in a record, a fixed element that is common among elements constituting a payment specifying code is specified and is recorded as an updating means for recording in the fixed element data storage means.

Images