JP2026064195A - Information processing device, information processing method, and program - Google Patents

Abstract

[Problem] To provide an information processing device, an information processing method, and a program that can effectively prevent the occurrence of bad debts.
[Solution] An information processing device comprising: an authorization processing unit that performs authorization to confirm whether payment is possible when a user makes a payment using a credit card; a rule generation unit that generates rules for combinations of authorization attribute information, which is information about the attributes of the authorization, and user attribute information, which is information about the attributes of the user, such that the probability of a default occurring for the user is above a predetermined threshold; and a determination unit that, triggered by the execution of the authorization, determines whether or not to perform ongoing credit assessment, which is a review conducted on the user while the credit card is being used after the credit card has been extended, based on the rule.
[Selection Diagram] Figure 7

Description

This invention relates to an information processing device, an information processing method, and a program.

Conventional technologies for improving the accuracy of credit card credit checks are known. For example, Patent Document 1 proposes an information processing device that generates a learning model based on the user's behavioral history before credit is granted and their record of defaulting on debt after credit is granted, and then uses the generated learning model to output an index value regarding whether or not the user will default on debt.

Patent No. 6679648

However, the information processing device described in Patent Document 1 could not perform ongoing credit checks based on information regarding credit card payment authorization (hereinafter referred to as "authorization"), and therefore, it was sometimes unable to effectively prevent bad debts.

This invention was made in consideration of these circumstances, and one of its objectives is to provide an information processing device, an information processing method, and a program that can effectively suppress the occurrence of bad debts.

One aspect of the present invention is an information processing device comprising: an authorization processing unit that performs authorization to confirm whether payment is possible when a user makes a payment using a credit card; a rule generation unit that generates rules for combinations of authorization attribute information (information relating to the attributes of the authorization) and user attribute information (information relating to the attributes of the user) such that the probability of a default occurring for the user is above a predetermined threshold; and a determination unit that, triggered by the execution of the authorization, determines whether or not to perform ongoing credit assessment processing, which is a review conducted on the user while using the credit card after credit has been extended for the credit card, based on the rule.

According to one aspect of the present invention, an information processing device, an information processing method, and a program can be provided that can effectively suppress the occurrence of bad debts.

This diagram shows an example of the configuration of an electronic payment system that enables electronic payment services. This is a sequence diagram (part 1) illustrating the general flow of electronic payments. This is a sequence diagram (part 2) illustrating the general flow of electronic payments. This is a diagram showing the configuration of the payment server 100. This figure shows an example of the contents of user information 172. This figure shows an example of the contents of merchant/store information 176. This is a diagram showing the configuration of the card company server 200. This figure shows an example of the contents of user information 272. This figure shows an example of the contents of credit card information 274. This figure shows an example of the contents of authorization history information 276. This figure shows an example of the contents of statistical information 278. This figure shows an example of the content of Rule R. This is a sequence diagram illustrating an example of a credit card payment process. This flowchart shows an example of a process performed by the card company server 200.

The following describes embodiments of the information processing apparatus, information processing method, and program of the present invention with reference to the drawings. Various devices, such as servers, that provide services to users or perform internal analysis may be implemented by a distributed group of devices, and the operators of each device may be different. Furthermore, the owner of the hardware (the provider of the cloud server) and the operator that actually operates the device may also be different. The application program and the payment server work together to provide an electronic payment service. In the following description, the application program will be referred to as a payment app. The electronic payment service is a service that supports payment for the purchase of goods and services at a store. A store is, for example, a physical store (a real store) existing in the real world, but may also include a virtual store for e-commerce. A virtual store may include one provided by an entity different from the operator of the electronic payment service. In that case, when settling a purchase at the virtual store, the user is controlled to transition to the electronic payment service interface screen. In the electronic payment service, a store is treated as belonging to, for example, a merchant (brand), and processing such as payment when a purchase is made at the store is mainly carried out between the user and the merchant. Alternatively, processing such as payment may be carried out between the user and the store.

[Electronic payment service]
Figure 1 shows an example of the configuration of an electronic payment system in which an electronic payment service is implemented. The electronic payment service is implemented with a payment server 100 at its center. The electronic payment system that implements 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 store terminal device for cards 80, a 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, and provider equipment.

Some or all of the functional configurations included in the electronic payment system may be distributed across multiple devices in any form, or integrated into any device. For example, some or all of the functional configurations of the card company server 200 may be included in the configuration of the payment server 100, and some or all of the functional configurations of the payment server 100 may be included in the functional configuration of the card company server 200.

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

The first store terminal device 50 is, for example, installed 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 may include a so-called POS (Point of Sale) device, and the product price acquisition function and optical reading function may be implemented 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 paper or plastic media. The store code image 60 may also be displayed on a display placed in the store (this may also be the display of a terminal device such as a smartphone).

The second store terminal device 70 is used by the operator of the affiliated store. The second store terminal device 70 is a smartphone, tablet, personal computer, etc. The affiliated store interface 72 operates on the second store terminal device 70. The affiliated store interface 72 may be an affiliated store application or a browser. The affiliated store interface 72 receives coupon settings, etc., from the affiliated store operator and transmits them to the payment server 100. The second store terminal device 70, being a smartphone, has the function of displaying a code image corresponding to the store code image by running the affiliated store application, and reading the code image displayed by the user terminal device 10.

The payment server 100 implements 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 a merchant server; in this case, payment information is transmitted from the POS device to the payment server 100 via the merchant server. In the following description, this distinction is not made, and it will be assumed that payment information is transmitted from the first store terminal device 50.

The card terminal device 80 is a terminal device used at credit card merchants. The card terminal device 80 acquires credit card information presented by the user and transmits the acquired information to the card company server 200.

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

Figures 2 and 3 are sequence diagrams illustrating the general flow of electronic payment. There may be two patterns for electronic payment: Pattern 1 and Pattern 2.

In the case of Pattern 1 shown in Figure 2 (hereinafter referred to as User Scan), the user terminal device 10, with the payment application 20 running, decodes the store code image 60 using its optical reading function (S1). The store code image 60 contains information about the store URL (Uniform Resource Locator). This store URL is an electronic payment service domain to which information that can identify the store has been added, and it is associated with the merchant ID and store ID, etc., in the payment server 100 (described later). The payment application 20 sends the first payment information, including the store URL and account ID, to the payment server 100 (S2). The payment server 100 searches for store information (described later) from the merchant ID and store ID corresponding to the store URL, obtains the merchant name and store name information (S3), and sends it to the payment application 20 (S4). The user enters the payment amount into the user terminal device 10 on the screen where the merchant name and store name are displayed (S5). The user terminal device 10 then generates second payment information, including at least the payment amount, and transmits it to the payment server 100 (S6). The payment server 100 performs the electronic payment based on the received second payment information (S7). The payment server 100 then sends a payment completion notification (information for displaying the payment completion screen) to the payment application 20 (S8), and the payment application 20 displays the payment completion screen (S9). Note that if the store code image 60 is displayed on a display in the store, the store code image 60 may include not only the store URL but also the payment amount information. In this case, the procedure for the user to enter the payment amount is omitted, and the payment amount information is included in the first payment information and transmitted to the payment server 100. Merchant name and store name information may be included and displayed on the payment completion screen.

In the case of Pattern 2 shown in Figure 3 (hereinafter referred to as Store Scan), when the payment app 20 is launched, when a payment operation is performed in the payment app 20, when it is time for automatic updates (for example, every minute), and at other times, the payment app 20 sends a request to the payment server 100 to issue a one-time code (S11). The payment server 100 generates a one-time code (S12) and sends it to the payment app 20 (S13). The payment app 20 displays a code image such as a QR code or barcode generated based on the one-time code (S14). The user holds the display surface of the user terminal device 10 over the first store terminal device 50 (presents it), and the first store terminal device 50 decodes the code image using its optical reading function and obtains the one-time code, etc. (S15). Then, the first store terminal device 50 generates payment information including the one-time code, payment amount, merchant ID, store ID, etc., and sends it to the payment server 100 (S16). The payment amount information is obtained in advance through barcode scanning or manual input. The payment server 100 identifies the user corresponding to the one-time code based on the received information and performs the electronic payment (S17). Then, the payment server 100 sends a payment completion notification to the payment application 20 (S18), and the payment application 20 displays a payment completion screen (S19).

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

[Payment Server]
Figure 4 is a diagram of the configuration of the payment server 100. The payment server 100 includes, for example, a communication unit 110, a payment content provision unit 120, a payment processing unit 130, an information management unit 140, and a storage unit 170. Components other than the communication unit 110 and the storage unit 170 are realized, for example, by 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 LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), GPU (Graphics Processing Unit), and SOC (System On Chip), or by the cooperation of software and hardware. The program may be stored in advance on a storage device such as an HDD (Hard Disk Drive) or flash memory (a storage device equipped with a non-transient storage medium), or it may be stored on a removable storage medium such as a DVD or CD-ROM (a non-transient storage medium) and installed on the storage device when the storage medium is inserted into the drive device.

The storage unit 170 may be an HDD, flash memory, or RAM (Random Access Memory). The storage unit 170 may also be a NAS (Network Attached Storage) device accessible by the payment server 100 via a network. The storage unit 170 stores information such as user information 172, payment content information 174, and merchant/store information 176. Some of this information may also be stored in the storage unit of the user terminal device 10.

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

The payment content provision unit 120, for example, has the functionality 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 provision unit 120 reads the necessary content from the payment content information 174 as appropriate and provides it to the user terminal device 10. The user terminal device 10 receives various inputs from the user while the content is being played by the payment application 20, and transmits the aforementioned payment information to the payment server 100. The above content may also be generated by the payment application 20. In this case, the payment content provision unit 120 provides the payment application 20 with the information necessary for content generation.

The payment processing unit 130 performs payment processing based on 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.

Figure 5 shows an example of the contents of User Information 172. User Information 172 is an example of user registration information. User Information 172 includes, for example, user URL, account ID, telephone number, password, as well as information such as email address, user ID, name, address, date of birth, registration date, charge balance, credit payment settings, credit payment limit, credit payment amount, available credit payment amount, payment method settings, bank account, credit card number, charge history information, and payment history information. The user URL is used for transfer processing between users. When registering for the electronic payment service for the first time, registration of a telephone number and password is mandatory. The account ID is issued to the user by the payment server 100, and the user ID is an ID that the user can set at will (or does not have to set). Similarly, the email address, name, address, and date of birth are also information that the user can set at will (or does not have to set). The registration date is the date the user registered for the electronic payment service (the date the account was created). Hereafter, the user instance (electronic payment account) to which this information is associated will be referred to as an account.

The charge balance is information indicating the balance of electronic money set by the user by sending money to their account in advance. Methods of sending money include sending from an ATM (Automatic Teller Machine) of a designated provider (bank) and sending from a registered bank account. The credit payment setting indicates whether or not the user has completed the settings to enable electronic payments by credit card, and is set to either "Completed" or "Not Completed". The credit payment limit is the monthly limit for credit payments, the credit payment amount is the amount of credit payments already made in the current month, and the available credit payment amount is the amount of credit payments available in the current month, calculated by subtracting the credit payment amount from the credit payment limit. While the diagram shows only one credit payment limit, in reality there are also daily limits, and the lower of these may be set as the credit payment limit. Further details on credit payments will be described later. The payment method setting indicates whether the user will make an electronic payment using the charge balance or a credit payment at that time. The bank account and credit card numbers refer to the bank account or credit card number (account number, card number) that can be used to deposit funds into the electronic payment service. The charge history information is a record of when the user has previously sent funds to the electronic payment service to increase their balance. The payment history information shows the details of each payment made by the user (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.).

Figure 6 shows an example of the contents of the merchant/store information 176. The merchant/store information 176 includes, for example, a first table 176A where the merchant ID and store ID are associated with the store URL, a second table 176B where the merchant name and sales amount (as described above) are associated with the merchant ID, and a third table 176C where the store name is associated with the store ID. In addition to this information, the merchant/store information 176 may also include information such as the merchant or store category, store location, and payment pattern. The merchant name may be, for example, information registered by the merchant, or information registered by the administrator of the electronic payment service. The merchant name and store name may be managed in an integrated manner. The merchant name may also be, for example, a combination of the merchant name and store name. It is preferable that the merchant name be the official name or a detailed name. In the merchant/store information 176, the merchant ID or store ID may be associated with the merchant icon, or other detailed information about the merchant.

The Information Management Unit 140 acquires information provided by other server and terminal devices. Based on the information acquired from the user terminal device 10 and the second store terminal device 70, the Information Management Unit 140 manages user information 172 and affiliated store/store information 176. The Information Management Unit 140 performs operations such as adding, editing, and deleting new records for user information 172 and affiliated store/store information 176.

[Electronic payment]
When the payment processing unit 130 obtains payment information from the user terminal device 10 or the first store terminal device 50, it refers to the user information 172 to obtain the user's "payment method setting". For users 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, which is managed in association with the user ID, and increasing the value of the merchant's sales proceeds item. The merchant's sales proceeds item value is not used as electronic money itself, for example, but rather the amount corresponding to the sales proceeds item value is transferred to the bank account in a cycle according to the agreement between the merchant and the electronic payment service.

The payment processing unit 130 performs electronic payment as follows for users whose "settings information" is set to "credit card payment." Credit card payment is a payment method that involves cooperation with a credit card company, which is a separate entity from the electronic payment service operator. The electronic payment service operator acts as the creditor, allowing electronic payments that do not depend on the charge balance, within the limits of the credit card payment limit. To use the credit card payment service, users may be required to obtain a credit card provided by the electronic payment service operator. The amount used via credit card payment is settled in a lump sum for the month on the payment date of the following month, for example, by direct debit from a bank account. In this case, the payment processing unit 130 performs a provisional settlement by adding the settlement amount to the credit card payment amount and subtracting the same amount from the available credit card payment limit. At the closing date, it processes the payment for the current month to be debited on the payment date of the following month, or requests the credit card company operator to perform the process. If the settlement amount exceeds the available credit card payment limit at the time of provisional settlement, an error notification is sent back to the payment application 20.

[Card company server]
Figure 7 is a diagram of the configuration 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. Components other than the communication unit 210 and the storage unit 270 are realized, for example, by a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuit parts) such as LSIs, ASICs, FPGAs, and GPUs, or by the cooperation of software and hardware. The program may be stored in advance on a storage device such as an HDD or flash memory (a storage device equipped with a non-transient storage medium), or it may be stored on a removable storage medium such as a DVD or CD-ROM (a non-transient storage medium) and installed on the storage device when the storage medium is inserted into a drive device.

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

The storage unit 270 can be an HDD, flash memory, RAM, etc. The storage unit 270 may also be a NAS (Network Attached Storage) device accessible by the card company server 200 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.

Figure 8 shows an example of the contents of User Information 272. User Information 272 contains information about the user who owns the credit card. Each item in User Information 272 is entered by the user when applying for the credit card.

User information 272 includes, for example, user ID, age, gender, and name, address, and date of birth. The user ID is identification information used to identify the credit card user. Age is the age of the credit card user. Gender is the gender of the credit card user. Name, address, and date of birth are the name, address, and date of birth of the credit card user. Note that user information 272 may also include other information. For example, user information 272 may include information such as the credit card user's occupation, annual income, or loan amount.

Figure 9 shows an example of the contents of credit card information 274. Credit card information 274 contains information about the user's credit card. 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.

Credit card information 274 includes, for example, the credit card number, user ID, cardholder name, expiration date, security code, credit limit, transaction amount, and card transaction history. The credit card number is a number used to identify the credit card. The user ID is identification information used to identify the user of the credit card, similar to the user ID shown in Figure 8. The cardholder name is the alphanumeric name of the credit card holder. The expiration date is information regarding the expiration date of the credit card. The security code is a number printed on the back of the credit card used to prevent fraudulent use. The credit limit is the maximum amount that can be spent using the credit card. Note that the credit limit may be set separately for shopping and cash advance limits. The transaction amount is the total amount paid using the credit card. Card transaction history is the history of credit card transactions and may include the name of the merchant where the payment was made, the merchant category, the date and time of payment, and the payment amount. Note that credit card information 274 may also include other information. For example, credit card information 274 may include information such as the type of credit card (standard, gold, platinum, black).

Figure 10 shows an example of the contents of authorization history information 276. Authorization history information 276 is information related to authorization (hereinafter referred to as "authorization") in credit card payments. Authorization is the process in credit card payments that verifies the validity and available credit limit of the credit card and determines whether payment is possible. Authorization is performed by the authorization processing unit 215.

The authorization history information 276 includes, for example, the transaction ID, credit card number, user ID, terminal identification number, merchant ID, payment amount, date and time, and whether or not there was a bad debt. The transaction ID is identification information for identifying the authorization transaction. The credit card number is a number for identifying the credit card, and is the same information as the credit card number shown in Figure 9. The user ID is identification information for identifying the credit card user, and is the same information as the user ID shown in Figures 8 and 9. The terminal identification number is the identification number of the card terminal device 80 that read the credit card information during credit card payment. The merchant ID is identification information for identifying the merchant. The payment amount is the payment amount for the credit card payment. The date and time indicates the date and time the authorization process was performed. The presence or absence of a bad debt indicates 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 will be "Yes". On the other hand, if no bad debt occurred, the presence or absence of a bad debt will be "No".

Figure 11 shows an example of the contents of statistical information 278. Statistical information 278 is information related to authorization statistics. Statistical information 278 is information generated by the authorization processing unit 215. Specifically, the authorization processing unit 215 generates statistical information 278 by performing statistical processing based on user information 272 and authorization history information 276. Statistical information 278 is an example of information related to authorization.

Statistical information 278 includes, for example, terminal identification information, amount range, time period, age, gender, user ID (normal), user ID (bad debt), and bad debt rate. The terminal identification number is the identification number of the card store terminal device 80 that read the information of the credit card used for credit card payment, and is the same information as the terminal identification number shown in Figure 10. The amount range is information indicating the amount range of the payment amount for credit card payments. The time period is information regarding the time period in which the authorization process was performed. Age is the age of the user who made the credit card payment. Gender is the gender of the user who made the credit card payment. User ID (normal) is a list of user IDs of users who did not incur a bad debt after the authorization process was performed. User ID (bad debt) is a list of user IDs of users who incur a bad debt after the authorization process was performed. The bad debt rate is information indicating the percentage of users who incur a bad debt. The authorization processing unit 215 calculates the default rate as the ratio (%) of user IDs (bad debts) to the total number of user IDs (normal) and user IDs (bad debts).

Furthermore, in the statistical information 278 shown in Figure 11, terminal identification information, amount range, and time period are examples of authorization attribute information, which is information related to the attributes of the authorization. Also, age and gender are examples of user attribute information, which is information related to the attributes of the user.

[Rule generation process]
Next, the rule generation process performed by the rule generation unit 260 will be described. As mentioned above, the authorization processing unit 215 performs authorization to confirm whether or not payment is possible when a user makes a payment using a credit card. Based on authorization information (statistical information 278) over a predetermined period, the rule generation unit 260 generates a rule R used to determine whether or not to perform ongoing credit assessment for the user. Ongoing credit assessment is a review performed on the user while using the credit card after credit has been extended for the credit card.

Specifically, the rule generation unit 260 refers to the statistical information 278 stored in the storage unit 270 and generates a rule R from combinations of authorization attribute information (terminal identification number, amount range, time period) and user attribute information (age, gender) such that the probability of a user defaulting on a loan is above a predetermined threshold.

For example, the rule generation unit 260 extracts combinations from the statistical information 278 shown in Figure 11 where the default rate is above a threshold (e.g., 40%). Specifically, the rule generation unit 260 extracts combinations with a default rate of 48% (T001, high amount, night, 20s, male), combinations with a default rate of 40% (T002, high amount, night, 20s, male), and combinations with a default rate of 50% (T003, high amount, night, 20s, male). The rule generation unit 260 then generates these extracted combinations as rule R.

Figure 12 shows 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 authorization attributes, including a terminal identification number, a price range, and a time zone. The terminal identification number is the identification number of the card store terminal device 80 that read the credit card information used for credit card payment, and is the same information as the terminal identification number shown in Figures 10 and 11. The price range is information indicating the price range of the credit card payment amount, and is the same information as the price range shown in Figure 11. The time zone is information about the time period during which the authorization process was performed, and is the same information as the time zone shown in Figure 11. The user attribute information is information about the user's attributes, including 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 Figure 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 Figure 11.

Furthermore, while authorization attribute information is defined as terminal identification number, transaction amount range, and time zone, it is not limited to this information. For example, authorization attribute information may include the merchant category to which the store where the payment was made belongs. Similarly, while user attribute information is defined as the user's age and gender, it is not limited to this information. For example, user attribute information may include the user's occupation, annual income, and loan amount.

[Sequence diagram]
Figure 13 is a sequence diagram showing an example of a credit card payment process. The process shown in the sequence diagram of Figure 13 is executed when a user places an order to purchase goods at a merchant's store. Although it is shown as a product purchase order here, it could also be an order to use a service.

First, the card terminal 80 acquires the user's credit card information (credit card number, expiration date, etc.) (S101). For example, the card terminal 80 may directly read the card information from the credit card presented by the user, or it may have the user input the card information.

Next, the card terminal 80 transmits authorization information to the card company server 200 (S102). For example, the authorization information includes the transaction ID, credit card number, terminal identification number, merchant ID, and payment amount. The transaction ID is identification information for identifying the transaction. The credit card number is the user's credit card number, included in the card information obtained in S101. The terminal identification number is identification information for identifying the card terminal 80. The merchant ID is identification information for identifying the merchant to which the store where the user intends to purchase goods belongs, and is similar to the merchant ID shown in Figure 6. The payment amount included in the authorization information is the payment amount at the time of authorization.

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

Furthermore, the authorization processing unit 215 updates the authorization history information 276 stored in the storage unit 270. Specifically, the authorization processing unit 215 adds the transaction ID, credit card number, user ID, terminal identification number, merchant ID, payment amount, and date and time to the authorization history information 276, linking them together. The transaction ID, credit card number, terminal identification number, merchant ID, and payment amount are information included in the authorization information received in S102. The user ID is the 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 field for bad debt in the authorization history information 276 is left blank.

Next, the communication unit 210 of the card company server 200 transmits the authorization result to the card-use store terminal device 80 (S104). The authorization result includes information such as the transaction ID and the judgment result (OK or NG). Here, we assume that the authorization process determines that the payment using the credit card is approved, and the authorization result (OK) is transmitted to the card-use store terminal device 80.

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

Next, the card company server 200 acquires the payment information transmitted from the card 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). Note that 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 merchant. For example, when a user makes a reservation for accommodation through a travel agency, the authorization process may use the accommodation fee as the payment amount, while the payment processing at the time of sale at the merchant (accommodation facility) may include the charges for services actually used at the accommodation (room service, etc.). Thus, the payment amount at the time of authorization and the payment amount at the time of sale at the merchant may differ.

Based on this, the card payment processing unit 220 retrieves 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 retrieved 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 charge amount by subtracting the payment amount retrieved from the authorization history information 276 from the payment amount included in the payment information. Then, the card payment processing unit 220 adds the additional charge amount to the amount used by the user's credit card in the credit card information 274, and completes the payment process. This ensures that payment processing can be performed appropriately even if the payment amount at the time of sale at the merchant is higher than the payment amount at the time of authorization.

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

Furthermore, even after credit card payment processing is complete, a default may occur on the payment due date of the following month due to insufficient funds in the user's bank account. If a default occurs, "Yes" will be recorded in the authorization history information 276. Conversely, if no default occurs, "No" will be recorded in the authorization history information 276.

[flowchart]
Figure 14 is a flowchart showing an example of a process executed by the card company server 200. The process shown in Figure 14 is triggered by the execution of the authorization process. The card company server 200 may execute the process shown in Figure 14 immediately after executing the authorization process, or it may be executed at a predetermined time (for example, 10:00 a.m. the day after the authorization process is executed).

First, the authorization attribute information acquisition unit 230 acquires authorization attribute information, which is information related to the attributes of the authorization (S201). The authorization attribute information includes, for example, the terminal identification number, the amount range, and the time zone. Specifically, the authorization attribute information acquisition unit 230 acquires the terminal identification number and amount range based on the authorization information (terminal identification number and payment amount, etc.) received in S102 of Figure 13. Furthermore, the authorization attribute information acquisition unit 230 acquires the time zone based on the time the authorization information was received.

Next, the user attribute information acquisition unit 235 acquires user attribute information, which is information about the user's attributes (S202). User attribute information includes, for example, age and gender. Specifically, the user attribute information acquisition unit 235 acquires the user ID linked to the credit card information included in the authorization information received in S102 of Figure 13 from the credit card information 274, and acquires the user's age and gender linked to the acquired user ID from the user information 272.

Next, the determination unit 225 determines whether or not to perform ongoing credit assessment 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 assessment is a review conducted on the user while the credit card is being used, after the credit has been extended. Specifically, the determination unit 225 determines whether the combination of the authorization attribute information acquired in S201 and the user attribute information acquired in S202 corresponds to rule R stored in the storage unit 270. If this combination of information does not correspond to rule R, the default rate will be below the threshold (for example, 40%), so the determination unit 225 determines not to perform ongoing credit assessment and terminates the process according to this flowchart.

On the other hand, if the combination of this information matches Rule R, the default rate will be above the threshold (e.g., 40%), and the determination unit 225 will determine to perform ongoing credit assessment. If it is determined that ongoing credit assessment 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). Credit information includes, for example, the user's credit card usage history (including those issued by other credit card companies), loan repayment status, and borrowed amounts.

Next, the score calculation unit 245 calculates a score indicating the likelihood of default for the user, based on the credit information acquired by the credit information acquisition unit 240 (S205). The score calculation unit 245 calculates a higher score the higher the likelihood of default. For example, the score calculation unit 245 calculates a higher score if the user has high credit card usage, is behind on loan repayments, or has a large outstanding debt.

Next, the execution unit 250 determines whether the score calculated by the score calculation unit 245 is higher than a predetermined threshold (S206). If the score is below the predetermined threshold, the execution unit 250 determines that the likelihood of bad debt is low and terminates the process according to this flowchart.

On the other hand, if the score is greater than a predetermined threshold, the execution unit 250 performs a credit limit reduction or suspension of the user's credit card (S207). Credit limit reduction is a process that reduces the available credit limit of the user's credit card. Credit card suspension is a process that prevents the user from using their credit card. For example, if the score calculated by the score calculation unit 245 is higher than a predetermined value, the execution unit 250 may suspend the user's credit card. Also, if the score calculated by the score calculation unit 245 is less than or equal to a predetermined value, the execution unit 250 may reduce the credit limit of the user's credit card. Afterward, the execution unit 250 terminates the process according to this flowchart.

Furthermore, in S203, the determination unit 225 may determine whether or not to perform ongoing credit assessment by taking into account the user's payment history information in the electronic payment service. Specifically, the payment history information acquisition unit 255 may acquire payment history information, which is the 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 the information included in the user information 172 shown in Figure 5. The determination unit 225 may also determine whether or not to perform ongoing credit assessment by taking into account the payment history information. For example, if the user's payment history information includes payment history at merchants (such as gambling establishments) included in a pre-configured blacklist, the determination unit 225 may determine to perform ongoing credit assessment. This allows the card company server 200 to more effectively suppress the occurrence of bad debts.

[Variations of the rule generation process]
In the above description, the rule generation unit 260 generates a rule R from among the combinations of authorization attribute information and user attribute information such that the default rate is equal to or greater than a predetermined threshold, but it is not limited to this. For example, the rule generation unit 260 may generate a rule R by performing machine learning based on statistical information 278. Specifically, the rule generation unit 260 may generate a trained model to be used as a rule R by performing machine learning with authorization attribute information and user attribute information as explanatory variables and the default rate as the dependent variable. This enables the card company server 200 to generate a rule R (trained model) for outputting a highly accurate default rate.

Furthermore, the statistical information 278 may include information about the credit card brand (Visa®, Mastercard®, etc.). The rule generation unit 260 may also generate rules R by analyzing authorization information (statistical information 278) over a predetermined period, for combinations of credit card brands and terminal identification numbers where the default rate exceeds a predetermined threshold (e.g., 40%). This allows the card company server 200 to generate rules R for outputting highly accurate default rates, taking into account the credit card brand.

Furthermore, the rule generation unit 260 may, by analyzing authorization information (statistical information 278) over a predetermined period, generate a list of merchant names among those to which credit card payments are made, where the probability of default for the user exceeds a predetermined threshold, as rule R. This allows the card company server 200 to generate a list of specific merchant names prone to default as a blacklist rule.

According to the embodiment described above, the card company server (information processing device) 200 comprises an authorization processing unit 215 and a determination unit 225. The authorization processing unit 215 performs authorization to confirm whether payment is possible when a user makes a payment using a credit card. The determination unit 225, triggered by the execution of authorization, determines whether or not to perform ongoing credit checks on the user based on information related to the authorization (statistical information 278). This allows the card company server 200 to effectively prevent bad debts.

In the above explanation, the card company server 200 is described as an example of an information processing device, and it is assumed that the payment server 100 and the card company server 200 are separate servers. However, this is not limited to this configuration. For example, if the electronic payment service provider and the card company are the same company or group companies, a single server integrating the payment server 100 and the card company server 200 may be provided as the information processing device.

Although embodiments for carrying out the present invention have been described above using examples, the present invention is not limited in any way to these embodiments, and various modifications and substitutions can be made without departing from the spirit of the invention.

10 User terminal device 20 Payment application 50 First store terminal device 100 Payment server 110 Communication unit 120 Payment content provision unit 130 Payment processing unit 140 Information management unit 170 Storage unit 200 Card company server 210 Communication unit 210
215 Authorization Processing Unit 220 Card Payment Processing Unit 225 Determination Unit 230 Authorization Attribute Information Acquisition Unit 235 User Attribute Information Acquisition Unit 240 Credit Information Acquisition Unit 245 Score Calculation Unit 250 Execution Unit 255 Payment History Information Acquisition Unit 260 Rule Generation Unit 270 Storage Unit

Claims (11)

When a user makes a payment using a credit card, an authorization processing unit performs an authorization to check whether the payment is possible, and
A rule generation unit generates rules for combinations of authorization attribute information, which is information about the attributes of the authorization, and user attribute information, which is information about the attributes of the user, such that the probability of a default occurring for the user is above a predetermined threshold.
A determination unit, triggered by the execution of the authorization, determines whether or not to perform an ongoing credit check, which is a review conducted on the user while the credit card is being used, after the credit for the credit card has been extended, based on the rules.
An information processing device equipped with the following features. The authorization attribute information acquisition unit acquires the authorization attribute information,
The system further comprises a user attribute information acquisition unit that acquires the aforementioned user attribute information,
The determination unit determines whether or not to perform the processing for ongoing credit assessment based on the rules, the authorization attribute information, and the user attribute information.
The information processing apparatus according to claim 1. The authorization attribute information includes at least one of the following: a terminal identification number for identifying the terminal of the store where the payment using the credit card was made, the merchant category to which the store belongs, the amount range of the payment, and the time period during which the authorization is performed.
The information processing apparatus according to claim 1. The user attribute information includes at least one of the user's age, gender, occupation, annual income, and loan amount.
The information processing apparatus according to claim 1. If it is determined that the aforementioned credit assessment process should be performed, a credit information acquisition unit obtains the user's credit information from an external server,
A score calculation unit calculates a score indicating the degree to which defaults are likely to occur for the user based on the aforementioned credit information,
An execution unit that, based on the score, performs a reduction or suspension of the user's credit card,
The information processing apparatus according to claim 1, further comprising the following: The system further includes a payment history information acquisition unit that acquires payment history information, which is the history of electronic payments made by the user, from a payment server that performs electronic payments using electronic money.
The determination unit takes the settlement history information into consideration and determines whether or not to perform the processing for ongoing credit assessment.
The information processing apparatus according to claim 1. The rule generation unit generates a trained model to be used as the rule by using authorization attribute information, which is information about the attributes of the authorization, and user attribute information, which is information about the attributes of the user, as explanatory variables, and default rate, which is information indicating the probability that a default has occurred for the user, as the target variable through machine learning.
The information processing apparatus according to claim 1. The rule generation unit analyzes the authorization information over a predetermined period and generates a rule for a combination of the credit card brand and the terminal identification number for identifying the terminal of the store where the payment was made using the credit card, such that the probability of a default occurring for the user is above a predetermined threshold.
The information processing apparatus according to claim 1. The rule generation unit analyzes the authorization information over a predetermined period and generates a list of the names of merchants to which the store where the credit card payment was made belongs, where the probability of a default occurring for the user is above a predetermined threshold, as the rule.
The information processing apparatus according to claim 1. Information processing device,
When a user makes a payment using a credit card, an authorization process is performed to verify whether the payment is valid.
A rule is generated for combinations of authorization attribute information, which is information about the attributes of the authorization, and user attribute information, which is information about the attributes of the user, such that the probability of a default occurring for the user is above a predetermined threshold.
Triggered by the execution of the authorization, the system determines whether or not to perform an ongoing credit check, which is a review conducted on the user while the credit card is being used, after the credit has been extended for the credit card, based on the rules.
Information processing methods. In an information processing device,
When a user makes a payment using a credit card, an authorization process is performed to verify whether the payment is valid.
A rule is generated for combinations of authorization attribute information, which is information about the attributes of the authorization, and user attribute information, which is information about the attributes of the user, such that the probability of a default occurring for the user is above a predetermined threshold.
Triggered by the execution of the aforementioned authorization, the system determines whether or not to perform an ongoing credit check, which is a review conducted on the user while the credit card is being used, after the credit for the credit card has been extended, based on the aforementioned rules.
program.