Credit card management apparatus

Abstract

To provide a credit card management apparatus which automatically determines a payment account according to how a credit card is used, without requiring a user of the credit card to designate the payment account when using the credit card.SOLUTION: A credit card management apparatus 10 includes: a management unit 111 which manages a card number of a credit card in association with a plurality of payment accounts; an acquisition unit 112 which acquires use information including the amount paid by using the credit card and the card number, use information relating to the use of the credit card; a classifying unit 113 which classifies modes of use of the credit card on the basis of the use information; a determination unit 114 which determines one of the payment accounts associated with the credit card, on the basis of the result classified by the classifying unit 113; and a settlement unit 115 which generates settlement information for withdrawing the amount paid from the one payment account.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a credit card management device. [Background technology]

[0002] Patent Document 1 discloses a system in which two or more payment accounts are registered to one credit card. In this system, a PIN is associated with each payment account and stored in a master file. A user inputs the PIN when using a credit card. If the input PIN is a PIN stored in the master file, the system recognizes the user as the owner of the credit card, and at the same time, determines the payment account corresponding to the matching PIN as the payment account for the credit card transaction. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2005-182560 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, in conventional systems, the payment account was designated by inputting a PIN number, so when entering the PIN number, the user had to decide which of multiple payment accounts to withdraw money from, which was inconvenient.

[0005] SUMMARY OF THE PRESENT EMBODIMENT An object of the present invention is to provide a credit card management device that automatically determines a payment account depending on the mode of credit card usage, without the need for a credit card user to specify a payment account when using the credit card. [Means for solving the problem]

[0006] The credit card management device of the present invention comprises a management unit that manages credit card numbers in association with multiple payment accounts, an acquisition unit that acquires usage information regarding the use of the credit card, including the payment amount associated with the use of the credit card and the card number, a classification unit that classifies the usage manner of the credit card based on the usage information, a determination unit that determines one of multiple payment accounts linked to the credit card based on the classification result of the classification unit, and a settlement unit that generates settlement information to debit the payment amount from the one payment account. Effect of the Invention

[0007] According to the present invention, a payment account can be automatically determined according to the manner of use of the credit card without the need to specify a payment account when using the credit card, thereby improving convenience for the credit card owner. [Brief description of the drawings]

[0008] [Figure 1] 1 is a block diagram showing the overall configuration of a credit card management system 1. FIG. [Diagram 2] FIG. 2 is a block diagram showing an example of the configuration of a credit card server 10. [Diagram 3] A table showing an example of the configuration of a payment account information database PDB. [Figure 4] 1 is a table showing an example of the configuration of a history information database HDB. [Diagram 5] FIG. 2 is a block diagram showing an example of the configuration of a user device 20. [Figure 6] 4 is a flowchart showing the operation of the credit card server 10. [Figure 7] A table showing an example of the configuration of a payment account information database PDB. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] 1: Implementation The credit card management system 1 according to this embodiment will be described below with reference to the drawings.

[0010] 1-1: Configuration of the embodiment 1-1-1: Overall composition FIG. 1 is a block diagram showing the overall configuration of a credit card management system 1 according to this embodiment. As shown in FIG. 1, the credit card management system 1 includes a credit card server 10, a user device 20, bank servers BS1 to BS4, and store servers SP1 to SP4. The credit card server 10, the user device 20, the bank servers BS1 to BS4, and the store servers SP1 to SP4 are connected to each other via a communication network NET so that they can communicate with each other. Note that FIG. 1 shows only one user device 20. However, the credit card management system 1 may include multiple user devices 20. Also, FIG. 1 shows four bank servers BS1 to BS4 and four store servers SP1 to SP4. However, the number of bank servers BS1 to BS4 and the number of store servers SP1 to SP4 may each be any number.

[0011] The credit card server 10 manages information related to credit cards used by credit card users. More specifically, the credit card server 10 manages the card number of the credit card in question in association with multiple payment accounts. The credit card server 10 then generates settlement information for debiting the payment amount from one of the multiple payment accounts. The functions of the credit card server 10 will be described in detail below with reference to FIG. 2. The credit card server 10 is an example of a "credit card management device."

[0012] The user device 20 is a device used by a credit card user. The user can purchase products or services on the Internet by inputting information including a credit card number into the user device 20, for example.

[0013] The user also uses a "household accounting app" that is an application with a household accounting function installed in the user device 20. The household accounting app manages data related to the user's expenditures on credit cards. When the user uses a credit card, payment information related to the payment at that time is read into the household accounting app. The user inputs a classification for each payment using the input device 25 described below. Here, "classification" refers to an item classified according to the content of the payment. For example, when the user photographs a receipt received at the time of payment with the user device 20, the household accounting app may automatically classify each payment. As a result, the past credit card usage history is classified in the household accounting app. The household account book application then generates classification information regarding classification of payments. Here, "classification information" refers to information that associates information regarding classification of expenses, such as food expenses, housing expenses such as rent or mortgage, communication expenses, utility expenses, education expenses, and entertainment expenses, with the payee of the expenses.

[0014] The bank servers BS1 to BS4 are servers that execute settlements corresponding to purchases when a credit card user uses a credit card to purchase a product or service. More specifically, when a credit card user purchases a product or service, the bank servers BS1 to BS4 debit the payment amount for the purchase from a single payment account linked to the credit card.

[0015] The store servers SP1 to SP4 are servers that accept credit card payments. Note that the "store" here may be a physical store that exists in real space, or a virtual store located on the Internet. When a credit card user purchases a product or service at a physical store, the store servers SP1 to SP4 read card information including the card number recorded on the credit card itself. When a credit card user purchases a product or service at a virtual store located on the Internet, the card information is transmitted from the user device 20 to the store servers SP1 to SP4. The store servers SP1 to SP4 acquire the card information transmitted from the user device 20.

[0016] The store servers SP1 to SP4 transmit the above card information, payment information indicating the date and time of payment and the amount of the purchase, and statement information indicating the transaction details including the store name to the credit card server 10 as usage information regarding the use of the credit card.

[0017] 1-1-2: Configuration of credit card server 10 Fig. 2 is a block diagram showing an example of the configuration of credit card server 10. As shown in Fig. 2, credit card server 10 comprises a processing device 11, a storage device 12, a communication device 13, a display device 14, and an input device 15. The elements of credit card server 10 are connected to each other by one or more buses for communicating information. Note that the term "apparatus" in this specification may be interpreted as other terms such as a circuit, a device, or a unit.

[0018] The processing device 11 is a processor that controls the entire credit card server 10. The processing device 11 is configured, for example, using one or more chips. The processing device 11 is also configured, for example, using a central processing unit (CPU) including an interface with peripheral devices, an arithmetic unit, and a register. Some or all of the functions of the processing device 11 may be realized by hardware such as a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array). The processing device 11 executes various processes in parallel or sequentially.

[0019] The storage device 12 is a recording medium that can be read and written by the processing device 11. The storage device 12 includes, for example, a nonvolatile memory and a volatile memory. The nonvolatile memory is, for example, a ROM (Read Only Memory), an EPROM (Erasable Programmable Read Only Memory), and an EEPROM (Electrically Erasable Programmable Read Only Memory). The volatile memory is, for example, a RAM (Random Access Memory). The storage device 12 also stores a control program PR1 executed by the processing device 11. The storage device 12 also functions as a work area for the processing device 11.

[0020] Furthermore, the storage device 12 stores a payment account information database PDB and a history information database HDB.

[0021] Figure 3 is a table showing an example of the configuration of the payment account information database PDB. In the example shown in Figure 3, payment account information is stored in the payment account information database PDB. The payment account information is information that associates information indicating a credit card number, information indicating a plurality of payment accounts, and the classification results of classification unit 113, which will be described later. Furthermore, the information indicating the payment accounts includes information indicating the account ID, financial institution code, branch code, account holder, account type, and account number of each account. The classification results of classification unit 113 are classification results relating to the manner of use of credit cards.

[0022] 3, for example, information indicating a card number of "3564412" is associated with information indicating three payment accounts with account IDs of "001" to "003". The payment account with account ID "001" has a financial institution code of "4362", a branch code of "224", an account holder name of "NA", an account type of "2" indicating a regular savings account, and an account number of "1309726". The payment account with account ID "002" has a financial institution code of "5681", a branch code of "115", an account holder name of "NA", an account type of "2" indicating a regular savings account, and an account number of "3598762". The payment account with account ID "003" has a financial institution code of "5681", a branch code of "115", an account holder of "BA", an account type of "9" indicating a current account, and an account number of "6798765". In other words, the payment account with account ID "001", the payment account with account ID "002", and the payment account with account ID "003" are three different accounts. Information indicating that the card number is "3564412" is associated with information indicating these three different payment accounts.

[0023] Furthermore, the payment account with the account ID of "001" is associated with the classification result of "food expenses". This correspondence indicates that when the classification result of classification unit 113 is "food expenses", the determination unit 114 described below will determine the payment account with the account ID of "001" as the payment account from which the payment amount is to be withdrawn. The payment account with the account ID of "002" is associated with the classification result of "utility expenses". This correspondence indicates that when the classification result of classification unit 113 is "utility expenses", the determination unit 114 described below will determine the payment account with the account ID of "002" as the payment account from which the payment amount is to be withdrawn. The payment account with the account ID of "003" is associated with the classification result of "entertainment expenses". This correspondence indicates that when the classification result of classification unit 113 is "entertainment expenses", determination unit 114, which will be described later, determines the payment account with the account ID of "003" as the payment account from which the payment amount is to be withdrawn. Details of the operations of classification unit 113 and determination unit 114 will be described later.

[0024] Fig. 4 is a table showing an example of the configuration of the history information database HDB. In the example shown in Fig. 4, history information is stored in the history information database HDB. The history information associates information indicating a card number with information indicating a usage history. The information indicating a usage history includes information indicating a usage ID, a payment date and time, a payment amount, a usage statement, and a payment account.

[0025] In the table shown in Fig. 4, for example, information indicating that the card number is "1865453" is associated with information indicating the usage history of the usage ID = "001". The information indicating the usage history of the usage ID = "001" includes information indicating that the payment date and time was "202311091231", that is, a payment was made at 12:31 on November 9, 2023, information indicating that the payment amount was "300,000" yen, information indicating that the usage details were used at "Store A", and information indicating that the payment account is an account with an account ID of "008" in the payment account information database PDB of Fig. 3.

[0026] In the example shown in Fig. 4, the payment account corresponding to the usage ID = "007" is left blank. This blank field indicates that the payment account has not yet been determined at the present time.

[0027] 2, the communication device 13 is hardware as a transmitting / receiving device for communicating with other devices. The communication device 13 is also called, for example, a network device, a network controller, a network card, and a communication module. The communication device 13 may include a connector for wired connection and a wireless communication interface. Examples of the connector and interface circuit for wired connection include products that comply with wired LAN, IEEE1394, and USB. Examples of the wireless communication interface include products that comply with wireless LAN, Bluetooth (registered trademark), and the like.

[0028] The display device 14 is a device for displaying images. The display device 14 displays various images under the control of the processing device 11.

[0029] The input device 15 is a device that accepts operations by a user of the credit card server 10. The input device 15 outputs an operation signal corresponding to the user's operation to the processing device 11. The input device 15 is composed of, for example, a keyboard and a pointing device.

[0030] In the above configuration, the processing device 11 reads the control program PR1 from the storage device 12. The processing device 11 functions as a management unit 111, an acquisition unit 112, a classification unit 113, a determination unit 114, and a settlement unit 115 by executing the read control program PR1.

[0031] The management unit 111 manages the payment account information stored in the payment account information database PDB and the history information stored in the history information database HDB.

[0032] The acquisition unit 112 acquires usage information from the store servers SP1 to SP4 via the communication device 13. Furthermore, the acquisition unit 112 stores the card information indicating the card number, payment information indicating the payment date and time and payment amount, and statement information indicating the usage details, which are included in the usage information, in the history information database HDB as part of the history information. The acquisition unit 112 also acquires payment account information and sorting information from the user device 20 via the communication device 13. Furthermore, the acquisition unit 112 stores the payment account information in the payment account information database PDB.

[0033] The classification unit 113 classifies the usage manner of the credit card based on the usage information acquired by the acquisition unit 112. For example, the classification unit 113 classifies the usage of the credit card based on the above-mentioned usage information and the classification information acquired by the acquisition unit 112. As an example, it is assumed that the acquisition unit 112 acquires usage information shown in the history information database HDB of FIG. 4, in which the card number is "1865453", the usage ID is "005", the payment date and time is "202311101835", the payment amount is "3,000" yen, and the usage details are "G gas". It is also assumed that the classification information is acquired from the user device 20 of a user who uses a credit card with the card number "1865453", indicating that the expenses paid to "G gas" are classified as utility expenses. In this case, the classification unit 113 classifies the usage of the credit card with the card number "1865453" corresponding to the usage ID = "005" into "utility expenses".

[0034] The determination unit 114 determines one of the multiple payment accounts linked to the credit card based on the classification result of the classification unit 113. As an example, if the classification unit 113 classifies the usage of the credit card with card number "1865453" corresponding to the usage ID "005" as "utility bills" as described above, the determination unit 114 refers to the payment account information database PDB to determine that the account with account ID "009", which is the account used for paying "utility bills", is the payment account out of the two accounts with account ID "008" and account ID "009" linked to the card number "1865453".

[0035] The settlement unit 115 generates settlement information for debiting the payment amount from the one payment account determined by the determination unit 114. The settlement unit 115 also transmits the generated settlement information to one of the bank servers BS1 to BS4 corresponding to the one payment account. For example, as described above, when the determination unit 114 determines the account with account ID = "009" as the payment account, the settlement unit 115 generates settlement information for debiting the payment amount of "3,000" yen corresponding to the usage ID = "005" from the account with account ID = "009". The settlement unit 115 also transmits the payment information to the bank server BS corresponding to the account with account ID = "009".

[0036] 1-1-3: Configuration of user device 20 Fig. 5 is a block diagram showing an example of the configuration of the user equipment 20. As shown in Fig. 5, the user equipment 20 includes a processing device 21, a storage device 22, a communication device 23, a display device 24, and an input device 25. The elements of the user equipment 20 are connected to each other by one or more buses for communicating information. Note that the term "apparatus" in this specification may be replaced with other terms such as a circuit, a device, or a unit.

[0037] The processing device 21 is a processor that controls the entire user device 20. The processing device 21 is configured, for example, using one or more chips. The processing device 21 is also configured, for example, using a central processing unit (CPU) including an interface with peripheral devices, an arithmetic unit, and a register. Some or all of the functions of the processing device 21 may be realized by hardware such as a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA). The processing device 11 executes various processes in parallel or sequentially.

[0038] The storage device 22 is a recording medium that can be read and written by the processing device 21. The storage device 22 includes, for example, a nonvolatile memory and a volatile memory. The nonvolatile memory is, for example, a Read Only Memory (ROM), an Erasable Programmable Read Only Memory (EPROM), and an Electrically Erasable Programmable Read Only Memory (EEPROM). The volatile memory is, for example, a Random Access Memory (RAM). The storage device 22 also stores a control program PR2 executed by the processing device 21. The storage device 22 also functions as a work area for the processing device 21.

[0039] The communication device 23 is hardware as a transmitting / receiving device for communicating with other devices. The communication device 23 is also called, for example, a network device, a network controller, a network card, and a communication module. The communication device 23 may include a connector for wired connection and a wireless communication interface. Examples of the connector and interface circuit for wired connection include products that comply with wired LAN, IEEE1394, and USB. Examples of the wireless communication interface include products that comply with wireless LAN, Bluetooth (registered trademark), and the like.

[0040] The display device 24 is a device for displaying images. The display device 24 displays various images under the control of the processing device 21.

[0041] The input device 25 is a device that accepts operations by a credit card user who is the user of the user device 20. The input device 25 outputs an operation signal according to the user's operation to the processing device 21. The input device 25 is composed of, for example, a keyboard and a pointing device.

[0042] In the above configuration, the processing device 21 reads out the control program PR2 from the storage device 22. The processing device 21 executes the read out control program PR2 to execute the household accounting application. The processing device 21 also transmits sorting information generated by the household accounting application to the credit card server 10 via the communication device 23.

[0043] 1-2: Operation of the embodiment FIG. 6 is a flowchart showing the operation of credit card server 10.

[0044] In step S1, the processing device 11 acquires, via the communication device 13, usage information from the store servers SP1 to SP4.

[0045] In step S2, the processor 11 classifies the manner of use of the credit card based on the usage information acquired in step S1.

[0046] In step S3, the processing device 11 determines one of the multiple payment accounts linked to the credit card based on the classification result in step S2.

[0047] In step S4, the processor 11 generates payment information for debiting the payment amount from the one payment account determined in step S3. Furthermore, the processor 11 transmits the generated payment information to any one of the bank servers BS1 to BS4 corresponding to the one payment account.

[0048] In step S1, the processing device 11 functions as an acquisition unit 112. In step S2, the processing device 11 functions as a classification unit 113. In step S3, the processing device 11 functions as a determination unit 114. In step S4, the processing device 11 functions as a settlement unit 115.

[0049] 1-3: Advantages of the present embodiment According to the above description, credit card server 10 as a credit card management device comprises management unit 111, acquisition unit 112, classification unit 113, determination unit 114, and settlement unit 115. Management unit 111 manages credit card card numbers in association with multiple payment accounts. Acquisition unit 112 acquires usage information related to the use of a credit card, including a payment amount and card number associated with the use of the credit card. Classification unit 113 classifies the usage manner of the credit card based on the usage information. Determination unit 114 determines one of the multiple payment accounts linked to the credit card based on the classification result of classification unit 113. Settlement unit 115 generates settlement information for debiting the payment amount from one payment account.

[0050] Since credit card server 10 has the above configuration, the payment account can be automatically determined according to the manner of use of the credit card without the credit card user having to specify a payment account when using the credit card. The user does not have to specify a payment account when using the credit card, and the payment account is automatically determined according to the manner of use of the credit card, improving convenience for the credit card user.

[0051] Furthermore, in the credit card server 10, the acquisition unit 112 acquires sorting information related to sorting of a household account book application used by a credit card user. The classification unit 113 determines a classification based on the sorting information.

[0052] Since the credit card server 10 can classify the usage patterns of the credit card using the classification information of the household account book application, it is possible to link the classification of the classification information with the payment account.

[0053] 2: Variations The present disclosure is not limited to the above-described embodiments. Specific modified embodiments are exemplified below. Two or more embodiments selected from the following examples may be combined.

[0054] 2-1: Variation 1 In the above embodiment, the classification unit 113 classified the usage of the credit card based on the usage information and sorting information acquired by the acquisition unit 112. However, the classification unit 113 may classify the usage of the credit card without using the sorting information. For example, the classification unit 113 may classify the usage of the credit card by using the name of the statement included in the usage information. Specifically, the classification unit 113 extracts keywords from the name of the statement. Furthermore, the classification unit 113 may classify the usage of the credit card into the items corresponding to the extracted keywords based on the relationship information that associates the extracted keywords with the classification items.

[0055] As an example, assume that the acquisition unit 112 acquires usage information shown in the history information database HDB in Fig. 4, in which the card number is "1865453", the usage ID is "005", the payment date and time is "202311101835", the payment amount is "3,000" yen, and the usage details are "G gas". In this case, the classification unit 113 extracts "gas" as a keyword from the name of the usage details, "G gas". Furthermore, the classification unit 113 may classify the usage of the credit card with the card number "1865453" corresponding to the usage ID = "005" into "utility expenses" based on the relationship information that associates "gas" with "utility expenses".

[0056] The above related information is registered in advance in the credit card server 10 by the credit card user using the user device 20. The registered related information is stored in the storage device 12.

[0057] The credit card server 10 according to the first modification can classify the manner of credit card usage by extracting keywords from the credit card statement, and can therefore automatically determine the payment account according to the statement.

[0058] 2-2: Variation 2 Furthermore, the classification unit 113 may classify the usage manner of the credit card by using the payment amount indicated by the usage information. For example, if the payment amount is less than 2,000 yen, the classification unit 113 classifies the usage manner of the credit card into "category A". If the payment amount is 2,000 yen or more and less than 10,000 yen, the classification unit 113 classifies the usage manner of the credit card into "category B". If the payment amount is 10,000 yen or more and less than 100,000 yen, the classification unit 113 classifies the usage manner of the credit card into "category C". If the payment amount is 100,000 yen or more, the classification unit 113 classifies the usage manner of the credit card into "category D".

[0059] As an example, assume that the acquisition unit 112 acquires usage information in which the card number is "1865453", the usage ID is "005", the payment date and time is "202311101835", the payment amount is "3,000" yen, and the usage details are "G Gas", as shown in the history information database HDB in Fig. 4. In this case, the classification unit 113 classifies the credit card usage into "Category B" based on the fact that the payment amount is "3,000" yen.

[0060] The determination unit 114 determines one of the multiple payment accounts linked to the credit card based on the classification result of the classification unit 113. Fig. 7 is a table showing an example of the configuration of the payment account information database PDB in this modified example. As an example, if the classification unit 113 classifies the usage of the credit card with card number "1865453" corresponding to the usage ID "005" into "category B" as described above, the determination unit 114 refers to the payment account information database PDB and determines that the account with account ID="009", which is the account linked to "category B", is the payment account out of the two accounts with account ID="008" and account ID="009" linked to the card number "1865453".

[0061] In credit card server 10 according to the second modification, the payment account is determined according to the payment amount, so that the credit card user can use different payment accounts for low and high payments.

[0062] 2-3: Variation 3 Furthermore, the classification unit 113 may classify the usage patterns of credit cards by using the payment dates indicated by the usage information. For example, the classification unit 113 classifies the usage patterns of credit cards whose payment dates fall between the 1st and 10th of each month into "Category A." The classification unit 113 also classifies the usage patterns of credit cards whose payment dates fall between the 11th and 20th of each month into "Category B." The classification unit 113 also classifies the usage patterns of credit cards whose payment dates fall between the 21st and 31st of each month into "Category C."

[0063] As an example, assume that the acquisition unit 112 acquires usage information shown in the history information database HDB in Fig. 4, in which the card number is "1865453", the usage ID is "005", the payment date and time is "202311101835", i.e., 18:35 on November 10, 2023, the payment amount is "3,000" yen, and the usage details are "G Gas". In this case, the classification unit 113 classifies the usage mode of the credit card into "Classification A" based on the fact that the payment date is November 10, 2023.

[0064] The determination unit 114 determines one of a plurality of payment accounts linked to a credit card based on the classification result of the classification unit 113. As an example, if the classification unit 113 classifies the usage of the credit card with card number "1865453" corresponding to the usage ID "005" into "Category A" as described above, the determination unit 114 refers to the payment account information database PDB to determine that the account with account ID="008", which is the account linked to "Category A", is the payment account out of two accounts with account ID="008" and account ID="009" linked to the card number "1865453".

[0065] In credit card server 10 according to the third modification, the payment account is determined based on the payment date, so that the credit card user can know the credit card payment amount for each payment account during the month.

[0066] 2-4: Variation 4 The usage information may also include the payment method of the credit card. In this case, the classification unit 113 may classify the usage manner of the credit card based on the payment method.

[0067] For example, the usage information may include information indicating each of the payment methods, ie, touch payment, QR code payment, and electronic money payment, as the payment method of the credit card. Note that "QR code" is a registered trademark. When using any of the payment methods to pay for the purchase price of a product or service, the card number of the credit card registered in association with each payment method is used. The classification unit 113 may classify the usage manner of the credit card associated with the payment method based on the payment method.

[0068] For example, classification unit 113 classifies the manner of use of a credit card when the payment method is touch payment into "category A." Classification unit 113 also classifies the manner of use of a credit card when the payment method is QR code payment into "category B." Furthermore, classification unit 113 classifies the manner of use of a credit card when the payment method is electronic money payment into "category C."

[0069] As an example, assume that the usage information with the usage ID "005" shown in the history information database HDB in Fig. 4 further includes information indicating that the payment method is "electronic money payment." In this case, the classification unit 113 classifies the usage of the credit card into "Category C" based on the fact that the payment method is "electronic money payment."

[0070] The determination unit 114 determines one of a plurality of payment accounts linked to a credit card based on the classification result of the classification unit 113. As an example, if the classification unit 113 classifies the usage of the credit card with card number "1865453" corresponding to the usage ID "005" into "Category C" as described above, the determination unit 114 refers to the payment account information database PDB to determine that the account with account ID="008", which is the account linked to "Category C", is the payment account out of two accounts with account ID="008" and account ID="009" linked to the card number "1865453".

[0071] In credit card server 10 according to the fourth modification, the payment account is determined based on the payment method, so that the credit card user can know the payment amount for each payment method and each payment account.

[0072] 2-5: Variation 5 In addition, if the credit card includes a principal card owned by the owner of the credit card and a family card owned by the owner's family, the usage information may include card type information indicating whether the usage is of the principal card or the family card. In this case, the classification unit 113 may classify the usage manner of the credit card based on the card type information.

[0073] For example, the classification unit 113 classifies the usage of a credit card when the card is used as a principal card into "Category A." Also, the classification unit 113 classifies the usage of a credit card when the card is used as a family card into "Category B."

[0074] As an example, assume that the usage information with the usage ID "005" shown in the history information database HDB in Fig. 4 further includes card type information indicating that the card is a family card. In this case, the classification unit 113 classifies the credit card usage into "Category B" based on the fact that the card is a readable card.

[0075] The determination unit 114 determines one of the multiple payment accounts linked to the credit card based on the classification result of the classification unit 113. As an example, if the classification unit 113 classifies the usage of the credit card with card number "1865453" corresponding to the usage ID "005" into "Category B" as described above, the determination unit 114 refers to the payment account information database PDB and determines that the account with account ID="009", which is the account linked to "Category B", is the payment account out of the two accounts with account ID="008" and account ID="009" linked to the card number "1865453".

[0076] In the credit card server 10 according to the fifth modification, the payment account is determined based on the card type, so that the credit card owner can grasp the payment amounts for himself and his family members by payment account.

[0077] 2-6: Variation 6 In the above embodiment, the acquisition unit 112 acquires usage information from the store servers SP1 to SP4. The acquisition unit 112 also acquires sorting information from the user device 20. In addition to the usage information and sorting information, the acquisition unit 112 may acquire account information indicating at least one of deposits, withdrawals, and balances for each of a plurality of payment accounts linked to the credit card from the bank servers BS1 to BS4. Here, the account information indicating a deposit includes information indicating the amount of the deposit and the date and time of the deposit. The information indicating a withdrawal includes information indicating the amount of the withdrawal and the date and time of the withdrawal. The information indicating the balance includes information indicating the balance of the payment account at the time immediately before the bank servers BS1 to BS4 transmit the account information to the credit card server 10.

[0078] In this case, the determination unit 114 determines one payment account based on the classification result of the classification unit 113 and the account information of multiple accounts. For example, if the classification unit 113 classifies the usage of a credit card with card number "1865453" corresponding to the usage ID "005" into "Category B", but the balance of an account with account ID="009", which is an account linked to "Category B", is predicted to be short of the payment amount of "3,000" on the settlement date, the determination unit 114 determines the account with account ID="008" as the payment account, which is predicted to have a positive balance even if settlement is made on the settlement date.

[0079] Here, the determination unit 114 may determine the account with account ID="008" as the payment account based on the fact that the balance of account ID="008" has never fallen below 30,000 yen in the past year. Alternatively, the determination unit 114 may determine the account with account ID="008" as the payment account based on the fact that, in the past year, the account with account ID="008" has always received a deposit of 100,000 yen on the 15th of every month, while the withdrawal in a month has never exceeded 10,000 yen.

[0080] In credit card server 10 according to modification 6, the payment account is determined based on the classification result of classification section 113 and the account information acquired by acquisition section 112, so that it is possible to prevent a balance shortage.

[0081] 3:Other (1) In the above-described embodiment, the storage device 12 and the storage device 22 are exemplified by ROM and RAM, but the storage device 12 and the storage device 22 may be a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory device (e.g., a card, a stick, a key drive), a CD-ROM (Compact Disc-ROM), a register, a removable disk, a hard disk, a floppy (registered trademark) disk, a magnetic strip, a database, a server, or any other suitable storage medium. The program may also be transmitted from a network via a telecommunication line. The program may also be transmitted from a communication network via a telecommunication line.

[0082] (2) In the above-described embodiments, the described information, signals, etc. may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0083] (3) In the above-described embodiment, the input / output information, etc. may be stored in a specific location (e.g., memory) or may be managed using a management table. The input / output information, etc. may be overwritten, updated, or added. The output information, etc. may be deleted. The input information, etc. may be transmitted to another device.

[0084] (4) In the above-described embodiments, the determination may be made based on a value represented using one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0085] (5) The order of the process steps, sequences, flow charts, etc. illustrated in the above-described embodiments may be changed without causing any inconsistency. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0086] (6) Each function illustrated in Figures 1 to 6 is realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device that is physically or logically combined, or may be realized by using two or more devices that are physically or logically separated and directly or indirectly connected (for example, by wire, wirelessly, etc.). The functional block may be realized by combining the one device or the multiple devices with software.

[0087] (7) The programs exemplified in the above-described embodiments should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., regardless of whether they are called software, firmware, middleware, microcode, hardware description language, or by other names.

[0088] Additionally, software, instructions, information, etc. may be transmitted or received over a transmission medium. For example, if the software is transmitted from a website, server, or other remote source using wired and / or wireless technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave, etc.), then these wired and / or wireless technologies are included within the definition of transmission media.

[0089] (8) In each of the above embodiments, the terms “system” and “network” are used interchangeably.

[0090] (9) The information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or corresponding other information.

[0091] (10) In the above-described embodiments, the user equipment 20 may be a mobile station (MS). A mobile station may be referred to by those skilled in the art as a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In this disclosure, the terms "mobile station", "user terminal", "user equipment (UE)", "terminal", etc. may be used interchangeably.

[0092] (11) In the above-mentioned embodiments, the terms "connected" and "coupled" or any variation thereof refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be a physical coupling or connection, a logical coupling or connection, or a combination thereof. For example, "connected" may be read with "access". As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and light (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0093] (12) In the above embodiments, the phrase "based on" does not mean "based only on," unless otherwise specified. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0094] (13) The terms "determining" and "determining" as used in this disclosure may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), and the like. In addition, "judgment" and "decision" can include considering resolving, selecting, choosing, establishing, comparing, etc., to be a "judgment" or "decision." In other words, "judgment" and "decision" can include considering some action to be a "judgment" or "decision." In addition, "judgment" can be interpreted as "assuming," "expecting," "considering," etc.

[0095] (14) In the above embodiments, when "include," "including," and variations thereof are used, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, the term "or" used in this disclosure is not intended to be an exclusive or.

[0096] (15) In this disclosure, where articles have been added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural.

[0097] (16) In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combined" may also be interpreted in the same way as "different."

[0098] (17) Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched according to execution. In addition, notification of specific information (e.g., notification that "X is the case") is not limited to explicit notification, but may be implicit (e.g., not notifying the specific information).

[0099] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented as modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is for illustrative purposes only and does not have any limiting meaning on the present disclosure. [Explanation of symbols]

[0100] 1...credit card management system, 10...credit card server, 11...processing device, 12...storage device, 13...communication device, 14...display device, 15...input device, 20...user device, 21...processing device, 22...storage device, 23...communication device, 24...display device, 25...input device, 111...management unit, 112...acquisition unit, 113...classification unit, 114...decision unit, 115...settlement unit, A, B, C, D...classification, BS, BS1, BS2, BS3, BS4...bank server, HDB...history information database, NET: communication network, PDB...payment account information database, PR1, PR2...control program, SP1, SP2, SP3, SP4...store server

Claims

1. a management unit that manages credit card numbers in association with a plurality of payment accounts; an acquisition unit that acquires usage information regarding the use of the credit card, the usage information including a payment amount associated with the use of the credit card and the card number; a classification unit that classifies the manner of use of the credit card based on the usage information; a determination unit that determines one of a plurality of payment accounts linked to the credit card based on a classification result of the classification unit; a payment unit that generates payment information for debiting the payment amount from the one payment account; A credit card management device comprising:

2. The acquisition unit acquires sorting information related to sorting of a household account book application used by a user of the credit card, The sorting unit determines the classification based on the sorting information.

2. The credit card management device according to claim 1.

3. The usage information includes the name of the usage statement, the classification unit extracts keywords from the name of the usage details, and determines a classification corresponding to the extracted keywords based on relationship information that associates the keywords with the classifications.

2. The credit card management device according to claim 1.

4. 2. The credit card management device according to claim 1, wherein the classification unit classifies the manner of use of the credit card based on a payment amount indicated by the usage information.

5. the usage information includes information indicating a payment date of the credit card; The classification unit determines a classification based on the payment date.

2. The credit card management device according to claim 1.

6. the usage information includes information indicating a payment method of the credit card; The classification unit determines a classification based on the payment method.

2. The credit card management device according to claim 1.

7. The credit card includes a principal card held by the owner of the credit card and a family card held by a family member of the owner, The usage information includes card type information indicating whether the usage is the principal card or the family card, The classification unit determines a classification based on the card type information.

2. The credit card management device according to claim 1.

8. the acquiring unit acquires account information indicating at least one of deposits, withdrawals, and balances for each of a plurality of payment accounts linked to the credit card; The determination unit determines one payment account based on the classification result of the classification unit and account information of the multiple accounts.

2. The credit card management device according to claim 1.

Images