Information processing device, information processing method, program, and application program

Abstract

To reduce the processing burden on users of electronic payment services when they withdraw electronic value as cash. [Solution] An information processing device comprising: a receiving unit that receives a withdrawal instruction from a payment application for withdrawing the user's electronic value, stored by a payment server that implements an electronic payment service in conjunction with a payment application installed on the user's terminal device, as cash via an automated teller machine of a financial institution; an authentication unit that, upon receiving the withdrawal instruction, cooperates with the payment application and the financial institution's server to perform authentication processing of the user regarding the withdrawal; and an instruction unit that, upon successful authentication processing, instructs the financial institution's server to perform the withdrawal via the automated teller machine.

Description

Technical Field

[0001] The present invention relates to an information processing apparatus, an information processing method, a program, and an application program.

Background Art

[0002] Conventionally, a technique for improving the efficiency of cash withdrawal processing from an automated teller machine (ATM) of a financial institution has been known. For example, Patent Document 1 describes a technique in which a withdrawal reservation is made by connecting a smartphone to a net banking server and performing a predetermined operation, and then the withdrawal is executed by touching the smartphone to the ATM.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

[0006] One aspect of the present invention is an information processing device comprising: a receiving unit that receives a withdrawal instruction from a payment application for withdrawing the user's electronic value, which is stored in a payment server that realizes an electronic payment service in conjunction with a payment application installed on the user's terminal device, as cash via an automated teller machine of a financial institution; an authentication unit that, upon receiving the withdrawal instruction, cooperates with the payment application and the financial institution's server to perform authentication processing for the user; and an instruction unit that, upon successful authentication processing, instructs the financial institution's server to perform the withdrawal via the automated teller machine. [Effects of the Invention]

[0007] According to one aspect of the present invention, it is possible to provide an information processing device, an information processing method, a program, and an application program that can reduce the processing load for users of electronic payment services when withdrawing electronic value as cash. [Brief explanation of the drawing]

[0008] [Figure 1] This diagram shows an example of a configuration for implementing an electronic payment service. [Figure 2] This is a sequence diagram (part 1) illustrating the general flow of electronic payments. [Figure 3] This is a sequence diagram (part 2) illustrating the general flow of electronic payments. [Figure 4] This is a configuration diagram of the payment server 100 according to the first embodiment. [Figure 5] This figure shows an example of the contents of user information 172. [Figure 6] This figure shows an example of the contents of merchant / store information 176. [Figure 7] This figure shows an example of the top screen of a payment app 20. [Figure 8] This diagram illustrates the flow of the first method of using ATM services by a user. [Figure 9]This diagram is intended to further explain the flow of the first method of using the ATM service shown in Figure 8. [Figure 10] This diagram illustrates the flow of the second method of using ATM services by users. [Figure 11] This diagram illustrates the third method of using ATM services by users. [Figure 12] This sequence diagram shows an example of the flow of a charge balance withdrawal process executed by the payment application 20, the payment server 100, the financial institution server 200, and the ATM 210. [Figure 13] Figure 12 is a sequence diagram showing the continuation of the withdrawal process for the charge balance. [Figure 14] This sequence diagram shows an example of the flow of a bank account balance withdrawal process executed by a payment application 20, a payment server 100, a financial institution server 200, an ATM 210, and a bank server 300. [Figure 15] This is a sequence diagram showing the continuation of the withdrawal process from the bank account balance shown in Figure 14. [Figure 16] This figure shows an example of the transitions in the ATM service usage screen related to a modified example. [Figure 17] This figure shows an example of an ATM service completion screen related to a modified example. [Modes for carrying out the invention]

[0009] The following describes embodiments of the information processing apparatus, information processing method, program, and application program of the present invention with reference to the drawings. Various devices used to provide services to users or perform internal analysis, such as the "server," "management device," and "information providing device" described below, may be implemented by a distributed group of devices, and the operators of each device may be different. Furthermore, the owner of the hardware of the devices (the provider of the cloud server) and the operator that actually operates them may also be different. The application program and the payment server work together to provide an electronic payment service. In the following description, the application program will be referred to as a payment app. The electronic payment service is a service that supports payment for the purchase of goods and services at a store. A store is, for example, a physical store (real store) that exists in the real world, but may also include a virtual store for e-commerce. A virtual store may include one provided by an entity different from the operator of the electronic payment service. In that case, when settling a purchase at a virtual store, the user may be directed to the interface screen of the electronic payment service. In the electronic payment service, stores are treated as belonging to, for example, affiliated merchants (brands), and processing such as payment when a purchase is made at a store is mainly carried out between the user and the affiliated merchant. Alternatively, payment and other processing may be conducted between the user and the store.

[0010] [Electronic payment service] Figure 1 shows an example of a configuration for realizing an electronic payment service. The electronic payment service is realized with a payment server 100 at its center. The payment server 100 communicates with, for example, one or more user terminal devices 10, one or more first store terminal devices 50, one or more second store terminal devices 70, the payment server 100, the financial institution server 200, and the bank server 300 via a network NW. The network NW includes, for example, the internet, LAN (Local Area Network), wireless base stations, and provider equipment. The financial institution server 200 also communicates with the ATM 210 via the intranet within the financial institution that operates the ATM 210.

[0011] The user terminal device 10 is, for example, a portable terminal device such as a smartphone or a tablet terminal. The user terminal device 10 is a computer device having at least an optical reading function, a communication function, a display function, an input reception function, and a program execution function. In the following description, the configurations for realizing these functions are respectively referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), etc. In the user terminal device 10, the payment application 20 is executed by a processor such as a CPU, and operates to provide an electronic payment service to the user in cooperation with the payment server 100. The payment application 20 is installed in the user terminal device 10 from, for example, an application store, and controls a camera, a communication device, a touch panel, etc.

[0012] The first store terminal device 50 is installed, for example, in a store. The first store terminal device 50 is a computer device having at least a product price acquisition function, an optical reading function, a program execution function, and a communication function. The first store terminal device 50 includes a so-called POS (Point of Sale) device, and the product price acquisition function and the optical reading function may be realized by the POS device. The store code image 60 is placed in the store and is a code image such as a QR code (registered trademark) printed on a paper or plastic medium. Note that the store code image 60 may be displayed by a display placed in the store (which may be a display of a terminal device such as a smartphone).

[0013] The second store terminal device 70 is used by the operator of the franchise store. The second store terminal device 70 is a smartphone, a tablet terminal, a personal computer, etc. In the second store terminal device 70, the interface 72 for the franchise store operates. The interface 72 for the franchise store may be an app for the franchise store or a browser. The interface 72 for the franchise store accepts settings of coupons, etc. by the operator of the franchise store and transmits them to the settlement server 100. The second store terminal device 70 which is a smartphone has functions such as displaying a code image corresponding to the store code image or reading the code image displayed by the user terminal device 10 by executing the app for the franchise store.

[0014] The settlement server 100 realizes electronic settlement based on the settlement information received from the user terminal device 10 or the first store terminal device 50. The first store terminal device 50 may include a POS device and a franchise store server. In that case, the settlement information is transmitted from the POS device to the settlement server 100 via the franchise store server. In the following description, without particularly distinguishing this, it is assumed that the settlement information is transmitted from the first store terminal device 50.

[0015] FIG. 2 and FIG. 3 are sequence diagrams illustrating a rough flow of electronic settlement. There may be two patterns, pattern 1 and pattern 2, in electronic settlement.

[0016] In the case of Pattern 1 shown in Figure 2 (hereinafter referred to as User Scan), the user terminal device 10, with the payment application 20 running, decodes the store code image 60 using its optical reading function (S1). The store code image 60 contains information about the store URL (Uniform Resource Locator). This store URL is an electronic payment service domain to which information that can identify the store has been added, and is associated with the merchant ID and store ID, etc., at the payment server 100 (described later). The payment application 20 sends the first payment information, including the store URL and account ID, to the payment server 100 (S2). The payment server 100 searches for store information (described later) from the merchant ID and store ID corresponding to the store URL, obtains the merchant name and store name information (S3), and sends it to the payment application 20 (S4). The user enters the payment amount into the user terminal device 10 on the screen where the merchant name and store name are displayed (S5). The user terminal device 10 then generates second payment information, including at least the payment amount, and sends it to the payment server 100 (S6). The payment server 100 performs electronic payment based on the received second payment information (S7). The payment server 100 then sends a payment completion notification (information for displaying the payment completion screen) to the payment application 20 (S8), and the payment application 20 displays the payment completion screen (S9). If the store code image 60 is displayed on a display placed in the store, the store code image 60 may include payment amount information as well as the store URL. In this case, the procedure for the user to enter the payment amount is omitted, and the payment amount information is included in the first payment information and sent to the payment server 100. Merchant name and store name information may be included and displayed on the payment completion screen.

[0017] In the case of Pattern 2 shown in Figure 3 (hereinafter referred to as Store Scan), when the payment app 20 is launched, when a payment operation is performed in the payment app 20, when it is time for an automatic update (for example, every minute), and at other times, the payment app 20 sends a request to the payment server 100 to issue a one-time code (S11). The payment server 100 generates a one-time code (S12) and sends it to the payment app 20 (S13). The payment app 20 displays a code image such as a QR code or barcode that was generated based on the one-time code (S14). The user holds the display surface of the user terminal device 10 over the first store terminal device 50 (presents it), and the first store terminal device 50 decodes the code image using its optical reading function and obtains the one-time code, etc. (S15). Then, the first store terminal device 50 generates payment information including the one-time code, payment amount, merchant ID, store ID, etc., and sends it to the payment server 100 (S16). The payment amount information is obtained in advance by barcode scanning or manual input. Based on the received information, the payment server 100 identifies the user corresponding to the one-time code and performs the electronic payment (S17). The payment server 100 then sends a payment completion notification to the payment app 20 (S18), and the payment app 20 displays a payment completion screen (S19).

[0018] Furthermore, electronic payment may be performed using only one of the above patterns. Also, the "account ID" explained in Figure 2 may be other information that can be used as user identification information (for example, a phone number). In addition, the issuance of a one-time code may be omitted during store scanning, and the payment app 20 may display a code image generated based on the user's account ID. In that case, the payment server 100 will identify the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[0019] [Payment Server] Figure 4 is a configuration diagram of a payment server 100 according to the first embodiment. The payment server 100 includes, for example, a communication unit 110, a payment content provision unit 120, a payment processing unit 130, an information management unit 140, an information processing unit 150, and a storage unit 170. Components other than the communication unit 110 and the storage unit 170 are realized, for example, by a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuitry) such as LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), and GPU (Graphics Processing Unit), or by the cooperation of software and hardware. The program may be stored in advance on a storage device such as an HDD (Hard Disk Drive) or flash memory (a storage device equipped with a non-transient storage medium), or it may be stored on a removable storage medium such as a DVD or CD-ROM (a non-transient storage medium) and installed on the storage device when the storage medium is inserted into the drive device. The information processing unit 150 further includes a display control unit 152, a withdrawal instruction receiving unit 154, a withdrawal authentication unit 156, and a withdrawal instruction unit 158 ​​as its functional units, the details of which will be described later.

[0020] The storage unit 170 can be an HDD, flash memory, RAM (Random Access Memory), etc. The storage unit 170 may also be a NAS (Network Attached Storage) device that can be accessed by the payment server 100 via the network. The storage unit 170 stores information such as user information 172, payment content information 174, and merchant / store information 176.

[0021] The communication unit 110 is a communication interface for connecting to a network NW. The communication unit 110 is, for example, a network interface card.

[0022] The payment content provision unit 120, for example, has the functionality of a web server and provides information (content) for displaying various screens of the electronic payment service to the user terminal device 10. The payment content provision unit 120 reads the necessary content from the payment content information 174 as appropriate and provides it to the user terminal device 10. The user terminal device 10 receives various inputs from the user while the content is being played by the payment application 20 and transmits the aforementioned payment information and other data to the payment server 100.

[0023] The payment processing unit 130 performs payment processing based on payment information transmitted by the user terminal device 10 or the first store terminal device 50. The payment processing unit 130 performs payment processing while referring to the user information 172.

[0024] Figure 5 shows an example of the contents of User Information 172. User Information 172 is an example of user registration information. User Information 172 includes, for example, user URL, account ID, telephone number, password, as well as information such as email address, user ID, name, address, date of birth, registration date, charge balance, credit payment settings, credit payment limit, credit payment amount, available credit payment amount, payment method settings, bank account, credit card number, charge history information, and payment history information. The user URL is used for money transfer processing between users. When registering for a new electronic payment service, registration of a telephone number and password is mandatory. The account ID is issued to the user by the payment server 100, and the user ID is an ID that the user can set at will (or does not have to set). Similarly, the email address and name, address, and date of birth are also information that the user can set at will (or does not have to set). The registration date is the date the user registered for the electronic payment service (the date the account was created). Hereafter, the user instance (electronic payment account) to which this information is associated will be referred to as an account.

[0025] The charge balance is information indicating the balance of electronic money set by the user by sending money to their account in advance. Methods of sending money include sending from an ATM (Automatic Teller Machine) of a designated provider (bank) and sending from a registered bank account. The credit payment setting indicates whether or not the user has completed the settings to enable electronic payments by credit card, and is set to either "Completed" or "Not Completed". The credit payment limit is the monthly limit for credit payments, the credit payment amount is the amount already used for credit payments in the current month, and the available credit payment amount is the amount available for credit payments in the current month, calculated by subtracting the credit payment amount from the credit payment limit. While the diagram shows only one credit payment limit, in reality there are also daily limits, and the lower of these may be set as the credit payment limit. Further details on credit payments will be described later. The payment method setting indicates whether the user will use electronic payment with the charge balance or payment by credit card at that time. The bank account and credit card numbers, respectively, are information (account number, card number) of a bank account or credit card number that can be used to deposit funds into the electronic payment service. The charge history information is a record of when the user has previously sent money to the electronic payment service to increase the charge balance. The payment history information shows the details of each payment made by the user (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.). The charge balance is an example of "electronic value" in the scope of the patent claims.

[0026] Figure 6 shows an example of the contents of the merchant / store information 176. The merchant / store information 176 includes, for example, a first table 176A in which the merchant ID and store ID are associated with the store URL, a second table 176B in which the merchant name and sales amount (as described above) are associated with the merchant ID, and a third table 176C in which the store name is associated with the store ID. In addition to this information, the merchant / store information 176 may also include information such as the merchant or store category, the store's location, and payment patterns.

[0027] The Information Management Unit 140 manages user information 172 and affiliated store / store information 176 based on information obtained from the user terminal device 10 and the second store terminal device 70. The Information Management Unit 140 performs operations such as adding, editing, and deleting new records for user information 172 and affiliated store / store information 176.

[0028] [Electronic payment] When the payment processing unit 130 obtains payment information from the user terminal device 10 or the first store terminal device 50, it refers to the user information 172 to obtain the user's "payment method setting". For users whose "payment method setting" is set to "charge balance", the payment processing unit 130 performs electronic payment as follows: For example, the payment processing unit 130 performs electronic payment by decreasing the charge balance, which is managed in association with the user ID, and increasing the value of the merchant's sales proceeds item. For example, the value of the merchant's sales proceeds item is not used as electronic money itself, but rather the amount corresponding to the value of the sales proceeds item is transferred to the bank account in a cycle according to the agreement between the merchant and the electronic payment service.

[0029] The payment processing unit 130 performs electronic payment as follows for users whose "settings information" is set to "credit payment". Credit payment is a payment method in cooperation with a credit card company, which is a separate entity from the electronic payment service operator. The electronic payment service operator acts as the donor and allows electronic payment within the credit limit, without relying on the charge balance. In order to use the credit payment service, users may be required to obtain a credit card provided by the electronic payment service operator. The amount used by credit payment is settled in a lump sum for the month on the payment date of the following month, for example, by withdrawal from a bank account. In this case, the payment processing unit 130 performs a provisional settlement by adding the settlement amount to the amount used by credit payment and subtracting the same amount from the available credit payment limit. When the closing date arrives, it processes the payment for the current month to be withdrawn on the payment date of the following month as described above, or requests the credit card company operator to perform the said process. If the settlement amount exceeds the available credit payment limit at the time of provisional settlement, an error notification is sent back to the payment app 20.

[0030] [Top screen] Figure 7 shows an example of the top screen of the payment app 20. The top screen displays a code image CI. The code image CI includes, for example, barcodes and QR codes. Next to the code image CI is a toggle switch SW for switching between electronic payment using the charged balance or electronic payment using credit. Note that "switch" and "button" are GUIs (Graphical User Interfaces) implemented in cooperation with the touch panel. In Figure 7, "Credit" is displayed, which means that the setting is to perform electronic payment using credit. The user can switch between electronic payment using the charged balance or electronic payment using credit by, for example, swiping the toggle switch SW. The top screen also includes an operation area OA, transition buttons TB1 and TB2. The operation area OA is equipped with buttons that instruct major operations in electronic payment, such as a button to instruct scanning (starting user scanning), a button to send the charged balance to other users, a button to display points earned by the user, and a button to display the history of electronic payments performed by the user. When the transition button TB1 is pressed, the user transitions to a payment screen displaying the code image used for electronic payment and the available balance. When the transition button TB2 is pressed, the user transitions to a screen displaying the available balance for either balance payment or credit payment. In Figure 7, since electronic payment using the charged balance is set, when the transition button TB2 is pressed, the available balance for balance payment is displayed.

[0031] At the bottom of the operating area OA, for example, a group of buttons (switches) M1, M2, ... for launching mini-applications are displayed. A mini-application is an application that operates using the payment application 20 as a platform and provides some kind of service. The service provider develops the mini-application by referring to the SDK (Software Development Kit), which consists of application development programs and technical documents provided by the administrator of the payment application 20. A mini-application is an application that operates when the payment application 20 is running. For example, when the payment application 20 is installed, some or all of the mini-application may be installed, or some or all of the mini-application may be installed from the service server corresponding to the mini-application. For example, when a mini-application is launched, it accesses a service server (not shown) that provides the service corresponding to the mini-application, and the mini-application and the service server cooperate to provide the service to the user. In this case, the service server may be the payment server 100 itself, or it may be an external server different from the payment server 100. In Figure 7, as an example, buttons M1 for a mini-app that provides a function to view information about coupons offered by participating merchants, and buttons M2 for a mini-app that provides a function to use the ATM service described later are displayed. However, buttons for launching various types of mini-apps may be displayed, such as an investment app for managing the charge balance or a payment app for paying public transportation fares. Furthermore, when the wallet button WA located at the bottom of the operation area OA is operated, the user transitions to the wallet screen, which displays the user's asset status in the electronic payment service. The wallet screen displays, for example, the user's charge balance and available deferred payment amount, as well as a list of electronic payment history information in chronological order.

[0032] [ATM Service] As explained above, users can deposit funds from their registered bank account into the electronic payment service to top up their balance and then make electronic payments. However, depending on the user's situation, it may be necessary to withdraw the electronic value, such as the balance deposited into the electronic payment service, as cash (for example, when a user uses a physical store that only accepts cash payments). Therefore, it is preferable for the electronic payment service to be integrated with financial institutions that have ATMs, enabling users to withdraw cash via ATMs. Conversely, it is preferable for users to be able to top up their balance using an ATM when depositing funds into the electronic payment service. The ATM service in this embodiment satisfies these various user needs.

[0033] [First method of using ATM services] Figure 8 is a diagram illustrating the flow of the first method of using the ATM service by a user. Figure 8 mainly shows the actions performed by the user to use the ATM service and the flow of the display screen of the payment application 20. First, in step 1, the user visits the ATM 210, performs the operation to display a code image, and presses the "Scan" button on the top screen of Figure 7. As a result, the ATM 210 displays a code image to start the ATM service, and the payment application 20 enters scan mode. Next, in step 2, the user uses the payment application 20 to scan the code image displayed by the ATM 210. When the payment application 20 scans the code image, it sends information about the scanned code image (hereinafter referred to as code image information) to the payment server 100.

[0034] When the payment server 100 receives code image information from the payment app 20, it identifies the financial institution operating the ATM and the user associated with the received code image information. The payment server 100 then sends the information necessary to display the ATM service usage screen (e.g., charge balance, bank account balance, etc.) to the identified user's payment app 20. As a result, in step 3, the payment app 20 displays the ATM service usage screen based on the information received from the payment server 100.

[0035] The ATM service screen includes, for example, area A1 for providing services related to the charge balance of the electronic payment service, area A2 for providing deposit and withdrawal services for bank accounts registered with the electronic payment service by the user, and area A3 for providing cash advance services using a credit card registered with the electronic payment service by the user. Area A1 includes, for example, button B1 for charging (depositing) the charge balance via ATM 210, and button B2 for withdrawing from the charge balance via ATM 210. Area A2 includes, for example, button B3 for depositing into a bank account balance via ATM 210, and button B4 for withdrawing from a bank account balance via ATM 210. Area A3 includes, for example, button B5 for repaying money borrowed from the cash advance service via ATM 210, and button B6 for borrowing from the cash advance service via ATM 210. Here, the cash advance service may be either a cash borrowing service attached to a credit card with a shopping function, or a cash borrowing service using a card without a shopping function (so-called card loan). Furthermore, users do not necessarily need to possess a physical credit card or card to use the cash advance service; they only need to be registered with the electronic payment service as a user of the cash advance service so that the display control unit 152 can make a determination. The bank account or financial institution providing the cash advance service may be the same institution (or an affiliated institution) as the electronic payment service operator, or it may be an unrelated third-party institution. When the user presses any of these buttons B1 to B6, the payment app 20 transitions to the service corresponding to the pressed button. In the following explanation, it is assumed that the user pressed button B2.

[0036] Although the ATM service usage screen in Figure 8 includes usage screens for all three services mentioned above, the ATM service usage screen may include only a portion of these services depending on whether the user has registered a bank account and a credit card. More specifically, when the display control unit 152 receives code image information from the payment application 20, it refers to the user information 172 to determine whether the user has registered a bank account and a credit card. If the display control unit 152 determines that the user has a bank account, it causes the payment application 20 to display area A2 for providing the bank account deposit and withdrawal services. If the display control unit 152 determines that the user has registered a credit card, it causes the payment application 20 to display area A3 for providing the cash advance service. Therefore, for example, if the user has not registered either a bank account or a credit card, the display control unit 152 causes the payment application 20 to display only area A1 on the ATM service usage screen for providing services related to the charge balance of the electronic payment service. Furthermore, in another embodiment, if the electronic payment service also provides securities services, the ATM service usage screen in Figure 8 may also include a usage screen for deposit and withdrawal services to and from a securities account. Here, securities services refer to services that enable the buying and selling of various financial products (stocks, bonds, investment trusts, etc.) using cash deposited into a securities account. When an electronic payment service provides securities services, the charge balance may be used as the securities account. The processing related to deposit and withdrawal services to and from a securities account is the same as the processing related to deposit and withdrawal services to and from a bank account.

[0037] When a user presses button B2, the payment application 20 sends instruction information to the payment server 100 instructing the user to use the ATM withdrawal service to withdraw funds from their charged balance via ATM 210. When the withdrawal instruction receiving unit 154 receives this instruction information, the withdrawal authentication unit 156 works in cooperation with the payment application 20 and the financial institution server 200 to perform user authentication processing for the withdrawal. If the authentication process is successful, the withdrawal instruction unit 158 ​​instructs the financial institution server 200 to perform the withdrawal of the charged balance via ATM 210. When the financial institution server 200 receives the withdrawal instruction, it instructs the ATM 210 to perform the withdrawal. The details of the authentication process are described below.

[0038] Figure 9 is a diagram illustrating the continuation of the flow of the first method of using the ATM service shown in Figure 8. The process shown in Figure 9 is executed, for example, after the user presses button B2 on the ATM service screen shown on the right side of Figure 8.

[0039] On the ATM service screen, when the user presses button B2, in step 4, the withdrawal authentication unit 156 sends and displays the company number to the payment application 20. After the user confirms the company number displayed on the payment application 20, they enter the company number on the ATM 210 screen. Upon receiving the company number, the ATM 210 sends the company number to the financial institution server 200. The financial institution server 200 calls a transaction inquiry API (application programming interface) for inquiring about a withdrawal transaction to the server of the company identified by the company number (i.e., in this case, the payment server 100), using parameters such as transaction serial number, account date, processing date and time, ATM number, and code image information. After receiving the API call, the withdrawal authentication unit 156 sends an authentication code to the payment application 20.

[0040] As a result, in step 5, the payment app 20 receives the authentication code, and the user, having confirmed the company number displayed on the payment app 20, enters the authentication code and withdrawal amount on the ATM 210 screen. Upon receiving the authentication code and withdrawal amount, the ATM 210 sends the authentication code and withdrawal amount to the financial institution server 200. The financial institution server 200 calls the payment server 100 to execute the withdrawal transaction, using parameters such as transaction serial number, processing date and time, customer number, transaction type, ATM number, authentication code, and withdrawal amount. The withdrawal authentication unit 156 determines that the authentication process was successful if the entered authentication code is correct. If the authentication process is determined to be successful, the withdrawal instruction unit 158 ​​instructs the financial institution server 200 to execute the withdrawal of the charge balance via the ATM 210, and upon receiving the withdrawal instruction, the financial institution server 200 instructs the ATM 210 to execute the withdrawal. The withdrawal instruction unit 158 ​​simultaneously deducts the user's withdrawal amount (and any fees, if applicable) from the user's charge balance.

[0041] As a result, in step 6, the withdrawal instruction unit 158 ​​notifies the payment app 20 of withdrawal completion information indicating that the withdrawal has been completed, and the payment app 20 displays the ATM service usage completion screen. The ATM service usage completion screen includes, for example, the amount deducted from the user's charge balance (10,100 yen in Figure 9) and its breakdown (the actual amount withdrawn from the ATM (10,000 yen in Figure 9) and the fee deducted from the charge balance (100 yen in Figure 9)). Figure 9 shows an example where the user enters 10,000 yen as the withdrawal amount into the ATM 210, and accordingly, 10,110 yen, including a 100 yen fee, is deducted from the charge balance. This completes the first method of using the ATM service.

[0042] [Second method of using ATM services] Figure 10 is a diagram illustrating the flow of the second method of using the ATM service by a user. First, in step 1, the user visits ATM 210, performs the operation to display a code image, and presses the "ATM Service" button M2 on the top screen of Figure 7. As a result, in step 2, ATM 210 displays a code image to start the ATM service, and the payment application 20 displays the ATM service usage screen shown in Figure 8. In other words, in the second method of using the ATM service, the user can reach the ATM service usage screen more quickly than in the first method of use. Next, in step 3, the user uses the payment application 20 to scan the code image displayed by ATM 210. When the payment application 20 scans the code image, it sends the scanned code image information to the payment server 100. The following flow is the same as steps 4 to 6 explained in Figure 9, so the explanation is omitted.

[0043] [Third way to use ATM services] Figure 11 is a diagram illustrating the flow of the third method of using the ATM service by a user. First, in step 1, the user visits ATM 210, performs the operation to display a code image, and presses the "Wallet" button WA on the top screen of Figure 7. As a result, in step 2, ATM 210 displays a code image to start the ATM service, and the payment application 20 displays the wallet screen showing the user's asset status in the electronic payment service.

[0044] On the wallet screen, when the user presses the withdrawal / transfer button B7 to instruct the withdrawal or transfer of the charged balance, in step 3, the payment app 20 displays a selection screen instructing the user to withdraw the charged balance from an ATM or transfer it to a bank. The selection screen includes, for example, a button B8 to instruct the user to withdraw the charged balance from an ATM and a button B9 to instruct the user to transfer the charged balance to a bank account. On the selection screen, when the user presses the withdrawal button B8, the payment app 20 enters scan mode, and in step 4, the user uses the payment app 20 to scan the code image displayed by the ATM 210. After scanning the code image, the payment app 20 sends the scanned code image information to the payment server 100. The following steps are the same as steps 4 to 6 explained in Figure 9, so the explanation is omitted.

[0045] Thus, according to this embodiment, the payment application 20 provides users with multiple methods (channels) for using ATM services. This improves the convenience for users when using ATM services.

[0046] [Flow of ATM withdrawal process for charged balance] Figure 12 is a sequence diagram showing an example of the flow of a charge balance withdrawal process executed by the payment application 20, the payment server 100, the financial institution server 200, and the ATM 210. The sequence diagram shown in Figure 12 shows, as an example, the flow when a user withdraws their charge balance via ATM 210 using the first method of using the ATM service shown in Figure 8.

[0047] First, the user visits ATM 210 and performs the operation to display a code image (S10). ATM 210 displays a code image accordingly (S12). After the user confirms the code image and scans it with the payment app 20, the payment app 20 sends the scanned code image information to the payment server 100 (S16). Upon receiving the code image information, the payment server 100 determines the menu items to be displayed on the ATM service usage screen according to whether the user's bank account and credit card associated with the code image information are registered, and instructs the payment app 20 to display the ATM service usage screen (S18).

[0048] The payment app 20 displays the ATM service usage screen in response to the display instruction (S20). When the user performs an instruction operation to withdraw the charged balance from the ATM on the ATM service usage screen displayed on the payment app 20 (for example, pressing button B2 in Figure 8) (S22), the payment app 20 registers the code image information with the payment server 100 (S24), and the payment server 100 sends the company number to the payment app 20 accordingly (S26). The payment app 20 displays the received company number (S28), and the user enters the confirmed company number into the ATM 210 (S30). The ATM 210 sends the entered company number to the financial institution server 200 (S32), and the financial institution server 200 requests an encryption key for the subsequent transaction from the server of the company associated with the entered company number (i.e., the payment server 100) (S34).

[0049] When the settlement server 100 receives a request for an encryption key, it sends the encryption key to the financial institution server 200 (S36). The financial institution server 200 uses the received encryption key to call the transaction inquiry API of the settlement server 100 (S38). In response to the call to the transaction inquiry API, the settlement server 100 sends a response (including the management number of the withdrawal transaction) to the financial institution server 200 (S40). Upon receiving the response, the financial institution server 200 further sends a response to the ATM 210 (S42). In response, the ATM 210 displays an authentication code input screen (S44).

[0050] Figure 13 is a sequence diagram showing the continuation of the withdrawal process for the charge balance shown in Figure 12. In S40 of Figure 12, the settlement server 100 sends a response to the financial institution server 200 and an authentication number to the settlement application 20 (S46). The settlement application 20 displays the received authentication number (S48), and the user enters the confirmed authentication number into the ATM 210 (S50). Next, the ATM 210 displays a withdrawal amount input screen (S52), and the user enters the desired withdrawal amount into the ATM 210 (S54).

[0051] ATM210 transmits the entered authentication number and withdrawal amount to financial institution server 200 (S56), and financial institution server 200 calls a withdrawal API to settlement server 100, including the said authentication number and withdrawal amount (S58). If the authentication number is correct and the entered withdrawal amount is less than or equal to the charge balance, settlement server 100 sends a response to financial institution server 200 instructing the withdrawal (S60), and financial institution server 200, upon receiving the response, further sends a response to ATM210 (S62). In response, ATM210 performs the withdrawal (S64).

[0052] In step S60 of Figure 13, the payment server 100 sends a response to the financial institution server 200 and a withdrawal completion notification to the payment application 20 (S66). The payment application 20 displays the received withdrawal completion notification (for example, the screen in step 6 of Figure 6). This completes the processing in this sequence diagram.

[0053] [Flowchart for ATM deposits and withdrawals of bank account balances] Figure 14 is a sequence diagram showing an example of the flow of bank account balance deposit and withdrawal processing executed by the payment application 20, payment server 100, financial institution server 200, ATM 210, and bank server 300. The sequence diagram in Figure 14 shows, as an example, the flow when a user presses button B4 on the ATM service usage screen shown in step 3 of Figure 8 to deposit or withdraw bank account balance via ATM 210. In the following, processes similar to those in the sequence diagrams of Figures 12 and 13 will be described using the same reference numerals.

[0054] First, the user visits ATM 210 and performs the operation to display a code image (S10). ATM 210 displays a code image accordingly (S12). After the user confirms the code image and scans it with the payment app 20, the payment app 20 sends the scanned code image information to the payment server 100 (S16). Upon receiving the code image information, the payment server 100 determines the menu items to be displayed on the ATM service usage screen according to whether the user's bank account and credit card associated with the code image information are registered, and instructs the payment app 20 to display the ATM service usage screen (S18).

[0055] The payment app 20 displays the ATM service usage screen in response to the display instruction (S20). When the user performs an instruction operation to deposit or withdraw money from a bank account balance at an ATM on the ATM service usage screen displayed on the payment app 20 (for example, pressing button B4 in Figure 8) (S22), the payment app 20 registers the code image information with the bank server 300 via the payment server 100 (S24), and the bank server 300 sends the company number to the payment app 20 via the payment server 100 in response (S26). The payment app 20 displays the received company number (S28), and the user enters the confirmed company number into the ATM 210 (S30). The ATM 210 sends the entered company number to the financial institution server 200 (S32), and the financial institution server 200 requests an encryption key for the subsequent transaction from the server of the company associated with the entered company number (i.e., the bank server 300) (S34).

[0056] When the bank server 300 receives a request for an encryption key, it sends the encryption key to the financial institution server 200 (S36). The financial institution server 200 uses the received encryption key to call the transaction inquiry API of the bank server 300 (S38). In response to the call to the transaction inquiry API, the bank server 300 sends a response (including the management number of the deposit / withdrawal transaction) to the financial institution server 200 (S40). Upon receiving the response, the financial institution server 200 further sends a response to the ATM 210 (S42). In response, the ATM 210 displays the deposit / withdrawal amount input screen (S44).

[0057] Figure 15 is a sequence diagram showing the continuation of the bank account balance deposit and withdrawal processing flow shown in Figure 14. When the ATM 210 displays the deposit and withdrawal amount input screen, the user enters the desired deposit and withdrawal amount into the ATM 210 (S54). The ATM 210 sends the entered deposit and withdrawal amount to the financial institution server 200 (S56), and the financial institution server 200 calls the deposit and withdrawal API including the deposit and withdrawal amount to the bank server 300 (S58). In the case of a withdrawal, if the entered withdrawal amount is less than or equal to the account balance, the bank server 300 sends a response to the financial institution server 200 instructing the withdrawal (S60), and the financial institution server 200, upon receiving the response, further sends a response to the ATM 210 (S62). In response, the ATM 210 performs the withdrawal (S64). On the other hand, in the case of a deposit, the user deposits banknotes from ATM 210, and the bank server 300 adds the deposited amount to the account balance.

[0058] In step S60 of Figure 15, the bank server 300 sends a response to the financial institution server 200 and a withdrawal completion notification to the payment application 20 (S68). The payment application 20 displays the received withdrawal completion notification (for example, the screen in step 6 of Figure 6). This completes the processing in this sequence diagram.

[0059] As shown in the sequence diagrams in Figures 13 to 15, users can use a single payment application 20 to deposit and withdraw funds from their electronic payment service balance, or to deposit and withdraw funds from their bank account balance (securities account balance) at a financial institution. In particular, while deposits and withdrawals from bank account balances at financial institutions have traditionally been performed using dedicated applications or mini-applications provided by the financial institution, this embodiment allows for the use of the electronic payment application 20 to deposit and withdraw funds from bank account balances at financial institutions, thereby further improving convenience for users.

[0060] [Differentiation] The above embodiment assumes that the electronic payment service only considers the charge balance as electronic value that can be withdrawn from an ATM. However, in practice, electronic payment services may manage not only a single type of electronic value but also multiple types of electronic value separately for each user, and make these multiple types of electronic value available for payment. In such cases, it is preferable for users of the electronic payment service to specify the withdrawal amount individually from the multiple types of electronic value and withdraw it from an ATM. In this modified example, it is assumed that the electronic payment service manages, as an example, the charge balance that the user charges via their bank account and the charge balance (salary) that the organization, such as the company where the user works, charges as the recipient of their salary. In other words, the user information 172 in Figure 2 includes "charge balance" and "charge balance (salary)".

[0061] Figure 16 shows an example of the transition of the ATM service usage screen in a modified example. In Figure 16, the screen on the left is the same as the ATM service usage screen in step 3 shown in Figure 8. When the user presses button B2 on the screen on the left, the display control unit 152 displays an input screen to the payment application 20 for entering the type and amount of the charge balance to be withdrawn. On the input screen, the user enters the withdrawal amount for both the charge balance and the charge balance (salary), within the withdrawal limit. When the user enters the withdrawal amount and presses the withdrawal button B10, the payment application 20 sends instruction information to the payment server 100 instructing the use of the ATM withdrawal service.

[0062] When the withdrawal instruction receiving unit 154 receives the instruction information, the withdrawal authentication unit 156, in cooperation with the payment application 20 and the financial institution server 200, performs user authentication processing for withdrawals, similar to the embodiment described above. If the authentication process is successful, the withdrawal instruction unit 158 ​​instructs the financial institution server 200 to perform a withdrawal of the charge balance via the ATM 210. Upon receiving the withdrawal instruction, the financial institution server 200 instructs the ATM 210 to perform the withdrawal. In Figure 16, as an example, a case is shown where withdrawals are made from both the charge balance and the charge balance (salary). However, in the right-hand part of Figure 16, the user can also set the withdrawal of the charge balance to zero and withdraw only the charge balance (salary).

[0063] Figure 17 shows an example of an ATM service completion screen according to a modified example. The ATM service completion screen, like in this embodiment, includes, for example, the amount deducted from the user's charge balance (10,100 yen in Figure 9) and its breakdown (the actual amount withdrawn from the ATM (10,000 yen in Figure 9) and the fee deducted from the charge balance (100 yen in Figure 9)). Furthermore, in this modified example, the ATM service completion screen includes a breakdown of the actual amount withdrawn from the ATM, broken down by the type of charge balance. As an example, Figure 17 shows a case where 5,000 yen is deducted from the charge balance and 5,000 yen is deducted from the charge balance (salary).

[0064] According to the embodiment described above, a payment server that implements an electronic payment service in conjunction with a payment application installed on the user's terminal device receives an instruction from the payment application to withdraw the user's stored electronic value as cash via an automated teller machine at a financial institution. Upon receiving the instruction, the payment server works in cooperation with the payment application and the financial institution's server to perform user authentication processing for the withdrawal. If the authentication process is successful, the payment server instructs the financial institution's server to execute the withdrawal via the automated teller machine. This reduces the processing load for users of the electronic payment service when withdrawing electronic value as cash.

[0065] Although embodiments for carrying out the present invention have been described above using examples, the present invention is not limited in any way to these embodiments, and various modifications and substitutions can be made without departing from the spirit of the present invention. [Explanation of symbols]

[0066] 10. User terminal device 20 Payment Apps 100 Payment Servers 120 Payment Content Provision Department 130 Payment Processing Unit 140 Information Management Department 150 Information Processing Unit 152 Display Control Unit 154 Withdrawal Instruction Receiving Unit 156 Withdrawal Verification Department 158 Withdrawal Instruction Department 170 Storage section

Claims

[Claim 1] A receiving unit receives a withdrawal instruction from the payment application to withdraw the user's electronic value, which is stored by the payment server that implements an electronic payment service in conjunction with the payment application installed on the user's terminal device, as cash via an automated teller machine of a financial institution. Upon receiving the aforementioned withdrawal instruction, an authentication unit, in cooperation with the payment application and the financial institution's server, performs the user authentication process related to the withdrawal. If the authentication process is successful, the system includes an instruction unit that instructs the financial institution's server to execute the withdrawal via the automated teller machine. Information processing device.

Images