JP7266019B2 - program, information processing method, terminal, server - Google Patents

Description

The present disclosure relates to programs, information processing methods, terminals, servers, and the like.

Conventionally, deferred payment is often used to purchase goods and services. For example, Japanese Laid-Open Patent Publication No. 2002-200000 discloses a technique for settling the purchase price of a product.

Japanese Patent Application Laid-Open No. 2002-176671

According to a first aspect of the present invention, a program executed by a terminal receives purchase information of a product or service purchased by a user of the terminal with deferred payment by a communication unit of the terminal; and at least one of the purchase information based on the terminal user selecting the first account information among the plurality of account information. Displaying, on a display, first information relating to paying the portion with a first account associated with the first account information is performed by the terminal.
According to a second aspect of the present invention, an information processing method for a terminal includes: receiving, by a communication unit of the terminal, purchase information of a product or service purchased by a user of the terminal with deferred payment; displaying a plurality of account information associated with the user on a display of the terminal; and at least a portion of the purchase information based on the selection of first account information from the plurality of account information by the user of the terminal. and displaying on the display first information relating to paying the payment of at a first account associated with the first account information.
According to a third aspect of the present invention, a terminal comprises: a communication unit for receiving purchase information of goods or services purchased by a user of the terminal with deferred payment; the purchase information; and a plurality of account information related to the user of the terminal. and a display unit for displaying, based on the user of the terminal selecting the first account information from among the plurality of account information, payment of at least a portion of the purchase information to the first account information associated with the first account information. and a control unit for controlling to display first information about paying with an account on the display unit.
According to a fourth aspect of the present invention, a terminal comprises a processor for reading a program stored in a memory and executing a process based on the program, the processor being adapted for use by a user of the terminal for goods or services purchased with deferred payment. receiving the purchase information by a communication unit of the terminal; displaying the purchase information and a plurality of account information related to the user of the terminal on a display unit of the terminal; and displaying, on the display unit, first information relating to paying at least a portion of the purchase information with a first account associated with the first account information based on the selection of the first account information. .
According to a fifth aspect of the present invention, a server communicating with a terminal receives purchase information purchased by a user of the terminal with deferred payment, transmits the purchase information to the terminal, and transmits at least part of the purchase information to the terminal. A communication unit is provided for receiving information from the terminal regarding payment by a first of a plurality of accounts associated with the user.

The figure which shows an example of the system configuration|structure of the communication system which concerns on 1st Example. The figure which shows an example of the function implement|achieved by the control part of the credit card company server based on 1st Example. The figure which shows an example of the information etc. which are memorize|stored in the memory|storage part of the credit card company server which concerns on 1st Example. The figure which shows an example of a data structure of the user registration data based on 1st Example. FIG. 4 is a diagram showing an example of data configuration of affiliated bank data according to the first embodiment; The figure which shows an example of a data structure of the user management database based on 1st Example. FIG. 4 is a diagram showing an example of functions realized by a control unit of the terminal according to the first embodiment; FIG. 4 is a diagram showing an example of information and the like stored in a storage unit of the terminal according to the first embodiment; Explanatory drawing of the principle of the credit card payment service based on 1st Example. The figure which shows an example of the display screen of the terminal which concerns on 1st Example. 4 is a flowchart showing an example of the flow of processing executed by each device according to the first embodiment; 4 is a flowchart showing an example of the flow of processing executed by each device according to the first embodiment; 10 is a flowchart showing an example of the flow of processing executed by each device according to the first modified example; The figure which shows an example of the system configuration|structure of the communication system which concerns on a 1st modification. The figure which shows an example of a data structure of the user management database based on a 1st modification. The figure which shows an example of the function implement|achieved by the control part of the server based on a 1st modification. The figure which shows an example of the information memorize|stored in the memory|storage part of the server based on a 1st modification. The figure which shows an example of the data structure of the account registration data which concerns on a 1st modification. FIG. 10 is a diagram showing an example of the data configuration of an account management database according to the first modified example; FIG. The figure which shows an example of the function implement|achieved by the control part of the terminal which concerns on a 1st modification. The figure which shows an example of the information memorize|stored in the memory|storage part of the terminal which concerns on a 1st modification. Explanatory drawing of the principle of the credit card payment service based on a 1st modification. The figure which shows an example of the display screen of the terminal which concerns on a 1st modification. 10 is a flowchart showing an example of the flow of processing executed by each device according to the first modified example; 10 is a flowchart showing an example of the flow of processing executed by each device according to the first modified example; FIG. 10 is a diagram showing an example of the data configuration of an account management database according to the first modified example; FIG. The figure which shows an example of the display screen of the terminal which concerns on a 1st modification. 10 is a flowchart showing an example of the flow of processing executed by each device according to the first modified example; FIG. 10 is a diagram showing an example of the data configuration of an account management database according to the first modified example; FIG. 10 is a flowchart showing an example of the flow of processing executed by each device according to the first modified example; The figure which shows an example of the display screen of the terminal which concerns on a 1st modification. 10 is a flowchart showing an example of the flow of processing executed by each device according to the first modified example; The figure which shows an example of the display screen of the terminal which concerns on 2nd Example. 9 is a flowchart showing an example of the flow of processing executed by each device according to the second embodiment; 9 is a flowchart showing an example of the flow of processing executed by each device according to the second embodiment; The figure which shows an example of the display screen of the terminal which concerns on a 2nd modification. The figure which shows an example of a data structure of the user management database based on 3rd Example. The figure which shows an example of the display screen of the terminal which concerns on 3rd Example. FIG. 11 is a flow chart showing an example of the flow of processing executed by each device according to the third embodiment; FIG. The figure which shows an example of a data structure of the information classification determination data for payment account setting which concerns on 4th Example. The figure which shows an example of a data structure of the information classification determination data for the payment account setting for each transaction based on 4th Example. The figure which shows an example of the display screen of the terminal which concerns on 4th Example. The figure which shows an example of the display screen of the terminal which concerns on 4th Example. The figure which shows an example of a data structure of the payment account setting remind condition data which concerns on 5th Example. 14 is a flow chart showing an example of the flow of processing executed by each device according to the fifth embodiment; The figure which shows an example of the display screen of the terminal which concerns on 6th Example. The figure which shows an example of a data structure of the user management database based on 7th Example. The figure which shows an example of the display screen of the terminal which concerns on 7th Example. FIG. 11 is a flow chart showing an example of the flow of processing executed by each device according to the seventh embodiment; FIG. The figure which shows an example of the display screen of the terminal which concerns on a 7th modification. The figure which shows an example of the data structure of the data for payment account determination based on 8th Example. FIG. 12 is a flow chart showing an example of the flow of processing executed by each device according to the eighth embodiment; FIG. The figure which shows an example of the display screen of the terminal which concerns on 9th Example. The figure which shows an example of the display screen of the terminal which concerns on a 9th modification. The figure which shows an example of the display screen of the terminal which concerns on a 9th modification. The figure which shows an example of the display screen of the terminal which concerns on a 9th modification. The figure which shows an example of a data structure of the user management database based on 10th Example. FIG. 22 is a diagram showing an example of the data configuration of an account management database according to the tenth embodiment; FIG. The figure which shows an example of the display screen of the terminal which concerns on 10th Example. FIG. 12 is a flow chart showing an example of the flow of processing executed by each device according to the tenth embodiment; FIG. FIG. 12 is a flow chart showing an example of the flow of processing executed by each device according to the tenth embodiment; FIG. FIG. 12 is a flow chart showing an example of the flow of processing executed by each device according to the tenth embodiment; FIG. FIG. 14 is a flowchart showing an example of the flow of processing executed by each device according to the tenth modification; FIG. FIG. 21 is a diagram showing an example of the data configuration of an account management database according to the tenth modification; FIG. FIG. 14 is a flowchart showing an example of the flow of processing executed by each device according to the tenth modification; FIG. The figure which shows an example of the display screen of the terminal which concerns on a tenth modification. FIG. 14 is a flowchart showing an example of the flow of processing executed by each device according to the tenth modification; FIG. FIG. 14 is a flowchart showing an example of the flow of processing executed by each device according to the tenth modification; FIG. FIG. 14 is a flowchart showing an example of the flow of processing executed by each device according to the tenth modification; FIG. FIG. 14 is a flowchart showing an example of the flow of processing executed by each device according to the tenth modification; FIG. FIG. 14 is a flow chart showing an example of the flow of processing executed by each device according to the eleventh embodiment; FIG. FIG. 14 is a flow chart showing an example of the flow of processing executed by each device according to the eleventh embodiment; FIG. FIG. 14 is a flowchart showing an example of the flow of processing executed by each device according to the eleventh modification; FIG. FIG. 14 is a flowchart showing an example of the flow of processing executed by each device according to the eleventh modification; FIG. FIG. 14 is a flowchart showing an example of the flow of processing executed by each device according to the eleventh modification; FIG. The figure which shows an example of the display screen of the terminal which concerns on another Example.

<Compliance with legal matters>
Note that the disclosure provided herein is subject to compliance with the legal requirements of the implementing country required for the practice of this disclosure, such as confidentiality of communications.

An embodiment for implementing a program or the like according to the present disclosure will be described with reference to the drawings.

A system can be a concept that includes, by way of example and not limitation, any of the following forms of system.
(1) Terminal & Server (2) Server (3) Terminal

(1) is a system including, by way of example and not limitation, at least one terminal and at least one server. An example of this is a server-client system.
In this case, the controller of the system can be at least one of the controller of the terminal and the controller of the server. That is, as an example and not a limitation, any one of (1A) only the control unit of the terminal, (1B) only the control unit of the server, or (1C) both the control unit of the terminal and the control unit of the server may be used in the system. can be a control unit.

Further, the control and processing performed by the control unit of the system (hereinafter collectively referred to as "control, etc.") may be performed only by (1A) the control unit of the terminal, or (1B) the control of the server (1C) It may be performed by both the control unit of the terminal and the control unit of the server.
In addition, in (1C), as an example and not a limitation, part of the control performed by the control unit of the system is performed by the control unit of the terminal, and the rest of the control is performed by the control unit of the server. You may do so. In this case, the allocation (allocation) of control and the like may be equally divided, or may be allocated at different ratios instead of equally divided.

(2) can be, for example and not limitation, a system composed of a plurality of servers (hereinafter referred to as "server system").

The control or the like performed by the server system may be performed by (2A) only one server, (2B) only another server, or (2C) one of the plurality of servers. server and another server.
Also, in (2C), as an example and not a limitation, one server may perform part of the control performed by the server system, and the remaining control may be performed by another server. good. In this case, the allocation (allocation) of control and the like may be equally divided, or may be allocated at different ratios instead of equally divided.

(3) can be, by way of example and not limitation, a system composed of a plurality of terminals.
The system may be, by way of example and not limitation, a system such as the following.
・A system in which terminals have server functions (distributed system). This can be accomplished using blockchain technology, by way of example and not limitation.
・A system in which terminals communicate wirelessly with each other. As an example and not a limitation, this can be realized by performing communication in a P2P (Peer-to-Peer) method or the like using short-range wireless communication technology such as Bluetooth.

Note that the above is not limited to the control section, and the same applies to each functional section such as an input/output section, a communication section, a storage section, a clock section, etc., which can be components of the system.

In the following embodiments, by way of example and not by way of limitation, a system including a terminal and a server (by way of example and not by way of limitation, a server-client system) is illustrated.
It is also possible to apply the server system of (2) above as the server.

Also, instead of a system including a terminal and a server, it is possible to apply a system that does not include a server, such as the system of (3) above as an example and not as a limitation.
An embodiment in this case can be configured based on the above-described blockchain technology or the like. Specifically, as an example and not a limitation, data stored and managed in a server described in the following embodiments is saved (stored) on a blockchain. The terminal can then generate a transaction to the blockchain, and when the transaction is approved on the blockchain, the data stored on the blockchain can be updated.

Also, in this specification, the expression "by communication I/F" is used as appropriate. This indicates that, as an example and not a limitation, the device transmits and receives various types of information and data via a communication I/F (via a communication unit) under the control of a control unit (processor or the like). It shall be acceptable.

Also, in this specification, the terms “related” and “related” are not limited to the terms “B related to A” and “B related to A”, and “A” and some relationship shall mean "B" having A specific example of this will be described later.

Further, in this specification, "A" and Including those in which "B" is performed at the same time (hereinafter referred to as "simultaneous") and those in which "A" and "B" are performed at different times (hereinafter referred to as "non-simultaneously"). shall be acceptable.
As an example and not as a limitation, in the case of transmitting the first information and the second information, it is possible to transmit the first information and the second information at the same timing, and to transmit the first information and the second information at the different timings. may include both the concept of what is sent with
In consideration of lag (time lag), "at the same time" may include "almost at the same time."

It should be noted that even though "A" and "B" are performed at different timings, it is only necessary to process "A" and "B" as targets, and the purpose is not necessarily the same. be omitted.
By way of example and not limitation, when it is said that the first information and the second information are transmitted as described above, it is only necessary to transmit the first information and the second information, and the first information and the second information are used for the same purpose. In addition to the case of transmitting the first information and the second information for different purposes, it may also include the case of transmitting the first information and the second information.

<Embodiment>
2. Description of the Related Art Payments using credit cards (hereinafter referred to as “credit card payments”) and the like are used on a daily basis.
This embodiment relates to deferred payment settlement including credit card settlement.

"Deferred payment" means that when a user purchases a product or service, although the purchase procedure has been completed, payment is not made at that timing, and the timing is set after that, as an example, not as a limitation. It is a service to pay the price by the date specified or by the set date. This can include a case where the user first receives the product or the like (or the product or the like is shipped to the user first) and then pays for it.

This post-payment may include, by way of example and not limitation, at least any of the following payment methods.
(1) Credit card payment (2) Tsukebarai

(1) For credit card payments, as an example, not limited, on a set date (or a set date), such as once a month, and during a set period (not limited, but for example, one month) Payment is made from the bank account linked to the credit card for the transactions that have been split.

(2) In Tsukebarai, as a non-limiting example, when a user receives a product (or when the product is shipped to the user), an invoice necessary for payment (postpay) is sent to the user at a later date. be done. Alternatively, the billing information is sent to the terminal 20 of the user. Then, the user can use financial institutions (including bank transfer), convenience stores, electronic money services, etc. to pay Make the payment of the stated amount.

In this specification, two types of (2) bill payment are exemplified as non-limiting examples, namely, (2-1) batch bill payment and (2-2) one-time bill payment.
(2-1) Lump-sum payment is, as an example, not a limitation, a method of collectively (collectively) making payment by payment for transactions made during a set period (a period of one month as an example, not a limitation). is.
(2-2) Pay-as-you-go is a method of making a payment as an example, not as a limitation, each time a transaction is made.

Also, in this specification, information related to the purchase of the product or service purchased by the user of the terminal with deferred payment is referred to as "purchase information". "Purchase information" may be information that has some relationship with the purchase of goods or services, and includes the following as examples, not limitation.
・Information indicating that the product or service was purchased with deferred payment ・Information indicating the outline and details of the product or service purchased with deferred payment ・Information regarding billing for deferred payment

The purchase information received by the terminal and the purchase information managed by the server of the credit card company or the server of the service provider that provides services such as messaging service and electronic money service may be completely the same information. , may be partially different information.

<First embodiment>
The first embodiment is a basic embodiment for realizing the method of the present disclosure by the aforementioned (1) credit card payment as an example and not as a limitation.

Some users may have accounts at multiple financial institutions and use the accounts at different financial institutions depending on the purpose of use. Even in the case of deferred payment such as credit card settlement, it is convenient if the account of the financial institution can be used according to the purpose of use.

The first embodiment is an embodiment in which a user can select a bank account (hereinafter referred to as "payment account") for credit card payment for each purchase information in credit card payment. In this embodiment, a credit card is associated with multiple bank accounts.
The content described in the first embodiment can be applied to each of the other embodiments and each of the other modifications.

In the examples described below, a "bank" is exemplified as a financial institution.
Banks can include not only banks with branches (including banks of the Japan Post Group, etc.), but also internet banks (net banks), for example and not limitation.
As the financial institution, instead of a bank, it is possible to apply a financial institution such as a central bank or a credit union.

Also, in the embodiments described below, withdrawal of the payment amount from the payment account is referred to as "account transfer". Further, the account transfer processing performed by the bank server 50 is referred to as "account transfer processing".

The account transfer may also be referred to as automatic transfer, automatic account transfer, or the like.
A payment account may also be referred to as a debit account, a transfer account, or the like.

<System configuration>
FIG. 1-1 is a diagram showing an example of the system configuration of a communication system 1A in this embodiment.
In the communication system 1A, as an example and not limitation, a credit card company server 10, one or more terminals 20 (terminal 20A, terminal 20B, terminal 20C, . 40 (store terminal 40A, store terminal 40B, store terminal 40C, . . . ) are connected to two or more bank servers 50 (bank server 50A, bank server 50B, bank server 50C).

The credit card company server 10 has a function of providing a credit card settlement service, which will be described later, via the network 30 to the terminal 20 owned by the user, the shop terminal 40, the bank server 50, etc. as an example and not as a limitation.
The credit card company server 10 can also be expressed as a credit card service server, credit payment management server, credit settlement service server, credit settlement management server, credit settlement system server, credit service server, or the like.
In this embodiment, as an example and not a limitation, the user of the credit card company server 10 is assumed to be a credit card company (credit settlement service provider).

Credit card payment systems include, but are not limited to, brand holders (international brands), card issuers (issuers), merchant management companies (acquirers), payment agency companies, card merchants, authorization networks, etc. contains the components of
In this embodiment, for the sake of simplification, the card issuing company and the affiliated store management company are collectively referred to as a "credit card company".
The card issuing company and member store management company may be the same company or may be different companies.

The number of credit card company servers 10, the number of terminals 20, the number of shop terminals 40, and the number of bank servers 50 connected to the network 30 are not limited to the above.

In this embodiment, the "credit settlement service" is a service provided by a credit card company (credit card company server 10) for implementing credit settlement. This credit settlement service is provided to a user (user's terminal 20), a store (store terminal 40), and a bank (bank server 50) by way of example and not limitation.

Hereinafter, a bank affiliated with a credit card company will be referred to as an "affiliated bank," and a store affiliated with a credit card company will be referred to as a "affiliated store."

The terminal 20 (terminal 20A, terminal 20B, terminal 20C, . . . ) may be any information processing terminal capable of realizing the functions described in each embodiment. Terminal 20 includes, by way of example and not limitation, smart phones, mobile phones (feature phones), computers (including but not limited to desktops, laptops, tablets, etc.), media computer platforms (including but not limited to cable, satellite set top boxes, digital video recorders), handheld computer devices (as non-limiting examples include PDA (personal digital assistant), email clients, etc.), wearable terminals (glass-type devices, watch-type devices, etc.), VR (Virtual Reality) Including terminals, smart speakers (devices for voice recognition), or other types of computers or communication platforms. Also, the terminal 20 may be expressed as an information processing terminal.

The configuration of terminal 20A, terminal 20B and terminal 20C may be identical, by way of example and not by way of limitation. Further, if necessary, the terminal used by the user X may be expressed as the terminal 20X, and the user information in a predetermined service associated with the user X or the terminal 20X may be expressed as the user information X. It doesn't have to be.
The user information is user information associated with an account used by the user in a predetermined service. User information includes, by way of example and not limitation, user's name, user's icon image, user's age, user's gender, user's address, user's hobbies, entered by the user or provided by a given service It may include information associated with the user, such as preferences, user identifiers, etc., and may or may not be any one or combination of these.

The network 30 plays a role of connecting each device constituting the communication system 1A. That is, the network 30 means a communication network that provides a connection path so that the various devices can transmit and receive data after being connected.

One or more portions of network 30 may or may not be wired or wireless networks. Network 30 may include, by way of example and not limitation, an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (wireless LAN), wide area network (WAN), wireless WAN (WWAN), metropolitan area network (MAN), part of the Internet, public switched telephone network (Public Part of Switched Telephone Network (PSTN), mobile phone network, ISDN (integrated service digital networks), wireless LAN, LTE (long term evolution), CDMA (code division multiple access), Bluetooth (registered trademark), satellite communication, etc., or a combination of two or more thereof. Network 30 may include one or more networks 30 .

The credit card company server 10 (not limited to, but an example of a server, an information processing device, an information management device) has a function of providing a predetermined service (credit settlement service in this embodiment) to the terminal 20 or the like. . The credit card company server 10 may be any information processing device capable of realizing the functions described in each embodiment. Credit card company server 10 includes, by way of example and not limitation, server equipment, computers (including but not limited to desktops, laptops, tablets, etc.), media computer platforms (including but not limited to cable, satellite set-top boxes, digital video recorders), handheld computing devices (eg, without limitation, PDAs, email clients, etc.), or any other type of computer or communication platform. Also, the credit card company server 10 may be expressed as an information processing device. If there is no need to distinguish between the credit card company server 10 and the terminal 20, the credit card company server 10 and the terminal 20 may or may not be represented as information processing devices.

[Hardware (HW) configuration of each device]
The HW configuration of each device included in the communication system 1A will be described.

(1) HW Configuration of Terminal FIG. 1-1 shows an example of the HW configuration of the terminal 20. As shown in FIG.
The terminal 20 includes a control unit 21 (CPU: central processing unit (central processing unit)), a storage unit 28, a communication I/F 22 (interface), an input/output unit 23, a clock unit 29A, and a position calculation information detection unit 29B. . Each component of the HW of terminal 20 is interconnected via bus B, by way of example and not limitation. Note that the HW configuration of the terminal 20 does not necessarily include all the components. By way of example and not limitation, terminal 20 may or may not be configured for individual or multiple components to be removed.

Communication I/F 22 transmits and receives various data via network 30 . Communication may be performed by wire or wirelessly, and any communication protocol may be used as long as mutual communication can be performed. Communication I/F 22 has a function of executing communication with various devices such as credit card company server 10 via network 30 . The communication I/F 22 transmits various data to various devices such as the credit card company server 10 according to instructions from the control unit 21 . The communication I/F 22 also receives various data transmitted from various devices such as the credit card company server 10 and transmits the data to the control unit 21 . Also, the communication I/F 22 may be simply referred to as a communication section. Moreover, when the communication I/F 22 is configured by a physically structured circuit, it may be expressed as a communication circuit.

The input/output unit 23 includes a device for inputting various operations to the terminal 20, a device for outputting processing results processed by the terminal 20, and the like. In the input/output unit 23, the input unit and the output unit may be integrated, the input unit and the output unit may be separated, or not.

The input unit is implemented by any one or a combination of all types of devices that can receive input from the user and transmit information related to the input to the control unit 21 . The input unit includes, but is not limited to, hardware keys such as a touch panel, a touch display, and a keyboard, a pointing device such as a mouse, a camera (operation input via moving images), and a microphone (operation input by voice).

The output unit is implemented by any one or a combination of all types of devices capable of outputting processing results processed by the control unit 21 . The output unit includes, as non-limiting examples, a touch panel, a touch display, a speaker (audio output), a lens (non-limiting examples include 3D (three dimensions) output and hologram output), a printer, and the like.

Although it is only an example, the input/output unit 23 includes a display unit 24 , a sound input unit 25 , a sound output unit 26 and an imaging unit 27 as an example and not a limitation.

The display unit 24 is realized by any one or a combination of all kinds of devices capable of displaying according to the display data written to the frame buffer. The display unit 24 includes a touch panel, a touch display, a monitor (as a non-limiting example, a liquid crystal display and an OELD (organic electroluminescence display)), a head mounted display (HDM), projection mapping, and a hologram. , including devices capable of displaying images, text information, etc. in air (which may or may not be a vacuum). Note that these display units 24 may or may not be capable of displaying display data in 3D.

The sound input unit 25 is used to input sound data (including voice data; the same applies hereinafter). Sound input unit 25 includes a microphone and the like.
The sound output unit 26 is used for outputting sound data. Sound output unit 26 includes a speaker and the like.
The imaging unit 27 is used to acquire image data (including still image data and moving image data; the same applies hereinafter). The imaging unit 27 includes a camera and the like.

When the input/output unit 23 is a touch panel, the input/output unit 23 and the display unit 24 may be arranged to face each other with substantially the same size and shape.

The clock unit 29A is a built-in clock of the terminal 20 and outputs time information (clock information). The clock unit 29A is configured with a clock using a crystal oscillator or the like, for example and not limitation. The clock unit 29A can also be expressed as a clock unit or a time information detection unit as an example and not as a limitation.

Note that the clock unit 29A may or may not have a clock to which the NITZ (Network Identity and Time Zone) standard or the like is applied.

The position calculation information detection unit 29B has a function of detecting (measuring) information necessary for the control unit 21 to calculate (measure) the position of its own terminal 20 (hereinafter referred to as “position calculation information”). Department. The position calculation information detection section 29B can also be expressed as a position calculation sensor section as an example and not as a limitation.

The position calculation information detection unit 29B includes, as a non-limiting example, a satellite positioning sensor (satellite positioning sensor) which is a sensor or unit for calculating the position of the terminal 20 using a satellite positioning system such as GPS (Global Positioning System). unit), an inertial measurement sensor (inertial measurement unit (IMU (Inertial Measurement Unit))), which is a sensor or unit for calculating the position of the terminal 20 using an inertial navigation system, UWB (ultra wideband radio: Ultra Wide A UWB positioning sensor (UWB positioning unit), etc., which is a sensor or unit for calculating the position of the terminal 20 using a band).

The satellite positioning unit includes, as a non-limiting example, an RF receiving circuit that converts an RF (Radio Frequency) signal including a positioning satellite signal transmitted from a positioning satellite received by an antenna (not shown) into a digital signal, Positioning satellite signals are acquired by performing correlation calculation processing, etc. on the digital signals output from the RF receiving circuit, and information such as satellite orbit data and time data extracted from the positioning satellite signals is used as position calculation information. It has a baseband processing circuit for output.

The inertial measurement unit has an inertial sensor that detects information necessary to calculate the position of terminal 20 by inertial navigation calculation. Examples of inertial sensors include, but are not limited to, triaxial acceleration sensors and triaxial gyro sensors. The acceleration detected by the acceleration sensor and the angular velocity detected by the gyro sensor are used as position calculation information. Output.

As a non-limiting example, the UWB positioning unit converts an ultra-wideband RF (Radio Frequency) signal including an ultra-wideband pulse signal for positioning transmitted from a positioning beacon received by an antenna (not shown) into a digital signal. It has a wideband RF receiving circuit, a relative position calculation processing circuit that calculates the relative position between the terminal 20 and the positioning beacon based on the digital signal output from the ultra-wideband RF receiving circuit, and the like.
As an example and not a limitation, the UWB positioning unit may cause the terminal 20 to function as a positioning beacon by transmitting an ultra-wideband RF signal including a positioning ultra-wideband pulse signal from an antenna (not shown), You don't have to.

As a non-limiting example, the control unit 21 calculates the position of its own terminal 20 at regular timings or specific timings based on the position calculation information detected by the position calculation information detection unit 29B. The position of the terminal is called "terminal position", and the calculated terminal position is called "calculated terminal position". The control unit 21 may or may not associate the calculated terminal position with the date and time when the calculated terminal position was calculated and store it in the storage unit 28 as calculated terminal position history data.

The control unit 21 comprises, by way of example and not limitation, a hardware built-in data processing device comprising physically structured circuitry for carrying out the functions implemented by the code or instructions contained within the program. It is realized by Therefore, the control unit 21 may or may not be expressed as a control circuit.

Control unit 21 includes, by way of example and not limitation, a central processing unit (CPU), microprocessor, processor core, multiprocessor, ASIC (application-specific integrated circuit), FPGA (field programmable gate array).

The storage unit 28 has a function of storing various programs and various data required for the terminal 20 to operate. The storage unit 28 includes various storage media such as HDD (hard disk drive), SSD (solid state drive), flash memory, RAM (random access memory), and ROM (read only memory) as examples and not limitation. Also, the storage unit 28 may or may not be expressed as a memory.

The terminal 20 stores the program P in the storage unit 28 and executes the program P so that the control unit 21 executes processing as each unit included in the control unit 21 . That is, the program P stored in the storage unit 28 causes the terminal 20 to implement each function executed by the control unit 21 . Also, this program P may or may not be expressed as a program module.

(2) HW Configuration of Credit Card Company Server FIG. 1-1 shows an example of the HW configuration of the credit card company server 10. As shown in FIG.
The credit card company server 10 includes a control unit 11 (CPU), a storage unit 15, a communication I/F 14 (interface), an input/output unit 12, a display unit 13, and a clock unit 19. Each component of the HW of credit card company server 10 is interconnected via bus B, by way of example and not limitation. It should be noted that the HW of the credit card company server 10 does not have to include all components as the HW configuration of the credit card company server 10 . By way of example and not limitation, the HW of the credit card company server 10 may or may not be configured to remove individual components or multiple components.

The control unit 11 comprises, by way of example and not limitation, a hardware built-in data processing device comprising physically structured circuitry for carrying out the functions implemented by the code or instructions contained within the program. It is realized by

The control unit 11 is typically a central processing unit (CPU), and may or may not be a microprocessor, processor core, multiprocessor, ASIC, or FPGA. In the present disclosure, the controller 11 is not limited to these.

The storage unit 15 has a function of storing various programs and various data necessary for the credit card company server 10 to operate. The storage unit 15 is realized by various storage media such as HDD, SSD, and flash memory. However, in the present disclosure, the storage unit 15 is not limited to these. Also, the storage unit 15 may or may not be expressed as a memory.

Communication I/F 14 transmits and receives various data via network 30 . Communication may be performed by wire or wirelessly, and any communication protocol may be used as long as mutual communication can be performed. The communication I/F 14 has a function of executing communication with various devices such as the terminal 20 via the network 30 . Communication I/F 14 transmits various data to various devices such as terminal 20 according to instructions from control unit 11 . The communication I/F 14 also receives various data transmitted from various devices such as the terminal 20 and transmits the data to the control unit 11 . Also, the communication I/F 14 may be simply referred to as a communication unit. Moreover, when the communication I/F 14 is configured by a physically structured circuit, it may be expressed as a communication circuit.

The input/output unit 12 includes a device for inputting various operations to the credit card company server 10, a device for outputting processing results processed by the credit card company server 10, and the like. In the input/output unit 12, the input unit and the output unit may be integrated, the input unit and the output unit may be separated, or not.

The input unit is implemented by any one or a combination of all types of devices that can receive input from the user and transmit information related to the input to the control unit 11 . The input unit is realized by hardware keys typically represented by a keyboard and a pointing device such as a mouse. Note that the input unit may or may not include a touch panel, a camera (operation input via a moving image), and a microphone (operation input by voice) as examples, not limitation.

The output unit is implemented by any one or a combination of all types of devices capable of outputting processing results processed by the control unit 11 . The output unit includes, as non-limiting examples, touch panels, touch displays, speakers (sound output), lenses (three-dimension (3D) output and hologram output as non-limiting examples), printers, and the like.

Although it is only an example, the input/output unit 12 includes the display unit 13 as an example and not as a limitation.

The display unit 13 is realized by a display or the like. The display is typically implemented by a monitor (for example, but not by way of limitation, a liquid crystal display or an OELD (organic electroluminescence display)). Note that the display may or may not be a head mounted display (HDM) or the like. These displays may or may not be capable of displaying display data in 3D. In the present disclosure, displays are not limited to these.

The clock unit 19 is a built-in clock of the credit card company server 10 and outputs time information (timekeeping information). The clock unit 19 includes, for example and not limitation, an RTC (Real Time Clock) as a hardware clock, a system clock, and the like. The clock unit 19 can also be expressed as a clock unit or a time information detection unit as an example and not as a limitation.

(3) HW Configuration of Store Terminal The store terminal 40 is a device used and managed by a store operator (hereinafter referred to as "store operator"). The store terminal 40 is realized by a server, a personal computer, a terminal (as a non-limiting example, a mobile terminal (smartphone, PDA, etc.)) or the like, as an example and not a limitation.

The HW configuration of the store terminal 40 can be configured in the same manner as the credit card company server 10 and the terminal 20, so illustration and description thereof will be omitted.

The store operator in this embodiment is a store business that has a tie-up with a credit card company and has introduced a credit card payment system so that users can purchase products and services with a credit card. Businesses of various business types, such as convenience stores, supermarkets, fast food restaurants, restaurants, pharmacies, department stores, etc., can be included as non-limiting examples.
A store operator is an example of an operator in this disclosure.

(4) HW configuration of bank server The HW configuration of the bank server 50 and the components and circuits that make up each functional unit can be configured in the same way as the credit card company server 10 or the like, not as a limitation, but as an example. Illustration and description are omitted.

(5) Others The credit card company server 10 stores the program P in the storage unit 15 and executes the program P, thereby causing the control unit 11 to perform processing as each unit included in the control unit 11 . That is, the program P stored in the storage unit 15 causes the credit card company server 10 to realize each function executed by the control unit 11 . This program P may or may not be expressed as a program module.
The same is true for other devices.

Each embodiment of the present disclosure will be described as being implemented by the CPU of the terminal 20 and/or the credit card company server 10 executing the program P.
The same is true for other devices.

It should be noted that the control unit 21 of the terminal 20 and/or the control unit 11 of the credit card company server 10 is not only a CPU having a control circuit, but also an integrated circuit (IC (Integrated Circuit) chip, LSI (Large Scale Integration)). Each processing may or may not be realized by a logic circuit (hardware) or a dedicated circuit formed in the same manner as the above. Also, these circuits may be realized by one or more integrated circuits, and the plurality of processes shown in each embodiment may or may not be realized by one integrated circuit. LSIs are also called VLSIs, super LSIs, ultra LSIs, etc., depending on the degree of integration. Therefore, the control unit 21 may or may not be expressed as a control circuit.
The same is true for other devices.

In addition, the program P of each embodiment of the present disclosure (as a non-limiting example, a software program, a computer program, or a program module) may be provided in a state stored in a computer-readable storage medium, It does not have to be. The storage medium can store the program P in a "non-transitory tangible medium". Also, the program P may or may not be for realizing part of the functions of each embodiment of the present disclosure. Furthermore, the function of each embodiment of the present disclosure may or may not be a so-called difference file (difference program) that can be realized in combination with a program P already recorded on a storage medium.

The storage medium may include one or more semiconductor-based or other integrated circuits (ICs) (such as, by way of example and without limitation, field programmable gate arrays (FPGAs) or application specific ICs (ASICs)), hard Disk drive (HDD), hybrid hard drive (HHD), optical disk, optical disk drive (ODD), magneto-optical disk, magneto-optical drive, floppy diskette, floppy disk drive (FDD), magnetic tape, solid state It may include a drive (SSD), RAM drive, secure digital card or drive, any other suitable storage medium, or any suitable combination of two or more thereof. Storage media may, where appropriate, be volatile, nonvolatile, or a combination of volatile and nonvolatile. Note that the storage medium is not limited to these examples, and any device or medium that can store the program P may be used. Also, the storage medium may or may not be expressed as memory.

The credit card company server 10 and/or the terminal 20 can implement the functions of the plurality of functional units shown in each embodiment by reading the program P stored in the storage medium and executing the read program P. .
The same is true for other devices.

In addition, the program P of the present disclosure may or may not be provided to the credit card company server 10 and/or the terminal 20 via any transmission medium (communication network, broadcast wave, etc.) capable of transmitting the program. may The credit card company server 10 and/or the terminal 20 implements the functions of the plurality of functional units shown in each embodiment by executing a program P downloaded via the Internet or the like, for example and not limitation.
The same is true for other devices.

Each embodiment of the present disclosure can also be implemented in the form of a data signal in which the program P is embodied by electronic transmission.
At least part of the processing in the credit card company server 10 and/or terminal 20 may or may not be realized by cloud computing configured by one or more computers.
At least part or all of the processing in the terminal 20 may or may not be performed by the credit card company server 10 . In this case, the credit card company server 10 may or may not perform at least some or all of the processing of the functional units of the control unit 21 of the terminal 20 .
At least part or all of the processing in the credit card company server 10 may or may not be performed by the terminal 20 . In this case, the terminal 20 may or may not perform at least some or all of the processing of the functional units of the control unit 11 of the credit card company server 10 .
Unless explicitly mentioned, the configuration of determination in the embodiments of the present disclosure is not essential, and predetermined processing is performed when the determination condition is satisfied, or predetermined processing is performed when the determination condition is not satisfied. may or may not.

Note that the program of the present disclosure uses script languages such as ActionScript and JavaScript (registered trademark), compiler languages such as Objective-C and Java (registered trademark), markup languages such as HTML5, and the like, for example and not limitation. Implemented.

[Functional configuration of each device]
(1) Functional Configuration of Credit Card Company Server FIG. 1-2 is a diagram showing an example of functions realized by the control unit 11 of the credit card company server 10 in this embodiment.
The control unit 11 includes, as a functional unit, a credit card settlement management processing unit 111 for executing credit card settlement management processing according to a credit card settlement management processing program 151 stored in the storage unit 15, as an example and not limitation.

FIG. 1-3 is a diagram showing an example of information stored in the storage unit 15 of the credit card company server 10 in this embodiment.
As an example and not limitation, the storage unit 15 stores a credit card settlement management processing program 151 executed as credit card settlement management processing, user registration data 153, affiliated bank data 155, affiliated store data 157, user management A database 159 is stored.

The user registration data 153 is registration data of the terminal 20 or the user of the terminal 20 who uses the credit card payment service, and an example of the data configuration is shown in FIG. 1-4.
The user registration data 153 stores, for example and not limitation, name, contractor ID, authentication password, credit card information, and other registration information in association with each other.

The name is the name of the user of the terminal 20 who uses the credit card payment service, and as an example, not limitation, the name registered when the user of the terminal 20 uses the credit card payment is stored.

The contractor ID is an ID that functions as identification information for identifying this user.
This contractor ID is preferably a unique value for each user, and as an example and not a limitation, the credit card company server 10 sets and stores a unique value (unique value) for each user.
The contractor ID is information associated with the user of the terminal, and is an example of information related to the user of the terminal.

The authentication password is an authentication password that is required to be input to the terminal 20 in the authentication process executed when using various functions provided as functions of the credit card payment service on the terminal 20 of the user. As an example instead, the password set by the user is stored.

The credit card information is information related to the credit card of the user of this contractor ID, and includes, as a non-limiting example, information such as credit card number, credit card expiration date, security code, and the like.

Other registration information is other registration information for this user and may include, by way of example and not limitation, some or all of the following information.
Address (or whereabouts): The address (or whereabouts) of this user. The address (or whereabouts) registered by the user when using the credit card payment service is stored.
• Phone Number: The phone number of this user. As an example and not a limitation, the telephone number registered by the user of the terminal 20 when using the credit card payment service (as an example and not a limitation, the terminal telephone number that is the telephone number of the terminal 20) is stored.
• E-mail address: The e-mail address of this user. As an example and not a limitation, the mail address registered by the user of the terminal 20 when using the credit card settlement service (as an example, not a limitation, the terminal mail address that is the mail address of the terminal 20) is stored.

Note that it is also possible to apply a method of managing users by information such as credit card information, telephone numbers and e-mail addresses instead of contractor IDs.

Further, the above various user information may be stored and managed by the credit card company server 10 as user information common to other services that the credit card company server 10 can provide and the credit card settlement service. , may be stored and managed by the credit card company server 10 as separate user information.

The partner bank data 155 is management data of the partner bank, and an example of the data configuration is shown in FIG. 1-5.
The affiliated bank data 155 stores, for example and not limitation, an affiliated bank ID, an affiliated bank name, an affiliated bank server URI, and other affiliated bank information in association with each other.

The partner bank ID is an ID that functions as identification information for identifying the partner bank or bank server 50 . This partner bank ID may include, by way of example and not limitation, information such as bank code, branch code, and the like.

The name of the affiliated bank stores the name of the affiliated bank (as an example, not as a limitation, such as the trade name, nickname, or common name of the affiliated bank).

The affiliated bank server URI stores a URI (Uniform Resource Identifier) (as an example, not a limitation, a URL (Uniform Resource Locator)) including an access method and an access destination to the bank server 50 of the affiliated bank.

Other affiliated bank information is other registered information of affiliated banks that have this affiliated bank ID. This includes information such as an icon image of a partner bank, which is image data.

The affiliated store data 157 is the management data of the affiliated store, and includes information such as an ID for identifying the affiliated store (affiliated store ID), the name of the affiliated store, the address and contact information of the affiliated store, etc. remembered.

The user management database 159 is a database that accumulates management data relating to users registered in the user registration data 153. An example of the data structure of the user management database 159A is shown in FIG. 1-6.
User management data is stored in the user management database 159A as management data for each contractor ID stored in the user registration data 153 .

Each user administration data stores, by way of example and not limitation, a contractor ID, transaction data, registered bank account data, and payment account setup data.

Transactions for purchasing goods or services by credit card settlement are hereinafter simply referred to as "transactions" or "credit card transactions."

The transaction data is data relating to transactions performed by the user of this contractor ID, and as an example, not limitation, the transaction ID, the store ID, and the purchase information are stored in association with each other.
In addition to this, it is also possible to store information such as credit inquiry results.

The transaction ID is an ID for identifying a transaction of purchase of goods or services by the user of this contractor ID, and preferably a unique value is set and stored for each transaction.

Store ID stores the store ID corresponding to the store where the transaction of this transaction ID is performed among the store IDs stored in the affiliated store data 157 .

The purchase information is information related to the purchase of a product or service in the transaction, and stores information such as the date and time of purchase, the store of purchase, and the amount of purchase, as examples without limitation.

The information that the credit card company server 10 can obtain from the store regarding credit card payment transactions may be, for example, the date and time of purchase, the store of purchase, and the amount of purchase.
However, this is only an example, and in addition to this, information such as the name of the purchased product or service, the number of purchases, etc. may be acquired from the store, and such information may also be stored as purchase information. may or may not.

The registered bank account data is data relating to the bank account linked to the credit card of the user of this contractor ID, and as a non-limiting example, the account ID and the account transfer token are stored.

The account ID is information for identifying the bank account of the user of this contractor ID.
The account ID may include an identification number for identifying a bank account, as well as information such as a bank code, branch code, account number, etc., as examples without limitation. The account ID identifies the bank account associated with the credit card of the user of this contractor ID.

Based on information such as the bank code, branch code, account number, etc., the credit card company server 10 sends the bank account information linked to the credit card to the web page of the credit card company described later (as an example, not limited to, the payment account setting page), the user who accesses this web page can check the bank account information linked to the credit card.

Note that it is not necessary to store all the digits of the account number, and only a part of the digits such as the last three digits or the last four digits may be stored. In this case, it is possible to display only part of the stored digits on the web page.

The account transfer token is authentication information issued by the bank server 50 of the affiliated bank that manages the bank account of this account ID.
The credit card company server 10 is based on the account transfer token issued in advance by the bank server 50 and notified from the bank server 50 and the amount requested/assigned for account transfer (hereinafter referred to as "transfer request amount"). Then, the bank server 50 is requested/requested for account transfer using the bank account of this account ID.
Note that the account transfer token may be expressed as a withdrawal token, an access token, or the like.

The payment account setting data is data related to the information of the set payment account (payment account setting information), and as a non-limiting example, the transaction ID and the payment account ID are stored in association with each other.

The transaction ID stores the transaction ID of the above transaction data.

In the payment account ID, the account ID corresponding to the bank account selected as the payment account by the user of the terminal 20 among the account IDs stored in the registered bank account data for the transaction of this transaction ID is stored and set. be.

It should be noted that there is a possibility that the user may forget to set up a payment account or not set it up in the first place.
Therefore, as an example and not as a limitation, a bank account specified in advance by the user among the registered bank accounts may be set as the default payment account.
In this case, if a bank account different from the default payment account is selected as the payment account, the payment account ID may be updated with that account ID.

In addition, the payment account setting data, as an example and not a limitation, after the monthly account transfer (withdrawal) in credit card payment is completed, is saved as the payment account setting data for the current month, or erased or reset can be made

(2) Functional Configuration of Terminal FIG. 1-7 is a diagram showing an example of functions realized by the control unit 21 of the terminal 20 in this embodiment.
The control unit 21 includes a terminal main processing unit 211 as a main functional unit as an example and not as a limitation.

The terminal main processing unit 211 has a function of performing processing based on various functions according to a terminal main processing program 281 stored in the storage unit 28 .

FIG. 1-8 is a diagram showing an example of information stored in the storage unit 28 of the terminal 20 in this embodiment.
The storage unit 28 stores a terminal main processing program 281 that is executed as a terminal main processing as an example and not a limitation.

<Overview of principle and processing>
FIG. 1-9 is a diagram for explaining the principle of the credit card settlement service in this embodiment, and illustrates the flow of credit card settlement.

In this embodiment, cases where the credit card settlement service is applied include, by way of example and not limitation, any of the following.
(A-1) When the user (customer) of the terminal 20 uses the store terminal 40 to make a payment with a credit card at the store (A-2) The user (customer) of the terminal 20 uses the EC site (example, not limitation) (a website that sells products and services) using the store terminal 40 to make a payment by credit card

In FIG. 1-9, as a non-limiting example, (A-1) the case where the user (customer) of the terminal 20 uses the store terminal 40 at the store to perform a credit card settlement procedure is illustrated. ((1) to (9B) shown in FIG. 1-9).

First, (1) when the user of the terminal 20 purchases a product or service at a store, an operation (user's operation or store clerk's operation) for performing credit card payment at the cash register of the store is sent to the store terminal 40. conduct.

Next, (2) the store terminal 40 sends information about the transaction (for example, but not limited to, payment date and time, payment store, product name, service name, purchase amount (settlement amount), etc.) and a credit inquiry for the purchase amount (credit information requesting the credit card company to perform inquiry processing) to the credit card company server 10.

Here, the credit inquiry is also referred to as "authorization" (also called "authorization" for short) or "provisional billing". It means to check the validity of the card and check the credit limit of the credit card). In the following, the credit inquiry processing performed by the credit card company server 10 will be referred to as "credit inquiry processing".
When the result of the credit inquiry is "approved" by the credit card company (hereinafter referred to as "credit inquiry result: approval"), the settlement amount is temporarily (temporarily) secured. In addition, if the result of the credit inquiry is "denied" by the credit card company (hereinafter referred to as "credit inquiry result: denied"), the settlement amount will not be secured.

Next, (3) the credit card company server 10 that has executed the credit inquiry process transmits information on the result of the credit inquiry (“approval” or “denial”) to the store terminal 40 .

In FIG. 1-9, the credit card company server 10 that has executed the credit inquiry process transmits information on the result of the credit inquiry to the store terminal 40, but the present invention is not limited to this.
The credit inquiry result information may be transmitted only to the terminal 20 , or the credit inquiry result information may be transmitted to both the store terminal 40 and the terminal 20 .

In this example, the case where the result of the credit inquiry is "approval" will be illustrated and explained.
Next, (4) the user (clerk) of the store terminal 40 who has received the credit inquiry result information (credit inquiry result: approval) provides the product or service purchased in (1) to the user (customer) of the terminal 20. do.

Next, (5) the credit card company server 10 pays the purchase amount/settlement amount to the store.
Here, as a method for the credit card company server 10 to pay the settlement amount to the store, a method for the credit card company to make a transfer to a bank account linked to the store or the store terminal 40, a method for the credit card company or a credit card company A method of transferring money from a bank account linked to the server 10 to a bank account linked to the store or the store terminal 40 is conceivable.

Next, (6) the credit card company server 10 sends information (for example, but not limited to, product purchase information, receipt information, etc.) related to billing of the settlement amount temporarily paid by the credit card company server 10 to the store terminal 40; , billing information including information for setting which bank account to use for payment of this settlement amount (example, not limitation, link information to the web page of the credit card company (URI (URL), etc.) Send to terminal 20 .

Next, (7) the user of the terminal 20 who has received the billing information for the payment amount performs an operation to select from which bank account the payment amount is to be paid. Send the information to the credit card company server 10 . A payment account is set by the credit card company server 10 .

(8A), (8B) When the credit card company server 10 requests (requests) the bank account transfer from the partner bank, the bank server 50 of the partner bank that manages the bank account set as the payment account Request to make a transfer (withdrawal).

In response to this, (9A) A bank server 50A conducts account transfer of the requested transfer amount and pays the requested transfer amount to the credit card company. Similarly, (9B) B bank server 50B conducts account transfer of the requested transfer amount and pays the requested transfer amount to the credit card company.

<Display screen>
In the following, as an example and not a limitation, a case where the terminal 20 is a smart phone having a vertically long display unit 24 will be illustrated.

As an example and not a limitation, a smartphone has a touch panel that functions as an input unit facing its display, thereby forming a touch screen. When an element such as an icon, button, item, or input area is displayed on the display, if the user operates an area that is part of the touch panel and faces the area where the element is displayed, A program associated with the element or a subroutine of that program is executed.

Hereinafter, the user's operation will be described as a tap (tap operation) as an example and not as a limitation.
A tap (tap operation) is, for example and not limitation, an operation in which the user touches the display unit 24 (touch screen) integrated with a touch panel by lightly tapping the display unit 24 (touch screen) with a finger or a pen tip, or touches and then releases It is action.

Note that the transition of the display screens described below is merely an example of the transition of the display screens for realizing the technique of the present disclosure. Regarding the transition of the display screens illustrated below, the display of a part of the display screens may be omitted, or another display screen may be added.

1-10 are diagrams showing an example of screen transitions displayed on the display unit 24 of the terminal 20 in this embodiment.
The left side of Fig. 1-10 shows a non-limiting example of a credit card company (credit card payment service provider) (as a non-limiting example, "X credit card company", hereinafter referred to as "X card" as appropriate). ), as billing information, an e-mail (hereinafter referred to as “E mail") is received, user A. FIG. 10 is a received e-mail screen displayed on the display unit 24 of A's terminal 20A. FIG.

At the top left of the received e-mail screen, the characters "E-mail" are displayed to inform the user which web page is being displayed.

A subject display area indicating the subject (title) of the received e-mail is configured below it, and in this example, the subject is displayed in the subject display area as "notice of card use". there is
Below that, there is a sender display area that indicates the sender (source) of the received e-mail. characters are displayed in the sender display area.

A body display area for displaying the body of the received e-mail is configured below it.
In this example, the body text display area displays the text "Usage information" as a headline of the body text as an example and not as a limitation.
In addition, below it, the product purchase information for this credit card payment is displayed, and as an example, not a limitation, there is a column of "date of use" that indicates the date of purchase and a column of "destination" that indicates the store where the purchase was made. There are provided a column and a column of "amount used" indicating the purchase amount. In this example, "2020/10/28" is entered in the "date of use" column, "Store A" is entered in the "destination" column, and "10,000" is entered in the "amount used" column. circles” are displayed.

In addition, below that, link information to the web page of the credit card company is displayed, and the text "Click here to set up a payment account>" is linked based on the registered URL of the web page of the credit card company. A link button BT1 including is displayed.

When the link button BT1 for moving to the credit card company's web page is tapped on the received e-mail screen shown on the left side of FIG. 1-10, the screen moves to the credit card company's web page.

The center of FIG. 1-10 shows an example of a display screen of a payment account setting page (as an example, not a limitation, a payment account setting screen) of a web page of a credit card company.

In the upper left part of this screen, characters "X card" are displayed to inform the user that the web page of the credit card company is being displayed.

Further, below that, there is an area indicating that this web page is a page for setting up a payment account, and in this example, the words "payment account setting" are displayed.
Specifically, below that, a bank account information display area is configured for displaying bank account information linked to the credit card (as an example, but not limited to, bank name, account number, etc.), In this example, the characters "A bank" are displayed as the bank name corresponding to A bank, and the numbers "XXXXXXX" are displayed as the account number. In addition, the characters "B bank" are displayed as the bank name corresponding to "B bank", and the numbers "XXXXXXX" are displayed as the account number.

Below that, there is an area for displaying product purchase information (for example, but not limited to, date and time of purchase, store of purchase, purchase amount, etc.). As information, the column of "date of use"("2020/10/28" in this example), the column of "usage amount"("10000yen" in this example), and the column of "details" (in this example (link information to check the details) is displayed.
The link information in the "details" column is link information with a link to the web page of the credit card company that includes detailed information on product purchase information. Detailed product purchase information may include, by way of example and not limitation, information such as date and time of purchase, name of product or service purchased, number of purchases, purchase amount, store of purchase, and the like.

In addition, on the right of it, a first icon display area for displaying a first icon for selecting a bank account for direct debit is configured. In this example, A A first icon IC1A containing the characters "A bank" corresponding to the bank and a first icon IC1B containing the characters "B bank" corresponding to the B bank are displayed.

Also, at the bottom of the screen, after selecting the first icon, a second icon display area is configured to display a second icon for saving and determining the information. A second icon IC2 including characters is displayed.
Note that the second icon IC2 may be a second button. The same applies hereinafter.

In the payment account setting screen shown in the center of FIG. 1-10, when the first icon IC1A corresponding to Bank A is tapped and then the second icon IC2 is tapped, as an example and not as a limitation, the right of FIG. 1-10 (hereinafter referred to as "payment account setting completion screen") of a web page of a credit card company notifying that the setting of a payment account has been completed is displayed.

In the upper left part of this screen, characters "X card" are displayed to inform the user that the web page of the credit card company is being displayed.

In addition, an area indicating that the setting of the payment account has been completed is configured below it, and in this example, the text "The setting of the payment account has been completed." is displayed.

In addition, an area for displaying product purchase information is configured below it, and the same information as the screen in the center of FIG. 1-10 is displayed.
An area for displaying the set payment account is configured to the right of it, and in this example, the characters "payment account" and the characters "A bank" corresponding to A bank are displayed. ing.

<Processing>
1-11 and 1-12 are flowcharts showing an example of the flow of processing executed by each device in this embodiment.
In this figure, from the left side, processing executed by the control unit 21 of the terminal 20A (the terminal 20 of the user A.A), processing executed by the control unit (not shown) of the store terminal 40A (the store terminal 40 of the store A) , processing executed by the control unit 11 of the credit card company server 10, processing executed by the control unit (not shown) of the bank A server 50A (bank server 50 of bank A), bank B server 50B (bank server 50 of bank B) ) shows an example of processing executed by a control unit (not shown).
Note that the processing executed by the control unit of the shop terminal 40 is omitted from the illustration. This is the same below.

As an example, user A. User A performs the procedure for credit card settlement using the store terminal 40A, and sets up the bank account for the account transfer as user A.A. A process for selecting from two bank accounts, namely, the bank account of Bank A and the bank account of Bank B, which are linked to A's credit card, will be illustrated.
In practice, the number of bank accounts linked to a credit card is not limited to two, but the same applies when there are three or more bank accounts, so illustrations and explanations are omitted here.

Also, this processing is merely an example of processing for realizing the technique of the present disclosure, and is not limited to this processing. Another step may be added to this process, or some steps may be omitted (deleted) from this process.
This is the same for each flowchart (process) described below.

First, user A. Based on the fact that A has completed the credit card payment procedure using the store terminal 40A, the control unit of the store terminal 40A, as a non-limiting example, receives the accepted credit card information and information about the transaction at the store. (as an example and not a limitation, information such as date and time of purchase, name of purchased product or service, number of purchases, purchase amount, etc.) and credit inquiry including information requesting settlement credit inquiry processing for the transaction; The request information is transmitted to the credit card company server 10 via a communication I/F (not shown).

When the credit reference request information is received from the store terminal 40A through the communication I/F 14, the control unit 11 refers to the user registration data 153 and identifies the contractor ID corresponding to the received credit card information. Then, among the user management data stored in the user management database 159A, the information on the received transaction is stored in the transaction data of the user management data corresponding to the identified contractor ID. Then, the control unit 11 executes credit inquiry processing based on the received credit inquiry request information (C110). Then, control unit 11 transmits credit inquiry result information including credit inquiry result information to store terminal 40A as an example, not limitation, via communication I/F 14 (C120).

When the credit inquiry result information is received from the credit card company server 10 via the communication I/F, the control unit of the shop terminal 40A displays the credit inquiry result on the display unit (not shown) based on the received credit inquiry result information. (B120). Then, the control section of the store terminal 40A returns to the beginning.

The credit card company server 10 may or may not transmit the credit inquiry result information also to the terminal 20A.
In this case, when the communication I/F 22 receives the credit inquiry result information from the credit card company server 10, the control unit 21 causes the display unit 24 to display the credit inquiry result based on the received credit inquiry result information. can do.

In this embodiment, regardless of whether the credit inquiry result is "approved" or "rejected", the credit The card company server 10 is transmitting credit inquiry result information.

By way of example and not limitation, billing information may be sent to user A. At the timing of notifying A (for example, but not limited to, the timing set by the credit card company, such as several days later, one week later, etc.), the control unit 11 receives information on billing of the purchase amount (not limited to, but for example, Product purchase information, receipt information, transaction data (transaction ID, store ID, etc.)) and information for setting which bank account to transfer the purchase amount from (for example, not as a limitation, credit card company (C130).

When billing information is received from the credit card company server 10 via the communication I/F 22, the control unit 21 causes the display unit 24 to display the received billing information (or information based thereon) (A130). Specifically, as a non-limiting example, product purchase information and link information to a web page of a credit card company (as a non-limiting example, a payment account setting page) are displayed on the display unit 24 .

Thereafter, based on the billing information displayed on the display unit 24, the control unit 21 determines whether or not an input for setting a payment account has been made via the input unit (A140). Specifically, as an example and not a limitation, it is determined whether or not an operation via the input section for link information to a credit card company's web page (payment account setting page) has been detected.
"Payment account establishment" in this context means, by way of example and not limitation, to establish a payment account for each transaction as it occurs.

When determining that the input for setting the payment account has not been made (A140: NO), the control unit 21 advances the processing to A195.
On the other hand, if it is determined that an input for setting a payment account has been made (A140: YES), the control unit 21, as a non-limiting example, sends payment account setting request information for moving to the payment account setting page, It is transmitted to the credit card company server 10 through the communication I/F 22 (A150). In this case, the payment account setup request information may include, by way of example and not limitation, at least the transaction ID information of the billing information as information for navigating to the payment account setup page.

After step C130, the control unit 11 determines whether or not payment account setting request information has been received (C140).
If it is determined that the payment account setting request information has not been received (C140: NO), the control section 11 advances the process to step C180.

On the other hand, if it is determined that the payment account setting request information has been received (C140: YES), the control unit 11, based on the received payment account setting request information, collects information related to billing of the settlement amount (example, not limitation). , product purchase information, receipt information, etc.), bank account information linked to the credit card (examples without limitation, bank name, account number, etc.) and other information necessary to set up a payment account (as a non-limiting example, the first icon corresponding to the bank account, the second icon to be stored and determined after selecting the first icon, etc.), and the information for setting the payment account, including Send (C150).

When the payment account setting information is received from the credit card company server 10 via the communication I/F 22, the control unit 21 receives the received payment account setting information (or information based thereon) (for example, not limitation, payment account setting screen) is displayed on the display unit 24 (A160).
As a non-limiting example, product purchase information (date and time of purchase, store of purchase, purchase amount, etc.), bank account information linked to credit cards (bank name, account number, etc.), necessary for setting up a payment account A payment account setting screen including information such as other information (first icon, second icon, etc.) can be displayed on the display unit 24, for example.

After that, the control unit 21 receives an input for selecting a payment account from the user via the input unit (A170). In this case, as a non-limiting example, the first icon displayed on the display unit 24 of the terminal 20A (in this example, the first icon corresponding to Bank A and the first icon corresponding to Bank B are the first icons corresponding to Bank A). The first icon) is user A. After being manipulated (tapped, for example and not by way of limitation) by user A.A, a second icon (by way of example and not by way of limitation, a "save" icon) is displayed by user A.A. When operated (tapped as an example, not as a limitation) by A, the control unit 21 sends payment account selection information including information on the selected bank account (in this example, the bank account of A bank) to the communication I/ It is transmitted to the credit card company server 10 by F22 (A180).

When the communication I/F 14 receives the payment account selection information from the terminal 20A, the control unit 11 performs payment account setting processing (C160). Specifically, by way of example and not limitation, among the user management data in which the contractor ID of the target contractor (user A.A in this example) is stored, the corresponding transaction ID of the payment account setting data The account ID corresponding to the payment account specified from the received payment account selection information is stored in the payment account ID.
That is, in this embodiment, the credit card company server 10 sets the payment account.

After that, the control unit 11 transmits payment account setting completion information for notifying that the setting of the payment account is completed to the terminal 20 via the communication I/F 14 (C170).

When the payment account setting completion information is received from the credit card company server 10 via the communication I/F 22, the control unit 21 receives the received payment account setting completion information (or information based thereon) (for example, not limitation, payment account setting completion screen) is displayed on the display unit 24 (A190).
As a non-limiting example, a payment account setting completion screen containing information such as product purchase information and payment account information (such as information notifying that one of the bank accounts has been set as the payment account) is displayed on the display unit 24. It is possible to

Thereafter, the control unit 21 determines whether or not to end the processing (A195), and if it determines to continue the processing (A195: NO), returns to the beginning.
On the other hand, if the control unit 21 determines to end the process (A195: YES), it ends the process.

When the payment account selection information is received from the terminal 20A through the communication I/F 14 and the payment account setting completion information is transmitted, the control unit 11 determines whether or not the account transfer request condition is satisfied (C180).
The account transfer requirement is a condition for requesting (requesting) the bank server 50 for account transfer. It was 24:00 on the 25th."

If it is determined that the account transfer request condition is satisfied (C180: YES), the control unit 11 sends the account transfer request information to the corresponding bank server 50 based on the transaction data and payment account setting data included in the user management data. , through the communication I/F 14 (C190).
Specifically, the payment account setting data is referred to, and for each payment account ID, the transaction ID stored in association with the payment account ID is specified. Then, the transaction data is referred to, and the sum of the purchase amounts stored in association with the specified transaction ID is calculated as the transfer request amount for the payment account. Then, referring to the partner bank data 155, the corresponding partner bank server URI is acquired for each payment account ID, and the calculated transfer request amount and the account transfer token stored in association with the payment account ID are included. The account transfer request information is transmitted to the corresponding bank server 50 via the communication I/F 14 with the corresponding partner bank server URI as the access destination.
Then, the control unit 11 saves, deletes, or resets the latest payment account setting data as the payment account setting data for the current month.

Processing between the credit card company server 10 and the bank server 50 can be realized by an application programming interface (API) or the like. This is the same below.

After that, the control unit 11 determines whether or not to end the process (C195), and if it determines to continue the process (C195: NO), it returns to the beginning.
On the other hand, if it is determined to end the process (C195: YES), the control unit 11 ends the process.

When account transfer request information is received from the credit card company server 10 via a communication I/F (not shown), the control unit (not shown) of the A bank server 50A performs account transfer processing based on the received account transfer request information. (D190).

After that, the control unit of the A bank server 50A determines whether or not to end the processing (D195), and if it determines to continue the processing (D195: NO), returns to the beginning. On the other hand, if it is determined to end the process (D195: YES), the process ends.

Similarly, when account transfer request information is received from the credit card company server 10 via a communication I/F (not shown), the control unit (not shown) of the B bank server 50B, based on the received account transfer request information, Account transfer processing is executed (E190).

After that, the control unit of the B bank server 50B determines whether or not to end the processing (E195), and if it determines to continue the processing (E195: NO), returns to the beginning. On the other hand, if it is determined to end the process (E195: YES), the process ends.

In the above process, when the account transfer request condition is satisfied (C180: YES), the credit card company server 10 transmits the account transfer request information to the bank server 50, and the bank server 50 performs the account transfer process. However, it is not limited to this.
As an example and not a limitation, step C180 is omitted and the control unit 11 of the credit card company server 10 executes step C190 after C170. That is, each time the payment account setting process is performed, account transfer request information including the purchase amount corresponding to the transaction is transmitted to the bank server 50 .

In this case, the bank server 50 cumulatively adds and updates the purchase amount based on the account transfer request information transmitted from the credit card company server 10 for each transaction. Then, the bank server 50 transfers the stored latest cumulative amount to the payment account when the account transfer condition (as an example, not limitation, the date and time of account transfer in credit card settlement) is met. As the amount of money, it is possible to perform account transfer processing.

In addition, the plurality of accounts (plurality of account information) does not necessarily have to be an account (account information) whose name is the user of the terminal 20, and may be an account (account information) related to the user of the terminal 20. . This can also include things like so-called shared wallets.
Similarly, the credit card does not necessarily have to be a credit card whose name is the user of the terminal 20 , and may be a credit card related to the user of the terminal 20 .
Although the details will be described later, by way of example and not limitation, the case of applying credit cards such as (A) a corporate credit card, (B) a family credit card, etc. is one example of these.

Also, in the above process, the purchase information (as an example, but not as a limitation, billing information) is displayed on the display unit 24 of the terminal 20, after which a plurality of account information related to the user of the terminal 20 (such as registered bank account information) is displayed, but it is not limited to this.

By way of example and not limitation, purchase information and multiple account information may be displayed on the same screen (or same page).
In this case, purchase information and a plurality of account information may be displayed at the same time, or may be displayed at the same time.
Also, in this case, the purchase information and the plurality of account information may be displayed in a positional relationship and manner in which both are visible, or in a positional relationship and manner in which only one of the information is visible. may be displayed as
As a non-limiting example, after the purchase information is displayed on one screen, a plurality of account information may be displayed so as to overlap the purchase information.

It should be noted that this display method is not limited to the case of displaying purchase information and a plurality of account information, and can be similarly applied to the case of displaying two or more types of information.

<Effect of the first embodiment>
In this embodiment, the terminal 20 uses billing information (not limited to, example of purchase information) is received by the communication I/F 22 . Then, the terminal 20 displays the received billing information and the registered bank account information of the user of the terminal 20 itself (not limited, but an example of a plurality of account information related to the user of the terminal) on the display unit 24 (not limited to , an example of the terminal display). Then, the terminal 20 recognizes that one account (not limited, but an example of a first account related to the first account information) has been selected as a payment account by the user of its own terminal 20 based on the registered bank account information. Based on this, payment account setting completion information (not limited to, but an example of first information about paying at least part of the purchase information with a first account related to the first account information) is displayed on the display unit 24. showing.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to allow the terminal user to confirm the goods or services purchased by the terminal user with deferred payment. Also, based on the selection of the first account information from the plurality of account information, the user of the terminal confirms that payment for at least a portion of the purchase information is to be made with a first account associated with the first account information. In addition, payment for goods or services purchased on a deferred basis can be made from the first account.

Here, the purchase information may be received by the terminal from the server of the post-payment service provider such as the server of the credit card company, or may be received from the terminal of the store where the transaction was made, the EC server, or the like. may
Further, although the details will be described later, it is also possible to receive from a server of another service provider or the like.

Further, in this embodiment, when the user of the terminal 20 selects the first account information from the registered bank account information and the first billing information from the billing information, the terminal 20 selects the first account. First payment account setting completion information (not a limitation, but an example of the first information about paying the first purchase information with the first account) indicating that the setting of the payment account has been completed is displayed on the display unit 24. , when the user of the terminal 20 selects the second account information from the registered bank account information and the second billing information from the billing information, it indicates that the second account has been set as the payment account. 4 shows a configuration for displaying on the display unit 24 the second payment account setting completion information (not limited to, but an example of the second information regarding paying the payment of the second purchase information with the second account).
As an example of the effect of the embodiment obtained by such a configuration, each postpaid purchase is paid from the account associated with the account information selected by the user of the terminal from among the plurality of account information. can be confirmed by the user of the terminal and the payment can be made from the corresponding account.

In addition, in the present embodiment, the terminal 20 performs bank transfer from among a plurality of registered bank account information for one of the billing information (not limited but an example of the first purchase information). Information such as a first icon for selecting account information (not limited, but an example of third information regarding the ability to select at least one account information from among a plurality of account information) is displayed on the display unit 24 showing configuration.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to select at least one account information from a plurality of account information for the first purchase information of the purchase information. The user can be notified.

Also, in the above, the registered bank account information is stored in the credit card company server 10 in association with the credit card information related to the user of the terminal 20 (not limited, but an example of credit card information related to the user of the terminal). can be made to be
As an example of the effect of the embodiment obtained by such a configuration, a plurality of account information can be associated with credit card information related to the user of the terminal.

Note that the registered bank account information is associated with credit card information related to the user of the terminal 20 (not a limitation, but an example of credit card information related to the user of the terminal) and stored in the storage unit 28 of the terminal 20. You may do so.

Also, in this case, the deferred payment is made by credit card, and the payment for at least part of the billing information made by the credit card is paid from the payment account (first account) selected by the user of his/her own terminal 20. can be made to be
As an example of the effect of the embodiment obtained by such a configuration, payment for at least a part of the purchase information of the product or service purchased by the terminal user with deferred payment is made according to the first account information selected by the terminal user. It can be done from the associated first account.

Also, in this case, deferred payment can include payment by a set date or by a set due date.
As an example of the effect of the embodiment obtained by such a configuration, deferred payment can be made from an account selected by the user of the terminal by a set date or a set date.

In addition, in this embodiment, the credit card company server 10 (not limited, but an example of a server) transmits transaction information (not limited, but an example of purchase information) by the user of the terminal 20 by credit card payment to the store terminal 40 or EC It receives from the server and transmits the corresponding billing information (purchase information) to the terminal 20 via the communication I/F 14 . The credit card company server 10 then sends payment account selection information (one example, without limitation, of information relating to paying at least part of the purchase information by a first of a plurality of accounts associated with the user of the terminal). A configuration for receiving from the terminal 20 by the communication I/F 14 is shown.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to receive purchase information of a purchase made by a terminal user with deferred payment, transmit the purchase information to the terminal, and notify the terminal user of the purchase information. can. Also, receiving information from the terminal relating to paying at least a portion of the purchase information by a first account of a plurality of accounts associated with the user of the terminal, thereby setting the account for payment to be the first account, etc. can do.

<First modification (1)>
In the above embodiment, when the control unit 11 of the credit card company server 10 receives the payment account selection information from the terminal 20, it confirms with the user whether there is no problem in setting the selected bank account as the payment account. (hereinafter referred to as “payment account setting confirmation information”) to the terminal 20. Then, the terminal 20 may display this payment account setting confirmation information on the display section 24 . In this case, the control unit 11 can perform the payment account setting process when receiving the information of “confirmation OK” from the terminal 20 .

Also, based on the selection of one bank account (first account) as the payment account, the control unit 11 transmits notification information to the effect that the first account has been selected to the terminal 20 . Then, the terminal 20 may display this notification information on the display section 24 .

In addition, based on the fact that one bank account (first account) is selected as a payment account, the control unit 11 causes the selected first account to be displayed in a display mode different from the bank accounts that are not selected. You may do so. In this case, by way of example and not limitation, the selected first account may be highlighted, or the like.

These are examples of first information relating to paying at least part of the purchase information with a first account associated with the first account information, and a display of this first information.

<First modification (2)>
It is also possible to implement the technique of the above embodiment by an application (hereinafter referred to as "credit card application") provided by a credit card company (credit card company server 10).
In this case, the terminal 20 can acquire and install a credit card application from the credit card company server 10 in advance, and execute the credit card application stored in the storage unit 28 .

In this case, the account data of the credit card application can be stored and managed in the storage unit 15 of the credit card company server 10 as an example and not as a limitation.

<First modification (3)>
After the payment account is established in the above example, the payment account may be changed to another bank account based on input by the user of terminal 20 to change the payment account.
In the following, this is referred to as "change of payment account".

In this case, the user of the terminal 20 accesses the payment account setting page of the credit card company server 10 from the terminal 20 and makes an input to change the payment account. Then, the credit card company server 10 updates the payment account ID associated with the corresponding transaction ID in the payment account setting data of the user management data of the user to the payment account ID corresponding to the designated payment account. to change the payment account.

<First modification (4)>
The method of the above embodiment can be similarly applied to the above-mentioned (2) bill payment.
In this case, the processing performed by the credit card company server 10 can be replaced with the processing performed by a device such as the server of the payment service provider, so that the processing can be configured in the same manner as in the above embodiment.

Of the (2) payment on a cost basis, when (2-1) lump-sum payment is applied, it is almost the same as the above (1) credit card payment.
Therefore, in the following, the processing in the case of applying the (2-2) pay-as-you-go method among the (2) pay-as-you-go will be exemplified.

FIG. 1-13 is a diagram showing an example of the flow of processing executed by each device in this modified example.
This processing is an example of processing in the case of applying pay-as-you-go payment. Similar to credit card payment, a payment account is set based on user input from the web page of the pay-as-you-go company, etc., and It is described as an example of processing for performing a transfer.

As an example and not as a limitation, at the time of a contract for payment on demand, the user of the terminal 20 notifies a plurality of bank account information related to the user to the payment on payment business server (hereinafter referred to as "payment on payment"). (referred to as a “business server”).

In this figure, from the left, processing executed by the control unit 21 of the terminal 20A, processing executed by the control unit of the payment service provider server, processing executed by the control unit of the A bank server 50A, and control of the B bank server 50B. 4 shows an example of processing executed by a unit.

In (2) Tsukebarai, processing equivalent to (1) credit inquiry in credit card payment is performed based on information such as the purchase amount, frequency of use of Tsukebarai, past payment history, etc. can be made
Note that processing corresponding to this credit inquiry may not be performed. In addition, the credit examination may be performed at the timing of a contract for payment on credit, or the like.

After executing the above-described step corresponding to C170, the control unit of the payment service provider server transmits account transfer request information to the bank server 50 of the bank corresponding to the payment account set in the payment account setting process through the communication I/F. is transmitted (G190).
Unlike the case of credit card payment, in pay-as-you-go payment, for example and not limitation, account transfer can be made each time a transaction (each time a product or service is purchased) by the user of terminal 20 is made. In this case, the bank server 50 to which the account transfer request information is sent in G190 is the bank server corresponding to one bank account alternatively set as the payment account for the transaction.

After that, the control unit of the service provider server determines whether or not to end the processing (G195), and if it determines to continue the processing (G195: NO), returns to the beginning.
On the other hand, if it is determined to end the process (G195: YES), the control unit of the payment-on-deposit business server ends the process.

<First modification (5)>
Payment accounts are not limited to methods in which payment accounts are set up via the credit card company's web page or credit card application, but payment accounts are set up via an application different from the credit application provided by a business operator different from the credit card company. may be set.

Applications that are different from credit card applications include, by way of example and not limitation, the following applications.
(A) Chat application (B) Electronic money application (payment application, electronic money settlement application)

A chat application is an application provided by a chat service provider, and is an application for users to chat.
By way of example and not limitation, this includes messaging applications provided by messaging service providers.

An electronic money application is an application provided by an electronic money service provider, and is an application for a user to make an electronic payment (payment by electronic money as an example, not a limitation).

In this modified example, the case where the above (A) chat application is applied is illustrated.
Also, in this modified example, a messaging application is illustrated as an example of a chat application. In other words, it is assumed that the messaging application installed in the terminal 20 executes various processes according to the present disclosure.

In addition, in this modification, the messaging service is an instant messaging service: IMS (Instant Messaging Service) that performs simple message transmission and reception between a plurality of devices via the server 60, and this messaging application is appropriately referred to as "Messaging App". will be illustrated and described as

A messaging service (including IMS) can also be considered as one form (one form) of a social networking service (SNS). Thus, a distinction may or may not be made between messaging services and social networking services. That is, a social networking service may or may not include a messaging service.

In addition to simple text, the message includes, without limitation, image information (including at least one of still image information and moving image information), sound information (including voice information), operation information ( buttons, icons, etc.), specific information/communication information/link information (URL, URI, etc.), and various other types of information that can be transmitted and received between devices.

Text may include, by way of example and not limitation, at least one of national characters represented by character codes, extended characters, machine-dependent characters, numerals, symbols, graphics and symbols.
Note that the text may not include at least one of the characters, extended characters, machine-dependent characters, numerals, symbols, graphics, and symbols described above, and may include other text.

Image information (images) may include, by way of example and not limitation, at least one of various types of image information such as icons, buttons, stamps, pictograms, banner images.

In this specification, information transmitted and received by the messaging service is referred to as "message", but this may be referred to as "content" in a broader sense.
In this case, the content includes text, image information (including at least one of still image information and moving image information), sound information (including sound information), operation information (button , icons, etc.), specific information, communication information, and link information (URL, URI, etc.), which can be transmitted and received between devices.
Also, by way of example and not limitation, the message may be text, and the "content" may include the message and information other than the message.

A messaging service herein is an example of a chat service.
The messaging service is configured so that users can chat using chat rooms.
In the following description, a UI (User Interface) or a GUI (Graphical User Interface) that allows each user to view content transmitted and received between terminals of a plurality of users will be referred to as a "talk room" as appropriate.
Note that the talk room may or may not be called a chat room.

In addition, as a non-limiting example, the talk room includes a one-to-one user talk room (hereinafter referred to as a "one-to-one talk room"), and a group talk room including a plurality of users (hereinafter referred to as a group talk room). (referred to as a “group talk room”). The talk room in this case means a UI or GUI that allows users included in the group to view content transmitted and received between terminals of the group including a plurality of users.

Also, in this specification, the user of the terminal 20 who uses the messaging service (messaging application) is referred to as "general user", and the account of this general user is referred to as "general account".
On the other hand, a user of a business device or a business terminal (not shown) that uses the messaging service is called an "official account (OA) business operator", and the account of this business operator is called an "official account". called.
In other words, in this specification, accounts of messaging services include general accounts and official accounts.

A business operator having an official account can also transmit and receive messages to and from other devices via the server 60 by way of a business device or business terminal, for example and not limitation, in the same way as the terminal 20 having a general account. It is possible. As a non-limiting example, similar to the case where messages are sent to other terminals 20, messages sent from the terminal 20 of a user having a general account to the operator device or operator terminal are sent via the server 60. It is delivered to the operator device or operator terminal. Then, the message history is displayed as a talk room or the like on the display unit (not shown) of the operator's device or operator's terminal.

In addition, examples of talk rooms include, but are not limited to, "one-to-one talk rooms", which are one-on-one user talk rooms, and "group talk rooms", which are groups containing a plurality of users. As an example, a talk room with an OA business (hereinafter referred to as "OA talk room") can be included.

In the following description, as an example and not a limitation, the talk information is stored and managed in the storage unit 65 of the server 60, but the talk information added and updated by the server 60 is transmitted to the terminal 20, It is assumed that the storage unit 28 also stores and holds the talk information separately from the server 60 .

Talk information is, for example and not limitation, a series of talk content including content (messages, not limitation) exchanged between accounts (including one-on-one and groups), history of content exchange ( content transmission/reception history).

In this case, due to problems such as the storage capacity of the server 60, the talk information stored and managed by the server 60 may be stored and managed by the server 60 after a certain period of time (a period of several weeks, not a limitation) has passed. 60 can be deleted from the storage unit 65 .
On the other hand, the data of the talk information stored in the storage unit 28 of the terminal 20 can be held unless the user of the terminal 20 inputs deletion through the input unit.

However, this is merely an example, and the present invention is not limited to this form.
As a non-limiting example, the terminal 20 may not hold the talk information, and the terminal 20 may acquire and display the talk information stored and managed by the server 60, or may not. good too.

<System configuration>
FIG. 1-14 is a diagram showing an example of the system configuration of a communication system 1B in this modified example.
The communication system 1B is a system obtained by adding a server 60 as a component to the communication system 1A of FIG. 1-1.

The server 60 (not limited to, but an example of a server, an information processing device, an information management device) has a function of providing a predetermined service (messaging service in this modified example) to the terminal 20 .
The server 60 may be any information processing device capable of realizing the functions described in this modified example. Server 60 includes, by way of example and not limitation, server devices, computers (including but not limited to desktops, laptops, tablets, etc.), media computer platforms (including but not limited to cable, satellite set-top boxes, digital video recorders, etc.). ), handheld computing devices (by way of example and not limitation, PDAs, email clients, etc.), or other types of computers or communication platforms. Also, the server 60 may be expressed as an information processing device. If there is no need to distinguish between the server 60 and the terminal 20, the server 60 and the terminal 20 may or may not be represented as information processing devices.

The server 60 includes a control unit 61 (CPU), a storage unit 65, a communication I/F 64 (interface), an input/output unit 62, and a clock unit 69 as an example and not limitation. Each component of the HW of server 60 is interconnected via bus B, by way of example and not limitation. It should be noted that the HW of the server 60 does not have to include all components as the HW configuration of the server 60 . By way of example and not limitation, the HW of server 60 may or may not be configured to remove individual components or multiple components.

Note that the HW of the server 60 can be the same as that of the credit card company server 10 or the like as an example and not as a limitation, and therefore will not be described again.

In this modification, the user of the server 60 is assumed to be a messaging service provider (hereinafter referred to as "messaging service provider"). Also, the messaging service provider shall be a business different from the credit card company.

In this case, when a credit card payment is made by the user of the terminal 20, the credit card company (credit card company server 10) can grasp which user made the credit card payment. The party (server 60) needs to know which user has made the credit card payment.

As a method for realizing this, one of the following methods can be applied as an example and not as a limitation.
(X) The user of the terminal 20 notifies the credit card company of the account information of the messaging application (for example, without limitation, a messaging application ID, etc., which will be described later). By way of example and not limitation, terminal 20 transmits account information to credit card company server 10 . Then, in the credit card company server 10, the user of the terminal 20 notifies the credit card information to the messaging service provider. By way of example and not limitation, terminal 20 transmits credit card information to server 60 . Then, in the server 60, a method in which credit card information is registered in association with the account information of the messaging service.

Although any method can be applied, in this modified example, as an example rather than a limitation, the case of applying the above method (X) will be illustrated.

<Functional configuration>
(1) Credit card company server 10
FIG. 1-15 is a diagram showing a data configuration example of a user management database 159B, which is an example of the user management database 159 stored in the storage unit 15 of the credit card company server 10 in this modification.
Each user management data stores the aforementioned subscriber ID, transaction data, registered bank account data, payment account setting data, as well as, by way of example and not limitation, the messaging application ID of the user of this subscriber ID. .

This messaging application ID may be used at some time (as a non-limiting example, but not as a limitation) when using the credit card service while already using the messaging service. When the messaging service is used in the state of using , the messaging application ID is transmitted from the terminal 20 to the credit card company server 10 at a timing such as when the messaging service is contracted.
Alternatively, the messaging application ID is transmitted from the server 60 to the credit card company server 10 . Then, the credit card company server 10 can associate the received messaging application ID with the contractor ID and store and register it in the user management data.

(2) Functional Configuration of Server 60 FIG. 1-16 is a diagram showing an example of functions realized by the control unit 61 of the server 60 in this modification.
Control unit 61 includes, as a functional unit, messaging application management processing unit 611 that executes messaging application management processing according to messaging application management processing program 651 stored in storage unit 65 .

FIG. 1-17 is a diagram showing an example of information stored in the storage unit 65 of the server 60 in this modification.
Storage unit 65 stores a messaging application management processing program 651 executed as messaging application management processing, account registration data 653 , and account management database 655 as an example and not limitation.

Account registration data 653 is registration data relating to a messaging application account, and an example of the data configuration is shown in FIG. 1-18.
Account registration data 653 stores, by way of example and not limitation, user names, messaging application IDs, and other registration information in association with each other.

The user name is the name of the user of the terminal 20 who uses the messaging application, and as an example and not a limitation, the name registered by the user of the terminal 20 when using the messaging application is stored.

A messaging application ID is information used to identify a messaging application account, or the account itself.
This messaging application ID is preferably a unique value for each account, and is set and stored by the server 60 as a unique value (unique value) for each account, by way of example and not limitation.
The messaging application ID is information associated with the terminal 20 or the user of the terminal 20, and is an example of information about the terminal or information about the user of the terminal.

The other registration information includes, for example and not limitation, identification information for identifying the terminal 20, the telephone number of the terminal 20 (terminal telephone number), the e-mail address (terminal e-mail address), and the Various information such as authentication information such as a password (login password, authentication password, etc.) can be included.

The identification information for identifying the terminal 20 may be, by way of example and not by way of limitation, a terminal ID (by way of example and not by way of limitation, IMEI (International Mobile Equipment Identity)).
Also, the identification information for identifying the user of the terminal 20 can be, by way of example and not limitation, a messaging application ID.
A “user ID” may or may not be used instead of the messaging application ID.

Also, if the application allows only one account to be registered for one terminal 20, as an example without limitation, "identification information for identifying the terminal 20=identification information for identifying the user of the terminal 20= Application ID".

Also, by way of example and not limitation, one user ID may or may not be allowed to be assigned multiple terminal IDs.

It is also possible to apply a method of managing an account using information such as a terminal telephone number instead of various IDs such as an application ID.
In this case, information such as a terminal telephone number can be stored in the account registration data 653 instead of storing ID information such as an application ID in the account registration data 653 .

The account management database 655 is a database for managing accounts stored in the account registration data 653, and an example of the data structure of the account management database 655A is shown in FIG. 1-19.
Account management data is stored in account management database 655A as management data for each messaging application ID stored in account registration data 653 .

Each account management data stores, by way of example and not limitation, friend data, talk information data, and transaction data.

The friend data is data related to accounts registered as friends by the account of this messaging application ID. Accounts that are registered as friends can include the above-mentioned official account in addition to the above-mentioned general account.

In this modification, it is assumed that the user of the terminal 20 performs an operation to add the credit card company's official account as a friend, and the credit card company's official account is registered in the friend data on the server 60 .

The talk information data is the talk information data of the account of this messaging application ID.
As an example and not a limitation, the server 60 receives message information sent from the terminal 20 that sent the message information, and performs processing to add the received message information to the chat room of the corresponding account. Specifically, in the account management data of the corresponding account in the account management database 655A, the received message information is added and updated to the talk information of the corresponding talk room. Then, the server 60 transmits the content added to the talk room (message information added to the talk room) to the terminal 20 of the destination user. Thereby, the message information in the talk room displayed on the display unit 24 of the terminal 20 is updated.

The transaction data is purchase information data that is stored based on the billing information (purchase information) transmitted from the credit card company server 10 and is purchased by the user of the terminal 20 by credit card payment.
The transaction data stored in the account management data may be data containing at least part of the information stored in the transaction data stored in the user management data of the credit card company server 10 .

(3) Functional Configuration of Terminal 20 FIG. 1-20 is a diagram showing an example of functions executed by the control unit 21 of the terminal 20 in this modification.
Control unit 21 includes, as a functional unit, in addition to terminal main processing unit 211 described above, messaging application processing unit 213 that executes messaging application processing according to messaging application program 283 stored in storage unit 28 as an example and not limitation. .

FIG. 1-21 is a diagram showing an example of information stored in the storage unit 28 of the terminal 20 in this modified example.
In addition to the above-described terminal main processing program 281, the storage unit 28 stores, for example and not limitation, a messaging application program 283 and a messaging application ID 285, which is messaging application account data.

<Overview of principle and processing>
FIG. 1-22 is a diagram for explaining the principle of the credit card settlement service in this modified example, and illustrates the flow of credit card settlement.
Note that the description of the same parts as in FIG. 1-9 is omitted.

(5) When the credit card company server 10 pays the purchase amount to the store, (6-1) the credit card company server 10 transmits billing information to the server 60 . Then, (6-2) the server 60 transmits to the terminal 20 billing message information, which is message information of the messaging application and corresponds to the billing information, as an example and not a limitation.

(7-1) The user of the terminal 20 who has received the billing message information makes an input to select a payment account based on the billing message information displayed on the display unit 24 of the terminal 20. Account is set.

Note that the entity that sets up the payment account (payment account setting process) can be one of the following as an example, not as a limitation.
・Credit card company server 10
・Server 60

When the payment account is set by the credit card company server 10, (7-1) payment account selection information is transmitted from the terminal 20 to the credit card company server 10. FIG. A payment account is set by the credit card company server 10 .
On the other hand, when the payment account is set by the server 60, (7-1) payment account selection information is transmitted from the terminal 20 to the server 60. FIG. After the payment account is set by the server 60, (7-2) payment account setting information is transmitted from the server 60 to the credit card company server .
Details of this will be described later.

<Display screen>
FIG. 1-23 is a diagram showing an example of screen transitions displayed on the display unit 24 of the terminal 20A in this modification.
The left side of FIG. 1-23 is an example of the chat room screen of the messaging application, and at the top center of the screen, the characters "Messaging App" are displayed as the name of the messaging application. Also, an icon image and a user name (user A.A in this example) in the messaging application of the user of this terminal 20 are displayed at the top right of the screen.

In addition, below that, as a non-limiting example, the name of the talk room (hereinafter referred to as "talk A talk room name display area CLR is provided. The talk room name display area CLR can also be said to be an area indicating the page in the messaging application where the user is currently located (the talk room in this example).

In this example, the talk room name display area CLR includes, by way of example and not limitation, the user A. Information indicating that A is an OA talk room for chatting with "X Card", a credit card company, as a chat partner (in this example, the "OA" icon and the characters "X Card") is displayed. ing.

User A. A talk area is configured for A and X card to talk in an interactive manner, and message information (message) originating from X card, which is the other party, is displayed on the left side of the screen, and on the right side of the screen. is user A. The message information of A is configured to be displayed.

In this example, user A. Billing message information containing information about one transaction by A at store A ("Usage information" on the screen) is transmitted with the X card as the sender, and the terminal 20A receives the billing message information via the server 60. Based on what has been done, billing message information is displayed on the left side of the OA talk room screen in association with the icon image of the X card.

At the bottom of the billing message information is a button operated to set up a payment account. A link button BT2 is provided that includes the text "Click here to set up a payment account>" linked to the setting page of the payment method.

When this link button BT2 is tapped, a transition is made to the web page of the credit card company via the messaging application, and as a non-limiting example, the web page of the credit card company similar to that shown in the center of FIG. 1-10 is displayed. .
The rest is the same as in FIG. 1-10.

<Processing>
1-24 and 1-25 are flow charts showing an example of the flow of processing executed by each device in this modified example. This processing is an example of processing when the server 60 is a server of a messaging service provider.
In this figure, from the left side, processing executed by the control unit 21 of the terminal 20A, processing executed by the control unit 61 of the server 60, processing executed by the control unit 11 of the credit card company server 10, and control of the A bank server 50A. 6 shows an example of processing executed by the bank B server 50B and processing executed by the control unit of the B bank server 50B.

After C120, the control unit 11, as a non-limiting example, sends the billing information including the messaging application account information (as a non-limiting example, the messaging application ID) of the user of the target contractor ID to the communication I/F 14. to the server 60 (C131).

When the billing information is received from the credit card company server 10 via the communication I/F 64, the control unit 61 of the server 60 receives the message information for the chat room, which corresponds to the received billing information (hereinafter referred to as "billing message information”). Then, the control unit 61 adds the generated billing message information to an OA talk room having the messaging application ID included in the received billing information and having the talk partner's account as the official account of the credit card company. . That is, the talk information data of the account management data corresponding to the messaging application ID is updated in the account management database 655A. And the control part 61 transmits the added message information to the terminal 20 (this example terminal 20A) of said messaging application ID by communication I/F64 (B131).

After that, the control unit 61 determines whether or not to end the process (B195), and if it determines to continue the process (B195: NO), returns to the beginning. On the other hand, if it is determined to end the process (B195: YES), the control unit 61 ends the process.

When receiving the billing message information from the server 60 through the communication I/F 22, the control unit 21 causes the display unit 24 to display the OA talk room including the received billing message information (A131). Then, the control unit 21 advances the processing to A140.
In other words, in this process, the terminal 20 makes a transition from the messaging application to the web page of the credit card company, performs input for setting up a payment account, and the payment account setting process is performed by the credit card company server 10 (C160). .

In this example, a transition is made from the chat room of the messaging application to the web page of the credit card company, and the payment account is selected.
As another method, a payment account may be selected by transitioning from the chat room of the messaging application to a payment account setting page of the messaging application.

As a non-limiting example, in the message information for payment account setting displayed in the chat room of the messaging application, the display mode (first display mode) of the bank account selected as the payment account is changed so that the user can easily understand it. It is conceivable to display in a display mode (second display mode) different from the bank accounts not selected as payment accounts.
However, as described above, it is possible to apply a mode in which the message information transmitted to the terminal 20 is stored in the storage unit 28 of the terminal 20 and saved. It is good to make the transition to the page and select the payment account.

However, since it can be said that generating message information in which the display mode or the like is changed on the server 60 side and transmitting it to the terminal 20 does not correspond to alteration of the message information, such a technique can be applied. .

Further, in the above process, when the payment account is set, the payment account setting completion message information is transmitted from the server 60 to the terminal 20 .
In this regard, if the payment account is changed to another bank account based on the user's input to change the payment account, payment account change message information indicating that the payment account has been changed is sent from the server 60 to the terminal. 20.

<Another method>
FIG. 1-26 is a diagram showing a data configuration example of an account management database 655B, which is another example of the account management database 655 stored in the storage unit 65 of the server 60 in this modification.
In this account management database 655B, in each account management data, in addition to friend data, talk information data, and transaction data, as a non-limiting example, registered bank account data and payment account setting data are stored. be.

Registered bank account data and payment account setup data may be, by way of example and not limitation, as in user management database 159B of credit card company server 10 .
By way of example and not limitation, the server 60 may at some point obtain registered bank account data from the credit card company server 10 and store it in the account management data.

It should be noted that there is also the idea that users dislike having information about users' bank accounts (which can be said to be information about credit cards in this specification) held and managed by messaging service providers, or that this is not desirable in terms of security. could be.
Therefore, after the server 60 transmits the necessary information to the credit card company server 10 on the closing date (closing date and time) as an example without limitation, the registered bank account data is deleted from the above account management data as an example without limitation. You may make it Similarly, payment account setup data may be erased.

FIG. 1-27 is a diagram showing an example of screen transitions displayed on the display unit 24 of the terminal 20A in this modification.
The left side of FIG. 1-27 shows an OA talk room similar to that of FIG. 1-23, but the content of the displayed billing message information is partially different.
Specifically, at the bottom of the billing message information, a list of bank accounts that you (user A.A in this example) can set as a payment account is displayed. IC3A and icon IC3B of "B bank" are displayed.

As an example and not by way of limitation, when the "A Bank" icon is tapped, a display such as that shown in the center of FIG. 1-27 is provided. Specifically, based on tapping and selecting the bank account of "Bank A" as the payment account in the OA chat room on the left of Figure 1-27, a message originating from myself (user A.A) Message information indicating "Select Bank A" is displayed in a balloon on the right side of the screen.

Confirmation information including text for confirming whether or not to set the bank account of "A Bank" as the payment account is displayed in a pop-up form in the center of the screen.
This confirmation information includes, by way of example and not limitation, the text "Set up payment account with Bank A?" is displayed.

As an example and not by way of limitation, when the "yes" button is tapped, a display such as that shown in FIG. 1-27 right is made. Specifically, based on the fact that the "yes" button is tapped and selected in the OA talk room in the center of FIG. is displayed below the message information labeled "Select Bank A" above.

In addition, based on the fact that the payment account has been set by the server 60, payment account setting completion message information indicating that the payment account has been set is displayed on the OA talk room screen on the left side of FIG. 1-27. It is displayed below the billing message information.

FIG. 1-28 is a flow chart showing another example of the flow of processing executed by each device in this modified example. This processing is an example of processing when the server 60 is a server of a messaging service provider.
When billing information is received from the credit card company server 10 via the communication I/F 64, the control unit 61, based on the registered bank account data stored in the account management data specified from the account information included in the received billing information, Generate billing message information including registered bank account information. Then, the control unit 61 adds the generated billing message information to the OA talk room in which the account of the talk partner is the official account of the credit card company, and transmits the added billing message information to the terminal 20A through the communication I/F 64. (B132).

When the billing message information is received from the server 60 via the communication I/F 22, the control unit 21 causes the display unit 24 to display the OA talk room including the received billing message information (A132). Then, the control unit 21 advances the processing to A140.

When the communication I/F 64 receives the payment account selection information from the terminal 20A, the control unit 61 performs payment account setting processing (B160).
Specifically, among the account management data of the user of the terminal 20A in the account management database 655B, for the transaction of the transaction ID corresponding to the payment account setting data, the account corresponding to the bank account specified from the received payment account selection information Store the ID in the payment account ID.
That is, in this process, the server 60 of the messaging service provider, not the server 10 of the credit card company, performs the payment account setting process.

Thereafter, the control unit 61 generates payment account setting completion message information and adds the generated payment account setting completion message information to the OA talk room. Then, the added payment account setting completion message information is transmitted to the terminal 20A through the communication I/F 64 (B172).

When the payment account setting completion message information is received from the server 60 through the communication I/F 22, the control unit 21 displays the received payment account setting completion message information in the OA talk room (A192). Then, the control unit 21 advances the processing to A195.

After B172, the control unit 61 determines whether or not the payment account setting information transmission condition is satisfied (B180).
The payment account setting information transmission condition is a condition for sending the payment account setting information to the credit card company server 10, and as an example, not as a limitation, is "the date (due date) for requesting account transfer from the partner bank has come". can do.
The payment account setting information is information related to the payment account set in the payment account setting process.

If it is determined that the payment account setting information transmission condition is satisfied (B180: YES), the control unit 61 transmits the payment account setting information corresponding to the latest payment account setting data stored in the account management data of the target account. is transmitted to the credit card company server 10 via the communication I/F 64 (B190). Then, the control unit 61 advances the process to B195.

After C132, the control unit 11 determines whether or not payment account setting information has been received from the server 60 via the communication I/F 14 (C180).

If it is determined that it has been received (C180: YES), the control unit 11 calculates the transfer request amount for each payment account based on the transaction data and the received payment account setting information. Specifically, the payment account setting data is referred to, and for each payment account ID, the transaction ID stored in association with the payment account ID is specified. Then, the transaction data is referred to, and the sum of the purchase amounts stored in association with the specified transaction ID is calculated as the transfer request amount for the payment account. Then, for each payment account, the control unit 11 communicates account transfer request information including the calculated transfer request amount and the account transfer token stored in association with the payment account ID to the corresponding bank server 50. /F14 (C191). Then, the control unit 11 advances the process to C195.

Processing between the server 60 and the bank server 50 can be realized by an application programming interface (API) or the like. This is the same below.

Also, in this modified example, an electronic money application can be applied in place of the messaging application.
In this case, in the communication system 1B, the server 60 is the server of the electronic money service provider, and the messaging application account (as a non-limiting example, the messaging application ID) is the electronic money application account (as a non-limiting example, As the electronic money application ID), the same processing as in the above embodiment can be performed.

In the electronic money application, it is possible to replenish (charge) electronic money and use the charged electronic money to perform electronic money settlement or the like.
In this case, as a charging method, for example, but not limited to, a method of charging using a prepaid card, or a method in which the user requests registration of a bank account to the server 60 and registers the bank account (electronic money application ID) with the user's own account (electronic money application ID). It is possible to apply a method of associating account information and charging from a registered bank account.

In addition, in the electronic money application, in principle, it is necessary for the electronic money service provider to authenticate the identity of the user due to the nature of handling the user's money.
This identification can be performed by requesting the user to present an official certificate such as a driver's license, or by requesting the user to present credit card information.

When requesting the user to present credit card information, the server 60 holds the credit card information in association with the user's account, so that the server 60 can register the user based on the credit card information. The credit card company server 10 can be queried for information such as bank account information and information on transactions made by the user using the credit card.

An electronic money application, which is an application provided as an electronic money service, is hereinafter illustrated and described as a "Payment App" as appropriate.

FIG. 1-29 is a diagram showing a data configuration example of an account management database 655C, which is another example of the account management database 655 stored in the storage unit 65 of the server 60 in this modification.
Each account management data stores, by way of example and not limitation, an e-money application ID, an e-money account balance, transaction data, registered bank account data, and payment account setup data.

The electronic money application ID is information used to identify the electronic money application account, or the account itself.
This electronic money application ID is preferably a unique value for each account, and as an example and not a limitation, the server 60 sets and stores a unique value (unique value) for each account.
The electronic money application ID is information associated with the terminal 20 or the user of the terminal 20, and is an example of information about the terminal or information about the user of the terminal.

The electronic money account balance is the amount of the electronic money account balance of this electronic money application ID (this account).

The registered bank account data and the payment account setting data can be configured, by way of example and not limitation, in the same manner as the user management database 159B of the credit card company server 10 described above.
By way of example and not limitation, server 60 may request registered bank account data from credit card company server 10 and obtain registered bank account data from credit card company server 10 for storage in account management data. can.

FIG. 1-30 is a flow chart showing another example of the flow of processing executed by each device in this modification. This processing is an example of processing when the server 60 is the server of an electronic money service provider.
After B150, the control unit 61 performs payment account setting processing (B160).
Specifically, among the account management data of the user of the terminal 20A in the account management database 655C, for the transaction of the transaction ID corresponding to the payment account setting data, the bank account specified from the payment account selection information received from the terminal 20A The corresponding account ID is stored in the payment account ID.
That is, in this process, the server 60 of the electronic money service provider, not the credit card company server 10, performs the payment account setting process.
Then, the control unit 61 advances the process to B170.

<First modification (6)>
In addition to (A) the case of applying the chat application (messaging application) and (B) the case of applying the electronic money application, as a non-limiting example, an application that allows both chat and payment is applied. It is also possible to As this form, by way of example and not limitation, any of the following forms are conceivable.
(a) Configuration of electronic money service function as one function of chat application (b) Configuration of chat service function as one function of electronic money application (c) Combination of chat service function and electronic money service function Forms Constituting a Composite (Integrated) Application Having a Form Below, a case where these forms are applied will be described.

For the system configuration in this case, as an example and not as a limitation, a configuration similar to that of the communication system 1B (FIG. 1-14) is applied, and the server 60 has a function of providing a messaging service (a function of managing information of a messaging application). and a function of providing an electronic money service (a function of managing electronic money application information).

For simplicity of explanation, here the server 60 is explained as one server having multiple functions.
Alternatively, in the communication system 1B, the server 60 may be divided into a messaging service server (first server) and an electronic money service server (second server).

FIG. 1-31 is a diagram showing an example of screen transitions displayed on the display unit 24 of the terminal 20A in this modification.
The left side of FIG. 1-31 shows an OA talk room screen of a messaging application similar to the left side of FIG. 1-23.
When the link button BT2 containing the words "Click here to set up payment account>" is tapped on this screen, as a non-limiting example, an electronic money application is activated on the terminal 20, and as a non-limiting example, FIG. 31 center screen is displayed.

This screen is a payment account setting screen in the electronic money application, and at the top of the screen, characters of "Payment App", which is the name of the electronic money application, are displayed.
Also below that is information for setting up a payment account.

Specifically, the registered user A. As information about A's bank account, a bank account information display area is configured to display bank account information linked to a credit card (examples, not limitation, bank name, account number, etc.).

Also, on the right of it, there is a first icon display area for displaying a first icon for selecting a bank account for the transfer. A first icon IC1A containing the characters "A bank" corresponding to , and a first icon IC1B containing the characters "B bank" corresponding to B bank are displayed.

In addition, at the bottom of the screen, after selecting the first icon, a second icon display area is configured to display a second button (second icon) for saving/determining the information. , the second button BT3 including the characters "save" is displayed. The function of this second button BT3 is similar to that of the second icon IC2 shown in FIG. 1-10.

In the payment account setting screen shown in the center of FIG. 1-31, as a non-limiting example, when the first icon IC1A corresponding to Bank A is tapped and then the second button BT3 is tapped, as a non-limiting example, , a payment account setting completion screen as shown in the right of FIG. 1-31 is displayed in the electronic money application.

FIG. 1-32 is a flow chart showing another example of the flow of processing executed by each device in this modified example. This processing is an example of processing when the server 60 is the server of a messaging service provider or an electronic money service provider.
After A131, the control unit 21 determines whether or not an input for setting a payment account has been made (A141). Specifically, as a non-limiting example, it is determined whether an input for setting a payment account has been made, such as by tapping a link button included in the billing message information displayed in the OA talk room. .

If it is determined that an input for setting a payment account has been made (A141: YES), the control unit 21 requests a payment account setting page from the server 60 via the communication I/F 22 (A151).
In response to this (B151: YES), the control unit 61 transmits the payment account setting page of the electronic money application to the terminal 20A via the communication I/F 64 (B153).

Then, the control unit 21 activates the electronic money application, transitions from the messaging application to the electronic money application, and displays the received payment account setting page on the display unit 24 (A153). Then, the control unit 21 advances the processing to A170.

After B160, the control unit 61 generates payment account setting completion information, adds the generated payment account setting completion information to the payment account setting page, and transmits it to the terminal 20A via the communication I/F 64 (B174). In response to this, the control unit 21 causes the display unit 24 to display the payment account setting page of the electronic money application including the payment account setting completion information (A184). Then, the control unit 21 advances the processing to A195.

In the above modification, the server 60 (not limited, but an example of a server) receives billing information (not limited, but an example of purchase information) for credit card payment by the user of the terminal 20 from the credit card company server 10, The received billing information is transmitted to the terminal 20 by communication I/F64. The server 60 then communicates I/ The configuration for receiving from the terminal 20 by F64 is shown.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to receive purchase information of a purchase made by a terminal user with deferred payment, transmit the purchase information to the terminal, and notify the terminal user of the purchase information. can. Also, receiving information from the terminal relating to paying at least a portion of the purchase information by a first account of a plurality of accounts associated with the user of the terminal, thereby setting the account for payment to be the first account, etc. can do.

<First modification (7)>
In the above modification, an example was shown in which the credit card company server 10 and the server 60 are configured as different servers in the communication system 1B, but the present invention is not limited to this.
It is also possible to configure the credit card company server 10 and the server 60 as one server (the same server).

<Second embodiment>
In the first embodiment, each time a user purchases a product or service by credit card payment, that is, each transaction, the user sets up a payment account.
The second embodiment is an embodiment that enables collective payment account setup for one or more transactions.
The content described in the second embodiment can be applied to each of the other embodiments and each of the other modifications.
Moreover, the same code|symbol is attached|subjected about the component same as an already-appearing component, and description for the second time is abbreviate|omitted.

In this embodiment, the control unit 11 performs a process of transmitting "this month's fixed billing information", which is an example of billing information different from the above-described billing information, separately from the above-described billing information transmission process (Fig. 2-2 See below).

"Confirmed billing information for the current month" means, as a non-limiting example, product purchase information for the current month related to credit card payment billing for the current month (as a non-limiting example, payment month information, total payment amount information, purchase date and time for each transaction, transaction (Including information such as separate purchase amount, transaction store, etc.) and information for setting which bank account to transfer each payment amount (by transaction) out of this total payment amount (not limited For example, the information includes link information to the web page of the credit card company, etc. The current month product purchase information includes information about the purchase history of the current month.
"Current month" may be expressed as "this month", "current month", "month to be settled", or may not be expressed.

The information about the purchase history is, for example and not limitation, information having some relationship with the purchase history, such as information on the purchase history itself and information necessary for displaying the purchase history.

<Display screen>
FIG. 2-1 is a diagram showing an example of screen transitions displayed on the display unit 24 of the terminal 20A in this embodiment.
FIG. 2-1 is a diagram showing an example of a display screen when the user collectively sets a payment account for a plurality of credit card transactions for this month (October in this example).

The left side of Figure 2-1 shows, as an example and not a limitation, an e-mail containing payment information for the current month and link information to the web page of the credit card company as confirmed billing information for the current month from the credit card company (X Card). user A. FIG. 10 is a received e-mail screen displayed on the display unit 24 of A's terminal 20A. FIG.

In the text display area of the received e-mail screen, as a non-limiting example, the characters "Usage Information for October" are displayed as the headline of the text.
In addition, below that, the payment information for the current month (October) is displayed. "Total Amount" column is provided. In this example, "2020/10" is displayed in the "usage month" column, and "50,000 yen" is displayed in the "total usage amount" column.

In addition, below that, link information to the web page of the credit card company (as an example, not limited to, the page for setting up the payment account for this month) is displayed, based on the registered URL of the web page of the credit card company. A link button BT4 including the text of "Click here to set up a payment account for this month>" is displayed.
In addition, the same information as the screen on the left side of FIG. 1-10 is displayed.

When the link button BT4 for moving to the credit card company's web page is tapped on the received e-mail screen shown on the left side of FIG. 2-1, the screen moves to the credit card company's web page.

In the center of FIG. 2-1, a display screen of a payment account setting page for the current month among the web pages of a credit card company (hereinafter referred to as a "payment account setting screen for the current month") (as a non-limiting example, An example of the “October payment account setting screen” of the current month payment account setting screen is shown.

In the region of the payment account setting screen for this month, the text "October payment account setting" is displayed in an area indicating that this web page is a page for setting a payment account.

Below that, there is an area for displaying product purchase information for the current month (for example, but not limited to, date and time of purchase, purchase amount, etc.). , "date of use" (in this example, "2020/10/01", "2020/10/15", "2020/10/28") and "usage amount" (in this example, " 25,000 yen", "15,000 yen", and "10,000 yen") and a column of "details" (see FIG. 1-10) are displayed in order of purchase date and time.

In addition, in the first icon display area on the right, in the column of "payment account", a first icon IC1A including the characters "Bank A" corresponding to Bank A and "Bank B" corresponding to Bank B are displayed. A first icon IC1B containing characters is displayed for each credit card transaction.
In addition, the same information as the screen in the center of FIG. 2-1 is displayed.

In the October payment account setting screen shown in the center of Fig. 2-1, the first icon for each credit card transaction (in this example, "first icon IC1A corresponding to bank A", "corresponding to bank B After tapping the first icon IC1B" and "first icon IC1A corresponding to Bank A"), when the second icon IC2 is tapped, as a non-limiting example, as shown on the right side of FIG. 2-1, A screen of a web page of a credit card company notifying that the setting of the payment account for the current month has been completed (hereinafter referred to as the "account setting completion screen for the current month") is displayed.

In the area indicating that the setting of the payment account has been completed on this month's payment account setting screen, the text "The setting of the payment account for October has been completed." is displayed.

In addition, an area for displaying the current month's product purchase information is configured below it, and the same information as the screen in the center of FIG. 2-1 is displayed.
To the right of it, there is an area for displaying the payment accounts that have been set up. In this example, the words "payment account" and ""BankA","BankB" corresponding to Bank B, and "Bank A" corresponding to Bank A are displayed.

<Processing>
2-2 and 2-3 are flowcharts showing an example of the flow of processing executed by each device in this embodiment. FIG. 2-2 is a portion corresponding to FIG. 1-12 in the flowchart described in the first embodiment, and the processing up to C120 is omitted because it is common to FIG. 1-11. .
In this figure, from the left side, the processing executed by the control unit 21 of the terminal 20A, the processing executed by the control unit 11 of the credit card company server 10, the processing executed by the control unit of the A bank server 50A, the B bank server 50B 3 illustrates an example of processing executed by a control unit;

After C140: NO or C170, the control unit 11 determines whether or not the conditions for sending the current month's final billing information are satisfied (C225).
The conditions for sending the confirmed billing information of the current month are the conditions for sending the confirmed billing information of the current month, which will be described later. (a specific time on the next business day)".

If it is determined that the current month's fixed billing information transmission condition is not satisfied (C225: NO), the control section 11 advances the process to C180.

On the other hand, if it is determined that the current month's fixed billing information transmission condition has been satisfied (C225: YES), the control unit 11, as a non-limiting example, provides information regarding the billing of the total settlement amount for the current month (as a non-limiting example, the current month's product (Purchase information, etc.) and information for selecting/setting an account for account transfer for transactions in the current month is transmitted to the terminal 20A via the communication I/F 14 (C230).

When receiving the current month billing information from the credit card company server 10 via the communication I/F 22, the control unit 21 displays the received current month billing information (or information based thereon) on the display unit 24 (A230). Specifically, as a non-limiting example, the display unit 24 is caused to display current month product purchase information (payment month, total payment amount, etc.) and link information to the web page of the credit card company.

After that, the control unit 21 determines whether or not an input for setting a payment account for each transaction has been made via the input unit based on the current month's fixed billing information displayed on the display unit 24 (A240). Specifically, as a non-limiting example, whether or not an operation via an input unit for link information to a web page of a credit card company (a page for setting a payment account for each credit card transaction to be transferred in the current month) has been detected. determine whether
Here, "setting of payment account for each transaction" means setting a payment account for each transaction from a list of transactions (transaction history).

If it is determined that the input for setting the payment account for each transaction has not been made (A240: NO), the control unit 21 advances the processing to A195.
On the other hand, if it is determined that the input for setting the payment account for each transaction has been made (A240: YES), the control unit 21 displays the setting page (web page) for the payment account for each transaction for the current month as an example, not as a limitation. Transaction-specific payment account setting request information for transfer is transmitted to the credit card company server 10 via the communication I/F 22 (A250).

After step C230, the control unit 11 determines whether or not the transaction-specific payment account setting request information has been received (C240).
If it is determined that the transaction-specific payment account setting request information has not been received (C240: NO), the control section 11 advances the process to C180.

On the other hand, when determining that the transaction-specific payment account setting request information has been received (C240: YES), the control unit 11 collects information related to billing of the total settlement amount based on the received transaction-specific payment account setting request information. (As an example, not limitation, product purchase information for the current month, etc.), bank account information linked to the credit card (as an example, not limitation, bank name, account number, etc.), and necessary to set up a payment account Information for setting a payment account for each transaction, including other information (as an example and not limitation, a first icon corresponding to a bank account, a second icon to be saved/determined after selecting the first icon, etc.) It is transmitted to the terminal 20A by F14 (C250).

When the information for setting a payment account for each transaction is received from the credit card company server 10 via the communication I/F 22, the control unit 21 receives the information for setting a payment account for each transaction (or information based on this) (as an example, not a limitation). , current month payment account setting screen) is displayed on the display unit 24 (A260).
As a non-limiting example, purchase information for the current month (purchase date and time, purchase amount, etc.), bank account information linked to the credit card (bank name, account number, etc.), and other information necessary to set up a payment account It is possible to cause the display unit 24 to display a current month payment account setting screen including information such as information (first icon, second icon, etc.).

After that, the control unit 21 receives an input for selecting a payment account for each transaction from the user via the input unit (A270). In this case, as an example and not a limitation, the first icon is user A.A. for each transaction displayed on display unit 24 of terminal 20A. After being manipulated (tapped as an example and not by way of limitation) by user A.A. When operated (tapped as an example, not as a limitation) by A, the control unit 21 transfers the payment account selection information for each transaction including the information of the bank account selected as the payment account for each transaction to the credit through the communication I/F 22. It is transmitted to the card company server 10 (A280).

When receiving the transaction-specific payment account selection information from the terminal 20A through the communication I/F 14, the control unit 11 performs transaction-specific payment account setting processing based on the received transaction-specific payment account selection information (C260). Specifically, as a non-limiting example, each transaction ID included in the payment account setting data among the user management data in which the contractor ID of the target contractor (user AA in this example) is stored For each, the account ID corresponding to the payment account specified from the received transaction-by-transaction payment account selection information is stored in the payment account ID.

After that, the control unit 11 transmits transaction-specific payment account setting completion information to the terminal 20A via the communication I/F 14 (C270) for notifying that the setting of the payment account for each transaction is completed, and sends the process to C180. proceed.

When the payment account setting completion information for each transaction is received from the credit card company server 10 via the communication I/F 22, the control unit 21 receives the payment account setting completion information for each transaction (or information based thereon) (as an example, not limitation). , payment account setting completion screen for the current month) is displayed on the display unit 24 (A290), and the process proceeds to A195.
As a non-limiting example, the display unit displays the payment account setting completion screen for the current month including information such as product purchase information for the current month and payment account information (such as information notifying that one of the bank accounts has been set as the payment account). 24 can be displayed.

<Effect of Second Embodiment>
In this embodiment, the terminal 20 receives product purchase information including information on the purchase history of products or services purchased by deferred payment by the user of its own terminal 20, and the received product purchase information and its own terminal 20 1 shows a configuration for displaying the registered bank account information of the user on the display unit 24. FIG.
As an example of the effect of the embodiment obtained by such a configuration, the terminal user can confirm the purchase history of the product or service purchased by the terminal user with deferred payment, and the payment can be made from any account. The user can select whether

Also, in this case, the terminal 20 receives transaction-specific payment account setup completion information (an example of, but not limited to, information relating to paying at least part of the purchase history based on the first account). can do.
As an example of the effect of the embodiment obtained by such a configuration, the user of the terminal confirms that at least part of the payment in the purchase history is to be paid with the first account related to the first account information, and the payment is made. can be made from the first account.

In addition, in this embodiment, the terminal 20 receives information about the total amount of goods or services purchased by the user of the terminal 20 itself, and the information about the received total amount and the user of the terminal 20 itself and the registered bank account information are displayed on the display unit 24. FIG.
As an example of the effect of the embodiment obtained by such a configuration, the terminal user can confirm the total amount of goods or services purchased by the terminal user with deferred payment, and the payment can be made from any account. The user can select whether

It should be noted that the information related to paying at least part of the payment based on the first account in the purchase history includes, by way of example and not limitation, information indicating that the first account was selected as the payment account, information indicating that the first Information that has some relation to at least part of the payment based on the first account in the purchase history, such as information indicating that the account has been set up as a payment account (the above payment account setting completion information) be.

In addition, information related to the total amount includes, but is not limited to, information that has some relationship with the total amount, such as information on the total amount itself and information for calculating the total amount (purchase amount for each transaction, etc.). is.

<Second modification>
The method of the second embodiment can be similarly applied to various contents described in the first modified example.
By way of example and not limitation, a payment account may be set up by an application such as a messaging application or an electronic money application.

Also, as described in the first modification,
(a) Configuration of electronic money service function as one function of chat application (b) Configuration of chat service function as one function of electronic money application (c) Combination of chat service function and electronic money service function It is also possible to apply a form that constitutes a composite (integrated) application having

<Display screen>
FIG. 2-4 is a diagram showing an example of transition of screens displayed on the display unit 24 of the terminal 20A in this modified example.
The left side of FIG. 2-4 is an example of a chat room screen of a messaging application.
In the talk area of this screen, user A. A's credit card transaction information for the current month ("October usage information" on the screen) is sent to the terminal 20A for the current month via the server 60. Based on the receipt of the confirmed billing message information, the current month's confirmed billing message information is displayed on the left side of the OA talk room screen in association with the icon image of the X card.

This "current month's fixed billing message information" is message information of a messaging application that is transmitted to the terminal 20 by the server 60 that receives the current month's fixed billing information from the credit card company server 10, and corresponds to the current month's fixed billing information. This is message information.

At the bottom of the current month's confirmed billing message information is a button operated to set up a payment account. A link button BT2 is provided that includes the text "Click here for payment account settings for this month" linked to a payment account setting page for each credit card transaction to be transferred.

On this screen, when the link button BT2 containing the text "Click here for payment account settings for this month" is tapped, as a non-limiting example, an electronic money application is activated on the terminal 20, and as a non-limiting example, FIG. 2-4 The center screen is displayed.

This screen is a payment account setting screen for this month (“October payment account setting screen” in this example) in the electronic money application, and displays the characters “Payment App”, which is the name of the electronic money application.
Below that, information similar to the screen in the center of FIG. 2-1 is displayed.

In the current payment account setting screen shown in the center of FIG. 2-4, as an example and not limitation, for each credit card transaction, in order from the top, the first icon IC1A corresponding to Bank A, the first icon corresponding to Bank B After tapping the first icon IC1A corresponding to IC1B and Bank A, when the second button BT3 is tapped, as an example and not as a limitation, the current month payment account setting completion screen shown on the right side of FIG. 2-4 appears. , is displayed in the electronic money application.

This screen is a payment account setting screen for this month (“October payment account setting screen” in this example) in the electronic money application, and displays the characters “Payment App”, which is the name of the electronic money application.
Below that, information similar to the screen on the right side of FIG. 2-1 is displayed.

<Processing>
2-2 to 2-3 are replaced by the processes in FIGS. The detailed description is omitted because the same configuration is possible by rewriting based on such processing.

<Third embodiment>
The third embodiment is an embodiment that enables a payment account to be set up by a method different from the selection of the payment account by the user as a method of setting up the payment account.
The content described in the third embodiment can be applied to each of the other embodiments and modifications.
Moreover, the same code|symbol is attached|subjected about the component same as an already-appearing component, and description for the second time is abbreviate|omitted.

In this embodiment, as an example and not a limitation, as a method of setting up a payment account, out of the amount charged by the credit card company (settlement amount for each product, total settlement amount for the current month, etc.), from one bank account A method of setting a payment account by allowing the user to arbitrarily input and specify the transfer amount for account transfer and the transfer amount for account transfer from another bank account (hereinafter referred to as the "amount input method" as appropriate) ) is applied. Note that this may be called an amount designation method or the like.

<Data structure>
FIG. 3-1 is a diagram showing a data configuration example of a user management database 159C, which is an example of the user management database 159 stored in the storage unit 15 of the credit card company server 10 in this embodiment.

Similar to user management database 159A, each user management data store, by way of example and not limitation, contractor ID, transaction data, registered bank account data, and payment account setup data. However, the data configuration of the payment account setting data is different.
Specifically, in the user management database 159C, the transfer amount and the payment account ID are associated and stored in the payment account setting data, for example and not limitation.

For the corresponding payment account ID, the transfer amount stores the amount specified by the user of this contractor ID as the amount to be transferred from the payment account of this payment account ID.

Among the account IDs stored in the registered bank account data, the payment account ID is set by storing an account ID corresponding to the bank account designated as the account for transferring the transfer amount.

<Display screen>
FIG. 3B is a diagram showing an example of screen transitions displayed on the display unit 24 of the terminal 20A in this embodiment.
FIG. 3-2 is a diagram showing an example of a display screen when the user sets up a payment account using the amount input method.

On the left side of Fig. 3-2, as a display screen (this month's payment account setting screen) of the payment account setting page for the current month (October in this example) of the web page of the credit card company, as an example, not as a limitation, An example of the “October payment account setting screen” is shown.

In the area for displaying the total settlement amount for the current month in the payment account setting screen for the current month, a column of "total amount used" ("50,000 yen" in this example) is displayed.

In addition, in the area for displaying the bank account (payment account) linked to the credit card on the right, the characters "payment account", the characters "A bank" corresponding to A bank, and the B Characters of "B bank" corresponding to the bank are displayed.

In addition, on the right, there is a transfer amount input area for entering the transfer amount for each payment account. "30,000 yen" based on the input of "30,000" in the corresponding transfer amount input area R1A, and the input of "20,000" in the transfer amount input area R1B corresponding to Bank B by the user. "20,000 yen") is displayed.
That is, in this example, the user has selected to transfer "30,000 yen" from the bank account of Bank A and to transfer "20,000 yen" from the bank account of Bank B. showing.
In addition, the same information as the screen in the center of FIG. 2-1 is displayed.

In the October payment account setting screen shown on the left side of Figure 3-2, the transfer amount (in this example, "30,000 yen" corresponding to bank A, bank B) is entered in the transfer amount input area corresponding to each bank's payment account "20,000 yen" corresponding to ) is input, and then the second icon IC2 is tapped. A screen of a page notifying that the setting of the payment account for this month has been completed (this month's payment account setting completion screen) is displayed.

In the area indicating that the setting of the payment account has been completed on this month's payment account setting screen, the text "The setting of the payment account for October has been completed." is displayed.

Below that, an area for displaying payment accounts is configured. In this example, the characters "Payment Account", the characters "A Bank" corresponding to Bank A, and the characters "Bank B" is displayed.

On the right of it, there is an area for displaying the transfer amount for each set payment account. In this example, the characters "transfer amount" and "30, 000 Yen” and “20,000 Yen” as the transfer amount corresponding to Bank B are displayed.

In this example, the display screen/user interface (UI) is used for the user to calculate and input the transfer amount based on the total settlement amount for the current month, but the display screen/user interface (UI) is not limited to this.
Although the details will be described later, it is also possible to provide a display screen/UI in which the transfer amount is set by (A) the transfer amount fixed method, (B) the ratio setting method, or the like.

<Processing>
FIG. 3C is a flow chart showing an example of the flow of processing executed by each device in this embodiment. FIG. 3-3 shows a portion of the flow chart of the second embodiment corresponding to FIG. 2-3.

After A230, the control unit 21 determines whether or not an input for setting a payment account by the amount input method is made via the input unit based on the current month's final billing information displayed on the display unit 24 ( A340).

If it is determined that no input has been made to set a payment account using the amount input method (A340: NO), the control unit 21 advances the process to A195.
On the other hand, if it is determined that an input has been made to set a payment account using the amount input method (A340: YES), the control unit 21, as an example and not as a limitation, displays a payment account setting page (web page) using the amount input method. amount input method payment account setting request information for moving to the credit card company server 10 via the communication I/F 22 (A350).

After step C230, the control unit 11 determines whether or not the amount input method payment account setting request information has been received (C340). When determining that it has not been received (C340: NO), the control unit 11 advances the process to C180.

On the other hand, when determining that the amount input method payment account setting request information has been received (C340: YES), the control unit 11 transmits the amount input method payment account setting information to the terminal 20A through the communication I/F 14 (C350 ).

When the communication I/F 22 receives the amount input method payment account setting information from the credit card company server 10, the control unit 21 receives the amount input method payment account setting information (or information based on this) (not limited to As an example, the current payment account setting screen) is displayed on the display unit 24 (A360).

After that, the control unit 21 receives the input of the transfer amount for each registered bank account by the user through the input unit (A370). Then, the control unit 21 transmits transfer amount input information including the transfer amount input for each registered bank account to the credit card company server 10 via the communication I/F 22 (A380).

When the transfer amount input information is received from the terminal 20A through the communication I/F 14, the control unit 11 performs the amount input method payment account setting process based on the received transfer amount input information (C360). Specifically, as a non-limiting example, from the received transfer amount input information to the payment account setting data of the user management data in which the contractor ID of the target contractor (user AA in this example) is stored The specified transfer amount is associated with the payment account ID and stored.

After that, the control unit 11 transmits to the terminal 20 via the communication I/F 14 information on the completion of the payment account setting by the amount input method for notifying that the setting of the payment account by the amount input method is completed (C370), and C180. proceed to

In this process, in C190, the control unit 11 refers to the payment account setting data included in the user management data, sets the transfer amount stored in association with each payment account ID as the transfer request amount, and determines the transfer request amount. and the account transfer token stored in association with the payment account ID is communicated to the corresponding bank server 50 via the communication I/F 14 with the corresponding partner bank server URI as the access destination. /F14.

When receiving the amount input method payment account setting completion information from the credit card company server 10 via the communication I/F 22, the control unit 21 displays the received amount input method payment account setting completion information (or information based thereon) on the display unit 24. is displayed (A390), and the process proceeds to A195.

<Effect of the third embodiment>
In this embodiment, the terminal 20 receives the transfer amount input (designated) by the user out of the total amount of goods or services purchased by the user of the own terminal 20 by deferred payment (not a limitation, but an example of the first amount). ) based on the first bank account (first account) selected by the user is received and displayed on the display unit 24 . Then, based on the input of the transfer amount by the user of the terminal 20 itself, the terminal 20 provides payment account setting completion information (not limited to, the first bank account) indicating that the first bank account is set as the payment account. An example of information) is shown on the display unit 24. FIG.
As an example of the effect of the embodiment obtained by such a configuration, the first amount out of the total amount of goods or services purchased by the terminal user with deferred payment is stored in the first account information selected by the terminal user. Payment can be made in the associated first account.

Also, in this case, when the user of the terminal 20 selects the second bank account (second account) from among the plurality of registered bank account information, the terminal 20 confirms that the second bank account is the payment account. Payment account setting completion information indicating that the payment account has been set as can be displayed in
As an example of the effect of the embodiment obtained by such a configuration, the second amount of the total amount of goods or services purchased by the terminal user with deferred payment is stored in the second account information selected by the terminal user. Payment can be made in the associated secondary account.

<Third modification>
The method of the third embodiment can be similarly applied to various contents described in the first modified example.
By way of example and not limitation, an application, such as a messaging application or an electronic money application, may allow the payment account to be set up in a money entry manner.

Also, as described in the first modification,
(a) Configuration of electronic money service function as one function of chat application (b) Configuration of chat service function as one function of electronic money application (c) Combination of chat service function and electronic money service function It is also possible to apply a form that constitutes a composite (integrated) application having

<Processing>
The processing in this modified example is based on the processing of FIGS. The detailed description is omitted because the same configuration can be achieved by rewriting with .

<Fourth embodiment>
In credit card payments, due to the fact that the date of account transfer is fixed, the period during which a payment account can be set up is limited. However, there is a possibility that the user may forget the time limit in credit card settlement, in which a certain period of time elapses from the time a product or service is purchased using credit card settlement until the account transfer is actually performed.
The fourth embodiment is an embodiment in which the user is notified of information (including information such as period, deadline, due date, etc.) regarding the time or date on which the user can select a payment account.
The content described in the fourth embodiment can be applied to each of the other embodiments and each of the other modifications.
Moreover, the same code|symbol is attached|subjected about the component same as an already-appearing component, and description for the second time is abbreviate|omitted.

In this embodiment, as a non-limiting example, the payment account is set at a date and time prior to the date of transfer from the payment account in credit card payment (hereinafter referred to as "transfer date" and "withdrawal date" as appropriate). A deadline (hereinafter referred to as a “payment account setting deadline” as appropriate) is set. The period up to the deadline for setting up a payment account is defined as a period in which a payment account can be set up (hereinafter referred to as a "payment account setting up period" as appropriate).

The payment account establishment deadline expressed in days is appropriately referred to as the “payment account establishment deadline”. By way of example and not limitation, if the 25th of each month is the transfer date and three days before that is set as the payment account establishment deadline date, the 22nd of each month will be the payment account establishment deadline.
The payment account setting deadline may or may not be set as "date and time".

In this embodiment, the information for notifying the user of the payment account setting deadline is referred to as "deadline notification information".
The "deadline notification information" may be any information that has some relationship with the payment account establishment deadline, and includes at least one of the following information as an example and not as a limitation.
・Information that directly notifies the deadline for setting up a payment account (as an example, not as a limitation, “payment account setup deadline information” described later)
・Information indirectly notifying the payment account setting deadline (as an example, not as a limitation, “payment account setting remaining period information” described later)

"Payment account setting deadline information" is information that notifies the payment account setting deadline itself. Information such as characters is included.

"Payment account setting remaining period information" is information for notifying the remaining period until the payment account setting deadline, and includes, as a non-limiting example, the remaining time itself until the payment account setting deadline.

The remaining payment account setting period information includes, as an example, not limitation, information that suggests the remaining period (remaining time) until the payment account setting deadline by an image or the like (hereinafter referred to as "payment account setting remaining period indication information"). .) can be included.

The payment account setup remaining period suggestion information is displayed on the terminal 20 in different display modes as follows, as an example, not limitation, based on the remaining period (remaining time) until the payment account setup deadline (remaining time). It can be made to display on the display part 24. FIG.
・When the remaining period (remaining time) until the payment account setting deadline is longer than a predetermined period (predetermined time) (as an example, not as a limitation, when it is one week or more): First display mode (as an example, not as a limitation, a round shape icon, display a blue frame around the first icon, etc.)
・When the remaining period (remaining time) until the payment account setting deadline is not longer than a predetermined period (predetermined time) (not limited, but within one week as an example): Second display mode (not limited as an example, triangular type icon, display a yellow frame around the first icon, etc.)

In this embodiment, the timing at which the deadline notification information is displayed includes at least one of the following timings as an example and not as a limitation.
・The timing at which the billing information or the billing information confirmed for the current month is displayed on the terminal 20 (as an example, not a limitation, the timing at which the received e-mail screen related to the billing information or the billing information confirmed for the current month is displayed)
・The timing when the payment account setting information and the payment account setting information for each transaction are displayed on the terminal 20 (as an example, not as a limitation, the timing when the payment account setting screen and the current payment account setting screen are displayed)
In the following, a case is exemplified in which the timing at which the time limit notification information is displayed is the timing at which the current month's payment account setting screen is displayed on the terminal 20 .

In addition, in this embodiment, as an example and not a limitation, information for notifying (suggesting) that the payment account setting deadline has passed will be referred to as “time limit notification information”. This deadline notification information is information that has some relationship with the deadline for setting up a payment account, and is information that notifies (suggests) that the deadline for setting up a payment account has been exceeded. or one information is included in this.
・Information notifying that the deadline for setting up a payment account has been exceeded (as an example, not as a limitation, “information on expiration of deadline for payment account” described later)
・Information notifying that there is no remaining period (exceeded) until the deadline for setting up a payment account (as an example, not as a limitation, "information on exceeding the remaining period for setting up a payment account", which will be described later)

"Payment account setting deadline exceeded information" is information that directly notifies that the payment account setting deadline has passed. : X month and Y day have passed." are included.

The “payment account setting remaining period over information” is information for notifying that there is no remaining period until the payment account setting deadline due to exceeding the deadline (expired).
The payment account setting remaining period expiration information includes, as a non-limiting example, information suggesting by an image or the like that there is no remaining payment account setting period (hereinafter referred to as "payment account setting remaining period expiration information"). can be included.

The payment account setup remaining period expiration indication information can be displayed on the display unit 24 of the terminal 20 in the following display mode as an example and not as a limitation.
・When there is no remaining period until the payment account setting deadline: 3rd display mode (as an example, not a limitation, a cross-shaped (x) icon is displayed, a red frame is displayed around the 1st icon, etc.)

In this embodiment, the payment account information includes, by way of example and not limitation, payment account information including deadline notification information and payment account information including overdue notification information.
Specifically, the payment account setting information including deadline notification information is, as an example, not a limitation, a payment account setting screen that includes the characters "can be set up to X month Y day", and the overdue notification information is displayed. The included payment account setting information is, for example and not limitation, a payment account setting screen that includes the characters “Set period ends on X month Y day”.

In addition, in this embodiment, the information for setting a payment account for each transaction includes, as an example, without limitation, information for setting a payment account for each transaction including deadline notification information, and information for setting a payment account for each transaction including expiration notification information. and are included.
Specifically, the transaction-by-transaction payment account setting information including the deadline notification information is, for example, not limitation, a payment account setting screen for the current month containing the characters "can be set up to X month Y day", and the deadline The payment account setting information including the excess notification information is, for example and not limitation, a payment account setting screen for the current month including characters of "the set period will end in X month and Y day".

<Data structure>
FIG. 4A is a diagram showing a data configuration example of information type determination data for setting a payment account stored in the storage unit 15 of the credit card company server 10 in this embodiment.
For the payment account setting information type determination data, as an example, not limitation, the determination result of whether the current timing information (current date and time) is within the payment account setting deadline, the payment account setting information type, and are stored in association with each other.

The control unit 11 of the credit card company server 10 can determine whether the current time information is within the payment account setting deadline based on the time information output from the clock unit 19 . If the current timing information is within the payment account establishment deadline, the determination result is "YES", and if the current timing information is not within the payment account establishment deadline, the determination result is "NO".

The type of payment account setting information is the type of payment account setting information, and as an example, not limitation, payment account setting information including deadline notification information and payment account setting information including overdue notification information. Included in this. In this data, if the determination result is "YES", the type of the payment account setting information is the payment account setting information including the deadline notification information, and if the determination result is "NO", the payment account setting information is determined to be payment account setting information including overdue notification information.

FIG. 4B is a diagram showing a data configuration example of information type determination data for setting a payment account for each transaction stored in the storage unit 15 of the credit card company server 10 in this embodiment.
In the payment account setting information type determination data for each transaction, as a non-limiting example, the judgment result of whether or not the current timing information is within the payment account setting deadline and the type of the information for setting payment account for each transaction are included. stored in association with each other.

The type of information for setting a payment account for each transaction is the type of information for setting a payment account for each transaction, and as an example, not a limitation, the information for setting a payment account for each transaction including deadline notification information and the transaction including overdue notification information This includes information for setting up another payment account. In this data, if the determination result is "YES", the type of information for setting a payment account for each transaction is the information for setting a payment account for each transaction that includes deadline notification information, and if the result is "NO" for payment The type of information for account setting is determined to be information for setting a payment account for each transaction, including expiration notification information.

<Display screen>
FIG. 4-3 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20A in this embodiment. FIG. 4-3 is a diagram showing an example of a display screen when payment account setting deadline information is displayed.

Fig. 4-3 shows a display screen of the setting page of the payment account for this month on the web page of the credit card company (this month's payment account setting screen) (as a non-limiting example, " 10 shows an example of “October payment account setting screen”).

This month's payment account setting screen includes a payment account setting deadline information area R2 for displaying payment account setting deadline information. "possible" is displayed.
In addition, the same information as the screen in the center of FIG. 2-1 is displayed.

FIG. 4-4 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20A in this embodiment. FIG. 4-4 is a diagram showing an example of a display screen when the payment account setting time limit information is displayed.

Fig. 4-4 shows a display screen of the setting page of the payment account for this month on the web page of the credit card company (this month's payment account setting screen) (as a non-limiting example, " 10 shows an example of “October payment account setting screen”).

This month's payment account setting screen includes a payment account setting overdue information display area R3 for displaying payment account setting overdue information. The text "The set period will end in 22 days" is displayed.
In addition, the same information as the screen in the center of FIG. 2-1 is displayed.

<Processing>
The process of the present embodiment can be configured based on FIGS. 1-11, 2-2, and 2-3 by way of example and not limitation.
Note that steps other than C150 and A160, and C250 and A260 are the same as in FIGS.

If C140 determines YES, the control unit 11 determines the type of payment account setting information to be transmitted to the terminal 20A based on the payment account setting information type determination data (see FIG. 4-1). Then, the control unit 11 transmits the determined type of payment account setting information to the terminal 20A through the communication I/F 14 (C150).

When any type of payment account setting information is received from the credit card company server 10 by the communication I/F 22, the control unit 21 receives the received type of payment account setting information (or information based on this) (in limitation, As an example, a payment account setting screen including time limit notification information or time limit overtime notification information) is displayed on the display unit 24 (A160).

Similarly, if C240 determines YES, the control unit 11 transmits the transaction-specific payment account setting information to the terminal 20A based on the transaction-specific payment account setting information type determination data (see FIG. 4-2). determine the type of Then, the control unit 11 transmits the transaction-specific payment account setting information of the determined type to the terminal 20A via the communication I/F 14 .

When receiving any type of payment account setting information for each transaction from the credit card company server 10 via the communication I/F 22, the control unit 21 receives the received type of payment account setting information for each transaction (or information based on this ) (this month's payment account setting screen including deadline notification information or expiration notification information as an example, not limitation) is displayed on the display unit 24 (A260).

<Effects of the fourth embodiment>
In this embodiment, the terminal 20 selects account information as a payment account from among a plurality of registered bank account information for one of the billing information (not a limitation, but an example of the first purchase information). Shows a configuration for displaying on the display unit 24 information about the time or date that the user can select (not limited, but an example of third information about being able to select at least one account information from among a plurality of account information) ing.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to select at least one account information from a plurality of account information for the first purchase information of the purchase information, The user of the terminal can be notified of information such as the time and date on which the can be selected.

Also, in this case, the above third information may include time limit notification information (not limited, but an example of information regarding a date on which at least one account information can be selected from a plurality of account information). .
As an example of the effect of the embodiment obtained by such a configuration, it is possible to notify the user of the terminal of information regarding the date on which at least one account information can be selected from a plurality of account information.

Also, in this case, the information (third information) regarding the timing or date when the user can select a payment account is the case where there is no remaining period until the payment account setting deadline, and the case where there is a remaining period until the payment account setting deadline. It can be displayed on the display unit 24 of the terminal 20 in different display modes.
As an example of the effect of the embodiment obtained by such a configuration, when it is not possible to select at least one account information from among a plurality of account information, the user of the terminal can be made to surely recognize it. can be done.

<Fourth modification>
The method of the fourth embodiment can be similarly applied to various contents described in the first modified example.
By way of example and not limitation, an application, such as a messaging application or an electronic money application, may notify the user of information such as a deadline for setting up a payment account.

Also, as described in the first modification,
(a) Configuration of electronic money service function as one function of chat application (b) Configuration of chat service function as one function of electronic money application (c) Combination of chat service function and electronic money service function It is also possible to apply a form that constitutes a composite (integrated) application having

<Processing>
Because the processing in this modified example can be configured similarly based on the processing of FIGS. , detailed description is omitted.

<Fifth embodiment>
In the above embodiment, billing information for each transaction based on credit card settlement, billing information confirmed for the current month for a month, and the like are transmitted from the credit card company server 10 to the terminal 20. FIG.
The fifth embodiment is an embodiment that allows payment account setup reminder information different from billing information and current month billing information to be sent from the credit card company server 10 to the terminal 20 .
The content described in the fifth embodiment can be applied to each of the other embodiments and other modifications.
Moreover, the same code|symbol is attached|subjected about the component same as an already-appearing component, and description for the second time is abbreviate|omitted.

In this embodiment, reminding or reconfirming the setting or changing of the payment account to the user is referred to as "payment account setting reminder", and information related to this payment account setting reminder is referred to as "payment account setting reminder information". called. This payment account setup reminder information can include various information used to set up a payment account (for example, without limitation, link information to the payment account setup page described above, etc.).

In addition, bank account information linked to the credit card (as a non-limiting example, bank name, account number, etc.), information related to billing for the settlement amount temporarily paid by the credit card company server 10 to the store terminal 40 (as non-limiting examples, product purchase information, receipt information, etc.), product purchase information for the current month related to credit card payment requests for the current month (as non-limiting examples, payment month information, total payment amount information, date and time of purchase by transaction, (including information such as purchase amount for each transaction, store for each transaction, etc.) may or may not be included in the payment account setup reminder information.

In this embodiment, a case where the credit card company server 10 performs a process of determining whether or not to perform a payment account setting reminder (hereinafter referred to as "payment account setting reminder determination process") will be exemplified.
Specifically, in this embodiment, the control unit 11 of the credit card company server 10 acquires various types of information stored in the storage unit 15, and based on the acquired information, sets a payment account setting reminder condition, which will be described later. Determine success or failure. Then, when the payment account setting reminder condition is satisfied, it is determined to transmit the payment account setting reminder information, and when the payment account setting reminder condition is not satisfied, it is determined not to transmit the payment account setting reminder information.

<Data structure>
FIG. 5-1 is a diagram showing a data configuration example of payment account setting reminder condition data stored in the storage unit 15 of the credit card company server 10 in this embodiment.
In the payment account setting reminder condition data, for example and not limitation, the payment account setting reminder condition number (No) and the payment account setting reminder condition corresponding to this number are stored in association with each other.

Note that this data is merely an example and is not limited to this.
It is not necessary to associate and store all of the above information, and some of the information may not be stored.
Further, determination of success or failure of payment account setting reminder conditions may be realized by a program rather than by referring to the above data.
This also applies to data described in other embodiments.

Each payment account setup reminder condition and its determination method will be described in detail below.

<No “SP01”>
In No "SP01", "a set time interval has elapsed or a set date and time has come" is defined as a reminder condition for setting a payment account.
The “set time interval” is not limited to, but can be set to an arbitrary time interval in advance on the terminal 20 side or the credit card company server 10 side.
By way of example and not limitation, a condition can be set such that the reminder is performed at a timing such as "every Sunday morning at 10:00". This is because Sunday, which is the weekend, may be relatively free.

In addition, as a non-limiting example, you can set a condition such that the reminder is performed at "10:00 am on the third day of every month (a specific time three days after the closing date for credit card payments)". may or may not.

As a non-limiting example of determination of the payment account setting reminder condition, the credit card company server 10 determines whether or not the condition is established based on the clock information output from the clock unit 19. can be done.

<No “SP02”>
In No "SP02", "the set time has passed while the payment account has not been set or changed" is defined as the payment account setting reminder condition.
As for the "set time", for example and not limitation, an arbitrary set time can be set in advance on the terminal 20 side or the credit card company server 10 side.

"Payment account not set or changed" includes "payment account not set" and "payment account not changed".

"A state in which a payment account has not been set up" is a state in which a payment account has never been set up after credit card settlement.
As a non-limiting example, after selecting the first icon of the payment account setting screen or the current payment account setting screen, the second icon for saving/determining the information is not operated, or the user is in the terminal 20 This includes the state in which the billing information displayed in , or the billing information confirmed for the current month has not been viewed.

Also, "a state in which the payment account has not been changed" is a state in which the payment account has not been changed even once after the payment account was set.
As an example and not a limitation, if a configuration is adopted in which the payment account for credit card settlement is initialized to one bank account (as an example, not a limitation, the bank account of Bank A) (initialization in this case The bank account is hereinafter referred to as the "initial payment account" as appropriate.), the payment account for any credit card payment has not been changed as the initial payment account, or the payment account for credit card payment is any bank account (this method is hereinafter referred to as the "payment account automatic setting method"), any credit card payment will remain the payment account set by the payment account automatic setting method. This includes unmodified states, etc.

As a non-limiting example, "Set time after the current month's fixed billing information is sent while the second icon is not operated (as a non-limiting example, the number of days until the due date for setting the payment account is 1 day. A condition such as "the number of days has passed" can be set. This means that the user may forget to set up a payment account even though the due date for setting up a payment account is approaching, so a reminder to set up a payment account is given.

In the determination of the payment account setting reminder condition, as a non-limiting example, the credit card company server 10 receives the payment account setting selection sent from the control unit 21 based on the user's input to the second icon. Information about the receipt of information and payment account setting selection information for each transaction (as an example, not limitation, information such as the reception history) and clock information (timekeeping information) output from the clock unit 19, Based on these pieces of information, it is possible to determine whether the conditions are met.

<No “SP03”>
In No "SP03", "the number of transactions for credit card settlement exceeds the set number" is defined as a reminder condition for setting a payment account.
The "set number" can be set to an arbitrary number in advance on the terminal 20 side or the credit card company server 10 side, for example and not limitation.
As a non-limiting example, if the number of transactions is a relatively large number ("20" or "30" as an example, not a limitation), credit card payments that do not have a payment account will accumulate, and later This may become a burden on the user. Therefore, a payment account setting reminder can be performed.

As a non-limiting example of determination of this payment account setting reminder condition, the credit card company server 10 calculates the number of transactions based on the transaction data included in the user management data, and the calculated number of transactions exceeds the set number. It can be realized by determining whether or not there is

<No “SP04”>
No "SP04" defines "the settlement amount exceeds the set amount" as a reminder condition for setting a payment account.
For the "set amount", for example and not limitation, an arbitrary amount can be set in advance on the terminal 20 side or the credit card company server 10 side.

The "settlement amount" in this condition can be the total settlement amount for the current month as an example and not as a limitation.
In addition, unlike this, the "settlement amount" in this condition may or may not be the settlement amount for each credit card settlement (each transaction).

As a non-limiting example, if the settlement amount is a relatively large amount (eg, "50,000 yen" or "100,000 yen", etc.), the user wishes to carefully determine the bank account to which the withdrawal is requested. Such cases are assumed. Therefore, a payment account setting reminder can be performed.

As a non-limiting example of determination of this payment account setting reminder condition, the credit card company server 10 calculates the settlement amount based on the transaction data included in the user management data, and the calculated settlement amount exceeds the set amount. It can be realized by determining whether or not there is

<Processing>
FIG. 5B is a flow chart showing an example of the flow of processing executed by each device in this embodiment.
Since the processing up to A290 and C270 shown in FIGS. 1-11, 2-2, and 2-3 is the same as the processing after A195 and C180, illustrations and explanations are omitted.

After C270 in FIG. 2-3, the control unit 11 executes payment account setting reminder condition determination processing (C510).
In this payment account setting reminder condition determination process, the control unit 11 determines whether or not the payment account setting reminder condition is satisfied based on the above-described payment account setting reminder condition data.

When determining that the payment account setting reminder condition is not satisfied (C520: NO), the control unit 11 advances the process to C180 in FIG. 2-3.
On the other hand, if it is determined that the payment account setting reminder condition is satisfied (C520: YES), the control unit 11, as an example and not as a limitation, sends the payment account setting reminder information related to the payment account setting reminder to the communication I/ It is transmitted to the terminal 20 by F14 (C530), and the process proceeds to C180 in FIG. 2-3.

As an example, not limitation, after A290 in FIG. 2-3, the control unit 21 determines whether or not payment account setting reminder information has been received from the credit card company server 10 via the communication I/F 22 (A530).

If it is determined that the payment account setting reminder information has not been received (A530: NO), the control section 21 advances the processing to A195 in FIG. 2-3.
On the other hand, if it is determined that payment account setting reminder information has been received (A530: YES), the control unit 21 receives the payment account setting reminder information (or information based thereon) (for example, not limitation, payment account setting reminder information). reminder screen) is displayed on the display unit 24 (A540), and the process proceeds to A195 in FIG. 2-3.

<Effect of the fifth embodiment>
In this embodiment, the terminal 20 may receive payment account setup reminder information (at least one of the purchase information, without limitation) based on at least one of the billing information (an example, without limitation, of at least a portion of the purchase information). (example of notification information based on unit) is received by the communication I/F 22, and the configuration for displaying the payment account setting information on the display unit 24 is shown.
As an example of the effect of the embodiment obtained by such a configuration, based on the communication unit receiving notification information based on at least part of the purchase information, a plurality of account information is displayed on the display unit, User can confirm.

Also, in this case, the payment account setting reminder information can be transmitted to the terminal 20 at set time intervals.
As an example of the effect of the embodiment obtained by such a configuration, since notification information based on at least part of the purchase information is transmitted to the terminal at set time intervals, it is possible to periodically check a plurality of account information with the user. It is possible to

Also, in this case, the payment account setting reminder information is for at least one of the billing information (not limited, but an example of at least a part of the purchase information), and the deadline for deferred payment (not limited, but multiple At least one of the account information can be transmitted to the terminal 20 based on a selectable period or date).
As an example of the effect of the embodiment obtained by such a configuration, for at least part of the purchase information, an appropriate Notification information can be sent to the terminal at the appropriate timing.

Also, in this case, the payment account setting reminder information can be sent to the terminal 20 based on the number of deferred payment transactions (not a limitation, but an example of the number of payments included in the purchase information).
As an example of the effect of the embodiment obtained by such a configuration, notification information can be transmitted to the terminal at appropriate timing based on the number of payments included in the purchase information.

In this case, the payment account setting reminder information indicates that the total payment amount for the current month (not limited, but an example of the total amount based on the purchase information) is greater than the set amount (not limited, but an example of the set amount) If so, it can be transmitted to the terminal 20 .
As an example of the effect of the embodiment obtained by such a configuration, notification information can be transmitted to the terminal when the total amount based on the purchase information is somewhat large.

<Fifth Modification>
The method of the fifth embodiment can be similarly applied to various contents described in the first modified example.
By way of example and not limitation, an application, such as a messaging application or an electronic money application, may provide a reminder to set up a payment account.

Also, as described in the first modification,
(a) Configuration of electronic money service function as one function of chat application (b) Configuration of chat service function as one function of electronic money application (c) Combination of chat service function and electronic money service function It is also possible to apply a form that constitutes a composite (integrated) application having

<Processing>
The processing in this modified example applies the processing in FIG. 5-2 to the processing in FIGS. 1-24 to 1-25, 1-28, 1-30, 1-32, etc. A detailed description is omitted because the same configuration can be achieved by doing so.

<Sixth embodiment>
The sixth embodiment is an embodiment in which the user can select the payment method to the credit card company in credit card settlement.
The content described in the sixth embodiment can be applied to each of the other embodiments and each of the other modifications.
Moreover, the same code|symbol is attached|subjected about the component same as an already-appearing component, and description for the second time is abbreviate|omitted.

In the above-described embodiment, the first icon display area of the payment account setting screen and the payment account setting screen for each transaction displays the first icon for selecting a payment account as an example of image information (as a non-limiting example, bank A and a first icon containing characters of "Bank B" corresponding to Bank B) are displayed.
In this embodiment, a third icon is displayed as another example of image information.

The "third icon" is an icon displayed in the first icon display area of the payment account setting screen and the payment account setting screen for each transaction, and is used to select and set the payment method to the credit card company in credit card payments. It is an icon for "Method of payment to a credit card company for credit card transactions" can include, by way of example and not limitation, at least any of the following:
(A) Installment payment (B) Revolving payment (C) Loan payment

(A) “Payment in installments” is a type of payment method in which the amount billed by the credit card company is not paid in one lump sum (one time), but in multiple payments (designated).
In the installment payment for credit card settlement in this embodiment, the split amount obtained by dividing the amount charged by the credit card company by the number of splits specified by the user is paid on a set day such as once a month or on a set date. Make payments from your linked bank account.

(B) "Revolving payment" is a type of payment method in which the amount billed by the credit card company is not paid in one lump sum (one time), but by specifying a fixed monthly payment amount and paying in multiple installments. is.
In the revolving payment of credit card settlement in this embodiment, the monthly payment amount specified by the user out of the billed amount from the credit card company is linked to a set date such as once a month or a set date. Make a payment from your bank account.

(C) "Loan payment" refers to the loan company (as a non-limiting example, a loan company related to a credit card company, credit A type of method in which a loan company (not affiliated with a card company, etc.) makes the payment, and the user later pays the loan company.
The loan payment in this embodiment is linked to the loan payment amount, which is paid by the loan company instead of the billed amount from the credit card company, to the loan company on a set date such as once a month or a set date. Make a payment from your bank account.

In this example, a "third icon" can include, by way of example and not limitation, at least any of the following.
(A) Third icon corresponding to installment payment (as a non-limiting example, a third icon containing the words “installment payment”)
(B) Third icon corresponding to revolving payment (as a non-limiting example, a third icon containing the words “revolving payment”)
(C) Third icon corresponding to loan payment (as an example, not limitation, a third icon containing the word "loan")

<Display screen>
FIG. 6-1 is a diagram showing an example of screen transitions displayed on the display unit 24 of the terminal 20A in this embodiment.
FIG. 6-1 is a diagram showing an example of the display screen when the third icon is displayed on the payment account setting screen.

FIG. 6A shows an example of a display screen (payment account setting screen) of a payment account setting page of a web page of a credit card company.

The payment account setting screen has an icon display area for displaying the first icon and the third icon. , a first icon IC1B containing the characters "Bank B" corresponding to Bank B, and a third icon IC3 containing the characters "revolving payment" corresponding to revolving payment are displayed. It is
In addition, the same information as the screen in the center of FIG. 1-10 is displayed.

In the payment account setting screen shown on the left side of FIG. 6-1, when the third icon IC3 corresponding to revolving payment is tapped and then the second icon IC2 is tapped, as an example and not as a limitation, the center of FIG. 6-1 (hereinafter referred to as "revolving payment payment account setting screen") corresponding to the payment method selected with the third icon IC3 is displayed.

The revolving payment payment account setting screen has an area for displaying information about which payment method this payment account setting screen supports, and in this example, the characters "revolving payment" are displayed. It is
In addition, the same information as the screen in the center of FIG. 1-10 is displayed.

In the revolving payment payment account setting screen shown in the center of FIG. As an example, as shown in the right of Fig. 6-1, the screen of the page notifying that the setting of the payment account for revolving payment has been completed among the web pages of the credit card company (hereinafter referred to as "revolving payment payment account setting completion screen") ) is displayed.

This screen consists of an area indicating that the revolving payment account has been set up. In this example, the text "The revolving payment account has been set up." is displayed. .
In addition, the same information as the screen on the right side of FIG. 1-10 is displayed.

<Processing>
The processing in this embodiment can be configured similarly according to the flow charts shown in FIGS. 1-11, 2-2, and 2-3.
The processes other than C150 and A160, C250 and A260 in the flow charts shown in FIGS. 1-11, 2-2, and 2-3 are the same, so description thereof will be omitted.

If C140 in FIG. 2-2 is determined to be YES, the control unit 11, based on the received payment account setting request information, collects information related to billing of the settlement amount (for example, but not limited to, product purchase information, Receipt information, etc.), bank account information linked to the credit card (examples, but not limitation, bank name, account number, etc.), and other information necessary to set up a payment account (examples, not limitation) , a first icon corresponding to a bank account, a second icon to be saved/determined after selecting the first icon, etc.) and information for setting the payment method (as a non-limiting example, a second icon corresponding to each payment method) 3 icon, etc.) and information for setting a payment account including the above are transmitted to the terminal 20A via the communication I/F 14 (C150).

When the payment account setting information is received from the credit card company server 10 via the communication I/F 22, the control unit 21 receives the received payment account setting information (or information based thereon) (for example, not limitation, payment account setting screen) is displayed on the display unit 24 (A160).
As a non-limiting example, product purchase information (payment date and time, payment store, payment amount, etc.), bank account information linked to credit cards (bank name, account number, etc.), necessary for setting up a payment account A payment account setting screen including other information (first icon, second icon, etc.) and information for setting a payment method (third icon, etc.) can be displayed on the display unit 24. .

If C240 in FIG. 2-3 is determined to be YES, the control unit 11, based on the received transaction-specific payment account setting request information, collects information related to billing of the total settlement amount (as an example, not a limitation). , product purchase information for the current month, etc.), bank account information linked to the credit card (as a non-limiting example, bank name, account number, etc.), and other information necessary to set up a payment account (not limited to As an example, a first icon corresponding to a bank account, a second icon that is saved/determined after selecting the first icon, etc.) and information for setting the payment method (as an example, not a limitation, for each payment method (corresponding third icon, etc.) and information for setting a payment account for each transaction is transmitted to the terminal 20A via the communication I/F 14 (C250).

When the information for setting a payment account for each transaction is received from the credit card company server 10 via the communication I/F 22, the control unit 21 receives the information for setting a payment account for each transaction (or information based on this) (as an example, not a limitation). , current month payment account setting screen) is displayed on the display unit 24 (A260).
As a non-limiting example, purchase information for the current month (purchase date and time, purchase amount, etc.), bank account information linked to the credit card (bank name, account number, etc.), and other information necessary to set up a payment account It is possible to display on the display unit 24 a current payment account setting screen including information (first icon, second icon, etc.) and information for setting a payment method (third icon, etc.). .

The above settings for (A) installment payment, (B) revolving payment, (C) loan payment, etc. are performed based on the billing information sent to the terminal 20 for each transaction (performed from the individual purchase information screen). Alternatively, it may be performed based on the current month fixed billing information transmitted to the terminal 20 (performed from the purchase information history screen).

<Effects of the sixth embodiment>
In this embodiment, the terminal 20 displays information for selecting and setting loan payment (an example of the fourth information regarding paying with a loan, not limitation) on the display unit 24 for the payment of at least one transaction. The configuration to be displayed is shown.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to inform the user of the terminal that payment with a loan is possible for at least part of the payment of the purchase information by deferred payment.

Also, in this case, the loan payment can be made through a bank account selected by the user of the terminal 20 as the payment account (one example of the first account, not a limitation).
As an example of the effect of the embodiment obtained by such a configuration, the first account selected by the user of the terminal can be used for payment by loan.

It should be noted that the fourth information regarding the payment with a loan is, for example and not limitation, information for notifying the user that the payment can be made with a loan, information for the user to apply for a loan, or other information that is similar to the loan payment. It is related information.

<Sixth modification>
The method of the sixth embodiment can be similarly applied to various contents described in the first modified example.
By way of example and not limitation, an application such as a messaging application or an electronic money application may set up a payment method to a credit card company.

Also, as described in the first modification,
(a) Configuration of electronic money service function as one function of chat application (b) Configuration of chat service function as one function of electronic money application (c) Combination of chat service function and electronic money service function It is also possible to apply a form that constitutes a composite (integrated) application having

<Processing>
Because the processing in this modified example can be configured similarly based on the processing of FIGS. , detailed description is omitted.

<Seventh embodiment>
In the above embodiment, the payment account setting screen and the payment account setting screen for each transaction display information such as the bank name and account number as the bank account information linked to the credit card.
In the seventh embodiment, information different from the bank name and account number (as an example, but not limited to, a bank account In this example, balance information related to the balance) is displayed.
The content described in the seventh embodiment can be applied to each of the other embodiments and each of the other modifications.
Moreover, the same code|symbol is attached|subjected about the component same as an already-appearing component, and description for the second time is abbreviate|omitted.

In this embodiment, as information different from the bank name and account number in the bank account information, the balance of the bank account of the user (depositor) (hereinafter referred to as "balance", "bank account balance", etc. as appropriate). Related information (hereinafter referred to as "balance information" as appropriate) is included.

<Data structure>
FIG. 7-1 is a diagram showing a data configuration example of a user management database 159H, which is an example of the user management database 159 stored in the storage unit 15 of the credit card company server 10 in this embodiment.

Similar to user management database 159A, each user management data store, by way of example and not limitation, contractor ID, transaction data, registered bank account data, and payment account setup data. However, the data configuration of the registered bank account data is different.
Specifically, in the user management database 159H, the payment account setting data includes, for example and not limitation, an account ID, an account transfer token, and a balance inquiry token in association with each other.

The balance inquiry token is authentication information issued by the bank server 50 of the affiliated bank that manages the bank account of this account ID.
The credit card company server 10 acquires information on the account balance of the user of this contractor ID based on the balance inquiry token issued in advance by the bank server 50 and notified from the bank server 50 and the above-mentioned account transfer token. The processing to be performed is performed with the bank server 50 .
Note that the balance inquiry token may be expressed as an access token or the like.

In addition, it is not limited to the configuration in which two or more tokens (in this example, one account transfer token and one balance inquiry token) are associated with one account ID, and one account token is associated with one account ID. (generic token) may or may not be associated.

In this embodiment, the credit card company server 10 acquires balance information from the bank server 50, and the acquired balance information is stored in the user management data in association with the account ID. The stored balance information is updated to the latest information each time the balance information is acquired.
The stored balance information may or may not be erased at the timing of the account transfer for the month.

<Display screen>
FIG. 7B is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20A in this embodiment. FIG. 7-2 is a diagram showing an example of a display screen when balance information is displayed on the payment account setting screen.

FIG. 7B shows an example of a display screen (payment account setting screen) of a payment account setting page of a web page of a credit card company.

A bank account information display area is configured to display bank account information linked to a credit card (for example, but not limited to, bank name, account number, balance, etc.).In this example, it corresponds to Bank A. The characters "A bank" are displayed as the name of the bank to which the account is to be transferred, the numbers "XXXXXXX" as the account number, and the numbers "YYYYYY Yen" as the balance. Also, the characters "B bank" are displayed as the bank name corresponding to "B bank", the numbers "XXXXXXX" as the account number, and the numbers "YYYYYY Yen" as the balance.
In addition, the same information as the screen in the center of FIG. 1-10 is displayed.

<Processing>
FIG. 7-3 is a flow chart showing an example of the flow of processing executed by each device in this embodiment.
Since the processing up to A150 and C140 shown in FIGS. 1-11 and 1-12 is the same as the processing after A170, C160, D190, and E190, illustrations and explanations are omitted.

After C140 in FIG. 1-12 determines YES, authentication system authorization processing is performed between the credit card company server 10 and the bank server 50. FIG.
Specifically, as a non-limiting example, the control unit 11 selects the account from the registered bank account data in the user management data in which the transaction ID included in the payment account setting request information is stored in the user management database 159H. Get the account transfer token and balance inquiry token associated with the ID.
The control unit 11 also acquires the affiliated bank server URI associated with the account ID (affiliated bank ID) included in the user management data from the affiliated bank data 155 . Then, the control unit 11 transmits balance inquiry request information (balance reference request information), including the account transfer token and the balance inquiry token, for requesting inquiry/reference of information on the account of the user of the terminal 20 to the communication I. /F14 is used to transmit the affiliated bank server URI as an access destination to the corresponding bank server 50 (A bank server 50A or B bank server 50B) (B820).

When receiving the balance inquiry request information from the credit card company server 10 via the communication I/F, the control unit of the A bank server 50A updates the balance inquiry request information in the account management database (not shown) stored in the storage unit. From the account management data (not shown) associated with the included balance inquiry token, obtain information such as, by way of example and not limitation, branch number, account type, account number, balance information and transaction history, and first and last name. Then, among these pieces of information, the bank account information including at least the balance information is transmitted to the credit card company server 10 via the communication I/F (D830), and the process proceeds to D190 in FIG. 1-12. This completes the authentication system authorization process performed between the credit card company server 10 and the A bank server 50A.

In addition, when receiving the balance inquiry request information from the credit card company server 10 through the communication I/F, the control unit of the B bank server 50B sends the bank account information through the communication I/F as in the case of the A bank server 50A. , is sent to the credit card company server 10 (E830), and the process proceeds to E190 in FIG. 1-12. This completes the authentication system authorization processing performed between the credit card company server 10 and the B bank server 50B.

When account information including balance information is received from the bank servers 50 (A bank server 50A, B bank server 50B) through the communication I/F 14, the control unit 11 performs processing relating to billing of the settlement amount based on the received account information. Information to be used (for example, but not limited to, product purchase information, receipt information, etc.), bank account information linked to the credit card (for example, not limited, bank name, account number, balance information, etc.), payment account Payment account setting information including other information necessary to set is transmitted to the terminal 20A through the communication I/F 14 (C150), and the process proceeds to C160 in FIG. 1-12.

When the payment account setting information is received from the credit card company server 10 via the communication I/F 22, the control unit 21 receives the received payment account setting information (or information based thereon) (for example, not limitation, payment account setting screen) is displayed on the display unit 24 (A160), and the process proceeds to A170 in FIG. 1-12.
As a non-limiting example, to set product purchase information (payment date and time, payment store, payment amount, etc.), bank account information linked to credit cards (bank name, account number, balance information, etc.), and payment account The display unit 24 can display a payment account setting screen including information such as other information (first icon, second icon, etc.) necessary for the payment.

In addition to the balance information, the terminal 20 uses image information for selecting and setting payment methods such as (A) installment payment, (B) revolving payment, and (C) loan payment, which are described in the sixth embodiment. (the above-described third icon, etc.) may or may not be displayed on the payment account setting screen or the transaction-by-transaction payment account setting screen.

<Effects of the seventh embodiment>
This embodiment shows a configuration in which the terminal 20 displays on the display unit 24 the balance information of the bank account selected by the user as the payment account.
As an example of the effect of the embodiment obtained by such a configuration, since the user can check the balance of the first account related to the first account information selected by the user of the terminal, payment from the first account can be performed. It becomes easy to judge whether it is possible or not.

<Seventh Modification>
The technique of the seventh embodiment can be similarly applied to various contents described in the first modified example.
By way of example and not limitation, balance information may be displayed by applications such as messaging applications and electronic money applications.

Also, as described in the first modification,
(a) Configuration of electronic money service function as one function of chat application (b) Configuration of chat service function as one function of electronic money application (c) Combination of chat service function and electronic money service function It is also possible to apply a form that constitutes a composite (integrated) application having

<Display screen>
FIG. 7-4 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20A in this modified example. FIG. 7-4 is a diagram showing an example of the display screen when the balance information is displayed on the payment account setting screen in the electronic money application of the terminal 20. FIG.

FIG. 7-4 shows an example of a display screen (payment account setting screen) of a payment account setting page of the electronic money application.

A bank account information display area is configured to display bank account information linked to a credit card (for example, but not limited to, bank name, account number, balance, etc.).In this example, it corresponds to Bank A. The characters "A bank" are displayed as the name of the bank to which the account is to be transferred, the numbers "XXXXXXX" as the account number, and the numbers "YYYYYY Yen" as the balance. Also, the characters "B bank" are displayed as the bank name corresponding to "B bank", the numbers "XXXXXXX" as the account number, and the numbers "YYYYYY Yen" as the balance.
In addition, the same information as the screen in the center of FIG. 1-31 is displayed.

<Processing>
The processing in this modified example applies the processing in FIG. 7-3 to the processing in FIGS. 1-24 to 1-25, 1-28, 1-30, 1-32, etc. A detailed description is omitted because the same configuration can be achieved by doing so.

<Eighth embodiment>
The eighth embodiment is an embodiment in which a payment account is determined (automatically determined) on the device (terminal or server) side.
The content described in the eighth embodiment can be applied to each of the other embodiments and modifications.
Moreover, the same code|symbol is attached|subjected about the component same as an already-appearing component, and description for the second time is abbreviate|omitted.

In this embodiment, the terminal 20 or the credit card company server 10 performs processing for determining a payment account (hereinafter referred to as "payment account determination processing").
Here, "determination of payment account" includes, as a non-limiting example, determining the bank account to be set as the payment account in the payment account setting process, and sending the candidate bank account to be set as the payment account to the user of the terminal 20. The concept can include either of proposing (suggesting) and .
In the former case, the determined bank account is automatically set as the payment account.
On the other hand, in the latter case, the determined bank account is proposed to the user of the terminal 20, and then, if the user of the terminal 20 agrees, the bank account is set as the payment account.

<Data structure>
FIG. 8-1 is a diagram showing a data configuration example of payment account determination data stored in the storage unit 15 of the credit card company server 10 in this embodiment.
This data may be, by way of example and not limitation, user A. . This is the data set for A.

The payment account determination data includes, as a non-limiting example, a condition number (No), an account determination condition corresponding to this number, and a bank account determined by this condition (hereinafter referred to as "determined account"). ) are stored in association with each other. In the determined account, the account ID corresponding to the determined account is written in parentheses.

Note that this data is merely an example and is not limited to this.
It is not necessary to associate and store all of the above information, and some of the information may not be stored.
Further, determination of success or failure of the conditions may be realized by a program rather than by referring to the above data.
This also applies to data described in other embodiments.
An example of the "account determination condition" will be described in detail below.

<No “SP11”>
For No "SP11", "type of purchased product or service" is defined as an account determination condition, and in association with this, a plurality of types of goods or services are defined. In this example, a plurality of product types such as "food", "clothes", and "medicine" are stored.

Also, in the determined account (account ID), the user A.A. A's bank account (account ID) is stored. In this example, "grocery" has "bank account at bank A (BA001)", "clothing" has "bank account at bank B (BB001)", and "medicine" has "bank account at bank A (BA001)". account (BB002)” are stored respectively.

Although the processing becomes complicated, the account determination condition may or may not be set for each product or service instead of the type of product or service.

<No “SP12”>
For No "SP12", "the type of store where the product or service was purchased" is defined as the account determination condition, and a plurality of store types are set in association with this. In this example, a plurality of types such as "supermarket", "department store", and "restaurant" are stored as the types of shops.

Also, in the determined account (account ID), user A. A's bank account (account ID) is stored. In this example, "Supermarket" has "A bank account (BA001)", "Department store" has "C bank account (BC001)", and "Restaurant" has "B bank account (BA001)". BB001)” are stored respectively.

Although the processing becomes complicated, the account determination condition may or may not be set for each store instead of the type of store.

<No “SP13”>
For No "SP13", the "purchase amount for purchasing the product or service" is defined as the account determination condition, and a plurality of purchase amount ranges are set in association with this. In this example, a plurality of ranges such as "less than 100,000 yen", "100,000 yen or more and less than 500,000 yen", and "500,000 yen or more and less than 1 million yen" are stored as the purchase amount range.

Also, in the determined account (account ID), the user A.A. A's bank account (account ID) is stored. In this example, "less than 100,000 yen" has "A bank account (BA001)", "100,000 yen or more and less than 500,000 yen" has "C bank account (BC001)", and "50 10,000 yen or more and less than 1,000,000 yen” stores “bank account of bank C (BC002)”.

The "purchase amount" in this condition may be the purchase amount for one transaction, or may be the total purchase amount for one month.

Applying at least one of these conditions, terminal 20 or credit card company server 10 determines the payment account.

The data for determining the payment account can be generated by the control section 21 of the terminal 20 based on the input by the user of the terminal 20 and stored in the storage section 28 .
Alternatively, it can be generated by the control unit 11 of the credit card company server 10 and stored in the storage unit 15 based on the input of the user of the terminal 20 .

As a non-limiting example, when the credit card company server 10 determines the payment account, as a non-limiting example, the user of the terminal 20 (in this example, user A.A.) is requested in advance to the credit card company's web page or the like. It is possible to access and input necessary items, and based on the input results, the control section 11 of the credit card company server 10 can generate payment account determination data.

As another method, the control unit 11 of the credit card company server 10 controls the credit card payment history (transaction history) of the user of the terminal 20 (user AA in this example), more specifically, which From which bank accounts do they tend to debit for types of goods or services, from which bank accounts do they tend to debit for what types of stores, and from which bank accounts do they tend to debit for what amounts? is analyzed and estimated. Then, the control unit 11 can generate payment account determination data based on the estimation result.

The application of the credit card company installed on the terminal 20 and the household account book application installed on the terminal 20 are linked, and based on the data of the user's household account book in the household account book application, the payment account determination data may or may not be generated.

In addition to the above, as an example and not limitation, the payment account is determined based on the terminal 20 (its user) located near the current location of one terminal 20 (its user). can also

Specifically, as a non-limiting example, the payment account may be determined based on a condition such as ``the person who was nearby when the product or service was purchased was the person who was set''. . As an example and not a limitation, if a specific person such as a family member or friend of the user of the terminal 20 exists near the terminal 20, the user of the terminal 20 may go out to eat or shop with those persons, A case can be considered in which the amount is withdrawn from a specific bank account by credit card settlement.

Therefore, the terminal 20 or the credit card company server 10 determines whether or not the terminal 20 of the registered specific person is located near the terminal 20 . Then, if it is determined that it is located, the specific bank account of the user of the terminal 20 can be determined as the payment account.

It should be noted that the determination of whether or not the terminal 20 of a specific person is located near the terminal 20 is not limited to a system in which terminals communicate wirelessly with each other, but is not limited to a short-distance system such as Bluetooth. It can be realized by communicating by a P2P (peer-to-peer) method or the like using wireless communication technology.
If the terminal 20 makes the determination, it can be determined through the above communication whether the terminal 20 of a specific person is located nearby.
If the credit card company server 10 makes the determination, the terminal 20 transmits the above communication result information to the credit card company server 10, so that the credit card company server 10 can make the determination.

In addition to this, each terminal 20 transmits the latest terminal position information of its own terminal 20 to the credit card company server 10 . Then, based on the terminal location information received from each terminal 20, the credit card company server 10 can determine whether the terminal 20 of a specific person is located nearby.

<Processing>
FIG. 8B is a flowchart showing an example of the flow of processing executed by each device in this embodiment.
Here, the processing when the control unit 11 of the credit card company server 10 determines the payment account is exemplified. Further, here, a process for proposing (suggesting) to the user of the terminal 20 bank account candidates to be set as the payment account will be exemplified.
Since the processes up to A130 and C130 shown in FIGS. 1-11 and 1-12 are the same, illustration and description are omitted.

After C120 in FIG. 1-11, the control unit 11 executes payment account determination processing (C910). Specifically, by way of example and not limitation, payment accounts are determined based on the aforementioned data for determining payment accounts.

Next, the control unit 11 determines whether or not the payment account has been determined (C920), and if it is determined that the payment account has been determined (C920: YES), as an example and not as a limitation, the billing information including the determined payment account information, It is transmitted to the terminal 20 through the communication I/F 14 (C930). Then, the control unit 11 advances the process to C140 in FIG. 1-12.

On the other hand, if it is determined that the payment account has not been determined (C920: NO), the control section 11 advances the process to C130 in FIG. 1-12.
The case where the payment account cannot be determined means the case where there is no data that satisfies the above conditions for payment account determination data.

When billing information is received from the credit card company server 10 via the communication I/F 22, the control unit 21 advances the process to A130 in FIG. 1-12.
In this case, in A130, the received billing information is displayed on the display unit 24 of the terminal 20A. At this time, the determined payment account information is also displayed, so that the bank account used as the payment account is displayed by the user. proposed to
This allows the user to consider whether it is okay to set up that bank account as a payment account.

<Eighth modification>
The method of the eighth embodiment can be similarly applied to various contents described in the first modified example.
By way of example and not limitation, an application, such as a messaging application or an electronic money application, may allow payment accounts to be set up in an automatic payment account setup scheme.

Also, as described in the first modification,
(a) Configuration of electronic money service function as one function of chat application (b) Configuration of chat service function as one function of electronic money application (c) Combination of chat service function and electronic money service function It is also possible to apply a form that constitutes a composite (integrated) application having

<Processing>
The processing in this modified example applies the processing in FIG. 8-2 to the processing in FIGS. 1-24 to 1-25, 1-28, 1-30, 1-32, etc. A detailed description is omitted because the same configuration can be achieved by doing so.

<Ninth embodiment>
The ninth embodiment is an embodiment in which privilege information associated with a bank account of a credit card is notified to the user and the user can receive a privilege corresponding to the privilege information.
The content described in the ninth embodiment can be applied to each of the other embodiments and each of the other modifications.
Moreover, the same code|symbol is attached|subjected about the component same as an already-appearing component, and description for the second time is abbreviate|omitted.

<Display screen>
FIG. 9-1 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20A in this embodiment, showing an example of a payment account setting screen corresponding to a web page of a credit card company.

On this payment account setting screen, under the schematic image of the cash card of Bank A linked to the credit card, "Bank A A campaign image G1A including the words "Point Y% reduction" is displayed.
In addition, below the schematic image of the cash card of Bank B linked to the credit card, "Bank B Coupon Distribution" is displayed as privilege information when the account is transferred from the bank account of Bank B. A campaign image G1B including characters is displayed.
In addition, the same information as the screen in the center of FIG. 1-10 is displayed.

<Processing>
The processing in this embodiment can be configured similarly according to the flow charts shown in FIGS. 1-11 and 1-12.
Note that processing other than C150 and A160 in the flow charts shown in FIGS. 1-11 and 1-12 is the same, so description thereof will be omitted.

If C140 in FIG. 1-12 is determined to be YES, the control unit 11, based on the received payment account setting request information, collects information related to billing of the settlement amount (for example, but not limited to, product purchase information, Receipt information, etc.), bank account information linked to the credit card (examples, but not limitation, bank name, account number, etc.), and other information necessary to set up a payment account (examples, not limitation) , a first icon corresponding to the bank account, a second icon that is saved and determined after selecting the first icon, etc.), and information on benefits that the user can obtain in association with each of the bank accounts linked to the credit card. to the terminal 20A via the communication I/F 14 (C150), and the process proceeds to C160 in FIG. 1-12.

When the payment account setting information is received from the credit card company server 10 via the communication I/F 22, the control unit 21 receives the received payment account setting information (or information based thereon) (for example, not limitation, payment account setting screen) is displayed on the display unit 24 (A160), and the process proceeds to A170 in FIG. 1-12.

In addition, after the account transfer is performed, the credit card company server 10 transmits to the terminal 20A privilege information corresponding to the bank account in which the account transfer was performed, that is, the bank account selected as the payment account by the user. do. Then, the terminal 20A can cause the display unit 24 to display the received privilege information.

Without limitation, in the example of FIG. 9-1, when a payment is made using the bank account of Bank A as the payment account, after account transfer processing is performed by the Bank A server 50A, the credit card company server 10 As a benefit, a point return process (as an example, not a limitation, a process of storing Y% points in association with user A.A) can be performed.
In addition, when a payment is made using the bank account of Bank B as the payment account, after bank transfer processing is performed by the bank B server 50B, the credit card company server 10 performs coupon provision processing (limited to As an example, a process of transmitting coupon information to the terminal 20A) can be performed.

<Effect of the ninth embodiment>
In this embodiment, the terminal 20 receives information such as discounts, campaigns, coupons, etc. associated with the bank account information selected as the payment account by the user of the terminal 20 itself (not limited to, the information associated with the first account information An example of privilege information) is shown on the display unit 24. FIG.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to obtain a privilege by making a payment with the first account related to the selected first account information, can be made visible to users of

Also, in this case, the terminal 20 receives information such as discounts, campaigns, coupons, etc. obtained by the user based on payment by the bank account selected by the user of the terminal 20 as the payment account (an example of privilege information associated with ) can be displayed on the display unit 24 .
As an example of the effect of the embodiment obtained by such a configuration, it is possible to confirm the privilege obtained by the user of the terminal based on the payment by the first account related to the selected first account information.

<Ninth Modification (1)>
By way of example and not limitation, an application, such as a messaging application or an electronic money application, may display reward information associated with a bank account linked to a credit card.

Also, as described in the first modification,
(a) Configuration of electronic money service function as one function of chat application (b) Configuration of chat service function as one function of electronic money application (c) Combination of chat service function and electronic money service function It is also possible to apply a form that constitutes a composite (integrated) application having

FIG. 9-2 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20A in this embodiment, showing an example of a payment account setting screen in an electronic money application.

On this payment account setting screen, under the schematic image of the cash card of Bank A linked to the credit card, "Bank A A campaign image G1A including the words "Point Y% reduction" is displayed.
In addition, below the schematic image of the cash card of Bank B linked to the credit card, "Bank B Coupon Distribution" is displayed as privilege information when the account is transferred from the bank account of Bank B. A campaign image G1B including characters is displayed.
In addition, the same information as the screen in the center of FIG. 1-31 is displayed.

<Processing>
Because the processing in this modified example can be configured similarly based on the processing of FIGS. , detailed description is omitted.

<Ninth Modification (2)>
In the above embodiment, information about a new bank (as a non-limiting example, new bank information) and image information corresponding to the new bank (as a non-limiting example, select a bank account for opening a new bank account) information) may be displayed.
Further, privilege information given to the user upon opening a new bank account may be displayed.

"New bank information" is information about a bank that is not tied to a credit card, as a non-limiting example, information about a bank with which the user has not opened a bank account.
By way of example and not limitation, the bank name of the new bank, campaign information for the new bank, etc. may be included.

<Display screen>
FIG. 9-3 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20A in this embodiment, showing an example of a payment account setting screen corresponding to a web page of a credit card company.

On this payment account setting screen, new bank information (as a non-limiting example, A new bank information display area is configured for displaying the bank name of the new bank, campaign information of the new bank, etc.). In this example, a campaign image G2C containing the characters "Recommended for you>" and the characters "C bank point Z% reduction" as new bank information, and a campaign image including the characters "D bank coupon distribution" An image G2D is displayed.

In addition, at the bottom of the payment account setting screen, as information for selecting a bank account to open a new bank account, "Customers who wish to open a PR account, click here!" An icon IC4C containing characters of "Bank C" and an icon IC4D containing characters of "Bank D" corresponding to Bank D are displayed.
In addition, the same information as the screen in the center of FIG. 1-10 is displayed.

<Processing>
The processing in this embodiment can be configured similarly according to the flow charts shown in FIGS. 1-11 and 1-12.
Note that processing other than C150 and A160 in the flow charts shown in FIGS. 1-11 and 1-12 is the same, so description thereof will be omitted.

If C140 in FIG. 1-12 is determined to be YES, the control unit 11, based on the received payment account setting request information, collects information related to billing of the settlement amount (for example, but not limited to, product purchase information, Receipt information, etc.), bank account information linked to the credit card (examples, but not limitation, bank name, account number, etc.), and other information necessary to set up a payment account (examples, not limitation) , a first icon corresponding to a bank account, a second icon that is saved and determined after selecting the first icon, etc.), bank information that is not linked to a credit card and for which the user has not opened a bank account, Information for the user to open a bank account is sent to the terminal 20A via the communication I/F 14 (C150), and the process proceeds to C160 in FIG. 1-12.

When the payment account setting information is received from the credit card company server 10 via the communication I/F 22, the control unit 21 receives the received payment account setting information (or information based thereon) (for example, not limitation, payment account setting screen) is displayed on the display unit 24 (A160), and the process proceeds to A170 in FIG. 1-12.

<Ninth Modification (3)>
By way of example and not limitation, an application, such as a messaging application or an electronic money application, may cause information such as new bank information to be displayed.

Also, as described in the first modification,
(a) Configuration of electronic money service function as one function of chat application (b) Configuration of chat service function as one function of electronic money application (c) Combination of chat service function and electronic money service function It is also possible to apply a form that constitutes a composite (integrated) application having

<Display screen>
FIG. 9-4 is a diagram showing an example of a screen displayed on the display unit 24 of the terminal 20A in this embodiment, showing an example of a payment account setting screen in an electronic money application.

On this payment account setting screen, new bank information (as a non-limiting example, A new bank information display area is configured for displaying the bank name of the new bank, campaign information of the new bank, etc.). In this example, a campaign image G2C containing the characters "Recommended for you>" and the characters "C bank point Z% reduction" as new bank information, and a campaign image including the characters "D bank coupon distribution" An image G2D is displayed.

In addition, at the bottom of the payment account setting screen, as information for selecting a bank account to open a new bank account, "Customers who wish to open a PR account, click here!" An icon IC4C containing characters of "Bank C" and an icon IC4D containing characters of "Bank D" corresponding to Bank D are displayed.
In addition, the same information as the screen in the center of FIG. 1-31 is displayed.

<Processing>
Because the processing in this modified example can be configured similarly based on the processing of FIGS. , detailed description is omitted.

<Other Examples Related to First to Ninth Examples>
(1) In the above embodiment, an example was shown in which the bank account from which the account transfer of each settlement amount (by transaction) out of the total settlement amount is to be transferred is set for each transaction. Alternatively, it may be possible to collectively set from which bank account each settlement amount (by transaction) of the total settlement amount is to be transferred.

Specifically, as a non-limiting example, the characters "payment account" are displayed in the first icon display area of the current payment account setting screen, and the first icon containing the characters "A bank" corresponding to A bank is displayed. The icon and the first icon containing the letters "B Bank" corresponding to Bank B are not for each credit card transaction, but for one or more credit card transactions this month (A The first icon corresponding to the bank and the first icon corresponding to the B bank are displayed one by one).
Then, after tapping this first icon (the first icon corresponding to Bank A, as an example, not limitation), when the second icon is tapped, as an example, not limitation, the setting of the payment account for the current month is performed. be done collectively.

(2) In the above embodiment, as a method of payment to the credit card company in credit card settlement, a method of performing account transfer from a bank account was shown, but the method is not limited to such a form, and account transfer is performed from a bank account. It may be possible to pay by a method different from the method.
Specifically, as a non-limiting example, payment to a credit card company in credit card settlement is made by a method using electronic money or points convertible into electronic money. In this case, in the first icon display area of the payment account setting screen or the payment account setting screen for each transaction, a fifth icon (example, not limitation) for making payment using electronic money or points that can be converted into electronic money , an icon containing the words "pay with points", an icon containing the words "pay with points", etc.) can be displayed.

(3) In addition to the amount input method described in the above embodiment, it is also possible to set up a payment account by one of the following methods as an example and not as a limitation.
(A) Fixed transfer amount method (B) Ratio setting method

(A) "Fixed transfer amount method" is, as an example and not a limitation, when the user arbitrarily designates the transfer amount to be transferred from one bank account, the remaining transfer amount is transferred from another bank account. It is a method that is automatically set so that
Specifically, as a non-limiting example, if the total settlement amount is "100,000 yen" and the user designates "60,000 yen" as the transfer amount for account transfer from one bank account, then "6 10,000 yen" is transferred from one bank account, and the remaining transfer amount of "40,000 yen" is transferred from another bank account.

(B) The "proportion setting method" is, for example and not limitation, the transfer amount for direct debit from one bank account and the transfer amount for direct debit from another bank account at an arbitrary ratio (ratio , percentage, etc.), the payment account is automatically set.
Specifically, as a non-limiting example, the total settlement amount is "100,000 yen", and the transfer amount is transferred from one bank account by the user, and the transfer amount is transferred from another bank account. If the ratio is specified as "8:2", "80,000 yen" of the total settlement amount of "100,000 yen" will be transferred from one bank account, and the remaining transfer amount will be "20,000 yen". is set up to be debited from another bank account.

(4) In the above example, the credit card contractor and the credit card user are the same (one-to-one relationship), but the credit card is not limited to such a form. The contract holder of the card and the user of this credit card do not have to be the same (they do not have to be linked one-to-one).

Specifically, when the credit card subscriber and the credit card user are not the same, the credit card may include, by way of example and not limitation, at least any of the following.
(A) Corporate credit card (B) Family credit card

(A) "Corporate Credit Card" means, by way of example and not limitation, that the party to this credit card is a legal entity (eg, without limitation, a company, sole proprietorship, etc.) and that the user of this credit card is that legal entity; It is a type of credit card used by people who belong to
In "corporate credit card", a corporate bank account or a user's personal bank account can be set as a bank account for account transfer.
A "corporate credit card" may also be referred to as a "company credit card," a "corporate card," a "business card," or the like.

(B) "Family Credit Card" means, by way of example and not limitation, the subscriber of this credit card and the user of this credit card who is a member of the subscriber's family It is a type of credit card used by spouses, parents, children (over 18 years old, excluding high school students), etc.).
In the "Family Credit Card", the contractor's bank account can be set as the bank account for account transfer.
A "family credit card" may also be referred to as a "family card" or the like.

(5) In the above embodiment, information (billing information, billing information finalized for the current month) regarding credit card settlement transactions is sent to the terminal 20 of the credit card user. Not limited to this, information (billing information, billing information finalized for the current month) in credit card settlement may be transmitted to the terminal 20 of a person other than the user of the credit card.
Specifically, as an example and not as a limitation, if the above-mentioned "corporate credit card" or "family credit card" is used, the information related to the transaction in these credit card payments (billing information, current month's final billing information) can be sent to the terminal 20 of a person different from the credit card user.

As an example and not a limitation, if a "corporate credit card" is used, the information related to transactions in this credit card payment (information request information, current month's billing information) is different from the user of this credit card (example, not limitation) can be transmitted to the terminal 20 of the person in charge of clerical work, accounting, etc. of the company who is the contractor.
Also, as a non-limiting example, if a "family credit card" is used, a person who is a contracting party whose transaction information (billing information, current month's billing information) in this credit card payment is different from the user of this credit card It can be sent to the terminal 20 of (as an example, not a limitation, a relative who is the contractor).

As for the timing at which information related to transactions in these credit card settlements is transmitted, in addition to the timing at which billing information and billing information confirmed for the current month are transmitted, timing different from this can also be applied as an example and not as a limitation.
Specifically, in the case of a corporate credit card, as an example rather than as a limitation, "the timing of the purchase of a non-work-related product or service for personal use" can be applied. In addition, in the case of a family credit card, as an example rather than as a limitation, "the timing of the purchase of a product or service with a high purchase price" or the like can be applied.

(6) In the above embodiment, an example of "payment in installments" was shown as a method of payment to a credit card company in credit card settlement. When the user selects (designates) the “payment in installments” method, at least one of the following methods can be applied as a method of setting up a payment account for monthly payment in installments, as an example and not as a limitation.
(A) Installment payment account fixed method (B) Installment payment payment account variable method

(A) “Installment payment account fixed method” is a method in which when a payment account is selected by the user for the first payment, the bank account selected by the user is set as the payment account for monthly installment payments. be.
Specifically, when the user selects payment in three installments and a bank account (as an example, but not a limitation, a bank account corresponding to Bank A) is selected as the payment account in the first payment, this bank account is Set up as a payment account for monthly installment payments.

(B) “Installment payment account variable method” means that when the user selects a payment account for each monthly payment, the bank account selected by the user is set as the payment account for monthly installment payments. method.
Specifically, the user selects three installment payments, and one bank account is used for monthly payments (as a non-limiting example, the first payment: the bank account corresponding to Bank A, the second payment: B When the bank accounts corresponding to the bank, 3rd payment: bank account corresponding to Bank A) are selected as payment accounts, these bank accounts are set as payment accounts in the installment monthly payments.

(7) In the above example, the payment account setting screen and the payment account setting screen for each transaction display information different from the bank name and account number as the bank account information linked to the credit card (as an example, not limited to This is not limited to such a form, and a screen different from the payment account setting screen or the payment account setting screen for each transaction is displayed, linked to the credit card. Information other than the bank name and account number may be displayed as the current bank account information (for example, but not by way of limitation, balance information related to the balance of the bank account).
Specifically, as a non-limiting example, billing information and current month's billing information, as bank account information linked to a credit card, along with the bank name and account number, as a non-limiting example, bank account balance Associated balance information may be displayed.

(8) In the above embodiment, the balance of the user's (depositor's) bank account itself is displayed.
Specifically, information relating to the user's (depositor's) bank account balance may include, by way of example and not limitation, at least any of the following:
(A) Expected balance information (B) Balance object information

(A) "Estimated balance information" is information related to the balance of the user's bank account, which is related to the expected balance when the settlement amount is subtracted from the balance of the bank account.
Specifically, as a non-limiting example, if the user's bank account balance is 100,000 yen and the settlement amount is 40,000 yen, "60,000 yen" is displayed as the expected balance information. be able to.

(B) "Balance object information" is information related to the balance of the user's bank account, and is information that displays the balance in an object format or the like.
Specifically, as a non-limiting example, a pie chart or bar graph (gauge) with 100% of the balance of the user's salary payment date (300,000 yen as an example, not a limitation) is used as an object, and the latest bank account The balance (100,000 yen as an example and not as a limitation) can be displayed as a pie chart or bar graph (gauge) of "33%" in this example.

(9) In addition, in relation to the display of the balance, when the settlement amount exceeds the balance of the bank account, the user may be notified that the settlement amount exceeds the balance of the bank account.
Specifically, by way of example and not by way of limitation, methods of informing the user that the payment amount exceeds the bank account balance may include, by way of example and not by way of limitation, at least any of the following.
(A) Change the display mode of expected balance information (B) Display alert information

In method (A), when the settlement amount exceeds the bank account balance, the user is notified that the settlement amount exceeds the bank account balance by changing the display mode of the expected balance information.
Specifically, by way of example and not limitation, if the settlement amount does not exceed the balance of the bank account, the expected balance information is displayed in the default first display mode (for example, but not by way of limitation, black characters). On the other hand, if the settlement amount exceeds the balance of the bank account, the expected balance information can be displayed in a second display mode different from the first display mode (as a non-limiting example, red characters).

In the method (B), when the settlement amount exceeds the balance of the bank account, alert information is displayed to inform the user that the settlement amount exceeds the balance of the bank account.
"Alert information" is information for notifying the user that the settlement amount exceeds the balance of the bank account, and can be included in the billing information and the current month's billing information as an example and not as a limitation.
Specifically, as a non-limiting example, if the payment amount does not exceed the bank account balance, the alert information will not be displayed, but if the payment amount exceeds the bank account balance, the alert information (example, not limitation) will be displayed. , the characters, mark, etc., of "Insufficient balance.") can be displayed.
Note that only this alert information may be transmitted to and displayed on the terminal 20 as information different from the billing information and the current month's fixed billing information.

Further, in the above embodiment, the server may remind the user to set a payment account based on the balance information of the bank account set as the payment account.
Specifically, if the server determines that the balance of the bank account set as the payment account is less than the amount of payment from that payment account, it indicates that the balance of the payment account is currently insufficient. Payment account setting reminder information including insufficient balance information and non-payment information indicating that payment cannot be made can be sent to the terminal 20 .

In this modification, the payment account setting reminder information (not limited, but an example of notification information) is at least the balance information of the bank account selected as the payment account by the user (not limited, but an example of the balance information of the first account ) to be transmitted to the terminal 20. FIG.
As an example of the effect of the modification obtained by such a configuration, notification information based on at least part of the purchase information can be transmitted to the terminal based on at least information on the balance of the first account.

(10) In the above embodiment, an example was shown in which the user can select the payment method to the credit card company in the credit card settlement, but this is not limited to such a form, and the set conditions are met. In this case, the user may be allowed to select the payment method to the credit card company in the credit card settlement.
Specifically, as a non-limiting example, conditions such as "the balance of the payment account has fallen below the set amount" and "the settlement amount has exceeded the balance of the payment account" can be set.
If this condition is not met, the user is not allowed to select the payment method to the credit card company in the credit card settlement. On the other hand, when this condition is satisfied, the user can select the payment method to the credit card company in the credit card settlement.

Specifically, as a non-limiting example, if the condition "the balance of the payment account has fallen below a set amount (not a limitation, but an example of 10,000 yen)" is not met, the third icon is not displayed, If the condition "the balance of the payment account has fallen below the set amount (not limited to, but as an example, 10,000 yen)" is established, a third icon can be displayed.

In addition, when the above set conditions are satisfied, as a method of allowing the user to select the payment method to the credit card company in credit card settlement, the method is not limited to displaying the third icon, and the condition is If this is the case, information different from the third icon may be displayed as a technique for allowing the user to select a payment method to the credit card company in credit card settlement.

Specifically, as "information different from the third icon", as an example and not as a limitation, link information of a web page of a loan company, advertisement information, or the like may be displayed. By doing so, the user can take out a loan from a loan company when there is a possibility that the settlement amount will exceed the balance of the payment account.

This modification shows a configuration in which the terminal 20 displays loan-related information on the display unit 24 based on the balance information of the bank account selected by the user as the payment account.
As an example of the effect of the embodiment obtained by such a configuration, if the balance of the first account associated with the first account information selected by the user of the terminal is insufficient to make the payment, the loan information can be notified to the user of the terminal.

(11) In the above embodiment, two bank accounts (bank accounts that can be set as payment accounts) linked to the credit card have been described, but three or more bank accounts may be used. Since the processing in this case can be configured in the same manner as in the above embodiment, detailed description thereof will be omitted.

(12) Among multiple credit card transactions (among multiple purchase information), for some or all of the credit card transactions (purchase information), from multiple bank accounts linked to the credit card It is possible not only to set one bank account as a payment account, but also to set two or more bank accounts as payment accounts.

As a non-limiting example, if three bank accounts, A bank account, B bank account, and C bank account, are linked to a credit card, for a certain credit card transaction (purchase information) By way of example and not limitation, two bank accounts, a bank account of B bank and a bank account of C bank, may be set as payment accounts.

In this case, as a non-limiting example, the transfer amount is transferred from each of the multiple payment accounts according to the above-mentioned amount input method, (A) transfer amount fixed method, (B) ratio setting method, etc. can be set based on input by the user of the terminal 20 .

(13) In the above embodiment, it is also possible to set a default payment account as described above.
In this case, instead of having the user select a bank account to be set as the payment account from among multiple bank accounts, the user may be asked to select a transaction for which payment is desired from a bank account different from the default payment account. good.
By way of example and not limitation, if you have a bank account at Bank A and a bank account at Bank B, and Bank A's bank account is set as the default payment account, you would like to pay from Bank B's bank account. Allow the user to choose which transactions to make. Then, for the selected transaction, the payment account can be updated to Bank B's bank account.

<Tenth embodiment>
The tenth embodiment is an embodiment that realizes deferred payment by a method different from the above-described embodiments. As the deferred payment, as described above, (1) credit card payment or (2) payment on credit can be applied.

In the embodiment described below, the above-mentioned (1) credit card settlement is applied as an example.
In the example described above, the credit card associated with the user of terminal 20 was associated with multiple bank accounts.
In contrast, in the embodiments described below, only one bank account is associated with the credit card associated with the user of terminal 20 .

Hereinafter, for convenience, a bank account associated with a user that is linked to a credit card associated with the user will be referred to as a "main bank account", and a bank account associated with the credit card associated with this user will be referred to as A bank account that does not have a

The content described in the tenth embodiment can be applied to each of the other embodiments and each of the other modifications.
Moreover, the same code|symbol is attached|subjected about the component same as an already-appearing component, and description for the second time is abbreviate|omitted.

In this embodiment, after the user makes a credit card payment, information such as the scheduled payment amount (not limited, but an example of the second amount) that is scheduled to be paid from the sub-bank account is sent to a predetermined amount. Server receives. Then, based on the received information, the predetermined server transfers the scheduled payment amount (not limited) from the sub bank account (not limited, but an example of the second account) to the main bank account (not limited, but an example of the first account) (an example of the second amount of money).

The processing related to remittance of the second amount from the second account to the first account includes, as an example and not limitation, the processing of actually remitting the second amount, and the information of the second amount to be transmitted to other parties in order to realize the remittance. This is a process that has some relationship with the remittance of the second amount, such as a process of transmitting to the device of the second amount. A specific example of this will be described later.

Predetermined servers that perform this process include, but are not limited to, financial institution servers (as a non-limiting example, bank server 50) and servers of fund transfer service providers (hereinafter referred to as "fund transfer service provider servers"). ) can be used.

In this embodiment, as an example and not a limitation, the funds transfer business is assumed to be the aforementioned electronic money service provider (electronic money application provider). The predetermined server is the server of the electronic money service provider described above, which is the server 60 described above.

In this embodiment, in credit card settlement, the user selects transaction information (purchase information) that the user wishes to make payment from the sub-bank account, and notifies the server 60 of it. In response to this, the server 60 communicates with the bank server 50 to transfer the purchase amount from the user's sub-bank account to the user's main bank account (bank account linked to the credit card). conduct. Here, "remittance" in this embodiment includes, as an example and not a limitation, charging electronic money from a sub-bank account and withdrawing money to a main bank account.
As a result, for transactions selected by the user, the purchase amount is actually deducted from the user's main bank account and paid to the credit card company. It will appear that the payment has been made.
Remittance in this way is called "inter-account remittance".

Methods for realizing inter-account remittance in this embodiment can be broadly classified into the following methods.
(1) Remittance (electronic money transfer/charge & withdrawal) for each transaction (2) Electronic money transfer/charge for each transaction and withdrawal for multiple transactions at once (3) Multiple transactions A method of collectively remittance (electronic money transfer, charge & withdrawal) for transactions

Moreover, as an example of the method (3), the following method is conceivable as a non-limiting example.
(3-1) Method of making remittance settings for each transaction and making a batch remittance for multiple transactions (3-2) Method of making a batch remittance setting for multiple transactions and making a batch remittance for multiple transactions

A case where each method is applied will be described below.

<System configuration>
In this embodiment, the communication system 1B shown in FIGS. 1-14 is applied as an example, not limitation, as a system configuration.
Also, in this embodiment, the server 60 explained with reference to FIG. 1-14 will be explained as a server of an electronic money service provider.

<Data structure>
FIG. 10-1 is a diagram showing a data configuration example of a user management database 159E, which is an example of the user management database 159 stored in the storage unit 15 of the credit card company server 10 in this embodiment.
Each user management data includes a contractor ID, an electronic money application ID, transaction data, and first registered bank account data.

The electronic money application ID is an account in the electronic money application of the user of this contractor ID.

Information about one bank account is stored in the first registered bank account data as bank account information linked to the credit card of the user of this contractor ID. Specifically, by way of example and not limitation, one account ID and the account transfer token corresponding to this account ID are stored in association with each other. In other words, the number of bank accounts linked to the credit card is one.

FIG. 10B is a diagram showing a data configuration example of an account management database 655E, which is an example of the account management database 655 stored in the storage unit 65 of the server 60 in this embodiment.
Each account management data stores, by way of example and not limitation, an e-money application ID, an e-money account balance, transaction data, second registered bank account data, and payment account setup data.

In the second registered bank account data, as information on the bank account of the user of this electronic money application ID, the account ID, the account transfer token, and the type are associated and stored as an example and not a limitation.

The account ID stores the account IDs of two or more (plural) bank accounts of this user.
As the account transfer token, the account transfer token corresponding to this account ID is stored.

The type is the main/sub type of the bank account of this account ID, and "main" is associated with the main bank account, and "sub" is associated with the sub bank account.
Specifically, the account ID stored in the first registered bank account data described above, that is, the bank account linked to the user's credit card is set as the main bank account, and the corresponding account ID is "main ” is associated and stored. On the other hand, an account ID that is not stored in the first registered bank account data described above, that is, a bank account that is not linked to the user's credit card is defined as a sub-bank, and the corresponding account ID is associated with "sub". stored.

By way of example and not limitation, the payment account setup data stores a transaction ID in association with a payment account ID.

Note that since the bank account linked to the credit card is the main bank account, the main bank account may be set as the default payment account as an example and not as a limitation. In this case, when a sub-bank account is selected as a payment account by the user, the payment account ID may be updated with that account ID.

<Display screen>
FIG. 10-3 is a diagram showing an example of screen transitions displayed on the display unit 24 of the terminal 20A in this embodiment.
FIG. 10-3 is a diagram showing an example of a display screen when setting a payment account in the electronic money application of terminal 20A.

The payment account setting screen in the electronic money application is displayed on the left side of FIG. 10-3.
At the top of this screen, characters of "Payment App", which is the name of the electronic money application, are displayed.
Also below that is information for setting up a payment account.

Specifically, the registered user A. As information about A's bank account, the main bank account information linked to the credit card (example, not limitation, bank name, account number, etc. corresponding to bank A, which is the main bank account) and credit card A bank account information display area is configured to display sub-bank account information (as a non-limiting example, bank name, account number, etc. corresponding to bank B, which is a sub-bank account).

Also, on the right of it, there is a first icon display area for displaying a first icon for selecting a bank account for the transfer. A first icon IC1A containing the characters "A bank" corresponding to , and a first icon IC1B containing the characters "B bank" corresponding to B bank are displayed.

In the payment account setting screen shown on the left side of FIG. 10-3, as a non-limiting example, when the first icon IC1B corresponding to Bank B is tapped and then the second button BT3 is tapped, as a non-limiting example, , a payment account setting completion screen as shown in the right of FIG. 10-3 is displayed in the electronic money application.

In the area for displaying the set payment account on this screen, the characters "payment account" and the characters "B bank" corresponding to B bank are displayed.
In addition, the same information as the screen on the right side of FIG. 1-31 is displayed.

In this example, the above screen diagram has the same display mode/user interface (UI) as the screen diagrams in the center of FIG. 1-31 and the screen diagrams on the right of FIG. 1-31 described in the first modified example.
In other words, in this embodiment, the payment amount is not deducted from the sub-bank account (bank B bank account in the above example), and the payment amount is actually debited from the main bank account (bank A bank account in the above example). is debited from the sub-bank account. In other words, the user does not need to be aware of the inter-account remittance, and can just select the payment account.

<Processing>
10-4 and 10-5 are flowcharts showing an example of the flow of processing executed by each device in this embodiment. This processing is an example of processing when applying the method (1) described above.
In this figure, from the left side, processing executed by the control unit 21 of the terminal 20A, processing executed by the control unit 21 of the server 60, processing executed by the control unit 11 of the credit card company server 10, and control of the A bank server 50A. 4 shows an example of processing executed by a unit.

Here, for the sake of clarity, user A. A's main bank account is the bank account of A bank (account ID: BA001), and user A.A. The sub-bank account of A is described as the bank account of Bank B (account ID: BB001).

When the billing information is received from the credit card company server 10 via the communication I/F 64, the control unit 61 converts the account management data based on the received billing information (as an example, not a limitation, to the billing page of the electronic money application including the billing information). update transaction data. And the control part 61 transmits the billing information which makes a transmission source the OA account of a credit card company to 20 A of terminals by communication I/F64 (B630).

Upon receiving billing information from the server 60 via the communication I/F 22, the control unit 21 executes step A130.

After B630, the control unit 61 determines whether or not the communication I/F 64 has received payment account setting request information from the terminal 20A (B640). The setting information is transmitted to the terminal 20A through the communication I/F 64 (B650).

When the communication I/F 22 receives the payment account setting information from the server 60, the control unit 21 displays the received payment account setting information on the display unit 24 (A660).

After that, the control unit 21 receives a payment account selection input from the user via the input unit (A670).
Specifically, if the user wishes to pay for this billing information from a sub-bank account (Bank B's bank account (account ID: BB001)), an input for selecting a sub-bank account is accepted. Then, the control unit 21 transmits payment account selection information indicating that the sub-bank account has been selected to the server 60 via the communication I/F 22 (A680).

If the user wishes to pay from the main bank account (bank account of bank A (account ID: BA001)) and the main bank account is selected, the control unit 21, for example and not limitation, A680, A690 step can be skipped.
Also, in this case, the control unit 61 can skip steps B660a and B670.

When the communication I/F 64 receives the payment account selection information from the terminal 20A, the control unit 61 executes inter-account remittance processing with the bank servers 50 (A bank server 50A, B bank server 50B) (B660a). .

FIG. 10-6 is a flow chart showing an example of the flow of inter-account remittance processing. 50B shows an example of processing executed by the control unit of 50B.

As an example and not a limitation, the control unit 61, based on the payment account selection information received from the terminal 20A, sets the payment account ID associated with the transaction ID corresponding to this billing information in the payment account setting data of the account management data to User A. The account ID of A's sub-bank account (account ID of B bank: BB001 in this example) is stored.

Then, the control unit 61 sets the purchase amount corresponding to this transaction ID in the transaction data as the remittance amount, and an account storing the remittance amount and the electronic money application ID of the target user (user A.A in this example). The electronic money transfer request information including the account transfer token associated with the account ID of the remittance source bank account (in this example, the bank account of B bank) included in the second registered bank account data of the management data is sent to the communication I. /F64 to send to B bank server 50B (B6610).

In response to this, the control unit of the B bank server 50B performs electronic money transfer processing (E6610). Specifically, from the account management database stored in the storage unit (not shown), the electronic money is calculated from the account balance stored in the account management data associated with the account transfer token included in the received electronic money transfer request information. The transaction history is updated by subtracting the remittance amount included in the transfer request information and adding the content of the current transaction to the transaction history stored in the account management data.
Then, the control unit of the B bank server 50B terminates the processing.

Next, the control unit of the B bank server 50B transmits electronic money transfer completion information indicating that electronic money transfer of the remittance amount has been completed to the server 60 via the communication I/F (E6620). As a result, the authentication system authorization processing performed between the server 60 and the B bank server 50B ends.

When the communication I/F 64 receives the electronic money transfer completion information from the B bank server 50B, the control unit 61 causes the display unit 63 to display the received electronic money transfer completion information (B6630). Note that this step may be omitted.

Thereafter, the control unit 61 performs charge processing (B6640). Specifically, based on the received transfer completion information, the remittance amount is added to the electronic money account balance of the account management data using electronic money.

Thereafter, the control unit 61 performs withdrawal processing (B6650). Specifically, the remittance amount is subtracted from the electronic money account balance in the above account management data, and this remittance amount is combined with the remittance destination bank account included in the second registered bank account data in the above account management data (this In the example, the payment information including the account transfer token associated with the account ID of the bank account of A bank) is transmitted to the A bank server 50A via the communication I/F 64 .

In response to this, the control section of the A Bank server 50A performs the deposit processing (D6650). Specifically, in the account management database stored in the storage unit (not shown), the withdrawal information is stored in the account balance stored in the account management data associated with the account transfer token included in the received withdrawal information. The transaction history is updated by adding the included remittance amount and adding the content of the current transaction to the transaction history stored in the account management data.
Then, the control unit of the A bank server 50A terminates the processing.

Next, the control unit of the A bank server 50A transmits payment completion information indicating that the payment has been completed to the server 60 via the communication I/F (D6660). As a result, the authentication system authorization processing performed between the server 60 and the A Bank server 50A is completed.

When the payment completion information is received from the A bank server 50A through the communication I/F 64, the control unit 61 causes the display unit 63 to display the received payment completion information (B6660). Note that this step may be omitted.
Then, the control unit 61 terminates the process.

Returning to FIG. 10-5, after performing the inter-account remittance process, the control unit 61 transmits inter-account remittance completion information indicating that the inter-account remittance has been completed to the terminal 20A via the communication I/F 64 (B670). . Then, the control unit 61 advances the process to B195.

In response to this, the control unit 21 displays the received inter-account remittance completion information on the display unit 24 (A690). Then, the control unit 21 advances the processing to A195.

If it is determined in C180 that the account transfer request condition is met (C180: YES), the control unit 11, as an example and not as a limitation, selects the first The bank server 50 of the bank corresponding to the account ID (in this example, A bank server 50A) (C690). Then, the control unit 11 advances the process to C195.

In the above processing, if the user wishes to pay from the main bank account and the main bank account is selected, the control unit 21 skips steps A680 and A690, but this is not skipped. You may do so.
However, even in this case, the control unit 61 can skip steps B660a and B670.

In addition, it is possible to arbitrarily decide the fee for realizing inter-account remittance between the electronic money service provider and the affiliated bank.
As an example, the electronic money service provider bears both the electronic money transfer fee and the deposit fee, and the fees are paid to the corresponding affiliated banks (A bank and B bank in the above example). can be
As another example, the electronic money transfer fee may be borne by the electronic money service provider, and the deposit fee may be borne by the bank to which the withdrawal is made (Bank A in the above example). can.

<Effects of the tenth embodiment>
In this embodiment, the server 60 (not limited, but an example of a server that communicates with a terminal) receives billing information ( example of purchase information) is received from the credit card company server 10; Then, the server 60 provides payment account selection information (not limited to and an example of the first information) and the amount (not limited, but an example of the second account) that the user of the terminal 20 pays from the sub-bank account (not limited, but an example of the second account). information (an example of second information, but not limitation), at least payment account selection information relating to the sub-bank account is received from the terminal 20; Then, based on the received inter-account remittance request information, the server 60 causes the control unit 61 to perform inter-account remittance processing (not a limitation, but an example of processing related to remittance of the second amount from the second account to the first account). shows the configuration performed by
As an example of the effect of the embodiment obtained by such a configuration, after the second amount of money is remitted from the second account to the first account, the payment can be made by deferred payment from the first account.

Also, in this case, the payment account selection information (first information) including information on the amount to be paid by the user of the terminal 20 from the main bank account includes information requesting payment from the main bank account for the first purchase information, and the terminal The payment account selection information (second information) containing the information of the amount to be paid by the 20 users from the sub-bank account may include information requesting payment from the sub-bank account for the second purchase information.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to actually make the payment from the first account as if the second purchase information were paid from the second account. .

Also, in this case, the inter-account remittance process can be performed before the closing date (not a limitation, but an example of a set date), as an example and not a limitation.
As an example of the effect of the embodiment obtained by such a configuration, the second amount of money can be transferred from the second account to the first account by the set date.

Also in this case the post-payment can be made by means of a credit card associated with the user of the terminal.
As an example of the effect of the embodiment obtained by such a configuration, after the second amount of money is remitted from the second account to the first account, payment can be made from the first account by credit card. .

In addition, in the present embodiment, the inter-account remittance processing (processing related to remittance) is based on the inter-account remittance request information (second information), and the electronic money of the user of the terminal 20 is transferred from the sub-bank account (second account). It shows a configuration including a process of transferring the remittance amount to an account (not limited, but an example of a third account) and a process of transferring the remittance amount from the electronic money account to the main bank account (first account).
As an example of the effect of the embodiment obtained by such a configuration, the second amount of money can be properly transferred from the second account to the first account via the third account.

Also, in this case, the electronic money account (third account) can be managed by the server 60 .
As an example of the effect of the embodiment obtained by such a configuration, since the third account is managed by the server, which is the main processing entity of the processing related to remittance, the remittance via the third account is reliably performed. can do.

Also, in this case, the process of transferring the remittance amount from the sub-bank account (second account) to the electronic money account of the user of the terminal 20 (not limited, but an example of the third account) is performed by transferring the balance of the sub-bank account to the electronic money account. It is possible to include charge processing to the account.
As an example of the effect of the embodiment obtained by such a configuration, it is possible to realize the remittance of the second amount from the second account to the third account by the process of charging the third account from the balance of the first account. .

Also, in this case, the electronic money account can be charged with the remittance amount in electronic money (electronic currency).
As an example of the effect of the embodiment obtained by such a configuration, it is possible to appropriately charge the second amount of money with electronic money.

<Tenth Modification (1)>
It is also possible to apply the method (2) described above.
With this method, multiple transactions are collectively withdrawn, so there is the advantage of being able to reduce the above-mentioned fees.

FIG. 10-7 is a flow chart showing an example of the flow of processing executed by each device in this modified example, and illustrates the portion corresponding to FIG. 10-5.
After B650, when the communication I/F 64 receives the payment account selection information from the terminal 20A, the control unit 61 performs electronic money transfer and charge processing (B661).
Specifically, the bank server 50 requesting the electronic money transfer (B bank server 50B in this example) exchanges data similar to B6610 to B6640 and E6610 to E6620 in FIG. process.

After that, the control unit 61 determines whether or not the payment condition is satisfied (B663).
The withdrawal condition may be, by way of example and not limitation, "the withdrawal date and time has come".

As described above, by way of example and not limitation, the deadline for setting up a payment account can be set to a day (date and time) prior to the account transfer date for credit card payments. By way of example and not limitation, if the 25th of each month is the debit date and three days before that is set as the payment account establishment deadline date, as described above, the 22nd of each month will be the payment account establishment deadline.

Based on this, the withdrawal date and time can be set as a date and time after the payment account establishment deadline and before the account transfer date, as an example and not a limitation.

If it is determined that the withdrawal condition is not satisfied (B663: NO), the control unit 61 advances the process to B195.
On the other hand, if it is determined that the withdrawal condition is satisfied (B663: YES), the control section 61 performs withdrawal processing (B665).
Specifically, the same processes as B6650 to B6660 and D6650 to D6660 in FIG. conduct.

After that, the control unit 61 transmits payment completion information indicating that the payment has been completed to the terminal 20A via the communication I/F 64 (B667). Then, the control unit 61 advances the process to B195.

When applying the method (2) above, the balance of the electronic money account increases due to charging, but the user of the terminal 20 can use the balance of the electronic money account to perform electronic money settlement, etc. be. Due to the consumption of the electronic money account balance, the electronic money account balance may become insufficient at the timing of collective withdrawal.

Therefore, an electronic money account that can be used by the user (normal electronic money account: hereinafter referred to as "first electronic money account") and an electronic money account that cannot be used by the user (electronic money account for withdrawal: hereinafter referred to as a "second electronic money account").

In this case, the balance of the first electronic money account and the balance of the second electronic money account can be stored in the account management data.
Then, the control unit 61 of the server 60 can charge the second electronic money account in the electronic money transfer and charge process, and withdraw money from the second electronic money account in the withdrawal process.

<Tenth Modification (2)>
It is also possible to apply the method (3) described above.
This method also has the advantage of being able to reduce the above-mentioned fees, since remittance (charge & withdrawal) is performed collectively for multiple transactions.

FIG. 10-8 is a diagram showing a data configuration example of an account management database 655F, which is an example of the account management database 655 stored in the storage unit 65 of the server 60 in this embodiment.
Each account management data stores, by way of example and not limitation, an e-money application ID, an e-money account balance, transaction data, second registered bank account data, and payment account setup data.

In addition to the transaction ID and payment account ID, the payment account setting data includes, by way of example and not limitation, a remittance flag.

The remittance flag is set to "OFF" by default, but is set to "ON" when inter-account remittance is performed for this transaction ID. When the inter-account transfer is completed, this flag is set back to "OFF".

FIG. 10-9 is a flowchart showing an example of the flow of processing executed by each device in this modified example, and illustrates a portion corresponding to FIG. 10-5. This process is an example of the process when the technique (3-1) described above is applied.

After B650, when the communication I/F 64 receives payment account selection information from the terminal 20A, the control unit 61 performs inter-account remittance setting processing (B662).
Specifically, by way of example and not limitation, based on the payment account selection information received from terminal 20A, in the payment account setting data of the account management data, the payment account ID associated with the transaction ID corresponding to this billing information, User A. The account ID of the sub-bank account of A (in this example, the account ID of bank B: BB001) is stored, and the remittance flag is set to "ON".

After that, the control unit 61 determines whether or not the inter-account remittance condition is satisfied (B664).
The inter-account remittance condition may be, by way of example and not limitation, "the inter-account remittance date and time has come". As a non-limiting example, the inter-account remittance date and time can be set as a date and time after the payment account setting deadline and before the account transfer date, like the withdrawal date and time.

If it is determined that the inter-account remittance condition is not satisfied (B664: NO), the control unit 61 advances the process to B195.

On the other hand, if it is determined that the inter-account remittance condition is satisfied (B664: YES), the control unit 61 performs inter-account remittance processing (B660b).
This inter-account remittance processing can be performed in the same procedure as in FIG. 10-6. 10-6 as the remittance amount. Then, the control unit 61 resets all the remittance flags to "OFF".

After that, the control unit 61 transmits inter-account remittance completion information indicating that the inter-account remittance is completed to the terminal 20A via the communication I/F 64 (B666). Then, the control unit 61 advances the process to B195.

In addition to the above, it is also possible to apply the method (3-2) described above.

<Display screen>
FIG. 10-10 is a diagram showing an example of screen transitions displayed on the display unit 24 of the terminal 20A when the technique (3-2) described above is applied. FIG. 10-10 is a diagram showing an example of a display screen when setting a payment account in the electronic money application of terminal 20. FIG.

The left side of FIG. 10-10 is a payment account setting screen for this month ("October payment account setting screen" in this example) in the electronic money application, and the characters "Payment App", which is the name of the electronic money application, are displayed. there is
Below that, information similar to the screen in the center of FIG. 2-4 is displayed.

In the current month's payment account setting screen shown on the left side of FIG. 10-10, as an example and not limitation, for each credit card transaction, the first icon IC1A corresponding to Bank A (main bank account), Bank B ( After tapping the first icon IC1B corresponding to Bank A (main bank account) and the first icon IC1A corresponding to Bank A (main bank account), the second button BT3 is tapped. -10 The current payment account setting completion screen as shown on the right is displayed in the electronic money application.

This screen is a payment account setting screen for this month (“October payment account setting screen” in this example) in the electronic money application, and displays the characters “Payment App”, which is the name of the electronic money application.
In addition, below it, the same information as the screen on the right side of FIG. 2-4 is displayed.

10-11 and 10-12 are flow charts showing an example of the flow of processing executed by each device in this modified example.
Among them, FIG. 10-11 shows the part corresponding to FIG. 10-9.

After C131 in FIG. 10-11, the control unit 11 determines whether or not the current month finalized billing information transmission condition has been established (C720). As a result, current month fixed billing information including the account information of the target user's electronic money application (as an example, not limitation, the electronic money application ID) is transmitted to the server 60 via the communication I/F 14 (C730). Then, the control unit 11 advances the process to C180.

After B666 in FIG. 10-11, the control unit 61 determines whether or not the current month final billing information has been received from the credit card company server 10 via the communication I/F 64 (B725). B725: YES), this month's fixed billing information (as an example, not limitation, the billing page in the electronic money application including the current month's fixed billing information) is transmitted to the terminal 20A via the communication I/F 64 (B730).

After A694 in FIG. 10-11, when this month's fixed billing information is received from the server 60 via the communication I/F 22, the control unit 21 causes the display unit 24 to display the received this month's fixed billing information (A230).

After that, the control unit 21 determines whether or not an input for setting a payment account has been made through the input unit (A740). If it is determined that no input has been made (A740: NO), the control unit 21 advances the processing to A195.
On the other hand, if it is determined that an input has been made (A740: YES), the control unit 21 transmits payment account setting request information for requesting payment account setting to the server 60 via the communication I/F 22 (A750).

After B730, the control unit 61 determines whether or not the communication I/F 64 has received payment account setting request information from the terminal 20A (B740). The setting information is transmitted to the terminal 20A through the communication I/F 64 (B750).

When the communication I/F 22 receives the payment account setting information from the server 60, the control unit 21 causes the display unit 24 to display the received payment account setting information (A760).
Thereafter, the control unit 21 accepts selection of a payment account by the user via the input unit (A770). Specifically, for each transaction information included in the current month's billing information, transaction information for the user to pay from the main bank account (hereinafter referred to as "first transaction information") and transaction information for the user to pay from the sub-bank account Information (hereinafter referred to as "second transaction information"), at least the selection of the second transaction information is accepted.
The first transaction information can be one or more transaction information. Similarly, the second transaction information can also be one or more transaction information.

Thereafter, the control unit 21 transmits payment account selection information including the input information to the server 60 via the communication I/F 22 (A780).

When the communication I/F 64 receives the inter-account remittance request information from the terminal 20A, the control unit 61 performs inter-account remittance setting processing (B772).
Specifically, by way of example and not limitation, for each second transaction information selected by the user in the payment account setup data of the account management data, based on the payment account selection information received from terminal 20A, a corresponding transaction ID The payment account ID associated with user A. The account ID of the sub-bank account of A (in this example, the account ID of bank B: BB001) is stored, and the remittance flag is set to "ON".
Then, the control unit 61 advances the process to B664.

In the inter-account remittance process of B660b, the control unit 61 sets the remittance amount to the sum of the purchase amounts of the transaction IDs for which the remittance flag is set to "ON" in the payment account setting data of the account management data. - Perform the same processing as 6. That is, the sum of the purchase amounts corresponding to the second transaction information selected by the user is the amount transferred from the sub-bank account to the main bank account.

In this modification, the inter-account remittance process is performed on the inter-account remittance date (not a limitation, but an example of a set date), or the deferred account transfer date (as an example, not a limitation). It can be done by a set date (example).
As an example of the effect of the modification obtained by such a configuration, a second amount of money can be transferred from the second account to the first account on a set date or by a set date. can be done.

In addition, in this modification, the billing information is billing information confirmed for the current month including a plurality of pieces of billing information (not a limitation, but an example of purchase information including first purchase information, second purchase information, and third purchase information). where the first amount includes a purchase amount corresponding to the first billing information (an example of an amount based on the purchase of the first purchase information, not limitation), and the second amount is the two or more second billing information It shows a configuration including a total amount of corresponding purchase amounts (not a limitation, but an example of a total amount of the second purchase information and the third purchase information).
As an example of the effect of the modification obtained by such a configuration, a second amount of money including the total amount of the second purchase information and the third purchase information can be transferred from the second account to the first account.

In addition, in this modification, the deferred payment is performed by a credit card associated with the user of the terminal 20, and the inter-account remittance process is performed on the account transfer date of the credit card payment (not limited, but an example of the credit card payment date). 1 shows a configuration made based on
As an example of the effect of the modification obtained by such a configuration, a second amount of money can be transferred from the second account to the first account based on the payment date of the credit card.

<Tenth Modification (3)>
Amount information including the purchase amount corresponding to the transaction information for which the server 60 has selected to pay from the main bank account by the user and the purchase amount corresponding to the transaction information for which the user has selected to pay from the sub-bank account. may be transmitted to the credit card company server 10 to notify the credit card company, or may not be notified.

Since the credit card company server 10 stores information such as the purchase amount for each transaction of the user and the total purchase amount for the current month by the user in the storage unit 15, the credit card company receives the user's main account by bank transfer. I know how much money will be deducted from my bank account.
However, the server 60 transmits the above amount information to the credit card company server 10, so that the credit card company can analyze how the user properly uses a plurality of bank accounts.

In this modification, the server 60 stores payment account selection information including information on an amount (not limited, but an example of a second amount) to be paid by the user of the terminal 20 from a sub-bank account (not limited, but an example of a second account) In addition, payment account selection information is also received from the terminal 20, including information on the amount (example of a first amount, without limitation) that the user of the terminal 20 will pay from the main bank account (example of a first account, without limitation). do. Based on the received payment account selection information, the server 60 controls the processing related to paying the amount including the first amount and the second amount from the main bank account (not limited to, but an example of the first account). 61 shows the configuration performed by .
As an example of the effect of the embodiment obtained by such a configuration, not only the second information including the information of the second amount to be paid by the second account associated with the user of the terminal, but also the first account associated with the user of the terminal After receiving the first information including the information of the first amount to be paid, based on the first information and the second information, perform processing related to paying the amount including the first amount and the second amount from the first account. It can be carried out.

Also in this case the post-payment is made by the credit card associated with the user of the terminal 20 . Then, the processing related to paying the amount including the first amount and the second amount from the main bank account of the user of the terminal 20, which is performed by the control unit 61, includes the information of the amount including the first amount and the second amount. , a process of transmitting to the credit card company server 10 (not limited to, but an example of a first server that manages credit card information) via the communication I/F 64 .
As an example of the effect of the embodiment obtained by such a configuration, the amount of money including the first amount to be paid by the first account associated with the user of the terminal and the second amount to be paid by the second account associated with the user of the terminal The information can be communicated to a user (such as a credit card company) of a first server that manages credit card information. Thereby, the user of the first server can analyze how the user uses the first account and the second account properly based on the received amount information.

In addition, the processing related to paying the amount including the first amount and the second amount from the first account is not a limitation, but for example, the payment of the amount including the first amount and the second amount from the first account. Paying the amount including the first amount and the second amount from the first account, such as the process of notifying the other apparatus and the process of transmitting the information of the amount including the first amount and the second amount to the other apparatus. It is a process that has some relationship with

<Tenth Modification (4)>
To make an electronic money service provider pay for a user's payment amount by credit card settlement, that is, temporarily bear the burden. It is also possible for the electronic money service provider to withdraw the paid amount (hereinafter referred to as "advance amount") from the user's main bank account (first account) by account transfer or the like.

10-13 and 10-14 are flow charts showing an example of the flow of processing executed by each device in this modified example.
After B666, the control unit 61 determines whether or not the replacement payment conditions are satisfied (B792). The advance payment conditions are conditions under which the electronic money service provider pays the credit card company the payment amount for the credit card settlement on behalf of the user.
This reimbursement payment condition may be, by way of example and not limitation, "the reimbursement date and time has come". The reimbursement date and time may be, by way of example and not limitation, a date and time set by the credit card company.

If the replacement payment conditions are met (B792: YES), the control unit 61 performs the replacement payment process (B794).
Specifically, by way of example and not limitation, based on the transaction data of the account management data, user A. Calculate A's payment amount for the current month. Then, the calculated payment amount is used as the "advance amount", and a transfer process or the like is performed to remit the payment amount from the bank account of the electronic money service provider to the bank account of the credit card company.

After that, the control unit 61 determines whether or not the account transfer request condition is satisfied (B796).
The account transfer request condition is a condition for the server 60 to request (request) the bank server 50 for account transfer, and as an example, not a limitation, "account transfer date and time set by the electronic money service provider (example, not limitation)" As a result, it was 24:00 on the 25th of every month."

If it is determined that the account transfer request condition is satisfied (B796: YES), the control unit 61 sets the type "main ” and the information of the transfer request amount (=reimbursement amount) are sent to the bank server 50 of the bank corresponding to the account ID by the communication I/F 64. (In this example, bank A server 50A) (B798).

The information on the requested transfer amount (=reimbursement amount) includes the amount (second amount) paid by the user of the terminal 20 from the sub-bank account (second account) and the amount paid by the user of the terminal 20 from the main bank account (first account). ) to be paid (first amount).

In response to this, the control unit of the A bank server 50A executes account transfer processing based on the received account transfer request information (D190).
Through this account transfer processing, the transfer request amount (=reimbursement amount) is paid to the electronic money service provider.

In this case, the information (information to be communicated) transmitted from the server 60 to the bank server 50 of the user's main bank account can be any of the following as an example and not as a limitation.
・ Information on the first amount and information on the second amount ・ Information on the total amount of the first amount and the second amount (information on the amount to be paid from the first account)
・ Information on the total amount of the first amount and the second amount (information on the amount to be paid from the first account) and information on the second amount (information on the amount to be paid from the second account)

In this modification, the server 60 stores payment account selection information including information on an amount (not limited, but an example of a second amount) to be paid by the user of the terminal 20 from a sub-bank account (not limited, but an example of a second account) In addition, payment account selection information is also received from the terminal 20, including information on the amount (example of a first amount, without limitation) that the user of the terminal 20 will pay from the main bank account (example of a first account, without limitation). do.
Then, the server 60, as a process related to paying the amount including the first amount and the second amount from the main bank account of the user of the terminal 20, transfers the account transfer request information (=reimbursement amount) including the information of the transfer request amount (=reimbursement amount). Bank server 50 that manages the user's main bank account (not limited to, but an example of amount information including a first amount and a second amount) is sent by communication I/F 64 to bank server 50 that manages the first account. 2 servers (an example).
As an example of the effect of the embodiment obtained by such a configuration, the amount of money including the first amount to be paid by the first account associated with the user of the terminal and the second amount to be paid by the second account associated with the user of the terminal The information may be communicated to a user (such as a financial institution) of a second server that manages the first account of the user of the terminal. Thereby, the user of the second server can pay the amount based on the received information to the user of the server (electronic money service provider, etc.).

<Tenth Modification (5)>
In the above embodiment, the user (operator) of the server is the electronic money service provider (electronic money application provider), but it is not limited to this.
As an example and not a limitation, a financial institution such as a bank may be a user (operator) of the server.
In this case, if the user's main bank account and sub-bank account are bank accounts of the same bank (or the same bank and same branch), the bank server 50 of this bank processes the transfer from the sub-bank account to the main bank account. (Transfer processing) may be performed to realize the remittance.
On the other hand, if the user's main bank account and sub-bank account are bank accounts of different banks, as an example and not limitation, the bank server 50 of the bank of the sub-bank account transfers the sub-bank account to the main bank account of another bank. The remittance can be realized by performing transfer (transfer processing) to .

Also, as an example and not a limitation, a fund transfer service provider may be the user (operator) of the server.
In this case, as a non-limiting example, a fund transfer company such as the electronic money service provider described above can be the user of the server. , a chat service (chat application) can also be interposed.
(a) Configuration of electronic money service function as one function of chat application (b) Configuration of chat service function as one function of electronic money application (c) Combination of chat service function and electronic money service function A form that constitutes a composite (integrated) application with

<Eleventh embodiment>
In the eleventh embodiment, after the user makes a credit card payment, the server 60 transmits to the bank server 50 information such as the amount (second amount) for which the payment is to be made from the sub-bank account. This embodiment implements inter-account remittance between the bank server 50 that manages the main bank account and the bank server 50 that manages the sub-bank accounts.
In the following, this method is referred to as "bank-account-to-account transfer."
The content described in the eleventh embodiment can be applied to each of the other embodiments and each of the other modifications.
Moreover, the same code|symbol is attached|subjected about the component same as an already-appearing component, and description for the second time is abbreviate|omitted.

The methods for realizing bank-account remittance can be broadly divided into the following methods.
(A) A method of making a remittance (transfer) for each transaction (B) A method of setting the transfer request amount for each transaction and making a batch remittance for multiple transactions (C) A batch remittance for multiple transactions ( transfer)

Moreover, as an example of the method (C), the following method is conceivable as a non-limiting example.
(C-1) Method of making remittance settings for each transaction and making a batch remittance for multiple transactions (C-2) Method of making a batch remittance setting for multiple transactions and making a batch remittance for multiple transactions

A case where each method is applied will be described below.

<Processing>
In this embodiment, the server 60 pre-stores the electronic money application ID of the target user (here, referred to as "user A.A") in the account management data and the account in which this electronic money application ID is stored. Information including an account transfer token associated with the account ID of the bank account whose type is "main" (here, it is explained as "A bank account") included in the second registered bank account data of the management data is transmitted to the A bank server 50A by the communication I/F 64.
Then, the A bank server 50A sends the user A. A's electronic money application ID and user A.A. The account transfer token associated with A's bank account of A bank is associated and stored.

Similarly, the server 60 preliminarily stores the electronic money application ID of the target user (hereinafter referred to as "user A.A") in the account management data and the account management data in which the electronic money application ID is stored. The information including the account transfer token associated with the account ID of the bank account whose type is "sub" (here, it is described as "bank B bank account") included in the second registered bank account data of It is transmitted to the B bank server 50B by the communication I/F 64 .
Then, the user A.B is sent by the B bank server 50B. A's electronic money application ID and user A.A. A credit transfer token associated with A's bank account of B bank is stored in association with it.

After that, bank system inter-account remittance is realized via this electronic money application ID among the server 60, the A bank server 50A, and the B bank server 50B.

Note that this method is merely an example, and is not limited to this.
Remittance between bank accounts may be realized through identification information different from the electronic money application ID.
Also, with the consent of the affiliated bank, remittance between bank accounts may be realized via the account transfer token.

FIG. 11A is a flow chart showing an example of the flow of processing executed by each device in this embodiment. This processing is an example of processing when applying the method (A) described above.
Since the processing up to B650 shown in FIGS. 10-4 and 10-5 is the same as the processing after B670, illustrations and explanations are omitted.
In this figure, from the left side, processing executed by the control unit 21 of the terminal 20A, processing executed by the control unit 21 of the server 60, processing executed by the control unit 11 of the credit card company server 10, and control of the A bank server 50A. 4 shows an example of processing executed by a unit.

After B650, when the payment account selection information is received from the terminal 20A by the communication I/F 64, the control unit 61 executes the first bank system inter-account remittance process (B660c).

FIG. 11-2 is a flow chart showing an example of the flow of the first inter-bank account remittance process. 6 shows an example of processing executed by the bank B server 50B and processing executed by the control unit of the B bank server 50B.

As an example and not a limitation, the control unit 61, based on the payment account selection information received from the terminal 20A, sets the payment account ID associated with the transaction ID corresponding to this billing information in the payment account setting data of the account management data to User A. The account ID of A's sub-bank account (account ID of B bank: BB001 in this example) is stored.

Then, the control unit 61 sets the purchase amount corresponding to this transaction ID in the transaction data as the remittance amount, and sets the remittance amount and the bank system including the electronic money application ID of the target user (user A.A in this example). The inter-account remittance information is transmitted to the A bank server 50A via the communication I/F 64 (B6615).
The bank-system inter-account remittance information is information for requesting bank-system inter-account remittance, and in this example, is information for requesting the A bank server 50A to withdraw money from the B bank server 50B.

In response to this, the control unit of the A bank server 50A transmits the transfer request information including the remittance amount and the electronic money application ID of the target user (user A.A in this example) to the A bank server 50A. Send to B bank server 50B by I/F (D6615).

Upon receiving this, the control unit of the B bank server 50B performs transfer processing (E6615).
Specifically, of the account management database stored in the storage unit (not shown), the account stored in the account management data corresponding to the account transfer token associated with the electronic money application ID included in the received transfer request information. The remittance amount included in the transfer request information is subtracted from the balance, and the remittance amount is transferred to the A bank server 50A, which is the sender of the transfer request information and the transfer destination.

Then, the control unit of the B bank server 50B transmits transfer completion information including information for notifying that the transfer process has been completed to the A bank server 50A via the communication I/F of the B bank server 50B (E6617). .

When the transfer completion information is received from the B bank server 50B through the communication I/F, the control unit of the A bank server 50A sends information notifying that the processing related to the remittance of the remittance amount has been completed based on the received transfer completion information. is transmitted to the server 60 through the communication I/F of the A bank server 50A (D6617).

Returning to FIG. 11-1, after performing the first bank-system inter-account remittance process, the control unit 61 advances the process to B670.

<Effects of the Eleventh Embodiment>
In this embodiment, the server 60 sends information about the scheduled payment amount (not limited to, but an example of the second amount) that the user of the terminal 20 plans to pay from the sub-bank account to the main bank account (second 1 account) to a bank server 50 (not limited to, but an example of a second server) that performs a bank system inter-account remittance process.
As an example of the effect of the embodiment obtained by such a configuration, the second server managing the first account related to the terminal user is notified of the second amount to be paid by the second account related to the terminal user. can be done.

<Eleventh Modification (1)>
It is also possible to apply the method (B) described above.
This method has the advantage of being able to reduce the above-mentioned fees, since multiple transactions are collectively remitted.

FIG. 11-3 is a flowchart showing an example of the flow of processing executed by each device in this modified example, and illustrates the part corresponding to FIG. 11-1.
After B650, when the payment account selection information is received from the terminal 20A by the communication I/F 64, the control unit 61 performs the second bank system inter-account remittance processing (B660d).

FIG. 11-4 is a flow chart showing an example of the flow of the second bank method inter-account remittance processing. 6 shows an example of processing executed by the bank B server 50B and processing executed by the control unit of the B bank server 50B.

When transfer request information including the remittance amount and the electronic money application ID of the target user (user A.A in this example) is sent from the A bank server 50A to the B bank server 50B by D6615, the B bank server The control unit of 50B performs transfer setting processing (E6611).
Specifically, as a non-limiting example, the e-money application ID included in the transfer request information received from the A bank server 50A is associated with the electronic money application ID, the remittance amount included in the received transfer request information is added, and the remittance is performed. Set the flag to "ON".

Next, the control unit of the B bank server 50B determines whether or not the transfer conditions are met (E6613).
The transfer condition may be, by way of example and not limitation, "the date and time of the transfer has come". As a non-limiting example, the transfer date and time can be set as a date and time after the payment account setting deadline and before the account transfer date, like the remittance date and withdrawal date and time described above.

If it is determined that the transfer conditions are not satisfied (E6613: NO), the control unit of the B bank server 50B terminates the process.

On the other hand, if it is determined that the transfer conditions are met (E6613: YES), the control unit of the B bank server 50B advances the process to E6615.
Upon receiving this, the control unit of the B bank server 50B performs transfer processing (E6615).
Specifically, of the account management database stored in the storage unit (not shown), the account stored in the account management data corresponding to the account transfer token associated with the electronic money application ID included in the received transfer request information. The latest remittance amount (cumulative remittance amount) stored in association with this electronic money application ID is subtracted from the balance, and the A bank server 50A, which is the sender of the transfer request information and the transfer destination, Remit the remittance amount.
Then, the control unit of the B bank server 50B advances the process to E6617.

Returning to FIG. 11-3, after performing the second bank method inter-account remittance process, the control unit 61 advances the process to B670.

In the above process, the A bank server 50A performs a process of cumulatively adding and updating the remittance amount included in the bank system inter-account remittance information received from the server 60, and when the transfer request condition is met, , the transfer request information including information on the accumulated remittance amount may be transmitted to the B bank server 50B.
In this case, the B bank server 50B remits the cumulative remittance amount included in the received transfer request information to the A bank server 50A by the transfer process.

<Eleventh Modification (2)>
It is also possible to apply the method (C) described above.
This method has the advantage of being able to reduce the above-mentioned fees, since multiple transactions are collectively remitted.

FIG. 11-5 is a flowchart showing an example of the flow of processing executed by each device in this modified example, and shows a portion corresponding to FIG. 11-3.

After B650, when the payment account selection information is received from the terminal 20A, the control unit 61 performs bank system inter-account remittance setting processing (B680).
Specifically, by way of example and not limitation, based on the payment account selection information received from terminal 20A, in the payment account setting data of the account management data, the payment account ID associated with the transaction ID corresponding to this billing information, User A. The account ID of the sub-bank account of A (in this example, the account ID of bank B: BB001) is stored, and the remittance flag is set to "ON".

After that, the control unit 61 determines whether or not the conditions for remittance between bank accounts are met (B682).
A bank-based inter-account transfer condition may be, by way of example and not limitation, "the date and time of the bank-account transfer has arrived." The bank system inter-account remittance date and time can be set as, by way of example and not limitation, a date and time after the payment account establishment deadline and before the account transfer date, similar to the withdrawal date and time.

If it is determined that the bank system inter-account remittance condition is not met (B682: NO), the control unit 61 advances the process to B195.

On the other hand, if it is determined that the bank-system inter-account remittance condition is met (B682: YES), the control unit 61 performs the third bank-system inter-account remittance process (B660e).
This third bank system inter-account remittance process can be performed in the same procedure as the first bank system inter-account remittance process in FIG. In step B6615, the sum of the purchase amounts of the transaction IDs whose remittance flag is set to "ON" is set as the remittance amount. Then, the control unit 61 resets all the remittance flags to "OFF".

<Eleventh Modification (3)>
As in the tenth modification (3), the server 60 stores the purchase amount corresponding to the transaction information for which the user has selected to pay from the main bank account and the transaction information for which the user has selected to pay from the sub-bank account. The information of the amount including the purchase amount corresponding to is transmitted to the credit card company server 10 and may be notified to the credit card company.

In this modification, the server 60 stores payment account selection information including information on an amount (not limited, but an example of a second amount) to be paid by the user of the terminal 20 from a sub-bank account (not limited, but an example of a second account) In addition, payment account selection information is also received from the terminal 20, including information on the amount (example of a first amount, without limitation) that the user of the terminal 20 will pay from the main bank account (example of a first account, without limitation). do. Then, the server 60 shows a configuration in which the control unit 61 performs processing related to paying the amount including the first amount and the second amount from the main bank account based on the received payment account selection information.
As an example of the effect of the embodiment obtained by such a configuration, not only the second information including the information of the second amount to be paid by the second account associated with the user of the terminal, but also the first account associated with the user of the terminal After receiving the first information including the information of the first amount to be paid, based on the first information and the second information, perform processing related to paying the amount including the first amount and the second amount from the first account. It can be carried out.

Also in this case the post-payment is made by the credit card associated with the user of the terminal 20 . Then, the processing related to paying the amount including the first amount and the second amount from the main bank account of the user of the terminal 20, which is performed by the control unit 61, includes the information of the amount including the first amount and the second amount. , a process of transmitting to the credit card company server 10 (not limited to, but an example of a first server that manages credit card information) via the communication I/F 64 .
As an example of the effect of the embodiment obtained by such a configuration, the amount of money including the first amount to be paid by the first account associated with the user of the terminal and the second amount to be paid by the second account associated with the user of the terminal The information can be communicated to a user (such as a credit card company) of a first server that manages credit card information. Thereby, the user of the first server can analyze how the user uses the first account and the second account properly based on the received amount information.

<Eleventh Modification (4)>
As in the tenth modification (4), the electronic money service provider pays the user's payment amount by credit card payment, and the advance amount is withdrawn from the user's main bank account (first account) by account transfer or the like. It is also possible to
In this case, as an example and not as a limitation, it is possible to implement by applying the processes of FIGS.

In this case, the information (information to be communicated) transmitted from the server 60 to the bank server 50 of the user's main bank account can be any of the following as an example and not as a limitation.
・ Information on the first amount and information on the second amount ・ Information on the total amount of the first amount and the second amount (information on the amount to be paid from the first account)
・ Information on the total amount of the first amount and the second amount (information on the amount to be paid from the first account) and information on the second amount (information on the amount to be paid from the second account)

In this modification, the server 60 stores payment account selection information including information on an amount (not limited, but an example of a second amount) to be paid by the user of the terminal 20 from a sub-bank account (not limited, but an example of a second account) In addition, payment account selection information is also received from the terminal 20, including information on the amount (example of a first amount, without limitation) that the user of the terminal 20 will pay from the main bank account (example of a first account, without limitation). do.
Then, the server 60, as a process related to paying the amount including the first amount and the second amount from the main bank account of the user of the terminal 20, transfers the account transfer request information (=reimbursement amount) including the information of the transfer request amount (=reimbursement amount). Bank server 50 that manages the user's main bank account (not limited to, but an example of amount information including a first amount and a second amount) is sent by communication I/F 64 to bank server 50 that manages the first account. 2 servers (an example).
As an example of the effect of the embodiment obtained by such a configuration, the amount of money including the first amount to be paid by the first account associated with the user of the terminal and the second amount to be paid by the second account associated with the user of the terminal The information may be communicated to a user (such as a financial institution) of a second server that manages the first account of the user of the terminal. Thereby, the user of the second server can pay the amount based on the received information to the user of the server (electronic money service provider, etc.).

<Eleventh Modification (5)>
In the above embodiment, the bank A server 50A sends a transfer request to the B bank server 50B by transmitting information requesting withdrawal from the B bank server 50B from the server 60 to the A bank server 50A. The information is transmitted and the transfer is made from the B bank server 50B to the A bank server 50A, but it is not limited to this.

Conversely, the server 60 transmits information requesting the bank B server 50B to transfer the money to the bank A server 50A, so that the bank B server 50B transfers the money to the bank A server 50A. is also possible.

<Eleventh Modification (6)>
As in the tenth modification (5), the server user may be a financial institution such as a bank.
In this case, if the user's main bank account (first account) and sub-bank account (second account) are bank accounts of the same bank (or same bank same branch), the bank server 50 of this bank will: Transferring (transfer processing) from the sub-bank account to the main bank account is sufficient to achieve inter-account remittance.
On the other hand, if the user's main bank account and sub-bank account are bank accounts of different banks, as an example and not limitation, the bank server 50 of the bank of the sub-bank account transfers the sub-bank account to the main bank account of another bank. The remittance can be realized by performing transfer (transfer processing) to .

Also, as an example and not a limitation, a fund transfer service provider may be the user (operator) of the server.
In this case, as a non-limiting example, a fund transfer company such as the electronic money service provider described above can be the user of the server. , a chat service (chat application) can also be interposed.
(a) Configuration of electronic money service function as one function of chat application (b) Configuration of chat service function as one function of electronic money application (c) Combination of chat service function and electronic money service function A form that constitutes a composite (integrated) application with

<Other Examples Related to Tenth to Eleventh Examples>
(1) The contents described in the first to ninth embodiments and modifications corresponding to these embodiments, and the contents described in other embodiments related to the first to ninth embodiments are The tenth embodiment and the eleventh embodiment are similarly applicable. Some examples are given below.

As an example and not a limitation, when the content of the seventh embodiment is applied to the tenth embodiment, information other than the bank name and account number may be displayed on the display unit 24 of the terminal 20 as the bank account information. can.
Specifically, as a non-limiting example, it is also possible to display the balance of the user's bank account or information related thereto as information different from the bank name and account number in the bank account information. be.

<Display screen>
FIG. 12-1 is a diagram showing an example of screen transitions displayed on the display unit 24 of the terminal 20A in this embodiment.
FIG. 12-1 is a diagram showing an example of a display screen when balance information is displayed on the payment account setting screen in the electronic money application of the terminal 20. FIG.

Fig. 12-1 shows an example of a display screen of a bank account setting page (hereinafter referred to as "payment account setting screen" as appropriate) of the electronic money application. Account information (as a non-limiting example, bank name, account number, balance, etc. corresponding to the main bank account, Bank A) and sub-bank account information not linked to a credit card (as a non-limiting example, a sub-bank A bank account information display area for displaying the bank name, account number, balance, etc. corresponding to Bank B, which is the account, is configured. In this example, the bank name corresponding to Bank A, which is the main bank account "Bank A", the number "XXXXXXX" as the account number, and the number "YYYYYY Yen" as the balance. In addition, the characters "B bank" are displayed as the bank name corresponding to the B bank, which is a sub-bank account, the numbers "XXXXXXX" as the account number, and the numbers "YYYYYY Yen" as the balance.
In addition, the same information as the screen in the center of FIG. 1-31 is displayed.

(2) In the tenth and eleventh embodiments, one sub-bank account was explained, but it is also possible to have two or more sub-bank accounts. Since the processing in this case can be configured in the same manner as in the above embodiment, detailed description thereof will be omitted.

(3) In the methods of the first to ninth embodiments, each bank account that can be set as a payment account is linked to a credit card, and account transfers can be made from each bank account. Payment accounts could only be changed before the transfer took place.
However, in the inter-account remittance method of the tenth and eleventh embodiments, account transfers are made only to the main bank account, so even after account transfers are made from the main bank account, It is also possible to allow the payment account to be changed.

By way of example and not limitation, if a main bank account is set up as a payment account and a direct debit is made from the main bank account and then the payment account is changed to a sub-bank account, then the amount debited from the main bank account , can be transferred from the sub-bank account to the main bank account by inter-account transfer after the fact.

(4) In the bank method inter-account remittance described in the eleventh embodiment, instead of the server 60 requesting the bank server 50 for inter-account remittance, the terminal 20 requests the bank server 50 for inter-account remittance. You may do so.
In this case, it is possible to exclude the server 60 from the components of the communication system 1B and apply the communication system 1A of FIG. 1-1.

(5) As mentioned above, it is also possible to set the main bank account as the default payment account.
In this case, instead of having the user select a bank account to be set as a payment account from among a plurality of bank accounts, the user may be allowed to select a desired transaction for payment from a sub-bank account.
As an example and not by way of limitation, if Bank A's bank account is the main bank account and Bank B's bank account is a sub-bank account, then allow the user to select a transaction for which they wish to be paid from Bank B's bank account. . Then, for the selected transaction, the payment account can be updated to Bank B's bank account.

1 (1A, 1B) communication system 10 credit card company server 20 terminal 30 network 40 store terminal 50 bank server 60 server

Claims (25)

A program executed by a terminal,
Receiving purchase information of a product or service purchased by a user of the terminal with deferred payment by a communication unit of the terminal;
displaying the purchase information and a plurality of account information associated with a user of the terminal on a display of the terminal;
Paying for at least a portion of said purchase information with a first account associated with said first account information based on said first account information being selected from said plurality of account information by a user of said terminal. Displaying on the display unit first information about
The plurality of account information is notification information transmitted according to a period or date that allows selection of at least one account information from among the plurality of account information based on the payment deadline for the deferred payment for at least part of the purchase information. It is displayed on the display unit based on the reception by the communication unit . The program according to claim 1,
When the user of the terminal selects the first account information from among the plurality of account information and the first purchase information from among the purchase information, payment for the first purchase information is made to the first account. the first information relating to paying with is displayed on the display unit, and the user of the terminal selects second account information from among the plurality of account information and second purchase information from among the purchase information; If so, displaying on the display unit second information relating to paying for the second purchase information with a second account associated with the second account information is executed by the terminal. The program according to claim 1 or claim 2,
The purchase information is information related to the purchase history of the product or service purchased by the user of the terminal with the deferred payment. The program according to claim 3,
The first information includes information relating to paying at least a portion of the purchase history based on the first account. The program according to claim 1,
The purchase information is information about the total amount of goods or services purchased by the user of the terminal with the deferred payment. The program according to claim 5,
The first information includes information relating to paying a first amount of the total amount based on the first account selected by the user of the terminal. The program according to claim 6,
Paying a second amount of the total amount to a second account associated with the second account information based on the second account information selected from the plurality of account information by the user of the terminal. Displaying on the display unit second information about is performed by the terminal. The program according to any one of claims 1 to 7,
Displaying, on the display unit, third information indicating that at least one of the plurality of account information can be selected for the first purchase information among the purchase information is executed by the terminal. be done. The program according to claim 8,
The third information includes information on dates when at least one of the plurality of account information can be selected. The program according to claim 8 or claim 9,
When the third information is not the selectable time or date, the third information is displayed on the display section in a display mode different from the selectable time or date. The program according to any one of claims 1 to 10,
Displaying on the display unit fourth information relating to paying with a loan is performed by the terminal in response to payment of at least part of the purchase information. A program according to claim 11,
The loan is paid by a first account associated with the first account information selected by the user of the terminal. The program according to any one of claims 1 to 12,
Displaying information on the balance of the first account on the display unit is performed by the terminal. 14. The program according to claim 13,
Displaying loan-related information on the display is performed by the terminal based on the balance information. The program according to any one of claims 1 to 14,
The plurality of account information is stored in association with credit card information associated with the user of the terminal. 16. The program according to claim 15,
said deferred payment is made by said credit card;
Payment for at least a portion of the purchase information made by the credit card is made from the first account associated with the first account information selected by the user of the terminal. The program according to any one of claims 1 to 16,
The deferred payment includes payment by a set date or by a set due date. The program according to any one of claims 1 to 17,
Displaying privilege information associated with the first account information on the display unit is executed by the terminal. 19. The program according to claim 18,
Displaying the privilege information associated with the user of the terminal on the display is performed by the terminal based on the payment by the first account. The program according to any one of claims 1 to 19 ,
The notification information includes information transmitted to the terminal at set time intervals. The program according to any one of claims 1 to 20 ,
The notification information includes information transmitted to the terminal based on the number of payments included in the purchase information. The program according to any one of claims 1 to 21 ,
The notification information includes information sent to the terminal when the total amount based on the purchase information is greater than a set amount. The program according to any one of claims 1 to 22 ,
The notification information includes at least information transmitted to the terminal based on information on the balance of the first account. An information processing method for a terminal,
Receiving purchase information of a product or service purchased by a user of the terminal with deferred payment by a communication unit of the terminal;
displaying the purchase information and a plurality of account information associated with a user of the terminal on a display of the terminal;
Paying for at least a portion of said purchase information with a first account associated with said first account information based on said first account information being selected from said plurality of account information by a user of said terminal. displaying on the display unit first information about
The plurality of account information is notification information transmitted according to a period or date that allows selection of at least one account information from among the plurality of account information based on the payment deadline for the deferred payment for at least part of the purchase information. It is displayed on the display unit based on the reception by the communication unit . a terminal,
a communication unit that receives purchase information of a product or service purchased by the user of the terminal with deferred payment;
a display for displaying the purchase information and a plurality of account information associated with the user of the terminal;
Paying for at least a portion of said purchase information with a first account associated with said first account information based on said first account information being selected from said plurality of account information by a user of said terminal. A control unit that performs control to display the first information about on the display unit ,
The plurality of account information is notification information transmitted according to a period or date that allows selection of at least one account information from among the plurality of account information based on the payment deadline for the deferred payment for at least part of the purchase information. It is displayed on the display unit based on the reception by the communication unit .

Images