JP7472003B2 - Terminal, information processing method, and program - Google Patents

Description

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

Recently, services that enable management of electronic money of a terminal or a terminal user and settlement with electronic money using applications that can be executed on terminals such as smartphones are becoming more widespread. For example, Patent Literature 1 discloses a technology for settling the purchase amount of a product.

JP 2002-176671 A

Conventional technology has had the problem that it is not possible to smoothly withdraw money from a financial institution's account via an automated teller machine (ATM) or other device as an electronic money service.

The present invention was developed in consideration of these problems, and its purpose is to enable users to easily withdraw cash by using electronic money services.

The first aspect of the present invention is a terminal comprising: a first reception means for receiving registration of accounts of a plurality of financial institutions as candidates for charging electronic money; a second reception means for receiving a target amount, selecting an account of a target financial institution from among the registered accounts of the plurality of financial institutions for charging the electronic money with the target amount and withdrawing the target amount of the electronic money from an automated teller machine, and receiving a withdrawal instruction; and a display means for displaying information for charging the electronic money with the target amount from the account of the target financial institution and withdrawing the charged target amount from the automated teller machine in response to receiving the target amount, the selection of the account of the target financial institution, and the withdrawal instruction.

FIG. 1 illustrates an example of a configuration of a communication system according to an embodiment. FIG. 4 is a diagram showing an example of functions implemented by a control unit of the server according to the embodiment. FIG. 4 is a diagram showing an example of information stored in a storage unit of a server according to an embodiment. FIG. 13 is a diagram illustrating an example of payment application user registration data according to the embodiment. FIG. 11 is a diagram showing an example of affiliated bank data according to the embodiment. FIG. 4 is a diagram showing an example of a data configuration of a user management database according to the embodiment. FIG. 4 is a diagram showing an example of functions implemented by a control unit of the terminal according to the embodiment. FIG. 4 is a diagram showing an example of information stored in a storage unit of the terminal according to the embodiment. FIG. 4 is a diagram showing an example of a display screen displayed on a display unit of the terminal according to the embodiment. FIG. 4 is a diagram showing an example of a display screen displayed on a display unit of the terminal according to the embodiment. FIG. 4 is a diagram showing an example of a display screen displayed on a display unit of the terminal according to the embodiment. FIG. 4 is a diagram showing an example of a display screen displayed on a display unit of the terminal according to the embodiment. FIG. 4 is a diagram showing an example of a display screen displayed on a display unit of the terminal according to the embodiment. FIG. 4 is a diagram showing an example of a display screen displayed on a display unit of the terminal according to the embodiment. FIG. 4 is a diagram showing an example of a display screen displayed on a display unit of the terminal according to the embodiment. FIG. 4 is a diagram showing an example of a display screen displayed on a display unit of the terminal according to the embodiment. FIG. 4 is a diagram showing an example of a display screen displayed on a display unit of the terminal according to the embodiment. FIG. 13 is a diagram showing an example of a display screen displayed on a display unit of a terminal according to a modified example. FIG. 13 is a diagram showing an example of a display screen displayed on a display unit of a terminal according to a modified example. FIG. 13 is a diagram showing an example of a display screen displayed on a display unit of a terminal according to a modified example. 4 is a flowchart showing an example of a flow of a process executed by each device according to the embodiment. 4 is a flowchart showing an example of a flow of a process executed by each device according to the embodiment. 4 is a flowchart showing an example of a flow of a process executed by each device according to the embodiment. 4 is a flowchart showing an example of a flow of a process executed by each device according to the embodiment.

<Compliance with legal matters>
It should be noted that the disclosures described herein are subject to compliance with the laws of the country of implementation, such as communications secrecy, as necessary for the implementation of the disclosure.

An embodiment for implementing the method disclosed herein will be described with reference to the drawings.

[System configuration]
FIG. 1 is a diagram illustrating an example of a configuration of a communication system 1 according to an embodiment of the present disclosure.
As disclosed in FIG. 1, in the communication system 1, a server 10, terminals 20 (terminal 20A, terminal 20B, terminal 20C, ...), a bank server 40 (bank server 40A, bank server 40B, bank server 40C, ...), and ATMs 50 (ATM 50A, ATM 50B, ATM 50C, ...) are connected via a network 30.

The server 10 provides predetermined services to the terminals 20 owned by users via the network 30. Specifically, by way of example and not limitation, the server 10 provides services relating to inquiries about the account balance of the terminals 20 or users of the terminals 20, withdrawals of the account balance, deposits, and the like.
The number of terminals 20 connected to the network 30 is not limited.

The network 30 serves to connect one or more terminals 20, one or more servers 10, one or more bank servers 40, and one or more ATMs 50. In other words, the network 30 refers to a communication network that provides a connection path so that the above-mentioned various devices can be connected and then send and receive data.

One or more portions of network 30 may or may not be wired or wireless. 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 (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a cellular network, integrated service digital networks (ISDN), wireless LAN, long term evolution (LTE), code division multiple access (CDMA), Bluetooth, satellite communications, or the like, or a combination of two or more thereof. Network 30 may include one or more networks 30.

The terminal 20 (terminal 20A, terminal 20B, terminal 20C, ...) (not limited to, but an example of a terminal or information processing device) may be any terminal that can realize the functions described in each embodiment. The terminal 20 includes, not limited to, a smartphone, a mobile phone (feature phone), a computer (not limited to, but an example of, a desktop, laptop, tablet, etc.), a media computer platform (not limited to, but an example of, a cable or satellite set-top box, digital video recorder, etc.), a handheld computer device (not limited to, but an example of, a PDA (personal digital assistant), email client, etc.), a wearable device (glasses-type device, watch-type device, etc.), or other types of computers or communication platforms. The terminal 20 may also be expressed as an information processing terminal.

Because terminals 20A, 20B, and 20C have basically the same configuration, the following description will focus on terminal 20. Note that user information is information about a user associated with an account used by the user in a specific service. User information includes, by way of example and not limitation, information associated with a user, such as the user's name, user icon image, user's age, user's gender, user's address, user's hobbies and interests, and user identifier, which is input by the user or assigned by a specific service, and may be any one or a combination of these, or none of them.

The server 10 (not limited to, but an example of a server, information processing device, or information management device) has a function of providing a predetermined service to the terminal 20. The server 10 may be any device that is an information processing device that can realize the functions described in each embodiment. The server 10 includes, not limited to, a server device, a computer (not limited to, but an example of, a desktop, laptop, tablet, etc.), a media computer platform (not limited to, but an example of, a cable or satellite set-top box, digital video recorder, etc.), a handheld computer device (not limited to, but an example of, a PDA, email client, etc.), or other types of computers or communication platforms. The server 10 may also be expressed as an information processing device. When there is no need to distinguish between the server 10 and the terminal 20, the server 10 and the terminal 20 may or may not be expressed as information processing devices.

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

(1) Terminal HW Configuration FIG. 1 shows an example of the HW configuration of the terminal 20.
The terminal 20 includes a control unit 21 (CPU: central processing unit), a storage unit 28, a communication I/F 22 (interface), an input/output unit 23, a display unit 24, a microphone 25, a speaker 26, and a camera 27. The HW components of the terminal 20 are connected to each other via a bus B, for example and not for limitation. It is not essential that the HW configuration of the terminal 20 includes all components. For example and not for limitation, the terminal 20 may or may not be configured such that individual components, such as the microphone 25, the camera 27, or multiple components, are removable.

The communication I/F 22 transmits and receives various data via the network 30. The communication may be performed either wired or wirelessly, and any communication protocol may be used as long as mutual communication can be performed. The communication I/F 22 has a function of performing communication with various devices such as the server 10 via the network 30. The communication I/F 22 transmits various data to various devices such as the 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 server 10 and transmits it to the control unit 21. The communication I/F 22 may also be simply referred to as a communication unit. When the communication I/F 22 is configured with a physically structured circuit, it may also be referred to as a communication circuit.

The input/output unit 23 includes a device for inputting various operations to the terminal 20, and a device for outputting the results of processing performed by the terminal 20. The input/output unit 23 may be an integrated input unit and an output unit, or may be separate input unit and output unit, or may not be.

The input unit is realized by any one or combination of any type of device that can accept input from a user and transmit information related to the input to the control unit 21. Examples of the input unit include, but are not limited to, a touch panel, a touch display, hardware keys such as 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 realized by any one or a combination of any type of device capable of outputting the results of processing by the control unit 21. Examples of the output unit include, but are not limited to, a touch panel, a touch display, a speaker (audio output), a lens (for example, but not limited to, 3D (three dimensions) output and hologram output), a printer, etc.

The display unit 24 is realized by any one of all types of devices or a combination thereof that can display according to the display data written to the frame buffer. Examples of the display unit 24 include, but are not limited to, touch panels, touch displays, monitors (for example, but not limited to, liquid crystal displays and organic electroluminescence displays (OLEDs)), head mounted displays (HDMs), projection mapping, holograms, 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.

If the input/output unit 23 is a touch panel, the input/output unit 23 and the display unit 24 may be arranged facing each other and have approximately the same size and shape.

The control unit 21 has circuitry that is physically structured to execute functions realized by the code or instructions contained in the program, and is realized by, for example and not by way of limitation, a data processing device built into hardware. As such, the control unit 21 may or may not be described as a control circuit.

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

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

The terminal 20 stores the program P in the memory unit 28, and by executing this program P, the control unit 21 executes the processing of each unit included in the control unit 21. In other words, the program P stored in the memory unit 28 causes the terminal 20 to realize each function executed by the control unit 21. Furthermore, this program P may or may not be expressed as a program module.

The microphone 25 is used to input audio data. The speaker 26 is used to output audio data. The camera 27 is used to obtain video data.

(2) HW Configuration of Server FIG. 1 shows an example of the HW configuration of the server 10. As shown in FIG.
The server 10 includes a control unit 11 (CPU), a storage unit 15, a communication I/F 14 (interface), an input/output unit 12, and a display 13. The components of the HW of the server 10 are connected to each other via a bus B, for example and not for limitation. It is not essential that the HW of the server 10 includes all the components as the configuration of the HW of the server 10. For example and not for limitation, the HW of the server 10 may or may not be configured such that the display 13 is detachable.

The control unit 11 has circuitry that is physically structured to execute the functions realized by the code or instructions contained in the program, and is realized, for example and not by way of limitation, by a data processing device built into hardware.

The control unit 11 is typically a central processing unit (CPU), but may also be a microprocessor, a processor core, a multiprocessor, an ASIC, or an FPGA, or may not be such a unit. In this disclosure, the control unit 11 is not limited to these.

The storage unit 15 has a function of storing various programs and various data required for the operation of the server 10. The storage unit 15 is realized by various storage media such as a HDD, SSD, and flash memory. However, in this disclosure, the storage unit 15 is not limited to these. Furthermore, the storage unit 15 may or may not be expressed as a memory.

The communication I/F 14 transmits and receives various data via the network 30. The communication may be performed either wired 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 performing communication with various devices such as the terminal 20 via the network 30. The communication I/F 14 transmits various data to various devices such as the terminal 20 according to instructions from the control unit 11. The communication I/F 14 also receives various data transmitted from various devices such as the terminal 20 and transmits it to the control unit 11. The communication I/F 14 may also be simply referred to as a communication unit. When the communication I/F 14 is composed of a physically structured circuit, it may also be referred to as a communication circuit.

The input/output unit 12 is realized by a device that inputs various operations to the server 10. The input/output unit 12 is realized by any of all types of devices or a combination thereof that can accept input from a user and transmit information related to the input to the control unit 11. The input/output unit 12 is typically realized by hardware keys such as a keyboard, or a pointing device such as a mouse. Note that the input/output unit 12 may or may not include, by way of example and not limitation, a touch panel, a camera (operation input via video images), or a microphone (operation input by voice). However, in the present disclosure, the input/output unit 12 is not limited to these.

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

(3) ATM Configuration An ATM (automatic teller machine) 50 (not limiting, but an example of an automated cash dispenser) includes a control unit (CPU), a memory unit, a card reader, a deposit/withdrawal machine, an input/output unit, a display, a speaker, and a communication I/F (interface). The hardware components of the ATM 50 are connected to each other via a bus B, not limiting, but for example.

The input/output unit is realized by a device that inputs various operations for the ATM 50. The input/output unit is realized by any type of device or combination of devices that can accept input from a depositor and transmit information related to the input to the control unit. The input/output unit is typically realized by a touch panel or buttons.

The display is typically realized by a monitor (for example, but not limited to, a liquid crystal display or an OELD). In accordance with instructions from the control unit, the display shows a list of services that can be provided to depositors (for example, but not limited to, deposits, withdrawals (refunds), transfers, bankbook entries, etc.) and the operations required to provide the services. If the input/output unit is a touch panel, the input/output unit and the display may be disposed opposite each other and have approximately the same size and shape. The speaker is used to output sounds that notify the progress of operations and reaction sounds that are emitted in response to operations on the input/output unit.

The card reader reads the information recorded on the magnetic stripe of a cash card with a magnetic stripe inserted by a depositor, and transmits the information read to the control unit. The depositing and dispensing machine ejects cash stored in the ATM body to the cash removal slot of the ATM body in accordance with instructions from the control unit. The depositing and dispensing machine also accumulates cash inserted into the cash insertion slot inside the ATM body in accordance with instructions from the control unit. Note that the cash removal slot and cash insertion slot may be realized by the same device.

Note that the control unit, memory unit, and communication I/F of ATM 50 can be similar to the control unit, memory unit, and communication I/F of server 10, respectively, by way of example and not limitation, and therefore a description thereof will be omitted. Also, the ATM main body (not shown) equipped with a card reader, deposit/withdrawal machine, input/output unit, display, and speaker, and the ATM operation server (not shown) equipped with a control unit, memory unit, and communication I/F may or may not be installed as separate entities.

(4) Others The hardware configuration of the bank server 40 and the components and circuits that make up each functional unit can be configured in the same manner as the server 10 and the ATM 50, for example and not for limitation, and therefore a description thereof will be omitted.

The server 10 stores a program P in the storage unit 15, and executes this program P, causing the control unit 11 to execute the processes of each unit included in the control unit 11. In other words, the program P stored in the storage unit 15 causes the 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 applies to other devices.

In each embodiment of the present disclosure, the description will be given assuming that the CPU of the terminal 20 and/or the server 10 executes the program P to realize the present invention.
The same applies to other devices.

The control unit 21 of the terminal 20 and/or the control unit 11 of the server 10 may or may not realize each process by a CPU having a control circuit, but may also realize each process by a logic circuit (hardware) formed in an integrated circuit (IC (Integrated Circuit) chip, LSI (Large Scale Integration)) or a dedicated circuit. These circuits may or may not be realized by one or more integrated circuits, and the multiple processes shown in each embodiment may or may not be realized by one integrated circuit. In addition, LSIs may be 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 applies to other devices.

In addition, the program P (which may be, for example and not by way of limitation, a software program, computer program, or program module) of each embodiment of the present disclosure may or may not be provided in a state stored in a computer-readable storage medium. The storage medium is capable of storing the program P in a "non-transitory tangible medium." The program P may or may not be for realizing part of the functions of each embodiment of the present disclosure. Furthermore, the program P may or may not be a so-called difference file (difference program) that can realize the functions of each embodiment of the present disclosure in combination with a program P already recorded in 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 not limitation, a field programmable gate array (FPGA) or an application specific IC (ASIC)), a hard disk drive (HDD), a hybrid hard drive (HHD), an optical disk, an optical disk drive (ODD), a magneto-optical disk, a magneto-optical drive, a floppy diskette, a floppy disk drive (FDD), a magnetic tape, a solid-state drive (SSD), a RAM drive, a secure digital card, or a drive, any other suitable storage medium, or a suitable combination of two or more of these. The storage medium may be volatile, non-volatile, or a combination of volatile and non-volatile, as appropriate. It should be noted that the storage medium is not limited to these examples and may be any device or medium capable of storing the program P. Also, the storage medium may or may not be referred to as a memory.

The server 10 and/or the terminal 20 can realize the functions of the multiple functional units shown in each embodiment by reading out a program P stored in a storage medium and executing the read out program P.
The same applies to other devices.

Furthermore, the program P of the present disclosure may or may not be provided to the server 10 and/or the terminal 20 via any transmission medium capable of transmitting a program (such as a communication network or broadcast waves). The server 10 and/or the terminal 20 executes the program P downloaded via the Internet or the like, for example and not for limitation, to realize the functions of the multiple functional units shown in each embodiment.
The same applies to other devices.

In addition, each embodiment of the present disclosure may be realized in the form of a data signal in which the program P is embodied by electronic transmission.
At least a part of the processing in the server 10 and/or the terminal 20 may or may not be realized by cloud computing consisting of one or more computers.
At least a part of the processing in the terminal 20 may or may not be performed by the server 10. In this case, at least a part of the processing of each functional unit of the control unit 21 of the terminal 20 may or may not be performed by the server 10.
At least a part of the processing in the server 10 may or may not be performed by the terminal 20. In this case, at least a part of the processing of each functional unit of the control unit 11 of the server 10 may or may not be performed by the terminal 20.
Unless explicitly stated, the judgment configuration in the embodiments of the present disclosure is not essential, and a specified process may or may not be performed when the judgment condition is satisfied, or when the judgment condition is not satisfied.

The programs disclosed herein may be implemented using, by way of example and not limitation, scripting languages such as ActionScript and JavaScript (registered trademark), object-oriented programming languages such as Objective-C and Java (registered trademark), and markup languages such as HTML5.

<Example>
In recent years, applications (application software) related to network services, such as applications for electronic payments using electronic money (payment applications), applications for transferring electronic money (remittance applications), and payment applications that consolidate some or all of the functions of these applications, are becoming more widespread, and users of terminal 20 are now able to receive various services related to electronic money using these applications.

The embodiment described below is an example, not a limitation, in which a user of terminal 20 has an account at a bank (hereinafter referred to as a "bank account"), and the user performs an operation on terminal 20 and ATM 50 to withdraw a desired amount of cash from his/her bank account to ATM 50, thereby providing a service in which cash is withdrawn from ATM 50 (a service in which the user withdraws cash from ATM 50) (hereinafter also referred to as a "withdrawal service"). In the following, the business providing the withdrawal service is also referred to as the "withdrawal service business." Furthermore, the user may or may not be referred to as a depositor. Furthermore, withdrawing cash from ATM 50 through the withdrawal service is also referred to as an "ATM withdrawal."

The operator of the withdrawal service may or may not be referred to as the operator of the payment application or the operator of the server 10. The depositor's account may be an account associated with the depositor, or an account associated with the depositor's terminal 20. In the following, these are collectively referred to as the "depositor's account."

In addition, in this embodiment, various services including a withdrawal service are provided within the payment application, and the server 10 is operated and managed by a remittance service provider. In the following, as an example, the payment application is illustrated and described as being named "Payment App."

In addition, in this embodiment, by way of example and not limitation, banks affiliated with the withdrawal service provider are shown in Figure 1 as "affiliated bank B1," "affiliated bank B2," ....

In this embodiment, "electronic money" refers to electronic currency that is distinct from physical currency and that is owned by the terminal 20 or the user of the terminal 20 and is managed in a payment application. Electronic money may or may not be expressed as "electronic currency."

In addition, the "API" in this embodiment is, by way of example and not limitation, a description of the data structure when sending data to a program component and the command method when processing in the program component, which are published by the bank server 40 etc. in order to make functions related to the withdrawal service available on the server 10. As an example and not by way of limitation, this includes the data structure and command method for receiving information about a depositor's account from the bank server 40 and sending a command to transfer electronic money to the bank server 40.

<Functional configuration>
(1) Functional Configuration of the Server FIG. 2A is a diagram showing an example of functions implemented by the control unit 11 of the server 10 in this embodiment.
The control unit 11 includes, as a main functional unit, a payment application management processing unit 111, for example and not by way of limitation.

The payment application management processing unit 111 has the function of executing a payment application management process that manages data related to the payment application executed on the terminal 20 in accordance with the payment application management processing program 151 stored in the memory unit 15.

The payment application management processing unit 111 includes, as functional units, a balance inquiry service management processing unit 1111 that executes processing for providing and managing a balance inquiry service, and a withdrawal service management processing unit 1112 that executes processing for providing and managing a withdrawal service, by way of example and not limitation.

The balance inquiry service is a service that allows a depositor to inquire about the balance of his/her bank account (hereinafter referred to as "bank account balance") using a payment application.
The withdrawal service is a service that allows a depositor to withdraw (withdraw) the balance of his/her bank account in cash from an ATM 50 using a payment application.

The balance inquiry service management processing unit 1111 manages the sending and receiving of information by the balance inquiry service, for example and not for limitation. Specifically, the balance inquiry service management processing unit 1111 obtains information such as the selected bank account balance and transaction history from the bank server 40 via an API provided by the affiliated bank in response to an instruction from the terminal 20 or the account of the user of the terminal 20 identified by an identifier in the balance inquiry service, and transmits the information to the terminal 20.

The withdrawal service management processing unit 1112 manages the withdrawal of cash by the withdrawal service, for example and not for limitation. Specifically, the withdrawal service management processing unit 1112 requests the bank server 40 to transfer (account transfer) electronic money to an account via the API, in response to an instruction from the terminal 20 or the account of the user of the terminal 20 identified by the identifier, and transmits information regarding the amount to be withdrawn (withdrawn) from the server 10 to the ATM 50, causing the ATM 50 to withdraw cash.

FIG. 2B is a diagram illustrating an example of information stored in the storage unit 15 of the server 10 in this embodiment.
The memory unit 15 stores a server main processing program executed as the main processing of the server 10, as well as a payment application management processing program 151 executed as a payment application management processing, for example and not by way of limitation.
The payment application management processing program 151 includes, as a subroutine program, an affiliated bank service management processing program 1511 which is executed as a balance inquiry service management processing and a withdrawal service management processing.

The memory unit 15 also stores payment application user registration data 153, affiliated bank data 154, and a user management database 155.

The payment application user registration data 153 is registration data of the terminal 20 or the user of the terminal 20 who uses the service provided by the payment application, and an example of the data configuration is shown in FIG. 2-3.
In the payment application user registration data 153, for example and not by way of limitation, a user name, a terminal phone number, a terminal email address, a payment application ID, an authentication password, and other registration information are stored in association with each other.

The user name is the name of the user of the terminal 20 who uses the services provided by the payment application, and by way of example and not limitation, the name registered by the user of the terminal 20 when using the payment application for the first time is stored.

The terminal phone number is the phone number of the terminal 20 of the user of this username, and by way of example and not limitation, the phone number of the terminal 20 that the user of the terminal 20 first registers when using a payment application is stored.
The terminal email address is the email address of the terminal 20 of the user of this username, and by way of example and not limitation, the email address of the terminal 20 that the user of the terminal 20 first registers when using a payment application is stored.
The terminal telephone number and the terminal email address are examples of identification information for identifying the terminal 20 (hereinafter, also referred to as "terminal identification information").

The payment application ID is an ID that functions as identification information for identifying the terminal 20 or the user of the terminal 20, and is an ID that is uniquely set by the server 10 for each terminal 20 or each user of the terminal 20 that uses the payment application.

The authentication password is an authentication password that is requested to be input to the terminal 20 during the authentication process executed when using various functions provided as payment application functions on the terminal 20 of the user with this username, and as a non-limiting example, the password set by the user is stored.

Other registration information is other registration information for the user of this username, and includes, by way of example and not limitation, information such as a user icon image, which is image data of an icon used by the user in a payment application.

The above various types of user information may be stored and managed by server 10 as user information common to the payment application and other applications that server 10 can provide, or may be stored and managed by server 10 as separate user information.

The affiliated bank data 154 is data managed by affiliated banks, and an example of the data structure is shown in FIG. 2-4.
In the affiliate bank data 154, for example and not for limitation, an affiliate bank ID, an affiliate bank name, an affiliate bank server URI, and other affiliate bank information are stored in association with each other.

The affiliated bank ID is an ID that functions as identification information for identifying an affiliated bank, and is stored by the server 10 as an ID that is uniquely set for each affiliated bank.

The name of the affiliated bank is stored as the name of the affiliated bank mentioned above (for example, but not limited to, the trade name, nickname, or common name of the affiliated bank, etc.).

The affiliated bank server URI stores a uniform resource identifier (URI) including the access method and access destination to the bank server 40 managed by the affiliated bank.

The other affiliated bank information is other registration information of the affiliated bank having this affiliated bank ID, and includes, by way of example and not limitation, information such as an affiliated bank icon image, which is image data of an icon symbolizing the affiliated bank, used in a payment application, and a card design image, which is image data that mimics the appearance of a cash card of that affiliated bank.

In the following, it will be explained that there are two types of card design images: large size images and small size images. For convenience, the large size images will be referred to as "large size cash card images" and the small size images will be referred to as "small size cash card images."

In this embodiment, the server 10 manages the electronic money of the terminal 20 or the user of the terminal 20 through an electronic money account (hereinafter referred to as the "electronic money account"). The balance of the electronic money in the electronic money account is referred to as the "electronic money account balance."

In this embodiment, we will explain that there are three types of deposits and withdrawals of electronic money (more specifically, electronic money account balance) to an electronic money account: "charge," "withdrawal," and "transfer."

"Charge" means that cash is transferred to server 10 from a bank account managed by bank server 40 of a partner bank that is registered on server 10 as a bank used by the user of terminal 20, resulting in the electronic money in the electronic money account (specifically, the electronic money account balance) being replenished (increased).

A user's electronic money account managed by server 10 can be associated with one or more bank accounts of the user, and the user of terminal 20 can use, by way of example and not limitation, the bank account balance to charge (deposit) electronic money into the electronic money account. By way of example and not limitation, when a user uses terminal 20 to select "10,000 yen" as the amount to charge electronic money, server 10 adds "10,000 yen" to the user's electronic money account balance.

"Withdrawal" is a function that uses the bank account balance of a bank account managed by the bank server 40 of an affiliated bank that is registered on the server 10 as a bank used by the user of the terminal 20 to withdraw cash from an ATM 50 managed by the affiliated bank or a bank other than the affiliated bank. In this embodiment, withdrawal can also be expressed as "ATM withdrawal" or "ATM withdrawal".

An overview of the flow for making a withdrawal via electronic money will now be described. As a non-limiting example, when a user uses terminal 20 to perform an operation to withdraw "10,000 yen" from the bank account used by the user, server 10 communicates with bank server 40 to subtract "10,000 yen" from the user's bank account balance and temporarily add "10,000 yen" to the user's electronic money account balance. Server 10 then communicates with ATM 50 to have ATM 50 dispense 10,000 yen in cash and subtract "10,000 yen" from the user's electronic money account balance.

"Transfer" is a function that transfers funds via electronic money from a bank account managed by the bank server 40 of a partner bank that is registered on the server 10 as a bank used by the user of the terminal 20 to a bank account of a partner bank that is a different bank account and is registered on the server 10.

The following is an overview of the flow for achieving a transfer via electronic money. As a non-limiting example, when a user uses terminal 20 to transfer "10,000 yen" from the user's bank account to a target account, server 10 communicates with bank server 40 to subtract "10,000 yen" from the user's bank account balance and temporarily add "10,000 yen" to the user's electronic money account balance. Server 10 then communicates with bank server 40 managed by an affiliated bank that holds the target account to add "10,000 yen" to the target account balance and subtract "10,000 yen" from the user's electronic money account balance.

Money managed in a bank account can be referred to as digital money (digital currency), meaning money managed as digital information, by way of example and not limitation.

The user management database 155 is a database that accumulates management data relating to users registered in the payment application user registration data 153, and an example of the data configuration is shown in FIG. 2-5.
The user management database 155 stores user management data as management data for each payment application ID stored in the payment application user registration data 153 .

Each user management data includes, by way of example and not limitation, a payment application ID, electronic money account balance, and affiliated bank authentication data.

The electronic money account balance is the amount of the balance in the electronic money account of the user of this payment application ID.

The affiliated bank authentication data includes, by way of example and not limitation, a bank ID, a bank name, and an access token, all of which are stored in association with each other.

The bank ID is the affiliated bank ID of the affiliated bank where the user of this payment application ID has an account, and is stored as registered by the user's registration operation. Details of this registration operation will be described later.

The bank name stores the name of the affiliated bank having the above bank ID (for example, but not limited to, the affiliated bank's trade name, nickname, or alias, etc.).

The access token is authentication data issued by a bank server 40 managed by an affiliated bank having the above bank ID. In this embodiment, the server 10 is able to use the access token provided by the bank server 40 to perform the process of obtaining account balance information of the user of this payment application ID and the process of transferring electronic money from the affiliated bank account to the electronic money account between the server 10 and the bank server 40.

Note that the configuration is not limited to one access token being associated with one bank ID, but may be one in which two or more access tokens are associated with one bank ID, or may not be so. When two or more access tokens are associated with one bank ID, as a non-limiting example, an access token can be set for each purpose, such that an access token for checking account balances and an access token for transferring electronic money are associated with one bank ID. This makes it possible to allow access to the bank server 40 of the server 10 for each purpose. Also, the user can select whether or not to allow the server 10 to check account balances, and can select whether or not to allow the server 10 to transfer electronic money.

(2) Functional Configuration of the Terminal FIG. 2-6 is a diagram showing an example of functions implemented by the control unit 21 of the terminal 20 in this embodiment.
The control unit 21 includes, as a main functional unit, a payment application processing unit 211, for example and not by way of limitation.

The payment application processing unit 211 has the function of performing processing based on various functions of the payment application in accordance with the payment application program 282 stored in the memory unit 28.

FIG. 2-7 is a diagram showing an example of information stored in the storage unit 28 of the terminal 20 in this embodiment.
In the memory unit 28, for example and not limitation, a terminal main processing program 281 executed as a terminal main processing, a payment application program 282 executed as a payment application processing, and payment application data 283 are stored.
The payment application in the text means this payment application program 282. Note that the payment application may be provided as a standalone application without a messaging service (MS) function, or may be provided as a composite application with an MS function.

Payment application data 283 is data for realizing various functions of the payment application, and includes, by way of example and not limitation, payment application ID data 2831, which is data on the payment application ID.

<Display screen example>
The card registration service, the balance inquiry service, the withdrawal service, and the like in this embodiment will be described with reference to examples of display screens. In this embodiment, the terminal 20 will be described as a smartphone having a vertically long display that functions as the display unit 24.

As a non-limiting example, a smartphone has a touch panel that functions as an input unit disposed opposite the display. When an element such as an icon, button, item, or input field is displayed on the display, and a user touches a portion of the touch panel that faces the area in which the element is displayed, a program associated with the element or a subroutine of that program is executed. Hereinafter, the area of the touch panel that faces the area in which the element is displayed on the display is also referred to as the facing area. In other words, the facing area functions as a receiving means.

(1) Display Screen of Terminal Fig. 3-1 is a diagram showing an example of an application screen displayed on display unit 24 in a payment application executed on terminal 20. This application screen is an example of a screen that is displayed when a user performs an operation to start the payment application and the payment application is started.

In this embodiment, the application screen displays the application name of the payment application, "Payment App", in the title bar at the top. Below the title bar, the current position in the hierarchical menu of "Payment App" is displayed, and more specifically, the currently active top-level menu, "Wallet Main Menu", is displayed. The "Wallet Main Menu" screen displays "￥25,000" as the balance of the electronic money account managed by "Payment App", and below that, six icons are displayed corresponding to the submenus selectable from the "Wallet Main Menu", namely "Deposit", "Code Payment", "Code Reader", "Coupon", "My Card", and "Transfer".

FIG. 3-2 is a diagram showing an example of a My Card screen that is displayed when the “My Card” icon is touched on the application screen shown in FIG. 3-1.
Below the title bar, "My Cards", which is the currently active submenu, is displayed as the current location in the hierarchical menu of "Payment App". Also, to the right of "My Cards", a sorting icon (hereinafter referred to as "sort icon") is displayed. Here, as the initial state, no My Cards for cash cards are registered in the account of the user of this terminal 20.

Hereinafter, My Card for a cash card will also be referred to as a "virtual cash card." For this reason, an explanation "Tap the + mark to add a card" is displayed below "My Card" as an operation guide for the user, and instead of displaying an icon of a virtual cash card below the explanation, an icon with a "+" mark for registering a new virtual cash card is displayed. Hereinafter, this icon with a "+" mark will be referred to as the "icon for adding my card."
When two or more virtual cash cards are registered, the order of the icons of the virtual cash cards can be rearranged by touching the sort icon.

FIG. 3-3 is a diagram showing an example of a card addition screen that is displayed when the my card addition icon is touched on the my card screen shown in FIG. 3-2.
Below the title bar, the currently active submenu "Add Card" is displayed as the current position in the hierarchical menu of "Payment App". Also, to the right of "Add Card", a camera icon and a sort icon are displayed. Below "Add Card", an explanatory text "Please select the card to add" is displayed as an operation guide for the user, and below the explanatory text, a list of affiliated banks that issue addable cash cards is displayed. This list includes a plurality of column items arranged vertically so that the user can select them, and the column items display icons including the affiliated bank icon images of the affiliated banks and character strings of the names of the affiliated banks located to the right of the icons. In this embodiment, in the list, the column items of "PP Bank", "QQ Bank", "RR Bank", and "SS Bank" are arranged in alphabetical order of the affiliated bank names from the top, by way of example and not of limitation.

When the sort icon located to the right of "Add Card" is touched, the order of the column items in the list can be rearranged. By way of example and not limitation, when the sort icon is touched, the order of the column items in the list is rearranged from top to bottom in reverse alphabetical order.
The sorting index may be changed to other indices such as the Japanese alphabet or the date and time of registration in addition to the alphabet, but this is not essential.

When the camera icon located to the right of "Add Card" is touched, the camera 27 of the terminal 20 becomes usable. Then, when the user takes an image of his/her own cash card with the camera 27, the terminal 20 recognizes the affiliated bank that issued the cash card based on the image capture result and the bank name or design engraved on the cash card. Then, the terminal 20 displays, by way of example and not limitation, only the row items of the affiliated bank in a list. This allows the user to easily display in a list the row items of the affiliated bank that issued the cash card captured by the camera 27. In particular, when the list contains a large number of affiliated banks, the user does not need to manually select the desired affiliated bank from the list, thereby saving time spent by the user searching for the desired row item.

In addition, instead of using a standard camera app for the OS provided as a function of the terminal 20, a camera provided as a function of the payment application (application camera) may be used as the camera 27, or it is not necessary to do so. The same applies below.

FIG. 3-4 is a diagram showing an example of a card information input screen that is displayed when the column item "QQ Bank" is touched on the card addition screen shown in FIG. 3-3.
Below the title bar, the currently active submenu "Enter Card Info" is displayed as the current location in the "Payment App" hierarchical menu. Also, a camera icon is displayed to the right of "Add Card". Below "Enter Card Info", an explanation "Please enter the required information" is displayed as an operation guide for the user, and below that explanation, the name and icon of the affiliated bank selected by the user on the "Add Card" screen (QQ Bank as an example and not a limitation) are displayed.

Below the name and icon of the affiliated bank, a list of items that need to be entered in order to receive balance inquiry services, withdrawal services, etc. from the affiliated bank is displayed. Hereinafter, this list will also be referred to as the "input list."
The input list includes, by way of example and not limitation, seven column items arranged vertically for each item, and each column item includes an item, a help icon located to the right of the item, and an input field located to the right of the icon. In this embodiment, seven column items each including the items "branch number", "account type", "account number", "last name", "first name", "PIN", and "date of birth" are displayed in order from the top. FIG. 3-4 shows a state in which the user has input values into the input fields of the seven column items. An authentication button containing the character string "authentication" is displayed below the input list. By way of example and not limitation, when the user touches the authentication button, authentication is performed by the bank server 40 based on the information input to the input list.

When the camera icon located to the right of "Enter card information" is touched, the camera 27 of the terminal 20 becomes usable, and when the user takes an image of his/her own cash card with the camera 27, the terminal 20 recognizes the branch number, account type, account number, last name, and first name from the numbers and letters engraved on the cash card based on the image capture result. Then, by way of example and not limitation, the terminal 20 writes the recognized branch number, account type, account number, last name, and first name into the corresponding input fields in the input list. This allows information about the account of the cash card to be displayed in the input list, thereby reducing the burden of input operations on the user.
Instead of inputting such personal information, a screen for inputting the ID and password for the online banking of the affiliated bank may be displayed. In this case, when the "QQ Bank" column item is touched on the card addition screen shown in FIG. 3-3, a screen for inputting the online banking ID and password registered in advance on the affiliated bank's website or application is displayed on the display unit 24. When the user inputs the ID and password and presses the login button, authentication processing is performed.

When an image of a cash card is captured while the "Add Card" submenu shown in FIG. 3-3 is being executed, the terminal 20 may, but need not, be configured to recognize the branch number, account type, account number, surname, and first name from the numbers and letters engraved on the cash card based on the image capture result, and to automatically enter this recognized information into each of the corresponding input fields while the "Enter Card Information" submenu is being executed.

FIG. 3-5 is a diagram showing an example of a My Card screen that is displayed when the authentication button is touched on the card information input screen shown in FIG. 3-4.
The currently active submenu "My Card" is displayed below the title bar as the current position in the hierarchical menu of "Payment App". FIG. 3-5 is an application screen in which the "My Card" submenu is active, similar to the My Card screen shown in FIG. 3-2. Here, it is assumed that a virtual cash card of "RR Bank" is registered in addition to a virtual cash card of "QQ Bank". Therefore, unlike the My Card screen shown in FIG. 3-2, below the description of "Tap + to add a card", an icon of a virtual cash card of "QQ Bank" including a small-sized cash card image of QQ Bank and the name of a partner bank, an icon of a virtual cash card of "RR Bank" including a small-sized cash card image of RR Bank and the name of a partner bank, and an icon for adding a My Card are displayed. In this embodiment, these virtual cash cards are arranged in alphabetical order in a Z-shaped pattern.

When the sort icon located to the right of "My Card" is touched, the order of the registered virtual cash cards can be rearranged. By way of example and not limitation, when the sort icon is touched, the icon of the virtual cash card for "QQ Bank" and the icon of the virtual cash card for "RR Bank" are arranged in a Z-pattern in reverse alphabetical order.
The sorting index may be changed to other indices such as the Japanese alphabet or the date and time of registration in addition to the alphabet, but this is not essential.

In this way, multiple registered bank accounts are displayed on the My Card screen, allowing the user to easily understand the accounts of multiple registered financial institutions.

FIG. 3-6 is a diagram showing an example of an account details screen that is displayed when the icon of the virtual cash card of “QQ Bank” is touched on the My Card screen shown in FIG. 3-5.
Below the title bar, the currently active submenu "QQ Bank" is displayed as the current location in the hierarchical menu of "Payment App." Below "QQ Bank," an image of a virtual cash card for QQ Bank is displayed. This image includes character strings indicating the branch number, account number, bank name, account type, first and last name, and the account balance within a large-sized cash card image that resembles a cash card.
Additionally, the large cash card image includes a circular icon in the upper right corner for reloading account information.

When the user touches the image of the virtual cash card in Figure 3-6, information such as the branch number, account number, and account balance may or may not be copied to the clipboard (a memory area that can be shared between applications) of the terminal 20.

Below the image of the virtual cash card, a transaction history display box, a service provided display box, and a notice display box are displayed in this order from top to bottom. In the transaction history display box, for example, the three most recent transaction details (transaction history) are displayed in chronological order from top to bottom, with "Transfer", "Deposit" and "Withdrawal" being examples but not limitations. In addition, below the three transaction details, a graph showing the change in account balance over time is displayed.

It should be noted that instead of displaying all of "Transfer,""Deposit," and "Withdrawal," at least one of them may or may not be displayed.
Furthermore, the transaction history display box is not limited to a configuration in which the three most recent transactions are displayed, but may be configured to display the two most recent transactions or less, or the four most recent transactions or more, or may not be configured in this way.

In this way, at least one of the history of deposits to the account of the target financial institution and the history of withdrawals from the account of the target financial institution is displayed, allowing the user to check the transaction history of the account of the target financial institution.

The provided services display box displays, from top to bottom, a "charge button" for executing a charge service that transfers (charges) electronic money from the user's bank account at an affiliated bank to the user's electronic money account of this payment application ID, an "ATM withdrawal button" for executing a withdrawal service, and a "transfer button" for executing a transfer service that transfers electronic money from the user's bank account at an affiliated bank to the bank account of another bank via the user's electronic money account of this payment application ID.

In this embodiment, in a withdrawal service performed when the ATM withdrawal button is touched, the account balance displayed in the image of the virtual cash card is set as the upper limit for cash that can be withdrawn from the ATM 50. In other words, the account balance of the bank selected by the user is displayed on the display unit 24, and a withdrawal instruction with this account balance as the upper limit for withdrawal is received by the input/output unit 23.
This allows the user to check the account balance at the target financial institution, and also allows the ATM to make a withdrawal up to the account balance as an upper limit for withdrawal.

It is also possible to add a loan service to the withdrawal service, allowing cash in excess of the account balance to be withdrawn from the ATM 50, but this is not required.

In addition, to the left of each of the above buttons, a design is displayed to explain the service corresponding to that button, by way of example and not limitation. Specifically, to the left of the charge button, a design is displayed that shows electronic money being transferred from the user's bank account at the affiliated bank to the user's electronic money account for this payment application ID.

In this way, there is no need to operate the charge button, and by simply operating the ATM withdrawal button, a screen for charging electronic money and withdrawing the charged amount from the ATM 50 is displayed on the display unit 24. Therefore, the user can easily withdraw the charged amount from the ATM by simply issuing a withdrawal instruction without having to issue a separate charge instruction.

Here, to the left of the ATM withdrawal button, a design is displayed that shows cash being directly withdrawn from the user's bank account at the affiliated bank. However, in reality, as described above, the user's electronic money account is charged with an amount equivalent to the withdrawal amount from the user's bank account, and electronic money equivalent to the withdrawal amount is transferred from the electronic money account to the ATM 50, and the cash is withdrawn from the ATM 50. However, this design conceals the fact that electronic money is being transferred from the user's bank account to the user's electronic money account.
This allows the user to withdraw money from his/her bank account in cash from the ATM 50 without being aware that the money is actually being withdrawn via an electronic money account.

In addition, the charge operation is accepted by the input/output unit 23, and a button other than the charge button is displayed on the display unit 24 as a button for accepting ATM withdrawals, so that the user can recognize that withdrawals and charge are performed by different instructions.

In addition, a My Card screen (not limited to this, but an example of the first screen) for selecting a bank account is displayed on the display unit 24, and an account details screen (not limited to this, but an example of the second screen) including account information for the bank account selected on the My Card screen and at least an ATM withdrawal button is displayed on the display unit 24, so that selection of an account at the target financial institution, confirmation of account information, and withdrawal instructions can be achieved through a series of operations.

The notification box displays notifications from affiliated banks (such as, but not limited to, QQ Bank) and withdrawal service providers.

FIG. 3-7 is a diagram showing an example of a withdrawal amount input screen that is displayed when the ATM Withdrawal button is touched on the account details screen shown in FIG. 3-6.
Below the title bar, the currently active submenu "Enter withdrawal amount" is displayed as the current position in the hierarchical menu of "Payment App". Below "Enter withdrawal amount", an explanatory text "Please enter the withdrawal amount" is displayed as an operation guide for the user, and below this explanatory text, a note that withdrawals of less than 1000 yen are not possible, and an input field for the account type, account balance, and withdrawal amount (not a limitation, but an example of the target amount) are displayed in that order from top to bottom. Below the input field, a clear button and a confirm button are displayed side by side in the horizontal direction. When the clear button is touched, the amount entered in the withdrawal amount input field is erased. When the confirm button is touched, the withdrawal service proceeds with the amount entered in the withdrawal amount input field.

FIG. 3-8 is a diagram showing an example of a code reading screen that is displayed when “10,000 yen” is entered in the withdrawal amount input field on the withdrawal amount input screen shown in FIG. 3-7 and the confirmation button is touched.
Below the title bar, the currently active submenu "Read two-dimensional code" is displayed as the current position in the hierarchical menu of "Payment App". Below "Read two-dimensional code", an explanation "Please match the two-dimensional code with the frame on the screen" is displayed as an operation guide for the user, and below that explanation, the withdrawal amount (10,000 yen as an example, not a limitation) is displayed. While the "Read two-dimensional code" submenu is being executed, the camera 27 of the terminal 20 becomes usable, and the image captured by the camera 27 and a frame are displayed below the withdrawal amount.

The user adjusts the position and orientation of the terminal 20 so that the image of the two-dimensional code displayed on the display of the ATM 50 falls within the field of view of the camera 27 of the terminal 20, and then the image of the two-dimensional code is captured by the camera 27, and the user fine-tunes the position and orientation of the terminal 20 so that the captured image falls within the above-mentioned frame. The terminal authentication code issued by the server 10 is stored in this two-dimensional code. Details of the terminal authentication code will be described later.

When the image of the two-dimensional code fits within the frame, the terminal 20 analyzes the image of the two-dimensional code and acquires the terminal authentication code stored in the image of the two-dimensional code. By way of example and not limitation, when the terminal 20 has successfully acquired the terminal authentication code, the terminal 20 notifies the user that the authentication code has been successfully acquired by emitting an electronic sound, vibrating the main body of the terminal 20, or changing the video of the captured image displayed on the display unit 24 to a still image. When the user recognizes the notification from the terminal 20, the user waits until the door of the cash withdrawal port of the ATM 50 opens, and when the door of the cash withdrawal port opens, the user receives the cash (10,000 yen, by way of example and not limitation) that has been dispensed into the cash withdrawal port. By way of example and not limitation, the ATM 50 closes the door of the cash withdrawal port when the user has received the cash.

FIG. 3-9 is a diagram showing an example of an account details screen that is displayed after the withdrawal of cash from the ATM 50 is completed.
Below the title bar, the currently active submenu "QQ Bank" is displayed as the current location in the hierarchical menu of "Payment App." Figure 3-9 is an application screen in which the "QQ Bank" submenu is active, similar to the Account Details screen shown in Figure 3-6. Here, we will explain the differences from the Account Details screen shown in Figure 3-6.

The image of the virtual cash card for QQ Bank displayed below "QQ Bank" includes the text string (for example, not by way of limitation, 90,000 yen) obtained by subtracting the withdrawal amount (for example, not by way of limitation, 10,000 yen) from the original account balance amount (for example, not by way of limitation, 100,000 yen as shown in Figure 3-6) as the account balance amount.

A confirmation item display box is displayed between the image of the virtual cash card and the transaction history display box. The details of the transaction that was just carried out are displayed in the confirmation item display box. In this embodiment, the confirmation item display box displays that cash was withdrawn from the ATM, the amount withdrawn, and the account balance after the withdrawal. The confirmation item display box can be cleared by touching the icon with an x mark in the upper right corner of the box.

The contents of the transaction history display box are updated with the transaction details of the cash withdrawal that was just made, compared to the transaction history display box shown in Figure 3-6. Specifically, as an example and not a limitation, since only the most recent three transaction histories are displayed, the "Withdrawal" in the bottom row of the transaction history display box shown in Figure 3-6 is erased, and the "Transfer" in the top row and the "Deposit" in the middle row are moved and displayed in the middle and bottom rows, respectively. The transaction details of the cash withdrawal that was just made are then added to the top row. In addition, the graph showing the time series changes in the account balance is updated to reflect the results of the cash withdrawal that was just made.

The contents of the provided services display box are the same as those of the provided services display box shown in FIG. 3-6, but because the confirmation items display box is displayed, only a portion of the upper part of the provided services display box is displayed on the display unit 24.

<Processing>
4-1 to 4-4 are flowcharts showing an example of the flow of processes executed by each device in this embodiment.
These figures show, from left to right, an example of a terminal main process executed by the control unit 21 of the terminal 20, a payment application management process executed by the control unit 11 of the server 10, and a bank server main process executed by the control unit (not shown) of the bank server 40.
4-3 and 4-4 further show an example of an ATM main process executed by a control unit (not shown) of the ATM 50 on the right side of the bank server main process.
Each step in the flowchart is realized, for example and not by way of limitation, by a processor of each device reading a program from a storage unit and executing it.

Note that the flowcharts described below are merely examples of the processing steps for implementing the method of the present disclosure. Therefore, the processing for implementing the method of the present disclosure is not limited to the processing executed according to the flowcharts described below, and it is possible to omit some steps and add other steps.

First, when the user of the terminal 20 touches the "My Card" icon while the application screen shown in FIG. 3-1 is displayed on the display unit 24 of the terminal 20, the payment application processing unit 211 of the terminal 20 recognizes that the input/output unit 23 has received the operation. The payment application processing unit 211 then transmits My Card List Request Information, which includes the payment application ID read from the payment application ID data 2831 stored in the memory unit 28 and includes a request for a list of registered My Cards, to the server 10 by the communication I/F 22 (via the communication I/F 22) (A110).

When the payment application management processing unit 111 of the server 10 receives the my card list request information from the terminal 20 via the communication I/F 14, it obtains the bank ID contained in the affiliated bank authentication data from the user management data in the user management database 155 in which the payment application ID contained in the my card list request information is stored.

Here, it is assumed that the bank ID and the like are not registered in the affiliated bank authentication data in the above user management data. In this case, the payment application management processing unit 111 transmits my card list information, including the fact that there is no registered affiliated bank, to the terminal 20 via the communication I/F 14.
In addition, if a bank ID or the like is registered in the affiliated bank authentication data in the above-mentioned user management data, the payment application management processing unit 111 obtains from the affiliated bank data 154 the "affiliated bank name" associated with that bank ID and a small-sized cash card image included in "other affiliated bank information," and transmits my card list information including the bank ID, affiliated bank name, and small-sized cash card image to the terminal 20 via the communication I/F 14 (B110).

When the payment application processing unit 211 of the terminal 20 receives the My Card list information from the server 10 via the communication I/F 22, it causes the My Card list information to be displayed on the display unit 24 (A120). Specifically, by way of example and not by way of limitation, the payment application processing unit 211 recognizes that there is no registered affiliated bank based on the My Card list information, and causes the display unit 24 to display a My Card screen such as that shown in FIG. 3-2.

Next, when the user of the terminal 20 touches the add my card icon, the payment application processing unit 211 of the terminal 20 recognizes that the input/output unit 23 has received this operation. Hereinafter, the affiliated bank that the user of the terminal 20 is about to register and use is also referred to as the "affiliated bank to be added". The payment application processing unit 211 then transmits add my card request information, which includes the read-out payment application ID and includes a request for a list of my cards that can be registered, to the server 10 via the communication I/F 22 (A130).

When the payment application management processing unit 111 of the server 10 receives the my card addition request information from the terminal 20 via the communication I/F 14, it reads out the user management data in the user management database 155 in which the payment application ID included in the my card addition request information is stored. Then, the payment application management processing unit 111 identifies the bank ID that is not registered in the user management data among the affiliated bank IDs included in the affiliated bank data 154. Hereinafter, the bank ID is also referred to as the "add target bank ID". Here, as described above, since the bank ID is not registered in the user management data, all of the affiliated bank IDs included in the affiliated bank data 154 are the added target bank IDs. The payment application management processing unit 111 acquires the affiliated bank name associated with the added target bank ID and the affiliated bank icon image included in the other affiliated bank information associated with the added target bank ID from the affiliated bank data 154, and transmits the added card list information including the added target bank ID, the acquired affiliated bank name, and the acquired affiliated bank icon image to the terminal 20 via the communication I/F 14 (B120).

When the payment application processing unit 211 of the terminal 20 receives the added card list information from the server 10 via the communication I/F 22, it causes the contents of the added card list information to be displayed on the display unit 24. Specifically, by way of example and not limitation, the payment application processing unit 211 causes the display unit 24 to display a card addition screen such as that illustrated in FIG. 3-3 based on the added card list information.

When the user of the terminal 20 performs an operation of touching a column item that includes the icon and name of the affiliated bank to be added, for example, the payment application processing unit 211 of the terminal 20 recognizes that the input/output unit 23 has received the operation, and identifies the affiliated bank ID associated with the name of the affiliated bank selected by the user based on the user's operation result and the added card list information (A140).

After A140, the payment application processing unit 211 transmits the additional card selection information including the read payment application ID and the identified affiliated bank ID to the server 10 via the communication I/F 22 (A150).

When the payment application management processing unit 111 of the server 10 receives additional card selection information from the terminal 20 via the communication I/F 14, it obtains the affiliated bank server URI associated with the affiliated bank ID included in the additional card selection information from the affiliated bank data 154. Then, the payment application management processing unit 111 transmits the bank server information including the affiliated bank server URI to the terminal 20 via the communication I/F 14 (B130).

When the payment application processing unit 211 of the terminal 20 receives bank server information from the server 10 via the communication I/F 22, it causes the display unit 24 to display a card information input screen that prompts the user of the terminal 20 to input information required for authentication (authorization), such as an "account number," as shown in FIG. 3-4. When the user inputs the information required for authentication (authorization) and touches the authentication button, the payment application processing unit 211 recognizes that the input/output unit 23 has received the operation. After that, an authentication system authorization registration process is performed between the terminal 20, the server 10, and the bank server 40.

In this embodiment, the authentication system authorization registration process is performed according to the OAuth standard, by way of example and not limitation. Specifically, the payment application processing unit 211 transmits authorization request information, which includes, by way of example and not limitation, the values entered by the user, such as "account number" and "PIN", to the bank server 40 via the communication I/F 22, with the affiliated bank server URI included in the bank server information as the access destination (A160).

When the control unit of the bank server 40 receives the authorization request information from the terminal 20 via the communication I/F, it executes an authorization determination process to determine whether the user of the terminal 20 is valid based on the authorization request information (C110). Specifically, the memory unit of the bank server 40 stores, by way of example and not limitation, an account management database that accumulates management data on depositors who have accounts at the bank that manages the bank server 40. The account management database includes account management data as management data for each depositor, in addition to authentication information such as online banking IDs and passwords. Each account management data stores, by way of example and not limitation, the bank number, account type, account number, account balance and transaction history of the depositor's account, the depositor's first name, last name and date of birth, and a PIN set by the depositor in association with each other.

The control unit of the bank server 40 searches for account management data including the branch number, account type, and account number included in the authorization request information from an account management database stored in the memory unit of the bank server 40, and, as a non-limiting example, the control unit of the bank server 40 then determines that the user of the terminal 20 is legitimate if account management data including the branch number, account type, and account number exists and the surname, first name, PIN, and date of birth included in the account management data match the surname, first name, PIN, and date of birth included in the authorization request information, respectively.

Then, the control unit of the bank server 40 generates an access token. In this embodiment, by way of example and not limitation, the control unit of the bank server 40 generates a random number of a predetermined number of digits according to an algorithm for generating random numbers, and uses this as the access token. The control unit of the bank server 40 associates the access token with the account management data of the user determined to be valid and stores it in the memory unit, and transmits the access token information including the access token to the server 10 via the API by the communication I/F (C120).

When the payment application management processing unit 111 of the server 10 receives the access token information from the terminal 20 via the communication I/F 14, it stores the access token included in the access token information in the user management database 155 in association with the payment application ID of the terminal 20 or the user of the terminal 20 and the bank ID (B140). This completes the authentication system authorization registration process carried out between the terminal 20, the server 10, and the bank server 40.

In detail, in the authentication system authorization registration process, after C110, the control unit of the bank server 40 transmits to the terminal 20 authorization token information that grants access permission for a certain period of time after the authorization decision process. The terminal 20 then transmits information including the received authorization token to the server 10, and the server 10 transmits information including the received authorization token to the bank server 40. After that, C120 is executed. Details of this authentication system authorization registration process will not be explained here because the process can be performed based on the OAuth standard.

Next, the payment application management processing unit 111 of the server 10 sends my card addition success information, including information that an access token for the affiliated bank to be added has been registered and that the cash card functions of the affiliated bank to be added have been granted to the server 10, to the terminal 20 via the communication I/F 14 (B150).

When the payment application processing unit 211 of the terminal 20 receives the My Card Addition Success Information from the server 10 via the communication I/F 22, it causes the display unit 24 to display a screen indicating that the functionality of the cash card of the affiliated bank to be added has been successfully added to the server 10 based on the My Card Addition Success Information (A170).

Next, the payment application management processing unit 111 of the server 10 obtains the bank ID included in the affiliated bank authentication data from the user management data in the user management database 155 in which the payment application ID is stored. Here, it is assumed that the affiliated bank authentication data in the user management data has registered the "bank ID", "bank name" and "access token" of "RR Bank" in addition to the "bank ID", "bank name" and "access token" of "QQ Bank" newly registered by the user of the terminal 20. The payment application management processing unit 111 obtains the "affiliated bank name" associated with the bank ID from the affiliated bank data 154 and the small-sized cash card image included in "other affiliated bank information", and transmits the my card list information including the bank ID, the acquired affiliated bank name, and the acquired small-sized cash card image to the terminal 20 via the communication I/F 14 (B160).

When the payment application processing unit 211 of the terminal 20 receives the my card list information from the server 10 via the communication I/F 22, it causes the contents of the my card list information to be displayed on the display unit 24. Specifically, by way of example and not limitation, the payment application processing unit 211 causes the display unit 24 to display a my card screen such as that illustrated in FIG. 3-5 based on the my card list information (A180).

Next, when the user of terminal 20 touches the icon of the virtual cash card of the affiliated bank that they are about to use, the payment application processing unit 211 of terminal 20 recognizes that the input/output unit 23 has received this operation. Here, it is assumed that the user of terminal 20 touches the icon of the virtual cash card of "QQ Bank". The payment application processing unit 211 transmits the my card selection information, including the read-out payment application ID and the bank ID of the affiliated bank selected by the user, to the server 10 via the communication I/F 22 (A190).

When the payment application management processing unit 111 of the server 10 receives the my card selection information from the terminal 20 via the communication I/F 14, an authentication system authorization process is performed between the server 10 and the bank server 40. Specifically, the payment application processing unit 211, by way of example and not limitation, obtains an access token associated with the bank ID included in the my card selection information from the affiliated bank authentication data in the user management data in the user management database 155 in which the payment application ID included in the my card selection information is stored. The payment application management processing unit 111 also obtains an affiliated bank server URI associated with the bank ID included in the my card selection information from the affiliated bank data 154. The payment application management processing unit 111 then transmits account reference request information including the access token and including a request for information regarding the account of the user of the terminal 20 to the bank server 40 via the API via the communication I/F 14, with the affiliated bank server URI as the access destination (B170).

When the control unit of the bank server 40 receives the account reference request information from the terminal 20 via the communication I/F, it obtains, by way of example and not limitation, the branch number, account type, account number, account balance and transaction history, as well as the first and last name from the account management data associated with the access token included in the account reference request information in the account management database stored in the memory unit, and transmits the account information including these to the server 10 via the API via the communication I/F (C130). This completes the authentication system authorization process performed between the server 10 and the bank server 40.

When the payment application management processing unit 111 of the server 10 receives the account information from the bank server 40 via the communication I/F 14, it obtains, by way of example and not limitation, the branch number, account type, account number, account balance and transaction history, as well as the family name and first name from the account information. The payment application management processing unit 111 then obtains, from the affiliated bank data 154, for example, the affiliated bank name associated with the bank ID of the affiliated bank that performed the authentication system authorization process, and a large-sized cash card image included in "other affiliated bank information", and transmits the my card information, including, by way of example and not limitation, the branch number, account type, account number, account balance and transaction history, family name and first name, as well as the bank ID, affiliated bank name, and large-sized cash card image, to the terminal 20 via the communication I/F 14 (B180).

When the payment application processing unit 211 of the terminal 20 receives the My Card Information from the server 10 via the communication I/F 22, it causes the contents of the My Card Information to be displayed on the display unit 24 (A200). Specifically, the payment application processing unit 211 causes the display unit 24 to display an account details screen such as that illustrated in FIG. 3-6, based on the My Card Information, as an example and not a limitation.

Next, when the user of the terminal 20 touches the ATM withdrawal button, the payment application processing unit 211 recognizes that the input/output unit 23 has received the operation, and causes the display unit 24 to display a withdrawal amount input screen as shown in FIG. 3-7. When the user of the terminal 20 touches the confirmation button after inputting the withdrawal amount, the payment application processing unit 211 reads out the payment application ID and obtains the bank ID from the my card information received from the server 10. The payment application processing unit 211 then transmits ATM withdrawal request information including, by way of example and not limitation, the payment application ID, the withdrawal amount, and the bank ID to the server 10 via the communication I/F 22 (A210).

When the payment application management processing unit 111 of the server 10 receives ATM withdrawal request information from the terminal 20 via the communication I/F 14, an authentication system authorization process is performed between the server 10 and the bank server 40. Specifically, the payment application management processing unit 111 obtains, by way of example and not limitation, an access token associated with the bank ID included in the ATM withdrawal request information from the affiliated bank authentication data in the user management data in the user management database 155 in which the payment application ID included in the ATM withdrawal request information is stored. The payment application management processing unit 111 also obtains an affiliated bank server URI associated with the bank ID included in the ATM withdrawal request information from the affiliated bank data 154. The payment application management processing unit 111 then transmits electronic money transfer request information including the access token and the withdrawal amount included in the ATM withdrawal request information, and including a request to transfer electronic money from the user's account of the terminal 20 to the electronic money account, to the bank server 40 via the API via the communication I/F 14, with the affiliated bank server URI as the access destination (B190).

When the control unit of the bank server 40 receives electronic money transfer request information from the terminal 20 via the communication I/F, it performs electronic money transfer processing to subtract the withdrawal amount included in the electronic money transfer request information from the account balance stored in the account management data associated with the access token included in the electronic money transfer request information in the account management database stored in the memory unit, and to update the transaction history stored in the account management data by adding the current transaction details to the transaction history (C140).

Next, the control unit of the bank server 40 sends transfer completion notification information, including information indicating that the transfer of the electronic money for the withdrawal amount was successful, to the server 10 via the API through the communication I/F (C150). This completes the authentication system authorization process performed between the server 10 and the bank server 40.

When the payment application management processing unit 111 of the server 10 receives transfer completion notification information from the terminal 20 via the communication I/F 14, it recognizes based on the transfer completion notification information that the transfer of electronic money for the requested withdrawal amount has been successful, and adds the withdrawal amount to the amount of "electronic money account balance" stored in the user management data in the user management database 155 in which the payment application ID included in the ATM withdrawal request information received from the terminal 20 is stored. The payment application management processing unit 111 then transmits terminal authentication code confirmation request information, which includes a request to confirm the terminal authentication code, to the terminal 20 via the communication I/F 14 (B200).

When the payment application processing unit 211 of the terminal 20 receives terminal authentication code confirmation request information from the server 10 via the communication I/F 22, it activates the camera 27 to capture an image of the two-dimensional code displayed on the display of the ATM 50, and displays a code reading screen on the display unit 24, such as the example shown in Figure 3-8.

Meanwhile, the user of terminal 20 performs an operation on ATM 50 to withdraw cash from ATM 50. In this embodiment, the user of terminal 20 performs an operation on the input/output unit of ATM 50 to touch a button to use the withdrawal service provided by the withdrawal service provider, by way of example and not limitation. The control unit of ATM 50 recognizes that the input/output unit has received the operation (D110).

Next, the control unit of the ATM 50 transmits terminal authentication code request information, including a request for a terminal authentication code, to the server 10 via the communication I/F (D120).
As a non-limiting example, relationship information including the relationship between the withdrawal service provider and the address of the server 10 managed by the withdrawal service provider is stored in the memory unit of the ATM 50, and the control unit of the ATM 50 obtains the destination to send the terminal authentication code request information based on the relationship information and the operation content received by the input/output unit.

When the payment application management processing unit 111 of the server 10 receives the terminal authentication code request information from the ATM 50 via the communication I/F 14, it generates a terminal authentication code based on the terminal authentication code request information (B210).

Next, the payment application management processing unit 111 transmits the terminal authentication code information to the ATM 50 via the communication I/F 14 (B220).

When the control unit of the ATM 50 receives the terminal authentication code information from the server 10 via the communication I/F, it displays the terminal authentication code information on the display (D130).

Next, the payment application processing unit 211 of the terminal 20 acquires a terminal authentication code, as illustrated in FIG. 3-8. The payment application processing unit 211 then transmits terminal authentication verification information, including the read payment application ID and the acquired terminal authentication code, to the server 10 via the communication I/F 22 (A230).

When the payment application management processing unit 111 of the server 10 receives terminal authentication verification information from the terminal 20 via the communication I/F 14, it performs a terminal authentication verification process to authenticate the terminal 20 based on the terminal authentication verification information and the terminal authentication code information sent to the ATM 50. In this embodiment, by way of example and not limitation, the payment application management processing unit 111 checks whether the terminal authentication code included in the terminal authentication verification information matches the terminal authentication code stored in the image of the two-dimensional code included in the terminal authentication code information. If the payment application management processing unit 111 confirms that the two match, it determines that the terminal 20 is valid. The payment application management processing unit 111 also determines that the ATM 50 that sent the terminal authentication code information is the withdrawal destination ATM (B230).

Next, the payment application management processing unit 111 of the server 10 transmits the withdrawal request information, including a request for a cash withdrawal and the withdrawal amount, to the ATM 50 via the communication I/F 14 (B240).

When the control unit of the ATM 50 receives the withdrawal request information from the server 10 via the communication I/F, it ejects the amount of cash included in the withdrawal request information into the inside of the cash withdrawal opening of the ATM 50 based on the withdrawal request information, and opens the door of the cash withdrawal opening (D140).

The user of the terminal 20 receives the cash that has been dispensed into the cash outlet. When the control unit of the ATM 50 detects that the cash has been removed from the cash outlet, it sends a withdrawal completion notification indicating that the cash withdrawal has been completed to the server 10 via the communication I/F (D150).

When the payment application management processing unit 111 of the server 10 receives a withdrawal completion notification from the ATM 50 via the communication I/F 14, the authentication system authorization process is performed again between the server 10 and the bank server 40. Specifically, the payment application management processing unit 111 obtains an access token associated with the bank ID included in the ATM withdrawal request information received from the terminal 20 from the affiliated bank authentication data in the user management data in the user management database 155, in which the payment application ID included in the terminal authentication verification information received from the terminal 20 is stored, as an example and not a limitation. In addition, the payment application management processing unit 111 obtains an affiliated bank server URI associated with the bank ID included in the ATM withdrawal request information from the affiliated bank data 154. Then, the payment application management processing unit 111 transmits account reference request information including the access token and including a request for information regarding the account of the user of the terminal 20 to the bank server 40 via the API via the communication I/F 14, with the affiliated bank server URI as the access destination (B250).

When the control unit of the bank server 40 receives the account reference request information from the server 10 via the communication I/F, it obtains, by way of example and not limitation, the branch number, account type and account number, account balance and transaction history after electronic money transfer processing, and first name and last name from the account management data associated with the access token included in the account reference request information in the account management database stored in the memory unit, and transmits the account information including these to the server 10 via the API via the communication I/F (C160).

When the payment application management processing unit 111 of the server 10 receives account information from the bank server 40 via the communication I/F 14, it obtains, by way of example and not limitation, the branch number, account type, account number, account balance and transaction history, as well as the surname and first name from the account information, and also obtains, by way of example and not limitation, the affiliated bank name associated with the bank ID of the affiliated bank that performed the authentication system authorization process and a large-sized cash card image included in "other affiliated bank information" from the affiliated bank data 154, and transmits ATM withdrawal completion notification information including the branch number, account type, account number, account balance and transaction history, surname and first name, as well as the bank ID, affiliated bank name, and large-sized cash card image to the terminal 20 via the communication I/F 14 (B260).

When the payment application processing unit 211 of the terminal 20 receives the ATM withdrawal completion notification information from the server 10 via the communication I/F 22, it causes the contents of the ATM withdrawal completion notification information to be displayed on the display unit 24 (A240). Specifically, by way of example and not limitation, the payment application processing unit 211 causes the display unit 24 to display an account details screen such as that illustrated in FIG. 3-9 based on the ATM withdrawal completion notification information.

After A240, the payment application processing unit 211 of the terminal 20 ends the terminal main processing. After B260, the payment application management processing unit 111 of the server 10 ends the payment application management processing. After C160, the control unit of the bank server 40 ends the bank server main processing. After D150, the control unit of the ATM 50 ends the ATM main processing.

Note that the above description shows a process for "withdrawing" electronic money deposited in a user's bank account in cash from the ATM 50. In addition, the system may be configured so that cash deposited by the user in the ATM 50 is "deposited" in electronic money into the user's bank account.
A detailed description of the processing in this case will be omitted.

In addition, the configuration described here is one in which the processing step A210 is performed in the terminal 20, and then the processing steps D110 to D130 are performed in the ATM 50, but this is not limiting. The processing for A210 and the processing for D120 in the server 10 can be performed independently, so for example, the processing steps D110 to D130 in the ATM 50 may be performed first, and then the processing step A210 may be performed.

Effects of the embodiment
In this embodiment, the input/output unit 23 (not limiting, an example of a first receiving means) accepts registration of accounts of multiple banks (not limiting, an example of multiple financial institutions) as candidates for charging electronic money. The input/output unit 23 also accepts a withdrawal amount (not limiting, an example of a target amount) and accepts selection of an account of a bank (not limiting, an example of a target financial institution) for charging the withdrawal amount to electronic money from the registered accounts of the multiple banks and withdrawing the withdrawal amount of the electronic money from an ATM 50 (not limiting, an example of an automated teller machine), and a touch operation by a user on an area facing an ATM withdrawal button (not limiting, an example of a withdrawal instruction). Then, the display unit 24 displays information for charging the withdrawal amount from the account to electronic money and withdrawing the charged withdrawal amount from the ATM 50 in response to accepting the withdrawal amount, the selection of the bank account, and the touch operation by a user on an area facing the ATM withdrawal button.
This allows the user to easily withdraw cash by utilizing electronic money services.

<Modification>
Modifications of the above embodiment will now be described.

<Modification (1)>
In the above embodiment, the currency managed in an electronic money account on the server 10 is referred to as "electronic money (electronic currency)" and the currency managed in an account on the bank server 40 (bank) is referred to as "digital currency (digital currency)". However, the two may not be distinguished from each other and both may be referred to as "electronic money" or both may be referred to as "digital currency (digital currency)".

In addition, "electronic money" or "digital currency" may be either legal tender or virtual currency. Furthermore, "electronic money" or "digital currency" may or may not include cryptocurrency (crypto assets). Furthermore, virtual currency may or may not include physical currency such as coupons.

<Modification (2)>
In the above embodiment, the payment application processing unit 211 of terminal 20 is configured to include a payment application ID in the information to be sent to server 10 and transmit it to server 10, but the payment application processing unit 211 may be configured to include, instead of the payment application ID, the user name of terminal 20, the terminal telephone number of terminal 20, or the terminal email address of terminal 20 in the information to be transmitted to server 10. Even in this case, server 10 can identify the payment application ID from the information received from terminal 20, based on payment application user registration data 153.

<Modification (3)>
The display screen configurations and user interfaces described in the above embodiments are merely examples and are not limited to these.

Specifically, as an example and not by way of limitation, the selection of a bank account (account at a target financial institution) and the input of the withdrawal amount (target amount) may be performed on the same screen.
Also, as a non-limiting example, the input of the withdrawal amount (target amount) and the operation for withdrawal (withdrawal instruction) may be performed on the same screen.
Also, as a non-limiting example, the selection of a bank account (account at the target financial institution), input of the withdrawal amount (target amount), and operation for withdrawal (withdrawal instruction) may be performed on the same screen.

In this way, by way of example and not limitation, any combination of target amount, selection of an account at a target financial institution, and withdrawal instructions can be accepted on the same screen.

<Modification (4)>
In the above embodiment, a configuration has been described in which a cash card issued by a financial institution is registered in the account of a user of the terminal 20 in the server 10. However, a card that can be used for a service using electronic money or points that can be converted into electronic money may or may not be registered in the account of a user of the terminal 20. Specific examples of such services include, but are not limited to, a point service that gives points to a user, and a service that stores a deposit from a user as electronic money. Hereinafter, the above card is also referred to as an electronic money card. Specific examples of electronic money cards include, but are not limited to, a prepaid card, a point card, or a membership card. In addition, a non-financial institution that issues an electronic money card is also referred to as an issuing business.

In this modified example, the affiliated bank data 154 (see FIG. 2-4) stored in the memory unit 15 of the server 10 stores the issuing company's "business ID," "issuing company name," "issuing company server URI," and "other issuing company information" in association with each other, in the same manner as the "affiliated bank ID," "affiliated bank name," "affiliated bank server URI," and "other affiliated bank information."

The business ID is an ID that functions as identification information for identifying the issuing business, and is stored by the server 10 as an ID that is uniquely set for each issuing business.

The issuing company name stores the name of the issuing company (for example, but not limited to, the issuing company's trade name, nickname, or alias, etc.).

The issuer server URI stores a URI that includes the access method and destination to the server managed by the issuer.

"Other issuer information" is other registration information of the issuer having this issuer ID, and includes, by way of example and not limitation, information such as an issuer icon image, which is image data of an icon symbolizing the issuer, used in a payment application, and an electronic money card design image, which is image data that mimics the appearance of an electronic money card of that issuer. Electronic money card design images include, for example, large-sized images and small-sized images. Hereinafter, this large-sized image will also be referred to as the "large-sized electronic money card image," and this small-sized image will also be referred to as the "small-sized electronic money card image."

Figure 3-10 is a diagram showing an example of an application screen displayed on the display unit 24 in a payment application executed on the terminal 20. This application screen is similar to the application screen shown in Figure 3-2, and shows an example of an application screen that is displayed when the "My Card" icon is touched on the application screen shown in Figure 3-1.

In this modification, below the description "Tap + to add a card" are displayed a My Card icon for an electronic money card issued by a coffee shop with the trade name "AAA COFFEE", a My Card icon for an electronic money card issued by a bookstore with the trade name "BBB Books", and an icon for adding a My Card. Hereinafter, the My Card for an electronic money card will also be referred to as a virtual electronic money card. The icon for the virtual electronic money card of the coffee shop with the trade name "AAA COFFEE" includes a small-sized electronic money card image associated with the issuer ID of the coffee shop. The icon for the virtual electronic money card of the bookstore with the trade name "BBB Books" includes a small-sized electronic money card image associated with the issuer ID of the bookstore. In this modification, these virtual electronic money cards are arranged in a Z-pattern in alphabetical order.

When the sort icon located to the right of "My Card" is touched, it becomes possible to rearrange the order of the registered virtual electronic money cards. As a non-limiting example, when the sort icon is touched, the icon of the virtual electronic money card for "AAA COFFEE" and the icon of the virtual electronic money card for "BBB Books" are arranged in a Z-shaped pattern in reverse alphabetical order. Note that the sorting index can be changed to the industry of the business issuing the card, the Japanese alphabet, the date and time of registration, and the like, in addition to the alphabet. As a non-limiting example, if the industry of the business issuing the card is used as the sorting index, virtual cash cards issued by affiliated banks and virtual electronic money cards issued by issuers that are not financial institutions are classified.

Figure 3-11 is a diagram showing an example of an application screen similar to the application screen shown in Figure 3-3, which is displayed when the Add My Card icon is touched on the application screen shown in Figure 3-10. Below the description "Please select the card to add", a list of affiliated banks that issue addable cash cards and issuers that issue addable electronic money cards is displayed. This list includes multiple column items arranged vertically so that the user can select them, and the column items display icons including the affiliated bank icon image of the affiliated bank or the issuer icon image of the issuer, and a character string of the name of the affiliated bank or issuer located to the right of the icon. In this embodiment, the list includes, by way of example and not limitation, column items for issuers "YY Electrical Appliances" and "ZZ Miscellaneous Goods", as well as column items for affiliated banks "PP Bank", "QQ Bank", "RR Bank", and "SS Bank".

When the sort icon located to the right of "Add Card" is touched, it becomes possible to rearrange the order of column items in the list. As a non-limiting example, when the sort icon is touched, the order of column items in the list is rearranged from top to bottom by business type and alphabetically by affiliated bank name or issuing business name. Figure 3-11 shows the list after sorting. Note that the sorting criteria may be changed to other criteria such as the Japanese alphabet and registration date and time, or a combination of these criteria, in addition to business type and alphabet.

When the camera icon located to the right of "Add Card" is touched, the camera 27 of the terminal 20 becomes usable, and when the user takes an image of his/her own electronic money card with the camera 27, the terminal 20 recognizes the issuer that issued the electronic money card based on the image capture result and the issuer name or design imprinted on the electronic money card. Then, the terminal 20 displays in a list only the column items of that issuer, by way of example and not limitation. This allows the user to easily display in a list the column items of the issuer that issued the electronic money card captured by the camera 27. In particular, when the list contains a large number of column items, the time it takes for the user to search for the desired column item can be effectively shortened.

Figure 3-12 is a diagram showing an example of an application screen displayed when a virtual cash card icon for "QQ Bank" and a virtual cash card icon for "RR Bank" are added to the application screen shown in Figure 3-10.
When the sort icon located to the right of "My Card" is touched, the order of the registered virtual cash cards and virtual electronic money cards can be rearranged. By way of example and not limitation, when the sort icon is touched, these icons are arranged in a Z-pattern in alphabetical order by business type and by affiliated bank name or issuing business name. Note that the sorting index may be changed to other indices such as the Japanese alphabet and registration date and time, or a combination of these indices, in addition to the business type and alphabet.

In this modification, the input/output unit 23 (not limited to this, but an example of a fourth accepting means) accepts registration of a plurality of services related to electronic money. Then, the display unit 24 displays a list of the registered accounts of the plurality of financial institutions and the registered plurality of services on the same screen.
This allows the user to check multiple registered financial institution accounts and multiple registered services on the same screen.

In addition, this modified example improves user convenience by allowing users to sort multiple registered financial institution accounts and multiple registered services by operating the sort icon.

<Modification (5)>
In the above embodiment, a configuration was described in which the payment application processing unit 211 of the terminal 20 accepts the registration of a cash card based on user operation, but the payment application processing unit 211 may or may not be configured to accept the registration of a cash card based on information about a financial institution account registered in an application different from the payment application, or a financial institution account managed by that application.

Specifically, by way of example and not limitation, the memory unit 28 of the terminal 20 stores a household accounting application that manages the income and expenditures of the user of the terminal 20 and links with an account at a financial institution. Also, by way of example and not limitation, the memory unit 28 stores account information indicating an account through which the household accounting application links with an account at a financial institution.

The account information includes, by way of example and not limitation, the branch number, account type, account number and PIN of the account at the financial institution, as well as the user's first name, last name and date of birth. The household accounting application accesses the bank server 40 managed by the financial institution based on the account information, and obtains information including transaction details from the bank server 40 via the communication I/F 14. The household accounting application manages the income and expenditure of the user of the terminal 20 based on the obtained information including transaction details.

By way of example and not limitation, the payment application displays an icon on the application screen shown in FIG. 3-3 for making available account information of financial institutions registered in the household accounting application. When the icon is touched by the user of the terminal 20, the payment application displays the application screen shown in FIG. 3-3, retrieves the account information stored in the memory unit 28, and displays the branch number, account type, account number, last name, first name, PIN, and date of birth contained in the account information in the input fields for "branch number," "account type," "account number," "last name," "first name," "PIN," and "date of birth," respectively, in the input list. When the user of the terminal 20 touches the authentication button, authentication is performed by the bank server 40 based on the information entered in the input list.

In this modification, the payment application processing unit 211 (not limited to this, but an example of an acquisition means) acquires account information of a household accounting application in which an account at a financial institution has been registered from the storage unit 28. The input/output unit 23 accepts the registration of an account at a financial institution based on the registered account identified from the acquired account information.
This allows a financial institution's account to be easily registered as a candidate for charging electronic money based on the account information of the registered application.

Reference Signs List 1 Communication system 10 Server 20 Terminal 30 Network 40 Bank server 50 ATM

Claims (18)

A first accepting means for accepting registration of an account of a financial institution as a candidate for use in charging an electronic money account;
a second receiving means for receiving a target amount and a withdrawal instruction for charging a predetermined amount from a registered account at the financial institution to the electronic money account and withdrawing the target amount from the electronic money account through an automated teller machine;
a display means for displaying information for dispensing money from the ATM in response to receiving the dispensing instruction;
A terminal comprising: The terminal according to claim 1,
The first accepting means accepts registration of accounts of a plurality of financial institutions as candidates to be used for charging,
The second reception means receives a selection of an account of a financial institution to be used for charging.
Terminal. A terminal according to claim 1 or 2,
the display means displays a screen for realizing the predetermined amount being charged to the electronic money account from a registered account of the financial institution and the target amount being withdrawn from the ATM, without the need for a charge instruction to the electronic money account that is different from the withdrawal instruction.
Terminal. A terminal according to any one of claims 1 to 3,
the display means displays, as acceptance information for accepting the withdrawal instruction, confidential information indicating that the predetermined amount will be charged to the electronic money account from a registered account of the financial institution.
Terminal. A terminal according to any one of claims 1 to 4,
a third reception means for receiving a charge instruction to the electronic money account different from the withdrawal instruction,
the display means displays, as the acceptance information for accepting the withdrawal instruction, information different from the acceptance information for accepting the charge instruction.
Terminal. A terminal according to any one of claims 1 to 5,
the display means displays a screen including account information of the registered account at the financial institution and reception information for receiving the withdrawal instruction.
Terminal. A terminal according to any one of claims 1 to 6,
The display means displays the account balance of the registered account at the financial institution,
The second receiving means receives the withdrawal instruction with the account balance as an upper limit for withdrawal.
Terminal. A terminal according to any one of claims 1 to 7,
The display means displays at least one of a history of deposits to an account of the registered financial institution and a history of withdrawals from an account of the registered financial institution.
Terminal. A terminal according to any one of claims 1 to 8,
The display means displays the registered account of the financial institution.
Terminal. A terminal according to any one of claims 1 to 9,
A fourth accepting unit is further provided for accepting registration for a service related to electronic money,
The display means displays the registered services.
Terminal. The terminal according to claim 10,
the display means displays the registered account of the financial institution and the registered service on the same screen.
Terminal. The terminal according to claim 10,
the fourth reception means receives registrations for a plurality of services related to electronic money;
The display means displays a list of the registered services.
Terminal. The terminal according to claim 2,
the display means displays a list of the registered accounts of the plurality of financial institutions.
Terminal. A terminal according to claim 13,
A fourth accepting unit is further provided for accepting registration of a plurality of services related to electronic money,
the display means displays a list of the registered accounts of the plurality of financial institutions and the registered services on the same screen.
Terminal. A terminal according to claim 14,
the display means displays information for accepting an operation to classify the registered accounts of the plurality of financial institutions and the registered services.
Terminal. A terminal according to any one of claims 1 to 15,
The system further includes an acquisition unit for acquiring account information of a registered application for an account of a financial institution,
the first accepting means accepts registration of an account at the financial institution based on a registered account identified from the acquired account information;
Terminal. An information processing method for a terminal, comprising:
Accepting registration of an account at a financial institution as a candidate for use in charging an electronic money account by the terminal ;
receiving, by said terminal, a target amount and a withdrawal instruction for charging said electronic money account with a predetermined amount from a registered account at said financial institution and withdrawing said target amount from said electronic money account through an automated teller machine;
displaying, on the terminal , information for dispensing money from the ATM machine in response to receiving the dispensing instruction;
An information processing method comprising: On the computer,
Accepting registration of financial institution accounts as candidates for use in charging an electronic money account;
receiving a target amount and a withdrawal instruction to charge a predetermined amount from a registered account at the financial institution to the electronic money account and to withdraw the target amount from the electronic money account through an automated teller machine;
displaying information for dispensing money from the ATM in response to receiving the withdrawal instruction;
A program for executing.

Images