Information processing device

Abstract

Usability can be improved. [Solution] An information processing device is provided that includes a receiving unit that receives an identification code from a terminal device, which includes identification information for identifying a remittance destination user in an electronic payment server that provides remittance services, and transition information for transitioning to a screen for remittance to the remittance destination user, and a control unit that controls the writing of the identification information and transition information into a communication control medium that can communicate via NFC (Near Field Communication).

Description

[Technical field]

[0001] The present disclosure relates to Information processing device This is regarding. [Background technology]

[0002] Cashless payments, which are payments made without using currency when paying for goods or services, are becoming more and more common. In particular, electronic payments using payment applications (hereinafter referred to as electronic payment apps) that can be installed on terminal devices such as smartphones are attracting attention due to their high convenience.

[0003] Patent Document 1 discloses a method for performing payment at a store by reading store identification information and the like from a Near Field Communication (NFC) tag placed in the store. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2021-135805 Summary of the Invention [Problem to be solved by the invention]

[0005] However, the above-mentioned conventional techniques leave room for improvement in terms of improving the usability of remittance services.

[0006] An object of the present disclosure is to improve usability. [Means for solving the problem]

[0007] An information processing device according to one embodiment of the present disclosure is characterized in that it comprises a receiving unit that receives from a terminal device an identification code including identification information for identifying a remittance destination user in an electronic payment server that provides a remittance service and including transition information for transitioning to a screen for remittance to the remittance destination user, and a control unit that controls writing of the identification information and the transition information into a communication control medium capable of communication via NFC (Near Field Communication). Effect of the Invention

[0008] According to the present disclosure, it is possible to improve usability. [Brief description of the drawings]

[0009] [Figure 1] FIG. 13 is a diagram illustrating an example of information processing. [Diagram 2] FIG. 1 illustrates an example of a system configuration. [Diagram 3] FIG. 2 is a block diagram showing an example of a hardware configuration of an information processing device. [Figure 4] FIG. 2 is a diagram illustrating an example of a software configuration of an electronic payment server. [Diagram 5] FIG. 2 is a diagram showing an example of electronic account information stored in an account database. [Figure 6] FIG. 13 is a diagram showing an example of remittance information stored in the PS user information database. [Figure 7] FIG. 4 is a diagram showing an example of terminal identification information stored in a terminal identification information database. [Figure 8] FIG. 2 illustrates an example of a software configuration of a terminal device. [Figure 9] FIG. 11 is a sequence diagram showing an example of a flow of information processing. [Figure 10] FIG. 13 is a diagram showing an example of a screen displayed on a remittance source terminal device. [Figure 11] FIG. 13 is a diagram showing an example of a screen displayed on a remittance destination terminal device. [Figure 12]11 is a flowchart illustrating an example of a process executed by a terminal device. [Figure 13] FIG. 13 is a diagram illustrating an example of information processing. [Figure 14] FIG. 2 is a diagram illustrating an example of a software configuration of an electronic payment server. [Figure 15] FIG. 13 is a diagram showing an example of remittance information stored in a PS user information DB. [Figure 16] FIG. 4 is a diagram showing an example of terminal identification information stored in a terminal identification information DB. [Figure 17] FIG. 11 is a sequence diagram showing an example of a flow of information processing. [Figure 18] FIG. 13 is a diagram showing an example of a screen displayed on a remittance source terminal device. [Figure 19] FIG. 13 is a diagram showing an example of a screen displayed on a remittance destination terminal device. [Figure 20] FIG. 2 is a diagram illustrating an example of a software configuration of an electronic payment server. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Preferred embodiments of an information processing device, an information processing method, a program, and an information processing system according to the present disclosure will be described in detail below with reference to the drawings. Note that the information processing device, the information processing method, the program, and the information processing system according to the present disclosure are not limited to the following embodiments. Also, the same components in the following embodiments are given the same reference numerals, and duplicated descriptions will be omitted.

[0011] <First embodiment> [1. An example of a possible case] Applications that can be installed in terminal devices such as smartphones include electronic payment applications, etc. In the following description, applications may be referred to simply as apps.

[0012] Electronic payment apps are operated and managed by service providers that provide electronic payment services, etc. Electronic payment apps can provide not only electronic payment services for making payments for goods or services, but also remittance services for exchanging digitalized currency (hereinafter referred to as electronic money) between users.

[0013] Remittance services enable monetary transactions without the intervention of financial institutions such as banks, and can be implemented on portable information processing devices such as smartphones, so they are expected to be used with a high degree of freedom. As a concrete example of using a remittance service, consider the case of giving pocket money. A first user can use the remittance service of an electronic payment app to send electronic money equivalent to the pocket money to a specified second user.

[0014] Unlike electronic payment services, remittance services allow electronic money to be exchanged anywhere and at any time. Electronic payment services are often used when paying for things in stores, and are subject to significant limitations in terms of location and time. On the other hand, as mentioned above, remittance services allow electronic money to be exchanged if the sender can specify the recipient.

[0015] Some terminal devices have a function capable of transmitting and receiving data by short-distance wireless communication such as NFC (Near Field Communication) (hereinafter referred to as short-distance wireless communication function). Such terminal devices can receive stored data from a communication control medium (hereinafter referred to as a wireless tag) having an IC (Integrated Circuit) chip, an antenna coil, and the like, which can communicate according to a short-distance wireless communication standard. Usability can be improved by combining a wireless tag with a terminal device having a short-distance wireless communication function.

[0016] For example, as disclosed in the above-mentioned prior art (Patent Document 1), a wireless tag stores identification information of a store that has a contract with a service provider that provides electronic payment services, and transition information for transitioning to a payment screen for inputting the price. A terminal device having a short-range wireless communication function can then acquire the identification information and the transition information from the wireless tag via short-range wireless communication, thereby displaying a payment screen for inputting the price to be paid to the store.

[0017] However, unlike the use of electronic payment services, to use a remittance service, both the remittance recipient user and the remittance sender user must launch an electronic payment app and perform the necessary operations to transfer the money, which places a heavy burden on both users. This leaves room for improvement in terms of usability. For example, by receiving information from a wireless tag used to use the remittance service to transition to a screen where the remittance service can be used, the burden on users to perform operations to transfer money between individuals can be reduced. Below, we will explain ways of improving usability.

[0018] [2-1. About information processing devices] Fig. 1 is a diagram showing an example of information processing executed by an information processing device according to this embodiment. First, the information processing device according to this embodiment will be described with reference to Fig. 1. Note that the terminal device 101, the electronic payment server 102, and the writing device 103 in Fig. 1 are all types of information processing devices. Below, the information processing executed by the writing device 103 will be described together with the processing executed by the terminal device 101 and the electronic payment server 102.

[0019] (Regarding terminal device 101) The terminal device 101 is an information processing device used by a user who receives electronic payment services and a code output adjustment service (to be described later) and the like. In this embodiment, the terminal device 101 is described as a smartphone, but is not limited thereto. The terminal device 101 may be, for example, a tablet terminal, a notebook PC (Personal Computer), or a PDA (Personal Digital Assistant).

[0020] The terminal device 101 can display an identification code including user identification information for identifying a user, as well as a screen and other information, provided by the electronic payment server 102, via a web browser or an app. In this embodiment, an information code including an identification code indicating user identification information for identifying a user is referred to as a My Code. In addition to user identification information, various information can be embedded in the information code including the My Code in this embodiment during the process of generating the My Code. As an example, information for transitioning to a screen for using a remittance service provided by the electronic payment server 102 can be embedded in the My Code.

[0021] In this embodiment, My Code is described as a two-dimensional code, but it may be a one-dimensional code such as a barcode. In this embodiment, an image showing My Code is referred to as a My Code image.

[0022] (Regarding the electronic payment server 102) The electronic payment server 102 is an information processing device that provides an electronic payment service that performs electronic payment processing, a remittance service that performs remittance processing, and the like. For example, the electronic payment server 102 can be realized by a server device, a cloud system, or the like. By installing an electronic payment app on the terminal device 101, the user can use multiple services provided by the electronic payment server. Note that the electronic payment service and the remittance service can also be used by accessing a page provided by the electronic payment server 102 using a general web browser.

[0023] In this embodiment, a user who receives services from the electronic payment server 102 is called a PS user. A PS user is, for example, a user who has obtained an account in an electronic payment app. The obtained account is managed by the electronic payment server 102.

[0024] "Electronic payment processing" refers to the process of transferring electronic money equivalent to the payment amount from the electronic account of the PS User who received the goods or services to the electronic account of the store that provided the goods or services when making a payment at a store that has a contract with a service provider that provides electronic payment services. "Money transfer processing" refers to the process of transferring electronic money equivalent to the transfer amount from the electronic account of the PS User who sent the money to the electronic account of the PS User who received the money.

[0025] In response to a request to obtain MyCode from the terminal device 101, the electronic payment server 102 generates a MyCode image in which the PS user's identification information and the like are embedded, and provides the MyCode image to the terminal device 101 that made the request.

[0026] (Regarding the writing device 103) The writing device 103 is an information processing device that provides a user with a service for writing predetermined information to a wireless tag (hereinafter, referred to as a writing service). In this embodiment, the writing device 103 is described as a desktop PC (Personal Computer), but is not limited thereto. The writing device 103 may be, for example, a smartphone, a tablet terminal, a notebook PC, or a PDA (Personal Digital Assistant).

[0027] Furthermore, the writing device 103 can realize information processing, which will be described later, via other server devices or other cloud systems (not shown).

[0028] The writing device 103 can analyze the MyCode image received from the terminal device 101 and obtain information embedded in the MyCode image. The writing device 103 can also write the information obtained from the MyCode image to a wireless tag.

[0029] In this embodiment, a user who receives the writing service from the writing device 103 is referred to as a D user. The D user is, for example, a user managed by the writing device 103. Alternatively, the D user is a user who has obtained an account managed by a server device or cloud system (hereinafter referred to as a service-related device) that provides the writing service together with the writing device 103. The service-related device can provide a website or app screen for inputting a MyCode image. In addition, the service-related device can execute part of the processing executed by the writing device 103 described later. In the following description, when there is no need to distinguish between a PS user and a D user, both are collectively referred to as a terminal user.

[0030] (About wireless tags) The wireless tag in this embodiment includes, for example, an IC chip and an antenna coil. The wireless tag can write information received by short-range wireless communication into a storage unit of the IC chip. The wireless tag can also read information stored in the storage unit of the IC chip by short-range wireless communication and transmit the information using the antenna coil.

[0031] The storage unit of the wireless tag can store various information, such as information for identifying PS users managed by the electronic payment server 102, information for transitioning to a screen for using the remittance service, and information for controlling the terminal device 101.

[0032] [2-2. An example of information processing] (About information processing) An overview of information processing according to this embodiment will be described. The terminal device 101 transmits a request to obtain MyCode to the electronic payment server 102 (S1). For example, a terminal user operates the terminal device 101 to start an electronic payment app. Then, when the terminal device 101 detects an operation of the terminal user on the electronic payment app, it transmits a request to obtain MyCode to the electronic payment server 102.

[0033] In response to the request to obtain My Code received in S1, the electronic payment server 102 identifies the PS user who made the request and generates a My Code image for the identified PS user (S2). For example, the electronic payment server 102 generates a My Code image in which PS user identification information linked to the identified PS user and transition information for transitioning to a screen for using the remittance service are embedded.

[0034] When the electronic payment server 102 generates a My Code image in S2, it transmits the generated My Code image to the terminal device 101 of the PS user who made the acquisition request (S3). After that, when the terminal device 101 receives the My Code image in S3, it stores the received My Code image. The file format of the My Code image may be, for example, JPEG (Joint Photographic Experts Group), PNG (Portable Network Graphics), or GIF (Graphics Interchange Format).

[0035] The terminal device 101 transmits the My Code image received in S3 to the writing device 103 based on the operation of the terminal user (S4). For example, the terminal user accesses a website provided by a service-related device and performs a transmission operation to transmit the My Code image from the site. Alternatively, the terminal user launches an app provided by the service-related device and performs a transmission operation to transmit the My Code image. When the terminal device 101 detects the terminal user's operation to transmit the My Code image, it transmits the My Code image to the writing device 103 via the service-related device.

[0036] When the writing device 103 receives the My Code image in S4, it analyzes the My Code image (S5). For example, the writing device 103 analyzes the received My Code image and obtains identification information for identifying the PS user and transition information for transitioning to a screen for using the remittance service, both of which are embedded in the My Code image.

[0037] The writing device 103 writes the identification information and the transition information acquired in S5 to the wireless tag (S6). For example, the writing device 103 writes the identification information and the transition information to the wireless tag by wire or wirelessly.

[0038] The business providing the writing service sends the wireless tag on which the identification information and transition information were written in S6 to the D user who sent the MyCode image (S7).

[0039] [3. An example of an information processing system] Fig. 2 is a diagram showing an example of the configuration of an information processing system. The configuration of the information processing system according to this embodiment will be described with reference to Fig. 2. The information processing system has a terminal device 101, an electronic payment server 102, and a writing device 103. These devices are connected to each other via a network N in a wired or wireless manner so as to be able to communicate with each other. The network N is, for example, a LAN (Local Area Network) or a WAN (Wide Area Network) such as the Internet.

[0040] In FIG. 2, one terminal device 101 is shown for the sake of simplicity, but this is merely an example and is not limiting. That is, there may be two or more terminal devices in the information processing system. The terminal device 101 can connect to the network N via a wireless communication network such as LTE (Long Term Evolution), a 4G (4th Generation) mobile communication system, and a 5G mobile communication system, and communicate with other devices. The terminal device 101 can connect to the network N via short-range wireless communication such as Bluetooth (registered trademark) and wireless LAN, and communicate with other devices.

[0041] Information transmitted and received between the terminal device 101, the electronic payment server 102, the writing device 103, and other devices may be described in a script language such as JavaScript (registered trademark). Information transmitted and received may be described in a style sheet language such as CSS (Cascading Style Sheets) or a programming language such as Java (registered trademark). Information transmitted and received may be described in a markup language such as XML (Extensible Markup Language) or HTML (HyperText Markup Language).

[0042] [4. An example of the hardware configuration of an information processing device] The terminal device 101, electronic payment server 102, and writing device 103 described above are realized, for example, by an information processing device 300 ("an example of a computer") configured as shown in Fig. 3. Fig. 3 is a block diagram showing an example of the hardware configuration of the information processing device 300. The information processing device 300 has a CPU 301, a ROM 302, a RAM 303, a storage device 304, an input / output I / F 305, and a network I / F 306. The components are mutually connected by a system bus.

[0043] (About CPU301) The CPU 301 reads a program stored in the ROM 302 into the RAM 303 and executes the read program to realize various controls. The CPU 301 may be an MPU (Micro Processing Unit) or an ASIC (Application Specific Integrated Circuit). The CPU 301 may be an FPGA (Field Programmable Gate Array) or the like.

[0044] (About ROM302) The ROM 302 stores control programs such as a startup program for the information processing device 300.

[0045] (About RAM303) The RAM 303 temporarily stores control programs or data when the CPU 301 executes various controls. The RAM 303 is used as a work memory.

[0046] (Regarding storage device 304) The storage device 304 is a memory for storing applications, software, various data, and the like. Examples of the storage device 304 include a hard disk drive (HDD), a solid state drive (SDD), a flash memory, and storage. If the storage device 304 is the electronic payment server 102, it stores an account information database (hereinafter, the database is referred to as DB) described below, and the like. If the storage device 304 is the writing device 103, it stores D user information, my code information, analysis information, and the like described below.

[0047] (About input / output I / F305) The input / output I / F 305 is an interface for transmitting output information to an output device such as a display unit 310. Examples of the display unit 310 include a display and a projector. The display unit 310 may be provided outside the information processing device 300 as shown in FIG. 3, or may be provided in the information processing device 300.

[0048] The input / output I / F 305 is an interface for receiving input information from an input device such as the input unit 311. Examples of the input unit 311 include a mouse, a keyboard, a button, a touch panel, and an operation key. The input unit 311 may be provided outside the information processing device 300 as shown in FIG.

[0049] Furthermore, the input / output I / F 305 may be connected wirelessly or by wire to the display unit 310 and the input unit 311. The input / output I / F 305 may be configured separately as an input I / F and an output I / F.

[0050] (About network I / F306) The network I / F 306 is an interface for receiving data, etc. from other devices via the network N, and for transmitting data generated or stored in the information processing device 300, etc. to other devices via the network N.

[0051] It should be noted that the information processing device 300 is not limited to the configuration shown in Fig. 3. For example, the writing device 103 may be provided with a writing device for implementing a function of writing to a wireless tag.

[0052] The information processing device 300 may also include a media I / F (not shown). The media I / F reads programs and data stored in a storage device (not shown) connected by wire or wirelessly, and provides them to the CPU 301 via the RAM 303. The CPU 301 can read the provided programs from the storage device onto the RAM 303 via the media I / F, and execute the read programs. The storage device is, for example, an optical recording medium such as a DVD (Digital Versatile Disc) or a PD (Phase change rewritable Disk), or a magneto-optical recording medium such as an MO (Magneto-Optical disk). The storage device is, for example, a tape medium, a magnetic recording medium, or a semiconductor memory.

[0053] For example, when the information processing device 300 functions as the terminal device 101 , the CPU 301 of the information processing device 300 executes a program read onto the RAM 303 to realize various functions of the information processing device 300 .

[0054] The CPU 301 of the information processing device 300 reads these programs from a storage device and executes them, but as another example, these programs may be obtained from another device via a predetermined communication network. Furthermore, it goes without saying that the information processing device 300 is provided with a configuration necessary for realizing the information processing in this embodiment.

[0055] [5. An example of software configuration for electronic payment server] Fig. 4 is a diagram showing an example of the software configuration of the electronic payment server 102. The configuration of the electronic payment server 102 in this embodiment will be described with reference to Fig. 4. The electronic payment server 102 has a communication unit 400, a control unit 410, and a storage unit 420. The control unit 410 includes a receiving unit 411, a generating unit 412, a transmitting unit 413, a payment processing unit 414, and a remittance processing unit 415. The control unit 410 controls the entire electronic payment server 102. The storage unit 420 includes an account information DB 421.

[0056] (Regarding account information DB421) Electronic account information of PS users is stored in the account information DB 421. Fig. 5 is a diagram showing an example of electronic account information stored in the account information DB 421. The electronic account information has an account ID 501, a PS user ID 502, and an account balance 503.

[0057] The account ID 501 is an identifier for uniquely identifying the account of a PS user. The PS user ID 502 is an identifier for uniquely identifying a PS user. The account balance 503 indicates the balance of electronic money in the electronic account held by the PS user. The electronic money may be, for example, points or currency provided by a service provider that operates an electronic payment service, or may be electronically tradable currency provided by a country, such as Japanese yen or dollars. A PS user can pay for goods or services and transfer electronic money within the balance of his or her electronic account. The electronic payment server 102 manages the electronic account of the PS user by linking it to the PS user ID 502.

[0058] (Regarding communication unit 400) The communication unit 400 communicates with the terminal device 101 and other devices via the network N.

[0059] (Regarding the receiving unit 411) The receiving unit 411 receives, via the communication unit 400, a request to obtain MyCode and other information.

[0060] (Regarding the generation unit 412) The generation unit 412 generates a My Code image. That is, the generation unit 412 generates a My Code image in which the identification information and transition information of the PS user who has made the acquisition request are embedded.

[0061] (Regarding the transmitting unit 413) The transmission unit 413 transmits the MyCode image and other information.

[0062] (Regarding payment processing unit 414) When a PS user makes a payment at a store or the like, the payment processor 414 performs electronic payment processing based on an electronic payment method, which will be described later.

[0063] (About electronic payment methods) There are two types of electronic payment methods: a first electronic payment method in which a store clerk scans a code presented by a user and makes the payment based on the scanned information, and a second electronic payment method in which a user reads a code placed in the store and makes the payment based on the read information.

[0064] (Regarding remittance processing unit 415) The remittance processing unit 415 performs remittance processing based on the remittance procedure of the remitter PS user using an electronic payment application.

[0065] (Regarding remittance procedures) There are two remittance procedures: a first remittance procedure in which the sending PS user specifies the destination PS user and the amount to be remitted, and a second remittance procedure in which the sending PS user specifies the amount to be remitted with a specific PS user set as the destination.

[0066] In the first remittance procedure, the remittance source PS user operates the electronic payment app to specify the remittance destination PS user and the remittance amount on a remittance screen (not shown) displayed on the electronic payment app. The first remittance procedure places a heavy burden on the PS user because it may involve multiple screen transitions and multiple operations to specify the remittance destination PS user and the remittance amount.

[0067] On the other hand, the second remittance procedure does not require the user to specify the PS user as the remittance destination, and therefore imposes a smaller burden on the PS user than the first remittance procedure. Details of the second remittance procedure will be described later. Note that the electronic settlement server 102 in this embodiment can execute the remittance process from either the first remittance procedure or the second remittance procedure.

[0068] [6. An example of the software configuration of the writing device] FIG. 6 is a diagram showing an example of the software configuration of the writing device 103. The configuration of the writing device 103 in this embodiment will be described with reference to FIG. 6. The writing device 103 has a communication unit 600, a control unit 610, and a storage unit 620. The control unit 610 includes a receiving unit 611, an acquiring unit 612, and a writing unit 613. The control unit 610 controls the entire writing device 103. The storage unit 620 includes D user information 621, MyCode information 622, and analysis information 623. The writing device 103 can execute an analysis process for analyzing an image and a writing process to a wireless tag.

[0069] (About D User Information DB621) Information on D users is stored in the D user information DB 621. Fig. 7 is a diagram showing an example of the D user information stored in the D user information DB 621. The D user information has a D user ID 701 and address information 702.

[0070] D user ID 701 is an identifier for uniquely identifying D user. Address information 702 stores "AR01" as information indicating the address of D user. "AR01" includes information indicating the residence of D user expressed, for example, as prefecture and city / town / village. "AR01" may also include information such as a postal code. In other words, "AR01" includes information used to send a package to D user, and information that identifies the residence of D user.

[0071] (About My Code Information 622) Information about the My Code of user D is stored in the My Code information 622. Fig. 8 is a diagram showing an example of information about the My Code stored in the My Code information 622. The My Code ID 801 shown in Fig. 8 is an identifier for uniquely identifying the My Code image of user D.

[0072] For example, when the writing device 103 receives a My Code image from user D indicated by D001, it generates M001 as a My Code ID, associates M001 with D001 and the received My Code image, and stores them in the My Code information 622.

[0073] (About analysis information 623) The analysis information 623 stores acquired information acquired in an analysis process (described later) executed by the writing device 103. Fig. 9 is a diagram showing an example of acquired information 901 stored in the analysis information 623. As shown in Fig. 9, the acquired information 901 is linked to the my-code ID 801. For example, the acquired information 901 includes identification information and transition information.

[0074] The identification information is information for identifying a PS user managed by the electronic payment server 102. The transition information is, for example, information for transitioning to a screen for inputting a remittance amount. The acquired information 901 may include information acquired in the analysis process in addition to the identification information and transition information.

[0075] (Regarding communication unit 600) The communication unit 600 communicates with the terminal device 101 and other devices via the network N.

[0076] (Regarding the receiving unit 611) The receiving unit 611 receives the My Code image and other devices from the terminal device 101 via the communication unit 600.

[0077] (Regarding the acquisition unit 612) The acquisition unit 612 acquires information embedded in an image through image analysis processing. For example, the acquisition unit 612 analyzes the My Code image received by the reception unit 611, and acquires the PS user's identification information embedded in the My Code image and transition information for transitioning to a screen for inputting the remittance amount. The analysis processing is a process for decoding the coded information embedded in the image.

[0078] (Regarding the writing unit 613) The writing unit 613 writes the information acquired by the acquiring unit 612 into the wireless tag. For example, the writing unit 613 can write the acquired information 901 into a recording unit of the wireless tag by wired or wireless transmission means. As an example, the writing unit 613 transmits the acquired information 901 to the wireless tag by electromagnetic waves using NFC. Then, the wireless tag performs control so that the received acquired information 901 is stored in a recording unit of an IC chip.

[0079] [7. An example of information processing] Fig. 10 is a sequence diagram showing an example of the flow of information processing among the terminal device 101, the electronic payment server 102, and the writing device 103. Fig. 11 is a diagram showing an example of a screen displayed on the terminal device 101. The flow of information processing according to this embodiment will be described with reference to Figs. 10 and 11.

[0080] In S1001, the terminal device 101 makes a request to the electronic payment server 102 to obtain My Code based on the operation of the terminal user. For example, the terminal user operates the terminal device 101 to launch an electronic payment app. The terminal device 101 then displays a home screen 1100 shown in FIG. 11 on the electronic payment app. The home screen 1100 displays app (1) 1101 to app (4) 1104 indicating apps that can be launched on the electronic payment app, and an account button 1105. The account button 1105 is an operator that accepts transition to a screen for checking the account information of the PS user. App (1) 1101 to app (4) 1104 are sometimes called mini apps.

[0081] When the terminal device 101 detects an operation by the terminal user on the account button 1105, it displays a user account screen 1110 shown in FIG. 11 on the electronic payment app. The user account screen 1110 displays account information 1111 related to the PS user's account and a generate my code button 1112. The generate my code button 1112 is an operator that accepts a request to the electronic payment server 102 to obtain a my code. When the terminal device 101 detects an operation by the terminal user on the generate my code button 1112, it makes a request to the electronic payment server 102 to obtain a my code.

[0082] In S1002, the electronic payment server 102 generates a My Code image in response to receiving the acquisition request in S1001. In S1003, the electronic payment server 102 transmits the My Code image generated in S1002 to the terminal device 101 of the PS user who made the acquisition request. Upon receiving the My Code image, the terminal device 101 stores the My Code image in the storage device 304.

[0083] In S1004, the terminal device 101 transmits the My Code image acquired in S1003 to the writing device 103 based on the operation of the terminal user. For example, the terminal user accesses a website or an app provided by a service-related device. If the access is successful, the terminal device 101 displays a My Code transmission screen 1120 shown in FIG. 11. The My Code transmission screen 1120 displays an input form 1121 for accepting input of a My Code and a send button 1122 for accepting an instruction to send the My Code image. The terminal user inputs a path indicating a storage location of the My Code image into the input form 1121 and presses the send button 1122. Then, when the terminal device 101 detects the operation of the terminal user on the send button 1122, it transmits the My Code image to the writing device 103 via the service-related device.

[0084] In S1005, the writing device 103 performs an analysis process on the My Code image received in S1004. For example, the writing device 103 decodes information that was encoded during the generation process of the received My Code image. The writing device 103 then stores the decoded information as acquired information in the analysis information 623. The writing device 103 can acquire, as the acquired information, the PS user's identification information and transition information for transitioning to a screen for inputting the remittance amount.

[0085] In S1006, the writing device 103 writes the identification information and transition information acquired in S1005 into the wireless tag.

[0086] [8. An example of processing performed by the writing device] Fig. 12 is a flowchart showing an example of processing executed by writing device 103. The flowchart shown in Fig. 12 is realized by CPU 301 of writing device 103 expanding a control program stored in ROM 302 into RAM 303 and executing the expanded control program.

[0087] In S1201, the receiving unit 611 receives a My Code image from the terminal device 101. In S1202, when the receiving unit 611 receives the My Code image in S1201, the acquiring unit 612 executes an analysis process on the My Code image.

[0088] In S1203, the acquisition unit 612 acquires information embedded in the MyCode image analyzed in S1202. The acquisition unit 612 acquires, as the acquired information, identification information for identifying the PS user and transition information for transitioning to a screen for inputting the remittance amount.

[0089] In S1204, the writing unit 613 writes the transition information and the identification information acquired by the acquiring unit 612 in S1203 into the wireless tag.

[0090] In the present embodiment, an example has been described in which the writing device 103 executes an analysis process on the MyCode image transmitted from the terminal device 101, but the present invention is not limited to this. For example, the terminal device 101 equipped with software having the functions of the writing device 103 may execute the analysis process and transmit information obtained from the MyCode image to the writing device 103 directly or via a service-related device.

[0091] [9. Effects] According to this embodiment, information obtained from a MyCode image generated by an electronic payment server that provides a person-to-person remittance service is written to a wireless tag, thereby reducing the burden on the user in performing the remittance operation. That is, the terminal device of the remittance source user obtains the identification information of the remittance destination user stored in the wireless tag and transition information for transitioning to a screen for inputting the remittance amount. This allows easy transition to the screen for inputting the remittance amount without the remittance destination user having to present his / her own identification information using an electronic payment app, and without the remittance source user having to specify the remittance destination user. This reduces the burden on both users in operating the app, and improves usability.

[0092] <Second embodiment> In the above embodiment, the flow of information processing up to writing the transition information for transitioning to the screen for inputting the remittance amount and the PS user's identification information into the wireless tag has been described. In this embodiment, the remittance processing using the wireless tag executed by the electronic payment server 102 will be described with reference to Fig. 13.

[0093] FIG. 13 is a diagram showing an example of information processing performed between the electronic payment server 102, the terminal device (1) 1300, and the terminal device (2) 1320. The basic configuration of this embodiment is the same as that of the above-mentioned embodiment. The terminal device (2) 1320 in this embodiment is an information processing device having a configuration similar to that of the terminal device 101 in the first embodiment. The terminal device (1) 1300 in this embodiment is an information processing device having a configuration similar to that of the terminal device (2) 1320 in this embodiment. Before describing the information processing shown in FIG. 13, the configuration different from the first embodiment will be described below. In the following description, the terminal device (1) 1300 will be referred to as the first terminal 1300, and the terminal device (2) 1320 will be referred to as the second terminal 1320.

[0094] [10. An example of the software configuration of an electronic payment server] 14 is a diagram showing an example of the software configuration of the electronic payment server 102 in this embodiment. The configurations of this embodiment that differ from the above-mentioned embodiments are a determination unit 1411, a PS user information DB 1421, and a terminal identification information DB 1422.

[0095] (Regarding the determination unit 1411) The determining unit 1411 determines the content of the response / non-response information and other information, which are received by the receiving unit 411 and will be described later.

[0096] (Regarding PS User Information DB1421) The PS user information DB 1421 stores remittance information of PS users. Fig. 15 is a diagram showing an example of remittance information 1501 stored in the PS user information DB 1421. The electronic payment server 102 manages the remittance information 1501 in association with the PS user ID 502. The remittance information 1501 has a remittance ID, a remittance amount, a remittance destination, and a date and time.

[0097] The remittance ID is an identifier for identifying the remittance process executed by the electronic payment server 102. The remittance amount indicates the amount of electronic money transferred in the remittance process. The remittance destination indicates the PS user ID of the remittance destination. The date and time indicates the date and time when the remittance process was executed by the electronic payment server 102. As shown in FIG. 15, the electronic payment server 102 manages remittance information 1501 for each remitting PS user.

[0098] (About terminal identification information DB1422) 16 is a diagram showing an example of terminal identification information 1601 stored in the terminal identification information DB 1422. The terminal identification information 1601 is used to identify a terminal device owned by a PS user.

[0099] The terminal identification information 1601 is an identifier for uniquely identifying a terminal device of a PS user. The electronic payment server 102 manages the terminal identification information 1601 in association with the PS user ID 502.

[0100] Here, assume that the PS user sets a notification function for the electronic payment app that allows the terminal device to receive notifications even when the terminal device is in a sleep state. The sleep state refers to a low-power state in which the terminal device consumes less power than when the terminal device is being used by the terminal user. For example, the sleep state refers to a state in which the display of the terminal device is turned off. When the PS user sets the notification function to be enabled, the terminal device transmits terminal identification information 1601 for identifying the terminal device to the electronic payment server 102. Then, the electronic payment server 102 manages the received terminal identification information 1601 by linking it with the PS user ID 502. The terminal device with the notification function set to be enabled can receive notifications from the electronic payment server 102 even in a situation in which the electronic payment app is not displayed on the screen of the terminal device. In other words, the PS user can check the receipt request notification described later without starting the electronic payment app. In order to realize the notification function, the electronic payment server 102 may operate to notify a specific terminal device in conjunction with a notification server (not shown) that notifies the terminal device.

[0101] [11. An example of information processing] 13, a description will be given of processing performed among the electronic payment server 102, the first terminal 1300, and the second terminal 1320. In addition, in this embodiment, the PS user who owns the first terminal 1300 is referred to as the first PS user, and the PS user who owns the second terminal 1320 is referred to as the second PS user.

[0102] In S1301, the first terminal 1300 acquires transition information for transitioning to a screen where the remittance amount can be input, and identification information for identifying the PS user, from a wireless tag. For example, a first PS user brings the first terminal 1300, which has a short-range wireless communication function enabled, close to the wireless tag within a distance where short-range wireless communication is possible (e.g., about 10 cm). Then, the first terminal 1300 receives from the wireless tag the transition information for transitioning to a screen where the remittance amount can be input, which are stored in the memory unit of the wireless tag, and the identification information for identifying the second PS user managed by the electronic payment server 102.

[0103] In S1302, when first terminal 1300 acquires the transition information in S1301, it displays a notification for displaying a screen on the electronic payment application where the remittance amount can be input (hereinafter, referred to as a remittance amount input notification). For example, first terminal 1300 displays, on a display unit provided in first terminal 1300, the remittance amount input notification in which the transition destination is specified by the transition information received in S1301.

[0104] In S1303, the first terminal 1300 requests the electronic payment server 102 to provide a screen on which the remittance amount can be input based on an operation of the PS user in response to the remittance amount input notification displayed in S1302. For example, the first PS user performs an operation (such as a tap operation) in response to the remittance amount input notification. When the first terminal 1300 detects the operation of the first PS user in response to the remittance amount input notification, it launches an electronic payment app. The first terminal 1300 requests the electronic payment server 102 to provide a screen on which the remittance amount can be input, on which the second PS user indicated by the identification information is set as the remittance destination. At this time, the first terminal 1300 can transmit the identification information of the second PS user received in S1301 to the electronic payment server 102.

[0105] In S1304, in response to the request received in S1303, the electronic payment server 102 transmits a screen on which the remittance amount can be input to the requesting first terminal 1300. For example, the electronic payment server 102 transmits to the first terminal 1300 a screen on which the remittance amount can be input, with the second PS user set as the remittance destination.

[0106] In S1305, the first terminal 1300 transmits the remittance amount to the electronic payment server 102 based on the sending operation of the PS user on the screen on which the remittance amount received in S1304 can be input. For example, the first PS user inputs the remittance amount on the screen on the electronic payment app on which the remittance amount can be input, and performs an operation to transmit the remittance amount. When the first terminal 1300 detects the sending operation of the remittance amount by the first PS user, it transmits information indicating the input remittance amount to the electronic payment server 102. In addition, the first terminal 1300 can transmit identification information for identifying the second PS user and identification information for identifying the first PS user to the electronic payment server 102 for the remittance process performed by the electronic payment server 102.

[0107] In S1306, upon receiving the remittance amount in S1305, the electronic payment server 102 notifies the second terminal 1320 of a receipt request. In this embodiment, a receipt request is a request from the remitter PS user to the remitter PS user to receive electronic money. The receipt request notification includes information for transitioning to a screen for receiving electronic money, which is displayed on the electronic payment app. The electronic payment server 102 notifies the second terminal 1320 of a receipt request with the first PS user as the remitter. The receipt request notification can be realized, for example, as a push notification.

[0108] In S1307, the second terminal 1320 requests the electronic payment server 102 to display a remittance acceptance / rejection screen for the PS user to select whether or not to accept the receipt request, based on the operation of the PS user in response to the receipt request notification displayed in S1306. For example, the second terminal 1320 displays the receipt request notification in S1306. Then, upon detecting the operation of the second PS user in response to the receipt request notification, the second terminal 1320 launches an electronic payment app and requests the electronic payment server 102 to display a remittance acceptance / rejection screen.

[0109] In S1308, the electronic payment server 102 transmits a remittance approval / disapproval screen to the second terminal 1320 in response to the request received in S1307.

[0110] In S1309, the second terminal 1320 transmits to the electronic settlement server 102 acceptance / rejection information indicating whether or not to accept the receipt request, based on the operation of the PS user on the remittance acceptance / rejection screen in S1308.

[0111] In S1310, if the electronic payment server 102 receives information indicating that the receipt request is accepted in S1309, it executes the remittance process. On the other hand, if the electronic payment server 102 receives information indicating that the receipt request is not accepted in S1309, it does not execute the remittance process and does not execute any subsequent processes.

[0112] In S1311, when the remittance process is completed in S1310, the electronic settlement server 102 transmits a remittance completion notice indicating that the remittance process is completed to the second terminal 1320.

[0113] When the remittance process is completed in S1310, the electronic payment server 102 transmits a remittance completion notice indicating that the remittance process is completed to the first terminal 1300 in S1312.

[0114] [12. An example of information processing] Fig. 17 is a sequence diagram showing an example of the flow of information processing among the second terminal 1320, the electronic payment server 102, and the first terminal 1300. Fig. 18 is a diagram showing an example of a screen displayed on the first terminal 1300. Fig. 19 is a diagram showing an example of a screen displayed on the second terminal 1320. The flow of information processing according to this embodiment will be described with reference to Figs. 17 to 19.

[0115] 18 is a diagram showing an example of a screen displayed on first terminal 1300. For example, home screen 1800 is a screen displayed on display unit 310 of first terminal 1300 when first terminal 1300 is started up. Home screen 1800 displays icon 1801 of an electronic payment application, and icons 1802 to 1804 of applications 5 to 7.

[0116] In this embodiment, it is assumed that the short-range wireless communication function is enabled in first terminal 1300 so that the function is utilized when first terminal 1300 is activated (hereinafter, referred to as activated state).

[0117] In S1701, the first terminal 1300 acquires transition information for transitioning to a screen where the remittance amount can be input, and identification information for identifying the PS user, from a wireless tag. For example, a first PS user brings the activated first terminal 1300 close to the wireless tag within a distance range where short-range wireless communication is possible. Then, the first terminal 1300 receives the transition information and identification information stored in the memory unit of the wireless tag from the wireless tag. Specifically, the transition information includes a URL (Uniform Resource Locator) scheme of the electronic payment application, and is information that specifies a page to be displayed on the electronic payment application.

[0118] In S1702, when the first terminal 1300 acquires the transition information in S1701, it notifies the first PS user of the remittance amount input. For example, the first terminal 1300 displays a remittance amount input notification 1811 on the display unit 310. The remittance amount input notification screen 1810 shown in FIG. 18 shows a state in which the remittance amount input notification 1811 is displayed on the home screen 1800.

[0119] In S1703, the first terminal 1300 requests the electronic payment server 102 to provide a screen for inputting the remittance amount based on the operation of the PS user in response to the remittance amount input notification displayed in S1702. For example, when the first terminal 1300 detects an operation (e.g., a tap operation) of the first PS user in response to the remittance amount input notification 1811, it launches an electronic payment app and requests the electronic payment server 102 to provide a screen on which the remittance amount can be input. That is, the first terminal 1300 requests the electronic payment server 102 to provide a screen on which the second PS user indicated by the identification information is set as the remittance destination and on which the remittance amount can be input. At this time, the first terminal 1300 can transmit the identification information of the second PS user received in S1701 to the electronic payment server 102.

[0120] In S1704, in response to the request received in S1703, the electronic payment server 102 transmits a remittance amount input screen to the first terminal 1300. For example, the electronic payment server 102 transmits a remittance amount input screen 1820 shown in FIG.

[0121] The remittance amount input screen 1820 has a name 1821 of the remittance PS user, softkeys 1822 which are an input area for inputting the remittance amount, and a display unit 1823 which displays the remittance amount input with the softkeys 1822. The remittance amount input screen 1820 has a remittance button 1824 which accepts a remittance instruction for the remittance amount displayed on the display unit 1823. The remittance amount input screen 1820 shows "xx" as the name of the remittance PS user, and "1,000 yen" input as the remittance amount.

[0122] In S1705, the first terminal 1300 transmits the remittance amount to the electronic payment server 102 based on the transmission operation of the PS user on the screen on which the remittance amount can be input, received in S1704. For example, when the first terminal 1300 detects that the first PS user has input the remittance amount on the remittance amount input screen 1820 and operated the remit button 1824, the first terminal 1300 transmits information indicating the input remittance amount to the electronic payment server 102. In addition, the first terminal 1300 can transmit identification information for identifying the second PS user and identification information for identifying the first PS user to the electronic payment server 102 for the remittance process performed by the electronic payment server 102. After that, the first terminal 1300 displays a remittance waiting screen 1830 shown in FIG. 18 on the electronic payment app.

[0123] The remittance waiting screen 1830 has a display area 1831 in which the remittance amount is displayed. The remittance amount displayed in the display area 1831 is "1,000 yen." In other words, the remittance amount entered and confirmed by the first PS user is displayed in the display area 1831.

[0124] In S1706, upon receiving the remittance amount in S1705, the electronic payment server 102 notifies the second terminal 1320 of a receipt request. For example, in a state in which the notification setting is enabled in the second terminal 1320, upon receiving the remittance amount from the first terminal 1300, the electronic payment server 102 identifies the second terminal 1320 from the terminal identification information 1601 linked to the user identification information of the second PS user. Then, the electronic payment server 102 notifies the identified second terminal 1320 of a receipt request. At this time, the electronic payment server 102 includes transition information for transitioning to a remittance acceptance / rejection screen, which will be described later, in the notification of the receipt request.

[0125] 19 shows a receipt request notification screen 1900 which displays a receipt request notification 1901 displayed on the display unit of the second terminal 1320. As the receipt request notification 1901, a message is displayed which indicates that a receipt request has been received from the first PS user.

[0126] In S1707, the second terminal 1320 requests the electronic payment server 102 to display a remittance acceptance / rejection screen for the PS user to select whether or not to accept the receipt request, based on the operation of the PS user in response to the receipt request notice displayed in S1706. For example, the second terminal 1320 displays a receipt request notice 1901 in S1706. Then, upon detecting an operation (e.g., a tap operation) of the second PS user in response to the receipt request notice 1901, the second terminal 1320 launches the electronic payment app and requests the electronic payment server 102 to display a remittance acceptance / rejection screen 1910 shown in FIG.

[0127] In S1708, the electronic payment server 102 transmits a remittance acceptance screen 1910 to the second terminal 1320 in response to the request received in S1707. The remittance acceptance screen 1910 shown in FIG. 19 is a receipt screen displayed on the electronic payment application for receiving electronic money for the remittance amount. The remittance acceptance screen 1910 displays a display area 1911 displaying the amount to be received, a "Decline" button 1912, and a "Receive" button 1913. The "Decline" button 1912 is an operator that accepts refusal to receive electronic money. The "Receive" button 1913 is an operator that accepts receipt of electronic money.

[0128] In S1709, the second terminal 1320 transmits to the electronic payment server 102 acceptance / rejection information indicating whether or not to accept the receipt request, based on the operation of the PS user on the operator displayed on the remittance acceptance / rejection screen in S1708. For example, the second terminal 1320 displays the remittance acceptance / rejection screen 1910 received in S1708 on the electronic payment application. Then, when the second terminal 1320 detects the second PS user's operation on the "Receive" button 1913, it transmits to the electronic payment server 102 information indicating that the receipt request is accepted. On the other hand, when the second terminal 1320 detects the second PS user's operation on the "Reject" button 1912, it transmits to the electronic payment server 102 information indicating that the receipt request is not accepted.

[0129] In S1710, if the electronic payment server 102 receives information indicating that the receipt request is accepted in S1709, it executes the remittance process. On the other hand, if the electronic payment server 102 receives information indicating that the receipt request is not accepted in S1709, it does not execute the remittance process and does not execute any subsequent processes. When the electronic payment server 102 executes the remittance process, it stores the remittance information 1501 shown in FIG. 15 in the PS user information DB 1421.

[0130] In S1711, when the remittance process is completed in S1710, the electronic payment server 102 transmits a remittance completion notice indicating that the remittance process is completed to the second terminal 1320. Then, when the second terminal 1320 receives the remittance completion notice, it switches the display from the remittance acceptance / rejection screen 1910 to a remittance completion screen 1920 shown in Fig. 19. The remittance completion screen 1920 displays a check mark 1921 indicating that the remittance is complete, and a message 1922 indicating that the receipt of the remittance amount has been completed.

[0131] In S1712, when the remittance process is completed in S1710, the electronic payment server 102 transmits a remittance completion notice indicating the completion of the remittance process to the first terminal 1300. Then, when the first terminal 1300 receives the remittance completion notice, it switches the display from the remittance waiting screen 1830 to the remittance completion screen 1920.

[0132] <Comparative Example> The above FIG. 18 (flow from 1800 to 1820) is an explanation of the second remittance procedure. As a comparative example, the first remittance procedure will be explained. In the first remittance procedure that does not conform to the present embodiment, the remittance source PS user operates the icon 1801 of the electronic payment application on the home screen 1800. After that, the remittance source PS user must operate the remittance screen (not shown) displayed on the electronic payment application to find and specify the remittance destination PS user from the list. If there are many PS users registered in the list, it takes time to search. Furthermore, if the remittance destination PS user is not registered, the remittance source PS user must first register the remittance destination PS user. In this case, the remittance destination PS user must start the electronic payment application and present his / her identification information to the remittance source PS user to have the remittance destination PS user register him / her as a user. Through such remittance procedure, the first terminal can display the screen of 1820 on the electronic payment application. Unlike such a comparative example, according to the second remittance procedure, the screen 1820 can be displayed without the need to specify the PS user to which the remittance is to be sent, thereby reducing the burden on the user. As described in this embodiment, by storing transition information to a screen where the remittance service is available in the wireless tag, it is possible to transition immediately to the screen 1820 when using the remittance service, thereby improving usability.

[0133] <Usage example> The wireless tag in this embodiment is not used for the purpose of utilizing electronic settlement services, but for the purpose of utilizing person-to-person remittance services. In other words, the wireless tag in this embodiment is not placed in a predetermined location in a store and used. As an example of the use of the wireless tag in this embodiment, the wireless tag is attached to a medium close to the user who owns the terminal device. For example, the wireless tag is used together with a sticker or a medium with a strap, a card, a business card, or the like.

[0134] <Other embodiments> In this embodiment, the wireless tag may be built into a terminal device such as a smartphone. Alternatively, a terminal device such as a smartphone may be configured to function as a wireless tag. In such a case, the terminals can transmit and receive the transition information and the PS user's identification information by short-range wireless communication such as NFC. In other words, a terminal device with a built-in wireless tag or a terminal device configured to function as a wireless tag can be applied to the above-mentioned embodiment.

[0135] Two application examples of a terminal device with a built-in wireless tag will be described below with reference to FIG.

[0136] (Example of a terminal device performing a write process) In this example, the information processing from S1 to S5 in FIG. 1 is similar to that described in the first embodiment, and therefore a description thereof will be omitted.

[0137] In S6, when the writing device 103 obtains, from the MyCode image in S5, the identification information for identifying the PS user and transition information for transitioning to a screen for inputting the remittance amount, it transmits this information together with write control information to the terminal device 101. The write control information in this embodiment is control information that instructs the terminal device 101 to write the identification information and transition information to a wireless tag built into the terminal device 101.

[0138] Then, when the terminal device 101 receives the write control information in S6, it controls writing of the identification information and transition information to the wireless tag according to the instructions in the write control information. In this way, when the wireless tag is built in the terminal device, writing to the wireless tag can be realized by receiving the write control information.

[0139] (Example of an electronic payment server executing a write process) In this example, the information processing from S4 to S7 in Fig. 1 is not executed, and therefore a description thereof will be omitted. An example of the software configuration of the electronic payment server in this example is shown in Fig. 20. Unlike the software configuration of the electronic payment server in the second embodiment shown in Fig. 14, the electronic payment server 102 in this example has a write control unit 2011 in the control unit 410. The write control unit 2011 controls the transmission of write control information to the terminal device 101 via the communication unit 400.

[0140] In S1, instead of requesting to obtain the My Code, the terminal device 101 makes a request to the electronic payment server 102 to write, into the wireless tag built into the terminal device 101, identification information for identifying the PS user and transition information for transitioning to a screen for inputting the remittance amount.

[0141] In S2, the electronic payment server 102 transmits the write control information together with the identification information and transition information to the terminal device 101 in response to the request received in S1.

[0142] Then, when the terminal device 101 receives the write control information in S2, it controls writing of the above-mentioned identification information and transition information to the wireless tag according to the instructions indicated in the write control information. In this way, by receiving the write control information from the electronic payment server 102 without going through the writing device 103, writing to the wireless tag can also be realized.

[0143] In the above-described embodiment, a time limit for use of MyCode may be set, or such a time limit may not be set.

[0144] The wireless tag in the above-described embodiment does not have a power source and controls communication using electromotive force generated by receiving electromagnetic waves from the outside with an antenna coil as a power source, but is not limited to this. For example, the wireless tag in the present embodiment may have a power source and control communication using the power source as a power source.

[0145] In the second embodiment, in S1708, the electronic payment server 102 sends the remittance approval / disapproval screen 1910 to the terminal device 101 as an example. However, the electronic payment server 102 may send a remittance completion screen 1920 to the terminal device 101 instead of the remittance approval / disapproval screen 1910.

[0146] For example, assume a case where an automatic receipt function for automatically accepting a receipt request without the second PS user's operation of accepting or rejecting the receipt request, as described with reference to the remittance acceptance screen 1910 in Fig. 19, can be set in the electronic payment application. If the automatic receipt function is enabled in the electronic payment application of the terminal device 101, the electronic payment server 102 transmits a remittance completion screen 1920 in S1708. In this case, S1709 is omitted, and the electronic payment server 102 executes the remittance process in S1710. In other words, the system may be configured such that receipt of electronic money for the remittance amount is automatically completed in response to the second PS user's operation in response to the receipt request notice 1901 shown in the receipt request notice screen 1900 in Fig. 19, without the second PS user's operation of accepting or rejecting the receipt request.

[0147] In the second embodiment, the short-distance wireless communication function is effectively performed when the terminal device is in an activated state, but is not limited thereto. For example, the short-distance wireless communication function may be configured to be effectively performed when an application or software for performing short-distance wireless communication is activated.

[0148] In the second embodiment, the first terminal requests the electronic payment server 102 to send a screen on which the remittance amount can be input, and receives the screen. However, the present invention is not limited to this. For example, if the first terminal stores the screen to be displayed on the electronic payment application, the first terminal does not need to request the screen from the electronic payment server 102. That is, if the first terminal determines that the screen indicated by the transition information acquired from the wireless tag matches the screen stored by the first terminal, the first terminal does not request the screen indicated by the transition information from the electronic payment server 102. For example, a case is assumed in which a remittance source user has previously remitted electronic money to a remittance destination user, and the first terminal has received and stored a screen on which the remittance amount can be input, in which the remittance destination user is designated as the remittance destination, from the electronic payment server 102. In such a case, the first terminal can set the PS user indicated by the identification information acquired from the wireless tag as the remittance destination and display the screen stored by the first terminal, without receiving the screen on which the remittance amount can be input again from the electronic payment server 102. Thereafter, the first terminal transmits to the electronic payment server 102 information indicating the remittance amount, as well as identification information for identifying the first PS user and identification information for identifying the second PS user obtained from the second terminal.

[0149] Furthermore, when the first terminal displays a screen on which the remittance amount can be input, the first terminal may request information necessary for displaying the screen from the electronic payment server 102. For example, the first terminal may request some or all of the information, such as objects and text, that constitute the screen from the electronic payment server 102.

[0150] Furthermore, the configuration of the above-mentioned first terminal and second terminal can be flexibly changed, for example, by calling an external platform or the like via an API or network computing, depending on the function.

[0151] Furthermore, the above-described embodiments can be appropriately combined as long as the processing contents are not contradictory. [Explanation of symbols]

[0152] 101 Terminal Equipment 102 Electronic payment server 103 Writing device

Claims

1. An information processing device that provides a payment service in which electronic money is transferred from an electronic account held by a user who pays for the purchase of a product at a store or the payment for a service provided at a store to an electronic account held by the store, by communicating with a terminal device having a communication function using NFC and using a communication means other than NFC, and a remittance service in which the electronic money used in the payment service is transferred from an electronic account held by a remitter user to an electronic account held by a remitter user, a receiving unit for receiving a request for control to write, into said terminal device, identification information for identifying the remittance destination user in said remittance service and transition information for transitioning to a screen for transferring the electronic money from the electronic account of the remittance source user to the electronic account of the remittance destination user in said remittance service; a transmission unit that transmits, in response to the request, an instruction for causing the terminal device to perform the control, the identification information, and the transition information to the terminal device; An information processing device comprising:

2. 2. The information processing apparatus according to claim 1, wherein the terminal device includes a communication control medium capable of communicating by NFC.

3. 3. The information processing apparatus according to claim 2, wherein the instruction is an instruction for causing the terminal device to write the identification information and the transition information onto the communication control medium.

Images