TW202405716A - Settlement system, settlement method, and program product capable of reducing the costs required to introduce settlement services - Google Patents

Abstract

The present invention aims to reduce the costs required to introduce settlement services. An assigning unit (102) of a settlement system (1) assigns a settlement number in the same format as a credit card number to the user. A calculation unit (104) calculates a trustworthiness score related to the user based on transaction information related to the transactions of the user in the past. A number settlement determination unit (105) determines whether or not to permit the number settlement related to the settlement number based on the score when the settlement request related to the settlement number is received. A number settlement execution unit (109) executes the number settlement when it is determined that the number settlement is permitted by the number settlement determination unit (105).

Description

Checkout systems, checkout methods, and program products

This disclosure relates to checkout systems, checkout methods, and program products.

Previously, technologies required to improve the convenience of users using checkout services have been studied. For example, Patent Document 1 describes a business transaction system that confirms the user's trustworthiness based on the user's transaction information when the user performs biometric authentication using a client device installed in a store. In the business transaction system of Patent Document 1, if the user is trustworthy, the purchase fee for the product is allowed to be paid later, or the discount amount for the purchase fee is increased. [Prior technical documents] [Patent documents]

[Patent Document 1] Japanese Patent Application Publication No. 2010-122950

[Problem to be solved by the invention]

However, if the business transaction system of Patent Document 1 is introduced, client devices of various stores must be modified in order to support biometric authentication, which is very costly. This is not limited to the business transaction system of Patent Document 1, but is also true for all checkout services. In the previous technology, in order to introduce the checkout service, most devices need to be modified, which is very costly.

One of the purposes of this disclosure is to reduce the cost required to introduce checkout services. [Means used to solve problems]

The checkout system described in this disclosure includes: an assignment part that assigns a checkout number in the same format as a credit card number to a user; and a calculation part that calculates based on past transaction information about the user's transactions. The score regarding the trustworthiness of the user mentioned above; and the number checkout determination unit, when the checkout request for the checkout number mentioned above has been accepted, determines whether to allow the number related to the checkout number mentioned above based on the score mentioned above The settlement; and the number settlement execution unit executes the settlement of the preceding number when it is determined that settlement of the preceding number is permitted by the settlement determination unit of the preceding number. ​[Effects of the invention]

If this disclosure is followed, the cost required for introducing the checkout service can be reduced.

[1. Overall structure of the checkout system]

An example of an implementation form of the checkout system described in the present disclosure will be described. This embodiment takes as an example a case where the checkout service and the EC (Electronic Commerce) service are linked. The checkout service may be linked to other services other than the EC service, or may not be specifically linked to other services but may complete all processing within the checkout service. An example of these is explained in the modification example described later.

FIG. 1 is a diagram illustrating an example of the overall configuration of the checkout system. For example, the checkout system 1 includes a checkout server 10 , an EC server 20 , and a user terminal 30 . Each of the checkout server 10, the EC server 20, and the user terminal 30 is a network N that can be connected to the Internet, a LAN, or the like.

The checkout server 10 is a server computer serving checkout. For example, the checkout server 10 includes a control unit 11, a storage unit 12, and a communication unit 13. The control unit 11 includes at least one processor. The memory unit 12 includes volatile memory such as RAM and non-volatile memory such as flash memory. The communication unit 13 includes at least one of a communication interface for wired communication and a communication interface for wireless communication.

The EC server 20 is a server computer serving EC. For example, the EC server 20 includes a control unit 21, a storage unit 22, and a communication unit 23. The physical structures of the control part 21, the memory part 22, and the communication part 23 may be the same as the control part 11, the memory part 12, and the communication part 13 respectively.

The user terminal 30 is the user's computer. For example, the user terminal 30 is a smart phone, a personal computer, a tablet terminal, or a wearable terminal. For example, the user terminal 30 includes a control unit 31, a memory unit 32, a communication unit 33, an operation unit 34, and a display unit 35. The physical structures of the control part 31, the memory part 32, and the communication part 33 may be the same as the control part 11, the memory part 12, and the communication part 13 respectively. The operation unit 34 is an input device such as a touch panel or a mouse. The display unit 35 is a liquid crystal display or an organic EL display.

In addition, the programs stored in the memory units 12, 22, and 32 can also be supplied through the network N. In addition, the program stored in the information storage medium that can be read by the computer can also be used to exchange data with external machines through the reading section of the information storage medium that can be read (such as a CD drive or a memory card slot). The input and output parts (such as USB ports) required for the input and output are provided.

In addition, the checkout system 1 only needs to include at least one computer, and is not limited to the example in Fig. 1 . For example, the checkout system 1 may not include the EC server 20 and the user terminal 30 , but may only include the checkout server 10 . In this case, the EC server 20 and the user terminal 30 may also exist outside the checkout system 1 . The checkout system 1 may also include computers other than the checkout server 10 , the EC server 20 and the user terminal 30 .

[2. Overview of the checkout system] In this embodiment, the user uses any of a plurality of checkout methods (checkout means) that can be used in the EC service, and in the EC service Purchase items. The checkout method can also be said to be the payment method (payment method). The settlement method itself can use various methods, such as: credit card settlement, bank transfer settlement, bank automatic deduction settlement, settlement using accounts other than bank accounts, crypto asset settlement, electronic currency settlement, Points checkout, bill checkout (convenience store checkout), or electronic wallet checkout.

Figures 2 and 3 are diagrams illustrating an example of the process for users to purchase goods in the EC service. In this embodiment, it is assumed that the user has completed membership login in the EC service. As shown in FIG. 2 , when the user operates the user terminal 30 and accesses the EC server 20 , the EC service login screen SC1 is displayed on the display unit 35 . In this embodiment, each screen is displayed on a browser, but each screen may be displayed on a dedicated application.

For example, once the user enters the user ID and password in the input forms F10 and F11 and selects the button B12, the login process to the EC service will be executed. Once the login process is successful, the top screen SC2 of the EC service is displayed on the display unit 35 . The user retrieves the desired product from the top screen SC2 and puts it in the shopping basket. Once the user performs the procedure required for ordering the products placed in the shopping basket, the order confirmation screen SC3 is displayed on the display unit 35 .

For example, the order confirmation screen SC3 displays a list of checkout methods available to the user. In the example in Figure 2, the user has logged in two credit cards, "Credit Card B" and "Credit Card D", to the EC service. These two credit cards are physical cards. The order confirmation screen SC3 displays the name of the credit card, the small icon I30 indicating the brand of the credit card, and a part of the card number of the credit card. The user selects the button B31 of any checkout method to order the product.

In this embodiment, the user is a postpaid service who can use one of the checkout services. Postpaid service is a service where payment is made after ordering the goods. Hereinafter, the settlement in the postpaid service is called postpaid settlement. In this embodiment, it is explained that postpaid settlement is a type of bill settlement, but postpaid settlement is not limited to bill settlement. For example, postpaid payment may be payment using other media such as postcards instead of payment notes, or payment may be payment using a payment note number notified by e-mail or the like.

For example, it is assumed that in order to select postpaid checkout as the checkout method, the user must log in as a member of the postpaid service. When the user selects button B32, a member login screen SC4 required for member registration for postpaid services is displayed on the display unit 35. In this embodiment, it is assumed that the provider of the settlement service and the provider of the EC service are the same, and a common user ID and password can be used. For example, once the user inputs the user ID and password in the input forms F40 and F41 and selects button B42, the legitimacy of the user ID and password that should have been input will be confirmed.

For example, once the legitimacy of the user ID and password is confirmed, the process proceeds to FIG. 3 , and a login completion screen SC5 indicating that the membership login for the postpaid service is completed is displayed on the display unit 35 . For example, once the user selects button B50, the user returns to the order confirmation screen SC3. As shown in the order confirmation screen SC3 in Figure 3, once the user logs in as a member of the postpaid service, the user can choose postpaid settlement.

In the example of FIG. 3, the basic items in the postpaid checkout display and the credit card checkout display are the same. However, while credit card checkout displays part of the card number, postpaid checkout does not display the postpaid number equivalent to the card number at all. In addition, the credit card checkout system displays a small icon I30 indicating the brand of the credit card, but in contrast, the postpaid checkout displays a small icon I34 indicating that this is a postpaid checkout instead of the brand. In the example of FIG. 3 , the small icons I30 and I34 present word strings, but they may also present other information such as graphics that can be visually understood as a brand or postpaid checkout.

For example, after the user selects the postpaid checkout button B31, once the order confirmation button B33 is selected, the SMS (Short Message Service) authentication required to perform postpaid checkout will be executed. The user confirms the message sent to the user terminal 30 with the SMS screen SC6. The user operates the user terminal 30 to access the checkout server 10 or the EC server 20 and inputs the confirmation code recorded in the message. Once the SMS authentication is successful, the order completion screen SC7 indicating that the order is completed is displayed on the display unit 35 . In postpaid settlement, you can make installment payments in the same way as in credit card settlement, and you can also set a consumption limit in the same way as in credit card settlement. The consumption amount can also change according to the usage status of the user in the EC service.

In this embodiment, it is assumed that after credit card settlement is introduced to the EC service, postpaid settlement is introduced to the EC service. Even when postpaid billing is introduced, the credit card billing mechanism that has been imported at that point will be used. Therefore, the basic mechanism of postpaid checkout is the same as that of credit card checkout. For example, credit card checkout uses card numbers in a specified format. The so-called format here refers to the number system. For example, the number of digits in a number or the meaning of each digit is equivalent to the format.

The format of the postpaid number itself can be the format of a general credit card number. For example, a typical credit card consists of 14 to 16 digits. The first 6 digits are the issuer identification number (bank identification number) that can be used to identify the card issuing company. The 7th digit to the last digit is the membership account number that can be used to identify the user. The last number is the check code. The format of postpaid numbers is also the same as this format.

In this embodiment, although it is said that a postpaid number is issued, a physical credit card is not issued. Therefore, the postpaid number can also be said to be the card number of a virtual credit card. The issuer identification number of the postpaid number is a number band that does not overlap with the issuer identification number of the card issuing company. For example, if the issuing company that issued the physical credit card did not use the number band with the first 6 digits of "9999-99", then the first 6 digits of the postpaid number would be "9999-99".

In addition, if the same postpaid service is provided in other checkout services, you can also use a number band that does not overlap with other checkout services. For example, if it is assumed that the first 6-digit number band "9999-99" is already used in the postpaid service provided by another business operator, then the postpaid number issued in the checkout system 1 will be The first 6 digits can also be "8888-88". If there is no doubt about confusion with the postpaid service of another provider (for example, when the postpaid service of this embodiment can be identified by other information such as user ID), the postpaid number, The first 6 digits can also be "9999-99".

This embodiment describes the case where postpaid numbers can only be used in EC services, but postpaid numbers can also be used in services other than EC services. The case where the postpaid number can be used in other services will be explained in the modifications described below. In addition, the postpaid number is set and will not be notified to the user. In the example of FIG. 3 , although the registration completion screen SC5 shows that the member registration for the postpaid service has been completed, all the postpaid numbers are hidden words and will not be notified to the user.

As described above, in this embodiment, the postpaid service is introduced using the credit card settlement mechanism already introduced in the EC service. The postpaid number is a number in the same format as a credit card number. The postpaid checkout process is the same as the credit card checkout process. This eliminates the need to build a new system dedicated to postpaid services, thereby reducing the cost of introducing postpaid services. Details of the checkout system 1 are explained below.

[3. Functions implemented in the checkout system] Figure 4 is a diagram illustrating an example of functions implemented in the checkout system 1.

[3-1. Functions implemented in the checkout server] For example, the checkout server 10 includes: a data storage unit 100, a payment determination unit 101, a payment unit 102, an acquisition unit 103, a calculation unit 104, and a postpayment unit. The settlement determination unit 105, the password authentication unit 106, the security code authentication unit 107, the message authentication unit 108, and the postpaid settlement execution unit 109. The data storage unit 100 is realized by the storage unit 12 . The payment determination unit 101, the payment unit 102, the acquisition unit 103, the calculation unit 104, the postpaid settlement determination unit 105, the password authentication unit 106, the security code authentication unit 107, the message authentication unit 108, and the postpaid settlement execution unit 109, This is realized by the control unit 11.

[Data storage unit] The data storage unit 100 stores data necessary for providing checkout services. In this embodiment, the description will mainly focus on the data required for the postpaid service in the checkout service. For example, the data storage unit 100 stores the first user database DB1.

FIG. 5 is a diagram showing an example of the first user database DB1. As shown in FIG. 5 , the first user database DB1 is a database in which various information on users of postpaid services is stored. For example, the first user database DB1 stores: user ID, password, name, address, phone number, email address, postpaid number, validity period, nominee, transaction information in postpaid service, and scores. Once the user completes the membership login of the postpaid service, a new record will be created in the first user database DB1, and various information about the user will be stored.

User ID is an example of user identification information that can be used to identify a user. User identification information is not limited to user ID, as long as it is information that can identify the user in some form. For example, user identification information can also be other information such as phone numbers or email addresses. This embodiment describes the case where the same user ID and password are used for the EC service and the postpaid service. However, different user IDs and passwords may be used for the EC service and the postpaid service. .

The postpaid number is an example of a checkout number. Therefore, wherever a postpaid number is stated, it can be replaced with a checkout number. The checkout number is the number required to use the credit card checkout mechanism to use the number to checkout. Number checkout refers to checkout regarding the checkout number. Number billing is billing other than credit card billing. Postpaid checkout is an example of number checkout. Therefore, where postpaid checkout is described, system can be replaced with number checkout. Number billing can also be billing other than postpaid billing. An example of other checkout will be explained in the modification example described later.

In this embodiment, the postpaid number is associated with the validity period and the nominee of the virtual credit card. Therefore, the checkout number can also be said to be the card number of a virtual credit card. The validity period and nominee of the virtual credit card are in the same format as the validity period and nominee of the physical credit card. For example, the validity period of a virtual credit card is a combination of years and months. The nominee of the virtual credit card is a string of English letters.

Transaction information is information about the user's transactions in the past. In this embodiment, the purchase of goods in the EC service is equivalent to a transaction. Furthermore, among all the transaction information in the EC service, the description is given regarding the transaction information on postpaid settlement that has been executed in the past, but the transaction information may also be as in the modification example described below. Information about billing other than postpaid billing. For example, the transaction information may also include: the date and time when the postpaid settlement was executed, the information of the counterparty of the postpaid settlement, and the amount of the postpaid settlement. Transaction information is updated each time postpaid checkout is executed.

In addition, the data stored in the data storage unit 100 is not limited to the above examples. The data storage unit 100 only needs to store the data necessary for the checkout service. For example, the data storage unit 100 may store the correct password, security code, and confirmation code among the password authentication, security code authentication, and message authentication described below. Each of the correct password, security code, and confirmation code can also be managed in computers other than the checkout server 10.

[Assignment Determination Unit] The assignment determination unit 101 determines whether to permit the assignment of the user's postpaid number based on predetermined assignment conditions. The granting conditions are conditions that serve as a criterion for determining whether to permit the granting of a postpaid number. As long as the conditions are related to any information about the user, any conditions can be set. The so-called assignment of a postpaid number refers to the issuance of a postpaid number or the activation of an issued postpaid number. The assignment of the postpaid number is performed by the assigning unit 102 described below.

In this embodiment, the granting determination unit 101 determines whether granting of the postpaid number to the user is permitted based on information about the user and information other than the transaction information. Other information refers to any information other than transaction information that can be used. An example of other information is the user's credit information obtained from an external credit information agency, but the other information is not limited to the user's credit information. For example, other information may also be transaction information of users in the EC service. For example, other information may also be transaction information of users in other services other than the EC service.

For example, the credit determination unit 101 requests the system of an external credit information organization to transmit the user's credit information. The granting determination unit 101 determines whether granting of a postpaid number is permitted based on the user's credit information acquired from the credit information agency's system. The granting determination unit 101 determines that granting of a postpaid number is not allowed when the user's credit information does not show a level of reliability that exceeds the benchmark; when the user's credit information shows a level of reliability that exceeds the benchmark , determined to be the granting of a permitted postpaid number.

In addition, the determination method provided by the determination unit 101 is not limited to the above-mentioned example. The grant determination unit 101 only needs to determine whether the grant condition is satisfied based on some information about the user. This information can also be transaction information in EC services, or the user's name, address, occupation, annual income, SNS account, or the usage history of a certain service. The allocation determination unit 101 may disallow the allocation of the postpaid number if it determines that the allocation condition is not satisfied, and allows the allocation of the postpaid number if it determines that the allocation condition is satisfied.

[Assignment Department] The assignment section 102 assigns a postpaid number to the user. This embodiment describes the case where the issuing unit 102 issues a new postpaid number once the user completes membership registration for the postpaid service. However, the postpaid number may not be issued at the time of membership registration. It is pre-issued before members log in. For example, the assigning unit 102 may establish a relationship between the user ID and the postpaid number in advance. In this case, raising the activation flag necessary to activate the postpaid number may be equivalent to assigning the postpaid number.

In this embodiment, the assigning unit 102 assigns the postpaid number to the user when it is determined by the granting determination unit 101 that the granting of the postpaid number is permitted. The assigning unit 102 does not assign the postpaid number to the user if it is not determined by the granting determination unit 101 that the granting of the postpaid number is permitted. For example, in this case, the issuing unit 102 does not issue a new postpaid number. When the aforementioned validation flag is used, the providing unit 102 sets the validation flag.

In addition, the determination by the payment determination unit 101 may not be executed. In this case, the checkout server 10 does not include the payment determination unit 101. In this case, the assigning unit 102 unconditionally assigns the postpaid number to the user who has registered as a member without any special review. For example, once the user completes the membership login of the postpaid service, the granting unit 102 may immediately issue a postpaid number unconditionally, or may immediately set up a validation flag unconditionally. Furthermore, the granting unit 102 may unconditionally issue a postpaid number immediately without registering a member for the postpaid service, or may unconditionally raise an activation flag immediately. That is, the postpaid number may be assigned at the time of member registration for the EC service.

In this embodiment, the assigning unit 102 associates the user ID with the postpaid number to assign the postpaid number to the user. The so-called establishment of a relationship here refers to making two pieces of information so that one of them can be used as a search key so that the other can be searched. For example, the assigning unit 102 stores the postpaid number in the record in which the user ID is stored in the first user database DB1, thereby associating the user ID with the postpaid number. The assigning unit 102 may add a postpaid number to the record, or set the validation flag stored in the record to erect, etc.

For example, the assigning unit 102 associates the user ID with a postpaid number that is not associated with a physical credit card, so as to assign the postpaid number to the user. This embodiment describes the case where the postpaid number is the card number of a virtual credit card that does not actually exist. However, the postpaid number may also be a card number associated with a physical credit card. In this case, for the physical credit card, a relationship is established between the normal card number and the postpaid number. Postpaid numbers can also be generated on physical credit cards. You can even create a postpaid number on a card that cannot be used in a real store. There is no ordinary card number on the card.

In this embodiment, the assigning unit 102 assigns the postpaid number to the user without notifying at least part of the postpaid number. The so-called notification here refers to the use of electronic means to output the postpaid number. Postpaid numbers may not be notified at all, or only part of them may be notified. For example, if the postpaid number is 16 digits, it can also be designed so that any digit among the 16 digits is not notified to the user, or only a part of 1 to 4 digits is notified to the user. The user will not be notified of the remaining portion.

In the example of FIG. 2 , from the time when the user starts the membership registration procedure for the postpaid service to the completion of the membership registration for the postpaid service, the granting unit 102 grants the postpaid number to the user without notifying it at all. Postpaid number. Therefore, the postpaid number is not displayed on each screen including the registration completion screen SC5 in FIG. 2 . Even if a message such as an e-mail is sent upon completion of membership registration for the postpaid service, it is designed that the postpaid number will not be notified in this message.

In addition, in the checkout system 1, the postpaid number can also be notified to the user. In this embodiment, although there is no opportunity for the user to input a postpaid number, if the postpaid number is made available in other services, the user may also be able to input the postpaid number in other services. Notify the user of the postpaid number. For another example, the postpaid number may not be notified to the user in principle, but if a disclosure request is specifically received from the user, the postpaid number may be notified to the user.

[Acquisition Department] The acquisition department 103 obtains the user's transaction information. The acquisition unit 103 acquires the user's transaction information for the calculation unit 104 to be described later to calculate points among the plurality of users who use the checkout service. In this embodiment, the transaction information is stored in the first user database DB1, so the acquisition unit 103 acquires the user's transaction information from the first user database DB1. The transaction information may also be stored in other databases other than the first user database DB1, or other server computers other than the checkout server 10. In this case, the acquisition unit 103 obtains transaction information from other databases or other server computers.

In this embodiment, the case where the score is calculated periodically is explained, so the acquisition unit 103 acquires the transaction information periodically. The acquisition unit 103 only needs to acquire the transaction information at the timing when the score is calculated. The timing at which the transaction information is acquired is not limited to the example of this embodiment. For example, if the score is calculated after the postpaid checkout request has been accepted, the acquisition unit 103 may also obtain the transaction information after the postpaid checkout request has been accepted.

In addition, the timing at which the postpaid settlement request is accepted is not limited to the example of this embodiment, and may be any timing. For example, the postpaid billing request may be accepted not after the confirmation request for confirming ordering in the EC service is accepted from the user terminal 30 but before. Others include, for example, when the user is asked to select a checkout method after confirming the order, the postpaid checkout request can also be processed only after the request is confirmed to be accepted and the user selects the checkout method. accepted.

[Calculation Section] The calculation section 104 calculates a score regarding the user's trustworthiness based on the transaction information obtained by the acquisition section 103 . This embodiment explains the case where the fraction system is represented by numerical values, but the fraction system may also be represented by characters or symbols. In this embodiment, the explanation is that the higher the numerical value of the score, the higher the reliability. However, as long as there is a correlation between the score and the reliability, the lower the numerical value of the score, the higher the reliability. .

Furthermore, it is assumed that data indicating the relationship between transaction information and points is stored in the data storage unit 100 . This embodiment describes the case where the data is in a numerical format, but the data may be in a table format or a program code. The data may also be a machine learning model that has learned the relationship between transaction information and scores. The calculation unit 104 calculates the score based on the transaction information and the above data.

For example, the calculation unit 104 digitizes the transaction information and calculates the score based on a predetermined rule. This rule can set any rules, such as: transaction amount of each transaction, total amount of transaction amount, unpaid amount, total unpaid amount, number of transactions, frequency of transactions, number of unpaid times, unpaid frequency, trading place , or distance from the center of use, etc. The calculation unit 104 calculates these numerical values based on rules to calculate the score. For example, the calculation unit 104 calculates the score in such a way that the greater the transaction amount or its total amount and the smaller the unpaid amount or its total amount, the higher the user's reliability. The calculation unit 104 associates the user's score with the user ID of the user and stores it in the first user database DB1.

In this embodiment, the calculation unit 104 regularly calculates the score based on the latest transaction information. For example, the calculation unit 104 calculates the score once a day. The period in which the score is calculated may not be every day, but any period. For example, the calculation unit 104 may calculate the score every half day, every several days, every week, or every month. By calculating points regularly, the calculation of points has already been completed when the user places an order in the EC service.

In addition, the calculation unit 104 may also calculate scores from time to time. For example, the calculation unit 104 may also calculate the score every time the user logs in to the EC service. For example, the calculation unit 104 may calculate the score on the spot when the user orders goods in the EC service (that is, when the postpaid checkout request is accepted). The calculation unit 104 only needs to complete the calculation of the score at the time when the judgment by the postpaid settlement judgment unit 105 is executed, and the score may be calculated at any other time sequence.

[Postpaid settlement determination unit] The postpaid settlement determination unit 105 determines whether to allow postpaid settlement based on the score when a postpaid settlement request for a postpaid number has been accepted. Postpaid billing requirements are the requirements required to execute postpaid numbers. Postpaid checkout requests are in the same format as credit card checkout requests. The format required for postpaid checkout only needs to be in compliance with the API for credit card checkout. This embodiment describes the case where the postpaid settlement request is transmitted from the EC server 20, but the postpaid settlement request may be transmitted from other computers such as the user terminal 30 or a store terminal.

In this embodiment, the payment request for credit card payment and the payment request for postpaid payment are taken as examples. Hereinafter, these are referred to as credit card settlement requirements and postpaid settlement requirements, respectively. As mentioned above, credit card billing requirements and postpaid billing requirements are in the same format as each other. The format itself may be a format defined in a well-known credit card settlement API. That is, the data structure itself of the header or real data portion contained in each of the credit card checkout request and the postpaid checkout request may be a publicly known data structure.

For example, credit card billing requirements and postpaid billing requirements contain a 14-digit to 16-digit value, validity period, and nominee. When requesting credit card payment, the 14-digit to 16-digit value represents the card number of the physical credit card. When postpaid billing is required, the 14-digit to 16-digit value represents the postpaid number. Although the data structure of credit card payment request and postpaid payment request are in the same format, the 14-digit to 16-digit number bands are different, so it can be distinguished based on the number band. Checkout requirements. Credit card billing requests and postpaid billing requests also include other information such as the billing amount.

For example, the postpaid settlement determination unit 105 specifies which type of payment is based on the 14-digit to 16-digit number band included in each of the credit card settlement request and the postpaid settlement request. Account requirements. In this embodiment, it is assumed that the number band system of the postpaid number is "9999-99". The postpaid billing determination unit 105 determines that the billing request is a postpaid billing request if it is a number band of "9999-99". The postpaid settlement determination unit 105 determines whether to allow postpaid settlement when it is determined that the request is for postpaid settlement. The postpaid settlement determination unit 105 determines that if the settlement request is for another number, it is a credit card settlement request. When the postpaid settlement determination unit 105 determines that the request is a credit card settlement, it does not determine whether to allow postpaid settlement.

For example, the postpaid settlement determination unit 105 determines whether the score is equal to or higher than a threshold, and determines whether postpaid settlement is permitted based on the corresponding determination result. In this embodiment, the higher the numerical value represented by the score, the higher the reliability. Therefore, if the postpaid settlement determination unit 105 determines that the score is less than the threshold, it determines that postpaid settlement is not allowed. , if it is determined that the score is above the threshold, it is determined that postpaid settlement is permitted. The threshold can be a fixed value common to all users, or it can be determined by the user.

In addition, when the relationship between scores and reliability is inverse (the lower the numerical value represented by the score, the higher the reliability), the postpaid settlement determination unit 105 determines that the score is equal to or above the threshold. If the score is below the threshold, it will be determined that postpaid settlement is not allowed. If it is determined that the score is less than the threshold, it will be determined that postpaid settlement is allowed. If the score is represented by characters or other symbols, the postpaid settlement determination unit 105 determines that the postpaid settlement is not allowed if the score is a character or symbol indicating relatively low reliability. If it is determined to be a character or symbol indicating relatively high reliability, it is sufficient to determine that postpay settlement is permitted.

In this embodiment, the postpaid settlement determination unit 105 determines whether postpaid settlement is permitted when the postpaid settlement request has been accepted due to the user's operation on the order confirmation screen SC3. The order confirmation screen SC3 is an example of the checkout screen. Therefore, the place described as order confirmation screen SC3 can be replaced with a checkout screen. The checkout screen is a screen related to number checkout, which is an example of later pay checkout. The checkout screen is a screen required for making a postpaid checkout request or for selecting a checkout method.

For example, the postpaid settlement determination unit 105 determines whether postpaid settlement is permitted when postpaid settlement is selected on the order confirmation screen SC3 and the postpaid settlement request has been accepted. When the user's payment method is fixed to post-pay payment, the post-pay payment determination unit 105 may still determine whether to allow post-pay even if there is no user operation on the order confirmation screen SC3. Checkout. For example, when a postpaid checkout request is sent from a computer in a store, the postpaid checkout determination unit 105 may still determine whether or not to approve the request even if there is no user operation on the order confirmation screen SC3. Pay checkout.

In addition, when the credit card settlement request has been accepted, the processing required to perform the credit card settlement will be performed. This process itself may be a well-known process. For example, the data storage unit 100 stores data indicating the relationship between the first six digits of the issuer identification number in the card number and the identification information (eg, IP address) of the card issuing company's server. The checkout server 10 performs a series of processes such as requesting the server of the card-issuing company associated with the card number included in the credit card checkout request, such as the first six-digit issuer identification number, and requesting credit. Once the checkout server 10 receives the processing result from the card issuing company's server, it transfers the processing result to the EC server 20 .

[Password Authentication Department] The password authentication unit 106 omits password authentication when a request for postpaid settlement has been accepted for postpaid settlement, and when a request for credit card settlement has been accepted for credit card settlement. Next, password authentication is performed. Postpaid checkout request is an example of the first checkout request. The credit card payment request is an example of the second payment request. Therefore, where the postpaid checkout requirement is stated, it may be replaced by the first checkout requirement. Where credit card billing requirements are explained, the system can be replaced with the second billing requirement.

The first settlement request is a request required to perform number settlement as an example of postpay settlement. The first checkout request is a request in the same format as the second checkout request. The format of the first checkout request and the second checkout request only needs to be a format that conforms to the credit card checkout API. In principle, the first checkout request and the second checkout request are performed by sending data with the same data structure. The difference between the first checkout request and the second checkout request is, in principle, a number band equivalent to the value of the card number or postpaid number. This embodiment describes the case where the first settlement request and the second settlement request are sent from the EC server 20 , but the first settlement request and the second settlement request may also be sent from the user terminal 30 or other computers such as store terminals.

Password authentication is authentication using the password registered by the user in advance. If the pre-registered password is inconsistent with the password entered by the user, the password authentication will be unsuccessful. If they are consistent, the password authentication will be successful. In this embodiment, a password authentication called 3D security verification using a password associated with a physical credit card is taken as an example, but the password authentication system may also be called by other names. For example, password authentication can also use the password required to log in to the checkout service, or other passwords.

[Security Code Authentication Department] The security code authentication unit 107 omits the security code authentication when the postpaid payment request has been accepted, and executes the security code authentication for the user when the credit card payment request has been accepted. Security code authentication. Security code authentication is an authentication using a security code (for example, a 2-digit or 3-digit code printed on the back) formed on the physical credit card. If the security code formed on the physical credit card is inconsistent with the security code entered by the user, the security code authentication will be unsuccessful. If they are consistent, the security code authentication will be successful.

[Message Authentication Section] The message authentication section 108 is the message authentication section 108 that performs message authentication with the user terminal when the postpaid settlement request has been accepted. Message authentication is authentication using messages containing authentication information. If the authentication information contained in the message is inconsistent with the authentication information entered by the user, the message authentication will be unsuccessful. If they are consistent, the message authentication will be successful.

In this embodiment, the SMS authentication is equivalent to the message authentication, but the message authentication may be of other types, for example, it may be authentication using email, messaging application, or SNS. In addition, the authentication information used in message authentication is not limited to the confirmation code illustrated in FIG. 3 . For example, authentication information can also be embedded in the parameters of a link contained in the message. In this case, if the user selects the link, there is no need to manually enter information such as a confirmation code to complete the message authentication.

In this embodiment, the message authentication unit 108 executes the message authentication after the postpaid settlement request has been accepted and before the postpaid settlement is executed. However, the message authentication unit 108 may also perform the message authentication. Message authentication is only performed after postpaid checkout is executed. In this case, if the message authentication has not been completed by the specified period, the postpaid settlement may also be cancelled.

[Postpaid Settlement Execution Unit] The postpaid settlement execution unit 109 executes postpaid settlement when it is determined that postpaid settlement is permitted by the postpaid settlement determination unit 105 . The postpaid settlement execution unit 109 does not execute postpaid settlement when it is determined by the postpaid settlement determination unit 105 that postpaid settlement is not permitted. The so-called execution of postpaid settlement refers to at least part of the processing required to execute postpaid settlement.

Postpaid checkout itself can be performed through various processes. For example, like in this embodiment, when postpaid settlement is one type of bill bill, the postpaid bill execution unit 109 generates storage information equivalent to the bill by executing: processing, processing of sending charging information to the charging agency, processing of generating payment slip data, processing of printing payment slips, processing of outputting information required for mailing payment slips, or a combination of these, to execute Pay checkout.

In this embodiment, the postpaid settlement execution unit 109 executes postpaid settlement when it is determined by the postpaid settlement determination unit 105 that postpaid settlement is permitted and the message authentication is successful. . The postpaid settlement execution unit 109 does not execute postpaid settlement when it is determined by the postpaid settlement determination unit 105 that postpaid settlement is not allowed or when the message authentication is unsuccessful.

[3-2. Functions implemented in the EC server] For example, the EC server 20 includes a data storage unit 200, a service providing unit 201, and a display control unit 202. The data storage unit 200 is realized by the storage unit 22. The service providing unit 201 and the display control unit 202 are realized by the control unit 21.

[Data storage unit] The data storage unit 200 stores data necessary for providing EC services. For example, the data storage unit 200 stores the second user database DB2.

FIG. 6 is a diagram showing an example of the second user database DB2. The second user database DB2 is a database in which various information on users of the EC service is stored. For example, the second user database DB2 stores: user ID, password, name, address, phone number, email address, checkout method information, and transaction information in the EC service. Once the user completes the membership login of the EC service, a new record will be created in the second user database DB2, and various information about the user will be stored.

The checkout method information is information about the checkout method used by the user to log in to the EC service. For example, if the user has registered a credit card to the EC service, the payment method information indicates the card number, expiration date, and nominee of the credit card. In this embodiment, it is assumed that the user can log in to the EC service with multiple credit cards. Therefore, even after the user completes membership registration for the postpaid service and is issued a postpaid number, the user can still add a postpaid number as if it were a set of credit card numbers using the same process as adding a credit card.

For example, when the user has registered as a member of the postpaid service, the checkout method information indicates the postpaid number, validity period, and nominee. This information is assumed to be sent from the checkout server 10 to the EC server 20 after the member of the postpaid service logs in. Since the user ID is common between the checkout service and the EC service, the EC server 20 can identify which user's postpaid number this is. The EC server 20 is associated with the user ID of the specified user, and stores the information such as the postpaid number in the second user database DB2.

For example, when the user has logged in to the EC service with a bank account, the settlement method information indicates the financial institution code, branch name, and account number of the bank account. The checkout method information of users who use postpaid services shows the postpaid number, validity period, and nominee. Where other checkout methods are available in the EC Service, information about the other checkout methods will be stored. Transaction information includes information such as the product purchased in the EC service, the amount used, and the date and time of use. Every time the user uses the EC service, the transaction information is updated.

[Service Provision Department] Service Provision Department 201 provides EC services. The EC service provision method itself can utilize various known methods. For example, the service providing unit 201 receives an order request for ordering goods from the user terminal 30 . The service providing unit 201 sends the data required for the checkout selected by the user to the checkout server 10 . When receiving a notification indicating that checkout has been completed from the checkout server 10, the service providing unit 201 generates transaction information and stores it in the second user database DB2.

For example, when the user selects credit card settlement, the service providing unit 201 sends a credit card settlement request to the settlement server 10 . The credit card settlement request includes the card number, expiration date, and nominee of the user's credit card that has been stored in the second user database. When the user selects postpaid settlement, the service providing unit 201 sends a postpaid settlement request to the settlement server 10 . The postpaid billing request includes the user's postpaid number, validity period, and nominee that have been stored in the second user database.

For example, if the checkout service supports other checkout methods other than credit card checkout and postpaid checkout, for example, the service providing unit 201 once the user selects other checkout methods, based on the other checkout methods. The checkout method information is sent to the checkout server 10, and the checkout request required for executing other checkout methods is sent.

[Display Control Unit] The display control unit 202 instructs various screens regarding the EC service to be displayed on the user terminal 30. For example, the display control unit 202 displays the order confirmation screen SC3 necessary for making a postpaid payment request without notifying the user of at least a part of the postpaid number. In this embodiment, the display control unit 202 causes the order confirmation screen SC3 to be displayed without notifying the postpaid number at all.

For example, the display control unit 202 sends the display data of the order confirmation screen SC3 to the user terminal 30 so that the order confirmation screen SC3 is displayed. Display data only needs to be used to display a certain screen, such as HTML data. When the order confirmation screen SC3 is displayed on an EC service-dedicated application instead of a browser, the display control unit 202 only needs to send display data in a format that can be displayed on the application.

For example, the display control unit 202 instructs the order confirmation screen SC3 required to accept the user's selection between postpaid payment and other payment methods, and separates postpay payment and other payment methods. Each one is distinguished and displayed. The difference here means that the first information indicating that this is postpaid payment and the second information indicating that this is other payment method are displayed on the order confirmation screen SC3. In the example of FIG. 3 , the display control unit 202 uses small icons I30 and I34 to distinguish them. Therefore, small icon I34 is equivalent to the first information, and small icon I30 is equivalent to the second information. .

In addition, the method of distinguishing postpaid payment from other payment methods is not limited to the method using the small icons I30 and I34. The display control unit 202 only needs to make the information about postpaid settlement and the information about other settlement methods visually different in some form. For example, the display control unit 202 may display a first character string indicating that this is a postpaid settlement and a second character string indicating that this is another payment method, so as to distinguish them. For example, the color of the button B31 required for selecting postpaid payment and the button B31 required for selecting credit card payment are used to distinguish them.

[3-3. Functions implemented in the user terminal] For example, the user terminal 30 includes a data storage unit 300, a display control unit 301, and an operation acceptance unit 302. The data storage unit 300 is realized by the storage unit 32. The display control unit 301 and the operation acceptance unit 302 are realized by the control unit 31 .

[Data storage unit] The data storage unit 300 stores data required for each person to use the checkout service and the periodic payment service. For example, the data storage unit 300 stores application programs for each of the checkout service and the regular payment service.

[Display Control Unit] The display control unit 301 causes the display unit 35 to display each screen described in FIGS. 2 and 3 .

[Operation Acceptance Unit] The operation acceptance unit 302 accepts operations on each screen described in FIG. 2 and FIG. 3 .

[4. Processing executed in the checkout system] FIG. 7 is a diagram illustrating an example of processing executed in the checkout system 1. This processing is executed when the control units 11, 21, and 31 operate according to the programs memorized in the memory units 12, 22, and 32, respectively. FIG. 7 illustrates the processing in the case where the user logs into the EC service, enters the procedure for ordering the product that has been placed in the shopping basket, and then selects button B32 from the order confirmation screen SC3.

As shown in FIG. 7 , the user terminal 30 is connected with the checkout server 10 and executes the necessary processing for displaying the member login screen SC4 (S1). The member login screen SC4 may be displayed not from the order confirmation screen SC3 but from other screens such as the top screen SC2. The member login screen SC4 may be displayed on the domain of the EC service, but in this embodiment, it is displayed on the domain of the checkout service. The user terminal 30 executes processing necessary to confirm the validity of the user ID and password with the checkout server 10 (S2).

In S2, the user terminal 30 sends the user ID and password that have been input into the input forms F40 and F41 to the checkout server 10. Once the checkout server 10 receives the user ID and password, it confirms their validity. At this point, since the user ID and password have not yet been stored in the first user database DB1, the checkout server 10 uses the EC service and other databases managed by the checkout service provider to confirm the use. The validity of the user ID and password. It is assumed that the correct user ID and password are stored in other databases.

Once the checkout server 10 confirms the validity of the user ID and password, it queries the system of the external credit information agency for the user's credit information (S3). In S3, the checkout server 10 sends information that can identify the user such as name, address, and phone number to the external credit information agency system. This information is assumed to be stored in other databases mentioned above. The system of the external credit information agency identifies the user based on the information received from the checkout server 10 and sends the credit information to the checkout server 10 . Credit information itself can make use of various information.

The checkout server 10 determines whether to assign a postpaid number based on the user's credit information (S4). In S4, the checkout server 10 determines that the postpaid number is not assigned if the user's reliability represented by the credit information is less than a predetermined standard, and if the reliability is above the standard. , it is determined that a postpaid number needs to be assigned. If it is determined that the postpaid number is not assigned (S4: N), this process ends. In this case, an error message will be displayed on the user terminal 30, and the membership login for the postpaid service will not be completed. The user uses a checkout method other than postpaid checkout to order goods.

If it is determined in S4 that a postpaid number is to be assigned (S4: Y), the checkout server 10 issues a postpaid number in the same format as the credit card number, and assigns the newly issued number to the user. Pay number (S5). In S5, the checkout server 10 issues a postpaid number whose first six digits are "9999-99" so as not to overlap with an already issued postpaid number. The checkout server 10 creates a new record in the first user database DB1, and stores information such as the user ID or postpaid number in the record. The checkout server 10 sends information such as the postpaid number to the EC server 20 . The EC server 20 stores information such as postpaid numbers in the second user database DB2.

Through the above processing, the membership registration for the postpaid service is completed, and the user can now select postpaid settlement in the EC service. The checkout server 10 calculates the score based on the transaction information stored in the first user database DB1 (S6). In S6, the checkout server 10 calculates the score of each user based on the user's transaction information and the calculation formula of the score. The checkout server 10 periodically executes the processing of S6 to update the points stored in the first user database DB1.

The user terminal 30 and the EC server 20 execute the necessary processing for displaying the order confirmation screen SC3 (S7). In S7, the EC server 20 specifies the brand using the first digit of the card number based on the checkout method information stored in the second user database DB2, and assigns the card number to the specified brand. The corresponding small icon I30 is selected. The EC server 20 selects the small icon I34 indicating postpaid checkout if the first 6 digits of the card number are "9999-99". The EC server 20 generates the display data of the order confirmation screen SC3 including these small icons I30 and I34, and sends it to the user terminal 30.

Once the user selects button B33, the user terminal 30 sends an order request to the EC server 20 (S8). Once the EC server 20 receives the order request from the user terminal 30 (S9), the EC server 20 sends a checkout request corresponding to the checkout method selected by the user to the checkout server 10. (S10). In S10, the EC server 20 sends a checkout request including the checkout method information stored in the second user database DB2.

Upon receiving the checkout request (S11), the checkout server 10 specifies the checkout method selected by the user (S12). In S12, the checkout server 10 specifies credit card checkout, postpaid checkout, or other checkout based on the information included in the checkout request. Since the basic formats of credit card checkout and postpaid checkout are the same, the checkout server 10 determines which one is selected based on the first 6-digit number band. Other checkouts have a different format from credit card checkout and postpaid checkout, so the checkout server 10 specifies other checkouts based on the format of the checkout request received in S11.

In S12, when the credit card settlement has been specified (S12: credit card settlement), the settlement server 10 performs password authentication and security code authentication as needed, executes the credit card settlement (S13), and ends This processing. The process of password authentication, security code authentication, and credit card checkout is performed as described above.

In S12, when postpaid settlement has been specified (S12: postpaid settlement), the settlement server 10 performs the settlement based on the user's score stored in the first user database DB1. Determine whether to perform postpaid settlement (S14). If it is determined that postpaid settlement is not performed (S14: N), this process is ended. In this case, an error message will be displayed on the user terminal 30 and the postpaid settlement will not be completed. The user uses a checkout method other than postpaid checkout to order goods.

In S14, if it is determined that postpaid settlement is to be performed (S14: Y), SMS authentication is performed between the settlement server 10 and the user terminal 30 (S15). The SMS authentication process in S15 is as described previously. Once the SMS authentication is successful, the checkout server 10 executes postpaid checkout (S16) and ends this process. In S16, the checkout server 10 performs postpaid checkout by performing processing required for mailing the payment slip to the user. Once the checkout server 10 sends the completion of the processing of S16 to the EC server 20, the EC server 20 executes the processing required to confirm the order.

In S12, when the other checkout has been specified (S12: Others), the checkout server 10 executes the other checkout (S17) and ends this process.

The checkout system 1 of this embodiment determines whether to allow postpayment of the postpaid number based on the user's score when a postpaid checkout request for a postpaid number in the same format as a credit card number has been accepted. Checkout. The checkout system 1 executes postpaid checkout when it is determined that postpaid checkout is permitted. In this way, since the credit card settlement mechanism can be used to introduce postpaid services, the cost of introducing postpaid services can be reduced. For example, in the EC service, multiple credit cards can be registered, so by registering the postpaid number as one of them, the existing mechanism can be used. Even before post-paid checkout is executed, it will be determined based on the user's score whether to allow post-paid checkout. Therefore, malicious users who do not pay for the goods can be prevented from being allowed to post-paid checkout. . It is also considered to confirm the user's trustworthiness when the postpaid number is assigned, but a malicious user may pass the trustworthiness check at this point by pretending to be a trustworthy user. The checkout system 1 checks the user's trustworthiness when executing postpaid checkout, and therefore can reliably prevent malicious users from using postpaid checkout.

In addition, the checkout system 1 determines whether to allow the granting of the user's postpaid number based on information about the user, which is information other than the transaction information. This prevents malicious users from being assigned postpaid numbers. For example, it is possible to immediately assign a postpaid number unconditionally, but until the transaction information of malicious users is accumulated to a certain extent, there is still a possibility that fraud cannot be prevented. In this regard, as in the embodiment, malicious use can be reliably prevented by determining whether to allow the granting of a postpaid number based on other information such as credit information obtained from the system of an external credit information provider. Improper behavior caused by the person.

In addition, the checkout system 1 associates the user ID with the postpaid number that is not associated with the physical credit card, thereby assigning the postpaid number to the user. This saves you the hassle of issuing a physical credit card for postpaid billing.

In addition, the checkout system 1 assigns the postpaid number to the user without notifying at least part of the postpaid number, causes the order confirmation screen SC3 to be displayed, and executes a series of processes in the postpaid checkout. This prevents postpaid numbers from being leaked to malicious third parties. For example, if the postpaid number is a dedicated number that can only be used in the EC service, even if the user does not know the postpaid number, as long as the postpaid number is managed on the EC service or the checkout service side, the postpaid number can still be executed. Pay checkout. Therefore, postpaid checkout can be performed without reducing convenience for legitimate users.

Furthermore, in the settlement system 1, the transaction information is information on postpaid settlements that have been executed in the past. By this, the scores corresponding to postpaid settlements that have been performed in the past can be calculated, so the user's trustworthiness can be accurately evaluated, and the use of postpaid settlements by malicious users can be reliably prevented. . For example, although the score can be calculated based on transaction information related to transactions other than postpaid checkout, if a malicious user disguises himself as a legitimate user in other transactions, there is a risk that it cannot be prevented. There is a possibility of late-pay settlement caused by malicious users. However, by calculating the score corresponding to the actual later-pay settlement, the reliability corresponding to the actual later-pay settlement can be evaluated.

Furthermore, the checkout system 1 omits password authentication when a postpaid checkout request has been accepted, and performs password authentication when a credit card checkout request has been accepted. In this way, when postpaid checkout does not require as high security as credit card checkout, redundant authentication can be omitted, thereby improving user convenience. For example, assuming postpaid checkout does not support high-value checkout, but credit card checkout does support high-value checkout. In this case, even if an error occurs in postpaid settlement, the amount of damage can still be limited to a low amount. Therefore, by omitting password authentication, user convenience can be prioritized over security. It also reduces the hassle of managing passwords for postpaid checkout.

In addition, the checkout system 1 omits security code authentication when a postpaid checkout request has been accepted, and performs security code authentication when a credit card checkout request has been accepted. In this way, when postpaid checkout does not require as high security as credit card checkout, redundant authentication can be omitted, thereby improving user convenience. For example, assuming postpaid checkout does not support high-value checkout, but credit card checkout does support high-value checkout. In this case, even if an error occurs in postpaid settlement, the amount of damage can be limited to a low amount. Therefore, by omitting the security code authentication, user convenience can be prioritized over security. It also reduces the hassle of managing security codes for postpaid checkout.

In addition, the checkout system 1 causes the order confirmation screen SC3 to display the postpaid checkout and other checkout methods separately. Thereby, the user can easily confirm postpaid settlement and other settlement methods on the order confirmation screen SC3, thereby improving user convenience. For example, if you use the credit card checkout mechanism to import postpaid checkout, there will also be the possibility that credit card checkout is similar to postpaid checkout on the user interface, but through the small icons I30 and I34, you can Distinguish between postpaid checkout and credit card checkout, so users can avoid mistakenly selecting credit card checkout when they want to use postpaid checkout. On the contrary, when the user wants to use a credit card to settle the bill, it can also prevent the user from mistakenly selecting postpaid settlement.

In addition, the checkout system 1 performs message authentication with the user terminal 30 when the postpaid checkout request has been accepted. This prevents third parties who log in pretending to be users from using postpaid checkout, thereby improving security.

[5. Modification] In addition, the present disclosure is not limited to the embodiment described above. Appropriate changes may be made within the scope that does not deviate from the purpose of this disclosure.

[5-1. Modification 1] For example, the embodiment describes a case where the score is calculated based on the transaction information of postpaid settlement that has been executed in the past. Transaction information may also be transaction information for services other than postpaid services. For example, the score can also be calculated based on transaction information of services other than postpaid services among a series of services provided by the checkout service. For example, the score can also be calculated based on transaction information for services other than checkout services.

Postpaid service is an example of the first service. Services other than postpaid services are examples of the second service. Therefore, where postpaid service is described, it can be replaced by the first service. Where other services are described, they can be replaced by the second service. The combination of the first service and the second service can be any combination. The business operator of the first service and the business operator of the second service may be the same as each other, or they may be different from each other.

In Modification 1, an EC service is explained as an example of the second service. It is assumed that the user has already used the EC service to some extent by paying with a credit card before the postpaid service starts. The second user database DB2 also stores the transaction information of the user's EC service before the start of the postpaid service. The acquisition unit 103 of Modification 1 acquires the transaction information in the EC service that is different from the postpaid settlement postpaid service based on the user ID.

For example, the acquisition unit 103 requests the EC server 20 for the transaction information of the user who is the target of the score calculation. The EC server 20 refers to the second user database DB2 and sends the transaction information of the user in the EC service in response to the request from the checkout server 10 . The acquisition unit 103 acquires the transaction information of the user in the EC service from the EC server 20 .

In Modification 1, as in the embodiment, the case where the user ID of the checkout service and the user ID of the EC service are the same is explained. However, if these user IDs are different, then the user ID of the settlement service is the same. At least one of the account server 10 and the EC server 20 maintains a correspondence relationship between these user IDs. At least one of the checkout server 10 and the EC server 20 can specify which user's transaction information is to be obtained based on this corresponding relationship.

The calculation unit 104 of Modification 1 calculates the score based on the transaction information in the EC service. The transaction information of the EC service is used for the calculation of points, which is different from the implementation form. However, the point calculation method itself can be the same as the implementation form. For example, the calculation unit 104 digitizes the transaction information of the EC service and substitutes the numerical value into the calculation formula to calculate the score. For example, the calculation unit 104 calculates the score in such a way that the greater the user's transaction amount and the greater the number of successfully completed transactions, the higher the user's reliability.

The checkout system 1 of modification 1 calculates the score based on the transaction information in the EC service. In this way, even users who have no usage performance in postpaid services or have fewer users can still calculate the correct score by taking into account their transactions in other services. For example, even if a user has just started using a postpaid service, the user's trustworthiness can still be evaluated to determine whether to perform postpaid settlement.

[5-2. Modification 2] For example, Modification 1 describes the case where the score is calculated based on the transaction information of one second service, the EC service, but the acquisition unit 103 can also obtain a plurality of second services. Transaction information among the parties to the service. For example, when the checkout service is linked to five second services, namely EC service, travel reservation service, financial service, communication service, and electronic book service, the acquisition unit 103 can also link these five second services. The transaction information of each of them can be obtained.

In Modification 2, it is assumed that the above five services are provided by the same business operator. Even, assume that the above five services use a common user ID. Since the user IDs in postpaid services are also common, using the user ID of a certain user, the user's transaction information in the above five services can be obtained.

The calculation unit 104 calculates the score based on the transaction information in each of the plurality of second services. This point differs from the embodiment in that the transaction information of each of the plurality of second services is used for the calculation of the score, but the score calculation method itself is the same as explained in the embodiment. For example, the calculation unit 104 may calculate the user's score for each second service, and calculate the total or average of the scores of each of the five second services as the final score. The calculation unit 104 may also digitize the transaction information of each of the five second services and substitute it into the calculation formula to calculate a score.

The checkout system 1 of Modification 2 acquires transaction information on each of the plurality of second services, and the calculation unit 104 calculates a score based on the transaction information on each of the plurality of second services. Thereby, the transactions of the users among the plurality of second service providers can be comprehensively considered and the correct score can be calculated.

[5-3. Modification 3] For example, number settlement can be any other settlement than credit card settlement, and is not limited to postpaid settlement. In the number payment, it is sufficient to use any payment method other than credit card. Modification 3 takes as an example a case where, in addition to postpaid settlement, bank automatic debit settlement and encrypted asset settlement can also be used as number settlement. That is, in Modification 3, it is designed so that three types of numbers can be used for settlement.

Automatic bank debit settlement is a settlement that automatically deducts the usage amount from the bank account. In other words, automatic bank deduction settlement is a settlement that uses a bank account as the settlement method. Automatic bank debit settlement is similar to credit card settlement in that it uses a bank account, but it takes about 1 to 2 months for credit card settlement to be automatically debited. In contrast, automatic bank debit is Checkout is different in that, in principle, automatic deductions are performed immediately.

Crypto-asset settlement refers to settlement using crypto-assets. In other words, crypto-asset settlement is settlement using crypto-assets as a settlement method. In Modification 3, it is assumed that the EC service and settlement service providers also provide crypto-asset services. Furthermore, it is assumed that the crypto-asset service uses the same user ID as the EC service and the checkout service. Therefore, as long as the user ID of the EC service and checkout service is available, the encrypted assets held by the user can be identified. Various techniques can be used to utilize the checkout itself of crypto-assets. Crypto assets themselves can also be used in various types.

In addition, for automatic bank deductions and encrypted asset settlements, additional member login procedures may also be required. In this case, the member login process for each of bank automatic debit settlement and crypto asset settlement can be the same as for postpaid settlement. For example, as long as the member login for any one of postpaid payment, automatic bank deduction payment, or crypto asset payment is completed, payment for other numbers will automatically become available. As for which of these three numbers to use for checkout, the user can freely choose, or as long as the member who uses any one number to checkout completes the login, the remaining two numbers will automatically become available for checkout. use.

The assigning unit 102 of Modification 3 assigns to the user a postpaid number corresponding to the type selected by the user from a plurality of types of checkout methods. In Modification 3, since three types of number settlement are possible, there are three number bands. For example, for postpaid checkout, the first 6 digits are "9999-99". For automatic bank deduction and settlement, the first 6 digits are "8888-88". For encrypted asset checkout, the first 6 digits are "7777-77". The number tape used for checking out each number can be any number tape and is not limited to the example of Modification 3.

FIG. 8 is a diagram illustrating an example of functional blocks in Modification 3. The checkout system 1 of Modification 3 includes a processing execution unit 203 . The processing execution unit 203 is realized by the control unit 21. The processing execution unit 203 executes predetermined processing based on the type corresponding to the number band of the number checkout. The prescribed processing is the processing corresponding to the type of number checkout. In Modification 3, it is explained that the processing of displaying the small icon I34 corresponding to the number checkout is equivalent to the prescribed processing, but the prescribed processing can be any processing and is not limited to the example of Modification 3. .

For example, in the case where the availability of installment payment varies depending on the type of billing number, the prescribed processing may also be a process that determines the availability of installment payment. For example, if the sending target of the checkout request varies depending on the type of number checkout, the processing system may also be to specifically process the sendee target of the checkout request. For example, if the format of the checkout request varies depending on the type of number checkout, the predetermined processing system may also be a process of generating a checkout request in a format corresponding to the type of number checkout. .

In Modification 3, the processing execution unit 203 includes the function of the display control unit 202 described in the embodiment. For example, the processing execution unit 203 instructs the order confirmation screen SC3 required for making a checkout request to display the small icon I34 of the type corresponding to the number band of the checkout number. Small icon I34 is an example of this type of image. Therefore, the description of the small icon I34 can be replaced by the category image. The type of image can also be other images other than the small icon I34. For example, the category image system may also be a string, number, or other symbol.

FIG. 9 is a diagram showing an example of the order confirmation screen SC3 of Modification 3. FIG. For example, the processing execution unit 203 causes the small icon I34 of the type corresponding to the number band of the checkout number to be displayed on the order confirmation screen SC3. The relationship between the number band and the small icon I34 is stored in the data storage unit 200. The processing execution unit 203 causes the small icon I34 of the type associated with the number band of the checkout number used by the user to be displayed on the order confirmation screen SC3.

For example, when the first six digits of the settlement number are "9999-99", the processing execution unit 203 selects the small icon I34 indicating postpaid settlement. When the first six digits of the settlement number are "8888-88", the processing execution unit 203 selects the small icon I34 indicating automatic bank deduction settlement. When the first six digits of the settlement number are "7777-77", the processing execution unit 203 selects the small icon I34 indicating the settlement of the crypto-asset. The processing execution unit 203 causes the order confirmation screen SC3 including the selected small icons I34 to be displayed.

For example, the postpaid settlement determination unit 105 determines whether or not number settlement is permitted when the settlement request has been accepted due to the user's operation on the order confirmation screen SC3. This differs from the embodiment in that an arbitrary number can be selected for settlement from the order confirmation screen SC3. However, the determination method itself of the postpaid settlement determination unit 105 is the same as that of the embodiment.

The checkout system 1 of Modification 3 assigns to the user a postpaid number corresponding to the type selected by the user from among plural types of checkout methods. The checkout system 1 executes predetermined processing based on the type corresponding to the number band. Thereby, processing corresponding to the type of number checkout selected by the user can be executed, thereby improving user convenience. Furthermore, by checking out the number band of the checkout number, you can easily identify which checkout number has been selected.

Furthermore, the checkout system 1 causes the order confirmation screen SC3 to display a small icon I34 of the type corresponding to the number band of the checkout number. The checkout system 1 determines whether to allow number checkout when the checkout request has been accepted by the user's operation on the order confirmation screen SC3. This makes it easy to confirm the number for checkout in the order confirmation screen SC3, thereby improving user convenience. When the user wants to perform checkout with a certain number, it can prevent the user from mistakenly selecting another number for checkout.

[5-4. Modification 4] For example, in the embodiment, postpaid checkout is used in an EC service provided by the same provider as the checkout service. However, it may also be used in an EC service provided by a different provider than the checkout service. Use postpaid billing for external services provided by the provider. Modification 4 explains the case where the postpaid number can be used for external services provided by a different provider than the issuer of the postpaid number. Furthermore, as an example of an external service, a food delivery service provided by a business operator different from the EC service described in the embodiment will be described.

The postpaid checkout determination unit 105 of Modification 4 determines whether to allow postpaid checkout based on the score when a postpaid checkout request for using postpaid checkout is received from the food delivery service. The postpaid checkout request in Modification 4 is received from the system of the takeout service. The format of the postpaid checkout request can be the same as the implementation, assuming it is the same format as the credit card checkout request. Although the subject sending the postpaid settlement request is different from the embodiment, the determination method itself of the postpaid settlement determination unit 105 is the same as that described in the embodiment.

The postpaid settlement execution unit 109 of Modification 4 executes postpaid settlement regarding the takeout service when it is determined that the postpaid settlement is permitted by the postpaid settlement determination unit 105 . Although there is a difference in that the postpaid checkout is executed in response to the postpaid checkout request received from the delivery service system, the method of executing the postpaid checkout by the postpaid checkout execution unit 109 In itself, it is as explained in the embodiment. In addition, external services are not limited to takeaway services. For example, the external service may be a travel reservation service, an electronic book service, or an online flea market service provided by an external business operator.

The checkout system 1 of Modification 4 determines whether to allow postpaid checkout based on the score when accepting a request for postpaid checkout from a delivery service provided by a business operator different from the issuer of the postpaid number. . The checkout system 1 executes postpaid checkout regarding the takeout service when it is determined that postpaid checkout is permitted. This makes it possible to increase the number of services that can utilize postpaid settlement, thereby improving user convenience.

[5-5. Modification 5] For example, as explained in Modification 3, the number checkout system can also be a bank automatic deduction checkout or a crypto asset checkout. Modification 3 illustrates the case where the payment can be made using these two numbers. However, in the payment system 1, only one of the automatic bank deduction payment or the encrypted asset payment can be used.

For example, if the number settlement is a bank automatic debit settlement, a relationship is established between the settlement number and the information related to the bank account in the first user database DB1. Automatic bank deduction and settlement are executed based on the information related to the bank account of the user who selected the number for settlement. The automatic bank deduction itself can be performed by known processes. For example, if the number settlement is a crypto-asset settlement, a relationship is established between the settlement number and the information on the crypto-assets in the first user database DB1. Crypto checkout is performed based on information related to the cryptographic assets of the user who selected the number for checkout. Cryptoasset settlement itself can be performed by well-known processes.

In the checkout system 1 of Modification 5, the number checkout is automatic bank deduction checkout or encrypted asset checkout. This makes it possible to reduce the cost required to introduce automatic bank debit settlement or crypto-asset settlement for the same reason as in the implementation form.

[5-6. Modification 6] For example, the overall configuration of the checkout system 1 is not limited to the example described in the embodiment. For example, the checkout system 1 can be used in each of a plurality of second services and external services. Modification 6 illustrates a case where the checkout service is linked to six services: a travel reservation service, an electronic book service, an online flea market service, a smartphone checkout service, and a takeout service.

FIG. 10 is a diagram illustrating an example of the overall configuration of the checkout system 1 according to Modification 6. In Modification 6, the checkout system 1 includes a GW server 10A, another checkout server 10B, and a postpaid checkout server 10C. Outside the checkout system 1, there are: EC server 20A, travel reservation server 20B, e-book server 20C, online flea market server 20D, smartphone checkout server 20E, takeout server 20F, and User terminal 30.

GW server 10A, other checkout server 10B, postpaid checkout server 10C, EC server 20A, travel reservation server 20B, e-book server 20C, online flea market server 20D, smartphone checkout server The physical configuration of each of the server 20E and the takeout server 20F can be the same as the checkout server 10 or the EC server 20 described in the embodiment.

The GW server 10A receives data from the EC server 20A, the travel reservation server 20B, the e-book server 20C, the online flea market server 20D, the smartphone checkout server 20E, and the takeout server 20F. Checkout requirements. Modification 6 explains the case where postpaid settlement is available for three of the EC service, online flea market service, and takeout service. However, it is also possible for postpaid settlement to be available for all six services. account.

Postpaid billing requests from EC services are as described in the implementation form. Postpaid checkout requests from the Online Flea Market Service are processed in the same form and process as the EC Service. Postpaid checkout requests from takeout services are as explained in Variation 4. Once the GW server 10A receives a settlement request from each service such as the EC service, it specifies the type of the settlement request. The method of specifying the type of checkout request is as explained in the implementation form.

When the postpaid settlement request has been accepted, the GW server 10A sends the postpaid settlement request to the postpaid settlement server 10C. The postpaid checkout server 10C has the functions of the checkout server 10 described in the embodiments and modifications 1 to 5. The processing of the postpaid checkout server 10C is the same as the process executed after the checkout server 10 described in the embodiment and modifications 1 to 5 accepts the postpaid checkout request. The postpaid settlement server 10C also performs processing of assigning a postpaid number, etc.

If the GW server 10A is a credit card payment request or other payment request, it sends the payment request to the other payment server 10B. The other settlement server 10B performs other settlements such as credit card settlement based on the settlement request received from the GW server 10A.

The checkout system 1 of Modification 6 can support postpaid checkout in various services. For example, the GW server 10A can support various checkout methods by specifying the type of checkout and assigning a subject to perform subsequent processing.

[5-7. Modification 7] For example, in the embodiment, the calculation unit 104 calculates the score, and the postpaid settlement determination unit 105 determines whether or not postpaid settlement is allowed. However, these processes Even if it is not implemented, the problem of "reducing the cost required to introduce checkout services" of the present disclosure can still be solved. That is, as long as the postpaid number is in the same format as the credit card number, the credit card checkout mechanism can be used to implement postpaid checkout. Therefore, even a checkout system that does not include the calculation unit 104 and the postpaid checkout determination unit 105 1, are still included in the scope of this disclosure. The calculation unit 104 and the postpaid settlement determination unit 105 are not included, but the payment determination unit 101, the payment unit 102, the acquisition unit 103, the password authentication unit 106, the security code authentication unit 107, the message authentication unit 108, or the postpaid settlement are included. The checkout system 1 of the execution unit 109 is also still included in the scope of this disclosure.

For example, when the checkout system 1 does not include the calculation unit 104 and the postpaid checkout determination unit 105, the postpaid checkout execution unit 109, once accepting the postpaid checkout request, will not execute the postpaid checkout based on the instructions described in the embodiment. of points, i.e. perform postpaid checkout. In this case, postpaid settlement can be performed unconditionally without performing the review required for postpaid settlement. If the postpaid number has the same consumption limit as the physical credit card, it can also be performed to ensure that the consumption has not been exceeded. Determination of amount. It is also possible to perform improper detection caused by an improper detection algorithm other than the score described in the embodiment first, and then perform postpaid settlement.

For example, in the embodiment, the case where a postpaid number in the same format as a credit card number is assigned is explained. However, the postpaid number may be a number in the same format as other payment methods other than credit card payment. If the checkout system 1 already supports other checkout methods, the checkout mechanism using other checkout methods can be used to introduce postpaid checkout, thus solving the problem of "reducing the cost of introducing checkout services" of the present disclosure. "The cost of" this topic. Therefore, the checkout system 1 that assigns postpaid numbers in the same format as other checkout methods other than credit cards is still included in the scope of the present disclosure.

For example, an example of the settlement system 1 that assigns a postpaid number in the same format as a settlement method other than a credit card is to assign a postpaid number in the same format as a bank account. In the checkout system 1, if the automatic deduction and settlement mechanism of the bank account has been introduced, a postpaid number in the same format as the bank account number can also be assigned. A bank account is identified by a financial institution code, branch number, and account number. Therefore, as a postpaid number, a financial institution code, a branch number, and an account number that are not used by any financial institution can also be assigned.

In addition, other settlement methods are not limited to bank account settlement, as long as it can be specified by a certain number. For example, it may be a crypto-asset account, a securities account, or an account of electronic currency. Checkout system 1 uses the automatic deduction and checkout mechanism of the imported bank account to introduce postpaid checkout, thus reducing the cost during introduction. Checkout system 1 can also assign postpaid numbers in the same format as other checkout methods other than credit card checkout and bank account.

[5-8. Other modifications] For example, two or more of modifications 1 to 7 described above may be combined.

For example, in the embodiment, the EC service and the checkout service are linked to each other, but the checkout service may not be linked to other services. In this case, you can also use the credit card checkout mechanism in the checkout service to introduce postpaid checkout.

For example, the function described as being implemented in the checkout server 10 may also be implemented in the EC server 20 or other server computers. The functions described as being implemented in the EC server 20 may also be implemented in the checkout server 10 or other server computers. For example, the functions described as being implemented in the checkout server 10 or the EC server 20 may be shared among a plurality of computers. Each function only needs to be implemented in at least one computer.

[6. Note] For example, the checkout system described in this disclosure can also be composed as follows. (1) A checkout system, which includes: an assigning unit, which assigns a checkout number in the same format as a credit card number to a user; and a calculating unit, which calculates based on past transaction information about the user's transactions. The score regarding the trustworthiness of the user mentioned above; and the number checkout determination unit determines whether to approve the number related to the checkout number mentioned above based on the score mentioned above when the checkout request for the checkout number mentioned above has been accepted. Checkout; and The number checkout execution unit executes the previous number checkout when it is determined that the previous number checkout is permitted by the previous number checkout determination unit. (2) The checkout system as described in (1), wherein the checkout system mentioned above also includes: a judgment unit that makes a determination based on the information about the user mentioned above and other information different from the transaction information mentioned above Whether or not the assignment of the aforementioned settlement number to the aforementioned user is permitted; The aforementioned settlement unit assigns the aforementioned settlement number to the aforementioned user if it is determined by the aforementioned grant determination unit that the assignment of the aforementioned settlement number is permitted. number. (3) The checkout system as described in (1) or (2), in which the front-end credit assignment part is accomplished by combining: user identification information that can identify the front-end user, and the front-end settlement that is not associated with a physical credit card. Account number, establish a relationship to assign the previous checkout number to the previous user. (4) The checkout system as described in any one of (1) to (3), in which the abovementioned payment department is responsible for transferring the foregoing settlement to the user of the foregoing without notifying at least part of the foregoing settlement number. The account number is assigned; the checkout system also includes: a display control unit, which notifies the user of at least a part of the checkout number in the above checkout, and causes the checkout screen required to perform the checkout request in the above checkout is displayed; The checkout determination unit with the aforementioned number determines whether or not the checkout with the aforementioned number is allowed when the aforementioned checkout request has been accepted due to the operation of the aforementioned checkout screen by the aforementioned user. (5) The checkout system as described in any one of (1) to (4), wherein the previous transaction information is information about the previous number checkout that has been executed in the past. (6) The checkout system as described in any one of (1) to (5), in which the abovementioned user is assigned the unit by combining: user identification information that can identify the user mentioned above, and the abovementioned checkout number, Establish a relationship to assign the aforementioned checkout number to the aforementioned user; The aforementioned checkout system also includes: an acquisition unit that obtains a second service that is different from the first service related to the aforementioned number checkout based on the aforementioned user identification information. Obtain the previous transaction information in the service; The previous calculation unit calculates the previous score based on the previous transaction information in the second service. (7) The checkout system as described in (6), wherein the aforementioned acquisition unit obtains the aforementioned transaction information in each of the plurality of the aforementioned second services; and the aforementioned calculation unit is based on the plurality of the aforementioned second services. 2. The previous transaction information in each service provider is used to calculate the previous score. (8) The checkout system as described in any one of (1) to (7), wherein the checkout system mentioned above also includes: a password authentication department, which is the first checkout requirement regarding the checkout with the number mentioned above. If the request is accepted, password authentication is omitted; if the second settlement request for credit card settlement is accepted, the password authentication mentioned above is performed. (9) The checkout system as described in any one of (1) to (8), wherein the checkout system mentioned above also includes: a security code authentication department, which is the first checkout requirement regarding the checkout with the number mentioned above. If the request has been accepted, the security code authentication will be omitted; if the second checkout request for credit card payment has been accepted, the security code authentication mentioned above will be performed. (10) The checkout system as described in any one of (1) to (9), in which the abovementioned assignment part is for the user of the foregoing, who has been assigned by the user of the foregoing from among the plural types of checkout methods. Select the previous checkout number with the number corresponding to the previous checkout type and assign it; The previous checkout system also includes: a processing execution unit, which executes the predetermined checkout based on the corresponding previous checkout type with the previous checkout number. processing. (11) The checkout system as described in (10), wherein the abovementioned processing execution unit instructs the checkout screen required to perform the abovementioned checkout request and displays the abovementioned number band corresponding to the abovementioned checkout number. Type image of the previous type; The previous number checkout determination unit determines whether to allow the previous number checkout when the previous checkout request has been accepted due to the previous user's operation on the previous checkout screen. (12) The checkout system as described in any one of (1) to (11), wherein the previous checkout system also includes: a display control unit, which is used to accept the user's previous checkout number, The checkout screen required for the selection among the other checkout methods is distinguished between the number checkout mentioned above and the other checkout method mentioned above. The checkout screen determined by the number mentioned above is linked to the checkout screen mentioned above. If the checkout with the previous number is selected and the request for checkout with the previous number has been accepted, it is determined whether to allow the checkout with the previous number. (13) The checkout system as described in any one of (1) to (12), wherein the foregoing checkout system also includes: a message authentication department, which, when the foregoing checkout request has been accepted, and Message authentication is performed between the user's user terminals; The above-mentioned number checkout execution unit executes the above-mentioned number checkout determination unit when it is determined that the above-mentioned number checkout is permitted and the above-mentioned message authentication is successful. Note the number before checkout. (14) The checkout system as described in any one of (1) to (13), in which the checkout number mentioned above can be used in an external service provided by a business entity different from the issuer of the checkout number mentioned above. Make use; The previous number checkout determination unit determines whether to allow the previous number checkout based on the previous score when the previous checkout request for using the previous number external service has been accepted; The aforementioned number settlement execution unit executes the preceding number settlement regarding the aforementioned external service when it is determined that the preceding number settlement is permitted by the aforementioned number settlement determination unit. (15) The checkout system as described in any one of (1) to (14), in which the checkout with the number mentioned above is the automatic bank deduction checkout or encrypted asset checkout.

1: Checkout system N: Network 10: Checkout server 10A: GW server 10B: Other checkout servers 10C: Postpaid checkout server 11, 21, 31: Control unit 12, 22, 32: Memory Part 13, 23, 33: Communication part 20: EC server 30: User terminal 34: Operation part 35: Display part 20A: EC server 20B: Travel reservation server 20C: Electronic book server 20D: Online flea market server Server 20E: Smartphone checkout server 20F: Takeout server 100: Data storage unit 101: Payment determination unit 102: Payment unit 103: Acquisition unit 104: Calculation unit 105: Postpaid settlement determination unit 106: Password authentication unit 107: Security code authentication unit 108: Message authentication unit 109: Postpaid settlement execution unit 200: Data storage unit 201: Service provision unit 202: Display control unit 203: Process execution unit 300: Data storage unit 301: Display control unit 302 : Operation reception department B12, B31, B32, B33, B42, B50: Button F10, F40: Input form I30, I34: Small icon SC1: Login screen SC2: Top screen SC3: Order confirmation screen SC4: Member login screen SC5: Login completion screen SC6: SMS screen SC7: Order completion screen DB1: First user database DB2: Second user database

[Fig. 1] An illustration of an example of the overall configuration of the checkout system. [Figure 2] An illustration of an example of the process for users to purchase goods in the EC service. [Figure 3] An illustration of an example of the process for users to purchase goods in the EC service. [Figure 4] An illustration of an example of functions implemented in the checkout system. [Figure 5] An illustration of an example of the first user database. [Figure 6] An illustration of an example of the second user database. [Figure 7] An illustration of an example of processing performed in the checkout system. [Figure 8] An illustration of an example of the functional block in Modification 3. [Figure 9] An illustration of an example of the order confirmation screen in Modification 3. [Fig. 10] An illustration of an example of the overall configuration of the checkout system according to Modification 6.

10: Checkout server

20:EC server

30:User terminal

100:Data Memory Department

101: Assigned to the judgment department

102: Endowment Department

103: Acquisition Department

104:Computing Department

105: Postpaid settlement judgment department

106: Password Authentication Department

107: Security Code Certification Department

108:Message Authentication Department

109: Postpaid Billing Execution Department

200:Data Memory Department

201:Service Provision Department

202:Display control department

300:Data Memory Department

301: Display control department

302: Operation acceptance department

DB1: 1st user database

DB2: 2nd user database

Claims (17)

A checkout system includes: an assigning part, which assigns a checkout number in the same format as a credit card number to a user; and a calculation part, which calculates the use of the foregoing user based on past transaction information about the user's transactions and The number checkout determination unit determines whether to allow the number checkout for the aforementioned checkout number based on the previous score when the checkout request for the aforementioned checkout number has been accepted; The number settlement execution unit executes the settlement of the preceding number when it is determined that settlement of the preceding number is permitted by the settlement determination unit of the preceding number. The checkout system as described in claim 1, wherein the checkout system further includes: a decision-making unit that determines whether to allow the transaction based on the information about the user of the foregoing and other information different from the transaction information in the foregoing. The above-mentioned settlement number is assigned to the above-mentioned user; The above-mentioned settlement number is assigned to the above-mentioned user by the above-mentioned settlement number when the above-mentioned settlement number is determined to be permitted by the above-mentioned grant determination section. The checkout system as described in claim 1 or 2, wherein the prefix assigning unit establishes a relationship by associating user identification information that can identify the user of the prefix with a predescript checkout number that is not associated with a physical credit card. , to assign the user of the previous account a checkout number. For example, the checkout system described in claim 1 or 2, wherein the above-mentioned checkout department assigns the above-mentioned checkout number to the user of the above-mentioned checkout without notifying at least part of the above-mentioned checkout number; The above-mentioned checkout system The system further includes: a display control unit that causes the checkout screen required to perform the above mentioned checkout request to be displayed without notifying the user of the above mentioned checkout number at least part of the above mentioned checkout number; and the above mentioned number checkout determination unit , in the case where the aforementioned checkout request has been accepted due to the aforementioned user's operation on the aforementioned checkout screen, it is determined whether to allow the aforementioned number to be settled. Such as the checkout system recorded in request item 1 or 2, wherein the "preceding transaction information" is information about the prefixed number checkout that has been executed in the past. For example, the checkout system described in claim 1 or 2, wherein the "forementioned user" is configured to associate the user identification information that can identify the aforementioned user with the aforementioned checkout number, so as to establish a relationship with the aforementioned user. The foregoing checkout number is assigned; the foregoing checkout system further includes an acquisition unit that acquires the foregoing transaction information in the second service that is different from the first service for the foregoing number checkout based on the foregoing user identification information. ; The front-end calculation department calculates the front-end score based on the front-end transaction information in the second service. A checkout system as described in claim 6, wherein the acquisition unit as mentioned above acquires the transaction information as mentioned above in each of the plurality of second services mentioned above; and the calculation unit as mentioned above is based on the plurality of second services mentioned above. The previous transaction information in each is used to calculate the previous score. The checkout system described in request item 1 or 2, wherein the checkout system mentioned above further includes a password authentication unit that omits password authentication when the first checkout request for checkout with the number mentioned above has been accepted. ; When the second payment request for credit card payment has been accepted, perform the password authentication mentioned above. The checkout system described in request item 1 or 2, wherein the checkout system mentioned above further includes: a security code authentication unit, which omits the security code when the first checkout request for checkout with the number mentioned above has been accepted. Code authentication: When the second checkout request for credit card payment has been accepted, the security code authentication mentioned above is performed. A checkout system as described in claim 1 or 2, wherein the "preamble assigning part" is a number corresponding to the type of the preamble that has been selected by the user of the preamble from a plurality of types of checkout methods. The prefixed checkout number is assigned; the prefixed checkout system also includes: a processing execution unit, which executes the prescribed processing based on the corresponding prefixed type of the prefixed checkout number. A checkout system as described in claim 10, wherein the preamble processing execution unit instructs a checkout screen required to perform a preamble checkout request, and displays a preamble type corresponding to the preamble number band of the preamble checkout number. The type of image; The checkout determination unit with the aforementioned number determines whether or not the checkout with the aforementioned number is allowed when the aforementioned checkout request has been accepted due to the operation of the aforementioned checkout screen by the aforementioned user. The checkout system described in claim 1 or 2, wherein the checkout system further includes: a display control unit, which is used to accept the user's checkout with the previous number and other checkout methods. The checkout screen required for the selection is displayed by distinguishing the checkout with the number mentioned above and the other checkout method mentioned above; The checkout judgment section with the number mentioned above is caused by the checkout with the number mentioned above being selected on the checkout screen mentioned above. When the checkout request mentioned above has been accepted, it is determined whether to allow checkout with the number mentioned above. Such as the checkout system described in request item 1 or 2, wherein, the aforementioned checkout system further includes: a message authentication unit, which is executed between the user terminal and the user when the aforementioned checkout request has been accepted. Message authentication; The aforementioned number checkout execution unit executes the aforementioned number checkout when it is determined that the aforementioned number checkout is permitted by the aforementioned number checkout determination unit and the preceding message authentication is successful. The checkout system described in claim 1 or 2, wherein the checkout number mentioned above can be used for external services provided by a business entity different from the issuer of the checkout number mentioned above; The checkout determination unit for the number mentioned above , when the previous payment request required to use the previous number settlement in order to use the previous number external service has been accepted, based on the previous number score, it is determined whether to allow the previous number settlement; The previous number payment execution department is based on the previous number settlement When it is determined that payment with the preceding number is permitted by the preceding number settlement determination unit, settlement with the preceding number regarding the aforementioned external service is executed. For example, the checkout system described in request item 1 or 2, in which the checkout with the number mentioned above is the automatic bank deduction checkout or encrypted asset checkout. A checkout method includes: an assigning step, which assigns a checkout number in the same format as a credit card number to a user; and a calculating step, which calculates the use of the foregoing user based on past transaction information about the user's transactions The number checkout determination step is based on the score of the previous checkout number when the checkout request for the previously mentioned checkout number has been accepted. and The number settlement execution step is to execute the preceding number settlement when it is determined that the settlement of the preceding number is permitted by the preceding number settlement determination step. A program product that is used to make a computer function and become: The assignment part is to assign a checkout number in the same format as a credit card number to the user; The calculation part is based on past transaction information about the user's transactions mentioned above. To calculate the score regarding the trustworthiness of the user mentioned above; The number checkout determination unit determines whether to allow the checkout request related to the checkout number mentioned above based on the score mentioned above when the checkout request related to the checkout number mentioned above has been accepted. Number settlement; The number settlement execution unit executes the preceding number settlement when it is determined that the preceding number settlement is permitted by the preceding number settlement determination unit.

Images