Payment management device, payment management method, program, and application program

Abstract

To provide a payment management device, payment management method, program, and application program that enable secure and convenient card payments for users. [Solution] A payment management device comprising: a display control unit that, in response to communication between a user terminal device of a user and a card having short-range wireless functionality, displays setting information on the user terminal device indicating a payment method set for card payment using the card, among a plurality of payment methods including a first payment method using the charge balance of electronic money and a second payment method using credit card payment; a change acceptance unit that accepts changes to the setting information in response to operations by the user; and a notification unit that notifies the card payment server that executes the card payment of information related to the changes.

Description

Technical Field

[0001] The present invention relates to a settlement management device, a settlement management method, a program, and an application program.

Background Art

[0002] Conventionally, an invention of a transaction settlement terminal device that handles a debit card, an electronic money card, or a transaction card having the functions of both of these cards has been disclosed (for example, Patent Document 1). This device includes a first input device for inputting the transaction amount to be settled and a second input device for designating and inputting the settlement method. By a store clerk designating and inputting the settlement method to the second input device, the settlement method for card settlement can be switched.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, when using the transaction card described in Patent Document 1, the user cannot confirm the balance of the electronic money in advance, and there is a case where the settlement fails due to insufficient balance. That is, in the prior art, there are cases where a card settlement that gives the user a sense of security and high convenience cannot be realized.

[0005] The present invention has been made in consideration of such circumstances, and one of the objects is to provide a settlement management device, a settlement management method, a program, and an application program that can realize a card settlement that gives the user a sense of security and high convenience.

Means for Solving the Problems

[0006] One aspect of the present invention is a payment management device comprising: a user terminal device of a user, a display control unit that, in response to communication between the user terminal device and a card having short-range wireless functionality, displays setting information on the user terminal device indicating a payment method set for card payment using the card, among a plurality of payment methods including a first payment method using the charge balance of electronic money and a second payment method using credit card payment; a change reception unit that accepts changes to the setting information in response to operations by the user; and a notification unit that notifies the card payment server that executes the card payment of information related to the changes. [Effects of the Invention]

[0007] According to one aspect of the present invention, it is possible to provide a payment management device, a payment management method, a program, and an application program that enable secure and convenient card payments for users. [Brief explanation of the drawing]

[0008] [Figure 1] This diagram shows an example of the configuration of an electronic payment system that enables electronic payment services. [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 diagram showing the configuration of payment server 100. [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 contents of card information 178. [Figure 8] This diagram conceptually illustrates the processes for terminal payments and card payments. [Figure 9] This figure shows an example of the contents of card payment settings information 210. [Figure 10]This diagram shows an example of the home screen of payment app 20. [Figure 11] This figure shows an example of the display screen of a payment app 20 related to the hybrid card 57. [Figure 12] This figure shows another example of the display screen of a payment app 20 related to a hybrid card 57. [Figure 13] This diagram illustrates the process by which the user terminal device 10 transitions to a display screen related to the hybrid card 57 in response to communication with the hybrid card 57. [Figure 14] This is a sequence diagram showing the process for changing the payment method. [Figure 15] This is a sequence diagram showing the payment process using the charge balance payment method. [Figure 16] This is a sequence diagram showing the payment processing flow for credit card payments. [Modes for carrying out the invention]

[0009] The embodiments of the payment management device, payment management method, and program of the present invention will be described below with reference to the drawings. Various devices, servers, etc., that appear below, which provide services to users or perform internal analysis, may be implemented by a distributed group of devices, and the operators of each device may be different. Also, the owner of the hardware of the devices (the provider of the cloud server) and the operator that actually operates them may be different. The application program and the payment management device work together to provide electronic payment services. In the following description, the application program will be referred to as the payment app, and the payment management device will be referred to as the payment server. 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 the virtual store, the user is controlled to transition 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 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 credit processing terminals 55, one or more second store terminal devices 70, and affiliated credit card company servers 200 via a network NW. The network NW includes, for example, the internet, LAN (Local Area Network), wireless base stations, provider equipment, etc.

[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 settlement application 20 is executed by a processor such as a CPU, and it operates to provide an electronic payment service to the user in cooperation with the payment server 100. The settlement 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 credit processing terminal 55 is installed in the store, similar to the first store terminal device 50. The credit processing terminal 55 includes, for example, a credit payment terminal (credit card reader) and a POS device. The credit payment terminal reads the PIN (Personal Identification Number) from the inserted or swung credit card (including hybrid cards 57) and verifies it against the PIN entered by the user, or transmits the BIN (Bank Identification Number) code etc. read from the credit card to the affiliated credit card company server 200 via the POS device. The POS device works in cooperation with the credit payment terminal to transmit information such as the payment amount to the affiliated credit card company server 200. A payment processing agent server (acquirer) may be interposed between the credit processing terminal 55 and the affiliated credit card company server 200. For the sake of simplicity, the description of the payment processing agent server will be omitted below.

[0014] The hybrid card 57 is, for example, in a form similar to a generally popular credit card, with a communication chip embedded in a card substrate. The communication chip incorporates a storage medium that stores a PIN and communicates with an external device via a contactor (or a wireless antenna). Instead of this, the hybrid card 57 may be a magnetic card. The hybrid card 57 may be a physical card having a configuration similar to those referred to as credit cards, debit cards, prepaid cards, etc. Specifically, the hybrid card 57 may be a physical card in which a contactor for performing contact communication or an antenna for performing non-contact communication and an IC chip are held by a card substrate. An example of a communication chip is the combination of a contactor or an antenna and an IC chip. The IC chip may include a communication control device, a storage device, a control device that processes received commands and returns a response, etc. In the storage device of the IC chip, in addition to an account ID and a card number, a password, key information used for mutual authentication with the settlement server 100, etc. may be stored. In this case, the credit processing terminal 55 may read information from the user's physical card, and the settlement server 100 may perform settlement processing and withdrawal processing based on the information read from the user's physical card.

[0015] 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, an interface 72 for the franchise store operates. The interface 72 for the franchise store may be an application 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 a store code image or reading a code image displayed by the user terminal device 10 by executing an application for the franchise store.

[0016] The payment server 100 implements electronic payment based on payment 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 merchant server, in which case payment information is transmitted from the POS device to the payment server 100 via the merchant server. In the following description, this distinction will not be made, and it will be assumed that payment information is transmitted from the first store terminal device 50.

[0017] The affiliated credit card company server 200 manages affiliated credit card payments, which are part of the electronic payment service. The affiliated credit card company server 200 is operated, for example, by a group company (affiliated credit card company) of the payment server 100. The affiliated credit card company may be a separate business from the external credit card company that provides the credit card as a fund source for charging the balance. The affiliated credit card company server 200 is an example of a "card payment server" in the claims.

[0018] Figures 2 and 3 are sequence diagrams illustrating the general flow of electronic payments. There may be two patterns for electronic payments: Pattern 1 and Pattern 2.

[0019] 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.

[0020] 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).

[0021] 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.

[0022] [Payment Server] Figure 4 is a diagram of the configuration of the payment server 100. 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, a payment management unit 150, and a storage unit 170. The payment management unit 150 further includes, for example, a display control unit 152, a change acceptance unit 154, a charge unit 156, and a notification unit 158. The payment content provision unit 120, the payment processing unit 130, the information management unit 140, and the payment management unit 150 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 a drive device. Of the payment server 100, the payment management unit 150 may be implemented as an independent server device. The payment management unit 150 is an example of a "payment management device" in the claims.

[0023] 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, merchant / store information 176, and card information 178.

[0024] 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.

[0025] 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, etc., to the payment server 100.

[0026] 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.

[0027] 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, terminal payment method, hybrid card number, bank account, credit card number, charge history information, and terminal payment history information. The user URL is used for money transfer processing between users. When registering for the 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 not set). Similarly, the email address, name, address, and date of birth are also information that the user can set at will (or not set). The registration date is the date the user registered for the electronic payment service (the date the account was created). Hereinafter, the user instance (electronic payment account) to which this information is associated will be referred to as an account.

[0028] 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 been set up to enable electronic payments by credit card, and is set to either "Done" or "Not Done". The credit payment setting is flag information common to both "Terminal Payment" and "Card Payment," which will be described later. Users who can use credit card payments for terminal payments are those who have been issued a Hybrid Card 57. Alternatively, the credit payment setting may be set separately for "Terminal Payment" and "Card Payment." The terminal payment method is setting information indicating whether the user will make an electronic payment using the charge balance or a credit payment in "Terminal Payment." As described later, the card payment method is synchronized in real time with the affiliated credit card company server 200. The hybrid card number is the number of the Hybrid Card 57 (for example, the PAN (Primary Account Number)). The bank account information refers to the bank account details (account number, 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 their charge balance. The terminal payment history information shows the details of each terminal payment made by the user (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.) for each transaction.

[0029] 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 the payment pattern. The merchant name may be, for example, information registered by the merchant, or information registered by the administrator of the electronic payment service. The merchant name and store name may be managed in an integrated manner. The merchant name may be, for example, a combination of the merchant name and the store name. It is preferable that the merchant name be the official name or a detailed name. In the merchant / store information 176, the merchant ID or store ID may be associated with the merchant's icon, or other detailed information about the merchant.

[0030] Figure 7 shows an example of the contents of card information 178. Card information 178 includes, for example, the hybrid card number, account ID, card payment method, credit payment limit, credit payment amount, available credit payment amount, and card payment history information. The hybrid card number is the number of the hybrid card 57 (e.g., PAN), and is the same information as the hybrid card number included in user information 172 in Figure 5. The account ID is a number used to identify the user of the electronic payment service, and is the same information as the account ID included in user information 172 in Figure 5. The card payment method is setting information that indicates whether the user will make an electronic payment using the charged balance or a credit payment in "card payment". The card payment method can be set by the user on the payment app 20. The credit payment limit is the monthly limit on credit payments that can be made. The credit payment amount is the amount of credit payments already made in the current month. The available credit payment amount is the amount of credit payments that can be made in the current month, calculated by subtracting the credit payment amount from the credit payment limit. Card payment history information is data that shows the details of each card payment made by the user (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.) for each card payment.

[0031] The Information Management Unit 140 acquires information provided by other server devices and terminal devices. Based on the information acquired from the user terminal device 10, the second store terminal device 70, and the affiliated credit card company server 200, the Information Management Unit 140 manages user information 172, merchant / store information 176, and card information 178. The Information Management Unit 140 adds, edits, deletes, etc., new records for user information 172, merchant / store information 176, and card information 178.

[0032] Next, we will explain terminal payments and card payments. Figure 8 is a conceptual diagram showing the processing of terminal payments and card payments, respectively. As explained below, electronic payment services can handle four patterns of electronic payments: (1) terminal payment / payment using charged balance, (2) terminal payment / payment using credit card, (3) card payment / payment using charged balance, and (4) card payment / payment using credit card.

[0033] [Terminal payment] (1) When the payment server 100 (payment processing unit 130) obtains payment information from the user terminal device 10 or the first store terminal device 50, terminal payment is initiated. The payment server 100 obtains the user's "terminal payment method" by referring to the user information 172. For users whose "terminal payment method" is set to "charge balance", the payment server 100 performs electronic payment through its own processing. In this case, the payment processing unit 130 subtracts the payment amount from the charge balance managed in association with the user's account ID, and adds the payment amount to the sales revenue item value of the merchant in the second table 176B of the merchant / store information 176, thereby performing electronic payment. The sales revenue item value of the merchant is not used as electronic money itself, for example, but rather the amount corresponding to the sales revenue item value is transferred to the bank account in a cycle according to the agreement between the merchant and the electronic payment service.

[0034] (2) In terminal payment, the payment server 100, for users whose "terminal payment method" is set to "credit card payment", transfers the payment information to the affiliated credit card company server 200, along with the user's hybrid card number obtained by referring to the user information 172. The affiliated credit card company server 200 checks whether the cumulative payment amount indicated by the payment information exceeds the monthly limit, and if it does not exceed the limit, it adds the acquired payment amount to the cumulative payment amount for that user. The cumulative payment amount is settled, for example, by being debited from a bank account on the payment date of the following month.

[0035] [Card payment] (3) When the affiliated credit card company server 200 obtains payment information from the credit processing terminal 55, electronic payment (card payment) using the hybrid card 57 is initiated. The affiliated credit card company server 200 refers to the card payment setting information 210 stored in the memory unit (not shown). Figure 9 shows an example of the contents of the card payment setting information 210. The card payment setting information 210 includes the hybrid card number, the card payment method, and the account ID. The hybrid card number, card payment method, and account ID are the same information as those included in the card information 178 in Figure 7, and are synchronized with the payment server 100. For users whose "card payment method" is set to "charge balance", the affiliated credit card company server 200 transfers the payment information to the payment server 100 along with the account ID of the user obtained by referring to the card payment setting information 210. Based on the acquired payment information, the payment server 100 performs the same processing as when "terminal payment method" is set to "charge balance" in terminal payment.

[0036] (4) In card payments, the affiliated credit card company server 200 performs electronic payments through its own processing for users whose "card payment method" is set to "credit payment". In this case, the affiliated credit card company server 200 performs the same processing as when "terminal payment method" is set to "credit payment" in terminal payments.

[0037] Switching between "charge balance" and "credit payment" in "terminal payment" and "card payment" is performed according to the user's actions on the payment app 20. The payment app 20 provides the user with separate interface screens for selecting either "charge balance" or "credit payment" (or other payment methods) in "terminal payment" and for selecting either "charge balance" or "credit payment" (or other payment methods) in "card payment". The following will explain in detail how the user switches payment methods, referring to the screens of the payment app 20.

[0038] [Payment app screen] Figure 10 shows an example of the home screen of the payment app 20. The home screen displays a code image CI. The code image CI includes, for example, barcodes and QR codes. Next to the code image CI, a toggle switch SW1 is displayed to switch between electronic payment using "charge balance" or electronic payment using "credit card" in "terminal payment". Note that "switch" and "button" are GUIs (Graphical User Interfaces) implemented in cooperation with the touch panel. In Figure 10, "Credit" is displayed, which means that the setting is to perform electronic payment using credit card. The user can switch between electronic payment using "charge balance" or electronic payment using "credit card" in "terminal payment" by, for example, swiping the toggle switch SW1.

[0039] The home screen also includes an operation area OA, and transition buttons TB1 and TB2. The operation area OA is equipped with buttons that instruct the main operations in electronic payment, such as a button to initiate scanning (start user scanning), a button to send the charge balance to other users, a button to display the points earned by the user, and a button to display the history of electronic payments performed by the user. When transition button TB1 is pressed, the user transitions to a payment screen that displays the code image used for "terminal payment" and the available amount. When transition button TB2 is pressed, the user transitions to a screen that displays the available amount for balance payment or credit payment. In Figure 10, since electronic payment by credit is set, when transition button TB2 is pressed, the available amount for credit payment is displayed.

[0040] At the bottom of the operating area OA, a group of icons (switches) M1, M2, ... for launching mini-applications are displayed. When a user selects (tap) one of these icons, the payment application 20 launches the mini-application corresponding to the selected (tapped) icon. For example, if a user selects (tap) the "Hybrid Card" icon corresponding to icon M2, the settings screen and payment history screen related to electronic payments using the hybrid card 57 will be displayed on the display unit of the user terminal device 10. The following describes the display of the payment application 20 related to electronic payments using the hybrid card 57, but this display control may be implemented in the payment application 20 or as the display control unit 152 of the payment server 100. In the latter case, the payment application 20 will only have the function of displaying information on the display unit of the user terminal device 10 according to the control from the display control unit 152.

[0041] Figure 11 shows an example of the display screen of the payment application 20 related to the hybrid card 57. The display screen shown in Figure 11 is displayed, for example, when a user selects (taps) icon M2 on the home screen shown in Figure 10. As shown in Figure 11, the display screen includes an area A1 that shows setting information related to electronic payment using the hybrid card 57, and an area A2 that shows detailed information related to electronic payment using the hybrid card 57.

[0042] The configuration information area A1 includes, for example, a toggle switch SW2 for switching the currently set payment method for electronic payments using the hybrid card 57. The screen in Figure 11 shows the case where the user has set the payment method to "charge balance". When the user has set the payment method to "charge balance", the payment application 20 refers to the user information 172 in Figure 5 to obtain the charge balance and displays it, for example, in the information area IA1.

[0043] For example, when a user presses the toggle switch SW2, the payment app 20 switches the payment method from "charge balance" to "credit payment" and displays it. At the same time, the payment app 20 sends information indicating that the payment method is being switched, along with the hybrid card number or account ID, to the payment server 100. When the change reception unit 154 of the payment server 100 receives the information indicating that the payment method is being switched, it refers to the card information 178 in Figure 7 using the hybrid card number or account ID as a key and changes the user's "card payment method" from "charge balance" to "credit payment".

[0044] Simultaneously, the notification unit 158 ​​notifies the affiliated credit card company server 200 of information indicating that the card payment method has been changed from "charge balance" to "credit payment," along with the hybrid card number or account ID. Upon receiving the information indicating that the card payment method has been changed from "charge balance" to "credit payment," the affiliated credit card company server 200 refers to the card payment settings information 210 in Figure 9 using the hybrid card number or account ID as a key, and changes the user's "card payment method" from "charge balance" to "credit payment." As a result, the next time the user makes a card payment, the affiliated credit card company server 200 will execute the electronic payment using "credit payment."

[0045] Returning to the screen description in Figure 11, the payment application 20 displays the charge button TB3 if the user has set the payment method to "charge balance". When the user presses the charge button TB3, the payment application 20 displays an input screen for entering the charge amount. Once the user enters the charge amount, it sends charge request information, along with the account ID, to the payment server 100, indicating that the entered amount will be charged. Upon receiving the charge request information, the charge unit 156 uses the account ID as a key to refer to the user information 172 in Figure 5, and simultaneously subtracts the entered amount from the bank account balance and adds it to the charge balance. This allows the user to avoid errors due to insufficient funds when making electronic payments using the hybrid card 57.

[0046] Detailed Information Area A2 is an area that displays detailed information about the hybrid card 57. Detailed Information Area A2 includes card information, such as the card number, name, expiration date, and security code of the hybrid card 57. By checking Detailed Information Area A2, users can smoothly enter the necessary credit card information for online payments, not only when using the hybrid card 57 for electronic payments at physical stores, but also when making payments on online shopping sites, for example.

[0047] Figure 12 shows another example of the display screen of the payment app 20 for the hybrid card 57. The display screen shown in Figure 12 is the same as in Figure 11, for example, when the user selects (taps) icon M2 on the home screen shown in Figure 10. The screen in Figure 12 shows the case where the user has set the payment method to "credit payment". When the user has set the payment method to "credit payment", the payment app 20 refers to the card information 178 in Figure 7 to obtain the available credit payment amount and displays it, for example, in the information area IA1.

[0048] For example, when a user presses the toggle switch SW2, the payment app 20 switches the payment method from "credit payment" to "charged balance" and displays it. At the same time, the payment app 20 sends information indicating that the payment method is being switched, along with the hybrid card number or account ID, to the payment server 100. When the change reception unit 154 of the payment server 100 receives the information indicating that the payment method is being switched, it refers to the card information 178 in Figure 7 using the hybrid card number or account ID as a key and changes the user's "card payment method" from "credit payment" to "charged balance".

[0049] Simultaneously, the notification unit 158 ​​notifies the affiliated credit card company server 200 of information indicating that the card payment method has been changed from "credit payment" to "charge balance," along with the hybrid card number or account ID. Upon receiving the information indicating that the card payment method has been changed from "credit payment" to "charge balance," the affiliated credit card company server 200 refers to the card payment settings information 210 in Figure 9 using the hybrid card number or account ID as a key, and changes the user's "card payment method" from "credit payment" to "charge balance." As a result, the next time the user makes a card payment, the affiliated credit card company server 200 will execute the electronic payment using the "charge balance."

[0050] Returning to the screen description in Figure 12, the payment app 20 displays the credit limit increase button TB4 if the user has set the payment method to "credit payment". When the user presses the credit limit increase button TB4, the payment app 20 sends information indicating a request to increase the credit limit, along with the account ID, to the payment server 100. Upon receiving this request information, the notification unit 158 ​​contacts the affiliated credit card company server 200, which, for example, performs a prescribed review and increases the credit limit. This allows the user to avoid errors due to insufficient available credit when making electronic payments using the hybrid card 57. The information displayed in the detailed information area A2 is the same as in Figure 11, so its explanation is omitted.

[0051] [Transition to the display screen for Hybrid Card 57] In this way, users can launch the payment app 20 and, for example, press icon M2 to check the settings and details of the hybrid card 57. However, this transition method requires users to perform multiple operations, making it cumbersome for them to check the settings and details of the hybrid card 57. As a result, users may attempt to make electronic payments using the hybrid card 57 at a store without checking the settings and details of the hybrid card 57 on the payment app 20, which may lead to errors due to insufficient balance or insufficient available credit limit.

[0052] Against this backdrop, in this embodiment, the hybrid card 57 stores link information (e.g., a deep link) in its storage medium for transitioning to the display screen related to the hybrid card 57 shown in Figures 11 and 12. When the user terminal device 10 communicates with the hybrid card 57, for example using near-field communication (NFC), it reads the link information from the storage medium of the hybrid card 57 and causes the user terminal device 10 to launch the payment application 20. In response, the payment application 20 displays the display screen related to the hybrid card 57 shown in Figures 11 and 12 on the user terminal device 10. Note that the communication method between the user terminal device 10 and the hybrid card 57 is not limited to NFC, but more generally, any method in which link information is stored in the storage medium of the hybrid card 57 and read by the user terminal device 10 via wireless communication is acceptable, such as the RFID (radio frequency identification) method.

[0053] Figure 13 is a diagram illustrating the flow of transitions from the user terminal device 10 to a display screen related to the hybrid card 57 in response to communication with the hybrid card 57. As shown on the left side of Figure 13, first, the user holds the user terminal device 10 over the hybrid card 57. At this time, the user may also launch the payment application 20, press a predetermined reading button, and then hold the device over the hybrid card 57.

[0054] When the user terminal device 10 communicates with the hybrid card 57 and obtains link information (deep link), the user terminal device 10 launches the payment application 20 and displays the display screen related to the hybrid card 57 as shown in Figures 11 and 12. More specifically, the payment application 20 queries the payment server 100 for the card payment method that the user has set up for card payment. If the set card payment method is "charge balance," it displays the display screen shown in Figure 11, while if the set card payment method is "credit payment," it displays the display screen shown in Figure 12. Alternatively, the payment application 20 may store the set card payment method in advance without querying the payment server 100.

[0055] This allows users to check the payment method set up for card payments and their charge balance or available credit limit before executing an electronic payment using the hybrid card 57. If the charge balance or available credit limit is insufficient, they can increase the charge balance or credit limit via the charge button TB3 or the credit limit increase button TB4. In other words, this enables card payments that are both secure and convenient for users.

[0056] In the above explanation, the hybrid card 57 is assumed to be a hybrid card that allows both credit payments and payments using the charged balance, but it is not limited to this. For example, the hybrid card 57 may also be a hybrid card that includes debit payments. In this case, the credit processing terminal 55 may read the user's bank account information (bank code, branch number, account number, etc.) from the hybrid card 57 and send the user's bank account information and payment information (payment amount, etc.) to a bank server (not shown). The bank server may also perform the payment processing by deducting the payment amount from the user's account based on the user's bank account information and payment information. In addition, debit payment may be set as the terminal payment method in the user information 172 in Figure 5. Furthermore, either "Completed" or "Not Completed" may be set as the debit payment setting in the user information 172.

[0057] If the hybrid card 57 also includes debit payment, the toggle switch SW2 in the screen shown in Figure 11 or Figure 12 may be configured to switch between three payment methods: charge balance, credit payment, and debit payment. Furthermore, if debit payment is selected, the payment application 20 may display the bank account balance in the information area IA1. In other words, according to the present invention, even if the hybrid card 57 supports three or more payment methods, the user can check or change the setting information for these multiple payment methods simply by holding the user terminal device 10 over the hybrid card 57.

[0058] [Sequence Diagram] Figure 14 is a sequence diagram showing the flow of the payment method change process. First, the user holds the user terminal device 10 over the hybrid card 57 to communicate with the hybrid card 57 (S101). Next, the user terminal device 10 displays the display screen of the hybrid card 57 on the payment application 20 in response to the communication with the hybrid card 57 (S102).

[0059] Next, the user terminal device 10 accepts a change in the payment method of the hybrid card 57 on the payment application 20 (S103). Then, when the user terminal device 10 accepts a change in the payment method of the hybrid card 57, it notifies the payment server 100 of the change in the payment method (S104).

[0060] Next, the change reception unit 154 of the payment server 100 receives a change in payment method from the user terminal device 10 and changes the "card payment method" in the card information 178 (S105). Next, the notification unit 158 ​​of the payment server 100 notifies the affiliated credit card company server 200 of the change in the payment method of the hybrid card 57 (S106).

[0061] Next, the affiliated credit card company server 200 updates the card payment settings information 210 based on the change information received from the payment server 100 (S105). Through the above process, real-time synchronization of card payment methods is achieved between the payment server 100 and the affiliated credit card company server 200.

[0062] Figure 15 is a sequence diagram showing the payment process using the charge balance payment method. This sequence diagram shows the process that takes place when a user purchases goods at a store.

[0063] First, the credit card processing terminal 55 reads the user's hybrid card 57 using a credit card reader (S201). This allows the credit card processing terminal 55 to obtain the card information (hybrid card number, etc.) of the hybrid card 57. Then, the credit card processing terminal 55 transmits the card information of the hybrid card 57 to the first store terminal device 50 (S202).

[0064] Next, the first store terminal device 50 generates payment information including at least the payment amount for the goods, and transmits the generated payment information to the affiliated credit card company server 200 (S203). At this time, the first store terminal device 50 also transmits the hybrid card number of the hybrid card 57 to the affiliated credit card company server 200 as information for identifying the user's hybrid card 57.

[0065] Next, the affiliated credit card company server 200 reads the card payment setting information 210 based on the hybrid card number of the hybrid card 57 received from the first store terminal device 50 (S204). At this time, the affiliated credit card company server 200 obtains the card payment method associated with the hybrid card number of the hybrid card 57 received from the first store terminal device 50 from the card payment setting information 210. Here, we assume that the card payment method obtained from the card payment setting information 210 is "charge balance".

[0066] If the card payment method obtained from the card payment setting information 210 is "charge balance", the affiliated credit card company server 200 sends payment information, including at least the payment amount for the product, to the payment server 100 (S205). At this time, the affiliated credit card company server 200 obtains the user's account ID from the card payment setting information 210 and also sends the obtained user's account ID to the payment server 100.

[0067] Next, the payment server 100 processes the payment based on the payment information received from the affiliated credit card company server 200 (S206). Specifically, the payment processing unit 130 of the payment server 100 obtains the card payment method associated with the user's account ID from the user information 172. Here, since the card payment information is the "charge balance," the payment processing unit 130 processes the payment using the charge balance. Specifically, the payment processing unit 130 subtracts the payment amount included in the payment information from the user's charge balance corresponding to the user's account ID in the user information 172.

[0068] Furthermore, the payment server 100 updates the card information 178 (S207). Specifically, the payment processing unit 130 obtains the hybrid card number associated with the user's account ID from the user information 172. The payment processing unit 130 also adds information related to the current card payment (date and time the payment was processed, store ID of the store where the purchase was made, payment amount, payment method, etc.) to the card payment history information linked to the hybrid card number obtained from the user information 172 in the card information 178.

[0069] Subsequently, the payment server 100 sends a payment completion notification to the affiliated credit card company server 200 and the first store terminal device 50 to inform them that the payment processing has been completed (S208, S209).

[0070] Figure 16 is a sequence diagram showing the flow of payment processing using the credit card payment method. This sequence diagram shows the flow of processing that occurs when a user purchases goods at a store. Note that the processes S301 to S303 in Figure 16 are the same as the processes S201 to S203 in Figure 12, so the explanation is omitted.

[0071] When the affiliated credit card company server 200 receives payment information from the first store terminal device 50, it reads the card payment setting information 210 based on the hybrid card number of the hybrid card 57 received from the first store terminal device 50 (S304). At this time, the affiliated credit card company server 200 obtains the card payment method associated with the hybrid card number of the hybrid card 57 received from the first store terminal device 50 from the card payment setting information 210. Here, it is assumed that the card payment method obtained from the card payment setting information 210 is "credit card payment".

[0072] If the card payment method obtained from the card payment setting information 210 is "credit payment", the affiliated credit card company server 200 executes credit payment processing based on the payment information received from the first store terminal device 50 (S305). For example, the affiliated credit card company server 200 checks whether the cumulative payment amount indicated by the payment information exceeds the monthly limit, and if it does not exceed the limit, it adds the obtained payment amount to the cumulative payment amount of the user. The cumulative payment amount is settled, for example, by being debited from the bank account on the payment date of the following month.

[0073] Next, the affiliated credit card company server 200 sends a payment completion notification to the first store terminal 50 and the payment server 100 to inform them that the payment processing has been completed (S306, S307). At this time, the affiliated credit card company server 200 also sends the user's account ID and information regarding this card payment (date and time the payment processing was performed, store ID of the store where the purchase was made, payment amount, payment method, etc.) to the first store terminal 50 and the payment server 100.

[0074] Subsequently, the payment server 100 updates the card information 178 (S308). Specifically, the payment processing unit 130 obtains the hybrid card number associated with the user's account ID received from the affiliated credit card company server 200 from the user information 172. The payment processing unit 130 also adds information related to the current card payment (date and time the payment was processed, store ID of the store where the purchase was made, payment amount, payment method, etc.) to the card payment history information linked to the hybrid card number obtained from the user information 172 in the card information 178.

[0075] As described above, the payment server 100 or payment application 20 of this embodiment, in response to communication between the user terminal device 10 operated by the user and the hybrid card 57 having short-range wireless functionality, displays setting information on the user terminal device 10 indicating the payment method set for card payment using the hybrid card 57, from among a plurality of payment methods including a first payment method using the electronic money charge balance and a second payment method using credit card payment. Furthermore, the payment server 100 or payment application 20 accepts changes to the setting information in response to user operations and notifies the affiliated credit card company server 200, which executes card payment using the hybrid card 57, of information regarding the changes. This makes it possible to realize card payment that is both secure and convenient for the user.

[0076] In the above explanation, a payment server 100 is described as an example of a payment management device, and it is assumed that the payment server 100 and the affiliated credit card company server 200 are separate servers. However, this is not limited to this configuration. For example, if the electronic payment service provider and the affiliated credit card company are the same company or group companies, a single server integrating the payment server 100 and the affiliated credit card company server 200 may be provided.

[0077] Furthermore, in the above embodiment, the hybrid card 57 is implemented as a card capable of both payment by charge balance and payment by credit. However, the present invention is not limited to such a configuration, and the hybrid card 57 may be a prepaid card capable of only payment by charge balance. In that case, for example, the display screen shown in Figure 11 may simply display "charge balance" as the current payment method instead of the toggle switch SW2 that indicates the current payment method, or the display field itself may be omitted. Even with such a configuration, the user can use the user terminal device 10 to communicate with the prepaid card via NFC before using the prepaid card to check the charge balance (and charge if necessary). In other words, it is possible to realize a card payment that is both secure and convenient for the user.

[0078] 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]

[0079] 10. User terminal device 20 Payment Apps 50. First store terminal device 100 Payment Servers 110 Communications Department 120 Payment Content Provision Department 130 Payment Processing Unit 140 Information Management Department 150 Payment Management Department 152 Display Control Unit 154 Change Request Department 156 Charging section 158 Notification Department 170 Storage section 172 User information 176 Merchant / Store Information 178 Card Information 200 Partner Credit Card Company Servers 210 Card Payment Settings Information

Claims

1. A display control unit, in response to communication between the user's user terminal device and a card having short-range wireless functionality, causes the user terminal device to display setting information indicating the payment method set for card payment using the card, among a plurality of payment methods including a first payment method using the electronic money charge balance and a second payment method using credit card payment. A change reception unit that accepts changes to the setting information and instructs the user to switch the payment method set for card payment from among the multiple payment methods in response to the user's operation, The system includes a notification unit that notifies the card payment server that performs the card payment of information regarding the aforementioned changes, Payment management device.

2. The display control unit further causes the user terminal device to display card information including at least one of the card number, name, expiration date, and security code of the card. The payment management device according to claim 1.

3. When the first payment method is set for card payment using the card, the display control unit further displays the charge balance on the user terminal device. The payment management device according to claim 1.

4. The aforementioned change acceptance unit further accepts a request to charge the balance in response to the user's operation. The payment management device further includes a charging unit that charges the charge balance based on the charge request. The payment management device according to claim 3.

5. When the second payment method is set for card payment using the card, the display control unit further displays the available credit amount on the user terminal device. The payment management device according to claim 1.

6. The aforementioned change acceptance unit, in response to the user's operation, further accepts the request to increase the available amount. The notification unit notifies the card payment server of the request for withdrawal. The payment management device according to claim 5.

7. The change reception unit accepts changes to the setting information, in response to an operation by the user, to instruct the user to switch from the first payment method to the second payment method, or from the second payment method to the first payment method, among the multiple payment methods, as the payment method set for card payment. The payment management device according to claim 1.

8. Computers In response to communication between the user's terminal device and a card with short-range wireless functionality, the user terminal device displays setting information indicating the payment method set for card payments using the card, from among a plurality of payment methods including a first payment method using the electronic money charge balance and a second payment method using credit card payment. In response to the user's actions, the system instructs the user to switch the payment method set for card payment from among the multiple payment methods, accepts changes to the setting information, The card payment server that performs the card payment will be notified of the information regarding the aforementioned changes. Payment management methods.

Images