Program, information processing method, and information processing device

Abstract

To provide an information processing method improving convenience for settlement with a credit card.SOLUTION: A processing section 12 generates a second identification number corresponding to a second credit card associated with a first identification number corresponding to a first credit card. The processing section 12 gives time attribute and a credit frame to each of the first identification number and the second identification number. The processing section 12 accepts a request for settlement specifying the first identification number and specifies an identification number corresponding to the time attribute of timing at which the request has been accepted among the first identification number and the second identification number associated with the first identification number. The processing section 12 commands execution of the settlement in the credit frame corresponding to the specified identification number.SELECTED DRAWING: Figure 1

Description

[Technical field]

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

[0002] Currently, payment is made by credit card. A credit limit is set for a credit card for a given period by the card issuing company, etc. The credit card owner can make payments by credit card within the credit limit.

[0003] For example, there has been a proposal for a virtual card system for generating issuance data for a child card, which is a virtual card, associated with a parent card, which is a credit card, and whose set credit limit is within the current remaining available credit of the parent card.

[0004] There has also been a proposal for a card creation device that creates a second card, separate from the first card, which can be used by the card member up to the credit limit, based on the card information, PIN number, and information regarding the available amount of a first card, such as a credit card.

[0005] There has also been a proposal for a post-payment card system that would allow IC (Integrated Circuit) cards, used for payments on public transport such as trains and buses, and in stores, to have child cards for family members in addition to a parent card for the individual.

[0006] Furthermore, there has been proposed a credit limit setting system that transfers the credit card limit from a parent card, which is a source card, to a child card, which is a destination card. [Prior art documents] [Patent documents]

[0007] [Patent Document 1] JP 2014-235567 A [Patent Document 2] JP 2010-277498 A [Patent Document 3] JP 2005-78258 A [Patent Document 4] Japanese Patent Application Publication No. 11-328273 Summary of the Invention [Problem to be solved by the invention]

[0008] One credit limit is set for one credit card. If a user wishes to use a credit card with a different credit limit from the current credit limit, the user must go through a procedure to change the credit limit, which is inconvenient.

[0009] In one aspect, the present invention aims to improve the convenience of payments made by credit card. [Means for solving the problem]

[0010] In one embodiment, a program is provided. The program causes a computer to execute the following process. The computer generates a second identification number corresponding to a second credit card, which is associated with a first identification number corresponding to a first credit card. The computer assigns a time attribute and a credit limit to each of the first identification number and the second identification number. When the computer receives a payment request in which the first identification number is specified, the computer identifies an identification number corresponding to a time attribute at the time the request is received from among the first identification number and the second identification number associated with the first identification number. The computer instructs execution of the payment using the credit limit corresponding to the identified identification number.

[0011] According to another aspect, there is provided an information processing method, and an information processing device having a storage unit and a processing unit. Effect of the Invention

[0012] On the one hand, it can improve the convenience of payments by credit card. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram illustrating an information processing apparatus according to a first embodiment. [Diagram 2] FIG. 11 illustrates an example of an information processing system according to a second embodiment. [Diagram 3] FIG. 2 illustrates an example of hardware of a server device. [Figure 4] FIG. 2 is a diagram illustrating an example of functions of a server device, a peripheral system, and a terminal device. [Diagram 5] FIG. 13 illustrates an example of a card application information table. [Figure 6] FIG. 13 is a diagram showing an example of a family card application information table. [Figure 7] FIG. 13 is a diagram showing an example of a time division card number table. [Figure 8] FIG. 11 illustrates an example of a time management master. [Figure 9] FIG. 13 illustrates an example of day of the week management master. [Figure 10] FIG. 13 is a diagram illustrating an example of a card payment information table. [Figure 11] FIG. 13 is a diagram illustrating an example of a credit limit management table. [Figure 12] FIG. 13 is a diagram showing an example of screen transitions when creating a family card. [Figure 13] FIG. 13 shows an example of screen transitions (continuation) for creating a family card. [Figure 14] FIG. 13 is a diagram showing an example of screen transitions for confirming family card details. [Figure 15] FIG. 13 is a diagram showing an example of screen transitions for updating a family card. [Figure 16] 13 is a flowchart showing an example of card creation. [Figure 17] 13 is a flowchart showing an example of card payment. [Figure 18] FIG. 11 is a sequence diagram showing the flow of creating a family card. [Figure 19] FIG. 13 is a sequence diagram showing the flow of updating a family card. [Figure 20]FIG. 11 is a sequence diagram showing the flow of family card registration. [Figure 21] FIG. 11 is a sequence diagram showing the flow of payment using a family card. [Figure 22] FIG. 11 is a sequence diagram showing a flow of confirming a credit card usage amount. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] This embodiment will be described below. [First embodiment] FIG. 1 is a diagram illustrating an information processing apparatus according to a first embodiment.

[0015] The information processing device 10 manages information on credit cards issued to users and provides a credit card payment service. The information processing device 10 may be operated by, for example, a business that issues credit cards. The information processing device 10 may also be called a computer. A credit card does not have to have a physical substance as a card, and may be issued electronically. An electronic credit card may be called a virtual card.

[0016] The information processing device 10 is connected to a network 20. A terminal device 30 is also connected to the network 20. The terminal device 30 is a client terminal used by a user. The terminal device 30 may be a smartphone, a tablet terminal, or a PC (Personal Computer), etc. The terminal device 30 holds information on a credit card issued to a user who uses the terminal device 30. The credit card information includes a credit card identification number. The credit card identification number is also called a credit card number or a card number. The user can use a credit card payment service provided by the information processing device 10 by operating the terminal device 30.

[0017] The storage unit 11 may be a volatile semiconductor memory such as a random access memory (RAM), or may be a non-volatile storage such as a hard disk drive (HDD) or a flash memory. The processing unit 12 is, for example, a processor such as a central processing unit (CPU), a graphics processing unit (GPU), or a digital signal processor (DSP). However, the processing unit 12 may include an electronic circuit for a specific purpose such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA). The processor executes a program stored in a memory such as a RAM (which may be the storage unit 11). A set of multiple processors may be called a "multiprocessor" or simply a "processor."

[0018] The memory unit 11 stores credit card management information 11a. The credit card management information 11a is information indicating the correspondence between the identification number of a credit card, the related identification number, and the time attribute. The related identification number is the identification number of another credit card related to the corresponding credit card.

[0019] The time attribute is a time attribute classified by day of the week, time period, etc. For example, the time attribute may be represented by either one of the day of the week and the time period, or may be represented by a combination of the day of the week and the time period. For example, the time attribute may be represented as "Monday to Friday 9:00 to 17:59", "Monday to Friday 18:00 to 23:59", etc. Note that the time attribute may be further classified by other information such as whether it is a holiday or not, instead of the day of the week and the time period, or in addition to at least one of the day of the week and the time period.

[0020] The memory unit 11 may store credit limit information 11b. The credit limit information 11b is information indicating the correspondence between a credit card identification number and a credit limit available for payments made with the credit card. The credit limit is the upper limit of the amount a user can use for payments made with the credit card in a certain period of time. The credit limit is also referred to as a usage limit or credit limit. The credit limit information 11b may be stored in a memory unit of another information processing device (not shown) that communicates with the information processing device 10.

[0021] The processing unit 12 manages credit cards based on the credit card management information 11a and controls payments in response to payment requests from the terminal device 30. First, the processing unit 12 generates a second identification number corresponding to a second credit card, which is associated with a first identification number corresponding to a first credit card, and stores the second identification number in the memory unit 11. For example, the first identification number is set as the associated identification number in the record of the second identification number in the credit card management information 11a stored in the memory unit 11. The first identification number is set as the associated identification number in the record of the first identification number. Alternatively, the associated identification number may not be set in the record of the first identification number.

[0022] Here, the first credit card corresponds to a credit card registered in the terminal device 30. The first identification number of the first credit card is designated by the user for payment. The second credit card is a card attached to the first credit card. The first identification number may be one that has been created in advance for the user and that has been stored in the memory unit 11. Alternatively, the processing unit 12 may generate the first identification number together with the second identification number.

[0023] For example, the processing unit 12 may generate the first identification number and the second identification number based on a card creation request from the terminal device 30 or another terminal device (not shown). The processing unit 12 may also generate the first identification number and the second identification number by transmitting a generation request for the first identification number and the second identification number to another information processing device (not shown) and acquiring the first identification number and the second identification number from the other information processing device.

[0024] There may be a plurality of second credit cards. That is, the processing unit 12 may generate a plurality of second identification information corresponding to a plurality of second credit cards associated with the first identification number. The number of second credit cards is specified by the terminal device 30 according to the number of credit limits that the user wants to use.

[0025] 1 shows an example in which two second identification numbers "X11" and "X12" are generated for a first identification number "X10" of a first credit card issued to a user who uses terminal device 30. In this case, processing unit 12 sets the first identification number "X10" as the related identification number of each record of identification numbers "X11" and "X12" in credit card management information 11a. Processing unit 12 also sets "X10" as the related identification number of the record of first identification number "X10".

[0026] The processing unit 12 assigns a time attribute and a credit limit to each of the first identification number and the second identification number. For example, the processing unit 12 acquires information on the time attribute and the credit limit designated by the user for each second credit card from the terminal device 30 or another terminal device.

[0027] More specifically, the processing unit 12 sets the time attribute "T1" for the second identification number "X11" in the credit card management information 11a. The processing unit 12 sets the credit limit "b" for the second identification number "X11" in the credit limit information 11b.

[0028] Furthermore, the processing unit 12 sets the time attribute "T2" for the second identification number "X12" in the credit card management information 11a. Here, the time attributes "T1" and "T2" are specified as time attributes that do not overlap with each other. The processing unit 12 sets the credit limit "c" for the second identification number "X12" in the credit limit information 11b.

[0029] Furthermore, the processing unit 12 sets the time attribute "other than T1, T2" for the first identification number "X10" in the credit card management information 11a. The time attribute "other than T1, T2" indicates a time attribute that does not belong to either the time attributes "T1" or "T2". The processing unit 12 sets the credit limit "a" for the first identification number "X10" in the credit limit information 11b.

[0030] Here, the sum of the credit limits "a", "b", and "c" is the total credit limit for the user who uses the terminal device 30. For example, a parent of the user who uses the terminal device 30 may apply to the information processing device 10 for the creation of a first credit card as a family card of the parent's credit card. In this case, the processing unit 12 may allocate a part of the credit limit of the parent's credit card as the total credit limit for the user (child) who uses the terminal device 30. For example, the processing unit 12 may accept the applicant's designation of the transfer credit limit to be transferred from the parent's credit card, the set of time period "T1" and credit limit "b", and the set of time period "T2" and credit limit "c". For example, b + c < the transfer credit limit. In this case, the processing unit 12 may set the amount obtained by subtracting the credit limits "b" and "c" from the transfer credit limit as the credit limit "a".

[0031] The processing unit 12 transmits the first identification number "X10" of the first credit card to the terminal device 30. If the source of the card creation request is a terminal device other than the terminal device 30, the processing unit 12 may provide the first identification number "X10" to the terminal device 30 via the other terminal device.

[0032] The terminal device 30 executes, for example, a Wallet application, and manages information related to the first credit card, including the first identification number "X10", through the Wallet application. The processing unit 12 does not need to transmit the second identification numbers "X11" and "X12" of the second credit card to the terminal device 30. In addition, when the first identification number is generated together with the second identification number, a physical credit card may be issued as the first credit card. In that case, the issued credit card is sent to the user of the terminal device 30 by the issuing business operator.

[0033] The terminal device 30 transmits a request for payment by the first credit card to the information processing device 10. The request for payment includes the designation of the first identification number. The processing unit 12 accepts a payment request in which a first identification number is specified. For example, the processing unit 12 accepts a payment request in which a first identification number "X10" is specified. The processing unit 12 may accept the payment request from the terminal device 30. Alternatively, the processing unit 12 may accept the payment request from a server computer that provides an EC (Electronic Commerce) site or the like. For example, when a physical credit card is issued to a user as the first credit card, the user may use a payment service by inputting the first identification number written on the credit card into a screen provided by the EC site.

[0034] The processing unit 12 identifies the identification number from the first identification number and the second identification number that corresponds to the time attribute of the timing at which the request is accepted. For example, assume that the timing at which the payment request designated by the first identification number "X10" is accepted is time t. Also assume that time t belongs to the time attribute "T1".

[0035] In this case, first, the processing unit 12 identifies the record of the identification number "X10" and the records of the identification numbers "X11" and "X12" that have the identification number "X10" as an associated identification number based on the credit card management information 11a. The processing unit 12 identifies the identification number "X11" that corresponds to the time attribute "T1" based on the identified records.

[0036] Then, the processing unit 12 instructs execution of a settlement using the credit limit corresponding to the identified identification number. For example, in response to the instruction to execute a settlement, the processing unit 12 may determine the credit limit "b" corresponding to the identified identification number "X11" based on the credit limit information 11b, and execute a settlement based on the credit limit "b". In a settlement based on the credit limit "b", it is checked whether the usage amount of the second credit card of the identification number "X11" has reached the credit limit "b".

[0037] Alternatively, an information processing device other than the information processing device 10 may execute the payment. In that case, the other information processing device may hold the credit limit information 11b. In response to a payment request specifying the identification number "X10", the processing unit 12 may transmit a payment execution instruction specifying the identification number "X11" to the other information processing device, and cause the other information processing device to determine the credit limit "b" based on the credit limit information 11b and execute the payment.

[0038] In the above example, if the timing at which the payment request with the first identification number "X10" is received belongs to the time attribute "T2", a payment instruction is made based on the credit limit "c" corresponding to the identification number "X12". If the timing at which the payment request with the first identification number "X10" is received does not belong to either the time attributes "T1" or "T2", a payment instruction is made based on the credit limit "a" corresponding to the identification number "X10".

[0039] As described above, according to the information processing device 10, a second identification number corresponding to a second credit card is generated, which is associated with a first identification number corresponding to a first credit card. A time attribute and a credit limit are assigned to each of the first identification number and the second identification number. When a payment request specifying a first identification number is accepted, an identification number corresponding to the time attribute at the time of accepting the request is identified from among the first identification number and the second identification number associated with the first identification number. An instruction is given to execute the payment using the credit limit corresponding to the identified identification number.

[0040] This allows the information processing device 10 to improve the convenience of credit card payments. For example, a user can use different credit limits depending on the time of day when credit card payments are made, without having to carry out a procedure to change the credit limit of the credit card he or she owns.

[0041] Here, the procedure for changing the credit limit that the user performs with the credit card issuer is performed periodically, such as monthly, and takes time. On the other hand, the information processing device 10 can eliminate the procedure for changing the credit limit, and therefore can instantly switch the credit limit used for payment.

[0042] In addition, even if the credit limit is stored in a data structure equivalent to the credit limit information 11b in an existing system, the information processing device 10 does not need to change the data structure of the credit limit information 11b by using the credit card management information 11a. Therefore, the information processing device 10 can easily realize the function of using different credit limits depending on the time period.

[0043] [Second embodiment] FIG. 2 illustrates an example of an information processing system according to the second embodiment. The information processing system 50 is a computer system that provides a payment service by credit card. The information processing system 50 is operated by a business operator that provides the payment service. The information processing system 50 has a server device 100 and a peripheral system 200. The information processing system 50 is connected to the Internet 60. Terminal devices 300, 400 are connected to the Internet 60. The server device 100 and the peripheral system 200 are connected to a LAN (Local Area Network) of the information processing system 50, and are connected to the Internet 60 via the LAN.

[0044] The server device 100 is a server computer that manages credit cards. The server device 100 controls the issuance of credit cards to users and the execution of payments using credit cards. The server device 100 is an example of the information processing device 10 of the first embodiment.

[0045] The peripheral system 200 is a subsystem of the information processing system 50 that manages credit card credit limits and executes credit card settlements in cooperation with the server device 100. The peripheral system 200 may be realized by one server computer or by multiple server computers. As will be described later, the server device 100 and the peripheral system 200 may be realized by one server computer or one information processing device.

[0046] Terminal device 300 is a client computer used by user A. Terminal device 400 is a client computer used by user B. Terminal devices 300 and 400 may be a smartphone, a tablet device, a PC, or the like. Here, user A is assumed to be the parent of user B. In other words, user B is assumed to be the child of user A.

[0047] Upon application from user A, server device 100 provides a service of issuing a credit card for user B as a family card of a credit card owned by user A. User A's credit card is called a parent card. User B's credit card is called a child card. A credit card does not have to have a physical entity. A credit card may be a virtual card.

[0048] FIG. 3 is a diagram illustrating an example of hardware of the server device. The server device 100 has a processor 101, a RAM 102, a HDD 103, a GPU 104, an input interface 105, a medium reader 106, and a communication interface 107. These units of the server device 100 are connected to a bus inside the server device 100. The processor 101 corresponds to the processing unit 12 in the first embodiment. The RAM 102 or the HDD 103 corresponds to the storage unit 11 in the first embodiment.

[0049] The processor 101 is an arithmetic device that executes program instructions. The processor 101 is, for example, a CPU. The processor 101 loads at least a part of the program and data stored in the HDD 103 into the RAM 102 and executes the program. The processor 101 may include multiple processor cores. The server device 100 may also have multiple processors. The processes described below may be executed in parallel using multiple processors or processor cores. A set of multiple processors may also be called a "multiprocessor" or simply a "processor."

[0050] The RAM 102 is a volatile semiconductor memory that temporarily stores programs executed by the processor 101 and data used in calculations by the processor 101. Note that the server device 100 may include a type of memory other than a RAM, or may include multiple memories.

[0051] The HDD 103 is a non-volatile storage device that stores software programs such as an OS (Operating System), middleware, and application software, as well as data. The server device 100 may include other types of storage devices, such as a flash memory or an SSD (Solid State Drive), or may include multiple non-volatile storage devices.

[0052] The GPU 104 outputs an image to a display 51 connected to the server device 100 in accordance with an instruction from the processor 101. As the display 51, any type of display can be used, such as a CRT (Cathode Ray Tube) display, a liquid crystal display (LCD: Liquid Crystal Display), a plasma display, or an organic EL (OEL: Organic Electro-Luminescence) display.

[0053] The input interface 105 acquires an input signal from an input device 52 connected to the server apparatus 100, and outputs the input signal to the processor 101. As the input device 52, a pointing device such as a mouse, a touch panel, a touch pad, or a trackball, a keyboard, a remote controller, a button switch, or the like can be used. In addition, a plurality of types of input devices may be connected to the server apparatus 100.

[0054] The medium reader 106 is a reading device that reads programs and data recorded on the recording medium 53. For example, a magnetic disk, an optical disk, a magneto-optical disk (MO: Magneto-Optical disk), a semiconductor memory, etc. can be used as the recording medium 53. The magnetic disk includes a flexible disk (FD: Flexible Disk) and a HDD. The optical disk includes a compact disc (CD) and a digital versatile disc (DVD).

[0055] The medium reader 106 copies, for example, the program or data read from the recording medium 53 to another recording medium such as the RAM 102 or the HDD 103. The read program is executed, for example, by the processor 101. Note that the recording medium 53 may be a portable recording medium, and may be used for distributing the program or data. Also, the recording medium 53 and the HDD 103 may be referred to as computer-readable recording media.

[0056] The communication interface 107 is connected to a network 54 and communicates with other information processing devices via the network 54. The network 54 is, for example, a LAN of the information processing system 50 and is connected to the Internet 60. The communication interface 107 may be a wired communication interface connected to a wired communication device such as a switch or a router, or a wireless communication interface connected to a wireless communication device such as a base station or an access point.

[0057] An information processing device such as a server computer that realizes the peripheral system 200 and the terminal devices 300 and 400 are also realized by the same hardware as the server device 100. The terminal devices 300 and 400 further include a camera for reading codes such as two-dimensional codes such as QR (Quick Response, registered trademark) codes or bar codes.

[0058] FIG. 4 is a diagram illustrating an example of functions of the server device, the peripheral system, and the terminal device. The server device 100 has a card information storage unit 110 and a card management unit 120. At least one storage area of ​​the RAM 102 and the HDD 103 is used for the card information storage unit 110. The card management unit 120 is realized by the processor 101 executing a program stored in the RAM 102.

[0059] The peripheral system 200 has a management information storage unit 210, a data linking unit 220, and a payment processing unit 230. The management information storage unit 210 uses storage areas such as a RAM and a HDD of the peripheral system 200. The data linking unit 220 and the payment processing unit 230 are realized by a processor of the peripheral system 200 executing a program stored in the RAM of the peripheral system 200.

[0060] The terminal device 300 has an application processing unit 310. The application processing unit 310 is realized by a program stored in the RAM of the terminal device 300 being executed by the processor of the terminal device 300. The terminal device 400 has an application processing unit 410. The application processing unit 410 is realized by a program stored in the RAM of the terminal device 400 being executed by the processor of the terminal device 400.

[0061] The card information storage unit 110 stores information related to credit cards. The information stored in the card information storage unit 110 includes information indicating the correspondence between a parent card and a child card, and information indicating the correspondence between a first child card and a second child card when a first child card and a second child card are issued as child cards. A plurality of second child cards may be created for a first child card. The information stored in the card information storage unit 110 also includes information indicating time attributes assigned to each of the first child card and the second child card.

[0062] When the card management unit 120 receives a family card creation request from the terminal device 300, it generates information for a child card for user B that corresponds to the credit card (parent card) of user A, and registers the generated child card information in the card information storage unit 110. The card management unit 120 also accepts a designation of a transfer credit limit, which is part of the parent card's credit limit, from the terminal device 300, and performs a process of transferring the transfer credit limit from the parent card to the child card. Specifically, the card management unit 120 subtracts the transfer credit limit from the parent card's credit limit. The card management unit 120 adds the amount allocated to the child card from the transfer credit limit to the child card's credit limit.

[0063] Here, the family card creation request may include information on time attributes and credit limits to be assigned to the first child card and the second child card. The card management unit 120 assigns the time attributes and credit limits specified for each child card to the relevant child card. The card management unit 120 may generate information on multiple child cards for user B and register it in the card management unit 120. The card management unit 120 registers information indicating the credit limits of each child card in the management information storage unit 210.

[0064] The credit limit of each child card is allocated from the transferred credit limit. The sum of the credit limits of each child card is equal to the transferred credit limit. The card number of the first child card is registered in the terminal device 400 via the terminal device 300, for example. The card number of the second child card does not need to be registered in the terminal device 400.

[0065] Furthermore, the card management unit 120 receives a payment request from each of the terminal devices 300 and 400. The payment request includes the card number of the credit card used for the payment. The card management unit 120 instructs the peripheral system 200 to execute the payment based on the card number included in the payment request.

[0066] Here, when card management unit 120 receives a payment request specifying a first child card from terminal device 400, it refers to card information storage unit 110 and identifies the card number of the child card according to the time attribute at the time when the payment request is received. Card management unit 120 instructs peripheral system 200 to execute payment using the card number of the identified child card. Card management unit 120 obtains the execution result of the payment from peripheral system 200 and responds to terminal device 400.

[0067] The management information storage unit 210 stores information on credit limits for each card number and payment history for each card number. Data linking unit 220 performs data linking with server device 100. Specifically, data linking unit 220 stores data acquired from card management unit 120 in management information storage unit 210. In response to a request from card management unit 120, data linking unit 220 responds to card management unit 120 with the data to be stored in management information storage unit 210.

[0068] The payment processing unit 230 receives an instruction to execute a payment from the card management unit 120. The instruction to execute a payment includes the card number to be used for the payment. The payment processing unit 230 obtains the credit limit corresponding to the card number specified in the instruction to execute the payment and the payment history for each card number from the management information storage unit 210, and if the payment amount does not exceed the remaining credit limit, executes the payment and responds to the card management unit 120 with the execution result. The remaining credit limit is the remaining amount of the credit limit for the corresponding card number in the current period. If the payment amount exceeds the remaining credit limit, the payment processing unit 230 responds to the card management unit 120 that the payment cannot be executed.

[0069] The application processing unit 310 manages the parent card registered in the terminal device 300, transmits a payment request using the parent card to the server device 100, and transmits a family card creation request to the server device 100. The application processing unit 310 displays a screen for user A to use a payment service on the display of the terminal device 300. The application processing unit 310 corresponds to a Wallet application that runs on the terminal device 300.

[0070] The application processing unit 410 manages the first child card registered in the terminal device 400, and transmits a payment request using the first child card to the server device 100. The application processing unit 410 displays a screen for user B to use a payment service on the display of the terminal device 400. The application processing unit 410 corresponds to a Wallet application that runs on the terminal device 400.

[0071] The server device 100 may have the functions of the peripheral system 200. That is, the server device 100 may have a management information storage unit 210, a data linking unit 220, and a payment processing unit 230.

[0072] FIG. 5 is a diagram illustrating an example of a card application information table. Card application information table 111 is stored in card information storage unit 110. Card application information table 111 includes items such as application number, name, date of birth, PIN, login ID (IDentifier), login PASS, and card number.

[0073] An application number is registered in the application number field. The application number is a number that identifies a credit card application procedure. The name of the credit card applicant is registered in the name field. The birth date of the credit card applicant is registered in the birth date field. In addition to the name and birth date, information such as the applicant's address and telephone number may be registered in the card application information table 111. The PIN field is registered with the PIN used when using the card. The login ID field is registered with the login ID used to log in to the Wallet app. The login PASS field is registered with the password used to log in to the Wallet app. PASS is an abbreviation for PASSWORD. The card number field is registered with the credit card card number.

[0074] For example, card application information table 111 has a record of application number "2022011301", name "Takken Taro", date of birth "19850101", PIN "XXXX", login ID "YYYY", login PASS "ZZZZ", and card number "9999123412342244". This record corresponds to the parent card owned by user A. In other words, user A is a person identified by personal information such as the name "Takken Taro" and date of birth "19850101" in this record.

[0075] FIG. 6 is a diagram showing an example of a family card application information table. A family card application information table 112 is stored in the card information storage unit 110. The family card application information table 112 includes items such as family number, parent application number, attribute, name, date of birth, login ID, login PASS, and card number.

[0076] In the Family Number field, a family number is registered. The family number is a number that identifies a family and the members of the family. In the Parent Application Number field, a parent application number is registered. The parent application number indicates the application number of the parent card associated with the relevant family card (child card). In the Attribute field, attributes as family members are registered. The attributes are also called family attributes. Family attributes include the person who owns the parent card, husband, wife, son, daughter, father, mother, etc. Attributes such as husband, wife, son, daughter, father, and mother are relationships based on the "person", for example. In the Name field, the name of the user who owns the credit card is registered. In the Date of Birth field, the date of birth of the user is registered. In the Login ID field, a login ID used to log in to the Wallet app is registered. In the Login PASS field, a password used to log in to the Wallet app is registered. PASS is an abbreviation of PASSWORD. The card number field contains the credit card number.

[0077] For example, the family card application information table 112 has a record of the family number "10000," parent application number "2022011301," attribute "person," name "Takken Taro," date of birth "19850101," login ID "YYYY," login pass "ZZZZ," and card number "9999123412342244." This record corresponds to the parent card owned by user A.

[0078] Furthermore, the family card application information table 112 has records for family number "10001," parent application number "2022011301," attribute "son," name "Patent Satoshi," date of birth "20050101," login ID "AAAA," login PASS "BBBB," and card number "9999111122225664." This record corresponds to the first child card owned by user B. In other words, user B is a person identified by personal information such as the name "Patent Satoshi" and date of birth "20050101" in this record.

[0079] Here, the card number of the first child card, "9999111122225664", is associated with the parent card by the parent application number, "2022011301". Specifically, the information of the parent card with the parent application number, "2022011301", corresponds to the record with the application number, "2022011301", in the card application information table 111. Note that the card information in the record with the attribute "Person" in the family card application information table 112 is the same as the card information in the record with the same card number in the card application information table 111.

[0080] FIG. 7 is a diagram showing an example of a time division card number table. The time-sharing card number table 113 is stored in the card information storage unit 110. The time-sharing card number table 113 includes items of card number, linked card number, day of the week, and time.

[0081] In the card number field, a card number is registered. In the linked card number field, a linked card number is registered. The linked card number is the card number of the first child card associated with the second child card. If the card number in question is the first child card, the linked card number is the card number of the first child card. In the day of the week field, a code value representing the day of the week is registered. In the time field, a code value representing the time is registered. In the example of the second embodiment, a time attribute is represented by a combination of the day of the week and the time.

[0082] For example, the time division card number table 113 has records of the card number “9999111122225664”, the linked card number “9999111122225664”, the day of the week “-”, and the time “-.” The credit card with the card number “9999111122225664” corresponds to the first child card of user B.

[0083] A hyphen symbol "-" on the first child card indicates that the corresponding item is not set. The time attribute of the first child card is assigned a day of the week and a time that do not belong to the days of the week and times specified on each second child card.

[0084] Furthermore, the time division card number table 113 has records of card number “9999111122225665”, linked card number “9999111122225664”, day of the week “2 (Saturday and Sunday)”, and time “1 (daytime)”. The credit card with card number “9999111122225665” corresponds to the first second child card of user B.

[0085] Furthermore, the time division card number table 113 has records of card number “9999111122225666”, linked card number “9999111122225664”, day of the week “2 (Saturday and Sunday)”, and time “2 (nighttime)”. The credit card with card number “9999111122225666” corresponds to user B’s second child card.

[0086] Furthermore, the time division card number table 113 has records of card number “9999111122225667”, linked card number “9999111122225664”, day of the week “1 (weekday)”, and time “2 (nighttime).” The credit card with card number “9999111122225667” corresponds to user B’s third child card.

[0087] In this way, the card number of the second child card is associated with the card number of the first child card by the setting value of the linked card number item in the time division card number table 113. In addition, the time division card number table 113 manages multiple child cards created for user B according to time periods.

[0088] In the above example, the first child card with card number "9999111122225664" is associated with a set of days of the week and times that are not included in the sets of days of the week and times that correspond to the three second child cards. That is, the set of day of the week "1 (weekday)" and time "2 (daytime)" is associated with the first child card. In this way, when assigning a time attribute to the first child card, it is not necessary to explicitly set a time attribute for the card number of the first child card, and it is sufficient to hold information that can identify the time attribute of the first child card, as exemplified by the time division card number table 113.

[0089] The card information storage unit 110 may store information indicating a card name set by the user for each card number in association with the card number. 7, for ease of understanding, "Saturdays and Sundays" and "Daytime" are listed as setting examples for items such as day of the week and time, but code values ​​such as "1" and "2" may be registered for these items. The meaning of each code value is defined by the time management master and day of the week management master shown below.

[0090] FIG. 8 is a diagram illustrating an example of the time management master. The time management master 114 is stored in the card information storage unit 110. The time management master 114 includes items such as a code value, a name, a start time, and an end time.

[0091] The code value field stores a code value that can be set in the time field of the time division card number table 113. The name field stores the name of the time period indicated by the code value. The start time field stores the start time of the time period corresponding to the code value. The end time field stores the end time of the time period corresponding to the code value.

[0092] For example, the time management master 114 has a record with a code value of "1," a name of "daytime," a start time of "9:00," and an end time of "18:59." This record indicates that the time code value "1" indicates "daytime," the start time of the daytime is 9:00, and the end time of the daytime is 18:59.

[0093] Furthermore, the time management master 114 has a record with a code value of "2", a name of "nighttime", a start time of "19:00", and an end time of "23:59". This record indicates that the time code value "2" indicates "nighttime", the start time of the nighttime is 19:00, and the end time of the nighttime is 23:59.

[0094] FIG. 9 is a diagram illustrating an example of the day of the week management master. The day of the week management master 115 is stored in the card information storage unit 110. The day of the week management master 115 includes items of code value, name, and day of the week.

[0095] The code value field is registered with a code value that can be set in the day of the week field of the time division card number table 113. The name field is registered with the name of the day of the week or the group of days of the week indicated by the code value. The day of the week field is registered with the day of the week corresponding to the code value.

[0096] For example, the day of the week management master 115 has a record with a code value of "1", a name of "weekday", and a day of the week of "Monday, Tuesday, Wednesday, Thursday, Friday". This record indicates that the day of the week code value of "1" represents a "weekday", and that weekdays include the five days of the week: Monday, Tuesday, Wednesday, Thursday, and Friday.

[0097] Furthermore, the day of the week management master 115 has a record with a code value of "2", a name of "Saturday / Sunday", and a day of the week of "Saturday, Sunday". This record indicates that the day of the week code value "2" represents "Saturday / Sunday", and that Saturday / Sunday includes two days of the week, Saturday and Sunday.

[0098] In addition to the above-mentioned information, the card information storage unit 110 may store other information such as the expiration date of each credit card in association with the card number of the credit card. The expiration date of the credit card may be stored in the management information storage unit 210 of the peripheral system 200.

[0099] FIG. 10 is a diagram showing an example of a card payment information table. The card payment information table 116 is stored in the card information storage unit 110. The card payment information table 116 is a history of payments recorded by the card management unit 120. The card payment information table 116 includes fields such as application number, family number, amount, and details.

[0100] The application number field contains an application number corresponding to the card number used for payment. The application number corresponds to the application number in card application information table 111. The family number field contains a family number corresponding to the card number used for payment. For example, when the card number of a second child card is used for payment, the family number of the owner of the first child card associated with the second child card is registered in the family number field. The amount field contains the payment amount. The unit of the payment amount is, for example, yen. The details field contains detail data showing the details of the payment usage.

[0101] For example, the card payment information table 116 has a record of application number "2022011301," family number "10000," amount "20000," and details "detailed data D1." This record indicates that a payment of 20,000 yen was made by user A, who corresponds to the combination of application number "2022011301" and family number "10000," through the payment service, and the details of the payment are described in the detailed data D1.

[0102] The card payment information table 116 may further include other information such as the date and time when the payment request was accepted and the date and time when the payment was made. For example, the card management unit 120 can provide the terminal devices 300, 400 with details of credit card usage amounts based on the card payment information table 116. The card management unit 120 can also hold the payment amount for each family member using the card payment information table 116. Therefore, when providing the terminal devices 300, 400 with the usage amounts for each family member, the card management unit 120 can provide the usage amounts without making an inquiry to the peripheral system 200.

[0103] FIG. 11 is a diagram illustrating an example of a credit limit management table. The credit limit management table 211 is stored in the management information storage unit 210. The credit limit management table 211 includes items such as card number, total credit limit, and remaining credit limit.

[0104] The card number is registered in the card number field. The total credit limit field is the total credit limit of the credit card in question, i.e., the original credit limit without the amount used being reduced. The remaining credit limit field is the total credit limit reduced by the amount used being reduced. The total credit limit and remaining credit limit are expressed in units of yen, for example.

[0105] For example, the credit limit management table 211 has a record of card number "9999123412342244", total credit limit "1000000", and remaining credit limit "800000". This record indicates that the total credit limit corresponding to card number "9999123412342244" is 1000000 yen, and the remaining credit limit is 800000 yen. Here, the credit card with card number "9999123412342244" is a parent card owned by user A. When calculating the remaining credit limit of the parent card, the transferred credit limit to the child card is also counted as used.

[0106] Furthermore, the credit limit management table 211 has a record of the card number "9999111122225664", the total credit limit "80000", and the remaining credit limit "80000". This record indicates that the total credit limit corresponding to the card number "9999111122225664" is 80000 yen, and the remaining credit limit is 80000 yen.

[0107] Furthermore, the credit limit management table 211 has records indicating the total credit limit and remaining credit limit corresponding to each of the card numbers "9999111122225665", "9999111122225666", and "9999111122225667".

[0108] The information processing system 50 provides the following screens to the terminal devices 300 and 400. The screens provided by the information processing system 50 are displayed on the terminal devices 300 and 400. First, an example of screen transitions for creating a family card on the terminal device 300 is as follows.

[0109] FIG. 12 shows an example of screen transitions when creating a family card. When the application processing unit 310 is started, the terminal device 300 displays the login screen 320 (step ST10). The login screen 320 has a login ID input field 321, a password input field 322, and a login button 323. The login ID input field 321 is used to input the login ID of user A. The password input field 322 is used to input the login password of user A. The login button 323 is a button for confirming the input contents in the login ID input field 321 and the password input field 322, and logging in to the payment service provided by the information processing system 50.

[0110] When the login button 323 is pressed and login authentication by the server device 100 is successful, the terminal device 300 displays the card management screen 330 (step ST11). The card management screen 330 has a card image 331, a statement display field 332, and a menu list button 333. The card image 331 is an image representing a credit card owned by user A, i.e., a parent card. The statement display field 332 is an area in which the usage statement of the parent card is displayed. The menu list button 333 is a button for displaying a menu list for card management.

[0111] When the menu list button 333 is pressed, the terminal device 300 displays the card management screen 340 (step ST12). The card management screen 340 has an account setting button 341, a payment setting button 342, a campaign information button 343, and a family card creation button 344. The account setting button 341 is a button for proceeding to change the settings of the user A's account in the payment service. The payment setting button 342 is a button for proceeding to change the settings of the payment method in the payment service. The campaign information button 343 is a button for proceeding to a screen that displays campaign information. The family card creation button 344 is a button for proceeding to create a family card.

[0112] When the family card creation button 344 is pressed, the terminal device 300 displays a card creation screen 350 (step ST13). The card creation screen 350 has an add button 351. The add button 351 is a button for proceeding to input information about a new family card. When the add button 351 is pressed, the screen displayed on the terminal device 300 transitions to the screen of the next step ST14.

[0113] FIG. 13 shows a continuation of the screen transition example for creating a family card. When the Add button 351 on the card creation screen 350 is pressed, the terminal device 300 displays the card creation screen 360 (step ST14). The card creation screen 360 has a card image 361, a login ID input field 362, a password input field 363, a transfer credit limit input field 364, a family card detailed setting item input field 365, and a Register button 366.

[0114] Card image 361 is an image representing a newly created family card. Login ID input field 362 is an input field for a login ID used by user B to log in to the payment service. Password input field 363 is an input field for a password used by user B to log in to the payment service.

[0115] The transfer credit limit input field 364 is an input field for the transfer credit limit of the parent card to be transferred to the child card. The family card detailed setting item input field 365 is an input field for detailed setting items of a family card (child card). The family card detailed setting item input field 365 accepts input of detailed setting items for each family card. In an example of the second embodiment, the detailed setting items of the second child card are input. Time attributes that do not correspond to the time attributes specified in the detailed setting items of the second child card are assigned to the first child card. The credit limit of the first child card is the sum of the credit limits specified for the second child card minus the transfer credit limit. The credit limit assigned to the first child card is called the basic credit limit.

[0116] For example, the family card detailed setting item input field 365 has a card name input field 365a1, a credit limit input field 365a2, and a time attribute input field 365a3 for the first family card (family card 1). The card name input field 365a1 is an input field for the card name of the family card. The credit limit input field 365a2 is an input field for the credit limit to be granted to the family card. The time attribute input field 365a3 is an input field for the time attribute to be granted to the family card. As described above, the time attribute is specified by a combination of a day of the week and a time. The time attribute input field 365a3 may be provided with an input form such as a pull-down menu that allows the user to select a name corresponding to a code value of a settable day of the week and time.

[0117] Furthermore, the family card detailed setting item input field 365 has a card name input field 365b1, a credit limit input field 365b2, and a time attribute input field 365b3 for the second family card (family card 2). In this way, the family card detailed setting item input field 365 specifies the credit limit and time attribute to be granted to each family card.

[0118] The register button 366 is a button for confirming the input contents on the card creation screen 360. When the register button 366 is pressed, a family card creation request including the input contents on the card creation screen 360 is sent to the server device 100, and the card management unit 120 creates information on a new child card for the parent card of user A. The server device 100 sends the child card creation result to the terminal device 300.

[0119] When the terminal device 300 receives the child card creation result from the server device 100, it displays a family card list screen 370 (step ST15). The family card list screen 370 has a card image 371, a card name display field 372, and an add button 373.

[0120] Card image 371 is an image of a created child card. Card name display field 372 is a display field for the card name of the child card. If multiple created child cards exist, multiple card images and card names corresponding to the multiple child cards may be displayed on family card list screen 370.

[0121] The ADD button 373 is a button for proceeding to add a new family card. When the ADD button 373 is pressed, the terminal device 300 displays the card creation screen 360. In addition to the above-mentioned input fields, card creation screen 360 may be provided with input fields for, for example, user B's family attributes, name, date of birth, and the like.

[0122] The card management screen 340 in step ST12 may further include a “family card list button.” In this case, when the family card list button is pressed on the card management screen 340, the terminal device 300 displays the family card list screen 370.

[0123] The card number of the first child card created using the card creation screen 360 is registered in the terminal device 400 by a procedure described later. User B can check the usage details linked to the first child card by a screen such as the following displayed on the terminal device 400.

[0124] FIG. 14 shows an example of screen transitions for checking family card details. When the application processing unit 410 is started, the terminal device 400 displays the login screen 420 (step ST20). The login screen 420 has a login ID input field 421, a password input field 422, and a login button 423. The login ID input field 421 is for inputting the login ID of user B. The password input field 422 is for inputting the login password of user B. The login button 423 is a button for confirming the input contents in the login ID input field 421 and the password input field 422, and logging in to the payment service provided by the information processing system 50.

[0125] Here, the login ID and password of user B are the login ID and password entered in login ID input field 362 and password input field 363 on the card creation screen 360 described above and registered in server device 100. User B's login ID is managed in the family card application information table 112 in association with the card number of the first child card.

[0126] When the login button 423 is pressed and login authentication by the server device 100 is successful, the terminal device 400 displays the family WALLET screen 430 (step ST21). The family WALLET screen 430 has a card image 431 and a statement display field 432. The card image 431 is an image representing a credit card owned by user B, i.e., a first child card. The statement display field 432 is an area in which the statement of the use of the payment service by user B is displayed. The statement of the use displayed in the statement display field 432 is both the statement of the use of user B's first child card and the statement of the use of the second child card associated with the first child card.

[0127] For example, the server device 100 can display transaction details in the details display field 432 based on the card payment information table 116. Furthermore, user A can update the settings of the family card (child card) issued to user B using the following screen displayed on terminal device 300.

[0128] FIG. 15 shows an example of screen transitions for updating a family card. The terminal device 300 accepts the selection of a card image 371 by user A on the family card list screen 370 (step ST30). For example, user A can select card image 371 by touching card image 371. Here, it is assumed that card image 371 is an image of a first child card owned by user B.

[0129] When the card image 371 is selected, the terminal device 300 displays the family WALLET screen 380 (step ST31). The family WALLET screen 380 has a card image 381, a details display field 382, ​​and a menu list button 383. The card image 381 is an image representing the first child card. The details display field 382 is an area in which the details of the use of the payment service by user B are displayed. The details displayed in the details display field 382 are, for example, both the details of the use of the first child card of user B and the details of the use of the second child card associated with the first child card. The menu list button 383 is a button for proceeding to display a setting change menu for the relevant family card.

[0130] When the menu list button 383 is pressed, the terminal device 300 displays a family WALLET screen 390 (step ST32). The family WALLET screen 390 has an account setting button 391, a suspension button 392, and a card information button 393. The account setting button 391 is a button for proceeding to change the account settings of user B. The suspension button 392 is a button for suspending the use of a child card owned by user B. The card information button 393 is a button for proceeding to change the settings of the credit limit, time attributes, etc. for the child cards (first child card and second child card) owned by user B.

[0131] Note that card images of both the first child card and the second child card may be displayed on the family card list screen 370. For example, when a card image of the second child card is selected on the family card list screen 370, the terminal device 300 may display a screen displaying the usage details of the second child card and a screen for changing the credit limit and time attributes of the second child card.

[0132] The server device 100 executes the following procedure for multiple child cards. FIG. 16 is a flow chart showing an example of card creation. (S10) The card management unit 120 acquires from the terminal device 300 the setting information for the child card (family card) entered on the card creation screen 360. The setting information for the child card includes information about the account of user B, the transfer credit limit to the child card, and the credit limit and time attributes for each child card. The card management unit 120 registers, from the acquired setting information, information about the account of user B in the family card application information table 112. The card management unit 120 sets the application number of the parent card owned by user A in the card application information table 111 as the parent application number of the record for user B in the family card application information table 112. The card management unit 120 may also add a record of the parent card owned by user A to the family card application information table 112.

[0133] (S11) The card management unit 120 generates information on the first child card and the second child card based on the setting information of the child card acquired from the terminal device 300. For example, the card management unit 120 may generate card numbers of the first child card and the second child card in cooperation with the peripheral system 200. The card management unit 120 also assigns the card number of the second child card for each set of credit limit and time attribute acquired from the terminal device 300. The card management unit 120 assigns the credit limit (=basic credit limit) obtained by subtracting the allocation to the second child card from the transfer credit limit, and a time attribute that does not belong to the time attribute of the second child card, to the first child card. The card management unit 120 registers the card number of the first child card in the record of user B in the family card application information table 112. As a result, the card number of the first child card of user B is associated with the login ID of user B and the card number of the parent card owned by user A.

[0134] (S12) The card management unit 120 registers the card numbers of the first child card and the second child card in the time division card number table 113. In the time division card number table 113, the second child card is associated with the first child card by setting the linked card number. The card management unit 120 registers the credit limit corresponding to each card number of the first child card and the second child card in the credit limit management table 211 via the data linkage unit 220. The credit limit registered here corresponds to the total credit limit in the credit limit management table 211. The card management unit 120 updates the remaining credit limit corresponding to the card number of the parent card to the amount obtained by subtracting the transfer credit limit from the current remaining credit limit via the data linkage unit 220. The card management unit 120 responds with the card creation result to the terminal device 300. Then, the card creation process ends.

[0135] The card number of the first child card created for user B is registered in terminal device 400 via terminal device 300. User B can use the payment service provided by information processing system 50 using terminal device 400 with the card number of user B's first child card.

[0136] Before step S11, the card management unit 120 may determine whether the transfer credit limit exceeds the remaining credit limit of the parent card, and if the transfer credit limit does not exceed the remaining credit limit of the parent card, execute step S12. If the transfer credit limit exceeds the remaining credit limit of the parent card, the card management unit 120 may not proceed to step S12, but may respond to the terminal device 300 that the transfer credit limit does not allow creation of a child card.

[0137] FIG. 17 is a flowchart showing an example of card payment. (S20) Card management unit 120 acquires a payment request from terminal device 400. The payment request includes the card number of the first child card registered in terminal device 400.

[0138] (S21) Card management unit 120 identifies the time attribute of the current time, i.e., the time when the payment request is accepted. For example, card management unit 120 acquires a code value of the time corresponding to the current time based on time management master 114. Card management unit 120 also identifies the current day of the week based on the day to which the current time belongs and the calendar information stored in card information storage unit 110. Then, card management unit 120 acquires a code value of the day of the week corresponding to the current day of the week based on day of the week management master 115.

[0139] (S22) The card management unit 120 identifies the card number of the second child card related to the card number of the first child card based on the time division card number table 113. The card management unit 120 identifies the card number of the first child card and the card number of the second child card that corresponds to the set of the code value of the time and the code value of the day of the week identified in step S21. If there is no card number in the time division card number table 113 that corresponds to the code value of the time and the code value of the day of the week of the current time identified in step S21, the card management unit 120 identifies the card number of the first child card as the card number that corresponds to the time attribute of the current time.

[0140] (S23) The card management unit 120 obtains the credit limit corresponding to the card number of the child card identified in step S22 from the credit limit management table 211 via the data linkage unit 220. For example, the card management unit 120 obtains the remaining credit limit as the credit limit corresponding to the card number.

[0141] (S24) Card management unit 120 performs a card validity check. In the card validity check, card management unit 120 confirms whether or not the current payment amount exceeds the remaining credit amount. Card management unit 120 may also check whether or not the expiration date of the child card used for the payment has passed. For example, if the expiration date has not passed and the current payment amount does not exceed the remaining credit amount, card management unit 120 determines that the child card is valid, and if not, determines that the child card is invalid.

[0142] (S25) Card management unit 120 determines whether the child card in question is valid based on the check result in step S24. If the child card in question is valid, processing proceeds to step S26. If the child card in question is invalid, processing proceeds to step S29.

[0143] (S26) The card management unit 120 specifies the card number identified in step S22 and instructs the payment processing unit 230 to execute the payment. The payment processing unit 230 executes the payment in accordance with the instruction. Specifically, the payment processing unit 230 obtains the credit limit (remaining credit limit) corresponding to the specified card number from the credit limit management table 211, and executes the payment using the credit limit. The payment processing unit 230 updates the credit limit management table 211 so as to deduct the current payment amount from the remaining credit limit of the corresponding card number.

[0144] (S27) Card management unit 120 obtains the execution result of the payment from payment processing unit 230. Card management unit 120 registers a record indicating the execution result of the payment in card payment information table 116.

[0145] (S28) Card management unit 120 responds to terminal device 400 that the payment has been completed. Then, the card payment process ends. (S29) Card management unit 120 responds to terminal device 400 that payment cannot be executed. Then, the card payment process ends.

[0146] As described above, the server device 100 may include the payment processing unit 230. When the server device 100 includes the payment processing unit 230, the payment in step S26 is executed by the server device 100.

[0147] An example of the process flow in the information processing system 50 will be described below. FIG. 18 is a sequence diagram showing the flow of creating a family card. When user A presses the register button 366 on the card creation screen 360, the terminal device 300 executes a family card creation confirmation process 500 based on the information entered on the card creation screen 360. In the family card creation confirmation process 500, the terminal device 300 transmits the login account information and transfer credit limit of user A to the server device 100 (step ST100). The login account information of user A is, for example, the login ID of user A.

[0148] When the server device 100 receives the login account information and the transfer credit limit of the user A from the terminal device 300, it executes the credit limit confirmation process 600. In the credit limit confirmation process 600, the server device 100 transmits the card number of the parent card owned by the user A, i.e., the parent card number, to the peripheral system 200 (step ST101). In this example, the card number (parent card number) of the parent card owned by the user A is "9999123412342244". The server device 100 receives the remaining credit limit corresponding to the parent card number from the peripheral system 200 (step ST102). The server device 100 checks whether the transfer credit limit exceeds the remaining credit limit of the parent card, and if the transfer credit limit does not exceed the remaining credit limit of the parent card, it determines that a family card can be created. On the other hand, if the transfer credit limit exceeds the remaining credit limit of the parent card, the server device 100 determines that the family card cannot be created. The server device 100 responds to the terminal device 300 with the confirmation result of the credit limit confirmation process 600, that is, whether or not the transfer credit limit exceeds the remaining credit limit of the parent card (step ST103).

[0149] The terminal device 300 receives the confirmation result from the server device 100. Here, the confirmation result indicates that the transfer credit limit does not exceed the remaining credit limit of the parent card. Then, the terminal device 300 executes a family card registration process 501. In the family card registration process 501, the terminal device 300 transmits the login account information of the user A and the setting information of the child card input on the card creation screen 360 to the server device 100 (step ST104).

[0150] When the server device 100 receives the login account information of user A and the setting information of the child card from the terminal device 300, it executes a child card number issuance process 601 for each time attribute. The setting information of the child card may include family information such as the family attributes of user B for user A and the name of user B. Based on the information received from the terminal device 300, the server device 100 registers a record of user B in the family card application information table 112.

[0151] In addition, in the child card number issuing process 601 for each time attribute, the server device 100 transmits the parent card number and family information regarding user B to the peripheral system 200 (step ST105). For example, in step ST105, the server device 100 acquires the number of child cards to be newly issued based on the setting information of the child cards, and requests the peripheral system 200 to issue card numbers for the newly issued child cards. In response to the request, the peripheral system 200 issues new card numbers based on the family information of user B. In this example, the card number "9999111122225664" of the first child card and the card numbers "9999111122225665", "9999111122225666", and "9999111122225667" of the three second child cards are issued to user B.

[0152] The server device 100 receives the card number of the child card, i.e., the child card number, from the peripheral system 200 (step ST106). In step ST106, the server device 100 acquires multiple child card numbers corresponding to multiple time attributes. In this way, the server device 100 can generate multiple new child card numbers in cooperation with the peripheral system 200. The server device 100 registers the card number of the first child card among the multiple child card numbers in the record of user B in the family card application information table 112.

[0153] Then, the server device 100 assigns the time attribute specified by the terminal device 300 to each of the received child card numbers. That is, the server device 100 registers the correspondence between the child card numbers and the time attributes in the time-divided card number table 113. At this time, the server device 100 also sets a linked card number that associates the card number of the first child card with the card number of the second child card.

[0154] When the server device 100 receives multiple child card numbers from the peripheral system 200, it executes a credit limit calculation process 602 for each card number. Specifically, the server device 100 assigns the credit limit specified by the terminal device 300 for each time attribute to the card number of the second child card corresponding to the time attribute. The server device 100 also assigns the amount obtained by subtracting the total of the credit limits assigned to the card numbers of the second child cards from the transfer credit limit (=basic credit limit) to the card number of the first child card. The server device 100 also sets the amount obtained by subtracting the transfer credit limit from the remaining credit limit of the parent card as the new remaining credit limit of the parent card. For example, if the remaining credit limit of the parent card is 1,000,000 yen and the transfer credit limit is 200,000 yen, the remaining credit limit of the parent card is 1,000,000-200,000=800,000 yen.

[0155] Then, the server device 100 executes credit limit registration processing 603 for each card number. In credit limit registration processing 603 for each card number, the server device 100 transmits information indicating the credit limit for each card number to the peripheral system 200 (step ST107). More specifically, the server device 100 notifies the peripheral system 200 of the credit limit (total credit limit) for each child card number, and registers it in the credit limit management table 211. When a child card number is newly registered, the remaining credit limit of the child card in the credit limit management table 211 becomes the same amount as the total credit limit. In addition, the server device 100 notifies the peripheral system 200 of the remaining credit limit after the update of the parent card number, and registers it in the credit limit management table 211.

[0156] The server device 100 then receives a response of the registration result of the credit limit for each card number from the peripheral system 200 (step ST108). Furthermore, the server device 100 responds with the registration result of the new family card (child card) to the terminal device 300 (step ST109). The terminal device 300 displays information of the newly created family card on the family card list screen 370.

[0157] FIG. 19 is a sequence diagram showing the flow of updating a family card. When the terminal device 300 acquires the new credit limit or new time attribute of the child card input by the user A on the setting change screen of the family card (child card) transitioned from the family WALLET screen 390, it executes the update content confirmation process 502. In the update content confirmation process 502, the terminal device 300 transmits a confirmation request for the credit limit including the card number of the child card and the new credit limit to the server device 100 (step ST200).

[0158] When the server device 100 receives a credit limit confirmation request from the terminal device 300, it executes a credit limit confirmation process 604. In the credit limit confirmation process 604, the server device 100 transmits a credit limit request for the parent card of user A and the corresponding child card to the peripheral system 200 (step ST201). In response to the credit limit request, the server device 100 receives information indicating the remaining credit limit of the parent card and the credit limit of the corresponding child card (total credit limit in the credit limit management table 211) from the peripheral system 200 (step ST202). Then, the server device 100 compares the remaining credit limit C1 of the parent card received from the peripheral system 200 with the amount C2 of the credit limit to be newly transferred to the corresponding child card, and determines that the new credit limit is appropriate if C1-C2>0. On the other hand, the server device 100 determines that the new credit limit is inappropriate if C1-C2≦0. Here, C2 is calculated, for example, as C2=(new credit limit received from terminal device 300)-(current total credit limit of the child cards). The server device 100 responds to the terminal device 300 with the result of the credit limit confirmation by the credit limit confirmation process 604 (step ST203). Here, it is assumed that the server device 100 responds to the terminal device 300 with the result of the credit limit confirmation that the new credit limit is appropriate.

[0159] When the terminal device 300 receives the confirmation result of the credit limit from the server device 100, it executes a family card information update process 503. In the family card information update process 503, the terminal device 300 transmits an update request to the server device 100 to update the credit limit of the child card with the new credit limit input by user A (step ST204). The update request includes a new time attribute for the child card.

[0160] When the server device 100 receives the update request from the terminal device 300, it executes an update process 605. In the update process 605, the server device 100 sets a new time attribute for the corresponding child card in the time division card number table 113. Also, in the update process 605, the server device 100 adds the above C2 to the credit limit (total credit limit) of the corresponding child card, and updates the credit limit management table 211 of the peripheral system 200 to subtract C2 from the remaining credit limit of the parent card (step ST205). At this time, the server device 100 also updates the remaining credit limit of the corresponding child card by adding C2. The server device 100 receives a response of the credit limit update result from the peripheral system 200 (step ST206).

[0161] Then, the server device 100 responds to the terminal device 300 with the registration result of the new credit limit and time attribute for the child card (step ST207). The terminal device 300 displays, on the display screen of the registration result, that the new credit limit and time attribute have been set for the card.

[0162] The server device 100 sets the time attribute corresponding to the first child card to a time attribute other than the time attribute corresponding to the second child card. Therefore, when the time attribute corresponding to the second child card is changed, the time attribute corresponding to the first child card is also changed to a time attribute that does not overlap with the time attribute of the second child card.

[0163] Here, the card number of the first child card issued to user B is registered in terminal device 400 via terminal device 300 as follows. FIG. 20 is a sequence diagram showing the flow of family card registration.

[0164] In response to an operational instruction from user A, terminal device 300 executes a Wallet addition code acquisition process 504 for registering the card number of the first child card issued to user B in terminal device 400. In the Wallet addition code acquisition process 504, terminal device 300 transmits a code generation request to server device 100 (step ST300).

[0165] When the server device 100 receives the code generation request from the terminal device 300, it executes a Wallet addition code generation process 606. In the Wallet addition code generation process 606, the server device 100 generates a Wallet addition code corresponding to the card number of the first child card based on the family card application information table 112, and responds to the terminal device 300 (step ST301). The Wallet addition code may be a barcode or a two-dimensional code. The two-dimensional code may be, for example, a QR code (registered trademark).

[0166] When the terminal device 300 receives the wallet addition code from the server device 100, it executes a wallet addition code display process 505. Specifically, the server device 100 causes the terminal device 300 to display the wallet addition code on its display.

[0167] Terminal device 400 executes Wallet addition code reading process 700. Specifically, terminal device 400 reads the Wallet addition code displayed on terminal device 300 with the camera of terminal device 400, and obtains code information corresponding to the Wallet addition code. The code information may be the card number of the first child card, or may be a predetermined authentication number generated by server device 100 for the card number of the first child card.

[0168] Then, the terminal device 400 executes a card information addition process 701. In the card information addition process 701, the terminal device 400 transmits a credit card addition request, including the code information acquired by reading the wallet addition code, to the server device 100 (step ST302).

[0169] When the server device 100 receives the addition request from the terminal device 400, the server device 100 performs card validity confirmation processing 607. In the card validity confirmation processing 607, the server device 100 identifies the card number of the first child card based on the code information, and confirms the validity of the first child card, such as the expiration date. Then, when the server device 100 confirms that the first child card is valid, the server device 100 transmits a registration request to the peripheral system 200 indicating that the card number of the first child card is to be registered in the terminal device 400 (step ST303). For example, the peripheral system 200 may hold information indicating the correspondence between the identification information of the terminal device 400 and the card number of the first child card. In response to the registration request, the server device 100 receives a registration response indicating the completion of registration from the peripheral system 200 (step ST304).

[0170] When the server device 100 receives the registration response from the peripheral system 200, the server device 100 transmits a result response indicating that the registration on the server side has been completed to the terminal device 400 (step ST305). At this time, the server device 100 may notify the terminal device 400 of the card number of the first child card.

[0171] Terminal device 400 stores the card number of the first child card in a predetermined storage unit. The card number of User B's first child card is "9999111122225664." As a result, the card number of the first child card is registered in the Wallet application of terminal device 400, and payment services using that card number become available.

[0172] FIG. 21 is a sequence diagram showing the flow of payment using a family card. When paying for a product or service on an EC site or the like, user B inputs a payment start command specifying the card number of the first child card to terminal device 400. When terminal device 400 accepts user B's payment start command specifying the card number of the first child card, it executes payment process 703 of the Wallet application. In payment process 703 of the Wallet application, terminal device 400 transmits a payment request specifying card number M to server device 100 (step ST400). Here, card number M is the card number of the first child card registered in terminal device 400, and in this example, M=9999111122225664. The payment request also includes information such as the payment amount.

[0173] When the server device 100 receives a payment request from the terminal device 400, it executes card validity confirmation processing 608. In the card validity confirmation processing 608, the server device 100 identifies the card number N of the child card according to the time attribute of the time when the payment request was received. For example, if the time when the payment request was received is 10:00 on Saturday, the server device 100 identifies N=9999111122225665 based on the time division card number table 113.

[0174] Then, the server device 100 designates the card number N and requests information on the card number N from the peripheral system 200 (step ST401). The server device 100 receives information indicating the remaining credit limit and expiration date corresponding to the card number N from the peripheral system 200 (step ST402). The server device 100 checks the validity of the card based on whether the current time has passed the expiration date of the child card and whether the current payment amount has passed the remaining credit limit.

[0175] If it is confirmed that the card number N is valid, the server device 100 executes a payment instruction process 609. In the payment instruction process 609, the server device 100 transmits payment information including the card number N to the peripheral system 200 (step ST403). The payment information may include the payment amount, information on the store used by user B, and the like. The peripheral system 200 executes a payment process 800 based on the payment information. In the payment process 800, the peripheral system 200 checks whether the store information is correct, and executes the payment using the card number N when the check is normally completed. The peripheral system 200 records the content of the payment in a card payment information registration table in the management information storage unit 210 in association with the card number N. The card payment information registration table is a table that holds the payment execution date and time, the card number, the payment amount, and the statement data in association with each other.

[0176] Then, the server device 100 receives a response of the execution result of the payment from the peripheral system 200 (step ST404). The server device 100 registers the execution result of the payment in the card payment information table 116. The server device 100 transmits the response of the execution result of the payment to the terminal device 400 (step ST405). The terminal device 400 displays the execution result of the payment on the display of the terminal device 400.

[0177] Here, user A can use terminal device 300 to check the amounts used for payments made with the parent card and the child card. FIG. 22 is a sequence diagram showing the flow of confirming the amount used by a credit card.

[0178] When the login button 323 on the login screen 320 is pressed and the login is successful, the terminal device 300 executes a member information display process 506. In the member information display process 506, the terminal device 300 transmits a member information display request to the server device 100 (step ST500). For example, the member information display request may include the login account information of user A.

[0179] When the server device 100 receives a display request from the terminal device 300, it executes information inquiry processing 610. In the information inquiry processing 610, the server device 100 refers to the card information storage unit 110 to identify the card number of the parent card owned by user A and the card numbers of the child cards associated with the parent card by the application number. The card numbers of the child cards may include the card number of the first child card and the card number of the second child card. There may be multiple card numbers for the second child card. The server device 100 transmits a usage amount request specifying each of the identified card numbers to the peripheral system 200 (step ST501).

[0180] The peripheral system 200 responds to the server device 100 with the usage amount for a predetermined period for each specified card number based on the card payment information registration table stored in the management information storage unit 210. The predetermined period is determined in advance, such as the most recent month. The predetermined period may be a period specified by the terminal device 300.

[0181] The server device 100 receives the usage amount for each card number from the peripheral system 200 (step ST502). Then, the server device 100 executes a billing linking process 611. In the billing linking process 611, the server device 100 adds the usage amount of the child card to the usage amount of the parent card to calculate the billing amount for user A.

[0182] For example, suppose the parent card's spending amount is 400,000 yen, the second child card's spending amount corresponding to the time attribute "Saturday and Sunday during the day" is 50,000 yen, the second child card's spending amount corresponding to the time attribute "weekdays at night" is 10,000 yen, and the first child card's spending amount is 100,000 yen. In this case, the billed amount for user A will be 400,000 yen + 50,000 yen + 10,000 yen + 100,000 yen = 560,000 yen.

[0183] The server device 100 responds to the terminal device 300 with display content including the calculated billing amount for user A (step ST503). The terminal device 300 displays the display content including the billing amount received from the server device 100 on the display of the terminal device 300.

[0184] 18 to 22 is executed by the card management unit 120. The processing of the peripheral system 200 in FIGS. 18 to 22 is executed by the data linkage unit 220 and the payment processing unit 230. The processing of the terminal device 300 in FIGS. 18 to 20 and 22 is executed by the application processing unit 310. The processing of the terminal device 400 in FIGS. 20 and 21 is executed by the application processing unit 410.

[0185] In this way, the server device 100 creates a card number of the second child card associated with the card number of the first child card for user B, and assigns a time attribute and a credit limit to each of the card numbers of the first child card and the second child card. Therefore, the server device 100 can use different credit limits for a payment request using the card number of the first child card depending on the time attribute at the time when the payment request is received. This allows the server device 100 to improve the convenience of payments using credit cards.

[0186] In the example of the second embodiment, the server device 100 creates card numbers for the first child card and the second child card for user B, who is a family member of user A. The example is not limited to this example, and the server device 100 may create one or more other card numbers corresponding to the time attribute and credit limit for the parent card owned by user A. In this case, the server device 100 registers the other card numbers and the time attribute in the time-divided card number table 113 by using the card number of the parent card in the card application information table 111 as a linked card number. In addition, the server device 100 registers the credit limit for each of these card numbers in the credit limit management table 211. In this way, the server device 100 can specify a card number corresponding to the time attribute of the timing of the payment request for user A himself, and use different credit limits depending on the card number.

[0187] In the existing credit limit management in credit card payment services, there may be cases where the user wishes to change the credit limit. However, currently there is no support for changing the credit limit according to the user's desired time. For example, after the credit company receives a change request from the user, the credit limit is changed through processing by the credit company (for example, monthly processing).

[0188] As a comparative example, a mechanism for changing the credit limit in real time for a certain credit card number at a user's desired time can be constructed. However, the existing credit management system has a simple configuration because many payments are made every day, and the cost of modifying the data structure for credit limit management is high. For example, there may be an increase in costs such as the cost of modification, the increase in system processing time due to the recovery of the data structure, and the increase in resource consumption due to the increase in processing time. More specifically, if the data structure of the existing credit limit management is a simple structure consisting of columns of key information (card number) and amount (credit limit), the above-mentioned increase in costs may occur if a column of time attributes (day of the week, time) is added to the data structure of the credit limit management.

[0189] Therefore, the server device 100 issues a different card number according to the time and day settings in a manner linked to the original card number, and manages them in the time-divided card number table 113. The server device 100 then makes it possible to use different credit limits for payment based on the time of the payment request and the time-divided card number table 113. This allows the server device 100 to switch the credit limit used for payment depending on the time of day, without requiring modifications to the credit limit management system (e.g., the peripheral system 200) side.

[0190] In addition, the server device 100 can safely issue credit cards (virtual cards) to children because it can control the credit limit according to the time of day. In addition, the server device 100 can vary the credit limit more flexibly than existing credit limit management, so it can allocate the credit limit according to the purpose of use. Furthermore, the server device 100 can give a sense of security to those who do not have a credit card and are concerned about overspending, and can encourage those who do not have a credit card to obtain a new credit card.

[0191] As described above, the server device 100 executes the following process. The card management unit 120 generates a second identification number corresponding to a second credit card, which is associated with a first identification number corresponding to a first credit card. The card management unit 120 assigns a time attribute and a credit limit to each of the first identification number and the second identification number. When the card management unit 120 receives a payment request in which the first identification number is specified, the card management unit 120 identifies an identification number corresponding to the time attribute at the time the request is received from among the first identification number and the second identification number associated with the first identification number. The card management unit 120 instructs execution of the payment using the credit limit corresponding to the identified identification number.

[0192] This allows the server device 100 to improve the convenience of credit card payments. Here, the above-mentioned first child card is an example of a first credit card. The second child card is an example of a second credit card. The card number of the first child card is an example of a first identification number. The card number of the second child card is an example of a second identification number.

[0193] The card management unit 120 may manage the correspondence between the second identification number and the first identification number by generating management information (time-divided card number table 113) that associates the second identification number with the first identification number. Alternatively, the card management unit 120 may make it possible to identify the association between the first identification number and the second identification number by associating the first identification number with the second identification number in the identification number of the credit card itself. For example, the card management unit 120 may make it possible to identify the association between the first identification number and the second identification number by generating the second identification number as a branch number of the first identification number (such as by incrementing the last digit).

[0194] Furthermore, the server device 100 may have a payment processing unit 230. Alternatively, the card management unit 120 may have the function of the payment processing unit 230. For example, in response to an instruction to execute a payment, the card management unit 120 may determine a credit limit corresponding to a specified identification number, and execute the payment based on the determined credit limit.

[0195] This allows the server device 100 to improve the convenience of credit card payments. Also, the card management unit 120 may generate multiple second identification numbers for the first identification number. In this case, the card management unit 120 assigns a time attribute and a credit limit to each of the first identification number and the multiple second identification numbers.

[0196] This allows the server device 100 to use different credit limits depending on detailed time attributes, thereby further improving the convenience of credit card payments. Furthermore, the card management unit 120 may grant a credit limit to each of the first identification number and the second identification number based on the credit limit of a third credit card associated with the first identification number.

[0197] This allows the server device 100 to transfer the credit limits of the first identification number and the second identification number from the credit limit of the third credit card. For example, the server device 100 can generate card numbers of the first credit card and the second credit card as family cards of the third credit card. The parent card owned by the user A mentioned above is an example of the third credit card.

[0198] Furthermore, the card management unit 120 may accept a user's designation of an assigned credit limit, which is the sum of the credit limits of the third credit card granted to the first identification number and the second identification number, and a credit limit of the assigned credit limit, which is to be granted to the second identification number. The card management unit 120 may assign the credit limit designated by the user to the second identification number, and assign to the first identification number a basic credit limit obtained by subtracting the credit limit granted to the second identification number from the assigned credit limit.

[0199] This allows the server device 100 to assist the user in easily specifying the credit limits to be granted to each of the first identification number and the second identification number. Furthermore, the card management unit 120 may accept a user's designation of a time attribute to be assigned to the second identification number. The card management unit 120 may assign the time attribute designated by the user to the second identification number, and assign another time attribute that does not belong to the time attribute designated by the user to the first identification number.

[0200] This allows the server device 100 to assist the user in easily specifying the time attributes to be assigned to each of the first identification number and the second identification number. Furthermore, the card management unit 120 may generate correspondence information indicating the correspondence relationship between the first identification number and the user's identification information. When a payment is made using each of the first identification number and the second identification number, the card management unit 120 may specify the user's identification information corresponding to the first identification number based on the correspondence information. The card management unit 120 may record the amount used in the payment in association with the user's identification information in the payment history information. When the card management unit 120 receives a request to obtain the payment history for the user, it may respond with the amount used corresponding to the user's identification information based on the payment history information.

[0201] This allows the server device 100 to manage credit limits for each credit card identification number, while collectively managing and providing the payment amounts for a user's multiple credit card identification numbers. The family card application information table 112 described above is an example of the above-mentioned correspondence information. The combination of a family number and a parent application number (application number) is an example of a user's identification information. The card payment information table 116 is an example of the above-mentioned payment history information. For example, the user's identification information may be managed in association with the user's account information (login ID and password) in the payment service. In this way, the server device 100 can obtain the identification information of the user who requested the payment history from the account information of the user, and obtain the payment amount corresponding to the identification information from the payment history information.

[0202] The information processing in the first embodiment can be realized by causing the processing unit 12 to execute a program. The information processing in the second embodiment can be realized by causing the processor 101 to execute a program. The program can be recorded in a computer-readable recording medium 53.

[0203] For example, the program can be distributed by distributing recording medium 53 on which the program is recorded. The program may also be stored in another computer and distributed via a network. The computer may store (install) the program recorded in recording medium 53 or a program received from another computer in a storage device such as RAM 102 or HDD 103, and read and execute the program from the storage device. [Explanation of symbols]

[0204] 10. Information processing device 11 Storage section 11a Credit card management information 11b Credit Facility Information 12 Processing section 20 Network 30 Terminal Equipment

Claims

1. On the computer, generating a second identification number corresponding to a second credit card that is associated with the first identification number corresponding to the first credit card; assigning a time attribute and a credit limit to each of the first identification number and the second identification number; When a payment request specifying the first identification number is received, an identification number corresponding to the time attribute at the time the request is received is identified from among the first identification number and the second identification number associated with the first identification number; instructing execution of the settlement using the credit line corresponding to the identified identification number; A program that executes a process.

2. in response to an instruction to execute the settlement, determining the credit limit corresponding to the specified identification number, and executing the settlement based on the determined credit limit; The program according to claim 1, which causes the computer to execute a process.

3. In the generation of the second identification number, a plurality of the second identification numbers are generated for the first identification number; In assigning the time attribute and the credit limit, the time attribute and the credit limit are assigned to the first identification number and each of the plurality of second identification numbers. The program according to claim 1, which causes the computer to execute a process.

4. the granting of the credit limit includes granting the credit limit to each of the first identification number and the second identification number based on the credit limit of a third credit card associated with the first identification number; The program according to claim 1, which causes the computer to execute a process.

5. accepting a user's designation of an assigned credit limit, which is the sum of the credit limits of the third credit card that are assigned to the first identification number and the second identification number, and a credit limit of the assigned credit limit that is assigned to the second identification number; granting the credit limit designated by the user to the second identification number, and granting a basic credit limit obtained by subtracting the credit limit granted to the second identification number from the transferred credit limit to the first identification number; 5. The program according to claim 4, which causes the computer to execute a process.

6. accepting a user's designation of the time attribute to be assigned to the second identification number; assigning the time attribute designated by the user to the second identification number, and assigning another time attribute not belonging to the time attribute designated by the user to the first identification number; The program according to claim 1, which causes the computer to execute a process.

7. generating correspondence information indicating a correspondence relationship between the first identification number and user identification information; When the payment is executed using the first identification number and the second identification number, the identification information of the user corresponding to the first identification number is identified based on the correspondence information, and an amount used in the payment is recorded in payment history information in association with the identification information; when a request for acquiring the history of the payment for the user is received, the transaction amount corresponding to the identification information of the user is responded to based on the payment history information; The program according to claim 1, which causes the computer to execute a process.

8. The computer generating a second identification number corresponding to a second credit card that is associated with the first identification number corresponding to the first credit card; assigning a time attribute and a credit limit to each of the first identification number and the second identification number; When a payment request specifying the first identification number is received, an identification number corresponding to the time attribute at the time the request is received is identified from among the first identification number and the second identification number associated with the first identification number; instructing execution of the settlement using the credit line corresponding to the identified identification number; Information processing methods.

9. a memory unit for storing an identification number corresponding to a credit card; a processing unit that generates a second identification number corresponding to a second credit card, which is associated with a first identification number corresponding to a first credit card, and stores the second identification number in the storage unit, and assigns a time attribute and a credit limit to each of the first identification number and the second identification number, and when a payment request specifying the first identification number is received, identifies, from among the first identification number and the second identification number associated with the first identification number, the identification number that corresponds to the time attribute at the time when the request is received, and instructs execution of the payment using the credit limit corresponding to the identified identification number; An information processing device having the above configuration.

Images