Information processing device, information processing method, and program

Abstract

An information processing device, an information processing method, and a program capable of effectively preventing bad debts from occurring. [Solution] An information processing device that includes an authorization processing unit that performs authorization to confirm whether payment is possible when a user makes a payment using a credit card, and a judgment unit that, triggered by the execution of the authorization, determines whether or not to perform processing for ongoing credit for the user based on information regarding the authorization.

Description

[Technical field]

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

[0002] Conventionally, there are known techniques for improving the accuracy of credit screening for credit cards. For example, Patent Document 1 proposes an information processing device that generates a learning model based on the user's behavior history before credit is granted and the record of whether the user has defaulted on a debt after credit is granted, and outputs an index value regarding whether the user will default on a debt using the generated learning model. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 6679648 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the information processing device described in Patent Document 1 was unable to perform ongoing credit based on information regarding credit card payment authorization (hereinafter referred to as authorization), and therefore was sometimes unable to effectively prevent bad debts from occurring.

[0005] The present invention has been made in consideration of the above circumstances, and one of its objects is to provide an information processing device, an information processing method, and a program that can effectively prevent bad debts from occurring. [Means for solving the problem]

[0006] One aspect of the present invention is an information processing device that includes an authorization processing unit that performs authorization to confirm whether or not payment is possible when a user makes a payment using a credit card, and a judgment unit that, triggered by the execution of the authorization, determines whether or not to perform processing for ongoing credit for the user based on information regarding the authorization. Effect of the Invention

[0007] According to one aspect of the present invention, it is possible to provide an information processing device, an information processing method, and a program that can effectively prevent bad debts from occurring. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram showing an example of the configuration of an electronic payment system in which an electronic payment service is realized. [Diagram 2] This is a sequence diagram (part 1) illustrating the general flow of electronic payment. [Diagram 3] This is a sequence diagram (part 2) illustrating the general flow of electronic payment. [Figure 4] FIG. 2 is a configuration diagram of a payment server 100. [Diagram 5] FIG. 13 is a diagram showing an example of the contents of user information 172. [Figure 6] FIG. 13 is a diagram showing an example of the contents of affiliated store / store information 176. [Figure 7] FIG. 2 is a diagram showing the configuration of a card company server 200. [Figure 8] FIG. 13 is a diagram showing an example of the contents of user information 272. [Figure 9] FIG. 13 is a diagram showing an example of the contents of credit card information 274. [Figure 10] A figure showing an example of the contents of authorization history information 276. [Figure 11] FIG. 13 is a diagram showing an example of the contents of statistical information 278. [Figure 12] FIG. 2 is a diagram showing an example of the content of a rule R. [Figure 13]FIG. 11 is a sequence diagram showing an example of a process related to credit card payment. [Figure 14] 13 is a flowchart showing an example of a process executed by the card company server 200. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, with reference to the drawings, an embodiment of an information processing device, an information processing method, and a program of the present invention will be described. Various devices, such as various devices and servers that appear below for providing services to users and performing internal analysis, may be realized by a distributed device group, and each device may be operated by a different business operator. Furthermore, the owner of the hardware of the device (provider of the cloud server) and the business that actually operates the device may also be different. An application program and a payment server work together to provide an electronic payment service. In the following description, the application program is referred to as a payment application. An electronic payment service is a service that supports payments related to the purchase of goods and services at a store. A store is, for example, a physical store (real store) that exists in the real world, but may also include a virtual store for electronic commerce. A virtual store may include a store provided by an entity different from the operator of the electronic payment service. In that case, when making a payment for shopping at a virtual store, the screen is controlled to transition to an interface screen of the electronic payment service. In an electronic payment service, a store is treated as belonging to, for example, an affiliated store (brand), and processing such as payment when a purchase is made at a store is mainly performed between the user and the affiliated store. Alternatively, processing such as payment may be performed between the user and the store.

[0010] [Electronic payment service] FIG. 1 is a diagram showing an example of the configuration of an electronic payment system in which an electronic payment service is realized. The electronic payment service is realized mainly by a payment server 100. The electronic payment system which realizes the electronic payment service includes, for example, one or more user terminal devices 10, one or more first store terminal devices 50, one or more second store terminal devices 70, a card store terminal device 80, the payment server 100, and a card company server 200. These devices communicate with each other, for example, via a network NW. The network NW includes, for example, the Internet, a LAN (Local Area Network), a wireless base station, a provider device, and the like.

[0011] A part or all of the functional configuration included in the electronic payment system may be distributed among multiple devices in any form, or may be integrated into any device. For example, a part or all of the functional configuration of the card company server 200 may be included in the configuration of the payment server 100, and a part or all of the functional configuration of the payment server 100 may be included in the functional configuration of the card company server 200.

[0012] The user terminal device 10 is, for example, a portable terminal device such as a smartphone or a tablet terminal. The user terminal device 10 is a computer device having at least an optical reading function, a communication function, a display function, an input reception function, and a program execution function. In the following description, components for realizing these functions are referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), etc. In the user terminal device 10, a processor such as a CPU executes a payment application 20, thereby operating to provide an electronic payment service to a user in cooperation with a payment server 100. The payment application 20 is installed in the user terminal device 10 from, for example, an application store, and controls the camera, communication device, touch panel, etc.

[0013] The first store terminal device 50 is installed, for example, in a store. The first store terminal device 50 is a computer device having at least a product price acquisition function, an optical reading function, a program execution function, and a communication function. The first store terminal device 50 includes a so-called POS (Point of Sale) device, and the product price acquisition function and the optical reading function may be realized by the POS device. The store code image 60 is placed in the store, and is a code image such as a QR code (registered trademark) printed on a paper or plastic medium. The store code image 60 may be displayed on a display placed in the store (which may be the display of a terminal device such as a smartphone).

[0014] The second store terminal device 70 is used by the operator of the affiliated store. The second store terminal device 70 is a smartphone, a tablet terminal, a personal computer, or the like. An interface 72 for affiliated stores runs on the second store terminal device 70. The interface 72 for affiliated stores may be an app for affiliated stores or a browser. The interface 72 for affiliated stores accepts coupon settings and the like made by the operator of the affiliated store and transmits them to the payment server 100. The second store terminal device 70, which is a smartphone, has the function of displaying a code image corresponding to a store code image and reading a code image displayed by the user terminal device 10 by executing the app for affiliated stores.

[0015] The payment server 100 realizes electronic payment based on payment information received from the user terminal device 10 or the first store terminal device 50. The first store terminal device 50 may include a POS device and an affiliated store server, in which case the payment information is sent from the POS device via the affiliated store server to the payment server 100. In the following explanation, no distinction is made between these two and it is assumed that the payment information is sent from the first store terminal device 50.

[0016] The store terminal 80 is a terminal used at credit card member stores. The store terminal 80 acquires information on the credit card presented by the user and transmits the acquired information to the card company server 200.

[0017] The card company server 200 is a server device of a credit card company that issues credit cards. The card company server 200 is operated by, for example, a group company of the settlement server 100.

[0018] 2 and 3 are sequence diagrams illustrating the general flow of electronic payment. There may be two patterns of electronic payment: pattern 1 and pattern 2.

[0019] In the case of pattern 1 (hereinafter referred to as user scan) shown in FIG. 2, the user terminal device 10 with the payment application 20 activated decodes the store code image 60 by the optical reading function (S1). The store code image 60 includes store URL (Uniform Resource Locator) information. This store URL is an electronic payment service domain to which store-identifying information is added, and is associated with an affiliated store ID, a store ID, etc. in the payment server 100 (described later). The payment application 20 transmits the first payment information including the store URL and the account ID to the payment server 100 (S2). The payment server 100 searches for store information (described later) from the affiliated store ID and the store ID corresponding to the store URL, acquires the affiliated store name and the store name information (S3), and transmits it to the payment application 20 (S4). The user inputs the payment amount into the user terminal device 10 on the screen on which the affiliated store name and the store name are displayed (S5). Then, the user terminal device 10 generates second payment information including at least the payment amount, and transmits it to the payment server 100 (S6). The payment server 100 performs electronic payment based on the received second payment information (S7). The payment server 100 then transmits a payment completion notice (information for displaying a payment completion screen) to the payment application 20 (S8), and the payment application 20 displays the payment completion screen (S9). Note that when the store code image 60 is displayed on a display installed in the store, the store code image 60 may include not only the store URL but also information on the payment amount. In this case, the step of the user inputting the payment amount is omitted, and the information on the payment amount is included in the first payment information and transmitted to the payment server 100. Information on the affiliated store name and the store name may be included in the payment completion screen and displayed.

[0020] In the case of pattern 2 (hereinafter referred to as store scan) shown in FIG. 3, when the payment application 20 is started, when a payment operation is performed in the payment application 20, when an automatic update timing (e.g., every minute) occurs, and at other timings, the payment application 20 transmits a request for issuing a one-time code to the payment server 100 (S11). The payment server 100 generates a one-time code (S12) and transmits it to the payment application 20 (S13). The payment application 20 displays a code image such as a QR code or a barcode generated based on the one-time code (S14). The user holds (presents) the display surface of the user terminal device 10 over the first store terminal device 50, and the first store terminal device 50 decodes the code image by an optical reading function and obtains the one-time code, etc. (S15). The first store terminal device 50 then generates payment information including the one-time code, payment amount, affiliated store ID, store ID, etc., and transmits it to the payment server 100 (S16). The payment amount information is acquired in advance by reading a barcode or manually entering it. The payment server 100 identifies the user corresponding to the one-time code based on the received information and performs electronic payment (S17). The payment server 100 then transmits a payment completion notice to the payment application 20 (S18), and the payment application 20 displays a payment completion screen (S19).

[0021] Note that electronic payment may be performed using only one of the above patterns. Furthermore, the "account ID" described in FIG. 2 may be other information (e.g., a phone number) that can be used as user identification information. Furthermore, issuance of a one-time code may be omitted in the store scan, and the payment application 20 may display a code image generated based on the user's account ID. In this case, the payment server 100 identifies the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[0022] [Payment server] 4 is a configuration diagram of the payment server 100. The payment server 100 includes, for example, a communication unit 110, a payment content providing unit 120, a payment processing unit 130, an information management unit 140, and a storage unit 170. The components other than the communication unit 110 and the storage unit 170 are realized by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuitry) such as an LSI (Large Scale Integration), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), a GPU (Graphics Processing Unit), or a SOC (System On Chip), or may be realized by cooperation between software and hardware. The program may be stored in advance in a storage device (a storage device with a non-transient storage medium) such as an HDD (Hard Disk Drive) or flash memory, or may be stored in a removable storage medium (non-transient storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device.

[0023] The storage unit 170 is a HDD, a flash memory, a RAM (Random Access Memory), etc. The storage unit 170 may be a NAS (Network Attached Storage) device that the payment server 100 can access via a network. The storage unit 170 stores information such as user information 172, payment content information 174, and affiliated store / shop information 176. Some of this information may be stored in the storage unit of the user terminal device 10.

[0024] The communication unit 110 is a communication interface for connecting to the network NW. The communication unit 110 is, for example, a network interface card.

[0025] The payment content providing unit 120 has, for example, a function of a Web server, and provides information (content) for displaying various screens of the electronic payment service to the user terminal device 10. The payment content providing unit 120 appropriately reads necessary content from the payment content information 174 and provides it to the user terminal device 10. The user terminal device 10 accepts various inputs by the user while the content is being played by the payment application 20, and transmits the above-mentioned payment information and the like to the payment server 100. The above content may be generated by the payment application 20. In this case, the payment content providing unit 120 provides information required for generating the content to the payment application 20.

[0026] The payment processing unit 130 performs payment processing based on the payment information transmitted by the user terminal device 10 or the first store terminal device 50. The payment processing unit 130 performs payment processing while referring to the user information 172.

[0027] FIG. 5 is a diagram showing an example of the contents of the user information 172. The user information 172 is an example of the registration information of a user. The user information 172 is information associated with, for example, a user URL, an account ID, a telephone number, a password, an email address, a user ID, a name, an address, a date of birth, a registration date, a charge balance, a credit payment setting, a credit payment limit, a credit payment amount used, a credit payment available amount, a payment method setting, a bank account, a credit card number, charge history information, and a payment history information. The user URL is used for a remittance process between users. When registering for the electronic payment service, it is necessary to register a telephone number and a password. The account ID is issued to the user by the payment server 100, and the user ID is an ID that can be set by the user at will (does not have to be set). Similarly, the email address, and the name, address, and date of birth are information that can be set by the user at will (does not have to be set). The registration date is the date on which the user registered for the electronic payment service (the date on which the account was created). Hereinafter, the user's instance (electronic payment account) to which this information is associated will be referred to as an account.

[0028] The charge balance is information indicating the balance of electronic money that is set by a user by transferring money to an account in advance. The means of transfer include transfer from an ATM (Automatic Teller Machine) of a designated company (bank) and transfer from a registered bank account. The credit payment setting is information indicating whether or not the setting for enabling electronic payment by credit payment has been completed, and is set to either "completed" or "not completed." The credit payment limit is the credit payment limit that can be used each month, the credit payment usage amount is the amount of credit payment that has already been used in the current month, and the credit payment available amount is the amount of credit payment that can be used in the current month, which is calculated by subtracting the credit payment usage amount from the credit payment limit. Although only one credit payment limit is shown in the figure, in reality, there is also a daily upper limit, and the lower of these may be set as the credit payment limit. Further details of credit payment will be described later. The payment method setting is setting information indicating whether the user will perform electronic payment using the charge balance or payment by credit payment at that time. The bank account and credit card number are information on a bank account or credit card number (account number, card number) that can be used to deposit funds into an electronic payment service. Charge history information is a history of the user's previous transfers to the electronic payment service to increase the charge balance. Payment history information is information that indicates the details of payments made by the user for each payment (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.).

[0029] FIG. 6 is a diagram showing an example of the contents of the affiliated store / store information 176. The affiliated store / store information 176 includes, for example, a first table 176A in which an affiliated store ID and a store ID are associated with a store URL, a second table 176B in which an affiliated store name and sales amount (described above) are associated with an affiliated store ID, and a third table 176C in which a store name is associated with a store ID. In addition to these pieces of information, the affiliated store / store information 176 may include information such as an affiliated store or store category, a store location, and a payment pattern. The above-mentioned affiliated store name may be, for example, information registered by the affiliated store or information registered by an administrator of the electronic payment service. The above-mentioned affiliated store name and store name may be managed in an integrated manner. The above-mentioned affiliated store name may be, for example, a combination of the affiliated store name and the store name. It is preferable that the above-mentioned affiliated store name is an official name or a detailed name. In the affiliated store / store information 176, an icon of an affiliated store or other detailed information of an affiliated store may be associated with an affiliated store ID or a store ID.

[0030] The information management unit 140 acquires information provided by other server devices and terminal devices. The information management unit 140 manages user information 172 and affiliated store / store information 176 based on information acquired from the user terminal device 10 and the second store terminal device 70. The information management unit 140 adds new records to, edits, and deletes the user information 172 and affiliated store / store information 176.

[0031] [Electronic payment] When payment information is acquired from the user terminal device 10 or the first store terminal device 50, the payment processing unit 130 refers to the user information 172 to acquire the "payment method setting" of the user. For a user whose "payment method setting" is set to "charge balance", the payment processing unit 130 performs electronic payment as follows. For example, the payment processing unit 130 performs electronic payment by decreasing the charge balance managed in association with the user ID and increasing the item value of the affiliated store's sales. The item value of the affiliated store's sales is not used as electronic money itself, for example, and an amount corresponding to the item value of the sales is transferred to a bank account in a cycle according to an agreement between the affiliated store and the electronic payment service.

[0032] The payment processing unit 130 performs electronic payment for users whose "setting information" is set to "credit card payment" as follows. Credit card payment is a payment method in cooperation with a credit card company, which is a separate entity from the operator of the electronic payment service, and the operator of the electronic payment service acts as a creditor and allows electronic payment that is not dependent on the charge balance within the credit card payment limit. In order to receive the credit card payment service, a credit card provided by the operator of the electronic payment service may be required. The amount used in the credit card payment is settled on the payment date of the following month, for example, by debiting from a bank account, for one month. In this case, the payment processing unit 130 performs provisional payment by adding the payment amount to the credit card payment amount and subtracting the same amount from the available credit card payment amount, and when the closing date comes, it performs processing to debit the payment for the current month on the payment date of the following month as described above, or requests the operator of the credit card company to perform the processing. In addition, if the payment amount exceeds the available credit card payment amount at the time of provisional payment, an error notification is returned to the payment application 20.

[0033] [Card company server] 7 is a configuration diagram of the card company server 200. The card company server 200 includes, for example, a communication unit 210, an authorization processing unit 215, a card payment processing unit 220, a determination unit 225, an authorization attribute information acquisition unit 230, a user attribute information acquisition unit 235, a credit information acquisition unit 240, a score calculation unit 245, an execution unit 250, a payment history information acquisition unit 255, a rule generation unit 260, and a storage unit 270. The components other than the communication unit 210 and the storage unit 270 are realized by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including a circuit unit) such as an LSI, an ASIC, an FPGA, or a GPU, or may be realized by cooperation between software and hardware. The program may be stored in advance in a storage device such as a HDD or flash memory (a storage device with a non-transient storage medium), or may be stored in a removable storage medium (non-transient storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device.

[0034] The communication unit 210 is a communication interface for connecting to the network NW. The communication unit 210 is, for example, a network interface card.

[0035] The storage unit 270 is a HDD, a flash memory, a RAM, etc. The storage unit 270 may be a NAS (Network Attached Storage) device that the card company server 200 can access via a network. The storage unit 270 stores information such as user information 272, credit card information 274, authorization history information 276, statistical information 278, and rule R.

[0036] 8 is a diagram showing an example of the contents of user information 272. User information 272 is information about a user who owns a credit card. Each item of user information 272 is input by the user when requesting issuance of a credit card.

[0037] The user information 272 includes, for example, a user ID, age, gender, name, address, and date of birth. The user ID is identification information for identifying the credit card user. The age is the age of the credit card user. The gender is the gender of the credit card user. The name, address, and date of birth are the name, address, and date of birth of the credit card user. Note that the user information 272 may include information other than the above. For example, the user information 272 may include information such as the occupation, annual income, or loan amount of the credit card user.

[0038] 9 is a diagram showing an example of the contents of credit card information 274. Credit card information 274 is information related to a credit card owned by a user. When a credit card is issued, a record related to the issued credit card is added to credit card information 274. Furthermore, when a credit card payment is made, the contents of credit card information 274 are updated based on the payment information.

[0039] The credit card information 274 includes, for example, a credit card number, a user ID, a name, an expiration date, a security code, a credit limit, a usage amount, and a card usage history. The credit card number is a number for identifying a credit card. The user ID is identification information for identifying a credit card user, and is the same information as the user ID shown in FIG. 8. The name is an alphabetical notation of the name of the credit card holder. The expiration date is information about the expiration date of the credit card. The security code is a number written on the back of the credit card, which is used to prevent fraudulent use of the credit card. The available limit is the upper limit amount that can be used with the credit card. The available limit may be set individually for each shopping limit and cash advance limit. The usage amount is the total amount of payments made using the credit card. The card usage history is a credit card usage history, and may include the name of the affiliated store where the payment was made, the category of the affiliated store, the date and time of the payment, the payment amount, and the like. The credit card information 274 may include information other than these. For example, the credit card information 274 may include information such as the type of credit card (general, gold, platinum, black).

[0040] FIG. 10 is a diagram showing an example of the contents of the authorization history information 276. The authorization history information 276 is information related to authorization in credit card payment (hereinafter referred to as authorization). Authorization is a process in credit card payment that checks the validity and available credit limit of a credit card and determines whether payment is possible. Authorization is performed by the authorization processing unit 215.

[0041] The authorization history information 276 includes, for example, a transaction ID, a credit card number, a user ID, a terminal identification number, an affiliated store ID, a payment amount, a date and time, and the presence or absence of a bad debt. The transaction ID is identification information for identifying a transaction related to the authorization. The credit card number is a number for identifying a credit card, and is the same information as the credit card number shown in FIG. 9. The user ID is identification information for identifying a credit card user, and is the same information as the user ID shown in FIG. 8 and FIG. 9. The terminal identification number is an identification number of the card store terminal device 80 that reads the credit card information at the time of credit card payment. The affiliated store ID is identification information for identifying the affiliated store. The payment amount is the payment amount of the credit card payment. The date and time is information indicating the date and time when the authorization process was performed. The presence or absence of a bad debt is information indicating whether or not a bad debt actually occurred after the authorization process was performed. If a bad debt occurred, the presence or absence of a bad debt is "Yes". On the other hand, if a bad debt did not occur, the presence or absence of a bad debt is "No".

[0042] 11 is a diagram showing an example of the contents of the statistical information 278. The statistical information 278 is information related to authorization statistics. The statistical information 278 is information generated by the authorization processing unit 215. Specifically, the authorization processing unit 215 generates the statistical information 278 by performing statistical processing with reference to the user information 272 and the authorization history information 276. The statistical information 278 is an example of information related to authorization.

[0043] The statistical information 278 includes, for example, terminal identification information, amount range, time period, age, gender, user ID (normal), user ID (default), and default rate. The terminal identification number is the identification number of the card store terminal device 80 that reads the information of the credit card used in the credit card payment, and is the same information as the terminal identification number shown in FIG. 10. The amount range is information indicating the amount range of the payment amount of the credit card payment. The time period is information regarding the time period in which the authorization process was performed. The age is the age of the user who made the credit card payment. The gender is the gender of the user who made the credit card payment. The user ID (normal) is a list of user IDs of users who did not have defaults after the authorization process was performed. The user ID (default) is a list of user IDs of users who had defaults after the authorization process was performed. The default rate is information indicating the percentage of users who had defaults. The authorization processing unit 215 calculates the percentage of user IDs (default) to the total number of user IDs (normal) and user IDs (default) as the default rate.

[0044] In addition, in the statistical information 278 shown in Fig. 11, the terminal identification information, the amount range, and the time period are examples of authorization attribute information, which is information about the attributes of the authorization. In addition, the age and the gender are examples of user attribute information, which is information about the attributes of the user.

[0045] [Rule generation process] Next, the rule generation process executed by the rule generation unit 260 will be described. As described above, when a user makes a payment using a credit card, the authorization processing unit 215 executes authorization to confirm whether or not the payment is possible. The rule generation unit 260 generates a rule R used to determine whether or not to perform processing for ongoing credit for the user, based on information (statistical information 278) regarding authorization during a predetermined period. Ongoing credit is an examination performed on a user while the credit card is being used after credit is granted.

[0046] Specifically, the rule generation unit 260 refers to the statistical information 278 stored in the memory unit 270, and generates as rule R a combination of authorization attribute information (terminal identification number, amount range, time period) and user attribute information (age, gender) that results in a probability of the user incurring a default equal to or greater than a predetermined threshold.

[0047] For example, the rule generating unit 260 extracts combinations whose bad debt ratio is equal to or greater than a threshold value (e.g., 40%) from the statistical information 278 shown in Fig. 11. Specifically, the rule generating unit 260 extracts a combination whose bad debt ratio is 48% (T001, high amount, night, 20s, male), a combination whose bad debt ratio is 40% (T002, high amount, night, 20s, male), and a combination whose bad debt ratio is 50% (T003, high amount, night, 20s, male). The rule generating unit 260 generates these extracted combinations as rule R.

[0048] FIG. 12 is a diagram showing an example of the contents of rule R. Rule R includes, for example, a rule ID, authorization attribute information, and user attribute information. The rule ID is identification information for identifying the rule. The authorization attribute information is information about the attributes of the authorization, and includes a terminal identification number, a price range, and a time period. The terminal identification number is an identification number of the card store terminal device 80 that reads the information of the credit card used in the credit card payment, and is the same information as the terminal identification number shown in FIG. 10 and FIG. 11. The price range is information indicating the price range of the payment amount of the credit card payment, and is the same information as the price range shown in FIG. 11. The time period is information about the time period when the authorization process was performed, and is the same information as the time period shown in FIG. 11. The user attribute information is information about the attributes of the user, and includes age and gender. The age is the age of the user who made the credit card payment, and is the same information as the age shown in FIG. 11. The gender is the gender of the user who made the credit card payment, and is the same information as the gender shown in FIG. 11.

[0049] Although the authorization attribute information is described as being the terminal identification number, the amount range, and the time period, it is not limited to these pieces of information. For example, the authorization attribute information may include the category of the affiliated store to which the store where the payment was made belongs. Furthermore, although the user attribute information is described as being the age and gender of the user, it is not limited to these pieces of information. For example, the user attribute information may include the user's occupation, annual income, and loan amount.

[0050] [Sequence diagram] Fig. 13 is a sequence diagram showing an example of a process related to credit card payment. The process shown in the sequence diagram of Fig. 13 is executed when a user applies to purchase a product at a member store. Note that although an application to purchase a product is used here, an application to use a service may also be used.

[0051] First, the card store terminal device 80 acquires card information (such as credit card number and expiration date) of the user's credit card (S101). For example, the card store terminal device 80 may read the card information directly from the credit card presented by the user, or may have the user input the card information.

[0052] Next, the card store terminal device 80 transmits authorization information to the card company server 200 (S102). For example, the authorization information includes a transaction ID, a credit card number, a terminal identification number, an affiliated store ID, and a payment amount. The transaction ID is identification information for identifying the transaction. The credit card number is the number of the user's credit card included in the card information acquired in S101. The terminal identification number is identification information for identifying the card store terminal device 80. The affiliated store ID is identification information for identifying the affiliated store to which the store where the user is going to purchase an item belongs, and is the same information as the affiliated store ID shown in FIG. 6. The payment amount included in the authorization information is the payment amount at the time of authorization.

[0053] Next, the card company server 200 acquires the authorization information transmitted from the card store terminal device 80. The authorization processing unit 215 of the card company server 200 performs authorization processing based on the authorization information (S103). The authorization processing is processing for determining whether or not to approve a payment using a credit card based on the authorization information. Specifically, the authorization processing unit 215 acquires the available credit limit and usage amount of the user's credit card from the credit card information 274 in the authorization processing. Furthermore, if the total of the payment amount included in the authorization information and the usage amount of the user's credit card is equal to or less than the available credit limit, the authorization processing unit 215 determines that the payment using the credit card is approved, and adds the payment amount to the usage amount of the user's credit card. On the other hand, if the total of the payment amount included in the authorization information and the usage amount of the user's credit card is greater than the available credit limit, the authorization processing unit 215 determines that the payment using the credit card is not approved because the transaction exceeds the available credit limit.

[0054] The authorization processing unit 215 also updates the authorization history information 276 stored in the memory unit 270. Specifically, the authorization processing unit 215 links the transaction ID, credit card number, user ID, terminal identification number, affiliated store ID, payment amount, and date and time and adds them to the authorization history information 276. The transaction ID, credit card number, terminal identification number, affiliated store ID, and payment amount are information included in the authorization information received in S102. The user ID is information linked to the credit card number in the credit card information 274. At this point, it is unknown whether or not a bad debt will occur in the future, so the presence or absence of a bad debt in the authorization history information 276 is left blank.

[0055] Next, the communication unit 210 of the card company server 200 transmits the authorization result to the card store terminal device 80 (S104). The authorization result is information including the transaction ID and the judgment result (OK or NG). In this example, it is determined that the payment using the credit card is approved in the authorization process, and the authorization result (OK) is transmitted to the card store terminal device 80.

[0056] Next, card store terminal device 80 transmits payment information to card company server 200 (S105). The payment information is payment information at the time of sale at the affiliated store. For example, the payment information includes a transaction ID, a credit card number, a terminal identification number, an affiliated store ID, and a payment amount. The payment amount included in the payment information is the payment amount at the time of sale at the affiliated store.

[0057] Next, the card company server 200 acquires the payment information transmitted from the card store terminal device 80. The card payment processing unit 220 of the card company server 200 performs card payment processing based on the payment information (S106). When performing card payment processing, the payment amount at the time of authorization may differ from the payment amount at the time of sale at the affiliated store. For example, when a user makes a reservation for a lodging facility at a travel agency, authorization processing may be performed with the accommodation fee of the lodging facility as the payment amount at the time of authorization, and when sales are made at the affiliated store (lodging facility), the payment processing may be performed with the payment amount including the fee for the service (room service, etc.) actually used at the lodging facility added thereto. In this way, the payment amount at the time of authorization may differ from the payment amount at the time of sale at the affiliated store.

[0058] Based on this, the card payment processing unit 220 obtains the payment amount linked to the transaction ID included in the payment information from the authorization history information 276. Furthermore, if the payment amount included in the payment information matches the payment amount obtained from the authorization history information 276, the card payment processing unit 220 completes the payment process. On the other hand, if these payment amounts do not match, the card payment processing unit 220 calculates the additional amount to be collected by subtracting the payment amount obtained from the authorization history information 276 from the payment amount included in the payment information. Thereafter, the card payment processing unit 220 adds the additional amount to be collected to the amount of credit card usage of the user in the credit card information 274, and completes the payment process. This allows the payment process to be performed appropriately even if the payment amount at the time of sale at the affiliated store is higher than the payment amount at the time of authorization.

[0059] Next, the communication unit 210 of the card company server 200 transmits a payment completion notice to the card store terminal device 80 (S107). The payment completion notice includes the transaction ID and information indicating that the payment has been completed. The card store terminal device 80 may display that the credit card payment has been completed based on the payment completion notice received from the card company server 200. This allows the user to know that the payment process has been completed.

[0060] After the credit card payment process is completed, a bad debt may occur on the payment date of the following month due to insufficient funds in the user's bank account. If a bad debt occurs, "Yes" is recorded in the "Whether or Not a Bad Debt" field in the authorization history information 276. On the other hand, if a bad debt does not occur, "No" is recorded in the "Whether or Not a Bad Debt" field in the authorization history information 276.

[0061] [flowchart] Fig. 14 is a flowchart showing an example of a process executed by the card company server 200. The process shown in Fig. 14 is executed when an authorization process is executed as a trigger. The card company server 200 may execute the process shown in Fig. 14 immediately after executing the authorization process, or may execute the process at a predetermined timing (for example, 10:00 a.m. on the day after the authorization process is executed).

[0062] First, the authorization attribute information acquisition unit 230 acquires authorization attribute information, which is information related to the attributes of authorization (S201). The authorization attribute information includes, for example, a terminal identification number, a price range, and a time period. Specifically, the authorization attribute information acquisition unit 230 acquires the terminal identification number and the price range based on the authorization information (terminal identification number, payment amount, etc.) received in S102 of FIG. 13. In addition, the authorization attribute information acquisition unit 230 acquires the time period based on the time when the authorization information is received.

[0063] Next, the user attribute information acquisition unit 235 acquires user attribute information, which is information related to the attributes of the user (S202). The user attribute information includes, for example, age and gender. Specifically, the user attribute information acquisition unit 235 acquires a user ID linked to the credit card information included in the authorization information received in S102 of FIG. 13 from the credit card information 274, and acquires the age and gender of the user linked to the acquired user ID from the user information 272.

[0064] Next, the determination unit 225 determines whether to perform processing for ongoing credit based on the authorization attribute information acquired by the authorization attribute information acquisition unit 230 and the user attribute information acquired by the user attribute information acquisition unit 235 (S203). Ongoing credit is an examination performed on a user while using a credit card after credit is granted to the credit card. Specifically, the determination unit 225 determines whether a combination of the authorization attribute information acquired in S201 and the user attribute information acquired in S202 corresponds to the rule R stored in the storage unit 270. If the combination of these pieces of information does not correspond to the rule R, the bad debt rate is less than a threshold value (for example, 40%), so the determination unit 225 determines not to perform processing for ongoing credit and ends the processing according to this flowchart.

[0065] On the other hand, if the combination of these pieces of information corresponds to rule R, the default rate is equal to or greater than a threshold value (e.g., 40%), and the judgment unit 225 judges that processing for ongoing credit should be performed. If it is judged that processing for ongoing credit should be performed, the credit information acquisition unit 240 acquires the user's credit information from an external server (S204). The external server may be, for example, a server of a credit information agency such as CIC (Credit Information Center). The credit information includes, for example, information such as the usage history of the user's credit card (including those issued by other credit card companies), the repayment status of the loan, and the amount borrowed.

[0066] Next, the score calculation unit 245 calculates a score indicating the likelihood of the user having a default based on the credit information acquired by the credit information acquisition unit 240 (S205). The score calculation unit 245 calculates a higher score as the likelihood of a default increases. For example, the score calculation unit 245 calculates a higher score when the user uses a large amount of credit card, is behind on loan repayments, or has a large borrowing amount.

[0067] Next, the execution unit 250 judges whether or not the score calculated by the score calculation unit 245 is higher than a predetermined threshold (S206). If the score is equal to or lower than the predetermined threshold, the execution unit 250 judges that the possibility of a bad debt occurring is low, and ends the process according to this flowchart.

[0068] On the other hand, if the score is greater than the predetermined threshold, the execution unit 250 reduces or suspends the credit card of the user (S207). Reducing the credit card limit is a process of reducing the available credit card limit of the user. Suspending the credit card is a process of making the user's credit card unavailable. For example, the execution unit 250 may suspend the user's credit card when the score calculated by the score calculation unit 245 is higher than a predetermined value. Also, the execution unit 250 may reduce the credit card limit of the user when the score calculated by the score calculation unit 245 is equal to or less than a predetermined value. Thereafter, the execution unit 250 ends the processing according to this flowchart.

[0069] In S203, the judgment unit 225 may determine whether to perform processing for ongoing credit by taking into account the payment history information of the user in the electronic payment service. Specifically, the payment history information acquisition unit 255 may acquire payment history information, which is a history of electronic payments made by the user, from the payment server 100 that performs electronic payments using electronic money. The payment history information is information included in the user information 172 shown in FIG. 5. The judgment unit 225 may also determine whether to perform processing for ongoing credit by taking into account the payment history information. For example, when the payment history information of the user includes a payment history at an affiliated store (gambling, etc.) included in a preset blacklist, the judgment unit 225 may determine that processing for ongoing credit is to be performed. This allows the card company server 200 to more effectively prevent bad debts from occurring.

[0070] [Variations of rule generation process] In the above description, the rule generating unit 260 generates a combination of the authorization attribute information and the user attribute information in which the bad debt ratio is equal to or greater than a predetermined threshold as the rule R, but this is not limited thereto. For example, the rule generating unit 260 may generate the rule R by performing machine learning based on the statistical information 278. Specifically, the rule generating unit 260 may generate a trained model to be used as the rule R by performing machine learning using the authorization attribute information and the user attribute information as explanatory variables and the bad debt ratio as an objective variable. This allows the card company server 200 to generate the rule R (trained model) for outputting a highly accurate bad debt ratio.

[0071] Furthermore, the statistical information 278 may include information on the brand of the credit card (Visa (registered trademark), Mastercard (registered trademark), etc.). Furthermore, the rule generating unit 260 may analyze the information (statistical information 278) on authorizations during a predetermined period to generate a rule R for a combination of the brand of the credit card and the terminal identification number whose default rate is equal to or exceeds a predetermined threshold value (e.g., 40%). This allows the card company server 200 to generate a rule R for outputting a highly accurate default rate, taking into account the brand of the credit card.

[0072] Furthermore, the rule generating unit 260 may analyze information (statistical information 278) related to authorizations for a predetermined period to generate a list of the names of affiliated stores to which the store where the payment was made using the credit card belongs, and which have a probability of the user having a default equal to or higher than a predetermined threshold, as rule R. This allows the card company server 200 to generate a list of the names of specific affiliated stores that are likely to have defaults as a blacklist rule.

[0073] According to the embodiment described above, the card company server (information processing device) 200 includes an authorization processing unit 215 and a determination unit 225. When a user makes a payment using a credit card, the authorization processing unit 215 executes authorization to confirm whether or not the payment is possible. The determination unit 225, triggered by the execution of authorization, determines whether or not to perform processing for ongoing credit for the user based on information related to the authorization (statistical information 278). This enables the card company server 200 to effectively prevent bad debts from occurring.

[0074] In the above description, the card company server 200 is described as an example of an information processing device, and the payment server 100 and the card company server 200 are separate servers, but this is not limited to the above. For example, if the electronic payment service provider and the card company are the same company or a group of companies, a single server that integrates the payment server 100 and the card company server 200 may be provided as an information processing device.

[0075] The above describes the form for carrying out the present invention using an embodiment, but the present invention is not limited to such an embodiment, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present invention. [Explanation of symbols]

[0076] 10 User terminal device 20. Payment App 50 First store terminal device 100 Payment Server 110 Communications Department 120 Payment Contents Provider 130 Payment processing unit 140 Information Management Department 170 Storage section 200 Card company server 210 Communication section 210 215 Authorization Processing Unit 220 Card payment processing unit 225 Judgment section 230 Authorization attribute information acquisition unit 235 User attribute information acquisition unit 240 Credit information acquisition department 245 Score Calculation Section 250 Executive Department 255 Payment History Information Acquisition Unit 260 Rule Generation Unit 270 Storage section

Claims

1. an authorization processing unit that performs authorization to confirm whether or not a payment can be made when a user makes a payment using a credit card; A rule generating unit that generates a rule from among combinations of authorization attribute information, which is information on the attributes of the authorization, and user attribute information, which is information on the attributes of the user, a combination in which a probability that the user has a bad debt is equal to or higher than a predetermined threshold value; A determination unit that determines whether or not a combination of the authorization attribute information and the user attribute information related to the executed authorization corresponds to the rule, when the authorization is executed as a trigger; a score calculation unit that calculates a score indicating a degree of bad debt for the user when it is determined that a combination of the authorization attribute information and the user attribute information related to the executed authorization corresponds to the rule; an execution unit that executes a reduction or suspension of the credit card of the user when the score is greater than a predetermined threshold; An information processing device comprising:

2. An authorization attribute information acquisition unit that acquires the authorization attribute information; A user attribute information acquisition unit that acquires the user attribute information.

2. The information processing device according to claim 1.

3. The authorization attribute information includes at least one of a terminal identification number for identifying a terminal of a store where the payment using the credit card was made, a category of an affiliated store to which the store belongs, a price range of a payment amount, and a time period during which the authorization is made.

3. The information processing device according to claim 2.

4. The user attribute information includes at least one of the user's age, sex, occupation, annual income, and loan amount.

3. The information processing device according to claim 2.

5. The method further includes a credit information acquisition unit that acquires credit information of the user from an external server when it is determined that a combination of the authorization attribute information and the user attribute information related to the executed authorization corresponds to the rule, The score calculation unit calculates a score indicating a degree of occurrence of a default of the user based on the credit information.

2. The information processing device according to claim 1.

6. The electronic payment system further includes a payment history information acquisition unit that acquires payment history information, which is a history of electronic payments made by the user, from a payment server that performs electronic payments using electronic money.

2. The information processing device according to claim 1.

7. The rule generation unit generates a trained model to be used as the rule by performing machine learning using the authorization attribute information and the user attribute information as explanatory variables and a bad debt rate, which is information indicating the probability that a bad debt has occurred to the user, as an objective variable.

2. The information processing device according to claim 1.

8. the rule generation unit analyzes information regarding the authorization for a predetermined period of time, and generates, as the rule, a combination of the brand of the credit card and a terminal identification number for identifying a terminal of a store where a settlement using the credit card is made, in which the probability that the user will have a default is equal to or higher than a predetermined threshold.

2. The information processing device according to claim 1.

9. The rule generation unit analyzes information regarding the authorization for a predetermined period of time to generate, as the rule, a list of names of affiliated stores to which a store where a settlement using the credit card belongs, the affiliated stores having a probability of the user having a bad debt equal to or greater than a predetermined threshold.

2. The information processing device according to claim 1.

10. An information processing device, When a user makes a payment using a credit card, authorization is performed to confirm whether the payment can be made, Generate, as a rule, a combination of authorization attribute information, which is information on the attributes of the authorization, and user attribute information, which is information on the attributes of the user, in which the probability of the user having a bad debt is equal to or greater than a predetermined threshold; Using the execution of the authorization as a trigger, it is determined whether or not a combination of the authorization attribute information and the user attribute information related to the executed authorization corresponds to the rule; If it is determined that a combination of the authorization attribute information and the user attribute information related to the executed authorization corresponds to the rule, a score indicating the degree to which the user is likely to have a bad debt is calculated; If the score is greater than a predetermined threshold, reducing or suspending the user's credit card. Information processing methods.

11. In the information processing device, When a user makes a payment using a credit card, authorization is performed to confirm whether the payment can be made, Generate, as a rule, a combination of authorization attribute information, which is information on the attributes of the authorization, and user attribute information, which is information on the attributes of the user, in which the probability of the user having a bad debt is equal to or higher than a predetermined threshold; Using the execution of the authorization as a trigger, it is determined whether or not a combination of the authorization attribute information and the user attribute information related to the executed authorization corresponds to the rule; When it is determined that a combination of the authorization attribute information and the user attribute information related to the executed authorization corresponds to the rule, a score indicating a degree of occurrence of a bad debt for the user is calculated; If the score is greater than a predetermined threshold, reducing or suspending the credit card of the user. program.

Images