Settlement processing device, method, and program

Abstract

To flexibly set an authentication item used for user authentication when an end user applies for service of a customer company, for each customer company.SOLUTION: A settlement processing device stores customer-specific display information and authentication master accounting information. The settlement processing device is configured to: receive, from a first device, one or more customer selection authentication items selected and changed by a customer from among a plurality of authentication items; store, in the customer-specific display information, the received one or more customer selection authentication items; and dynamically configure an authentication interface so as to include one or more customer selection authentication items associated with the customer to provide it to a second device, in response to user access associated with the customer. The settlement processing device receives, from the first device, a first authentication item name associated with a first customer selection authentication item among the customer selection authentication items, and configures the authentication interface so as to display the first authentication item name in association with the first customer selection authentication item.SELECTED DRAWING: Figure 8

Description

[Technical field]

[0001] The present invention relates to a payment processing device, method, and program that provides a client company with a mechanism for implementing a service that accepts registration of payment information such as account transfers on the Web and registers data necessary for continuous billing processing. More specifically, the present invention relates to a payment processing device, method, and program that allows an end user to flexibly set, for each client company, authentication items used for identity authentication when applying for a service of the client company. [Background technology]

[0002] In the past, businesses have provided continuous services to end users and periodically billed them for the services. Such businesses bill users through payment methods such as direct debit and credit cards.

[0003] When entering into a direct debit contract with a user, a company would build its own website that was linked to a service such as that shown in Non-Patent Document 1. The company would accept direct debit applications from end users, receive account information for direct debit, and have the end users enter information required for identity verification, thereby carrying out continuous billing processes such as direct debit. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] NTT Data Corporation, "Starts offering the "Internet Direct Debit Reception Gateway Service," a service that enables direct debit contracts over the Internet," [online], March 25, 2008, [Retrieved November 13, 2023], Internet<https: / / www.nttdata.com / global / ja / news / release / 2008 / 032500 / > Summary of the Invention [Problem to be solved by the invention]

[0005] Even if the system part to be constructed is only the front part that links to a service such as Non-Patent Document 1 when an enterprise constructs its own website for account transfer applications, it is a heavy burden for the enterprise. Even if there is a general-purpose service that provides the mechanism of the front part that links to a service such as Non-Patent Document 1 and the enterprise introduces such a service, since the information suitable for identifying the end user varies depending on the enterprise, it is difficult to set flexible authentication items (customer identification items) according to the service content of the enterprise if the screen input items of the general-purpose service are fixed. Furthermore, it was very difficult to identify a reliable end user if the screen input items were fixed in this way.

[0006] The present invention has been made to solve such problems, and an object thereof is to provide a settlement processing device, method, and program that enable flexible setting of authentication items used for personal authentication when an end user applies for a service of a customer enterprise for each customer enterprise.

Means for Solving the Problems

[0007] A settlement processing device according to an aspect of the present invention is a settlement processing device including a communication unit, a storage unit, and a control unit for communicating with an external network, wherein the storage unit stores display control information and authentication master information, and the control unit receives, from a first device, one or more customer-selected authentication items selected and changed by a customer from among a plurality of authentication items via the communication unit, stores the received one or more customer-selected authentication items in the display control information of the storage unit, dynamically configures an authentication interface to include the one or more customer-selected authentication items associated with the customer in response to a user access associated with the customer via the communication unit, and provides the configured authentication interface to a second device and is configured to execute the above.

Effects of the Invention

[0008] According to the present invention, it is possible to flexibly set the authentication items used for personal authentication when an end user applies for the services of a customer company for each customer company. In addition, each customer company does not need to set up its own payment information registration site, and even for a payment information registration site that can be shared by various customer companies, the input items, that is, the authentication items (customer identification items), are not fixed, and dynamic changes according to the customer are possible.

Brief Description of the Drawings

[0009] A detailed understanding of the embodiments disclosed in this specification can be obtained from the following description illustrated in relation to the accompanying drawings.

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Embodiments for Carrying Out the Invention

[0010] (Overall Configuration and Functions of Each Component) FIG. 1 is a configuration diagram of an entire system including a settlement processing apparatus 10 according to the present invention. The settlement processing apparatus 10 is communicably connected to a settlement agency system 11, an end-user terminal 12, and a customer device 13. The settlement agency system 11 and the customer device 13 are communicably connected to each other. In FIG. 1, only one end-user terminal 12 and one customer device 13 are shown, but there may be a plurality of these. As is known to those skilled in the art, the settlement agency system 11 can be used by a settlement agency company that mediates between a company and a financial institution for settlement means such as account transfer and credit card settlement.

[0011] In this specification, "customer" means any entity such as a local government or a non-profit organization, not limited to a company, and the terms "customer" and "company", "local government", "non-profit organization", etc. are used interchangeably. Also, "user" means an end-user who receives services from a customer, and the terms "user" and "end-user" are used interchangeably.

[0012] The settlement processing apparatus 10 provides an authentication item setting screen 600 to the customer device 13 to allow each customer to set one or more authentication items required for the user, and stores the set information as authentication master information. The authentication item can also be referred to as a customer identification item. The settlement processing apparatus 10 receives user master billing information for authenticating each user from the customer device 13 and stores it in the apparatus.

[0013] The payment processing device 10 can provide the end-user terminal 12 with a login screen 700 associated with each customer in response to a user access based on the access information (e.g., URL) assigned to each customer, and allow the end-user to input the authentication information set for each customer. That is, the payment processing device 10 can change the screen interface of the login screen 700 for each customer by preparing the URL of the login screen 700 for each customer. The login screen 700 may have different authentication items (customer identification items) for each customer, and the number and names of the authentication items that need to be input or selected on the screen may vary.

[0014] The payment processing device 10 provides the end-user terminal 12 with an interface for inputting billing information to an authenticated end-user, allows the input of user information including payment information such as a recurring billing method, account number, and credit card number, and receives the user information. The payment processing device 10 can change the input interface in cooperation with the payment agency system 11 according to the content of the user information to be acquired. The payment processing device 10 can transmit the user information to the payment agency system 11 and provide the response data from the payment agency system 11 to the customer device 13. Also, the information input on a certain input interface (screen) can be directly transmitted to and registered in the payment agency system 11 (without being temporarily stored in the payment processing device 10) when a predetermined registration event occurs.

[0015] The payment agency system 11 can receive and store user information including payment information such as a recurring billing method, account number, and credit card number for each user from the payment processing device 10 and / or the end-user terminal 12. The payment agency system 11 receives a payment request (e.g., account transfer request) associated with each user from the customer device 13 and requests a financial institution system corresponding to the payment request of the user for payment processing (e.g., account transfer). The processing of account transfer is the same as the conventional processing and will be omitted from detailed description in this specification.

[0016] The end-user terminal 12 may be any type of device operable in a wired or wireless environment (e.g., smartphone, PC, tablet terminal, etc.), and is not limited to a specific device or apparatus.

[0017] The end-user terminal 12 receives access information (e.g., URL) from the customer device 13 for logging in to the login screen 700 associated with each customer. The end-user terminal 12 can access the login screen 700 provided by the payment processing device 10 via the access information and input authentication information.

[0018] After authentication, the end-user terminal 12 can input user information including continuous payment methods and payment information such as account numbers or credit card numbers via one or more interfaces for inputting billing information. The information input via these interfaces may be registered with the payment processing device 10 or may be registered with the payment agency system 11.

[0019] The customer device 13 may be any type of device (e.g., smartphone, PC, tablet terminal, etc.) or server device operable in a wired or wireless environment, and is not limited to a specific device or apparatus.

[0020] The customer device 13 can select one or more authentication items that the customer requests from the end-user via the authentication item setting screen 600 provided by the payment processing device 10, and register an alias for each of the selected authentication items with the payment processing device 10. The customer device 13 can send or register user master billing information for use in authenticating each user with the payment processing device 10.

[0021] The customer device 13 transmits access information (e.g., URL) for logging in to the login screen 700 associated with each customer to the end-user terminal 12. The customer device 13 transmits a payment request (e.g., bank transfer request) associated with each user to the payment agency system 11.

[0022] (System Configuration) FIG. 2 is a system configuration diagram of the payment processing device 10 according to the present invention. The payment processing device 10 includes a control unit 101, a main memory unit 102, an auxiliary storage unit 103, an IF unit 104, and an output unit 105, which are interconnected by a bus 120 or the like, similar to a general computer. The payment processing device 10 includes customer-specific display information 106 and authentication master charging information 107 in the form of storage means such as files / databases in the auxiliary storage unit 103.

[0023] The control unit 101, also called a central processing unit (CPU), controls each component of the payment processing device 10 and performs data calculations, and also reads out various programs stored in the auxiliary storage unit 103 to the main memory unit 102 for execution. The main memory unit 102, also called a main memory, can store various received data, computer-executable instructions, and data after arithmetic processing by the instructions. The auxiliary storage unit 103 is a storage device represented by a hard disk drive (HDD) or the like and is used for long-term storage of data and programs.

[0024] The embodiment of FIG. 2 will describe an embodiment in which the control unit 101, the main memory unit 102, and the auxiliary storage unit 103 are provided in the same computer. However, as another embodiment, the payment processing device 10 can be configured to realize parallel distributed processing by a plurality of computers by using a plurality of the control unit 101, the main memory unit 102, and the auxiliary storage unit 103. Also, as another embodiment, it is possible to adopt an embodiment in which a plurality of servers for the payment processing device 10 are installed and the plurality of servers share one auxiliary storage unit 103.

[0025] The IF unit 104 serves as an interface (IF) for transmitting and receiving data to and from other systems and devices, and also provides an interface for receiving various commands and input data (various masters, tables, etc.) from the system operator. The output unit 105 provides a display screen for displaying the processed data, printing means for printing the data, and the like.

[0026] Components having functions similar to those of the control unit 101, the main memory unit 102, the auxiliary storage unit 103, the IF unit 104, and the output unit 105 also exist in the settlement agency system 11, the end-user terminal 12, and the customer device 13, but descriptions thereof are omitted in this specification.

[0027] The customer-specific display information 106 stores information on one or more authentication items for identifying an end user, which are set by each customer. The data of the customer-specific display information 106 can be different for each customer. FIG. 3 is a diagram for explaining an example of the data structure of the customer-specific display information 106. The customer-specific display information 106 can include a customer ID 301, an authentication item name N302, and a name N303 of the authentication item before change, but is not limited to these data items and can also include other data items. For example, it can also include information such as the display start date of the authentication item name displayed to the end user and the display period (such as the display end date from the display start date).

[0028] The customer ID 301 is an identifier for identifying a customer who uses the settlement information registration reception service provided by the settlement processing apparatus 10 according to the present invention. As described above, the customer means any entity such as a local government or a non-profit organization, not limited to a company. The authentication item name N302 is the item name selected by the customer in the settlement information registration reception service, and indicates the item name displayed to the end user of the customer. N represents a natural number. For example, when there are three authentication item names selected by the customer, the authentication item name N302 can indicate the first authentication item name, the second authentication item name, and the third authentication item name.

[0029] The name of the authentication item before change N303 indicates each authentication item name before change when the customer changes the name of the selected authentication item. The payment information registration acceptance service has a plurality of default authentication item names. The customer determines the number of authentication items to prompt the end user for input, selects that number of authentication items, and can arbitrarily change the names of the selected authentication items. For example, in the payment information registration acceptance service, when the name of the authentication item initially displayed as "customer number" is changed to "student ID number", the name of the authentication item before change is "customer number". The name of the authentication item before change is not shown to the end user.

[0030] Returning to FIG. 2 and continuing the explanation, the authentication master billing information 107 stores the authentication master information and billing information of each user associated with the authentication information specified by the customer. Since the data of the authentication master billing information 107 includes the authentication information specified by the customer, the content of the data format may differ depending on the customer. FIG. 4 is a diagram for explaining an example of the data structure of the authentication master billing information 107. The authentication master billing information 107 can include a customer ID 301, a user ID 401, an authentication item name N302, user authentication information N402, a payment method flag 403, and payment means information 404, but is not limited to these data items and can also include other data items.

[0031] Customer ID 301 is an identifier that identifies a customer who uses the payment information registration reception service as described above. User ID 401 is an identifier that identifies the end-user of the customer. Authentication item name N302 is the name of the authentication item selected by the customer as described above, and indicates the name of the authentication item displayed to the end-user of the customer. User authentication information N402 indicates authentication information (for example, customer number, name, telephone number, etc.) corresponding to the authentication item name N302. N is a natural number. When the number of authentication item names selected by the customer is 2, the user authentication information N402 includes the first user authentication information and the second user authentication information. Payment method flag 403 indicates the payment method (for example, account transfer, credit card payment) selected by the user for continuous billing by the customer. Payment means information 404 indicates information on the payment means corresponding to the information of the payment method flag 403, for example, bank account information, credit card number, etc. In an embodiment where bank account information or credit card numbers are stored in the payment agency system 11, the payment means information 404 may include an identifier of the payment agency system that performs the storage and information for specifying bank account information or credit card numbers.

[0032] (Processing content of payment information registration reception service) FIG. 5 is a flowchart for explaining the processing content of the payment information registration reception service executed by the payment processing device 10.

[0033] In S501, in response to a request from the customer device 13, the payment processing device 10 provides the authentication item setting screen 600 to the customer device 13 to allow the customer to select desired authentication items. The payment processing device 10 has a plurality of authentication items that can be used in the payment information registration reception service. The customer determines the number of authentication items that prompt the end-user to input according to their own business type, service content, etc., and selects the determined number of authentication items from among the plurality of available authentication items. Further, the customer can change the name of each selected authentication item as needed. FIG. 6 illustrates an authentication item setting screen 600 for the customer to select one or more arbitrary authentication items from among a plurality of authentication items and change the name of the authentication item.

[0034] The authentication item setting screen 600 includes user authentication item candidates 601, required user authentication items 602, a change title 603, and a registration button 604. The user authentication item candidates 601 indicate a plurality of authentication items that are predefined by the settlement processing device 10 and can be used in the settlement information registration reception service. The required user authentication items 602 indicate the authentication items selected by the customer among the authentication items shown in the user authentication item candidates 601. The required user authentication items 602 can be newly added with authentication items or existing authentication items can be deleted by operator operation. The change title 603 indicates a name obtained by changing the name of the customer-selected authentication item shown in the required user authentication items 602 to a name that is easy for the end user to understand according to the customer's business type and service content. The registration button 604 is a button for performing a registration process of storing the content selected and input by the customer in the customer-specific display information 106.

[0035] The settlement processing device 10 can store one or more authentication items selected by the customer in the authentication item setting screen 600 in the customer-specific display information 106, and can also receive and store in the customer-specific display information 106 the changed authentication item name for any of the one or more authentication items. One or more authentication items selected by the customer in the authentication item setting screen 600 will be displayed to the end user.

[0036] In S502, the settlement processing device 10 receives the authentication master information from the customer device 13 and stores it in the authentication master billing information 107. The authentication items included in the authentication master information are the authentication items selected by the customer in S501, and the authentication master information includes the authentication information of each user associated with the customer. The settlement processing device 10 can send the data format for registering the authentication master information to the customer device 13 and can also provide a registration screen for registering the authentication master information, but the method is not particularly limited.

[0037] In S503, in response to the authentication master information being stored in the authentication master charging information 107, the payment processing device 10 generates the customer-specific access information (e.g., URL) for accessing the payment information registration reception service and transmits it to the customer device 13. The customer-specific access information contains information that can identify the customer. In response to receiving the customer-specific access information, the customer device 13 notifies the customer's user of the access information via any communication means such as an email.

[0038] In S504, in response to a user access based on the customer-specific access information (e.g., URL) from the end-user terminal 12, the payment processing device 10 provides the end-user terminal 12 with a login screen 700 associated with the access information. Specifically, the payment processing device 10 identifies the customer information associated with the user access, and reads out the authentication item name N302 associated with the identified customer information from the customer-specific display information 106, thereby dynamically configuring the login screen 700 described below to display the read authentication item name and providing it to the end-user terminal 12. If the content of the authentication item name N302 has been changed by the customer as described above, the changed name can be displayed on the login screen 700.

[0039] FIG. 7 illustrates a login screen 700 where an end user inputs a user ID and authentication information set by a customer. The login screen 700 includes a user information input field 701 and a login button 702. The user information input field 701 is a field for inputting a user ID and one or more authentication items set by the customer. The login button 702 is a button for starting an authentication process based on the information input in the user information input field 701. The user ID is a user identifier assigned to the end user by the customer. The one or more authentication items indicate the authentication items selected by the customer on the authentication item setting screen 600. That is, since the authentication items are arbitrarily selected by the customer and the names of the authentication items can be set by the customer, the content displayed on the login screen 700 may differ for each customer. The part labeled "Authentication Item 1" in FIG. 7 can display the name set by the customer in the change title 603 of the authentication item setting screen 600 in FIG. 6.

[0040] The settlement processing device 10 receives the user ID and one or more authentication items input by the end user.

[0041] In S505, the settlement processing device 10 queries the authentication master billing information 107 based on the customer ID associated with the login screen 700 and the input user ID, identifies the user information, and reads out the user ID 401, authentication item name N302, and user authentication information N402 of the identified user information. The settlement processing device 10 compares the user ID and one or more authentication items input via the login screen 700 with the read user ID 401, authentication item name N302, and user authentication information N402, and determines whether they match. If it is determined that they match, the process proceeds to S506. On the other hand, if it is determined that they do not match, a message indicating login failure is displayed on the login screen 700, and the process returns to S504 to display a message prompting re - input.

[0042] In S506, after the authentication process is successfully completed, the payment processing device 10 provides the service application and payment method selection screen 800 to the end-user terminal 12. FIG. 8 illustrates a service application and payment method selection screen 800 where the user selects a payment method and enters payment information (e.g., account information, credit card information, etc.) corresponding to the selected payment method.

[0043] The service application and payment method selection screen 800 includes a payment method 801, payment information 802, and a registration button 803. The payment method 801 includes a payment method selection field for continuous billing. In the payment method selection field, any payment method can be selected. In the example of FIG. 8, an example is shown where one can select between bank transfer and credit card, but other arbitrary payment means such as debit cards and electronic money may also be selectable. Further, the service application and payment method selection screen 800 can display, on the screen, and change the information to be input / selected based on the content of the service provided by the customer.

[0044] The payment information 802 is a field for entering payment information corresponding to the payment method selected in the payment method 801. For example, account information for bank transfer or card information for credit card payment may be entered in the payment information 802. Depending on the type of information entered, the system where the entered information is registered may differ. For example, the account information for bank transfer may be registered in the payment agency system 11, and the credit card information may be registered in the payment processing device 10, but it is not limited to these embodiments. The registration button 803 is a button for storing the information entered on the service application and payment method selection screen 800 in a predetermined storage location, e.g., the payment processing device 10 or the payment agency system 11.

[0045] In response to the pressing of the registration button 803, the settlement processing device 10 can store the information input on the service application and payment method selection screen 800 in the authentication master billing information 107. Also, the settlement processing device 10 can transmit the input information to the settlement agency system 11 for registration. In the example of FIG. 8, although input fields for the payment method, account information for account transfer, and credit card information are shown on the service application and payment method selection screen 800, the present invention is not limited to such an example of the screen 800. For example, the items displayed on the screen may be separated for each storage destination where the information is registered.

[0046] In S507, in response to the completion of the storage process to the authentication master billing information 107, the settlement processing device 10 can provide the stored information to the customer device 13. The provision of information to the customer device 13 may be performed in a form in which the settlement processing device 10 transmits a data set at a predetermined timing, or alternatively, may be in a form in which a search is performed using a reference screen (not shown) and the target data is downloaded in a batch. As a result, when a predetermined date arrives, the customer can generate an account transfer request for charging the user and transmit it to the settlement agency system 11.

[0047] As another embodiment of the present invention, when a credit card is selected as the settlement means for charging, the settlement processing device 10 can store information necessary for card settlement, that is, the card number, card expiration date, security code, etc. in the settlement means information 404 and provide it to the customer device 13, or store the card number, card expiration date, security code, etc. in the settlement agency system 11, and store information for identifying the settlement agency system 11 as the storage destination and information such as the card number in the settlement means information 404 and provide it to the customer device 13. When performing a charging process on the end user, the customer device 13 will transmit an authorization message and a sales message to the corresponding card company in the same manner as in the conventional card settlement.

[0048] The principles of the present invention have been described with reference to the above exemplary embodiments. Those skilled in the art will understand that various embodiments can be realized with modifications in configuration and details without departing from the gist of the present invention. That is, the present invention can be implemented, for example, as an embodiment such as a system, apparatus, method, program, or storage medium.

Explanation of Reference Numerals

[0049] 10 Settlement processing device 11 Settlement agency system 12 End-user terminal 13 Customer device 101 Control unit 102 Main memory unit 103 Auxiliary storage unit 104 IF unit 105 Output unit 106 Customer-specific display information 107 Authentication master charging information

Claims

1. A settlement processing device including a communication unit, a storage unit, and a control unit for communicating with an external network, wherein the storage unit stores display control information and authentication master information, and the control unit receives, via the communication unit, one or more customer-selected authentication items selected and changed by a customer from among a plurality of authentication items from a first device; stores the received one or more customer-selected authentication items in the display control information of the storage unit; dynamically configures an authentication interface to include one or more customer-selected authentication items associated with the customer in response to user access associated with the customer via the communication unit, and provides the configured authentication interface to a second device; A settlement processing device configured to perform the above.

2. The control unit further receives, via the communication unit, a first authentication item name associated with a first customer-selected authentication item among the customer-selected authentication items from the first device, and configures the authentication interface to display the first authentication item name in association with the first customer-selected authentication item among the customer-selected authentication items; The settlement processing device according to claim 1, further configured to perform the above.

3. The control unit receives, via the communication unit, first authentication information associated with the one or more customer-selected authentication items from the first device, and stores the received first authentication information in the authentication master information; receives second authentication information from the second device via the authentication interface; queries the authentication master information based at least on a user identifier included in the second authentication information, and obtains the first authentication information associated with the user identifier; and compares the obtained first authentication information with the second authentication information The settlement processing device according to claim 1 or claim 2, which is further configured to execute

4. A method executed by a settlement processing device including a communication unit, a storage unit, and a control unit for communicating with an external network, wherein the storage unit stores display control information and authentication master information, the control unit receives, via the communication unit, one or more customer-selected authentication items selected and changed by a customer from among a plurality of authentication items from a first device, the control unit stores the received one or more customer-selected authentication items in the display control information of the storage unit, the control unit dynamically configures an authentication interface to include one or more customer-selected authentication items associated with the customer in response to user access associated with the customer via the communication unit and provides it to a second device A method comprising

5. the control unit receives, via the communication unit, a first authentication item name associated with a first customer-selected authentication item among the customer-selected authentication items from the first device, the control unit configures the authentication interface to display the first authentication item name in association with the first customer-selected authentication item among the customer-selected authentication items, The method according to claim 4, further comprising

6. the control unit receives, via the communication unit, first authentication information associated with the one or more customer-selected authentication items from the first device and stores it in the authentication master information, the control unit receives second authentication information from the second device via the authentication interface, the control unit queries the authentication master information based at least on a user identifier included in the second authentication information and obtains the first authentication information associated with the user identifier, The control unit collates the acquired first authentication information and the second authentication information The method according to claim 4 or claim 5, further comprising:

7. A program for causing a computer to execute the method according to claim 4 or claim 5.

Images