JP7271851B1 - server, computer program, method - Google Patents

Abstract

The present invention provides a server that provides credit card technology with less management burden on the user. SOLUTION: In a credit card providing system in which a plurality of user terminals and a server terminal are connected via a network, the server terminal that supports payment by credit card includes first user information and a storage unit for storing associated first credit card information, a first wallet having a first balance, and a second wallet having a second balance; and a wallet information processing unit that receives an instruction to select at least one of the two wallets as the wallet for settlement with the first credit card. [Selection drawing] Fig. 3

Description

Application of Article 30, Paragraph 2 of the Patent Law Attachment 2 of the submission form for the exception certificate of lack of novelty dated January 20, 2022 and the attachment pertaining to the procedural supplement dated February 8, 2022 Published on the website listed in Table 1

The present invention relates to servers, computer programs and methods.

In the past, methods have been proposed to enable the issuance of related credit cards for commonly available credit cards.

For example, in Patent Document 1, a card used for payment, such as a credit card generally used at stores, is used as a parent card, and a card such as an ETC card that can be used exclusively in an automatic toll collection system for toll roads is used as a child card. A child card issuing system for issuing cards is disclosed.

JP-A-2008-84240

In the technique disclosed in Patent Literature 1, the usage amount of the child card is settled from the withdrawal account linked to the parent card. Therefore, it is not possible to use the child card to make payments with an account different from the withdrawal account linked to the parent card. In the case of making payments using separate payment accounts, the user has to have multiple credit cards, which is inconvenient.

SUMMARY OF THE INVENTION Accordingly, an object of the present invention is to provide a credit card settlement technology that is highly convenient for users.

A server for supporting credit card payments, said server comprising: information of a first user; information of a first credit card associated with said first user; a first wallet having a first balance; a storage unit for storing a second wallet having a second balance; and at least one of the first wallet and the second wallet selected from the first user as a wallet for settlement with the first credit card. a wallet selection unit that receives an instruction to

According to the present invention, it is possible to provide a credit card settlement technology that is highly convenient for users.

1 is a block configuration diagram showing a credit card providing system according to a first embodiment of the present invention; FIG. It is a figure which shows the hardware structural example of the computer which implement|achieves the server terminal 100 which concerns on the same embodiment. 3 is a diagram showing a software configuration example of the server terminal 100 according to the same embodiment; FIG. 4 is a diagram showing an example of user information stored in the server terminal 100; FIG. 4 is a diagram showing an example of wallet information stored in the server terminal 100; FIG. 3 is another diagram showing an example of user information stored in the server terminal 100. FIG. 3 is another diagram showing an example of wallet information stored in the server terminal 100. FIG. 3 is another diagram showing an example of wallet information stored in the server terminal 100. FIG. 3 is a diagram showing an example of transaction history information stored in server terminal 100. FIG. It is a figure which shows the hardware structural example of the computer which implement|achieves the user terminal 200 which concerns on the same embodiment. It is a figure which shows the software structural example of the user terminal 200 which concerns on the same embodiment. It is a figure which shows the hardware structural example of the computer which implement|achieves the shop terminal 300 which concerns on the same embodiment. It is a figure which shows the software structural example of the shop terminal 300 which concerns on the same embodiment. It is a flowchart concerning an example of the provision method of the credit card based on 1st embodiment of this invention. It is a flowchart concerning other examples of the provision method of the credit card based on 1st embodiment of this invention. FIG. 9 is a flow chart of yet another example of the credit card providing method according to the first embodiment of the present invention. FIG. It is an example of a screen displayed on the user terminal according to the first embodiment of the present invention. It is another example of the screen displayed on the user terminal according to the first embodiment of the present invention. It is another example of the screen displayed on the user terminal according to the first embodiment of the present invention. It is another example of the screen displayed on the user terminal according to the first embodiment of the present invention. FIG. 2 is a diagram schematically showing the relationship between user IDs (credit card information) and wallet IDs, and the relationship between shared wallet IDs and user IDs (credit card information);

The contents of the embodiments of the present invention are listed and explained. One embodiment of the present invention has the following configuration.
[Item 1]
A server that supports payment by credit card,
The server stores information of a first user, information of a first credit card associated with the first user, a first wallet having a first balance, and a second wallet having a second balance. a storage unit that stores
a wallet selection unit that receives an instruction from the first user to select at least one of the first wallet and the second wallet as a wallet for settlement with the first credit card;
A server with
[Item 2]
the storage unit stores information of a second user, information of a second credit card associated with the second user, and a third wallet having a third balance;
The wallet selection unit receives from the second user an instruction to select at least one of the second wallet and the third wallet as a wallet for settlement with the second credit card;
A server according to item 1, characterized by:
[Item 3]
The wallet selection unit is configured to be able to receive instructions from the first user and the second user to select a wallet for settlement by credit card.
The server of item 2.
[Item 4]
The settlement history of the first credit card can be viewed by the first user when settlement is made using the first wallet, and can be viewed by the first user when settlement is made using the second wallet. and is viewable by the second user;
A server according to item 2 or 3.
[Item 5]
The server has a history display unit that displays a payment history,
The history display unit displays the payment history of the second wallet in a manner different from that of the first wallet,
A server according to any of items 2-4.
[Item 6]
The history display unit displays a settlement amount in the settlement history of the first wallet,
The payment history of the second wallet displays the payment amount and information related to the user who made the payment.
A server according to item 5.
[Item 7]
The server has a point giving unit that gives points based on the credit card settlement amount,
The point granting unit grants the points to the first user when the settlement is made using the first wallet at the time of settlement by the first credit card, and the settlement is made using the second wallet. If done, awarding the points to the first user;
A server according to any of items 2-6.
[Item 8]
at least one of the first user and the second user can invite a user who can use the second wallet;
The invited user is allowed to use the second wallet on the condition that identity verification has been completed.
A server according to any of items 2-7.
[Item 9]
A computer program for assisting payment by credit card,
to the processor,
obtaining information of a first user, information of a first credit card associated with said first user, a first wallet having a first balance, and a second wallet having a second balance; ,
receiving from the first user an instruction to select at least one of the first wallet and the second wallet as a wallet for settlement with the first credit card;
computer program that causes the
[Item 10]
A method of assisting payment by credit card, comprising:
the processor
obtaining information of a first user, information of a first credit card associated with said first user, a first wallet having a first balance, and a second wallet having a second balance; ,
receiving from the first user an instruction to select at least one of the first wallet and the second wallet as a wallet for settlement with the first credit card;
how to run

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described with reference to the drawings. It should be noted that the embodiments described below do not unduly limit the content of the present disclosure described in the claims. Also, not all the components shown in the embodiments are essential components of the present disclosure. In the present specification and drawings, constituent elements having substantially the same functional configuration are denoted by the same reference numerals, thereby omitting redundant description.

(Embodiment 1)
<Configuration>
FIG. 1 is a block configuration diagram showing a credit card providing system 1 according to the first embodiment of the present invention. In this embodiment, the credit card providing system 1 includes a server terminal 100, user terminals 200A and 200B, which are terminals of a plurality of users who use credit cards, and credit card companies in exchange for goods or services. and a store terminal 300, which is a member store terminal that can use the credit card issued by . The server terminal 100 stores credit card information related to credit cards and manages credit card related transactions by users. The server terminal 100 is managed by a credit card issuing company that issues credit cards or a business operator that provides financial services to users of credit cards. Although the numbers and types of server terminals, user terminals, and store terminals are not limited, in this embodiment, for convenience of explanation, the configuration shown in FIG. 1 will be described in detail below.

Credit card companies, so-called credit card issuers, issue cards to users, perform credit management, and authorize transactions when users use credit cards in exchange for products at affiliated stores. (Approve). A user may be an individual user or a corporate user.

Also, a credit card company issues a so-called virtual card, a credit card that does not physically exist and is displayed via an application installed on a mobile terminal such as a smartphone by the user. In addition, the credit card company can also issue a physical credit card with a built-in magnetic or IC chip, which is called a real card, at the request of the user. Here, in this embodiment, a case where both a virtual card and a credit card are issued to each user will be described. Note that the virtual card and the real card may be cards having the same credit card information. In this embodiment, the server terminal 100 stores a personal account and a shared account as settlement accounts for credit card information. A personal account is an account that cannot be shared with other users and is limited to payment users. Shared accounts are accounts that can be shared with other users and are not limited to payment users. In this way, the server terminal 100 associates and stores a plurality of accounts (wallets) as settlement accounts for settlements made by users.

The server terminal 100, user terminals 200A and 200B, and store terminal 300 are connected via a network NW. The network NW includes the Internet, an intranet, a wireless LAN (Local Area Network), a WAN (Wide Area Network), and the like.

== Server terminal 100 ==
The server terminal 100 may be, for example, a general-purpose computer such as a workstation or personal computer, or may be logically realized by cloud computing. In the present embodiment, one card company terminal is illustrated for convenience of explanation, but the present invention is not limited to this, and a plurality of terminals may be used.

==User Terminal 200==
The user terminal 200 is a computer operated by a credit card user. For example, smart phones, tablet computers, personal computers, and the like. A user can access the server terminal 100 by, for example, an application executed on the user terminal 200 or a web browser.

==Store terminal 300==
The store terminal 300 is a terminal installed at a card affiliated store, and includes, for example, terminals such as POS/CCT/CAT installed at supermarkets, shopping centers, convenience stores, etc., and applications having similar functions. It also includes personal computers, smartphones, tablet terminals, etc. In addition, it is not limited to a store, and may include a business owner terminal installed in a business owner who conducts business activities. Using the store terminal 300, operations such as payment by credit card, prepaid card, and debit card can be performed at the storefront of the member store. Also, the store terminal 300 is communicably connected to the server terminal 100 and terminals of other credit card issuing companies (not shown) via the network NW. It is also conceivable to connect to the server terminal 100 or the like via an international brand card system such as VISA (registered trademark).

FIG. 2 is a diagram showing a hardware configuration example of the server terminal 100 of this embodiment. The server terminal 100 includes a CPU 101 , a memory 102 , a storage device 103 , a communication interface 104 , an input device 105 and an output device 106 . The CPU 101 is an arithmetic unit that controls the overall operation of the server terminal 100, controls transmission and reception of data between elements, executes applications, and performs information processing necessary for authentication processing. For example, the CPU 101 is a processor such as a CPU (Central Processing Unit), and executes a program or the like stored in the storage device 103 and developed in the memory 102 to perform each information process. The memory 102 includes a main memory composed of a volatile memory device such as a DRAM (Dynamic Random Access Memory) and an auxiliary memory composed of a non-volatile memory device such as a flash memory and a HDD (Hard Disc Drive, solid state drive). and including. The memory 102 is used as a work area for the CPU 101, and stores a BIOS (Basic Input/Output System) executed when the server terminal 100 is started, various setting information, and the like. The storage device 103 is, for example, a hard disk drive, solid state drive, flash memory, etc., which stores various data and programs. The communication interface 104 is an interface for connecting to the network NW. Examples include a USB (Universal Serial Bus) connector and an RS232C connector for serial communication. The input device 105 is a device that accepts data input through a keyboard, mouse, touch panel, button, microphone, or the like, for example. The output device 106 includes, for example, a display, printer, speaker, etc. for outputting data.

FIG. 3 is a block diagram showing the functional configuration of the server terminal 100 of FIG. 1. As shown in FIG. As shown in FIG. 3, the server terminal 100 includes a communication section 110, a storage section 120, and a control section . Storage unit 120 includes user information storage unit 121 and wallet information storage unit 122 . Control unit 130 includes request accepting unit 131 , user information processing unit 132 , and wallet information processing unit 133 .

The communication unit 110 is a communication interface for communicating with the user terminal 200 and the store terminal 300 via the network NW, and communication is performed according to a communication protocol such as TCP/IP (Transmission Control Protocol/Internet Protocol). will be Storage unit 120 is implemented as part of a storage area provided by memory 102 and storage device 103 provided in server terminal 100 . Control unit 130 is implemented by CPU 101 of server terminal 100 reading a program stored in storage device 103 to memory 102 and executing the program.

Here, in the present embodiment, the data configurations of storage unit 120, user information storage unit 121, and wallet information storage unit 122 will be described.

The storage unit 120 stores transaction authorization (approval) when a credit card user purchases a product or service at a member store, and various data necessary for depositing money into an account. Storage unit 120 includes user information storage unit 121 and wallet information storage unit 122 . Furthermore, the storage unit 120 temporarily stores the contents and information acquired from the user terminals 200A and 200B and the store terminal 300 via the communication interface 204 . Note that a database (not shown) storing various data may be constructed outside the storage unit 120 .

The user information storage unit 121 stores user data 1000 relating to users, an example of which is shown in FIG. FIG. 4 shows an example of one user (user identified by user ID "10001") for convenience of explanation, but information of a plurality of users can be stored. As shown in FIG. 4, user data 1000 includes registration information, card information, credit information, and account information in association with a user ID. The registration information includes, for example, the user's registration information (in the case of a corporation, the corporation name, representative name, address, contact information, etc. In the case of an individual or employee, the name, date of birth, gender, address , and contact information (telephone number, e-mail address, etc.), and in the case of an employee, may further include employee ID, department, etc.). The card information includes information such as card number (PAN), card member name, expiration date (EXP), security code (CAV/CVC2/CVV2/CID, etc.), personal identification number (PIN, etc.), and track record. The credit information includes information such as bank account balance, electronic money balance, and credit limit. The account information includes information on the user's charging source, credit card information, debit card information, bank account information, virtual currency account information, carrier payment information, wallet information, point information, and the like.

The wallet information storage unit 122 stores wallet information (wallet data 2000), an example of which is shown in FIG. Wallet information is various data related to the wallet associated with the user's credit card. In FIG. 5, for convenience of explanation, an example of one wallet (a wallet identified by wallet ID "20001") is shown, but information of a plurality of wallets can be stored. As shown in FIG. 5, the wallet data 2000 includes wallet type information, owner information, shared user information, balance information, and transaction history information in association with the wallet ID. The wallet type information includes, for example, the type of target wallet (for example, the type of personal account associated with an individual user, the type of shared account associated (shared) with multiple users, etc.). In the case of a shared account, the owner information includes information such as the user ID of the owner of the shared wallet in question, the corporate name (if the owner is an individual, the name), and contact information. The shared user information includes information such as the user ID of the user set as the user of the target shared wallet, the corporate name (the full name in the case of an individual), and the like. The balance information includes information such as wallet balance. The transaction history information includes information such as date and time of use, user who made the payment (user information such as user ID and name), amount used, payee, payment method (single payment, installment payment, etc.).

FIG. 6 is an explanatory diagram showing an example of user data stored in the server terminal 100. As shown in FIG. As shown in FIG. 6, each user's user ID (for example, users "A", "B", and "C" are stored in association with a credit card number. , is associated with status information (for example, "completed" or "uncompleted") as to whether or not the identity verification of the user has been completed.The identity verification information, which will be described in detail later, determines whether or not the shared account can be used. Here, personal identification is a necessary procedure for the purpose of preventing money laundering, etc. When registering for use, in order to confirm that the registrant is the user himself/herself, personal identification such as a driver's license It is possible to request the transmission of image data of documents.

FIG. 7 is an explanatory diagram showing an example of wallet data stored in the server terminal 100. As shown in FIG. As shown in FIG. 7, as wallet data, user IDs (for example, users "A" and "B"), wallet IDs (for example, "AA", "AB", "BB", etc.), wallet balance, point balance , wallet type (e.g., individual or shared (participation attribute of shared account (owner OR participation)), payment settings (settings for specifying wallets for payment when making credit card payments), automatic recharge settings for wallets (e.g., "Valid or "impossible") are stored in association with each other.In FIG. , indicating that user A is a participating user.

A wallet ID is assigned to each wallet and stored in association with the user ID. A plurality of wallet IDs are stored in association with one user ID. User IDs and wallet IDs are associated in a 1:N (many) relationship. That is, multiple wallet IDs are associated with one credit card information associated with a user ID. In this way, credit card information and wallet IDs have a 1:N (many) relationship. Also, the wallet ID has information on the balance of money deposited into the account.

A point is a point given based on the use of a credit card. Points are given only to the wallet type "individual" and not to the wallet type "shared". In FIG. 7, wallet ID "AA", which is an individual account, has 1200 points, and wallet ID "AB", which is a shared account, has no point balance. Points are awarded to personal accounts regardless of the account used for payment. Points can be awarded to individual accounts, but not to shared accounts. Points are given by using a credit card. For example, it is given based on the number of times of use, frequency of use, amount of use, use at a specific store, and the like. Payment by credit card is an act performed by an individual. Therefore, it is preferable to give points, which are incentives for use, to individuals. For example, in the case of a configuration in which points are not awarded when payment is made using the balance of the shared account, points will be awarded differently between payments made using the balance of the personal account and payments made using the shared account. In this way, regardless of the type of account used for payment, points can be awarded by giving points to the personal account regardless of whether the account used for payment is a personal account or a shared account. Therefore, it is possible to provide a credit card payment technique that is highly convenient for users.

The wallet type has three types of "individual", "shared (owner)", and "shared (participant)". The wallet type “individual” is a personal account and means an account that cannot be shared with other users. Only one user associated with a personal account can make payments using the balance of the personal account. In FIG. 7, only user A can make a payment using the balance of wallet ID "AA". The wallet types "shared (owner)" and "shared (participating)" are shared accounts, meaning accounts shared with other users. Multiple users associated with the shared account can make payments using the balance of the shared account. In FIG. 7, users A and B can make payments using the balance of the wallet ID "BB". The difference between the wallet types “share (owner)” and “share (participate)” will be described later.

The payment setting is a setting for preliminarily designating a wallet ID for payment when payment is made using a credit card. The server terminal 100 accepts selection of a payment wallet for credit card payment from the user terminal 200 . In FIG. 7, user A can select a payment wallet from wallet IDs "AA", "AB", and "BB" associated with the user ID. In this embodiment, the wallet ID "BB" is selected as the settlement account of user A (the settlement setting is set to "ON"). In this way, the user can select in advance a payment wallet for payment using the credit card he/she owns. The user can select from a plurality of accounts for settlement even if the settlement is made using one credit card. Therefore, a highly convenient credit card payment technology can be provided.

Automatic recharge is a function of automatically depositing money into an account from a deposit source (bank account, credit card, etc.) set in advance by the user, without the user's instruction to deposit each time. For example, when the balance of the account becomes equal to or less than the amount set in advance by the user, the money is automatically deposited. Alternatively, if it is determined that the balance of the account is insufficient at the time of settlement, the insufficient amount or the amount set by the user is automatically deposited. Here, when automatic charging is "effective", automatic charging is performed. If automatic charging is "disabled", automatic charging is not performed. If automatic charging is "impossible", automatic charging cannot be set. Auto-charge is configurable for individual accounts, but not for shared accounts. A shared account is shared by a plurality of users and used for settlement, and if it is possible to set automatic deposit, there is a possibility that unforeseen circumstances may arise for the user who has set the automatic deposit. On the other hand, if both the personal account and the shared account are configured so that automatic payment cannot be made, the convenience of the personal account is reduced. Therefore, it is possible to provide a highly convenient credit card settlement technology by changing the settings related to automatic payment between the personal account and the shared account.

FIG. 8 is an explanatory diagram showing an example of shared wallet data stored in the server terminal 100. As shown in FIG. As shown in FIG. 8, user IDs of participating users (eg, users “A”, “B”, “C”), participating User attributes (e.g., "owner", "participated", "waiting to participate"), identity verification completion status for credit card user registration (e.g., "done", "not yet"), payment settings (credit card payment A setting that designates a wallet for settlement at a time), and the credit card number of each participating user is associated and stored. In this figure, wallet ID "AB" is a shared account shared by user A, user B and user C. User A is the owner of wallet ID "AB". Also, the wallet ID is stored in association with the credit card of each owner or participating user. In this way, multiple user IDs are stored in association with the wallet ID of one shared account. Wallet IDs and user IDs of shared accounts have a 1:N (many) relationship. That is, a plurality of credit card information are associated with one shared account information. In other words, the wallet ID and credit card information of the shared account also have a 1:N (many) relationship.

Participating users have three attributes: "owner", "participated", and "waiting for participation". A participating user's attribute "owner" means that he or she is the creator of the shared account. A participating user's attribute "participated" means that he or she is a participant in the shared account, not the creator of the shared account. Participation in a shared account is accomplished by receiving an invitation to join the shared account from the owner of the shared account or another participant. If a user who has been invited to a shared account can select the shared account as a settlement account, the attribute of the participating user is "participated". If the invitation to the shared account is received, but the shared account cannot be selected as the settlement account, the attribute of the participating user becomes "waiting for participation". Invitation to a shared account can be made by a user whose attribute of a participating user is "owner" or "participated". Here, invitation and participation in the shared account are configured to be possible only for users whose identities have been verified. In this way, only users whose identities have been verified can join or be invited to the shared account, ensuring the security of the shared account.

As described above, the payment setting is a setting for designating a wallet ID (account) for payment when payment is made using a credit card. In FIG. 8, user B has set the payment setting to "ON" for wallet ID "AB", which is a shared account. In this case, when user B makes a payment using user B's credit card, the payment is made using the balance of wallet ID "AB", which is a shared account. In addition, user A sets the payment setting to "OFF" for wallet ID "AB", which is a shared account. In this case, even if user A makes a payment using user A's credit card, the payment is not made using the balance of wallet ID "AB", which is a shared account.

FIG. 21 is a diagram schematically showing the relationship between user IDs (credit card information) and wallet IDs, and the relationship between shared wallet IDs and user IDs (credit card information). In this way, one user ID (credit card information) is associated with a plurality of wallet IDs, and the user IDs (credit card information) and wallet IDs have a 1:N (many) relationship. Therefore, for example, in FIG. 21, even if user A uses the credit card information of 1, he can use the balance of the account (wallet ID: D, E, or F) selected by the user to make the payment. . A plurality of user IDs (credit card information) are associated with the wallet ID of one shared account. The shared account wallet ID and user ID (credit card information) have a 1:N (many) relationship. Therefore, for example, in FIG. 21, using the balance of one joint account (wallet ID: F), a plurality of users (user IDs: B and C) can make payments using their own credit card information. In this way, it is possible to provide a highly convenient settlement technology for settlement using one credit card.

FIG. 9 is an explanatory diagram showing an example of transaction history information stored in the server terminal 100. As shown in FIG. As shown in FIG. 9, for each transaction ID indicating a transaction such as deposit/withdrawal and settlement related to a wallet, a wallet ID (for example, "AB", "AA") related to the transaction, a transaction amount, User ID related to the transaction (for example, user "A", "B"), usage category (for example, in the case of payment, the purpose of use ("food expenses", "transportation expenses", "shopping", etc.), deposit and withdrawal In that case, the type (for example, "deposit", "remittance", "withdrawal", "transfer", etc.) and the wallet ID (personal account of the user who performed the transaction) to which points are given are associated. In this figure, for example, transaction ID "xxxx1" is a transaction related to wallet ID "AB", 700 yen is settled by user A for "food expenses", and points are transferred to user A's personal account. Indicates that it has been granted. The use may be guessed based on the store code of the member store acquired from the store terminal 300 at the time of credit card payment.

The above is the description of the data structure of the data stored in the server terminal 100 .

Here, functions of the control unit 130, the request reception unit 131, the user information processing unit 132, and the wallet information processing unit 133 in this embodiment will be described.

As functions of the control unit 130, a request reception unit 131 that receives instructions from the user terminals 200A and 200B or the store terminal 300, and a user that refers to the user information related to the credit card of the card user and executes a predetermined process. It includes an information processing unit 132 and a wallet information processing unit 133 that refers to the wallet information associated with the credit card of the card user and executes a predetermined process.

For example, the request receiving unit 131 is a user interface displayed via an application installed in the user terminal 200, for example, when the user registers user information, issues a virtual card or a real card, and performs a predetermined operation. When making a request, the request is accepted from the user terminal 200 via the communication unit 110 . Further, for example, when the user purchases a product or service using a card at a member store, reads the magnetic card with the reader of the store terminal 300, and transmits an authorization telegram to request authorization, A request is accepted from the store terminal 300 via the communication unit 110 .

The user information processing unit 132 performs a predetermined process, which will be described later, upon receiving a request related to credit card registration and payment from the user terminal 200 used by the credit card user.

The wallet information processing unit 133 performs predetermined processing, particularly when receiving a request for registration or payment related to a wallet among processing related to a credit card.

The control unit 130 can also have a screen generation unit (not shown), and generates screen information to be displayed via the user interfaces of the user terminal 200 and the store terminal 300 upon request. For example, by using image and text data (not shown) stored in the storage unit 120 as materials and arranging various images and text in a predetermined area of the user interface based on predetermined layout rules, to create a user interface (such as a dashboard) for visualizing information related to credit cards and wallets. Processing related to the screen generator can also be executed by a GPU (Graphics Processing Unit).

FIG. 10 is a diagram showing a hardware configuration example of the user terminal 200 of this embodiment. The user terminal 200 includes a CPU 201 , a memory 202 , a storage device 203 , a communication interface 204 , an input device 205 and an output device 206 . The CPU 201 is an arithmetic unit that controls the overall operation of the user terminal 200, controls transmission and reception of data between elements, executes applications, and performs information processing necessary for authentication processing. For example, the CPU 201 is a processor such as a CPU (Central Processing Unit), and executes each information processing by executing a program stored in the storage device 203 and developed in the memory 202 . The memory 202 includes a main memory composed of a volatile memory device such as a DRAM (Dynamic Random Access Memory) and an auxiliary memory composed of a non-volatile memory device such as a flash memory, a HDD (Hard Disc Drive), a solid state drive, and the like. and including. The memory 202 is used as a work area for the CPU 201, and stores a BIOS (Basic Input/Output System) executed when the user terminal 200 is started, various setting information, and the like. The storage device 203 is, for example, a hard disk drive, solid state drive, flash memory, etc., which stores various data and programs. The communication interface 204 is an interface for connecting to the network NW. Examples include a USB (Universal Serial Bus) connector and an RS232C connector for serial communication. The input device 205 is a device that accepts data input through a keyboard, mouse, touch panel, button, microphone, or the like, for example. The output device 206 includes, for example, a display, printer, speaker, etc. for outputting data.

FIG. 11 is a block diagram showing the functional configuration of the user terminal 200. As shown in FIG. As shown in FIG. 11 , the user terminal 200 includes a communication section 210 , a display operation section 220 , a storage section 230 and a control section 240 .

Note that each of the functional units described above is implemented by the CPU 201 provided in the user terminal 200 reading a program stored in the storage device 203 into the memory 202 and executing it, and the storage unit 230 is implemented by the memory 202 provided in the user terminal 200. and part of the storage area provided by the storage device 203 .

The communication unit 210 is a communication interface for communicating with the server terminal 100 via the network NW, and communication is performed according to a communication protocol such as TCP/IP.

The display operation unit 220 is a user interface used by the user to input instructions and display text, images, etc. according to input data from the control unit 240, and the user terminal 200 is configured by a personal computer. When the user terminal 200 is a tablet terminal, it is composed of a touch panel and the like. The display operation unit 220 is activated by a control program such as an application program stored in the storage unit 230 and executed by the user terminal 200, which is a computer (electronic calculator).

The storage unit 230 stores programs, input data, and the like for executing various control processes and functions in the control unit 240, and is composed of RAM, ROM, and the like. The storage unit 230 also temporarily stores the content and information acquired from the server terminal 100 via the communication interface 204 .

The control unit 240 controls the overall operation of the user terminal 200 by executing programs stored in the storage unit 230, and is composed of a CPU, a GPU, and the like.

Note that the server terminal 100 may have all or part of the functions of the control program such as the application program stored in the user terminal 200 .

FIG. 12 is a diagram showing a hardware configuration example of the shop terminal 300 of this embodiment. The store terminal 300 includes a CPU 301 , a memory 302 , a storage device 303 , a communication interface 304 , an input device 305 and an output device 306 . The CPU 301 is an arithmetic unit that controls the overall operation of the store terminal 300, controls transmission and reception of data between elements, executes applications, and performs information processing necessary for authentication processing. For example, the CPU 301 is a processor such as a CPU (Central Processing Unit), and executes each information process by executing a program stored in the storage device 303 and developed in the memory 302 . The memory 302 includes a main memory composed of a volatile memory device such as a DRAM (Dynamic Random Access Memory), and an auxiliary memory composed of a non-volatile memory device such as a flash memory, a HDD (Hard Disc Drive), a solid state drive, and the like. and including. The memory 302 is used as a work area for the CPU 301, and stores a BIOS (Basic Input/Output System) executed when the store terminal 300 is started, various setting information, and the like. A storage device 303 is, for example, a hard disk drive, a solid state drive, a flash memory, or the like, which stores various data and programs. The communication interface 304 is an interface for connecting to the network NW. Examples include a USB (Universal Serial Bus) connector and an RS232C connector for serial communication. The input device 305 is a device that accepts data input through a keyboard, mouse, touch panel, button, microphone, or the like, for example. The output device 306 includes, for example, a display, printer, speaker, etc. for outputting data.

FIG. 13 is a functional block configuration diagram showing the store terminal 300. As shown in FIG. The store terminal 300 includes a communication section 310 , a display operation section 320 , a storage section 330 , a reader 340 and a control section 350 .

Note that each of the functional units described above is implemented by the CPU 301 of the shop terminal 300 reading out a program stored in the storage device 303 into the memory 302 and executing it. and part of the storage area provided by the storage device 303 .

The communication unit 310 is a communication interface for communicating with the server terminal 100 (with an international brand card system (not shown) when passing through an international brand card system) via the network NW. Communication is performed according to a communication protocol such as IP.

The display operation unit 320 is a user interface used by a store clerk to input instructions and display text, images, etc. according to input data from the control unit 350. If it is a CAT terminal, it is composed of a display, buttons, a pointing device, a keyboard, etc. If it is composed of a personal computer, it is composed of a display, a keyboard, a mouse, etc. If the store terminal 300 is composed of a tablet terminal is composed of a touch panel and the like. The display operation unit 320 is activated by a control program such as an application program stored in the storage unit 330 and executed by the store terminal 300, which is a computer (electronic calculator).

The storage unit 330 stores programs, input data, and the like for executing various control processes and functions in the control unit 350, and is composed of RAM, ROM, and the like. Further, the storage unit 330 temporarily stores communication contents with the server terminal 100 .

The reader 340 is composed of devices such as a magnetic card reader, bar code reader, IC chip reader, NFC tag reader, etc., and can read information on prepaid cards, credit cards, debit cards, and the like.

The control unit 350 controls the overall operation of the store terminal 300 by executing programs stored in the storage unit 330, and is composed of a CPU, a GPU, and the like.

<Process flow>
With reference to FIG. 14, the processing flow of the credit card providing method executed by the system 1 of the present embodiment will be described. FIG. 14 is a flow chart of an example of a credit card providing method according to the first embodiment of the present invention.

<Credit card issuing process>
Here, first, as an example, the user installs an application on his/her own user terminal 200 in order to issue a credit card. The user activates the installed application, registers the registration information on the provided user interface, and requests issuance of a credit card. As a credit card, a credit card that does not physically exist and is displayed via an application installed on a mobile terminal such as a smartphone by the user, which is called a virtual card, is issued. In addition, the credit card company can also issue a physical credit card with a built-in magnetic or IC chip, which is called a real card, at the request of the user. A credit card issued to each user is first associated with a personal account for use by the individual user. Then, the user uses the application in advance to select the desired deposit source information (for example, credit card information, debit card information, bank account information, virtual currency account information, carrier payment information, etc.) and deposit a predetermined amount in advance. It is also possible to deposit money in cash using an ATM installed in a store such as a convenience store. Here, when the user's card is issued, the registration information and credit card account information input by the user are stored as user data 1000 in the user information storage section 121 of the storage section 120 of the server terminal 100 . Further, identity confirmation is performed through a predetermined process to determine whether the user information registered as user information is a genuine user. Contains status information. Note that the credit card described in the present embodiment has been described as an example in which a predetermined amount is deposited in advance into an account and payment is made using the deposited balance, but the present invention is not limited to this. It also includes a prepaid credit card used by charging electronic money equivalent to a predetermined amount in advance. It also includes a credit card that withdraws the settlement amount from a bank account at a predetermined timing after the credit card is used for settlement.

<Create shared account>
Assuming that the credit card has been registered, first, as the shared account generation process, as the processing of SQ101, the request reception unit 131 of the server terminal 100 receives the credit card user A, who is the credit card user, A shared account creation request is received from the user terminal 200A to be used.

Here, a shared account is issued separately from a personal account that can be traded only by the user himself/herself. A shared account is an account that can be shared with other users and that can be used for settlement with a shared user who is a user sharing another account. That is, a personal account is associated with the user's own single credit card, whereas a shared account is associated with multiple credit cards, including the user's own and other shared users. This embodiment is characterized in that the user can make payments from the shared account when using the credit card by setting the shared account as the settlement account when using the credit card or in advance. Here, the control unit 130 stores and manages the user who made the shared account creation request in the wallet data as the "owner" of the shared account.

Next, as processing of SQ102, the server terminal 100 generates a shared account based on the user A's request. The wallet information processing unit 133 reads the user information of the user A whose request has been received from the user information processing unit 132 and generates a shared account wallet ID based on the user data stored in the user information storage unit 121 . Wallet information processing unit 133 stores the generated shared account information as wallet data associated with user A in wallet information storage unit 122 of storage unit 120 .

Next, as the process of SQ103, the wallet information processing unit 133 of the server terminal 100 notifies the user terminal 200A via the communication unit 110 that the shared account has been created.

<Invitation to shared account>
Next, the shared account invitation process will be described. As the process of SQ201, the request receiving unit 131 receives the invited user information (user ID, etc.) and the invited shared account information (shared account ID) from the user terminal 200A used by the user A via the communication unit 110. do. For example, a request from user A to invite user B to a shared account is received. When inviting to a shared account, a user whose participating user attribute is "owner" or "already attended" in the shared wallet data of the shared account that invites can invite other users to the shared account. In this way, even if the user is not the owner, other users can be invited to the shared account, so a highly convenient credit card payment technique can be provided.

Next, as the processing of SQ202, the user information processing unit 132 refers to the user data 1000 stored in the user information storage unit 121, and confirms the information on the invited user ("user B" in this example). . Here, the user information processing unit 132 confirms by referring to the user data 1000 whether the user B to be invited is a user whose identity has been confirmed.

Next, as the process of SQ203, the wallet information processing unit 133 transmits an invitation notification of the shared account to the user terminal 200B used by the user B via the communication unit 110. FIG.

Next, as the processing of SQ204, the request receiving unit 131 of the server terminal 100 receives a request to participate in the shared account from the user terminal 200B (and if the identity verification in the above SQ202 is "not yet", the identity verification in this processing). receive the information necessary for In this way, since only users whose identity has been verified can participate in the shared account, the security of the shared account is ensured.

Next, as the process of SQ205, the wallet information processing unit 133 performs the process of associating the user information regarding the user B who made the participation request with the shared account. For example, as shown in FIG. 8, a process of registering user B as a participating user of a shared account with wallet ID "AB" created by user A as the owner is performed. If the user who has been invited to the shared account is not the "owner" user of the shared account, before registering as a participating user of the shared account, the user may confirm with the "owner" user whether or not to participate.

Next, as the process of SQ206, the wallet information processing unit 133, via the communication unit 110, sends the user terminal 200A of the user A who invited and the user terminal 200B of the user B who invited the Send notification that you have joined the account. A notification to the effect that a new user has been registered for participation may be sent to the user terminals of all users who share the wallet, not just the user who actually invited them.

<Settlement account selection>
Next, as the process of selecting a settlement account, as the process of SQ301, the request receiving unit 131 receives a wallet information acquisition request from the user terminal 200A of the user A via the communication unit 110. FIG. In response to this, as the processing of SQ302, the wallet information processing unit 133 refers to the wallet data associated with user A stored in the wallet information storage unit 122, and acquires wallet information with which user A can make payment settings. do. Wallet information processing unit 133 transmits the acquired wallet information to user terminal 200A via communication unit 110 .

Next, as the process of SQ303, the request receiving unit 131 receives a payment account selection request from the user terminal 200A via the communication unit 110. FIG. As the processing of SQ303, for example, if the wallet selected by user A is a shared account, the wallet information processing unit 133 of the server terminal 100 refers to the wallet data in the wallet information storage unit 122 and sets the settlement account as the shared account. make changes like this: That is, the payment setting associated with the selected wallet ID is changed from "OFF" to "ON". Then, as the process of SQ305, the wallet information processing section 133 transmits a notification to the effect that the settlement account has been changed to the user terminal 200A via the communication section 110. FIG. The user terminal 200</b>A acquires the wallet information in which the settlement account is set from the server terminal 100 through communication, and stores it in the storage unit 230 . In this way, the user can select the payment wallet for the credit card he or she holds. Therefore, even if the same credit card is used for settlement, the user can select from a plurality of accounts for settlement. Therefore, a highly convenient credit card payment technology can be provided.

<Payment (transfer)>
An example of another credit card offering technique will now be described with reference to FIG. First, as a deposit (transfer) process, which is an example of transaction processing, as the process of SQ401, the request reception unit 131 receives the deposit (transfer) destination wallet information from the user terminal 200A of user A via the communication unit 110 and receive a deposit (transfer) request, including amount information;

Next, as the processing of SQ402, the wallet information processing unit 133 refers to the wallet data stored in the wallet information storage unit 122, and also accesses the wallet data stored in the user information storage unit 121 via the user information processing unit 132. While referring to the user information, a process of depositing (transferring) the requested amount from the deposit source specified by the user to the deposit destination specified by the user is performed. The wallet information processing unit 133 updates the transaction history information of the wallet data stored in the wallet information storage unit 122 with the balance information after payment.

Next, as the process of SQ403, the wallet information processing unit 133 of the server terminal 100 notifies the user terminal 200A of the user A via the communication unit 110 that the money has been deposited and the amount of money deposited.

Explain the difference between depositing (transferring) to an individual account and a shared account. Here, in this example, deposit or withdrawal means transfer of balance between a deposit/withdrawal source (bank account, credit card, ATM, etc.) outside the system 1 and an account on the system 1. do. A transfer means a transfer of a balance between accounts on the credit card providing system 1, for example, between a personal account and a shared account.

A personal account is configured to allow deposits, withdrawals and transfers. In other words, the personal account can deposit and withdraw money to and from outside the system 1 (bank account, credit card, ATM, etc.). Shared accounts, on the other hand, allow transfers but cannot deposit or withdraw funds. That is, when increasing or decreasing the balance of the shared account, the balance is transferred from the balance of the personal account on the system 1 or to the balance of the individual account. A personal account is an account associated with a user. By limiting the increase/decrease in the balance of the shared account, it is possible to clarify which user caused the increase/decrease in the balance of the shared account.

When a predetermined transaction such as deposit or transfer is executed in the personal account, the wallet information processing unit 133 notifies the user terminal of the individual user that the predetermined transaction such as deposit or transfer has been performed. Send notifications. On the other hand, the wallet information processing unit 133, when a predetermined transaction such as a transfer is executed to the shared account, not only the user who actually made the transaction, but also the user terminals of all users who share this wallet. , a notification is sent to the effect that a predetermined transaction such as deposit or transfer has been performed. In this way, by changing the notification method for a predetermined transaction between the personal account and the shared account, it is possible to appropriately notify the user of the occurrence of the predetermined transaction.

<Withdrawal (transfer)>
Next, transfer from a shared account to a personal account will be described as a withdrawal (transfer) process as an example of a transaction. As the process of SQ501, the request receiving unit 131 sends the wallet information of the withdrawal source (in this example, the shared account owned by the user A) and the amount information from the user terminal 200A of the user A via the communication unit 110. , receives a withdrawal (transfer) request. It should be noted that user A cannot make a withdrawal request to a bank account or the like of a withdrawal destination outside the system 1 for the shared account. User A can make a withdrawal request to a bank account or the like outside the system 1 for a personal account.

Next, as the processing of SQ502, the wallet information processing unit 133 refers to the wallet data stored in the wallet information storage unit 122, and also accesses the wallet data stored in the user information storage unit 121 via the user information processing unit 132. While referring to the user information, the user A performs a process of withdrawing (transferring) the requested amount from the shared account of the "owner" to the user A's personal account. The wallet information processing unit 133 updates the balance information of the wallet data stored in the wallet information storage unit 122 with the balance information after withdrawal.

Next, as the processing of SQ503, the wallet information processing unit 133, via the communication unit 110, sends the user terminal 200A of the user A and the user B, who is a participant of the shared account, a withdrawal from the shared account. and information on the withdrawal amount. As a feature of this example, when a predetermined transaction such as withdrawal is executed to a shared account, not only the user who actually made the transaction but also the user terminals of all users who share the wallet , a notification is sent that the transaction has taken place.

<Withdrawal/deletion from shared account>
Next, as the process of withdrawing from the shared account, as the process of SQ601, the request receiving unit 131 requests, via the communication unit 110, from the user terminal 200B of the user B who participates in the shared account that he/she withdraws from the shared account. receive.

Next, as the processing of SQ602, the wallet information processing unit 133 of the server terminal 100 refers to the wallet data stored in the wallet information storage unit 122. FIG. Next, wallet information processing section 133 refers to the user information stored in user information storage section 121 . The wallet information processing unit 133 confirms the attributes of the user B who requested to leave the shared account. For example, as shown in FIG. 8, if the user B is not the "owner" of the shared account "AB", the wallet information processing unit 133 performs the process of withdrawing the user B from the shared account. On the other hand, if user B is the "owner" of the shared account "AB", the wallet information processing unit 133 does not perform the process of withdrawing user B from the shared account. In this way, the wallet information processing unit 133 determines whether or not to allow the exit process based on the attributes of the user who requests the exit. Therefore, it is possible to prevent other users participating in the shared account from being unintentionally disadvantaged due to the withdrawal process from the shared account. Subsequently, as the processing of SQ603, the wallet information processing unit 133 performs the withdrawal processing from the shared account of the user who made the withdrawal request based on the confirmation result in the processing of SQ602.

Next, as the processing of SQ604, the wallet information processing unit 133, via the communication unit 110, sends user terminal 200A of user A and user B who is a participant in the shared account Notify the information that you have left. A feature of this example is that when a user participates in or withdraws from a shared account, participation Alternatively, a notification is sent to the effect that the exit has been made.

As described above, the process of exiting from the shared account has been described, but deletion of the shared account itself can be made possible by a request made only by the "owner" user who created the shared account. In this case, if there is a balance amount deposited in the shared account, other participants of the wallet will be disadvantaged, so it is possible to delete only when the balance is zero yen.

A case where settlement using the balance of the shared account is refunded later will be explained. If the shared account is not deleted at the time of refund, the refund will be made to the shared account where the payment was made. If the shared account has been deleted at the time of refund, refund processing is performed for the personal account of the user who was the "owner" of the shared account for which the payment was made. In this way, even if the shared account is deleted, the refund process can be reliably executed.

<Payment>
Next, settlement processing, which is an example of transaction processing, will be described with reference to FIG. In this example, an example will be described in which user A visits a store and uses a credit card to make payment in exchange for goods or services provided at the store. Specifically, User A uses a credit card to purchase goods or services at a credit card affiliated store. In this case, when a user purchases a product or service at a physical store, the user presents a physical credit card called a real card to the person in charge of the store. When a user uses the user terminal 200 or the like to purchase a product or service at an online store or the like, an application on the user terminal 200 displays information about a credit card that does not physically exist, which is called a virtual card. Enter the purchase screen of the store. The same credit card information can be used for the real card and the virtual card. In this way, by using the same credit card information, it is possible to provide a highly convenient credit card technology that reduces the user's management burden.

First, as the processing of SQ701, the store terminal 300 of the affiliated store where the user A uses the credit card performs the payment operation for the product or service, and transmits an authorization request for the transaction of the product or service to the server terminal 100. For example, in the case of an online store, the store terminal 300 accepts a purchase request for a product or service from the user terminal 200 via the network and performs payment processing. Also, in the case of a real store, the store terminal 300 makes a terminal such as POS/CCT/CAT read the credit card and performs settlement processing.

Next, as the process of SQ702, the wallet information processing section 133 receives predetermined payment information from the shop terminal 300 via the communication section 110. FIG. Information included in the payment information includes, for example, credit card information, member store ID, date and time, amount used, and the like.

Next, as the processing of SQ703, the user information processing section 132 refers to the user data stored in the user information storage section 121 based on the credit card information included in the received payment information, and acquires user information. Subsequently, as the processing of SQ704, the wallet information processing unit 133 refers to the wallet data stored in the wallet information storage unit 122 for the wallet information associated with the user information, and refers to the wallet information related to the credit card payment. Get account information. As the processing of SQ705, the wallet information processing unit 133 acquires the balance information of the wallet set as the settlement account (the settlement setting is set to "ON") while referring to the wallet data. Here, if the settlement account is set to a personal account and the settlement amount is greater than the balance of the personal account, if the wallet is set to be automatically charged in advance, the wallet information processing The unit 133 performs a process of charging the insufficient amount of money or the predetermined amount of money. Here, if automatic deposit (charging) is not set for the personal account, the insufficient amount cannot be charged, so the wallet information processing unit 133 determines an error in the payment. Also, if the settlement account is set as a shared account and the settlement amount is equal to or greater than the balance of the account, automatic deposit (charge) is not set for the shared account. Therefore, the wallet information processing unit 133 determines that the payment is an error because the insufficient amount cannot be charged.

Next, in the process of SQ705, if it is determined that the payment is possible, the wallet information processing unit 133 makes the payment based on the wallet information as the process of SQ706. For example, when the settlement account is set as a shared account, the wallet information processing unit 133 refers to the wallet data stored in the wallet information storage unit 122, and subtracts the usage amount from the shared account owned by user A. and update the transaction history information. For example, as shown in FIG. 9, when user A purchases a product for 700 yen as food expenses at a member store and makes a credit card payment, the information to the effect that 700 yen has been subtracted from the shared account "AB" is updated. . In the present example, the case where the payment is made directly from the shared account has been described, but the present invention is not limited to this. For example, if the settlement account is set as a shared account, the settlement amount may be automatically transferred from the shared account to the personal account, and finally settled from the personal account. Regardless of the mode, it is sufficient that the settlement amount is reduced from the balance of the shared account set as the settlement account, and the settlement is performed.

In this way, basically, the settlement is completed when the user uses the credit card, and the settlement amount is immediately subtracted from the balance amount deposited in the shared account. Transactions in which settlement is performed after a certain period of time has passed are also conceivable. For example, when a small amount of payment is made at the time of service registration, such as a monthly service, and then the payment for the service usage fee is made, or when an option is added after purchasing the product, it is different from when using a credit card. Payment may be made at a later date. In this case, all the participants of the shared account are notified that the settlement will not be made when using the credit card (for example, "transaction without deduction when crediting"). In this way, it is possible to eliminate the anxiety of the user due to the fact that the payment is not immediately made (the balance is not subtracted).

In addition, in order to confirm the validity of the credit card as a transaction with the affiliated store, when the credit card is used, the store will formally request payment of a certain amount, confirm the validity of the credit card, and confirm the amount used. We may refund the difference. Even in such a case, the user's anxiety can be eliminated by notifying all the participants of the shared account that it is a temporary payment for confirming the validity of the card.

Next, as the process of SQ707, the wallet information processing unit 133 performs the process of giving points to the user who made the payment. In this example, the wallet information processing unit 133 performs a process of giving points to the personal account of user A, who actually made the payment, even if the shared account is set as the payment account. The wallet information processing unit 133 refers to the wallet data stored in the wallet information storage unit 122, and performs a process of updating the points given to the personal account of the user A. For example, as shown in FIG. 9, points are given to user A's personal wallet "AA" in response to payment of 700 yen for meals using the shared account "AB". In this way, by giving points directly to the personal account of the user who actually made the payment, fairness can be ensured. Here, it is preferable that points can be given to individual accounts, but not given to shared accounts. Points are given as incentives by using a credit card, for example, the number of times of use, frequency of use, amount of use, use at a specific store, and the like. Even when the shared account is set as the settlement account and the settlement is made, the incentive of the user to use the credit card is ensured by giving points to the personal account. In this example, an example in which points are given to a personal account has been described, but the points to which points are given are not limited as long as the points can be used only by individual users using credit cards. For example, dedicated account (wallet) information for managing points may be generated and points may be given to that account. Thus, the wallet information processing unit 133 gives points to individual users.

Next, as the processing of SQ708, the wallet information processing unit 133 makes payment by the shared account for the user terminal 200A of the user A and the user B who is a participant of the shared account via the communication unit 110. Notifies you of the information to the effect that it has been As a feature of this example, when a predetermined transaction such as payment is executed to a shared account, not only the user who actually made the transaction, but also the user terminals of all users who share this wallet, A notification is sent that the transaction has taken place.

Here, when the user A activates the credit card application installed in the user terminal 200A and performs an operation for using the wallet for transactions such as payment, as shown in FIG. Information about the account is displayed. As shown in FIG. 17, as information about personal accounts, balance information, deposit source information (e.g., designated bank account), transaction history information (e.g., deposit/withdrawal and settlement information, deposit source, store used, etc.) is displayed.

In order to select a shared account, User A performs a predetermined operation (for example, selects an arrow icon (901) displayed on the screen, selects an arrow icon (901) displayed on the screen, and ), information about the shared account is displayed on the screen as shown in FIG. In this way, the user can transition to a desired screen by a simple operation method such as one-tap or swipe on the wallet-related application screen in order to refer to the information about the shared account.

Balance information and transaction history information (for example, information on deposits/withdrawals and settlements, information on deposit sources, stores used, etc.) are displayed on the screen that displays information on the shared account. Regarding the transaction history information of the shared account, unlike the personal account, information that identifies the user who made the transaction (for example, user name, user icon) is included so that it is easy to see which user made the transaction. Displayed as transaction history information.

When the user starts the credit card application installed in the user terminal 200, the control unit 240 of the user terminal 200 causes the user terminal 200 to display the account information. The control unit 240 changes the display of the account information associated with the user displayed on the user terminal 200 by performing a swipe operation or the like on the display operation unit 220 . At this time, the control unit 240 controls so that the account information set for the settlement account is displayed with priority over other account information. Displaying preferentially means, for example, displaying it on the screen when the application is started, displaying it by default when displaying account information, displaying it in a larger size than other account information, and using a different color from other account information. display, and so on. By doing so, the user can easily understand through the user interface which account has been set for payment among the plurality of accounts.

In addition, as shown in FIG. 18, the application screen of the shared account displays not only the payment amount and purpose of use, but also information about the user who made the payment as transaction history information. Information and display mode are different. A shared account is an account shared by a plurality of users for making payments, unlike a personal account. Therefore, each user has a need to know who has made a transaction such as settlement or transfer. In this way, when displaying the transaction history information of the shared account, unlike the personal account, by displaying the information of the user who made the transaction, it is possible to provide a highly convenient credit card technology.

In addition, as shown in FIG. 18, on the shared account screen, the message "Transfer" is displayed near the icon indicating deposit/withdrawal. Unlike a personal account, a shared account cannot directly deposit or withdraw money to a bank account set up by an individual user. You can understand the difference in functions related to deposits and withdrawals of personal accounts.

Also, based on the transaction history information in the personal account shown in FIG. 17, as shown in FIG. 19 and FIG. , as information for each predetermined period such as monthly, can be visualized and displayed using a graph such as a pie chart. As a result, the credit card user can confirm, at a glance, how much money has been used for what in the personal account, the ratio of each usage purpose, and the like.

Also, although not shown, the usage and the total amount and percentage for each usage can be similarly displayed for the shared account. Furthermore, for the shared account, it is possible to display the information of the participating users in combination. For example, it is possible to display the usage amount, usage ratio, deposit (transfer) ratio, withdrawal (transfer) ratio, etc. of each owner or participant who shares the account. In this way, based on the characteristics of each account, by visualizing and displaying information on the use of the account in a graph or the like, the user can confirm the use of the account at a glance. In other words, in the personal account, the first display that displays the information on the purpose of use and amount of money of the individual is displayed. Further, in the shared account, in addition to the first display that displays information on usage and amount, a second display that displays information on the user who has made the transaction is provided. In this way, by changing the display mode (appearance, items, number of graphs, etc.) of the transaction history information of the personal account and the transaction history information of the shared account, the user can easily see the displayed transaction history information. It is possible to understand the usage status of the account of the transaction history information.

As described above, according to the present embodiment, a credit card associated with each user is provided, and a personal account and a shared account are associated with the credit card, thereby making the credit card technology highly convenient for the user. can be provided.

Although the preferred embodiments of the present disclosure have been described in detail above with reference to the accompanying drawings, the technical scope of the present disclosure is not limited to such examples. It is obvious that those who have ordinary knowledge in the technical field of the present disclosure can conceive of various modifications or modifications within the scope of the technical idea described in the claims. is naturally within the technical scope of the present disclosure.

For example, in the present disclosure, when using a credit card, the balance of one settlement account (with the settlement setting set to "ON") selected by the user is used for settlement. can't For example, multiple settlement accounts may be selected. In this case, settlement is performed using the balances of multiple accounts (wallets) selected as settlement accounts. Furthermore, it may be configured such that a settlement rate can be set for each of a plurality of selected accounts.

An example of processing will be described. The request reception unit 131 of the server terminal 100 receives the settlement rate for each account from the user terminal 200 and stores it in the wallet information storage unit 122 . When payment is made by credit card, the wallet information processing unit 133 reads the payment ratio set by the user for each account from the wallet information storage unit 122 . The wallet information processing unit 133 makes payments from a plurality of payment accounts based on the read payment ratios. In this way, based on the settlement ratio set by the user, settlement can be made using the balances of multiple accounts (wallets). For example, by setting up a second account in advance for subsidizing a certain percentage of the payment amount, subsidies corresponding to the usage amount can be easily provided from the second account. Alternatively, the user may set the settlement amount instead of the settlement ratio. In this case, a fixed amount is settled from the first account balance, and the remaining amount is settled from the second account balance. In addition, priority is given to the use of the account (wallet) selected as the settlement account, and if the balance of the high-priority account is insufficient, the balance of the low-priority account (wallet) may be used for settlement.

For example, in the present disclosure, a case has been described where participating users of a shared account can make payments using the balance of the shared account without restrictions, but this is not the only option. For example, the user who is the “owner” of the shared account may be configured to be able to set the available amount and usage period of the shared account for each participating user.

An example of processing will be described. The request receiving unit 131 of the server terminal 100 receives the restriction information regarding the participating users of the shared account from the user terminal 200 of the user who is the “owner” of the shared account, and stores it in the wallet information storage unit 122 . The limit information includes a usage limit for each payment for each participating user, a usage limit for a predetermined period, a usage period during which payment can be made using a shared account, and the like. When payment is made by credit card, the wallet information processing unit 133 reads the participating user's restriction information from the wallet information storage unit 122 . The wallet information processing unit 133 determines whether payment can be made from the shared account based on the read restriction information. In this manner, based on the limit information set by the user who is the owner of the shared account, settlement can be made with the balance of the shared account. For example, by providing restriction information, it is possible for the owner to temporarily or for a limited time permit the use of the shared account, and to control the use (increase or decrease) of the shared account balance of the participating users of the shared account.

For example, in the present disclosure, a case has been described in which the transaction history information of the personal account and the shared account is displayed as usage or information for each predetermined period, but the present disclosure is not limited to this. For example, it may be possible for the user to add notes to the transaction history information.

An example of processing will be described. The user obtains transaction history information from the wallet information storage unit 122 of the server terminal 100 by operating the display operation unit 220 of the user terminal 200 . An arbitrary transaction is selected from the transaction history information displayed on the user terminal 200 using the display operation unit 220, and a memo is entered. The user terminal 200 transmits the memo input by the user to the server terminal 100 . The server terminal 100 stores the received memo in the wallet information storage unit 122 in association with the transaction history information. Here, it is preferable that the shared account is an account shared by a plurality of users, and the memo has contents that can be understood by others. On the other hand, a personal account is an account used by an individual user, and the contents of the memo can be understood by the user. Therefore, it is preferable to provide a difference in the amount of memo information that can be written in the transaction history information between the personal account and the shared account. Specifically, the amount of memo information that can be written in the transaction history information of the shared account is made larger than the amount of memo information that can be written in the transaction history information of the personal account. In this way, it is possible to leave a memo of the required amount of information, which is more convenient for the user.

For example, in the present disclosure, the case of transferring (depositing and withdrawing) the balances of the personal account and the shared account has been described, but the present disclosure is not limited to this. For example, not only the balance but also the transaction history information may be transferred. After the first account is set as the settlement account and the balance of the first account is used for settlement, the user may decide that the settlement should be made from the second account. In such a case, by transferring the transaction history information along with the balance, the settlement itself can be treated as if it were settled using the second account.

An example of processing will be described. The user obtains transaction history information from the wallet information storage unit 122 of the server terminal 100 by operating the display operation unit 220 of the user terminal 200 . Any transaction is selected from the transaction history information displayed on the user terminal 200 using the display operation unit 220 . Next, the user selects a transfer destination account from the accounts associated with the user and transmits a history transfer request to the server terminal 100 . When the wallet information processing unit 133 of the server terminal 100 receives the history transfer request, the wallet information storage unit 122 reads the transaction history information for the transfer. The wallet information processing unit 133 updates the balance data of the transfer destination account stored in the wallet information storage unit 122 by decreasing the amount corresponding to the settlement amount based on the settlement amount information of the read transaction history information. Next, the balance data of the transfer source account stored in the wallet information storage unit 122 is increased by the amount equivalent to the settlement amount and updated. Further, the wallet information processing unit 133 writes the content of the read transaction history information to the transaction history information of the transfer destination account, and deletes the transaction history information of the transfer source. In this way, after the settlement is made using the first account, the transaction history information and the balance are transferred between the first account and the second account by the user's operation, so that the second account is used from the beginning. can be treated as if the payment was made

The devices described herein may be implemented as a single device, or may be implemented by a plurality of devices (eg, cloud servers) partially or wholly connected via a network, or the like. For example, the CPU 101 and storage device 103 of the server terminal 100 may be implemented by different servers connected to each other via a network.

The sequence of operations performed by the apparatus described herein may be implemented using software, hardware, or a combination of software and hardware. It is possible to prepare a computer program for realizing each function of the server terminal 100 according to the present embodiment and to implement it in a PC or the like. A computer-readable recording medium storing such a computer program can also be provided. The recording medium is, for example, a magnetic disk, an optical disk, a magneto-optical disk, a flash memory, or the like. Also, the above computer program may be distributed, for example, via a network without using a recording medium.

Also, the processes described with reference to flowcharts in this specification do not necessarily have to be executed in the illustrated order. Some processing steps may be performed in parallel. Also, additional processing steps may be employed, and some processing steps may be omitted.

Also, the effects described herein are merely illustrative or exemplary, and are not limiting. In other words, the technology according to the present disclosure can produce other effects that are obvious to those skilled in the art from the description of this specification, in addition to or instead of the above effects.

1 credit card providing system 100 server terminal 101 CPU
102 memory 103 storage device 104 communication interface 105 input device 106 output device 110 communication unit 120 storage unit 121 user information storage unit 122 wallet information storage unit 130 control unit 131 request reception unit 132 user information processing unit 133 wallet information processing unit 200 user terminal 201 CPUs
202 memory 203 storage device 204 communication interface 205 input device 206 output device 210 communication unit 220 display operation unit 230 storage unit 240 control unit 300 store terminal 301 CPU
302 memory 303 storage device 304 communication interface 305 input device 306 output device 310 communication unit 320 display operation unit 330 storage unit 340 reader 350 control unit NW network

Claims (10)

A server that supports payment by credit card,
The server stores information of a first user, information of a first credit card associated with the first user, a first wallet having a first balance, and a second wallet having a second balance. a storage unit that stores
At least one of the first wallet and the second wallet is selected from the terminal owned by the first user as a wallet for settlement with the first credit card at a timing desired by the first user that is not related to settlement. a wallet selection unit that receives an instruction to
A server characterized by having: the storage unit stores information of a second user, information of a second credit card associated with the second user, and a third wallet having a third balance;
The wallet selection unit receives from the second user an instruction to select at least one of the second wallet and the third wallet as a wallet for settlement with the second credit card;
A server according to claim 1, characterized by: A server that supports payment by credit card,
The server stores information of a first user, information of a first credit card associated with the first user, a first wallet having a first balance, and a second wallet having a second balance. a storage unit that stores
a wallet selection unit that receives an instruction from the first user to select at least one of the first wallet and the second wallet as a wallet for settlement with the first credit card;
the storage unit stores information of a second user, information of a second credit card associated with the second user, and a third wallet having a third balance;
The wallet selection unit receives from the second user an instruction to select at least one of the second wallet and the third wallet as a wallet for settlement with the second credit card;
a server characterized by The settlement history of the first credit card can be viewed by the first user when settlement is made using the first wallet, and can be viewed by the first user when settlement is made using the second wallet. and is viewable by the second user;
A server according to claim 2 or 3. The server has a history display unit that displays a payment history,
The history display unit displays the payment history of the second wallet in a manner different from that of the first wallet,
A server according to any one of claims 2 to 4. The history display unit displays a settlement amount in the settlement history of the first wallet,
The payment history of the second wallet displays the payment amount and information related to the user who made the payment.
A server according to claim 5 . A computer program for assisting payment by credit card,
to the processor,
obtaining information of a first user, information of a first credit card associated with said first user, a first wallet with a balance of one and a second wallet with a second balance;
At least one of the first wallet and the second wallet is selected from the terminal owned by the first user as a wallet for settlement with the first credit card at a timing desired by the first user that is not related to settlement. receiving instructions to
computer program that causes the A method of assisting payment by credit card, comprising:
the processor
obtaining information of a first user, information of a first credit card associated with said first user, a first wallet having a first balance, and a second wallet having a second balance; ,
At least one of the first wallet and the second wallet is selected from the terminal owned by the first user as a wallet for settlement with the first credit card at a timing desired by the first user that is not related to settlement. receiving instructions to
how to run A computer program for assisting payment by credit card,
to the processor,
obtaining information of a first user, information of a first credit card associated with said first user, a first wallet having a first balance, and a second wallet having a second balance; ,
a step of receiving an instruction from the first user to select at least one of the first wallet and the second wallet as a wallet for settlement with the first credit card; information of the second user; and the second user. obtaining information for a second credit card associated with and a third wallet having a third balance;
receiving from the second user an instruction to select at least one of the second wallet and the third wallet as a wallet for settlement with the second credit card;
computer program that causes the A method of assisting payment by credit card, comprising:
the processor
obtaining information of a first user, information of a first credit card associated with said first user, a first wallet having a first balance, and a second wallet having a second balance; ,
a step of receiving an instruction from the first user to select at least one of the first wallet and the second wallet as a wallet for settlement with the first credit card; information of the second user; and the second user. obtaining information for a second credit card associated with and a third wallet having a third balance;
receiving from the second user an instruction to select at least one of the second wallet and the third wallet as a wallet for settlement with the second credit card;
how to run

Images