Management server and management method

Abstract

To provide a management server capable of judging whether the version of a payment application is suitable for a payment when a customer who proposes payment uses the payment application to make the 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 of a terminal 40 requests payment, a communication control unit 111 that, when the acquisition unit 112 acquires the payment data, sends to the terminal 40 a startup instruction to instruct it to launch an application to be used for the payment, and a first judgment unit 113 that, when terminal data including the application version is acquired from the terminal 40, judges 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 technology]

[0002] When a user purchases a product or service, the user may use a payment application. The payment application is usually upgraded in response to the addition of new functions.

[0003] For example, Patent Document 1 discloses that when a payment application installed on a mobile terminal owned by a store is upgraded, the payment application is updated. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2015-060262 A Summary of the Invention [Problem to be solved by the invention]

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

[0006] Therefore, an object of the present invention is to provide a management server that can determine whether the version of a payment application is suitable for a payment when a customer who proposes payment uses a payment application to make the payment. [Means for solving the problem]

[0007] A management server according to a preferred embodiment of the present invention includes an acquisition unit that, when a user of a terminal requests a payment, acquires payment data indicating the content of the payment from a payment server that executes the payment, a communication control unit that, when the acquisition unit acquires the payment data, sends to the terminal a startup instruction to instruct the terminal to launch an application to be 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] In addition, a management method according to a preferred embodiment of the present invention includes, when a user of a terminal requests a payment, acquiring payment data indicating the content of the payment from a payment server that executes the payment, when the acquisition unit acquires the payment data, sending to the terminal a launch instruction instructing the terminal to launch an application used for the payment, and when terminal data including the version of the application is acquired from the terminal, determining whether the acquired version is equal to or greater than a threshold corresponding to the type of payment. Effect of the Invention

[0009] According to the present invention, when a customer who proposes payment makes a payment using a payment application, it becomes possible to determine whether the version of the payment application is suitable for the payment. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a block diagram showing the overall configuration of a payment system 1. [Diagram 2] FIG. 2 is a block diagram showing an example of the configuration of a management server 10. [Diagram 3] FIG. 1 is a diagram showing an example of the configuration of an application database ADB. [Figure 4] FIG. 2 is a sequence diagram showing the operation of the payment system 1 according to the first embodiment. [Diagram 5] FIG. 2 is a sequence diagram showing the operation of the payment system 1 according to the first embodiment. [Figure 6] FIG. 4 is a diagram showing an example of a screen SI1. [Figure 7] FIG. 13 shows an example of a screen SI2. [Figure 8] FIG. 13 shows an example of an approval confirmation screen SI3. [Figure 9] FIG. 13 shows an example of an approval completion screen SI4. [Figure 10] FIG. 13 shows an example of an approval confirmation screen SI5. [Figure 11] FIG. 13 shows an example of an approval completion screen SI6. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] 1: First embodiment Hereinafter, a payment system 1 according to the first embodiment will be described with reference to FIGS.

[0012] As described above, in the conventional technology, when a customer who proposes to make a payment uses a payment application to make a payment, it is not possible to determine whether the version of the payment application is suitable for the payment. In the payment system 1 of the present embodiment, when a customer who proposes to make a payment uses a payment application to make a payment, it is possible to determine whether the version of the payment application is suitable for the payment. In this embodiment, "settlement" refers to "payment of the price for goods or services" as an example.

[0013] 1-1: Configuration of the first embodiment 1-1-1: Overall composition FIG. 1 is a block diagram showing the overall configuration of a payment system 1 according to this 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 40[n]. The management server 10, the store server 20, the payment server 30, and terminals 40[1] to 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, terminals 40[1] to 40[n] may be collectively referred to as "terminals 40". In FIG. 1, a user U uses terminal 40. Furthermore, a user U[k] uses terminal 40[k]. 1, the number of the management server 10, the store server 20, and the payment server 30 is one, which is merely an example. The payment system 1 includes any 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 pay for the goods or services by using a payment application installed on the terminal 40[k]. Alternatively, the user U[k] may connect the terminal 40[k] to the Internet and pay for the goods or services online. In the following, payment using a payment application may be referred to as "app 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 a user U[k] purchases goods or services using a terminal 40[k]. The user U[k] purchases goods or services listed on the store site by accessing the store site using the terminal 40[k].

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

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

[0019] When a user U[k] uses the above-mentioned application installed on terminal 40[k] to pay for goods or services, the payment server 30 executes payment processing based on data obtained from the management server 10, the store server 20, and terminal 40[k] via the communication network NET. In addition, when a user U[k] connects a terminal 40[k] to the Internet and makes an online payment, the payment server 30 executes the payment processing based on data obtained from the store server 20 via the communication network NET.

[0020] 1-1-2: Management server configuration 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. The elements included in the management server 10 are connected to each other by a single or multiple buses for communicating data.

[0021] The processing device 11 is a processor that controls the entire management server 10. The processing device 11 is configured, for example, using one or more chips. The processing device 11 is also configured, for example, using a central processing unit (CPU) including an interface with peripheral devices, an arithmetic unit, and a register. Some or all of the functions of the processing device 11 may be realized by hardware such as a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA). The processing device 11 executes various processes in parallel or sequentially.

[0022] The storage device 12 is a recording medium that can be read and written by the processing device 11. The storage device 12 includes, for example, a nonvolatile memory and a volatile memory. The nonvolatile memory is, for example, a ROM (Read Only Memory), an EPROM (Erasable Programmable Read Only Memory), and an EEPROM (Electrically Erasable Programmable Read Only Memory). The volatile memory is, for example, a RAM (Random Access Memory). The storage device 12 also stores a 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] The storage device 12 also stores an application database ADB. The application database ADB is a database that stores the correspondence between the type of payment and the threshold value of the version of the payment application corresponding to the type of payment.

[0024] FIG. 3 is a diagram showing an example of the configuration of the application database ADB. Application data AD is stored in the application database ADB. Each application data AD has the fields of "data ID", "payment type ID", and "version". "Data ID" is an identifier for each application data AD. "Payment type ID" is an identifier indicating the type of payment. "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 FIG. 3, as an example, application data AD with a “Data ID” of “001” indicates that the payment application corresponding to a payment type with a “Payment Type” of “A” has a “Version” of “7.0.9” or higher. 3 stores 20 pieces of application data AD. However, the number of pieces of application data AD being 20 is merely an example. Any number of pieces of application data AD may be stored in the application database ADB.

[0025] In Fig. 2, the communication device 13 is hardware as a transmitting / receiving device for communicating with other devices. The communication device 13 is also called, for example, a network device, a network controller, a network card, or a communication module. The communication device 13 may include a connector for wired connection and an interface circuit corresponding to the connector. The communication device 13 may also include a wireless communication interface. Examples of the connector and interface circuit for wired connection include products that comply with wired LAN, IEEE1394, and USB. Examples of the wireless communication interface include products that comply with wireless LAN, Bluetooth (registered trademark), and the like.

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

[0027] The input device 15 is a device that accepts operations from an administrator of the payment system 1. For example, the input device 15 includes a keyboard, a touch pad, a touch panel, or a pointing device such as a mouse. Here, when the input device 15 includes a touch panel, it may also function as the display device 14.

[0028] The processing device 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 a control program PR1 from the storage device 12.

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

[0030] The acquisition unit 112 acquires payment data indicating the details of the payment from the payment server 30 when the user U[k] uses the terminal 40[k] to offer payment for a product or service.

[0031] More specifically, when an offer to purchase a product or service is sent from terminal 40[k] to a store server 20 that provides a store site selling the product or service, the acquisition unit 112 acquires payment data from a payment server 30 that cooperates with the store server 20.

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

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

[0034] More specifically, the first determination unit 113 acquires a threshold value for the version of the payment application corresponding to the type of payment by referring to the application database ADB using the type of payment indicated by the payment data acquired from the payment server 30. Furthermore, the first determination unit 113 determines whether the version of the payment application included in the above terminal data is equal to or higher than the threshold value acquired from the application database ADB.

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

[0036] As an example, if terminal 40[k] is an Android (registered trademark) terminal, the second judgment unit 114 may determine whether or not a payment application is installed on terminal 40[k] based on whether or not terminal 40[k] is accessing a site provided by management server 10 by using a browser provided in the above-mentioned payment application.

[0037] Alternatively, the second determination unit 114 may determine whether or not a payment application is installed in the terminal 40[k] depending on whether or not the acquisition unit 112 can acquire the above terminal data within a pre-set time period after the communication control unit 111 sends an instruction to the terminal 40[k] to launch the above payment application.

[0038] As an example, when 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 is able to acquire the above-mentioned terminal data within a pre-set time period after the communication control unit 111 sends an instruction to terminal 40[k] to launch the above-mentioned payment application.

[0039] When the first determination unit 113 determines that the version of the payment application of the terminal 40[k] is less than the threshold, the display control unit 115 may cause the browser of the payment application to display a screen informing the user of an update to the payment application. Alternatively, the display control unit 115 may cause a browser that is provided in the terminal 40[k] and different from the browser provided in the payment application to display a screen informing the user of an update to the payment application. As an example, the "browser that is provided in the terminal 40[k] and different from the browser provided in the payment application" may be a browser that is installed in the terminal 40[k] when the terminal 40[k] is shipped from the factory.

[0040] Alternatively, when the first determination unit 113 determines that the version of the payment application of terminal 40[k] is less than a threshold value, the display control unit 115 may launch a browser on terminal 40[k] that is different from the browser on the payment application, and cause the different browser to display a screen for accepting payment without using the payment application. Note that the "browser different from the browser included in the payment application" is an example of the "second browser." Also, the "screen for accepting payment" is an example of the "second screen."

[0041] When 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 browser on the terminal 40[k], which is different from the browser on the payment application, to display a screen providing information on updating the payment application.

[0042] Alternatively, when 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 on the payment application, and cause the different browser to display a screen for accepting payment without using the payment application. As in the above, the "browser different from the browser included in the payment application" is an example of the "second browser." Also, the "screen for accepting payment" is an example of the "second screen."

[0043] When the first determination unit 113 determines that the version of the payment application of terminal 40[k] is equal to or higher than the threshold value and the second determination unit 114 determines that the payment application is installed in terminal 40[k], the display control unit 115 causes the browser of the payment application to display a screen for accepting payment. As one example, the "screen for accepting payment" may include an operator to be operated to accept payment using the payment application and an operator to be operated to make payment without using the payment application.

[0044] 1-2: Operation of the First Embodiment 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 the user U[k] displays a shop page provided by the shop server 20.

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

[0047] In step S3, the terminal 40[k] transmits to the store server 20 a purchase instruction to purchase the above-mentioned product or service.

[0048] In step S4, the store server 20 transmits a payment request for payment of the price of the product or service for which the user U[k] has offered to pay, to the payment server 30. The payment request includes payment data indicating the content of the payment.

[0049] In step S5, the payment server 30 transmits the payment data to the management server 10. The processing device 11 included in the management server 10 functions as the acquisition unit 112 to acquire the payment data.

[0050] In step S6, the management server 10 transmits a start-up instruction to the terminal 40[k] to instruct the terminal 40[k] to start up a payment application. More specifically, the processing device 11 of the management server 10 transmits the start-up instruction to the terminal 40[k] by functioning as the communication control unit 111. The start-up instruction includes a link associated with a site provided by the management server 10.

[0051] In step S7, the terminal 40[k] starts a payment application. The terminal 40[k] also uses a 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, the terminal 40[k] transmits terminal data to the management server 10. The terminal data includes the version of the payment application. The processing device 11 included in the management server 10 functions as the acquisition unit 112 to acquire the terminal data.

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

[0054] If the version of the payment application installed on the terminal 40[k] is equal to or higher than the threshold value corresponding to the type of payment, the management server 10 executes the operation of step S10.

[0055] On the other hand, if the version of the payment application installed on terminal 40[k] is less than the threshold corresponding to the type of payment, as an example, the processing device 11 provided in the management server 10 functions as a display control unit 115 to cause terminal 40[k] to display screen SI1 informing the user about updating the payment application.

[0056] 6 is a diagram showing an example of a screen SI1 that guides a user to update a payment application. The screen SI1 includes an icon IC1. The user U[k] updates the payment application by operating the icon IC1.

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

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

[0059] On the other hand, when the payment application is not installed on the terminal 40[k], as an example, the processing device 11 provided in the management server 10 functions as a display control unit 115 to display a screen SI2 that guides the user to install the payment application on a browser provided on the terminal 40[k] that is different from the browser provided in the payment application.

[0060] 7 is a diagram showing an example of a screen SI2 that guides the user to install a payment application. The screen SI2 includes an icon IC2. The user U[k] operates the icon IC2 to install the payment application in the terminal 40[k].

[0061] In step S11, the management server 10 transmits the payment data to the terminal 40[k]. More specifically, the processing device 11 of the management server 10 functions as the communication control unit 111 to transmit the payment data to the terminal 40[k].

[0062] In step S12, the terminal 40[k] transmits to the payment server 30 a screen display request to request that the terminal 40[k] display an approval confirmation screen SI3 in step S14 described below.

[0063] In step S13, the payment server 30 transmits screen data for displaying the above-mentioned consent confirmation screen SI3 to the terminal 40[k].

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

[0065] FIG. 8 is a diagram showing an example of the consent confirmation screen SI3. The consent confirmation screen SI3 displays the store selling the product or service to be paid and the price. The store selling the product or service and the price are included in the payment data acquired by the terminal 40[k] from the management server 10 in step S11. The consent confirmation screen SI3 also includes icons IC3[1], IC3[2], and IC3[3]. The user U[k] consents to paying the price using a payment application by operating the icon IC3[1]. The user U[k] also consents to paying the price without using a payment application by operating the icon IC3[2]. The user U[k] also instructs to stop paying the price by operating the icon IC3[3].

[0066] In step S15, the terminal 40[k] transmits a payment request to the payment server 30 to request payment for the product or service, based on the operation of the user U[k] in step S14.

[0067] In step S16, the settlement server 30 executes the settlement of the price of the product or service.

[0068] In step S17, the payment server 30 transmits to the terminal 40[k] screen data for displaying an approval completion screen SI4 indicating that the above approval has been completed.

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

[0070] 9 is a diagram showing an example of an approval completion screen SI4. The approval completion screen SI4 indicates that the display screen will automatically transition to a store site screen to complete the procedure. The approval completion screen SI4 also includes an icon IC4. If the display screen does not automatically transition to the store screen, the user U[k] operates the icon IC4 to transition the approval completion screen SI4 to the store site screen.

[0071] In step S19, the terminal 40[k] sends a screen display request to the store server 20 to request that the store server 20 display a store approval completion screen on the terminal 40[k] in step S21 described below, which indicates that approval at the store site has been completed.

[0072] In step S20, the store server 20 transmits screen data for displaying the above-mentioned store approval completion screen to the terminal 40[k].

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

[0074] In addition, in the above step S9, if it is determined that the version of the payment application installed in terminal 40[k] is lower than the threshold corresponding to the type of payment, as another example, the processing device 11 provided in the management server 10 functions as a display control unit 115. The processing device 11 may start a browser provided in terminal 40[k] that is different from the browser provided in the payment application, and cause the browser to display an approval confirmation screen SI5 for approving the payment.

[0075] Fig. 10 is a diagram showing an example of an approval confirmation screen SI5. The approval confirmation screen SI5 shows a case where the price of a product or service is paid after being added to the telephone charge of the terminal 40[k] used as a mobile phone. The approval confirmation screen SI5 includes an input field BC5 and an icon IC5. The user U[k] approves the payment by inputting a PIN in the input field BC5 and operating the icon IC5.

[0076] FIG. 11 is a diagram showing an example of an approval completion screen SI6 displayed on a browser provided on terminal 40[k], which is different from the browser provided on the payment application, when user U[k] operates icon IC5 on approval confirmation screen SI5. The approval completion screen SI6 indicates that the display screen will automatically transition to a screen of the store site to complete the procedure. The approval completion screen SI6 also includes icon IC6. If the display screen does not automatically transition to the screen of the store site, user U[k] operates icon IC6 to transition the approval completion screen SI4 to the screen of the store site.

[0077] In addition, in the above step S10, if it is determined that the payment application is not installed in the terminal 40[k], the processing device 11 of the management server 10 may also function as the display control unit 115. In this case, the processing device 11 may also start a browser provided in the terminal 40[k] that is different from the browser provided in the payment application, and cause the browser to display an approval confirmation screen SI5 for approving the payment.

[0078] 1-3: Advantages 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 a terminal 40[k] requests a payment, the acquisition unit 112 acquires payment data indicating the content of the payment from the payment server 30 that executes the payment. When the acquisition unit 112 acquires the payment data, the communication control unit 111 transmits, to the terminal 40[k], a start instruction to instruct the terminal 40[k] to start an application used for the payment.

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

[0080] In the management server 10 according to this embodiment, the payment is a payment for a product or a role. When a purchase offer for a product or a service is sent from the terminal 40[k] to the store server 20 that provides a store site that sells the product or service, the acquisition unit 112 acquires the payment data from the payment server 30 that cooperates with the store server 20.

[0081] Since the management server 10 in this embodiment has the above-mentioned configuration, it is possible to determine whether the version of the payment application is appropriate for the type of payment, triggered by obtaining payment data from the payment server 30.

[0082] Furthermore, in the management server 10 according to this embodiment, the above-mentioned start-up instruction includes a link linked to the first site provided by the management server 10. When the terminal 40[k] uses the first browser included in the above-mentioned payment application to access the first site via the above-mentioned link, the acquisition unit 112 acquires terminal data from the terminal 40[k].

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

[0084] Moreover, the management server 10 according to this embodiment further includes a display control unit 115. When the first determination unit 113 determines that the version is equal to or greater than a threshold, the display control unit 115 causes a first browser included in the application to display a first screen for accepting the payment.

[0085] Since the management server 10 according to this embodiment has the above-mentioned configuration, if the version of the payment application is equal to or higher than a threshold, payment can be made using the payment application.

[0086] In addition, in the management server 10, when the first judgment unit 113 judges that the above version is less than the threshold value, the display control unit 115 launches a second browser provided in the terminal 40[k], which is different from the above first browser, and causes the second browser to display a second screen for accepting the above payment.

[0087] Since the management server 10 in this embodiment has the above-mentioned configuration, if the version of the payment application is below a threshold, online payment is possible using a browser on the terminal 40[k] itself, rather than the payment application.

[0088] 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 in the terminal 40[k] based on whether or not the above first site is accessed by using the above first browser.

[0089] The management server 10 according to this embodiment has the above-described configuration, and therefore, as an example, when the terminal 40[k] is an Android terminal, it can determine whether or not a payment application is installed.

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

[0091] The management server 10 according to this embodiment has the above-mentioned configuration, and therefore, as an example, when the terminal 40[k] is an iPhone, it can determine whether or not a payment application is installed.

[0092] In addition, in the management server 10, when the second determination unit 114 determines that the above application is not installed in the terminal 40[k], the display control unit 115 launches a second browser provided in the terminal 40[k] and different from the first browser, and causes the second browser to display a second screen for accepting the above payment.

[0093] Since the management server 10 in this embodiment has the above-mentioned configuration, if a payment application is not installed, online payment can be made using a browser on the terminal 40[k] itself, rather than using the payment application.

[0094] The management method according to the present embodiment also includes, when a user U[k] of terminal 40[k] requests payment, acquiring payment data indicating the content of the payment from the payment server 30 that executes the payment. The management method according to the present embodiment also includes, when acquiring the payment data, sending to terminal 40[k] a startup instruction to instruct the startup of an application used for the payment. The management method according to the present embodiment also includes, when acquiring terminal data including the version of the application from terminal 40[k], determining whether the acquired version is equal to or greater than a threshold corresponding to the type of payment.

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

[0096] 2:Other (1) In the above-described embodiment, ROM and RAM are given as examples of storage device 12, but the storage device 12 may also be a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory device (e.g., a card, a stick, a key drive), a CD-ROM (Compact Disc-ROM), a register, a removable disk, a hard disk, a floppy (registered trademark) disk, a magnetic strip, a database, a server, or any other suitable storage medium.

[0097] (2) In the above-described embodiments, the described information, signals, etc. may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0098] (3) In the above-described embodiment, the input / output information, etc. may be stored in a specific location (e.g., memory) or may be managed using a management table. The input / output information, etc. may be overwritten, updated, or added. The output information, etc. may be deleted. The input information, etc. may be transmitted to another device.

[0099] (4) In the above-described embodiments, the determination may be made based on a value represented using one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0100] (5) The order of the process steps, sequences, flow charts, etc. illustrated in the above-described embodiments may be changed without causing any inconsistency. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0101] (6) Each function illustrated in Fig. 1 to Fig. 11 is realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device that is physically or logically combined, or may be realized by using two or more devices that are physically or logically separated and directly or indirectly connected (for example, by wire, wirelessly, etc.). The functional block may be realized by combining the one device or the multiple devices with software.

[0102] (7) The programs exemplified in the above-described embodiments 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., regardless of whether they are called software, firmware, middleware, microcode, hardware description language, or by other names.

[0103] Additionally, software, instructions, information, etc. may be transmitted or received over a transmission medium. For example, if the software is transmitted from a website, server, or other remote source using wired and / or wireless technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave, etc.), then these wired and / or wireless technologies are included within the definition of transmission media.

[0104] (8) In each of the above embodiments, the terms “system” and “network” are used interchangeably.

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

[0106] (10) In the above-described embodiments, 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, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable term. In this disclosure, the terms "mobile station", "user terminal", "user equipment (UE)", "terminal", etc. may be used interchangeably.

[0107] (11) In the above-mentioned embodiments, the terms "connected" and "coupled" or any variation thereof refer to 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" to 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, "connected" may be read with "access". As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and light (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0108] (12) In the above embodiments, the phrase "based on" does not mean "based only on," unless otherwise specified. In other words, the phrase "based on" means both "based only 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" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), and the like. In addition, "judgment" and "decision" can include considering resolving, selecting, choosing, establishing, comparing, etc., to be a "judgment" or "decision." In other words, "judgment" and "decision" can include considering some action to be a "judgment" or "decision." In addition, "judgment" can be interpreted as "assuming," "expecting," "considering," etc.

[0110] (14) In the above embodiments, when "include," "including," and variations thereof are used, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, the term "or" used in this disclosure is not intended to be an exclusive or.

[0111] (15) In this disclosure, where articles have been added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the 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 "combined" may also be interpreted in the same way as "different."

[0113] (17) Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched according to execution. In addition, notification of specific information (e.g., notification that "X is the case") is not limited to explicit notification, but may be implicit (e.g., not notifying the specific information).

[0114] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented as modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is for illustrative purposes only and does not have any limiting meaning on the present disclosure. [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 judgment unit, 114...second judgment unit, 115...display control unit, AD...application data, ADB...application 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...approval confirmation screen, SI4...approval completion screen, SI5...approval confirmation screen, SI6...approval completion screen, U...user

Claims

1. an acquisition unit that acquires, when a user of the terminal requests payment, payment data indicating the content of the payment from a payment server that executes the payment; a communication control unit that transmits, when the acquisition unit acquires the payment data, a startup instruction to the terminal to instruct the terminal to start an application used for the payment; a first determination unit that, when terminal data including a version of the application is acquired from the terminal, determines whether the acquired version is equal to or greater than a threshold corresponding to a type of payment; Equipped with The settlement is a payment for goods or services, When an offer to purchase the product or service is transmitted from the terminal to a store server providing a store site selling the product or service, the acquisition unit acquires the payment data from the payment server linked to the store server. Management server.

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

3. and a display control unit that, when the first determination unit determines that the version is equal to or greater than a threshold, causes a first browser included in the application to display a first screen for accepting the payment. The management server according to claim 1 .

4. and a display control unit that starts a second browser provided on the terminal, different from the first browser, when the first determination unit determines that the version is less than a threshold value, and causes the second browser to display a second screen for accepting the payment. The management server according to claim 2.

5. a second determination unit that determines whether or not the application is installed in the terminal based on whether or not the first site is accessed by using the first browser; The management server according to claim 2.

6. a second determination unit that determines whether the application is installed in the terminal depending on whether the acquisition unit has acquired the terminal data within a preset time period after the communication control unit has transmitted the start instruction, The management server according to claim 2.

7. and a display control unit that, when it is determined by the second determination unit that the application is not installed in the terminal, starts a second browser that is different from the first browser and causes the second browser to display a second screen for accepting the payment. The management server according to claim 5 .

8. and a display control unit that, when it is determined by the second determination unit that the application is not installed in the terminal, starts a second browser that is different from the first browser and causes the second browser to display a second screen for accepting the payment. The management server according to claim 6.

9. When a user of the terminal requests payment, acquiring payment data indicating the content of the payment from a payment server that executes the payment; When the payment data is acquired, transmitting to the terminal a start instruction for instructing the terminal to start an application used for the payment; When terminal data including a version of the application is acquired from the terminal, determining whether the acquired version is equal to or greater than a threshold corresponding to a type of payment; Including, The settlement is a payment for goods or services, When an offer to purchase the product or service is transmitted from the terminal to a store server providing a store site selling the product or service, the payment data is acquired from the payment server linked to the store server. Management method.

Images