Management server and management method

Abstract

When a customer requests payment and uses a payment application to make the payment, a management server is provided that can determine whether the version of the payment application is suitable for that payment. [Solution] The management server 10 includes an acquisition unit 112 that acquires payment data indicating the details of the payment from the payment server 30 that executes the payment when a user U on terminal 40 requests payment, a communication control unit 111 that sends a startup instruction to terminal 40 to start the application used for payment when the acquisition unit 112 has acquired the payment data, and a first determination unit 113 that, when it acquires terminal data including the application version from terminal 40, determines whether the acquired version is equal to or greater than a threshold corresponding to the type of payment.

Description

Technical Field

[0001] The present invention relates to a management server and a management method.

Background Art

[0002] When a user purchases a product or service, a payment application may be used. The payment application is usually updated according to additional functions or the like.

[0003] For example, Patent Document 1 discloses updating the payment application when there is a version update in the payment application installed on a mobile terminal owned by a store.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] In the prior art, when a customer offering payment uses a payment application for payment, it was not possible to determine whether the version of the payment application is suitable for the payment.

[0006] Therefore, an object of the present invention is to provide a management server capable of determining whether the version of a payment application is suitable for a payment when a customer offering payment uses the payment application for payment.

Means for Solving the Problems

[0007] A management server according to a preferred embodiment of the present invention includes: an acquisition unit that acquires payment data indicating the details of a payment from a payment server that performs a payment when a user of a terminal requests a payment; a communication control unit that, when the acquisition unit acquires the payment data, transmits a startup instruction to the terminal to start the application used for the payment; and a first determination unit that, when terminal data including the version of the application is acquired from the terminal, determines whether the acquired version is equal to or greater than a threshold corresponding to the type of payment.

[0008] Furthermore, a management method according to a preferred embodiment of the present invention includes: obtaining payment data indicating the details of a payment from a payment server that executes the payment when a user of a terminal requests payment; sending a startup instruction to the terminal to start the application used for the payment when the acquisition unit has obtained the payment data; and determining whether the acquired version is equal to or greater than a threshold corresponding to the type of payment when terminal data including the version of the application has been obtained from the terminal. [Effects of the Invention]

[0009] According to the present invention, when a customer requests payment and makes the payment using a payment application, it becomes possible to determine whether the version of the payment application is suitable for that payment. [Brief explanation of the drawing]

[0010] [Figure 1] A block diagram showing the overall configuration of payment system 1. [Figure 2] A block diagram showing an example configuration of management server 10. [Figure 3] A diagram showing an example configuration of the application database ADB. [Figure 4] A sequence diagram showing the operation of the payment system 1 according to the first embodiment. [Figure 5] A sequence diagram showing the operation of the payment system 1 according to the first embodiment. [Figure 6] A diagram showing an example of screen SI1. [Figure 7] A diagram showing an example of screen SI2. [Figure 8] A diagram showing an example of the SI3 acceptance confirmation screen. [Figure 9] This figure shows an example of the acceptance completion screen SI4. [Figure 10] A diagram showing an example of the SI5 acceptance confirmation screen. [Figure 11] This figure shows an example of the acceptance completion screen SI6. [Modes for carrying out the invention]

[0011] 1: First Embodiment The payment system 1 according to the first embodiment will be described below with reference to Figures 1 to 11.

[0012] As described above, in the conventional technology, when a customer requests payment and makes a payment using a payment application, it was not possible to determine whether the version of the payment application was suitable for that payment. The payment system 1 of this embodiment can determine whether the version of the payment application is suitable for that payment when a customer requests payment and makes a payment using a payment application. In this embodiment, "settlement" means, for example, "payment of consideration for goods or services."

[0013] 1-1: Configuration of the First Embodiment 1-1-1: Overall structure FIG. 1 is a block diagram showing the overall configuration of the payment system 1 according to the present embodiment. As shown in FIG. 1, the payment system 1 includes a management server 10, a store server 20, a payment server 30, and terminals 40[1] to terminals 40[n]. The management server 10, the store server 20, the payment server 30, and the terminals 40[1] to terminals 40[n] are communicably connected to each other via a communication network NET. Here, n is an integer of 1 or more. k is an integer of 1 or more and n or less. In the following description, the terminals 40[1] to terminals 40[n] may be collectively referred to as "terminals 40". In FIG. 1, the user U uses the terminal 40. Also, the user U[k] uses the terminal 40[k]. Note that in FIG. 1, the number of the management server 10, the store server 20, and the payment server 30 being one is merely an example. The payment system 1 includes an arbitrary number of management servers 10, store servers 20, and payment servers 30. The management server 10, the store server 20, and the payment server 30 may be the same as each other or different from each other.

[0014] The terminal 40 is a device used by the user U to purchase goods or services. The user U[k] may settle the price of goods or services by using the payment application installed on the terminal 40[k]. Alternatively, the user U[k] may perform online payment for the price of goods or services after connecting the terminal 40[k] to the Internet. Hereinafter, the payment using the payment application may be referred to as "application payment".

[0015] The terminal 40 is preferably a mobile terminal. The terminal 40 may be, for example, a smartphone or a tablet. Alternatively, the terminal 40 may be a PC (Personal Computer).

[0016] The store server 20 is a server that provides a store site where the user U[k] purchases goods or services using the terminal 40[k]. The user U[k] accesses the store site using the terminal 40[k] to purchase the goods or services posted on the store site.

[0017] The management server 10 manages the payment application installed on the terminal 40 via the communication network NET. Further, when the user U[k] makes a payment using the payment application installed on the terminal 40[k], the management server 10 manages the data used for the payment.

[0018] In the present embodiment, the management server 10 determines whether a payment application is installed on the terminal 40[k]. Further, the management server 10 determines whether the version of the application installed on the terminal 40[k] is equal to or higher than the threshold value corresponding to the type of payment.

[0019] When the payment server 30 settles the price of goods or services by using the above application installed on the terminal 40[k] by the user U[k], the payment server 30 executes payment processing based on the data acquired from the management server 10, the store server 20, and the terminal 40[k] via the communication network NET. Further, when the user U[k] makes an online payment after connecting the terminal 40[k] to the Internet, the payment server 30 executes payment processing based on the data acquired from the store server 20 via the communication network NET.

[0020] 1-1-2: Configuration of Management Server FIG. 2 is a block diagram showing a configuration example of the management server 10. As shown in FIG. 2, the management server 10 includes a processing device 11, a storage device 12, a communication device 13, a display device 14, and an input device 15. Each element of the management server 10 is interconnected by a single or a plurality of buses for communicating data.

[0021] The processing unit 11 is a processor that controls the entire management server 10. The processing unit 11 is configured using, for example, one or more chips. The processing unit 11 is also configured using a central processing unit (CPU) that includes, for example, interfaces with peripheral devices, arithmetic units and registers. Some or all of the functions of the processing unit 11 may be implemented by hardware such as a DSP (Digital Signal Processor), ASIC (Application Specific Integrated Circuit), PLD (Programmable Logic Device), and FPGA (Field Programmable Gate Array). The processing unit 11 executes various processes in parallel or sequentially.

[0022] The storage device 12 is a recording medium that can be read from and written to by the processing device 11. The storage device 12 includes, for example, non-volatile memory and volatile memory. Non-volatile memory is, for example, ROM (Read Only Memory), EPROM (Erasable Programmable Read Only Memory), and EEPROM (Electrically Erasable Programmable Read Only Memory). Volatile memory is, for example, RAM (Random Access Memory). The storage device 12 also stores the control program PR1 executed by the processing device 11. The storage device 12 also functions as a work area for the processing device 11.

[0023] Furthermore, the storage device 12 stores the application database ADB. The application database ADB is a database that stores the correspondence between the type of payment and the version threshold of the payment application corresponding to that type of payment.

[0024] Figure 3 shows an example of the configuration of the application database (ADB). The application database (ADB) stores application data (AD). Each application data AD has the following fields: "Data ID," "Payment Type ID," and "Version." The "Data ID" is the identifier for each application data AD. The "Payment Type ID" is the identifier indicating the type of payment. The "Version" is the version of the payment application corresponding to the type of payment indicated by the "Payment Type ID." In the application database ADB illustrated in Figure 3, for example, the application data AD with "Data ID" "001" indicates that the payment application corresponding to the payment type with "Payment Type" "A" has a "Version" of "7.0.9" or higher. Note that the application database ADB shown in Figure 3 stores 20 application data ADs. However, 20 application data ADs is just one example. The application database ADB can store any number of application data ADs.

[0025] In Figure 2, the communication device 13 is hardware acting as a transmitting and receiving device for communicating with other devices. The communication device 13 is also called, for example, a network device, network controller, network card, or communication module. The communication device 13 may be equipped with a connector for wired connection and an interface circuit corresponding to the above-mentioned connector. The communication device 13 may also be equipped with a wireless communication interface. Examples of connectors and interface circuits for wired connection include products compliant with wired LAN, IEEE 1394, and USB. Examples of wireless communication interfaces include products compliant with wireless LAN and Bluetooth®.

[0026] The display device 14 is a device that displays various types of information, including images and characters. The display device 14 displays various types of information under the control of the processing unit 11. For example, various display panels such as liquid crystal display panels and organic EL display panels may be suitably used as the display device 14.

[0027] The input device 15 is a device that receives operations from the administrator of the payment system 1. For example, the input device 15 is configured to include a keyboard, touchpad, touch panel, or pointing device such as a mouse. If the input device 15 is configured to include a touch panel, it may also serve as the display device 14.

[0028] The processing unit 11 functions as a communication control unit 111, an acquisition unit 112, a first determination unit 113, a second determination unit 114, and a display control unit 115, for example, by reading and executing the control program PR1 from the storage device 12.

[0029] The communication control unit 111 causes the communication device 13 to send and receive various types of data between the store server 20, the payment server 30, and the terminal 40.

[0030] When user U[k] requests payment for goods or services using terminal 40[k], the acquisition unit 112 acquires payment data indicating the details of the payment from the payment server 30.

[0031] More specifically, when a terminal 40[k] sends a request to purchase goods or services to a store server 20 that provides a store website for selling goods or services, the acquisition unit 112 acquires payment data from a payment server 30 that is in cooperation with the store server 20.

[0032] When the acquisition unit 112 acquires payment data, the communication control unit 111 sends a command to the terminal 40[k] to start the application used for payment using the communication device 13. This command includes a link to a site provided by the management server 10. When the terminal 40[k] accesses the site via the link using the browser provided in the payment application, the acquisition unit 112 acquires terminal data from the terminal 40[k]. This terminal data includes the version of the payment application. Note that the "site provided by management server 10" mentioned above is an example of the "first site." Also, the "browser included in the payment application" mentioned above is an example of the "first browser."

[0033] The first determination unit 113 determines whether the acquired version is equal to or greater than the threshold corresponding to the type of payment when the acquisition unit 112 acquires terminal data including the version of the payment application from the terminal 40[k].

[0034] More specifically, the first determination unit 113 uses the payment type indicated by the payment data obtained from the payment server 30 to refer to the application database ADB and obtain a threshold for the version of the payment application corresponding to that payment type. Furthermore, the first determination unit 113 determines whether the version of the payment application included in the terminal data is equal to or greater than the threshold obtained from the application database ADB.

[0035] The second determination unit 114 determines whether or not the payment application is installed on terminal 40[k], based on whether or not terminal 40[k] is accessing a site provided by the management server 10 by using the browser provided in the payment application.

[0036] For example, if terminal 40[k] is an Android® terminal, the second determination unit 114 may determine whether or not the payment application is installed on terminal 40[k] based on whether or not terminal 40[k] is accessing a site provided by the management server 10 by using the browser provided in the payment application.

[0037] Alternatively, the second determination unit 114 may determine whether or not a payment application is installed on terminal 40[k], depending on whether or not the acquisition unit 112 was able to acquire the above-mentioned terminal data within a predetermined time after the communication control unit 111 sent the above-mentioned instruction to terminal 40[k] to start the payment application.

[0038] For example, if terminal 40[k] is an iPhone (registered trademark), the second determination unit 114 may determine whether or not a payment application is installed on terminal 40[k], depending on whether or not the acquisition unit 112 was able to acquire the above terminal data within a predetermined time after the communication control unit 111 sent a command to terminal 40[k] to start the payment application.

[0039] If the first determination unit 113 determines that the version of the payment application on terminal 40[k] is below a threshold, the display control unit 115 may cause the browser installed in the payment application to display a screen informing the user of updating the payment application. Alternatively, the display control unit 115 may cause a different browser installed on terminal 40[k], which is different from the browser installed on the payment application, to display a screen informing the user of updating the payment application. "A different browser installed on terminal 40[k], which is different from the browser installed on the payment application" may, for example, be the browser that is installed on terminal 40[k] at the time of factory shipment.

[0040] Alternatively, if the first determination unit 113 determines that the version of the payment application on terminal 40[k] is below a threshold, the display control unit 115 may launch a browser on terminal 40[k] that is different from the browser provided by the payment application, and display a screen in that different browser that prompts the user to accept a payment that does not use the payment application. Note that "a browser different from the browser provided in the payment application" is an example of a "second browser." Also, "the screen requesting payment acceptance" is an example of a "second screen."

[0041] If the second determination unit 114 determines that the above-mentioned payment application is not installed on the terminal 40[k], the display control unit 115 may cause a screen instructing the terminal 40[k] to update the payment application using a browser that is different from the browser provided with the payment application.

[0042] Alternatively, if the second determination unit 114 determines that the above-mentioned payment application is not installed on the terminal 40[k], the display control unit 115 may launch a browser on the terminal 40[k] that is different from the browser provided by the payment application, and display a screen in that different browser that prompts the user to accept a payment that does not use the payment application. As mentioned above, "a browser different from the browser provided in the payment application" is an example of a "second browser." Also, "the screen that prompts the user to accept the payment" is an example of a "second screen."

[0043] The display control unit 115, when the first determination unit 113 determines that the version of the payment application on terminal 40[k] is above a threshold, and the second determination unit 114 determines that the payment application is installed on terminal 40[k], causes the browser provided in the payment application to display a screen for accepting the payment. This "screen for accepting the payment" may, for example, include operators to be operated to accept a payment using the payment application and operators to be operated to make a payment without using the payment application.

[0044] 1-2: Operation of the First Embodiment Figures 4 and 5 are sequence diagrams showing the operation of the payment system 1 according to the first embodiment.

[0045] In step S1, the terminal 40[k] used by user U[k] displays the store page provided by the store server 20.

[0046] In step S2, user U[k] operates the button on the store page that accepts the purchase of the product or service displayed on the store page in order to offer to pay for the product or service.

[0047] In step S3, terminal 40[k] sends a purchase instruction to store server 20 instructing it to purchase the above-mentioned goods or services.

[0048] In step S4, the store server 20 sends a settlement request to the settlement server 30 requesting settlement of the price for the goods or services that user U[k] has offered to pay for. The settlement request includes settlement data indicating the details of the settlement.

[0049] In step S5, the settlement server 30 transmits the settlement data to the management server 10. The processing unit 11 of the management server 10 functions as an acquisition unit 112 to acquire the settlement data.

[0050] In step S6, the management server 10 sends a startup instruction to terminal 40[k] instructing it to launch the payment application. More specifically, the processing unit 11 of the management server 10 functions as a communication control unit 111 and sends the startup instruction to terminal 40[k]. The startup instruction includes a link to a site provided by the management server 10.

[0051] In step S7, terminal 40[k] launches the payment application. Terminal 40[k] also uses the browser included in the payment application to access the site provided by the management server 10 via the link received in step S6.

[0052] In step S8, terminal 40[k] transmits terminal data to the management server 10. This terminal data includes the version of the payment application. The processing unit 11 of the management server 10 functions as an acquisition unit 112 to acquire this terminal data.

[0053] In step S9, the management server 10 determines the version of the payment application installed on terminal 40[k]. More specifically, the processing unit 11 of the management server 10 functions as a first determination unit 113 to determine whether the version of the payment application installed on terminal 40[k] is equal to or greater than a threshold corresponding to the type of payment.

[0054] If the version of the payment application installed on terminal 40[k] is equal to or greater than the threshold corresponding to the type of payment, the management server 10 performs the action in step S10.

[0055] On the other hand, if the version of the payment application installed on terminal 40[k] is below the threshold corresponding to the type of payment, for example, the processing unit 11 on the management server 10 functions as a display control unit 115 to display screen SI1 to terminal 40[k] instructing it to update the payment application.

[0056] Figure 6 shows an example of screen SI1, which guides the user through updating the payment application. Screen SI1 includes icon IC1. User U[k] updates the payment application by interacting with icon IC1.

[0057] In step S10, the management server 10 determines whether or not a payment application is installed on terminal 40[k]. More specifically, the processing unit 11 of the management server 10 functions as a second determination unit 114 to determine whether or not a payment application is installed on terminal 40[k].

[0058] If a payment application is installed on terminal 40[k], the management server 10 performs the operation in step S11.

[0059] On the other hand, if the payment application is not installed on terminal 40[k], for example, the processing unit 11 on the management server 10 functions as a display control unit 115 to display screen SI2, which guides users through the installation of the payment application, in the browser on terminal 40[k], which is different from the browser on the payment application.

[0060] Figure 7 shows an example of screen SI2, which guides the user through the installation of a payment application. Screen SI2 includes icon IC2. User U[k] installs the payment application on terminal 40[k] by operating icon IC2.

[0061] In step S11, the management server 10 transmits the above settlement data to terminal 40[k]. More specifically, the processing unit 11 of the management server 10, functioning as a communication control unit 111, transmits the above settlement data to terminal 40[k].

[0062] In step S12, terminal 40[k] sends a screen display request to payment server 30, requesting that it display the acceptance confirmation screen SI3 to terminal 40[k] in step S14, which will be described later.

[0063] In step S13, the payment server 30 sends screen data to the terminal 40[k] to display the acceptance confirmation screen SI3 described above.

[0064] In step S14, terminal 40[k] displays the acceptance confirmation screen SI3.

[0065] Figure 8 shows an example of the acceptance confirmation screen SI3. The acceptance confirmation screen SI3 displays the sales store and price of the goods or services to be paid. The sales store and price are included in the payment data obtained by terminal 40[k] from the management server 10 in step S11. The acceptance confirmation screen SI3 also includes icons IC3[1], IC3[2], and IC3[3]. User U[k] agrees to pay the price using the payment application by operating icon IC3[1]. User U[k] also agrees to pay the price without using the payment application by operating icon IC3[2]. User U[k] also instructs to cancel the payment by operating icon IC3[3].

[0066] In step S15, terminal 40[k] sends a settlement request to settlement server 30 requesting settlement of the price for goods or services, based on the operation of user U[k] in step S14.

[0067] In step S16, the settlement server 30 performs settlement of the payment for the goods or services.

[0068] In step S17, the payment server 30 sends screen data to the terminal 40[k] to display the acceptance completion screen SI4, which indicates that the above acceptance has been completed.

[0069] In step S18, terminal 40[k] displays the acceptance completion screen SI4.

[0070] Figure 9 shows an example of the acceptance completion screen SI4. The acceptance completion screen SI4 indicates that the displayed screen will automatically transition to the store site screen in order to complete the procedure. The acceptance completion screen SI4 also includes an icon IC4. If the displayed screen does not automatically transition to the store screen, the user U[k] will operate the icon IC4 to transition the acceptance completion screen SI4 to the store site screen.

[0071] In step S19, terminal 40[k] sends a screen display request to the store server 20, requesting that in step S21 described later, the store consent completion screen be displayed to terminal 40[k] indicating that consent on the store site has been completed.

[0072] In step S20, the store server 20 sends screen data to terminal 40[k] to display the store approval completion screen described above.

[0073] In step S21, terminal 40[k] displays the store approval completion screen.

[0074] In step S9 described above, if it is determined that the version of the payment application installed on terminal 40[k] is below the threshold corresponding to the type of payment, as another example, the processing unit 11 on the management server 10 may function as a display control unit 115. The processing unit 11 may launch a browser on terminal 40[k] that is different from the browser installed in the payment application, and display the acceptance confirmation screen SI5 for accepting the payment in that browser.

[0075] Figure 10 shows an example of the acceptance confirmation screen SI5. The acceptance confirmation screen SI5 shows a case where the price of goods or services is paid together with the telephone charges of the terminal 40[k] used as a mobile phone. The acceptance confirmation screen SI5 includes an input field BC5 and an icon IC5. User U[k] accepts the payment by entering a PIN in the input field BC5 and operating the icon IC5.

[0076] Figure 11 shows an example of the acceptance completion screen SI6 displayed in a browser on terminal 40[k], which is different from the browser on the payment application, when user U[k] operates icon IC5 on acceptance confirmation screen SI5. Acceptance completion screen SI6 indicates that the displayed screen will automatically transition to the store site screen in order to complete the procedure. Acceptance completion screen SI6 also includes icon IC6. If the displayed screen does not automatically transition to the store site screen, user U[k] will transition the acceptance completion screen SI4 to the store site screen by operating icon IC6.

[0077] In step S10 described above, if it is determined that the payment application is not installed on terminal 40[k], the processing unit 11 on the management server 10 may also function as a display control unit 115. In this case as well, the processing unit 11 may launch a browser on terminal 40[k] that is different from the browser on the payment application, and display the acceptance confirmation screen SI5 for accepting the payment on that browser.

[0078] 1-3: Effects of the First Embodiment The management server 10 according to this embodiment includes an acquisition unit 112, a communication control unit 111, and a first determination unit 113. When a user U[k] of terminal 40[k] requests payment, the acquisition unit 112 acquires payment data indicating the details of the payment from the payment server 30 that executes the payment. When the acquisition unit 112 acquires the above payment data, the communication control unit 111 sends a startup instruction to terminal 40[k] instructing it to start the application used for the above payment.

[0079] Because the management server 10 according to this embodiment has the above configuration, when a customer requesting payment makes a payment using the payment application, it is possible to determine whether the version of the payment application is suitable for that payment.

[0080] Furthermore, in the management server 10 according to this embodiment, the above settlement is payment for goods or services. Also, when a terminal 40[k] sends an offer to purchase goods or services to the store server 20 which provides a store site for selling goods or services, the acquisition unit 112 acquires the above settlement data from the settlement server 30 which is in cooperation with the store server 20.

[0081] Because the management server 10 according to this embodiment has the above configuration, it can determine whether the version of the payment application is suitable for the type of payment when it receives payment data from the payment server 30.

[0082] Furthermore, in the management server 10 according to this embodiment, the above startup instruction includes a link associated with the first site provided by the management server 10. When terminal 40[k] accesses the first site via the above link using the first browser provided in the above payment application, acquisition unit 112 acquires terminal data from terminal 40[k].

[0083] Because the management server 10 according to this embodiment has the above configuration, it is possible to obtain information indicating the version of the payment application by having the terminal 40[k] access the site provided by the management server 10.

[0084] Furthermore, the management server 10 according to this embodiment further comprises a display control unit 115. When the first determination unit 113 determines that the version is above a threshold, the display control unit 115 causes the first browser provided in the application to display a first screen for accepting the payment.

[0085] Because the management server 10 according to this embodiment has the above configuration, if the version of the payment application is above a threshold, payment using the payment application becomes possible.

[0086] Furthermore, in the management server 10, if the first determination unit 113 determines that the above version is below a threshold, the display control unit 115 launches a second browser installed in terminal 40[k], which is different from the first browser, and displays a second screen for accepting the above payment in the second browser.

[0087] Because the management server 10 according to this embodiment has the above configuration, if the version of the payment application is below the threshold, online payment becomes possible using the browser installed on the terminal 40[k] itself, instead of the payment application.

[0088] Furthermore, the management server 10 further includes a second determination unit 114. The second determination unit 114 may determine whether or not the above application is installed on the terminal 40[k] based on whether or not the terminal is accessing the above first site using the above first browser.

[0089] Because the management server 10 according to this embodiment has the above configuration, it can determine, for example, whether or not a payment application is installed if terminal 40[k] is an Android terminal.

[0090] Alternatively, in the management server 10, the second determination unit 114 may determine whether the above application is installed on the terminal 40[k] depending on whether the acquisition unit 112 was able to acquire the above terminal data within a predetermined time after the communication control unit 111 sent the above startup instruction.

[0091] Because the management server 10 according to this embodiment has the above configuration, it can determine, for example, whether a payment application is installed on terminal 40[k] if it is an iPhone.

[0092] Furthermore, in the management server 10, if the second determination unit 114 determines that the above application is not installed on the terminal 40[k], the display control unit 115 will launch a second browser on the terminal 40[k] that is different from the first browser, and will display a second screen for accepting the above payment in the second browser.

[0093] Because the management server 10 according to this embodiment has the above configuration, if a payment application is not installed, online payment is possible using the browser installed on the terminal 40[k] itself, rather than using the payment application.

[0094] Furthermore, the management method according to this embodiment includes obtaining payment data indicating the details of the payment from the payment server 30 that executes the payment when user U[k] of terminal 40[k] requests payment. Furthermore, the management method according to this embodiment includes sending a startup instruction to terminal 40[k] to start the application used for the payment when the above payment data has been obtained. Furthermore, the management method according to this embodiment includes determining whether the obtained version is equal to or greater than a threshold corresponding to the type of payment when terminal data including the version of the above application has been obtained from terminal 40[k].

[0095] Because the management method according to this embodiment has the above configuration, when a customer requesting payment makes a payment using a payment application, it becomes possible to determine whether the version of the payment application is suitable for that payment.

[0096] 2: Others (1) In the embodiments described above, the storage device 12 is exemplified by ROM and RAM, but it can also be a flexible disk, magneto-optical disk (e.g., compact disk, digital multipurpose disk, Blu-ray® disk), smart card, flash memory device (e.g., card, stick, key drive), CD-ROM (Compact Disc-ROM), register, removable disk, hard disk, floppy® disk, magnetic strip, database, server, or other suitable storage medium.

[0097] (2) In the embodiments described above, the information, signals, etc. may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0098] (3) In the embodiments described above, the input and output information may be stored in a specific location (e.g., memory) or managed using a management table. The input and output information may be overwritten, updated, or appended to. The output information may be deleted. The input information may be transmitted to other devices.

[0099] (4) In the embodiments described above, the determination may be made by a value represented using 1 bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0100] (5) The processing procedures, sequences, flowcharts, etc., exemplified in the embodiments described above may be rearranged in order, as long as they do not contradict each other. For example, the methods described in this disclosure present various step elements using an exemplary order and are not limited to the specific order presented.

[0101] (6) Each function illustrated in Figures 1 to 11 is implemented by any combination of at least one of hardware and software. Furthermore, the method of implementing each functional block is not particularly limited. That is, each functional block may be implemented using one device that is physically or logically coupled, or it may be implemented using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be implemented by combining the aforementioned one device or the aforementioned multiple devices with software.

[0102] (7) The programs illustrated in the embodiments described above should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., whether they are called software, firmware, middleware, microcode, hardware description languages ​​or by other names.

[0103] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0104] (8) In each of the above-mentioned forms, the terms “system” and “network” shall be used interchangeably.

[0105] (9) The information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information.

[0106] (10) In the embodiments described above, the terminal 40 may be a mobile station (MS). A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other appropriate terms. In this disclosure, terms such as “mobile station,” “user terminal,” “user equipment (UE),” and “terminal” may be used interchangeably.

[0107] (11) In the embodiments described above, the terms “connected,” “coupled,” or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be a physical coupling or connection, a logical coupling or connection, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain and optical (both visible and invisible) domain.

[0108] (12) In the embodiments described above, the phrase “based on” does not mean “based solely on” unless otherwise specified. In other words, the phrase “based on” means both “based solely on” and “based at least on.”

[0109] (13) The terms “determining” and “determining” as used in this disclosure may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in a table, database or other data structure), and ascertaining. “Determining” may also include, for example, receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0110] (14) Where the terms “include,” “including,” and variations thereof are used in the embodiments described above, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to be exclusive OR.

[0111] (15) In the present disclosure, if articles are added by translation, such as a, an, and the in English, the present disclosure may include the fact that the noun following these articles is plural.

[0112] (16) In this disclosure, the term “A and B are different” may mean “A and B are different from each other.” The term may also mean “A and B are each different from C.” Terms such as “separate” and “combine” may be interpreted in the same way as “different.”

[0113] (17) Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed in practice. Furthermore, notification of certain information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0114] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Accordingly, the descriptions in the present disclosure are illustrative and not restrictive in any way. [Explanation of symbols]

[0115] 1...Payment system, 10...Management server, 11...Processing device, 12...Storage device, 13...Communication device, 14...Display device, 15...Input device, 20...Store server, 30...Payment server, 40...Terminal, 111...Communication control unit, 112...Acquisition unit, 113...First determination unit, 114...Second determination unit, 115...Display control unit, AD...App data, ADB...App database, BC5...Input field, IC1...Icon, IC2...Icon, IC3...Icon, IC4...Icon, IC5...Icon, IC6...Icon, NET...Communication network, PR1...Control program, SI1...Screen, SI2...Screen, SI3...Acceptance confirmation screen, SI4...Acceptance completion screen, SI5...Acceptance confirmation screen, SI6...Acceptance completion screen, U...User

Claims

1. When a user of the terminal requests payment, an acquisition unit obtains payment data indicating the details of the payment from the payment server that executes the payment, When the acquisition unit acquires the payment data, a communication control unit transmits a startup command to the terminal instructing it to start the application used for the payment, A first determination unit, which, upon obtaining terminal data including the application version from the terminal, determines whether the obtained version is equal to or greater than a threshold corresponding to the type of payment, A management server equipped with the following features.

2. The aforementioned settlement is payment for goods or services, When the terminal transmits a request to purchase the goods or services to the store server that provides the store website for selling the goods or services, the acquisition unit acquires the payment data from the payment server which is in cooperation with the store server. The management server according to claim 1.

3. The aforementioned startup instruction includes a link associated with the first site provided by the management server, When the terminal accesses the first site via the link using the first browser provided in the application, the acquisition unit acquires the terminal data from the terminal. The management server according to claim 1.

4. The application further includes a display control unit that, if the first determination unit determines that the version is above a threshold, causes the first browser provided in the application to display a first screen for accepting the payment. The management server according to claim 1.

5. The system further includes a display control unit that, when the first determination unit determines that the version is below a threshold, launches a second browser installed on the terminal, which is different from the first browser, and displays a second screen for accepting the payment in the second browser. The management server according to claim 3.

6. The system further includes a second determination unit that determines whether the application is installed on the terminal based on whether or not the terminal is accessing the first site using the first browser. The management server according to claim 3.

7. The system further includes a second determination unit that determines whether the application is installed on the terminal, depending on whether the acquisition unit was able to acquire the terminal data within a predetermined time after the communication control unit transmits the startup instruction. The management server according to claim 3.

8. If the second determination unit determines that the application is not installed on the terminal, the system further includes a display control unit that launches a second browser, different from the first browser, installed on the terminal, and displays a second screen for accepting the payment in the second browser. The management server according to claim 6.

9. If the second determination unit determines that the application is not installed on the terminal, the system further includes a display control unit that launches a second browser, different from the first browser, installed on the terminal, and displays a second screen for accepting the payment in the second browser. The management server according to claim 7.

10. When a user of the terminal requests payment, the terminal obtains payment data indicating the details of the payment from the payment server that executes the payment, When the aforementioned payment data is obtained, a startup command is sent to the terminal instructing it to start the application used for the payment. When terminal data including the application version is obtained from the terminal, it is determined whether the obtained version is equal to or greater than the threshold corresponding to the payment type. Management methods including those mentioned.

Images