JP7655839B2 - PROGRAM, INFORMATION PROCESSING APPARATUS AND METHOD - Google Patents

Description

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

Payment by credit card is becoming more common when purchasing goods or receiving services at stores. As a result, the number of stores that allow payment by credit card is also increasing.

As a technology for notifying the user of credit card usage in such credit card payments, Patent Document 1 discloses a technology for a card limit setting system that notifies the user's terminal of credit card usage by email. This limit setting system is a system that notifies the user of the approved amount by email when the credit card usage is approved.

JP 2008-276499 A

In recent years, there has been an increase in the issuance of credit cards to corporations under the name of business cards or the like. Such credit cards are issued in the name of an individual, such as the representative of the corporation, and are issued, for example, for the number of employees authorized to use the card within the corporation. There is a demand for a simple process to grasp the usage status of such corporate credit cards and register it as accounting information.

Therefore, this disclosure describes a technology that makes it possible to easily grasp the usage status of, for example, corporate credit cards by employees and register the information as accounting information.

According to one embodiment of the present disclosure, a program is provided for managing credit card usage when executed by a computer having a processor and memory. The memory stores information linked to the person to whom the credit card is to be issued, including information on a person authorized to view credit card usage and information on a person authorized to manage credit card usage. The program causes the processor to execute the following steps: accepting authorization information requesting payment by credit card; acquiring credit limit information indicating the amount of credit card available and judging whether or not payment by credit card is possible based on the credit limit information; sending the result of the judgment on whether or not payment by credit card is possible to one or more terminal devices of the person to whom the credit card is to be issued, the person authorized to view the credit card, and the person authorized to manage the credit card; and, if the result of the judgment on whether or not payment by credit card is possible indicates that payment is possible, registering the information on the credit card payment as accounting information for the accounting service used by the person to whom the credit card is to be issued.

According to one embodiment of the present disclosure, an information processing device is provided that includes a control unit and a storage unit and that manages the use of a credit card. The storage unit stores information associated with the person to whom the credit card is to be issued, including information on a person authorized to view the credit card's usage status and information on a person authorized to manage the credit card's usage status. The control unit executes the steps of accepting authorization information requesting payment by credit card, acquiring credit limit information indicating the amount of credit card available and judging whether or not payment by credit card is possible based on the credit limit information, transmitting the result of the judgment on whether or not payment by credit card is possible to one or more terminal devices of the person to whom the credit card is to be issued, the person authorized to view the credit card, and the person authorized to manage the credit card, and, if the result of the judgment on whether or not payment by credit card is possible indicates that payment is possible, registering the information on the credit card payment as accounting information for the accounting service used by the person to whom the credit card is to be issued.

According to one embodiment of the present disclosure, a method for managing credit card usage is provided, the method being executed by a computer having a processor and a memory. The memory stores information associated with the person to whom the credit card is to be issued, including information on a person authorized to view the credit card usage status and information on a person authorized to manage the credit card usage status. The method includes the steps of: receiving authorization information requesting a payment by credit card, acquiring credit limit information indicating the amount of credit card available, and judging whether or not the payment by credit card can be made based on the credit limit information, transmitting the result of the judgment on whether or not the payment by credit card can be made to one or more terminal devices of the person to whom the credit card is to be issued, the person authorized to view the credit card, and the person authorized to manage the credit card, and, if the result of the judgment on whether or not the payment by credit card can be made indicates that the payment is possible, registering the information on the payment by credit card as accounting information for the accounting service used by the person to whom the credit card is to be issued.

According to the present disclosure, the result of the determination as to whether or not a payment can be made by credit card is notified to the person to whom the credit card is to be issued, the person authorized to view the credit card, or the person authorized to manage the credit card. In addition, information on payments made by credit card is registered as accounting information. Therefore, for example, for corporate credit cards, it becomes possible to easily grasp the usage status of employees and the like and register the information as accounting information.

1 is a diagram showing the overall configuration of a card usage management system 1 of a first embodiment. 1 is a block diagram showing the functional configuration of a terminal device 10 constituting a card usage management system 1 of embodiment 1. A diagram showing the functional configuration of a server 20 constituting a card usage management system 1 of embodiment 1. A diagram showing an example of the data structure of a card member database 2021 and a card usage history database 2022 stored in the server 20. 2 is a diagram showing an example of the data structure of an accounting database 2023 stored in the server 20. FIG. 11 is a flowchart showing an example of a flow of card-related information registration processing performed by the card usage management system 1 of the first embodiment. 1 is a flowchart showing an example of the flow of authorization processing by the card usage management system 1 of embodiment 1. 11 is a flowchart showing an example of a flow of card usage status change processing performed by the card usage management system 1 of the first embodiment. 13 is a diagram showing an example of a screen displaying a payment availability determination result displayed on the terminal device 10. FIG. A diagram showing the functional configuration of a server 20 constituting a card usage management system 1 of embodiment 2. 13 is a diagram showing an example of a screen displaying a payment availability determination result displayed on the terminal device 10. FIG.

Below, an embodiment of the present disclosure will be described with reference to the drawings. In the following description, identical parts are given the same reference numerals. Their names and functions are also the same. Therefore, detailed descriptions thereof will not be repeated.

＜Overview＞
The card usage management system according to the present disclosure will be described below. This card usage management system is a system for managing the usage of a credit card by accepting authorization information requesting payment by using a credit card and settling the usage fee with the credit card. When settling the usage fee with a credit card, this card usage management system acquires information on the credit limit indicating the amount that can be used with the credit card and judges whether or not the payment can be made with the credit card. In the card usage management system according to the present disclosure, the information on the credit limit (available limit) may be managed in the own system and the authorization information may be accepted to judge whether or not the payment can be made, or the information on the credit limit (available limit) may be acquired from an external system and the authorization information may be accepted to judge whether or not the payment can be made. In addition, the card usage management system according to the present disclosure is a system provided by a so-called SaaS (Software as a Service) as a Web service by, for example, a cloud server or the like, and is configured to be accessible by a user who uses the service of this card usage management system through a predetermined authentication.

The card usage management system according to the present disclosure mainly registers information on persons with viewing authority, persons with management authority, and persons with permitted use as information linked to persons to whom credit cards are issued, for corporate credit cards. A person with viewing authority is a person who can view the usage status of a credit card, and can only view, i.e. cannot change the usage status. A person with management authority is a person who can change the usage status of a credit card, and can specify and change the credit card's available credit limit and the affiliated stores at which it can be used for authorized users, which will be described later. An authorized user is a person who can make payments by credit card, such as an employee of a corporation related to corporate credit cards.

The card usage management system according to the present disclosure also displays a workflow on a terminal device that allows the person to whom the credit card is issued (the issuer), the person authorized to view, and the person authorized to manage to refer to and change the usage status of the credit card, and accepts various operations. In this workflow, when authorization information is accepted, related information indicating the usage details of the credit card related to the payment is accepted in association with the authorization information. This related information includes, for example, text information of a memo indicating the usage details, or image information such as a photograph of a voucher indicating the usage details.

Furthermore, the card usage management system according to the present disclosure is configured to, when it receives authorization information from a credit card when a product is purchased or a service is used using the credit card, transmit the result of the judgment as to whether or not the payment can be made to the terminal device of the person to whom the credit card is issued, the person authorized to view it, and the person authorized to manage it. This configuration makes it possible to immediately grasp the information on the payment made using the credit card. Furthermore, it is configured to accept input from the person authorized to manage to change the usage status of the credit card based on this judgment result as to whether or not the payment can be made. This configuration makes it possible to control whether or not the payment can be made based on the judgment result as to whether or not the payment can be made using the credit card.

Furthermore, the card usage management system according to the present disclosure is configured to link with an accounting system for providing accounting processing services to corporations and the like related to corporate credit cards. This accounting system may be provided as a web service by the same service provider, or may be provided as a web service by another service provider, and may be configured so that data is linked between the web services. Specifically, when the result of the determination as to whether or not payment can be made by credit card is that payment is possible, the card usage management system according to the present disclosure registers information about the payment made by credit card as accounting information in the accounting system (accounting service). This configuration makes it possible to instantly reflect information about payment made using a credit card as accounting information.

The above configuration makes it possible to easily grasp the usage status of corporate credit cards by employees, control their usage, and register the information as accounting information.

First Embodiment
The following describes the card usage management system 1. In the following description, for example, when the terminal device 10 accesses the server 20, the server 20 responds with information for generating a screen on the terminal device 10. The terminal device 10 generates and displays a screen based on the information received from the server 20.

<1 Overall configuration of card usage management system 1>
Fig. 1 is a diagram showing the overall configuration of a card usage management system 1 according to embodiment 1. As shown in Fig. 1, the card usage management system 1 includes a plurality of terminal devices (terminal device 10A and terminal device 10B are shown in Fig. 1. Hereinafter, they may be collectively referred to as "terminal device 10"), a server 20, and an affiliated store terminal device 30. The terminal device 10, the server 20, and the affiliated store terminal device 30 are connected to each other via a network 80 so as to be able to communicate with each other. The network 80 is formed of a wired or wireless network.

The terminal device 10 is a device operated by each user. Here, a user is a person who uses the terminal device 10 to manage credit card usage, which is a function of the card usage management system 1, and is, for example, a corporate employee who is mainly responsible for corporate credit cards. The terminal device 10 is realized by a stationary PC (Personal Computer), a laptop PC, etc. Alternatively, the terminal device 10 may be, for example, a tablet compatible with a mobile communication system, a mobile terminal such as a smartphone, etc.

The terminal device 10 is connected to the server 20 via a network 80 so as to be able to communicate with the server 20. The terminal device 10 is connected to the network 80 by communicating with communication devices such as a wireless base station 81 that supports communication standards such as 4G, 5G, and LTE (Long Term Evolution), and a wireless LAN router 82 that supports wireless LAN (Local Area Network) standards such as IEEE (Institute of Electrical and Electronics Engineers) 802.11. As shown as the terminal device 10B in FIG. 1, the terminal device 10 includes a communication IF (Interface) 12, an input device 13, an output device 14, a memory 15, a storage unit 16, and a processor 19.

The communication IF 12 is an interface for inputting and outputting signals so that the terminal device 10 can communicate with external devices. The input device 13 is an input device (e.g., a keyboard, a touch panel, a touch pad, a pointing device such as a mouse, etc.) for receiving input operations from a user. The output device 14 is an output device (a display, a speaker, etc.) for presenting information to a user. The memory 15 is for temporarily storing programs and data processed by the programs, etc., and is a volatile memory such as a DRAM (Dynamic Random Access Memory). The storage unit 16 is a storage device for saving data, such as a flash memory or a HDD (Hard Disc Drive). The processor 19 is hardware for executing an instruction set described in a program, and is composed of an arithmetic unit, a register, peripheral circuits, etc.

The server 20 is a device provided by businesses that issue credit cards and manages the use of credit cards. The server 20 accepts authorization information that requests payment by credit card use, obtains credit limit information that indicates the amount that can be used on the credit card, and determines whether or not payment by credit card is possible. For credit cards mainly for corporations, the server 20 stores information on the person authorized to view, the person authorized to manage, and the person authorized to use as information linked to the person to whom the credit card is issued. When the server 20 accepts authorization information, it transmits the result of the determination of whether or not payment is possible to the terminal device of the person authorized to view and the terminal device 10 of the person authorized to manage. The server 20 also registers the information on the payment by credit card as accounting information.

The server 20 is a computer connected to the network 80. The server 20 includes a communication IF 22, an input/output IF 23, a memory 25, a storage 26, and a processor 29.

The communication IF 22 is an interface for inputting and outputting signals so that the server 20 can communicate with external devices. The input/output IF 23 functions as an interface with an input device for accepting input operations from the user and an output device for presenting information to the user. The memory 25 is for temporarily storing programs and data processed by the programs, etc., and is a volatile memory such as a DRAM (Dynamic Random Access Memory). The storage 26 is a storage device for saving data, such as a flash memory or a HDD (Hard Disc Drive). The processor 29 is hardware for executing a set of instructions written in a program, and is composed of an arithmetic unit, registers, peripheral circuits, etc.

The affiliated store terminal device 30 is a terminal device that accepts payments made by credit card and is installed in various retail stores and other stores. When a customer in the store wishes to pay by credit card when purchasing a product or the like, a store clerk or the like operates the affiliated store terminal device 30 to scan the credit card presented by the customer, thereby reading the magnetic information or IC chip information embedded in the credit card, authenticating that it is a legitimate credit card, and sending authorization information to the server 20 to execute the payment. The affiliated store terminal device 30 is a terminal device connected to the network 80. Note that in the case of so-called online shopping on an EC site or the like, information is not obtained directly from the credit card, so the payment may be executed without sending authorization information from the affiliated store terminal device 30 to the server 20.

<1.1 Configuration of terminal device 10>
FIG. 2 is a block diagram showing the functional configuration of the terminal device 10 constituting the card usage management system 1 of the first embodiment. As shown in FIG. 2, the terminal device 10 includes a plurality of antennas (antenna 111, antenna 112), wireless communication units (first wireless communication unit 121, second wireless communication unit 122) corresponding to each antenna, an operation reception unit 130 (including a keyboard 131 and a mouse 132), a voice processing unit 140, a microphone 141, a speaker 142, a display 150, a storage unit 160, and a control unit 170. The terminal device 10 also has functions and configurations (e.g., a battery for storing power, a power supply circuit for controlling the supply of power from the battery to each circuit, etc.) that are not particularly shown in FIG. 2. As shown in FIG. 2, each block included in the terminal device 10 is electrically connected by a bus or the like.

The antenna 111 emits the signal emitted by the terminal device 10 as a radio wave. The antenna 111 also receives the radio wave from space and provides the received signal to the first wireless communication unit 121.

The antenna 112 emits the signal emitted by the terminal device 10 as a radio wave. The antenna 112 also receives the radio wave from space and provides the received signal to the second wireless communication unit 122.

The first wireless communication unit 121 performs modulation and demodulation processing and the like for transmitting and receiving signals via the antenna 111 so that the terminal device 10 can communicate with other wireless devices. The second wireless communication unit 122 performs modulation and demodulation processing and the like for transmitting and receiving signals via the antenna 112 so that the terminal device 10 can communicate with other wireless devices. The first wireless communication unit 121 and the second wireless communication unit 122 are communication modules including a tuner, an RSSI (Received Signal Strength Indicator) calculation circuit, a CRC (Cyclic Redundancy Check) calculation circuit, a high-frequency circuit, and the like. The first wireless communication unit 121 and the second wireless communication unit 122 perform modulation and demodulation and frequency conversion of wireless signals transmitted and received by the terminal device 10, and provide the received signals to the control unit 170.

The operation reception unit 130 has a mechanism for receiving input operations from the user. Specifically, the operation reception unit 130 includes a keyboard 131 and a mouse 132. Note that the operation reception unit 130 may be configured as a touch screen that detects the user's contact position on the touch panel, for example, by using a capacitive touch panel.

The keyboard 131 accepts input operations by the user of the terminal device 10. The keyboard 131 is a device for inputting characters, and outputs the input character information to the control unit 170 as an input signal.

The mouse 132 accepts input operations by the user of the terminal device 10. The mouse 132 is a pointing device for selecting an object displayed on the display 150, and outputs position information of the object selected on the screen and information indicating that a button has been pressed as input signals to the control unit 170.

The audio processing unit 140 modulates and demodulates audio signals. The audio processing unit 140 modulates a signal provided by the microphone 141 and provides the modulated signal to the control unit 170. The audio processing unit 140 also provides the audio signal to the speaker 142. The audio processing unit 140 is realized, for example, by a processor for audio processing. The microphone 141 accepts audio input and provides an audio signal corresponding to the audio input to the audio processing unit 140. The speaker 142 converts the audio signal provided by the audio processing unit 140 into audio and outputs the audio to the outside of the terminal device 10.

The display 150 displays data such as images, videos, and text in response to the control of the control unit 170. The display 150 is realized, for example, by an LCD (Liquid Crystal Display) or an organic EL (Electro-Luminescence) display.

The storage unit 160 is configured, for example, with a flash memory, and stores data and programs used by the terminal device 10. In one aspect, the storage unit 160 stores user information 161.

User information 161 is information about a user who uses the terminal device 10 to manage credit card usage, which is a function of the card usage management system 1. User information includes information that identifies the user (user ID), the user's name or title, etc.

The control unit 170 controls the operation of the terminal device 10 by reading a program stored in the storage unit 160 and executing instructions contained in the program. The control unit 170 is, for example, an application that is pre-installed in the terminal device 10. The control unit 170 operates according to the program to fulfill the functions of an input operation reception unit 171, a transmission/reception unit 172, a data processing unit 173, and a notification control unit 174.

The input operation reception unit 171 performs processing to receive user input operations on an input device such as the keyboard 131.

The transmission/reception unit 172 performs processing for the terminal device 10 to transmit and receive data to and from external devices such as the server 20 in accordance with a communication protocol.

The data processing unit 173 performs calculations on the data received by the terminal device 10 according to a program, and outputs the results of the calculations to a memory or the like.

The notification control unit 174 performs processing to present information to the user. The notification control unit 174 performs processing to display a display image on the display 150, output audio to the speaker 142, etc.

<1.2 Functional configuration of server 20>
Fig. 3 is a diagram showing the functional configuration of the server 20 constituting the card usage management system 1 of the embodiment 1. As shown in Fig. 3, the server 20 performs the functions of a communication unit 201, a storage unit 202, and a control unit 203.

The communication unit 201 performs processing for the server 20 to communicate with external devices.

The memory unit 202 stores data and programs used by the server 20. The memory unit 202 stores a card member database 2021, a card usage history database 2022, an accounting database 2023, etc.

The card member database 2021 is a database for storing credit card information managed by the card usage management system 1, as well as information on persons with viewing authority, persons with management authority, and persons authorized to use that are linked to the credit card information. Details will be described later.

The card usage history database 2022 is a database for storing authorization information for credit cards managed by the card usage management system 1, and information regarding the results of judgments on whether or not a payment can be made. Details will be described later.

The accounting database 2023 is a database for holding accounting information related to the accounting processing of businesses, and includes accounting information of corporations and the like related to corporate credit cards that are managed by the card usage management system 1. Details will be described later.

The control unit 203 performs the functions shown in various modules, such as a receiving control module 2031, a sending control module 2032, a card-related information registration module 2033, an authorization information acceptance module 2034, a payment possibility determination module 2035, a determination result transmission module 2036, an accounting information registration module 2037, and a workflow management module 2038, by the processor 29 of the server 20 performing processing according to a program.

The reception control module 2031 controls the process in which the server 20 receives signals from external devices according to a communication protocol.

The transmission control module 2032 controls the process in which the server 20 transmits signals to external devices according to a communication protocol.

The card-related information registration module 2033 controls the process of accepting and registering information on persons authorized to view, persons authorized to manage, and persons authorized to use from the terminal device 10 as information linked to persons to whom a credit card is issued, who are users of the card usage management system 1. A person authorized to view is a person who can view the usage status of a credit card and can only view, i.e., cannot change the usage status. A person authorized to view is, for example, an accounting officer of a corporation related to a corporate credit card. A person authorized to manage is a person who can change the usage status of a credit card and can specify and change the credit card's available credit limit and the affiliated stores at which it can be used for an authorized user. A person authorized to manage is, for example, a manager or owner of the corporation. A person authorized to use is a person who can use a credit card to make payments, such as an employee of a corporation related to a corporate credit card.

In the case of corporate credit cards, or so-called business cards, the credit card is often issued in the name of an individual, such as the representative of the corporation. Therefore, the person with administrative authority may also be the credit card issuer.

The card-related information registration module 2033, for example, registers and stores the received information on the person authorized to view, the person authorized to manage, and the person authorized to use in the card member database 2021 as information linked to the person to whom the credit card is to be issued (the issuer).

The authorization information reception module 2034 controls the process of receiving authorization information requesting payment by credit card. The authorization information received by the authorization information reception module 2034 is, for example, information requesting payment that is sent from the affiliated store terminal device 30 when a user wishes to pay by credit card when purchasing goods or receiving services in a store such as various retail stores and the like, scans the credit card using the affiliated store terminal device 30 at the store. Alternatively, when a user wishes to pay by credit card when paying for online shopping on an EC site or the like, the information requesting payment is sent from a server or the like managing the EC site.

The authorization information accepted by the authorization information acceptance module 2034 includes, for example, information on the date and time the payment was accepted, the credit card number, the expiration date, the card issuer, information on the card company (brand) of the credit card, the payment category (lump sum or installments), the payment amount, etc.

The authorization information reception module 2034, for example, registers and stores the received authorization information in the card usage history database 2022 as information linked to credit card information.

The payment possibility determination module 2035 acquires information on the credit limit, which indicates the available amount of the credit card, and controls the process of determining whether or not the payment related to the authorization information accepted by the authorization information acceptance module 2034 is possible based on the acquired credit limit information. The credit limit information acquired by the payment possibility determination module 2035 may be information on the credit limit (available limit) stored by the server 20 (not shown), or may be information on the credit limit (available limit) acquired from an external system such as a credit card company. Note that the credit limit information here refers to the amount obtained by subtracting the balance of the credit card that has actually been used and has not yet been paid to the credit card company from the credit limit amount granted at the time of issuing the credit card, but may not match due to a time lag in updating information. For example, if the amount of the payment related to the authorization information is equal to or less than the credit limit amount, the payment possibility determination module 2035 determines that the payment is possible, and if it exceeds the credit limit amount, the payment possibility determination module 2035 determines that the payment is impossible.

For example, if an external system such as a credit card company (card brand) determines whether or not payment related to authorization information can be made, the payment possibility determination module 2035 does not need to be included as a function of the server 20.

The payment approval/disapproval determination module 2035, for example, registers and stores information regarding the result of the determination of whether or not payment related to the authorization information can be made in the card usage history database 2022.

The determination result sending module 2036 controls the process of sending the result of the determination made by the payment feasibility determination module 2035 as to whether or not payment related to the authorization information can be made to the terminal device 10 of the person to whom the credit card is to be issued, the person with viewing authority, or the person with management authority. The determination result sending module 2036 sends the determination result as to whether or not payment can be made to, for example, the contact information of the person to whom the credit card is to be issued registered when the credit card was issued, the information of the person with viewing authority received by the card-related information registration module 2033, and each of the contact information included in the information of the person with management authority. The destination at this time may be an email address, a telephone number for a short message, or a messenger account for various web services.

When transmitting the determination result of whether or not payment related to the authorization information can be made, the determination result transmission module 2036 may transmit link information to a workflow that the workflow management module 2038, described below, displays on the terminal device 10. This link information is, for example, link information for viewing information on the usage history, such as payment information and available balance using the credit card, and accepting changes to the usage status. Alternatively, this link information is, for example, link information for accepting registration of related information for the transmitted payment information.

The determination result transmission module 2036 also transmits the result of the determination made by the payment feasibility determination module 2035 as to whether or not payment related to the authorization information can be made to the sender of the authorization information accepted by the authorization information acceptance module 2034, such as the affiliated store terminal device 30 or the server managing the EC site. As a result, if the determination result of whether or not payment can be made indicates that payment is possible, the payment process is actually performed.

If the result of the determination by the payment feasibility determination module 2035 as to whether or not payment related to the authorization information is possible, the accounting information registration module 2037 controls the process of registering information about the credit card payment as accounting information in the accounting system (accounting service) that the card usage management system 1 links to. The accounting system (accounting service) that the card usage management system 1 links to is an accounting system for providing accounting processing services to businesses such as corporations, and may be provided as a web service by the same service provider as the card usage management system 1, or may be provided as a web service by another service provider and configured to link data with the card usage management system 1.

Specifically, the accounting information registration module 2037 registers the transaction information related to the authorization information in the accounting system as accounts payable (credit accounts payable) for the corporation.

The workflow management module 2038 displays a workflow on the terminal device that allows the issuance target (issuer), authorized user, viewing authority, and management authority of the credit card to refer to and change the credit card usage status, and controls the process of accepting various operations. In response to accepting an input operation to display the credit card usage status by the above-mentioned person operating the terminal device 10, the workflow management module 2038 transmits information indicating the credit card usage status to the terminal device 10 and displays it. The information indicating the credit card usage status is not only the payment information and available balance information of the credit card, but also the available credit limit and available affiliated stores set for each authorized user as information on the range of the credit card that can be used by the authorized user. Furthermore, the workflow management module 2038 changes the credit card usage status in response to accepting an input operation to change the credit card usage status by the management authority (which may include the issuance target) operating the terminal device 10.

The workflow management module 2038 also accepts related information indicating the credit card usage details relating to the payment, linked to the authorization information accepted by the authorization information acceptance module 2034. This related information includes, for example, text information of a memo indicating the usage details, or image information such as a photograph of a voucher (receipt, invoice) indicating the usage details. The text information of the memo indicating the usage details is, for example, a memo explaining the purpose for which the product was purchased, for whom it was purchased, etc.

<2 Data Structure>
Fig. 4 is a diagram showing an example of the data structure of the card member database 2021 and the card usage history database 2022 stored by the server 20. Fig. 5 is a diagram showing an example of the data structure of the accounting database 2023 stored by the server 20.

As shown in FIG. 4, each record in the card member database 2021 includes the items "member ID," "card number," "card holder," "authorized user ID/usage conditions," "viewer ID/contact information," and "management authority ID/contact information," etc.

The item "member ID" is information that identifies each person to whom an issued credit card is issued (the issuer's name), which is managed by the card usage management system 1.

The "Card No." item is the card number of an issued credit card that is managed by the card usage management system 1. A credit card card number is a 14- to 16-digit number that uniquely identifies a credit card.

The item "Cardholder" is the name of the person to whom an issued credit card is issued (issuer), which is managed by the card usage management system 1.

The item "Authorized User ID/Conditions of Use" is information that identifies each authorized user who is registered as someone who can make payments by credit card and is managed by the card usage management system 1, and information on the usable range of the credit card registered for that authorized user. The usable range of the credit card is stored as information on the usable range, including the usable credit limit set for each authorized user and information on the affiliated stores where it can be used.

The item "Viewing Authorized Person ID/Contact Information" is information that identifies each viewing authorized person who is registered as someone who can view the credit card usage status managed by the card usage management system 1, and the contact information registered for that viewing authorized person.

The item "Administrative Authorities ID/Contact Information" is information that identifies each administrative authority registered as someone who can change the usage status of credit cards managed by the card usage management system 1, and the contact information registered for that administrative authority.

The card-related information registration module 2033 of the server 20 adds records to the items "Viewing Authorized Person ID/Contact Information," "Management Authorized Person ID/Contact Information," and "User Authorized Person ID/Conditions of Use" in the card member database 2021 upon receiving input of viewing authorized person information, management authorized person information, and authorized user information.

Each record in the card usage history database 2022 includes the items "member ID," "card number," and "card usage history details," etc.

The item "member ID" is information that identifies each person to whom an issued credit card is issued (the issuer), which is managed by the card usage management system 1, and corresponds to the item "member ID" in the card member database 2021.

The "Card No." item is the card number of an issued credit card that is managed by the card usage management system 1, and corresponds to the "Card No." item in the card member database 2021.

The item "Card usage history details" is historical information about payments made using issued credit cards that are managed by the card usage management system 1, and specifically includes the items "Date," "Affiliated store ID," "Payment amount," and "Approval number," etc.

The "Date" item is information about the date when authorization information related to a credit card payment was received. Information about the time when the authorization information was received is also obtained, but is not shown in the figure.

The "Member Store ID" item is information that identifies each card member store, such as a shop that sent authorization information related to a credit card payment.

The "Payment amount" item is information that indicates the amount of a credit card payment.

The "approval number" item is a number that is assigned to the authorization information related to a credit card payment when the result of the judgment on whether or not the payment can be made is that the payment is possible. Therefore, if the result of the judgment on whether or not the payment can be made is that the payment is not possible, no number is stored in the "approval number" item.

The authorization information reception module 2034 of the server 20 adds a record to the card usage history database 2022 in response to receiving the authorization information. In addition, the payment permission determination module 2035 stores the authorization number in the "approval number" field of the card usage history database 2022 in response to determining whether or not payment related to the authorization information can be made.

As shown in FIG. 5, each record in the accounting database 2023 includes the items "member ID," "user name," and "journal entry information," etc.

The item "member ID" is information that identifies each person to whom an issued credit card is issued (the issuer), which is managed by the card usage management system 1, and corresponds to the item "member ID" in the card member database 2021.

The "User name" item is the user's name or corporate name in the accounting system that is linked to the card usage management system 1.

The item "Journal entry information" is information registered by registering (bookkeeping) accounting information using an accounting system linked to the card usage management system 1, and specifically includes the item "Date", the item "Account ID", the item "Debit (amount)", the item "Credit (amount)", etc. This item "Journal entry information" is configured so that when accounting information is registered (bookkeeping) using an accounting system linked to the card usage management system 1, the latest information is added as a record in chronological order, for example, by the item "Date".

The "Date" item is information that indicates the date on which the user's accounting information was registered in the accounting system.

The item "Account ID" is the account information entered into the accounting system and corresponds to the account listed in the summary column on the ledger.

The item "Debit (amount)" is the amount recorded on the debit side of the ledger in the accounting information entered into the accounting system.

The item "Credit (amount)" is the amount recorded on the credit side of the ledger in the accounting information entered into the accounting system.

The accounting information registration module 2037 of the server 20 adds a record to the "journal entry information" item in the accounting database 2023 as it registers the payment information related to the authorization information as accounting information.

<3 Operation>
Hereinafter, the card-related information registration process, the authorization process, and the card usage status change process performed by the card usage management system 1 in the first embodiment will be described with reference to FIGS.

Figure 6 is a flowchart showing an example of the flow of card-related information registration processing by the card usage management system 1 of embodiment 1.

As a pre-processing for step S111, the input operation reception unit 171 of the terminal device 10 receives an operation from the user to input a user ID and password for authentication required to use the services of the card usage management system 1. The transmission/reception unit 172 transmits the received user ID, password, and user information to the server 20. The server 20 receives the user ID and password via the communication unit 201, confirms that the user's user ID and password are valid, and performs the specified authentication. If they are valid, the server 20 transmits authentication completion information to the terminal device 10 via the communication unit 201. The transmission/reception unit 172 of the terminal device 10 receives the authentication completion information transmitted from the server 20. The notification control unit 174 displays the received authentication completion information on the display 150, and step S111 is started.

In step S111, the input operation acceptance unit 171 of the terminal device 10 accepts, through operation by the user, an instruction to display a card-related information registration screen for inputting card-related information. The transmission/reception unit 172 transmits the accepted display instruction to the server 20. The transmission/reception unit 172 of the terminal device 10 accepts display data for the card-related information registration screen transmitted from the server 20. The notification control unit 174 causes the display 150 to display the accepted display data for the card-related information registration screen.

In step S121, the server 20 accepts the display instruction for the card-related information registration screen transmitted from the terminal device 10 via the communication unit 201. The server 20 transmits display data for the card-related information registration screen to the terminal device 10 via the communication unit 201.

In step S112, the input operation reception unit 171 of the terminal device 10 receives, through user operation, input of credit card related information, specifically, information on the person authorized to view, the person authorized to manage, and the person authorized to use, as information linked to the person to whom the credit card is to be issued. The transmission/reception unit 172 transmits the received credit card related information to the server 20.

In step S122, the card-related information registration module 2033 of the server 20 accepts the credit card related information transmitted from the terminal device 10, specifically the information of the person authorized to view, the person authorized to manage, and the person authorized to use, which is linked to the person to whom the credit card is to be issued, via the communication unit 201. The card-related information registration module 2033 registers the accepted credit card related information in the card member database 2021.

As described above, the card usage management system 1 registers information related to the person to whom the credit card is to be issued, such as information on the person authorized to view, the person authorized to manage, and the person authorized to use, based on input from the user. This information is used to notify authorization information, etc.

Figure 7 is a flowchart showing an example of the flow of authorization processing by the card usage management system 1 of embodiment 1.

In step S211, in a store such as a retail store where the affiliated store terminal device 30 is installed, if a customer wishes to pay by credit card as a payment method when purchasing a product, etc., a store employee, etc. operates the affiliated store terminal device 30 to scan the credit card presented by the customer. The affiliated store terminal device 30 reads the magnetic information or IC chip information embedded in the credit card, authenticates that it is a legitimate credit card, and transmits authorization information to the server 20.

In step S221, the authorization information reception module 2034 of the server 20 receives the authorization information sent from the affiliated store terminal device 30 via the communication unit 201. The authorization information reception module 2034 registers the received authorization information in the card usage history database 2022 as information linked to credit card information.

In step S222, the payment availability determination module 2035 of the server 20 acquires credit limit information indicating the available credit amount for the credit card, which is related to the authorization information received in step S221. Here, the acquired credit limit information may be credit limit (available limit) information stored by the server 20, or may be credit limit (available limit) information acquired from an external system such as a credit card company.

In step S223, the payment approval/disapproval determination module 2035 of the server 20 determines whether or not payment related to the authorization information received in step S221 can be approved based on the credit limit information acquired in step S222.

The determination of whether or not payment related to the authorization information can be made in step S223 will be specifically described. In step S223, as described above, if the amount of the payment related to the authorization information is equal to or less than the amount of the credit limit, it is determined that payment is possible, and if it exceeds the amount of the credit limit, it is determined that payment is impossible. The credit limit here is a credit limit calculated from the available credit limit set for the authorized user when the authorization information is from the authorized user. In addition, if the authorization information is from an available affiliated store set for the authorized user, it is determined that payment is possible, and if the authorization information is from a store other than the available affiliated store, it is determined that payment is impossible. Furthermore, the possibility of payment may be determined by comprehensively taking into account these pieces of information. At this time, for example, a machine learning model for determining whether or not payment can be made may be used for the determination. Such a machine learning model may be generated by machine learning performed as a function of the payment possibility determination module 2035, or a machine learning model generated as a result of machine learning performed by another device may be obtained. The machine learning referred to here may be performed by supervised machine learning using predetermined teacher data, unsupervised machine learning, or deep learning. In addition, further machine learning may be performed based on the estimation results by the payment feasibility determination module 2035 and the subsequent deposit and withdrawal status, and an aggregation process may be performed to merge the learning results.

In step S224, the determination result transmission module 2036 of the server 20 transmits the determination result of whether or not the payment can be made, determined in step S223, to the terminal device 10 via the communication unit 201. The determination result transmission module 2036 also transmits the determination result of whether or not the payment can be made, via the communication unit 201, to the sender of the authorization information received in step S221, such as the affiliated store terminal device 30 or a server managing the EC site.

In step S214, the affiliated store terminal device 30 accepts the result of the judgment on whether or not the payment can be made, which is sent from the server 20. The affiliated store terminal device 30 notifies the result of the judgment on whether or not the payment can be made, and if the judgment result on whether or not the payment can be made indicates that the payment can be made, the affiliated store terminal device 30 actually performs the payment process.

In step S234, the transmission/reception unit 172 of the terminal device 10 accepts the result of the judgment on whether or not the payment can be made, which is sent from the server 20. The notification control unit 174 causes the display 150 to display the accepted judgment on whether or not the payment can be made.

In step S225, if the result of the determination as to whether or not the payment is possible in step S223 indicates that the payment is possible, the accounting information registration module 2037 of the server 20 registers the information on the credit card payment as accounting information in the accounting system (accounting service) linked to the card usage management system 1.

As described above, when the card usage management system 1 receives authorization information, it determines whether or not payment can be made based on the credit limit. This determination result on whether or not payment can be made is sent to the terminal devices of the person to whom the credit card is issued, the person authorized to view it, and the person authorized to manage it. This makes it possible to immediately grasp information about payments made using a credit card.

Figure 8 is a flowchart showing an example of the flow of card usage status change processing by the card usage management system 1 of embodiment 1.

In step S311, the input operation reception unit 171 of the terminal device 10 receives a display instruction to display a card usage status screen that displays the card usage status, through an operation by an authorized administrator. The transmission/reception unit 172 transmits the received display instruction to the server 20.

In step S321, the workflow management module 2038 of the server 20 receives, via the communication unit 201, an instruction to display a card usage status screen that displays the card usage status, sent from the terminal device 10.

In step S322, the workflow management module 2038 of the server 20 reads the card usage history database 2022 to obtain payment information and available balance information for the credit card. The workflow management module 2038 also reads the card member database 2021 to obtain the available credit limit and available affiliated stores set for each authorized user as information on the range of credit card usage by the authorized user. The workflow management module 2038 transmits the above obtained information and display data for a card usage status screen displaying this information to the terminal device 10 via the communication unit 201.

In step S312, the transmission/reception unit 172 of the terminal device 10 accepts the display data for the card usage status screen sent from the server 20. The notification control unit 174 causes the display 150 to display the accepted display data for the card usage status screen.

In step S313, the input operation reception unit 171 of the terminal device 10 receives an input for changing the card usage status from an authorized administrator. The transmission/reception unit 172 transmits the received information for changing the card usage status to the server 20.

In step S313, the administrator inputs a change to the card usage status, for example, an input to change the range of the credit card that can be used by the authorized user, specifically the available credit limit and the available affiliated stores. For example, the administrator refers to the payment history and balance of a specific authorized user, and if the administrator determines that the balance is insufficient despite the user making payments related to purchases necessary for business, the administrator changes the available credit limit set for the authorized user to an increased amount. Also, for example, the administrator refers to the payment history and balance of a specific authorized user, and if the administrator determines that the user has not made many payments related to purchases necessary for business and has a surplus balance, the administrator changes the available credit limit set for the authorized user to a decreased amount. Also, for example, if the administrator determines that there is doubt as to whether the payment history of a specific authorized user is for purchases necessary for business, the administrator changes the authorization for the authorized user to be revoked. Furthermore, if an authorized user, such as an employee, is transferred within the corporation or leaves the corporation, the administrator can change or cancel the available credit limit set for the authorized user.

In step S323, the workflow management module 2038 of the server 20 accepts the information for changing the card usage status sent from the terminal device 10 via the communication unit 201. The workflow management module 2038 registers the accepted information for changing the card usage status in the card member database 2021.

As described above, the card usage management system 1 is configured to display and change the credit card usage status through a workflow that allows the credit card usage status to be referenced and changed. This makes it possible to grasp the usage status of corporate credit cards by employees, etc., and control their usage.

<4 Screen example>
Hereinafter, with reference to FIG. 9, an example of a screen displaying the result of the payment approval/disapproval determination in the authorization process by the card usage management system 1 will be described.

Figure 9 is a diagram showing an example of a screen displaying the payment availability determination result displayed on the terminal device 10. The example screen in Figure 9 shows an example of a screen displaying the payment availability determination result related to the authorization information by the payment availability determination module 2035, which is transmitted by the determination result transmission module 2036 to the terminal device 10 of a person authorized to view, etc. This corresponds to step S234 in Figure 7.

As shown in FIG. 9, the display 150 of the terminal device 10 displays a payment availability display field 1031a that shows the result of the judgment on whether or not payment is possible based on the authorization information, and a usage status transition link display field 1031b that shows a link to refer to the usage status of the credit card. A person with viewing authority or a person with management authority can instantly refer to the payment amount displayed in the payment availability display field 1031a and the amount of the card usage balance, etc., that is displayed as a transition destination via the usage status transition link display field 1031b.

<Summary>
As described above, according to this embodiment, when authorization information requesting payment by credit card is received, it is determined whether or not payment can be made based on the credit limit. The result of this determination of whether or not payment can be made is sent to the terminal device of the person to whom the credit card is to be issued, the person authorized to view, and the person authorized to manage. This makes it possible to grasp the usage status of corporate credit cards by employees, etc., for example. This can contribute to the early detection of inappropriate or fraudulent use of credit cards.

In addition, for authorization information requesting payment by credit card, if the determination result indicates that payment is possible, the system will link with an accounting system that provides accounting services and register the credit card payment information as accounting information. This makes it possible to instantly reflect the information on payments made using credit cards as accounting information.

In addition, a workflow that allows you to refer to and change credit card usage status is configured to display and change the credit card usage status. This makes it possible to understand the usage status of corporate credit cards by employees, etc., and control their usage.

Second Embodiment
Other embodiments of the card usage management system 1 will now be described.

<1 Overall configuration of card usage management system 1>
Fig. 10 is a diagram showing the functional configuration of the server 20 constituting the card usage management system 1 of the second embodiment. The overall configuration of the card usage management system 1 and the configuration of the terminal device 10 in the second embodiment are the same as those in the first embodiment, and therefore will not be described repeatedly. The configuration of the server 20 is the same as that in the first embodiment, except that it is newly provided with the function of a card-related information change module 2039, as shown in Fig. 10. The function of the card-related information change module 2039 in the second embodiment will be described below.

The card-related information change module 2039 controls the process of accepting input operations to change the card-related information registered in the card member database 2021. For example, the card-related information change module 2039 changes the possibility of payment in response to an input operation to change the possibility of payment by an administrator (which may include the person to whom the card is issued) operating the terminal device 10 in response to the judgment result of whether or not payment is possible, sent by the judgment result sending module 2036. In response to this, the card-related information change module 2039 changes the card-related information registered in the card member database 2021. Such operations are performed so that the authorized user can make payment within the credit limit of the credit card itself, when the administrator judges that the payment should be possible.

For example, when the result of the judgment on whether or not the payment is possible is not possible, the card-related information change module 2039 accepts an input operation from the management authority to change the possibility of payment to make it possible. This operation may be performed immediately after the judgment result on whether or not the payment is possible is transmitted, but since the person who is trying to make a credit card payment is usually notified immediately based on the judgment result on whether or not the payment is possible, it is considered that this is often not possible in time. Therefore, the judgment result of whether or not the payment is impossible by the judgment result transmission module 2036 is once transmitted to the affiliated store terminal device 30 or the server that manages the EC site. After that, by accepting an input operation from the management authority to change the possibility of payment to make it possible, when authorization information related to the purchase of the same product is received, the judgment result of whether or not the payment is possible by the payment possibility judgment module 2035 becomes "payment possible". In response to this, the card-related information change module 2039 changes the card-related information registered in the card member database 2021.

In addition, for example, the card-related information change module 2039 may be configured to change the card-related information registered in the card member database 2021 when the authorized user makes a request to the administrative authority regarding the result of the judgment that payment is impossible once sent by the judgment result sending module 2036.

<2 Data Structure>
The data structure in the second embodiment is similar to that in the first embodiment, so it will not be described repeatedly.

<3 Operation>
The operation of the second embodiment is similar to that of the first embodiment, and therefore will not be described repeatedly.

<4 Screen example>
An example of a screen displaying the result of the payment approval/disapproval determination in the authorization process by the card usage management system 1 will be described below with reference to FIG.

Figure 11 is a diagram showing an example of a screen displaying the result of the payment permission determination displayed on the terminal device 10. The example screen in Figure 11 shows an example of a screen displaying the result of the determination made by the payment permission determination module 2035 on the authorization information, which is transmitted to the terminal device 10 of the administrator by the determination result transmission module 2036. This corresponds to step S234 in Figure 7.

As shown in FIG. 11, the display 150 of the terminal device 10 displays a payment availability display field 1032a that shows the result of the judgment on whether or not payment is possible based on the authorization information, and a change payment availability button 1032b that is a button for changing the result of the judgment on whether or not payment is possible (to make payment possible) displayed in the payment availability display field 1032a. An administrative authority can change the result of the judgment on whether or not payment is possible (to make payment possible) by pressing the change payment availability button 1032b.

<Summary>
As described above, according to this embodiment, the administrator can input a change to the decision on whether or not payment is possible. This makes it possible to individually control and appropriately manage the use of credit cards by employees.

Although the disclosed embodiments have been described above, they can be embodied in various other forms and can be implemented with various omissions, substitutions, and modifications. These embodiments and variations, as well as omissions, substitutions, and modifications, are included in the technical scope of the claims and their equivalents.

<Additional Notes>
The matters described in the above embodiments will be supplemented below.

(Note 1) A program for managing credit card usage when executed by a computer having a processor 29 and memory 25, in which the memory 25 stores information linked to the person to whom the credit card is to be issued, such as information about a person authorized to view credit card usage (2021) and information about a person authorized to manage credit card usage (2021), and the program causes the processor 29 to execute the following steps: accepting authorization information requesting payment by credit card (S221); acquiring credit limit information indicating the amount of credit card available, and judging whether or not payment by credit card is possible based on the credit limit information (S222-S223); sending the result of the judgment on whether or not payment by credit card is possible to one or more terminal devices of the person to whom the credit card is to be issued, the person authorized to view the credit card, or the person authorized to manage the credit card (S224); and, if the result of the judgment on whether or not payment by credit card is possible is that payment is possible, registering the information on the credit card payment as accounting information for the accounting service used by the person to whom the credit card is to be issued (S225).

(Appendix 2) The program described in (Appendix 1) further executes the steps of: sending information indicating the credit card usage status to the terminal device in response to receiving an input operation to display the credit card usage status from the terminal device by the operation of either or both of a person authorized to view the credit card and/or a person authorized to manage the credit card (S322); and changing the credit card usage status in response to receiving an input operation to change the credit card usage status from the terminal device by the operation of a person authorized to manage the credit card (S323).

(Appendix 3) A program as described in (Appendix 2), in which, in the step of transmitting the result of the determination as to whether or not payment can be made by credit card, information is transmitted that accepts change information regarding whether or not payment can be made by credit card, and the program further executes a step of accepting change information regarding whether or not payment can be made by credit card from a terminal device of a person with management authority over the credit card.

(Appendix 4) The program described in any one of (Appendix 1) to (Appendix 3) further executes a step of storing in memory, in response to receiving an input operation from the terminal device to register a card user who wishes to use a credit card, the card user as an authorized user who can use a credit card.

(Appendix 5) In the step of storing the authorized user of the credit card, the program described in (Appendix 4) accepts an input operation of information related to the authorized user of the credit card, which is the range of information that the credit card can be used for, and stores the information in memory.

(Appendix 6) The program described in (Appendix 5) includes, as information on the range in which credit cards can be used, information on affiliated stores where credit cards can be used, and information on the payment amount for which credit cards can be used.

(Appendix 7) A program described in any of (Appendix 1) to (Appendix 6), in which in the step of transmitting the result of the determination as to whether or not payment by credit card is possible, information is transmitted that accepts relevant information about payment by credit card, and the program further executes a step of accepting relevant information about payment by credit card from one or more terminal devices of the person to whom the credit card is to be issued, the person authorized to view the credit card, or the person authorized to manage the credit card, and in the step of registering the information about payment by credit card, the relevant information about payment by credit card is registered in association with the transaction information.

(Appendix 8) The program described in (Appendix 7) includes text information or image information entered by the person to whom the credit card is to be issued, the person authorized to view the credit card, or the person authorized to manage the credit card, as relevant information regarding payment by credit card.

(Appendix 9) An information processing device that includes a control unit 203 and a storage unit 202 and manages the use of a credit card, in which the storage unit 202 stores information associated with the person to whom the credit card is to be issued, such as information about a person authorized to view the credit card usage status (2021) and information about a person authorized to manage the credit card usage status (2021), and the control unit 203 performs the steps of accepting authorization information requesting payment by credit card (S221), acquiring credit limit information indicating the amount of credit card available, and judging whether or not payment by credit card is possible based on the credit limit information (S222-S223), transmitting the result of the judgment on whether or not payment by credit card is possible to one or more terminal devices of the person to whom the credit card is to be issued, the person authorized to view the credit card, or the person authorized to manage the credit card (S224), and, if the result of the judgment on whether or not payment by credit card is possible is that payment is possible, registering the information about the credit card payment as accounting information for the accounting service used by the person to whom the credit card is to be issued (S225).

(Appendix 10) A method for managing credit card usage, executed by a computer including a processor 29 and a memory 25, in which the memory 25 stores information linked to the person to whom the credit card is to be issued, including information on a person authorized to view the credit card usage status (2021) and information on a person authorized to manage the credit card usage status (2021), and the method includes the steps of: the processor 29 receiving authorization information requesting payment by credit card (S221); acquiring credit limit information indicating the amount of credit card available, and judging whether or not payment by credit card is possible based on the credit limit information (S222-S223); transmitting the result of the judgment on whether or not payment by credit card is possible to one or more terminal devices of the person to whom the credit card is to be issued, the person authorized to view the credit card, or the person authorized to manage the credit card (S224); and, if the result of the judgment on whether or not payment by credit card is possible is that payment is possible, registering the information on the credit card payment as accounting information for the accounting service used by the person to whom the credit card is to be issued (S225).

REFERENCE SIGNS LIST 10 Terminal device, 20 Server, 80 Network, 130 Operation reception unit, 161 User information, 22 Communication IF, 23 Input/output IF, 25 Memory, 26 Storage, 29 Processor, 201 Communication unit, 202 Memory unit, 2021 Card member database, 2022 Card usage history database, 2023 Accounting database, 203 Control unit

Claims (9)

A program for managing credit card usage when executed by a computer having a processor and a memory, comprising:
the memory stores, as information linked to the person to whom the credit card is to be issued, information on a person authorized to view the usage status of the credit card, information on a person authorized to manage the usage status of the credit card, and information on a person authorized to use the credit card,
The program causes the processor to:
receiving authorization information requesting payment by the credit card through the use of the authorized user;
acquiring information on a credit limit indicating a usable amount of the credit card by the authorized user, and determining whether or not payment can be made by the credit card based on the information on the credit limit;
a step of transmitting the result of the determination as to whether or not the payment can be made by the credit card and information for accepting change information regarding whether or not the payment can be made by the credit card to one or more terminal devices of the person to whom the credit card is to be issued, the person authorized to view the credit card, and the person authorized to manage the credit card, by referring to the information associated with the person to whom the credit card is to be issued stored in the memory;
If the result of the determination as to whether or not the payment can be made by credit card is that the payment can be made, registering information about the payment by credit card as transaction information for the transaction service used by the person to whom the credit card is issued;
receiving, from a terminal device of a person authorized to manage the credit card, information on whether or not the credit card can be used for settlement;
The program, wherein the licensee is an employee of a corporation related to a corporate credit card. The program further comprises:
transmitting information indicating the usage status of the credit card to the terminal device in response to an input operation for displaying the usage status of the credit card from a terminal device by an operation of either or both of a person authorized to view the credit card and a person authorized to manage the credit card;
2. The program according to claim 1, further comprising: a step of changing the usage status of the credit card in response to receiving an input operation for changing the usage status of the credit card from a terminal device by operation of a person with management authority of the credit card. The program further comprises:
3. The program according to claim 1, further comprising a step of storing in the memory, in response to receiving an input operation from a terminal device to register a card user who wishes to use the credit card, the card user being an authorized user who can use the credit card. The program according to claim 3, wherein in the storing step, an input operation of information related to the authorized user of the credit card, which is information related to the range of use of the credit card, is accepted and stored in the memory. The program according to claim 4, wherein the information on the range in which the credit card can be used includes information on affiliated stores where the credit card can be used and information on the payment amount for which the credit card can be used. In the step of transmitting the result of the determination as to whether or not the payment by credit card is possible, transmitting information for accepting information related to the payment by credit card;
The program further comprises:
executing a step of receiving information related to the payment by the credit card from any one or more terminal devices of the person to whom the credit card is to be issued, the person authorized to view the credit card, and the person authorized to manage the credit card;
6. The program according to claim 1, wherein in the step of registering the credit card payment information, information related to the credit card payment is registered in association with the transaction information. The program according to claim 6, wherein the information related to the payment by the credit card includes text information or image information input by the person to whom the credit card is to be issued, the person authorized to view the credit card, or the person authorized to manage the credit card. An information processing device that includes a control unit and a storage unit and manages the use of a credit card,
the storage unit stores, as information linked to the person to whom the credit card is to be issued, information on a viewing authorized person who can view the usage status of the credit card, information on a management authorized person who can change the usage status of the credit card, and information on a usage authorized person who can use the credit card for payment;
The control unit is
receiving authorization information requesting payment by the credit card through the use of the authorized user;
acquiring information on a credit limit indicating a usable amount of the credit card by the authorized user, and determining whether or not payment can be made by the credit card based on the information on the credit limit;
a step of transmitting the result of the determination as to whether or not the payment can be made by the credit card and information for accepting change information regarding whether or not the payment can be made by the credit card to one or more terminal devices of the person to whom the credit card is to be issued, the person authorized to view the credit card, and the person authorized to manage the credit card, by referring to information associated with the person to whom the credit card is to be issued that is stored in the storage unit;
If the result of the determination as to whether or not the payment can be made by credit card is that the payment can be made, registering information about the payment by credit card as transaction information for the transaction service used by the person to whom the credit card is issued;
receiving, from a terminal device of a person authorized to manage the credit card, information on whether or not the credit card can be used for settlement;
The information processing device, wherein the authorized user is an employee of a corporation related to a corporate credit card. A method for managing credit card usage, the method being executed by a computer having a processor and a memory, the method comprising:
the memory stores, as information linked to the person to whom the credit card is to be issued, information on a person authorized to view the usage status of the credit card, information on a person authorized to manage the usage status of the credit card, and information on a person authorized to use the credit card,
The method further comprises the processor:
receiving authorization information requesting payment by the credit card through the use of the authorized user;
acquiring information on a credit limit indicating a usable amount of the credit card by the authorized user, and determining whether or not payment can be made by the credit card based on the information on the credit limit;
a step of transmitting the result of the determination as to whether or not the payment can be made by the credit card and information for accepting change information regarding whether or not the payment can be made by the credit card to one or more terminal devices of the person to whom the credit card is to be issued, the person authorized to view the credit card, and the person authorized to manage the credit card, by referring to the information associated with the person to whom the credit card is to be issued stored in the memory;
If the result of the determination as to whether or not the payment can be made by credit card is that the payment can be made, registering information about the payment by credit card as transaction information for the transaction service used by the person to whom the credit card is issued;
receiving, from a terminal device of a person authorized to manage the credit card, information on whether or not the credit card can be used for settlement;
The method, wherein the authorized user is an employee of a corporate entity for a corporate credit card.