Method for controlling application programs, payment systems, and terminal devices

Abstract

To improve user convenience when using multiple applications. [Solution] An application program that operates in cooperation with other application programs on a terminal device, wherein the terminal device receives settings related to the font size of the application program, stores the received settings related to the font size as font size setting information in a storage unit, and provides the font size setting information stored in the storage unit to the other application program in response to a request for the font size setting information from the other application program.

Description

Technical Field

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

Background Art

[0002] Conventionally, in an electronic payment service using a user terminal device owned by a user, in addition to the function of electronic payment, a system that provides various functions together has been realized. For example, in Patent Document 1, an information processing system that proposes the use of a point management application according to the payment status of a payment application has been proposed. Further, in Patent Document 2, an information processing system that proposes the use of an insurance application that promotes insurance enrollment according to the payment status of a payment application has been proposed.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the information processing systems described in Patent Documents 1 and 2, various types of information set by the user were not shared between the two applications. For this reason, for example, when the user set the font size of the screen display when using one application and then used the other application, the font size set by the user was not reflected in the screen display of the other application, and the usability of the application might deteriorate.

[0005] This invention has been made in consideration of these circumstances, and one of its objectives is to provide an application program, an information processing system, and an information processing method that can improve user convenience when using multiple applications. [Means for solving the problem]

[0006] One aspect of the present invention is an application program that operates in cooperation with other application programs on a terminal device, wherein the terminal device receives settings related to the font size of the application program, stores the received settings related to the font size as font size setting information in a storage unit, and provides the font size setting information stored in the storage unit to the other application program in response to a request for the font size setting information from the other application program. [Effects of the Invention]

[0007] According to one aspect of the present invention, it is possible to provide an application program, a payment system, and a control method for a terminal device that can improve user convenience when using multiple applications. [Brief explanation of the drawing]

[0008] [Figure 1] This diagram shows an example of a configuration for implementing an electronic payment service. [Figure 2] This is a sequence diagram (part 1) illustrating the general flow of electronic payments. [Figure 3] This is a sequence diagram (part 2) illustrating the general flow of electronic payments. [Figure 4] This is a diagram showing the configuration of payment server 100. [Figure 5] This figure shows an example of the contents of user information 172. [Figure 6] This figure shows an example of the contents of merchant / store information 176. [Figure 7] This is a diagram showing the configuration of the user terminal device 200. [Figure 8] This is an example of the IM1 top screen of payment app 20. [Figure 9] This sequence diagram shows an example of the process for setting the font size in the payment app 20 and the display process for the help mini-app 30A. [Figure 10] These are examples of the settings screen IM2 and font size setting screen IM3 of the payment app 20. [Figure 11] This is an example of the information screen IM4 of the payment app 20 and the help mini-app screen IM01 of the help mini-app 30A. [Modes for carrying out the invention]

[0009] The following describes embodiments of the application program, payment system, and terminal device control method of the present invention with reference to the drawings. Various devices such as "servers" that appear below, which provide services to users or perform internal analysis, may be implemented by a distributed group of devices, and the operators of each device may be different. Furthermore, the owner of the hardware of the devices (the provider of the cloud server) and the operator that actually operates them may also be different. An electronic payment service is a service that supports payment for the purchase of goods and services at a store. A store is, for example, a physical store (a real store) that exists in the real world, but it may also include a virtual store for e-commerce. A virtual store may include one provided by an entity different from the operator of the electronic payment service. In that case, when settling a purchase at a virtual store, the system is controlled to transition to the interface screen of the electronic payment service. In an electronic payment service, a store is treated as belonging to, for example, a merchant (brand), and processing such as payment when a purchase is made at a store is mainly carried out between the user and the merchant. Alternatively, processing such as payment may be carried out between the user and the store.

[0010] [Electronic payment service] Figure 1 shows an example of a configuration for realizing an electronic payment service. The electronic payment service is implemented with a payment server 100 at its center. The payment server 100 communicates with, for example, one or more user terminal devices 200, one or more first store terminal devices 50, and one or more second store terminal devices 70 via a network NW. The network NW includes, for example, the internet, a LAN (Local Area Network), a wireless base station, and provider equipment.

[0011] The user terminal device 200 is a portable terminal device such as a smartphone or tablet. The user terminal device 200 is a computer device having at least optical reading functionality, communication functionality, display functionality, input acceptance functionality, and program execution functionality. In the following description, the components for realizing these functions will be referred to as a camera, communication device, touch panel, CPU (Central Processing Unit), etc. In the user terminal device 200, a payment application (hereinafter referred to as the payment app) 20 that provides electronic payment services is executed by a processor such as the CPU, and it operates in cooperation with the payment server 100 to provide electronic payment services to the user. In addition, a mini-application (hereinafter referred to as the mini-app) 30 is executed by a processor such as the CPU in the user terminal device 200, and it operates in cooperation with the payment server 100 to provide services related to the mini-app to the user. The payment app 20 is installed on the user terminal device 200 from an application store, for example, and controls the camera, communication device, touch panel, etc. The payment app 20 operates in cooperation with the mini-app 30 on the user terminal device 200. Payment app 20 is an example of a "first application program".

[0012] A mini-app operates on the payment app 20 as a platform (runs on the payment app 20) and provides some kind of service (a service related to electronic payment). Mini-apps 30 include, for example, a help mini-app 30A, a points management app, a coupon management app, a stamp card management app, etc. Mini-apps 30 have a mini-app SDK (Software Development Kit) built into them. The mini-app SDK develops mini-apps by referring to the SDK (Software Development Kit), which is, for example, a program and technical documentation for app development provided by the administrator of the payment app 20. For example, when the payment app 20 is installed on the user terminal device 200, some or all of the mini-app may be installed, or some or all of the mini-app may be installed from a service server corresponding to the mini-app. For example, when a mini-app is started, the mini-app may access an external service server (not shown) that provides a service corresponding to the mini-app, and the mini-app and the external service server may cooperate to provide a service to the user. Mini-apps 30 are examples of "other application programs" and "second application programs". Help Mini App 30A is an example of an "application program that provides at least one function of providing information on how to use electronic payment services and receiving questions."

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

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

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

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

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

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

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

[0020] [Payment Server] Figure 4 is a diagram of the configuration of the payment server 100. The payment server 100 includes, for example, a communication unit 110, a payment content provision unit 120, a payment processing unit 130, an information management unit 140, a mini-application management unit 150, and a storage unit 170. Components other than the communication unit 110 and the storage unit 170 are realized, for example, by a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuitry) such as LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), and GPU (Graphics Processing Unit), or by the cooperation of software and hardware. The program may be stored in advance on a storage device such as an HDD (Hard Disk Drive) or flash memory (a storage device equipped with a non-transient storage medium), or it may be stored on a removable storage medium such as a DVD or CD-ROM (a non-transient storage medium) and installed on the storage device when the storage medium is inserted into the drive device.

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

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

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

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

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

[0026] Figure 6 shows an example of the contents of the merchant / store information 176. The merchant / store information 176 includes, for example, a first table 176A in which merchant IDs and store IDs are associated with store URLs, a second table 176B in which merchant names and sales figures are associated with merchant IDs, and a third table 176C in which store names are associated with store IDs. In addition to this information, the merchant / store information 176 may also include information such as the merchant or store category, store location, and payment patterns.

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

[0028] The mini-application management unit 150 manages the provision of functions for various mini-applications. The mini-application management unit 150 includes, for example, an authentication unit 151 and a mini-application content provision unit 152.

[0029] The authentication unit 151 performs user authentication processing when various mini-applications are launched on the user terminal device 200. For example, when various mini-applications are launched during the processing of the payment application 20 running on the user terminal device 200 (for example, when a link to launch a help mini-application such as "Help / FAQ" is clicked on the screen of the payment application 20), the authentication unit 151 performs general authentication processing using JWT (JASON WEB TOKEN) authentication technology. In this case, the payment server 100 (authentication unit 151) takes on the role of an ID provider, authenticates the user on behalf of the help mini-application 30A, and issues a JWT (token) for that authentication information.

[0030] The mini-application content provider unit 152, for example, has the functionality of a web server and provides information (content) for displaying various screens of the mini-application service to the user terminal device 200. The mini-application content provider unit 152 reads the necessary content from the mini-application content information 178 as appropriate and provides it to the user terminal device 200. The user terminal device 200 receives various inputs from the user while the content is being played by the mini-application 30 and transmits them to the payment server 100.

[0031] [Electronic payment] When the payment processing unit 130 obtains payment information from the user terminal device 200 or the first store terminal device 50, it refers to the user information 172 to obtain the user's "payment method setting". For users whose "payment method setting" is set to "charge balance", the payment processing unit 130 performs electronic payment as follows. For example, the payment processing unit 130 performs electronic payment by decreasing the charge balance, which is managed in association with the user ID, and increasing the value of the merchant's sales proceeds item. The merchant's sales proceeds item value is not used as electronic money itself, for example, but rather the amount corresponding to the sales proceeds item value is transferred to the bank account in a cycle according to the agreement between the merchant and the electronic payment service. The merchant may also receive the sales proceeds as electronic money. In this case, the payment server 100 manages the account (wallet) corresponding to the merchant ID, the electronic money balance of the account, and the sales proceeds history for each payment method in association.

[0032] The payment processing unit 130 performs electronic payment as follows for users whose "settings information" is set to "credit payment". Credit payment is a payment method in cooperation with a credit card company, which is a separate entity from the operator of the electronic payment service, and allows electronic payment that does not depend on the charge balance within the credit limit. In order to use the credit payment service, it may be required to obtain a credit card provided by the operator of the electronic payment service. The payment processing unit 130 adds the payment amount to the credit payment usage amount in the user information 172 and subtracts the above payment amount from the available credit payment amount. If the payment amount exceeds the available credit payment amount, an error notification is sent back to the payment app. The amount used by credit payment is settled, for example, in a lump sum for one month on the payment date of the following month, for example, by direct debit from a bank account. This processing is performed by the operator of the credit card company.

[0033] [User terminal device] Figure 7 is a diagram of the user terminal device 200. The user terminal device 200 includes, for example, a communication unit 210, a control unit 220, a display unit 230, an input unit 240, and a storage unit 270. The control unit 220 is implemented, for example, by a hardware processor such as a CPU executing a program (software). Some or all of these components may be implemented by hardware (including circuitry) such as an LSI, ASIC, FPGA, or GPU, or by the cooperation of software and hardware. The program may be stored in advance in a storage device such as an HDD or flash memory (a storage device equipped with a non-transient storage medium), or it may be stored in a removable storage medium such as a DVD or CD-ROM (a non-transient storage medium) and installed in the storage device when the storage medium is mounted on a drive device.

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

[0035] The control unit 220 includes, for example, a font size setting unit 221. The font size setting unit 221 sets the font size (character size) used in the screen display of the payment application 20 in response to user input. The font size is defined, for example, by levels such as normal (default), large, and extra-large. Alternatively, the font size may be defined, for example, by a numerical value, symbol, etc., indicating the size of the characters.

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

[0037] The storage unit 270 can be an HDD, flash memory, RAM, etc. The storage unit 270 may also be a NAS device accessible by the user terminal device 200 via a network. The storage unit 270 stores the payment application 20, the mini-applications 30, and information used by these applications. For example, the storage unit 270 stores font size setting information FS as information managed by the payment application 20.

[0038] [App screen] Figure 8 shows an example of the top screen IM1 of the payment app 20. As shown in Figure 8, the top screen IM1 of the payment app 20 includes areas A1, A2, A3, and A4. Area A1 displays code images such as barcodes and QR codes (registered trademarks) used for smartphone payments. Area A2 displays various icons for instructing major smartphone payment operations such as charging and scanning. Area A3 displays various icons for launching various mini-apps that can be executed with the payment app 20. When the user selects (tap) one of the icons for launching a mini-app, the payment app 20 launches the mini-app corresponding to the selected icon. Area A4 displays various icons for instructing major smartphone payment operations such as payment and account settings.

[0039] [Sequence Diagram] The following describes the process of linking the payment app 20 and the mini-app 30. In the following description, the case where the mini-app 30 is the help mini-app 30A will be used as an example. Figure 9 is a sequence diagram showing an example of the font size setting process for the payment app 20 and the display process for the help mini-app 30A. Figure 10 is an example of the settings screen IM2 and the font size setting screen IM3 of the payment app 20. Figure 11 is an example of the information screen IM4 of the payment app 20 and the help mini-app screen IM01 of the help mini-app 30A. The process shown in the sequence diagram in Figure 9 is started when the user taps (selects) the "Change Font Size" link on the settings screen IM2 of the payment app 20 shown in Figure 10.

[0040] First, the payment application 20 running on the user terminal device 200 displays the font size setting screen IM3 on the display unit 230 (step S101). Next, the payment application 20 accepts the font size setting of the payment application 20 in response to the instruction entered by the user via the input unit 240 (step S103). Next, the payment application 20 associates the accepted font size setting of the payment application 20 with the user's account ID and stores it in the font size setting information FS of the storage unit 270 (step S105).

[0041] As shown in Figure 10, when the "Change Font Size" link is tapped (selected) on the settings screen IM2 of the payment application 20 displayed on the display unit 230 of the user terminal device 200, the font size setting screen IM3 is displayed. On this font size setting screen IM3, the font size setting (selection of "Normal," "Large," or "Extra Large") can be selected. In Figure 10, "Extra Large" is shown as the selected font size. By accepting such a selection, the font size setting for each user is stored in the font size setting information FS.

[0042] Next, the payment application 20 accepts an operation to launch the help mini-application 30A in response to the instructions entered by the user via the input unit 240 (step S107). In response to this launch operation, the help mini-application 30A sends an authentication request to the payment server 100 (step S109). Next, the authentication unit 151 of the payment server 100 makes an authentication decision in response to the authentication request sent from the help mini-application 30A, determining whether to accept the authentication request or not (authentication success / authentication failure) (step S111). Next, the authentication unit 151 of the payment server 100 sends the authentication result to the user terminal device 200 (step S113).

[0043] If authentication is successful, the help mini-app 30A requests the payment app 20 for font size setting information associated with the user (step S115). In response to this request, the payment app 20 reads the font size setting information associated with the user from the font size setting information FS in the storage unit 270 (step S117) and provides the read font size setting information (step S119). For example, the help mini-app 30A sends a request for font size setting information (API request) to the payment app 20 by using the API (Application Programming Interface) provided by the mini-app SDK (by calling getFontsize). In response to the API request via the API, the payment app 20 reads the font size setting information associated with the user from the font size setting information FS in the storage unit 270 and sends the read font size setting information as an API response.

[0044] Next, the Help Mini App 30A uses the font size setting information provided by the Payment App 20 to set the font size used for displaying the Help Mini App 30A screen (step S121). For example, the Help Mini App 30A sets the font size for the Help Mini App 30A's text (Textview), the user interface of various buttons, and the Web header. Next, the Help Mini App 30A displays the Help Mini App screen on the display unit 230 according to the set font size (step S123). For example, if the font size is set to "extra large" in the font size setting screen IM3 of the Payment App 20, then, as shown in Figure 11, the information screen IM4 of the Payment App 20 will be displayed with the font size "extra large" according to this setting. When the Help Mini App 30A is launched on this information screen IM4 (when the "Help / Frequently Asked Questions" link is tapped (selected)), the Help Mini App screen IM01 will be displayed with the font size "extra large," just as the font size setting of the Payment App 20 ("extra large") was set. This allows users to see screens with the same font size when transitioning from the payment app 20 screen to the help mini-app 30A screen. This improves user convenience when using multiple applications.

[0045] As described above, the payment application 20 of this embodiment is an application program that operates in cooperation with the mini-application 30 on the user terminal device 200. The payment application 20 receives settings related to the font size of the payment application 20, stores the received settings related to the font size as font size setting information in the storage unit 270, and provides the font size setting information stored in the storage unit 270 to the mini-application 30 in response to a request for font size setting information from the mini-application 30. As a result, the payment application 20 and the mini-application 30 of this embodiment can standardize font size settings, improving user convenience when using multiple applications.

[0046] In the above embodiment, a configuration was described in which font size setting information is stored in the storage unit 270 of the user terminal device 200. However, the font size setting information may also be stored in the payment server 100 (a server that the user terminal device 200 can communicate with via the network NW). The font size setting information stored in the payment server 100 may, for example, associate the user's account ID with the font size set by the font size setting unit 221. In this case, the payment application 20 may, in response to a request for font size setting information from the mini-application 30, send an API request for font size setting information to the payment server 100 via an API, receive the font size setting information as an API response from the payment server 100, and provide the font size setting information received from the payment server 100 to the mini-application 30.

[0047] In the above embodiment, a configuration was described in which the font size setting is standardized between the payment application 20 and the mini-application 30. However, in addition to the font size, settings such as graphic displays (user interface displays) for buttons, font type, and font color may also be standardized. In this case, the payment application 20 may, for example, receive settings related to the graphic display of the payment application 20, store the received graphic display settings as graphic display setting information in the storage unit 270, and provide the graphic display setting information stored in the storage unit 270 to the mini-application 30 in response to a request for graphic display setting information from the mini-application 30.

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

[0049] 20 Payment Applications 30 Mini Applications 50. First store terminal device 70. Second store terminal device 100 Payment Servers 110 Communications Department 120 Payment Content Provision Department 130 Payment Processing Unit 140 Information Management Department 150 Mini-App Management Department 151 Certification Department 152 Mini-App Content Provision Department 170 Storage section 200 User terminal devices 210 Communications Department 220 Control Unit 221 Font Size Setting Section 230 Display section 240 Input section 270 Storage section

Claims

1. An application program that operates in cooperation with other application programs on a terminal device, wherein the application program is an application program that provides electronic payment services, and the other application programs are application programs that operate on the application program and provide services related to the electronic payment services. The application program is installed on the terminal device. The application program will accept settings regarding the font size, The received font size setting is stored in the storage unit as font size setting information. In response to an API request for font size setting information from the aforementioned other application program via the API (Application Programming Interface), the font size setting information stored in the storage unit is provided to the aforementioned other application program as an API response. Application program.

2. The aforementioned other application program is an application program that provides at least one function of providing information on how to use the electronic payment service and receiving questions. The application program according to claim 1.

3. The storage unit is provided in the terminal device, The application program according to claim 1 or 2.

4. The storage unit is provided in a server that the terminal device can communicate with via a network. The application program is installed on the terminal device. In response to an API request for font size setting information from the aforementioned other application program, the API is used to send the API request for font size setting information to the server, and the server receives the font size setting information as an API response. The font size setting information received from the server is provided to the other application program. The application program according to claim 1 or 2.

5. The aforementioned terminal device, The application program accepts settings related to the graphic display, The received graphic display settings are stored in the storage unit as graphic display setting information. In response to a request for graphic display setting information from the aforementioned other application program, the storage unit is made to provide the graphic display setting information stored in the storage unit to the aforementioned other application program. The application program according to claim 1 or 2.

6. A payment server that handles electronic payments, A first application program and a second application program that operate in cooperation with each other on a terminal device that can communicate with the payment server via a network, A payment system comprising the following: the first application program is an application program that provides electronic payment services, and the second application program is an application program that operates on the first application program and provides services related to the electronic payment services. The first application program is installed on the terminal device. The first application program accepts settings regarding the font size, The received font size setting is stored in the storage unit as font size setting information. In response to an API request for font size setting information from the second application program via the API (Application Programming Interface), the font size setting information stored in the storage unit is provided to the second application program as an API response. The second application program is installed on the terminal device. The screen is displayed using the font size setting information provided by the first application program. Payment system.

7. A control method for a terminal device in which a first application program and a second application program operate in cooperation with each other, wherein the first application program is an application program that provides electronic payment services, and the second application program is an application program that operates on the first application program and provides services related to the electronic payment services. The terminal device executes the first application program, The first application program accepts the font size settings, The received font size setting is stored in the storage unit as font size setting information. In response to an API request for font size setting information from the second application program via the API (Application Programming Interface), the font size setting information stored in the storage unit is provided to the second application program as an API response. A method for controlling terminal devices.

Images