Application program, settlement system, and control method of terminal device

Abstract

To provide an application program, and the like, configured to combine points issued to a user with electronic money available for an electronic payment to be applied to the bill of a credit card, thereby improving the convenience for the user.SOLUTION: An application program causes a terminal device configured to communicate with a credit card company server managed by a credit card company over a network to: display credit-card bill on a display unit of the terminal device; acquire the quantity of points offered to a user who operates the terminal device; and transmit, to the credit card company server, an instruction to apply the amount of electronic money in combination with the quantity of points to the bill, in accordance with an input of the user.SELECTED DRAWING: Figure 15

Description

[Technical Field]

[0001] The present invention relates to an application program, a payment system, and a method for controlling a terminal device. [Background technology]

[0002] In the past, a point service has been proposed in which a store selling goods issues points to a user in response to payment of a fee, and the issued points are used to pay the fee. Patent Document 1 also proposes a system in which the points issued to a user are used to pay the amount charged to a credit card. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2010-282439 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the system described in Patent Document 1 can be inconvenient for users because it is not possible to combine the points issued to users with electronic money that can be used for electronic payments and apply it to the credit card bill.

[0005] The present invention has been made in consideration of the above circumstances, and one of its objects is to provide an application program, a payment system, and a method for controlling a terminal device that can combine points issued to a user with electronic money that can be used for electronic payments and apply it to the credit card bill, thereby improving convenience for users. [Means for solving the problem]

[0006] One aspect of the present invention is an application program that causes a terminal device capable of communicating via a network with a credit card company server managed by a credit card company to display the credit card billing amount on a display unit of the terminal device, obtain the number of points awarded to the user operating the terminal device to apply to the billing amount, and, in accordance with input from the user, send to the credit card company server an application instruction instructing the credit card company server to combine the amount of electronic money and the number of points and apply them to the billing amount. [Effects of the Invention]

[0007] According to one aspect of the present invention, it is possible to provide an application program, a payment system, and a control method for a terminal device that can combine points issued to a user with electronic money that can be used for electronic payments and apply it to the credit card bill, thereby improving convenience for users. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of a configuration for realizing an electronic payment service. [Figure 2] This is a sequence diagram (part 1) illustrating the general flow of electronic payment. [Figure 3] This is a sequence diagram (part 2) illustrating the general flow of electronic payment. [Figure 4] FIG. 2 is a configuration diagram of a payment server 100. [Figure 5] FIG. 10 is a diagram showing an example of the contents of user information 172. [Figure 6] FIG. 10 is a diagram showing an example of the contents of affiliated store / store information 176. [Figure 7] FIG. 2 is a diagram illustrating the configuration of a user terminal device 200. [Figure 8] FIG. 3 is a diagram illustrating the configuration of a credit card company server 300. [Figure 9] FIG. 10 is a diagram showing an example of the contents of credit card information 372. [Figure 10] 10 is an example of a home screen of the payment application 20. [Figure 11] 10 is an example of a management screen for the mini app 30. [Figure 12] 13 is an example of a payment amount input screen of the mini appli 30. [Figure 13] 10 is an example of a payment details confirmation screen of the mini app 30. [Figure 14] 10 is an example of a procedure completion screen for the mini app 30. [Figure 15] FIG. 10 is a sequence diagram showing details of the electronic money and points appropriation process. [Figure 16] 10 is an example of a home screen of the mini app 30. [Figure 17] 10 is another example of a home screen of the mini app 30. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, with reference to the drawings, embodiments of an application program, a payment system, and a terminal device control method of the present invention will be described. Various devices, such as the "server" mentioned below, that provide services to users and perform internal analysis may be realized by a group of distributed devices, and each device may be operated by a different business. Furthermore, the owner of the device's hardware (the cloud server provider) and the business that actually operates it may also be different. An electronic payment service is a service that supports payments for the purchase of goods and services at a store. A store may be, for example, a physical store (real-world store) existing in real space, but may also include a virtual store for e-commerce transactions. Virtual stores may also include those operated by entities other than the operator of the electronic payment service. In such cases, when making a payment for a purchase at a virtual store, the user is controlled to transition to the interface screen of the electronic payment service. In an electronic payment service, a store is treated as belonging to, for example, a member store (brand), and when a purchase is made at a store, processing such as payment is primarily conducted between the user and the member store. Alternatively, processing such as payment 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 mainly by a payment server 100. The payment server 100 communicates with, for example, one or more user terminal devices 200, one or more first store terminal devices 50, one or more second store terminal devices 70, and a credit card company server 300 via a network NW. The network NW includes, for example, the Internet, a LAN (Local Area Network), a wireless base station, a provider device, etc.

[0011] The user terminal device 200 is, for example, a portable terminal device such as a smartphone or tablet terminal. The user terminal device 200 is a computer device having at least an optical reading function, a communication function, a display function, an input acceptance function, and a program execution function. In the following description, the components for realizing these functions are referred to as a camera, a communication device, a touch panel, a central processing unit (CPU), etc. In the user terminal device 200, a processor such as a CPU executes a payment application (hereinafter referred to as a payment app) 20, which operates in cooperation with the payment server 100 to provide electronic payment services to users. In addition, a processor such as a CPU executes a mini application (hereinafter referred to as a mini app) 30 in the user terminal device 200, which operates in cooperation with the credit card company server 300 to provide credit card-related services to users. The payment app 20 is installed on the user terminal device 200 from, for example, an application store and controls the camera, communication device, touch panel, etc. The mini app 30 runs on the payment app 20.

[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. The store code image 60 may be displayed on a display placed in the store (which may be the display of a terminal device such as a smartphone).

[0013] The second store terminal device 70 is used by the operator of the affiliated store. The second store terminal device 70 is a smartphone, tablet terminal, personal computer, etc. An interface for affiliated stores 72 runs on the second store terminal device 70. The interface for affiliated stores 72 may be an app for affiliated stores or a browser. The interface for affiliated stores 72 accepts coupon settings and the like from the operator of the affiliated store and transmits them to the payment server 100. The second store terminal device 70, which is a smartphone, has the function of displaying a code image corresponding to a store code image and reading the code image displayed by the user terminal device 200 by executing the app for affiliated stores.

[0014] The payment server 100 realizes electronic payment based on payment information received from the user terminal device 200 or the first store terminal device 50. The first store terminal device 50 may include a POS device and an affiliated store server, in which case payment information is sent from the POS device via the affiliated store server to the payment server 100. In the following explanation, this distinction will not be made and it is assumed that payment information is sent from the first store terminal device 50.

[0015] The credit card company server 300 is a computer managed by the credit card company, and communicates with the payment server 100 and the user terminal device 200 via the network NW. As will be described in detail later, the credit card company server 300 holds information relating to the user's credit card.

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

[0017] In the case of pattern 1 (hereinafter referred to as user scan) shown in FIG. 2, user terminal device 200, with payment application 20 running, decodes store code image 60 using its optical reading function (S1). Store code image 60 includes store URL (Uniform Resource Locator) information. This store URL is the domain of the electronic payment service to which store identification information has been added, and is associated with an affiliated store ID, store ID, etc. in payment server 100 (described below). Payment application 20 sends first payment information including the store URL and account ID to payment server 100 (S2). Payment server 100 searches for store information (described below) using the affiliated store ID and store ID corresponding to the store URL, acquires information on the affiliated store name and store name (S3), and sends this information to payment application 20 (S4). The user enters the payment amount into user terminal device 200 on the screen displaying the affiliated store name and store name (S5). Then, the user terminal device 200 generates second payment information including at least the payment amount and sends it to the payment server 100 (S6). The payment server 100 makes the electronic payment based on the received second payment information (S7). The payment server 100 then sends a payment completion notice (information for displaying a payment completion screen) to the payment app 20 (S8), and the payment app 20 displays the payment completion screen (S9). Note that when the store code image 60 is displayed on a display installed in the store, the store code image 60 may include information on the payment amount in addition to the store URL. In this case, the step of the user inputting the payment amount is omitted, and the payment amount information is included in the first payment information and sent to the payment server 100. Information on the affiliated store name and store name may be included and displayed on the payment completion screen.

[0018] In the case of pattern 2 (hereinafter referred to as store scan) shown in FIG. 3, the payment app 20 sends a request to issue a one-time code to the payment server 100 when the payment app 20 is launched, when a payment operation is performed in the payment app 20, at the automatic update timing (e.g., every minute), and at other timings (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, generated based on the one-time code (S14). The user holds (presents) the display surface of the user terminal device 200 over the first in-store terminal device 50, and the first in-store terminal device 50 decodes the code image using its optical reading function and obtains the one-time code, etc. (S15). The first in-store terminal device 50 then generates payment information including the one-time code, payment amount, affiliated store ID, store ID, etc., and sends it to the payment server 100 (S16). The payment amount information is acquired in advance by reading a barcode, manually entering it, etc. Based on the received information, the payment server 100 identifies the user corresponding to the one-time code and performs electronic payment (S17). Then, the payment server 100 sends a payment completion notice to the payment application 20 (S18), and the payment application 20 displays a payment completion screen (S19).

[0019] Note that electronic payment may be performed using only one of the above patterns. Furthermore, the "account ID" described in FIG. 2 may be other information (e.g., a phone number) that can be used as user identification information. Furthermore, issuing a one-time code may be omitted in store scanning, and the payment application 20 may display a code image generated based on the user's account ID. In this case, the payment server 100 identifies the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[0020] [Payment server] FIG. 4 is a configuration diagram of the payment server 100. The payment server 100 includes, for example, a communication unit 110, a payment content providing unit 120, a payment processing unit 130, an information management unit 140, and a storage unit 170. The components other than the communication unit 110 and the storage unit 170 are implemented by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be implemented by hardware (including circuitry) such as a large-scale integration (LSI), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a graphics processing unit (GPU), or may be implemented by a combination of software and hardware. The program may be stored in advance in a storage device (a storage device with a non-transitory storage medium) such as an HDD (hard disk drive) or flash memory, or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device.

[0021] The storage unit 170 is a hard disk drive (HDD), a flash memory, a random access memory (RAM), etc. The storage unit 170 may be a network attached storage (NAS) device that can be accessed by the payment server 100 via a network. The storage unit 170 stores information such as user information 172, payment content information 174, and affiliated store / shop information 176.

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

[0023] The payment content providing unit 120 has, for example, a function of a web server, and provides information (content) for displaying various screens of the electronic payment service to the user terminal device 200. The payment content providing unit 120 reads out necessary content from the payment content information 174 as appropriate and provides it to the user terminal device 200. The user terminal device 200 accepts various inputs from the user while content is being played by the payment application 20, and transmits the above-mentioned payment information and the like to the payment server 100.

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

[0025] FIG. 5 is a diagram showing 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, a user URL, account ID, telephone number, and password, as well as an email address, user ID, name, address, gender, date of birth, registration date, remaining charge balance, credit card payment settings, credit card limit, credit card payment amount, available credit card payment amount, payment method settings, bank account, credit card number, charge history information, payment history information, and membership number. The user URL is used for remittance processing between users. When registering for the electronic payment service, registration of a phone number and password is required. The account ID is issued to the user by the payment server 100, and the user ID can be set by the user (or does not have to be set). The email address, name, address, and date of birth are also information that can be set by the user (or do not have to be set). The registration date is the date on which the user registered for the electronic payment service (the date on which the account was created). Hereinafter, the user's instance (electronic payment account) to which this information is associated will be referred to as an account.

[0026] The charge balance indicates the balance of electronic money set by the user by transferring funds to the account in advance. Transfer methods include transfers from a designated bank's ATM (Automatic Teller Machine) or from a registered bank account. The credit payment setting indicates whether the settings for electronic credit payment have been completed and is set to either "completed" or "not completed." The credit payment limit is the monthly credit payment limit. The credit payment amount is the amount of credit payment already used in the current month. The available credit payment amount is the amount of credit payment available in the current month, calculated by subtracting the credit payment amount from the credit payment limit. While the figure shows only one credit payment limit, in reality, there may also be 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 currently make electronic payments using the charge balance, credit payment, or bank account payments using the deposit balance in their bank account. The bank account and credit card number are information on the bank account or credit card number (account number, card number) that can be used to deposit funds into the electronic payment service. The charge history information is a history of the user's previous transfers to the electronic payment service to increase the charge balance. The payment history information is information that shows the breakdown of payments made by the user for each payment (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.). Points are awarded to users when they purchase products and can be used in electronic payments like electronic money.

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

[0028] The information management unit 140 manages the user information 172 and the affiliated store / store information 176 based on information acquired from the user terminal device 200 and the second store terminal device 70. For example, the information management unit 140 adds, edits, deletes, etc. new records for the user information 172 and the affiliated store / store information 176.

[0029] [Electronic Payment] When payment information is acquired from the user terminal device 200 or the first store terminal device 50, the payment processing unit 130 refers to the user information 172 to acquire the "payment method setting" of the user. For users whose "payment method setting" is set to "electronic payment," 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 managed in association with the user ID and increasing the item value of the affiliated store's sales proceeds. The item value of the affiliated store's sales proceeds is not itself used as electronic money, for example, but rather the amount corresponding to the item value of the sales proceeds is transferred to a bank account in a cycle according to the agreement between the affiliated store and the electronic payment service.

[0030] The payment processing unit 130 performs electronic payments for users whose "Payment Method Setting" is set to "Credit Card Payment" as follows. Credit card payment is a payment method in cooperation with a credit card company, which is a separate entity from the operator of the electronic payment service. The operator of the electronic payment service acts as the creditor, and allows electronic payments within the credit card payment limit, independent of the remaining balance. To receive the credit card payment service, a user may be required to obtain a credit card provided by the operator of the electronic payment service. The monthly amount used for credit card payment is settled on the following month's payment date, for example, by debit from a bank account. In this case, the payment processing unit 130 makes a provisional settlement by adding the settlement amount to the credit card payment amount and subtracting the same amount from the available credit card balance. On the closing date, the payment processing unit 130 performs the process described above to debit the current month's payment on the following month's payment date, or requests the credit card company operator to perform this process. If the settlement amount exceeds the available credit card balance at the time of provisional settlement, an error notification is returned to the payment app 20.

[0031] [User terminal device] FIG. 7 is a configuration diagram of user terminal device 200. User terminal device 200 includes, for example, a communication unit 210, a control unit 220, a display unit 230, an input unit 240, and a storage unit 270. The control unit 220 is 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 an LSI, ASIC, FPGA, or GPU, or may be realized by a combination of software and hardware. The program may be stored in advance in a storage device such as an HDD or flash memory (a storage device having a non-transitory storage medium), or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device.

[0032] Storage unit 270 is a HDD, flash memory, RAM, etc. Storage unit 270 may be a NAS device that user terminal device 200 can access via a network. Storage unit 270 stores payment application 20, mini application 30, and information used by these applications.

[0033] The communication unit 210 is a wireless communication module that performs wireless communication with a wireless base station connected to the network NW.

[0034] The display unit 230 is a display device such as a liquid crystal display device. The input unit 240 is a device that accepts input from a user. The display unit 230 and the input unit 240 may be configured as a touch panel display.

[0035] [Credit card company server] FIG. 8 is a configuration diagram of credit card company server 300. Credit card company server 300 includes, for example, a communication unit 310, a credit card payment processing unit 320, and a storage unit 370. Credit card payment processing unit 320 is 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 an LSI, ASIC, FPGA, or GPU, or may be realized by a combination of software and hardware. The program may be stored in advance in a storage device such as an HDD or flash memory (a storage device with a non-transitory storage medium), or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device.

[0036] The storage unit 370 is a HDD, flash memory, RAM (Random Access Memory), etc. The storage unit 370 may be a NAS device that can be accessed by the credit card company server 300 via a network. The storage unit 370 stores information such as credit card information 372.

[0037] The communication unit 310 is a communication interface for connecting to the network NW, and is, for example, a network interface card.

[0038] The credit card payment processing unit 320 performs credit card-related processing, the details of which will be described later. The credit card payment processing unit 320 also reads out credit card information 372 from the storage unit 370, updates the credit card information 372, and so on.

[0039] FIG. 9 is a diagram showing an example of the contents of credit card information 372. The credit card information 372 associates information such as a card number, a user name, an expiration date, a security code, a billing history, and an account ID. The card number is information indicating a credit card number. The user name is information indicating the name of the credit card owner. The expiration date is information indicating the expiration date of the credit card. The security code is information indicating a number printed on the back of the credit card to prevent fraudulent use. The billing history is information related to the credit card billing history, including, for example, the billing year and month and the billing amount. The credit card billing amount may include both the billing amount for product purchases (shopping) and the billing amount for cash borrowing (cashing). The account ID is information similar to the account ID included in the user information 172 (FIG. 5) and is identification information for identifying a user who uses an electronic payment service. The credit card company server 300 obtains the account ID from the payment server 100 by linking accounts with the payment server 100 and writes the obtained account ID to the credit card information 372.

[0040] [App screen] FIG. 10 is an example of the home screen of the payment app 20. As shown in FIG. 10, the home screen of the payment app 20 includes areas A1, A2, and A3. Area A1 displays code images such as barcodes and QR codes (registered trademarks) used for smartphone payments. Area A2 displays icons for instructing main smartphone payment operations such as charging and scanning. Area A3 displays various icons for launching various mini-apps that can be executed by the payment app 20.

[0041] Specifically, eight icons IC1 to IC8 are displayed in area A3. Icons IC1 to IC6 are icons for launching mini apps. When a user selects (tap) one of icons IC1 to IC6, payment application 20 launches the mini app corresponding to the selected icon. Icon IC7 is a favorite icon. When a user selects (tap) icon IC7, payment application 20 displays a favorite screen on the display of user terminal device 200, which displays a list of favorite mini apps set by the user in advance. Icon IC8 is a function list icon. When a user selects (tap) icon IC8, payment application 20 displays a function list screen on the display of user terminal device 200, which displays a list of all mini apps.

[0042] Fig. 11 shows an example of the management screen of the mini app 30. When the user selects (tap) icon IC1 displayed on the home screen of Fig. 10, the credit card company's mini app 30 (hereinafter simply referred to as "mini app") is launched. After that, when the user selects (tap) an administration icon (not shown) from the home screen of the mini app 30, the management screen of the mini app 30 shown in Fig. 11 is displayed on the display unit 230 of the user terminal device 200. As shown in Fig. 11, the management screen of the mini app 30 includes an administration menu display area A4, a various procedures / confirmation display area A5, and a button B1.

[0043] The management menu display area A4 displays menus such as "Check available balance," "Check card information," "Check / change payment account," "Revolving management," "Cashing service," and "Notification delivery settings."

[0044] The procedure / confirmation display area A5 displays menus such as "Increase available credit limit," "Pay card bill with electronic money," "Apply for ETC card," "Family card," "Account linking," "Confirm / change customer information," and "Identity authentication service."

[0045] Button B1 is a button for proceeding to the procedure for paying the card bill with electronic money. When the user taps (selects) button B1, the payment amount input screen shown in FIG.

[0046] Fig. 12 is an example of a payment amount input screen for the mini app 30. As described above, when the user taps (selects) button B1 on the management screen (Fig. 11) for the mini app 30, the payment amount input screen for the mini app 30 is displayed on the display unit 230 of the user terminal device 200. As shown in Fig. 12, the payment amount input screen includes a planned billing amount display area A6, an amount input area A7, a check box C, a button B2, and a button B3.

[0047] The estimated billing amount display area A6 displays the estimated billing amount for the current month's card bill, the available electronic money balance, and the available points. In the example shown in Figure 12, the estimated billing amount is 250,000 yen, the available electronic money balance is 3,000 yen, and the available points are 1,000 points.

[0048] Checkbox C is used to select whether or not to apply points to a card charge. In the example shown in FIG. 12, if the user checks checkbox C, 1,000 points held by the user will be applied to the card charge. For example, points may be applied to the card charge at an exchange rate of 1 point = 1 yen. Therefore, in the example shown in FIG. 12, if the user checks checkbox C, 1,000 points will be applied to the card charge, resulting in a payment of 1,000 yen.

[0049] The amount input area A7 is an area for inputting the amount to be applied to the card bill. The user can input the amount in the amount input area A7 using the input unit 240 of the user terminal device 200. In the example shown in Figure 12, the available electronic money balance is 3000 yen and the available points are 1000 points, so the user can input an amount up to 3000 + 1000 = 4000 yen in the amount input area A7.

[0050] Button B2 is a button for instructing the user to use all of the electronic money balance and points. In the example shown in Figure 12, when the user taps (selects) button B2, 3000 (electronic money) + 1000 (points) = 4000 yen is automatically entered into the amount input field A7.

[0051] Button B3 is a confirmation button. When the user taps (selects) button B3 after inputting the amount in amount input area A7, the payment details confirmation screen of FIG.

[0052] FIG. 13 is an example of a payment details confirmation screen of the mini app 30. On the payment details confirmation screen, the user can confirm the bill amount after payment with electronic money. In FIG. 12 described above, if the user checks checkbox C and enters 3000 yen in amount input field A7, the payment details confirmation screen shown in FIG. 13 is displayed on display unit 230 of user terminal device 200. In this case, the amount to be used for payment (amount to be applied to card billing) is 3000 yen, and the number of points to be used is 1000 points, so the balance of electronic money to be used is 3000-1000=2000 yen.

[0053] In this way, the mini app 30 obtains the total amount to be applied to the billing amount in accordance with the user's input in the amount input area A7. The mini app 30 also calculates the amount of electronic money to be applied to the billing amount by subtracting the amount corresponding to the number of points from the total amount. This allows the amount of electronic money to be paid by the user to be reduced depending on the number of points used.

[0054] Furthermore, the mini app 30 determines whether or not to apply points to the billing amount based on the user's input in check box C. If the mini app 30 determines that points should be applied to the billing amount, it applies the points to the billing amount in preference to electronic money. Electronic money can be withdrawn to a bank or sent to a friend, but points cannot be withdrawn to a bank or sent to a friend. For this reason, points, which have fewer opportunities to be used, are applied to the billing amount in preference to electronic money.

[0055] 13, the payment details confirmation screen displays the estimated card billing amount for this month (250,000 yen), the amount to be used for payment (3,000 yen), the electronic money balance to be used (2,000 yen), the number of points to be used (1,000 points), and the final estimated billing amount (247,000 yen). The payment details confirmation screen also includes buttons B4 and B5.

[0056] Button B4 is a button for returning to the previous screen. When the user taps (selects) button B4, the payment amount input screen of FIG. 12 is displayed on the display unit 230. By returning to the payment amount input screen, the user can modify the amount to be applied to the card bill. Button B5 is a button for instructing the user to proceed with the application procedure for electronic money and points. When the user taps (selects) button B5, the credit card company server 300 and the payment server 100 work together to perform the application process for electronic money and points. The details of the application process for electronic money and points will be described later.

[0057] Fig. 14 is an example of a procedure completion screen for the mini app 30. When the electronic money and point allocation process is completed, the procedure completion screen shown in Fig. 14 is displayed on the display unit 230 of the user terminal device 200. On the procedure completion screen, the user can understand that the application for the electronic money and point allocation process has been completed. The procedure completion screen also includes a button B6.

[0058] Button B6 is a button for returning to the management screen (FIG. 11). When the user taps (selects) button B6, the management screen of FIG. 11 is displayed on display unit 230. By returning to the management screen, the user can perform other procedures.

[0059] 15 is a sequence diagram showing details of the electronic money and points appropriation process. The process according to this sequence diagram is executed when the user taps (selects) button B1 on the management screen of the mini app 30 shown in FIG.

[0060] First, the credit card payment processing unit 320 of the credit card company server 300 sends a user information request to the payment server 100 (step S21). The user information request includes the account ID of the user who operates the mini app 30.

[0061] Next, the payment processing unit 130 of the payment server 100 transmits the user information to the credit card company server 300 in response to the user information request received from the credit card company server 300 (step S22). Specifically, the payment processing unit 130 acquires the user's electronic money balance and points linked to the account ID included in the user information request from the user information 172, and transmits the acquired electronic money balance and points to the credit card company server 300.

[0062] Next, the credit card payment processing unit 320 of the credit card company server 300 transmits the amount of the card bill for the user, the user's electronic money balance, and points to the credit card company's mini app 30 (step S23). Specifically, the credit card payment processing unit 320 obtains the amount of the card bill for the user from the billing history in the credit card information 372. The credit card payment processing unit 320 also receives the user's electronic money balance and points from the payment server 100. The credit card payment processing unit 320 then transmits this information to the mini app 30.

[0063] Next, the credit card company's mini app 30 displays the payment amount input screen shown in Fig. 12 on the display unit 230 based on the card bill amount, electronic money balance, and points received from the credit card company server 300 (step S24). This allows the user to understand the card bill amount, electronic money balance, and points held by the user. The user then inputs the amount in the amount input field A7 and taps (selects) button B3.

[0064] When the user taps (selects) button B3, the mini app 30 obtains the balance of electronic money to be used (step S25) and the number of points to be used (step S26). For example, in the above-mentioned Figure 12, if the user checks checkbox C and enters 3,000 yen in amount input field A7, the balance of electronic money to be used will be 2,000 yen and the number of points to be used will be 1,000 points.

[0065] Next, the mini app 30 displays the payment details confirmation screen shown in Fig. 13 on the display unit 230 based on the card bill amount, the electronic money balance to be used, and the number of points to be used (step S27). This allows the user to confirm the electronic money balance and the number of points to be applied to the card bill. If there are no problems with the content displayed on the payment details confirmation screen, the user taps (selects) button B5.

[0066] When the user taps (selects) button B5, the mini app 30 sends an allocation instruction to the credit card company server 300 (Step S28). The allocation instruction includes the electronic money balance and the number of points to be allocated to the card bill.

[0067] Next, the credit card payment processor 320 of the credit card company server 300 sends the payment information to the payment server 100 based on the appropriation instruction sent from the mini app 30 (step S29). The payment information includes the user's account ID, the affiliated store ID, the balance of electronic money to be used, the number of points to be used, etc. The affiliated store ID is assumed to be stored in advance in the storage unit 370 as identification information for specifying the credit card company.

[0068] Next, the payment processing unit 130 of the payment server 100 performs electronic payment based on the payment information received from the credit card company server 300 (step S30). Here, the balance of electronic money to be used included in the payment information is treated as the payment amount, and the number of points to be used included in the payment information is treated as payment points. In the example shown in FIG. 13, the payment amount is 2000 yen (the balance of electronic money to be used), and the number of payment points is 1000 points (the number of points to be used). Specifically, in the user information 172 (FIG. 5), the payment processing unit 130 subtracts the payment amount (2000 yen) from the charge balance of the user linked to the account ID included in the payment information, and subtracts the payment points (1000 points) from the points of the user linked to the account ID included in the payment information. In addition, the payment processing unit 130 calculates the payment amount by summing the payment amount and the amount equivalent to the payment points. In the example shown in FIG. 12, the payment amount is 2000 + 1000 = 3000 yen. Thereafter, the payment processing unit 130 adds the payment amount (3,000 yen) to the sales amount (sales amount of the credit card company) linked to the affiliated store ID included in the payment information in the second table 176B (FIG. 6).

[0069] When the electronic payment is completed, the payment processing unit 130 sends a payment completion notice to the credit card company server 300 (step S31). The payment completion notice may include the user's account ID and the payment amount.

[0070] The credit card payment processing unit 320 of the credit card company server 300 updates the credit card information 372 based on the payment completion notice (step S32). Specifically, the credit card payment processing unit 320 identifies the user based on the account ID included in the payment completion notice. The credit card payment processing unit 320 also subtracts the payment amount included in the payment completion notice from the card billing amount for the current month included in the billing history of the identified user in the credit card information 372.

[0071] Once the update of the credit card information 372 is complete, the credit card payment processor 320 sends a payment completion notice to the mini appli 30 (step S33). After that, based on the payment completion notice received from the credit card company server 300, the mini appli 30 displays the procedure completion screen shown in Fig. 14 on the display unit 230 (step S34). This allows the user to understand through the mini appli 30 that the electronic money and points allocation process has been successfully completed.

[0072] In the above embodiment, a case has been described in which both electronic money and points are applied to the card billing amount. On the other hand, if checkbox C in FIG. 12 is not checked, the mini app 30 determines not to apply points to the billing amount. In this case, in step S28, an application instruction is sent to the credit card company server 300 instructing that electronic money equivalent to the total amount entered in the amount input field A7 in FIG. 12 be applied to the billing amount. This allows the application process to proceed even if the user does not want to use points.

[0073] [Other embodiments] In the above embodiment, the procedure for allocating electronic money and points is carried out from the management screen of the mini appli 30, but this is not limiting. For example, the procedure for allocating electronic money and points may be carried out from the home screen that is displayed when the mini appli 30 is launched. This point will be described below.

[0074] Fig. 16 is an example of the home screen of the mini appli 30. When the user selects (tap) icon IC1 displayed on the home screen of Fig. 10, the credit card company's mini appli 30 is launched, and the home screen of the mini appli 30 shown in Fig. 16 is displayed on the display unit 230 of the user terminal device 200. On the home screen of the mini appli 30, the user can check various information related to the credit card. The home screen of the mini appli 30 also includes a button B7 and a message display area A8.

[0075] Button B7 is a button for proceeding to the management screen (FIG. 11). When the user taps (selects) button B7, the management screen of FIG. 11 is displayed on the display unit 230. By proceeding to the management screen, the user can check information about their credit card and perform various procedures.

[0076] The message display area A8 is an area where a message for the user is displayed. In the example shown in Fig. 16, the message "You can reduce the billing amount by using your electronic money balance and points" is displayed in the message display area A8. This encourages the user to proceed with the application procedure for electronic money and points.

[0077] Furthermore, when the user selects (tap) message display area A8, the payment amount input screen for mini app 30 shown in FIG. 12 is displayed on display unit 230. This allows the user to proceed with the electronic money and points appropriation procedure directly from the home screen (FIG. 16) without going through the management screen (FIG. 11). Note that message display area A8 may be displayed on the home screen only during the provisional confirmation period of the card bill. The provisional confirmation period may be the period from when the card bill amount is provisionally confirmed to when it is finally confirmed.

[0078] Fig. 17 is another example of the home screen of the mini app 30. When the user swipes the home screen of the mini app 30 in Fig. 16 to scroll it down, the home screen of the mini app 30 shown in Fig. 17 is displayed on the display unit 230 of the user terminal device 200. As shown in Fig. 17, the home screen of the mini app 30 includes a payment service display area A9.

[0079] The payment service display area A9 is an area that displays payment services for card charges. In the example shown in Figure 17, "Flat Revolving," "Skip Revolving," and "Balance Application" are displayed in the payment service display area A9.

[0080] Furthermore, when the user selects (tap) "Balance Application" in the payment service display area A9, the payment amount input screen of the mini app 30 shown in Fig. 12 is displayed on the display unit 230. This allows the user to proceed with the application procedure for electronic money and points directly from the home screen (Fig. 17) without going through the management screen (Fig. 11).

[0081] Also, a banner may be displayed on the home screen of the mini appli 30 to guide the user to the payment amount input screen of the mini appli 30 shown in Fig. 12. Also, a link to the payment amount input screen of the mini appli 30 shown in Fig. 12 may be displayed on the screen of the payment appli 20. This allows the user to easily proceed with the procedure to apply electronic money and points.

[0082] As described above, the mini app 30 of this embodiment causes the user terminal device 200, which can communicate with the credit card company server 300 managed by the credit card company via the network NW, to display the credit card bill on the display 230 of the user terminal device 200 (step S24), obtain the amount of electronic money available for electronic payment to apply to the bill (step S25), obtain the number of points awarded to the user in connection with the user's purchase of a product to apply to the bill (step S26), and send an application instruction to the credit card company server instructing the credit card company server to combine the amount of electronic money and the number of points and apply them to the bill (step S28). This allows the points issued to the user and the electronic money available for electronic payment to be combined and applied to the credit card bill, improving convenience for the user.

[0083] The payment system of this embodiment also includes a credit card company server 300 managed by a credit card company, a payment server 100 that performs electronic payments using electronic money, and a mini app 30 installed on a user terminal device 200 that can communicate with the credit card company server 300 and payment server 100 via a network NW. The mini app 30 causes the user terminal device 200 to display the credit card bill on the display 230 of the user terminal device 200 (step S24), obtain the amount of electronic money that can be used for electronic payment to apply to the bill (step S25), obtain the number of points awarded to the user in connection with the user's purchase of a product to apply to the bill (step S26), and transmit an application instruction to the credit card company server instructing the credit card company server to combine the amount of electronic money and the number of points and apply them to the bill (step S28). The credit card company server 300 transmits payment information based on the amount of electronic money and the number of points included in the application instruction received from the user terminal device 200 to the payment server 100 (step S29). The payment server 100 subtracts the payment amount included in the payment information from the user's electronic money balance and adds the payment amount to the credit card company's sales (step S30). This allows the points issued to the user and the electronic money that can be used for electronic payment to be combined and applied to the credit card bill, improving convenience for the user.

[0084] The above describes the form for carrying out the present invention using an embodiment, but the present invention is not limited to such an embodiment, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present invention. [Explanation of symbols]

[0085] 20. Payment App 30 Mini Apps 100 Payment Server 110 Communications Department 120 Payment Contents Department 130 Payment processing unit 140 Information Management Department 170 Storage section 200 User terminal device 210 Communications Department 220 Control Unit 230 Display section 240 Input section 270 Storage section 300 Credit card company server 310 Communications Department 320 Credit card payment processing unit 370 Storage section

Claims

1. A terminal device capable of communicating with a credit card company server managed by the credit card company via a network, Displaying the credit card billing amount on the display unit of the terminal device, acquire the number of points granted to the user operating the terminal device to be used to pay the bill; transmitting, to the credit card company server, an application instruction instructing that the amount of electronic money and the number of points be combined and applied to the billing amount in accordance with the input by the user; Application program.

2. The terminal device further includes: determining whether or not to apply the points to the billing amount in accordance with the input of the user; 2. The application program according to claim 1.

3. The terminal device further includes: When it is determined that the points should be applied to the billing amount, the application instruction for applying the points to the billing amount in priority to the electronic money is transmitted to the credit card company server.

2. The application program according to claim 1.

4. The terminal device further includes: when it is determined that the points should not be applied to the billing amount, an application instruction is sent to the credit card company server to instruct the credit card company to apply the electronic money equivalent to the total amount to be applied to the billing amount.

3. The application program according to claim 2.

5. a credit card company server managed by the credit card company; a payment server that performs electronic payments using electronic money; an application program installed in a terminal device capable of communicating with the credit card company server and the payment server via a network; A payment system comprising: The application program is installed on the terminal device. Displaying the credit card billing amount on the display unit of the terminal device, acquire the number of points granted to the user operating the terminal device to be used to pay the bill; transmits to the credit card company server, instructing that the amount of the electronic money and the number of points be combined and applied to the billing amount in accordance with the input of the user; The credit card company server transmitting payment information based on the amount of the electronic money and the number of the points included in the application instruction received from the terminal device to the payment server; The payment server subtracting a payment amount based on the payment information from the balance of the electronic money of the user, and adding the payment amount to the sales amount of the credit card company; Payment system.

6. A terminal device capable of communicating with a credit card company server managed by the credit card company via a network, Displaying the credit card billing amount on the display unit of the terminal device, Acquire the number of points granted to the user operating the terminal device to be applied to the billed amount; transmits to the credit card company server an application instruction instructing that the amount of electronic money and the number of points be combined and applied to the billing amount in accordance with the input by the user; A method for controlling a terminal device.

Images