Information processing device
The information processing device enhances remittance service usability by automatically transitioning to a remittance service screen using NFC, reducing user interaction and operational complexity.
Patent Information
- Application Number
- JP2024088932
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-05-31
- Publication Date
- 2025-12-11
- Estimated Expiration
- 2044-05-31
AI Technical Summary
Conventional remittance services through electronic payment apps place a significant burden on users due to the need for both sender and recipient to launch the app and perform multiple operations, lacking in usability compared to electronic payment services.
An information processing device that includes a receiving unit to obtain an identification code from a terminal device and a control unit to write this information to a wireless tag via NFC, enabling seamless transition to a remittance service screen without requiring users to manually specify the remittance destination or input details.
Reduces the operational burden on users by allowing direct access to a remittance service screen, improving usability and simplifying the remittance process.
Smart Images

Figure 2025181130000001_ABST
Abstract
Description
[Technical Field]
[0001] The present disclosure relates to an information processing device, an information processing method, and a program. [Background technology]
[0002] Cashless payments, which allow users to pay for goods or services without using currency, are becoming increasingly popular. 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 making a payment at a store by reading store identification information and the like from an NFC (Near Field Communication) 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 have room for improvement in terms of improving the usability of remittance services.
[0006] The present disclosure aims to improve usability. [Means for solving the problem]
[0007] An information processing device according to one embodiment of the present disclosure is characterized by comprising: 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 remittance services, 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 to a communication control medium that can communicate via NFC (Near Field Communication). [Effects of the Invention]
[0008] According to the present disclosure, usability can be improved. [Brief explanation of the drawings]
[0009] [Figure 1] FIG. 10 is a diagram illustrating an example of information processing. [Figure 2] FIG. 1 illustrates an example of a system configuration. [Figure 3] FIG. 2 is a block diagram illustrating an example of a hardware configuration of an information processing device. [Figure 4] FIG. 2 is a diagram illustrating an example of the software configuration of an electronic payment server. [Figure 5] FIG. 10 is a diagram showing an example of electronic account information stored in an account database. [Figure 6] FIG. 10 is a diagram showing an example of remittance information stored in the PS user information database. [Figure 7] FIG. 10 is a diagram illustrating 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. 10 is a sequence diagram illustrating an example of a flow of information processing. [Figure 10] FIG. 10 is a diagram showing an example of a screen displayed on a terminal device of a remitter. [Figure 11] FIG. 10 is a diagram showing an example of a screen displayed on a terminal device of a remittance destination. [Figure 12]10 is a flowchart illustrating an example of a process executed by a terminal device. [Figure 13] FIG. 10 is a diagram illustrating an example of information processing. [Figure 14] FIG. 2 is a diagram illustrating an example of the software configuration of an electronic payment server. [Figure 15] FIG. 10 is a diagram showing an example of remittance information stored in a PS user information DB. [Figure 16] FIG. 2 is a diagram showing an example of terminal identification information stored in a terminal identification information DB. [Figure 17] FIG. 10 is a sequence diagram illustrating an example of a flow of information processing. [Figure 18] FIG. 10 is a diagram showing an example of a screen displayed on a terminal device of a remitter. [Figure 19] FIG. 10 is a diagram showing an example of a screen displayed on a terminal device of a remittance destination. [Figure 20] FIG. 2 is a diagram illustrating an example of the software configuration of an electronic payment server. DETAILED DESCRIPTION OF THE INVENTION
[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. Furthermore, the same components in the following embodiments will be assigned 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 on terminal devices such as smartphones include electronic payment applications, etc. In the following, applications may be simply referred to 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 electronic currency (hereinafter referred to as electronic money) between users.
[0013] Remittance services enable the exchange of currency 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 flexibility. 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 designated 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 purchases 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 as long as the sender can specify the recipient.
[0015] Some terminal devices have a function (hereinafter referred to as a short-range wireless communication function) that enables data transmission and reception via short-range wireless communication such as NFC (Near Field Communication). Such terminal devices can receive stored data from a communication control medium (hereinafter referred to as a wireless tag) that has an IC (Integrated Circuit) chip, an antenna coil, etc., and that can communicate according to a short-range wireless communication standard. Usability can be improved by combining a wireless tag with a terminal device that has a short-range 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 with 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 using electronic payment services, using a remittance service requires both the recipient user and the sender user to launch an electronic payment app and perform the necessary operations to send the money, which places a significant burden on both users. This leaves room for improvement in terms of usability. For example, by receiving information from a wireless tag used to access the remittance service to transition to a screen where the remittance service can be used, the burden on users for sending money between individuals can be reduced. Below, we will explain how usability can be improved.
[0018] [2-1. 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, electronic payment server 102, and 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 (described later). In this embodiment, the terminal device 101 is described as a smartphone, but is not limited to this. 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, via a web browser or an app, an identification code including user identification information for identifying a user, as well as screens and other information, provided by the electronic payment server 102. 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 other 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 and a remittance service that performs remittance processing. For example, the electronic payment server 102 can be realized by a server device or a cloud system. By installing an electronic payment app on the terminal device 101, a user can use multiple services provided by the electronic payment server. Note that the electronic payment service and 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 referred to as a PS user. A PS user is, for example, a user who has acquired an account within an electronic payment app. The acquired 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 a PS User who has received 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 contracted 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 a PS User who is the sender of the money to the electronic account of a PS User who is the recipient of the money.
[0025] In response to a request for obtaining a My Code from the terminal device 101, the electronic payment server 102 generates a My Code image in which the PS user's identification information and the like are embedded, and provides the My Code 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 being a desktop personal computer (PC), but is not limited to this. The writing device 103 may be, for example, a smartphone, a tablet terminal, a notebook PC, or a personal digital assistant (PDA).
[0027] Furthermore, the writing device 103 can realize information processing, which will be described later, via another server device or another cloud system (not shown).
[0028] The writing device 103 can analyze the MyCode image received from the terminal device 101 and obtain the 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 My Code image. The service-related device can also execute part of the processing executed by the writing device 103, which will be described later. In the following description, when there is no need to distinguish between a PS user and a D user, both will be 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 via short-range wireless communication into a memory unit in the IC chip. The wireless tag can also read information stored in the memory unit in the IC chip via 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 acquire My Code to the electronic payment server 102 (S1). For example, the terminal user operates the terminal device 101 to launch an electronic payment app. Then, when the terminal device 101 detects the terminal user's operation on the electronic payment app, it transmits a request to acquire My Code to the electronic payment server 102.
[0033] In response to the request for obtaining 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 associated with the identified PS user and transition information for transitioning to a screen for using the remittance service are embedded.
[0034] The electronic payment server 102 generates a My Code image in S2 and transmits the generated My Code image to the terminal device 101 of the PS user who requested the acquisition (S3). After that, the terminal device 101 receives the My Code image in S3 and saves the received My Code image. The My Code image may be in a file format such as JPEG (Joint Photographic Experts Group), PNG (Portable Network Graphics), or GIF (Graphics Interchange Format), for example.
[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 the service-related device and performs a transmission operation to transmit the My Code image from the website. 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, which are embedded in the My Code image.
[0037] The writing device 103 writes the identification information and transition information acquired in S5 to the wireless tag (S6). For example, the writing device 103 writes the identification information and 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 have been written in S6 to User D, who is the sender of 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 so as to be able to communicate with each other via wired or wireless means. 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, for the sake of simplicity, one terminal device 101 is shown, 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 written in a script language such as JavaScript (registered trademark). The information transmitted and received may be written in a style sheet language such as CSS (Cascading Style Sheets) or a programming language such as Java (registered trademark). The information transmitted and received may be written 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 connected to each other via 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 also 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, data, etc. 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), flash memory, and storage. If the storage device 304 is the electronic payment server 102, it stores an account information database (hereinafter, the database will be referred to as DB) described below. 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 within 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 operation keys. The input unit 311 may be provided outside the information processing device 300 as shown in FIG. 3, or may be provided within the information processing device 300.
[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 as being divided into 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 realizing a function of writing to a wireless tag.
[0052] 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 CPU 301 via RAM 303. CPU 301 can read the provided programs from the storage device onto RAM 303 via the media I / F and execute the read programs. The storage device may be, 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 may also be a tape medium, a magnetic recording medium, a semiconductor memory, or the like.
[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, thereby realizing various functions of the information processing device 300.
[0054] The CPU 301 of the information processing device 300 reads and executes these programs from a storage device, but as another example, these programs may be acquired 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 to realize the information processing in this embodiment.
[0055] [5. An example of software configuration for an 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 sending 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) The account information DB 421 stores electronic account information for PS users. Fig. 5 is a diagram showing an example of electronic account information stored in the account information DB 421. The electronic account information includes 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 a PS user's account. 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 PS user's electronic account. The electronic money may be, for example, points or currency awarded by a service provider that operates an electronic payment service, or it may be electronically tradable currency provided by a country, such as Japanese yen or dollars. The PS user can pay for goods or services and transfer electronic money within the balance of their electronic account. The electronic payment server 102 manages the PS user's electronic account by linking it to the PS user ID 502.
[0058] (Regarding the 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 a request to acquire MyCode and other information via the communication unit 400.
[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 My Code image and other information.
[0062] (Regarding the payment processing unit 414) The payment processor 414 performs electronic payment processing based on the electronic payment method described below when a PS user makes a payment at a store or the like.
[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 payment based on the scanned information, and a second electronic payment method in which a user reads a code placed in a store and makes payment based on the read information.
[0064] (Regarding the remittance processing unit 415) The remittance processing unit 415 performs remittance processing based on the remittance procedure of the remitter PS user using the electronic payment app.
[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 specified PS user set as the destination.
[0066] In the first remittance procedure, the PS user who is the remitter operates the electronic payment app to specify the PS user who is the recipient and the amount to be remitted 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 PS user who is the recipient and the amount to be remitted.
[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 places less of a burden on the PS user than the first remittance procedure. Details of the second remittance procedure will be explained 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, My Code information 622, and analysis information 623. The writing device 103 can perform analysis processing for analyzing images and writing processing to wireless tags.
[0069] (About D User Information DB621) Information about D users is stored in the D user information DB 621. Fig. 7 is a diagram showing an example of 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] The D user ID 701 is an identifier for uniquely identifying the D user. The address information 702 stores "AR01" as information indicating the address of the D user. "AR01" includes information indicating the residence of the D user, expressed, for example, as a prefecture and city / town / village. "AR01" may also include information such as a postal code. In other words, "AR01" is information used to send a package to the D user, and includes information that identifies the D user's place of residence.
[0071] (About My Code Information 622) Information about user D's my code is stored in the my code information 622. Fig. 8 is a diagram showing an example of information about my code stored in the my code information 622. My code ID 801 shown in Fig. 8 is an identifier for uniquely identifying user D's my code image.
[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, transition information, and the like.
[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 the remittance amount. In addition to the identification information and transition information, the acquired information 901 may also include information acquired in the analysis process.
[0075] (Regarding the 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 the 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 and transition information for transitioning to a screen for inputting the remittance amount, which are embedded in the My Code image. The analysis processing is a process of 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 the 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 controls so that the received acquired information 901 is stored in the recording unit of the 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 requests 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 apps (1) 1101 to (4) 1104, which indicate 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 PS user's account information. Apps (1) 1101 to (4) 1104 are sometimes called mini apps.
[0081] When the terminal device 101 detects a terminal user's operation 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 a terminal user's operation 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 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 the 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 terminal user's operation 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 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 to the wireless tag.
[0086] [8. Example of processing performed by the writing device] Fig. 12 is a flowchart showing an example of processing executed by the writing device 103. The flowchart shown in Fig. 12 is realized by the CPU 301 of the writing device 103 loading a control program stored in the ROM 302 into the RAM 303 and executing the loaded 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 the information embedded in the My Code 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 identification information acquired by the acquiring unit 612 in S1203 to the wireless tag.
[0090] In the present embodiment, an example has been described in which the writing device 103 performs 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 perform 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 person-to-person remittance services is written to a wireless tag, thereby reducing the burden on users when performing remittance operations. Specifically, 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 the remittance destination user to easily transition to the screen for inputting the remittance amount without the need for the remittance destination user to submit their own identification information using the electronic payment app, or for the remittance source user to specify the remittance destination user. This reduces the burden on both users when operating the app, improving usability.
[0092] <Second embodiment> In the above embodiment, the flow of information processing up to writing transition information for transitioning to a screen for inputting the remittance amount and the PS user's identification information into the wireless tag was explained. In this embodiment, the remittance processing using a wireless tag executed by the electronic payment server 102 will be explained with reference to Fig. 13.
[0093] FIG. 13 is a diagram showing an example of information processing performed among 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-described embodiment. The terminal device (2) 1320 in this embodiment is an information processing device having the same configuration as the terminal device 101 in the first embodiment. The terminal device (1) 1300 in this embodiment is also an information processing device having the same configuration as the terminal device (2) 1320 in this embodiment. Before describing the information processing shown in FIG. 13, the configuration that differs 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 software configuration for 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 different from the above-described 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 received by the receiving unit 411, which 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 by linking it to the PS user ID 502. The remittance information 1501 includes 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 Figure 15, the electronic payment server 102 manages remittance information 1501 for each remitting PS user.
[0098] (About terminal identification information DB1422) Terminal identification information for identifying terminal devices owned by PS users is stored in the terminal identification information DB 1422. Fig. 16 is a diagram showing an example of terminal identification information 1601 stored in the terminal identification information DB 1422.
[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, we assume that a PS user enables a notification function for the electronic payment app that allows the user to receive notifications even when the terminal device is in sleep mode. The sleep mode 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 mode refers to a state in which the display of the terminal device is turned off. When the PS user enables the notification function, the terminal device transmits terminal identification information 1601 for identifying the terminal device to the electronic payment server 102. The electronic payment server 102 then manages the received terminal identification information 1601 by linking it with the PS user ID 502. A terminal device with the enabled notification function can receive notifications from the electronic payment server 102 even when 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 launching the electronic payment app. To implement the notification function, the electronic payment server 102 may operate in conjunction with a notification server (not shown) that sends notifications to terminal devices to notify specific terminal devices.
[0101] [11. An example of information processing] 13, a description will be given of the processing performed between the electronic payment server 102, the first terminal 1300, and the second terminal 1320. In this embodiment, the PS user who owns the first terminal 1300 will be referred to as the first PS user, and the PS user who owns the second terminal 1320 will be referred to as the second PS user.
[0102] In S1301, the first terminal 1300 acquires, from a wireless tag, transition information for transitioning to a screen where the remittance amount can be input, and identification information for identifying the PS user. For example, a first PS user brings the first terminal 1300, which has the 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). The first terminal 1300 then receives, from the wireless tag, 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 identification information for identifying the second PS user managed by the electronic payment server 102.
[0103] In S1302, upon acquiring the transition information in S1301, the first terminal 1300 displays a notification (hereinafter referred to as a remittance amount input notification) for displaying a screen on the electronic payment app where the remittance amount can be input. For example, the first terminal 1300 displays the remittance amount input notification, in which the transition destination is specified by the transition information received in S1301, on a display unit provided on the first terminal 1300.
[0104] In S1303, the first terminal 1300 requests the electronic payment server 102 to display a screen on which the remittance amount can be input, based on the PS user's operation 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 first PS user's operation in response to the remittance amount input notification, it launches the electronic payment app. The first terminal 1300 requests the electronic payment server 102 to display a screen on which the remittance amount can be input, with the second PS user indicated by the identification information 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 PS user's sending operation 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 a screen displayed on the electronic payment app on which the remittance amount can be input, and performs an operation to send the remittance amount. When the first terminal 1300 detects the first PS user's sending operation of the remittance amount, it transmits information indicating the entered 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 recipient PS user to receive electronic money. The receipt request notification includes information for transitioning to a screen displayed on the electronic payment app for receiving electronic money. The electronic payment server 102 notifies the second terminal 1320 of a receipt request from the first PS user as the remitter. The receipt request notification can be implemented, 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 PS user's operation 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 second PS user's operation in response to the receipt request notification, the second terminal 1320 launches the 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] In S1312, when the remittance process is completed in S1310, the electronic settlement server 102 transmits a remittance completion notice to the first terminal 1300 indicating that the remittance process has been completed.
[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 the first terminal 1300. For example, the home screen 1800 is a screen displayed on the display unit 310 of the first terminal 1300 when the first terminal 1300 is started up. The home screen 1800 displays an icon 1801 for an electronic payment application, and icons 1802 for applications 5 to 1804 for applications 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, from a wireless tag, transition information for transitioning to a screen where the remittance amount can be input and identification information for identifying the PS user. For example, the first PS user brings the activated first terminal 1300 close to the wireless tag within a distance that allows short-range wireless communication. The first terminal 1300 then receives the transition information and identification information stored in the memory of the wireless tag from the wireless tag. Specifically, the transition information includes the URL (Uniform Resource Locator) scheme of the electronic payment app and specifies the page to be displayed on the electronic payment app.
[0118] In S1702, upon acquiring the transition information in S1701, the first terminal 1300 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 display 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) by the first PS user in response to the remittance amount input notification 1811, it launches the electronic payment app and requests the electronic payment server 102 to display a screen on which the remittance amount can be input. That is, the first terminal 1300 requests the electronic payment server 102 to display 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. 18 to the first terminal 1300.
[0121] The remittance amount input screen 1820 has a name 1821 of the PS user of the remittance destination, softkeys 1822 which are an input area for inputting the remittance amount, and a display unit 1823 which displays the remittance amount input using the softkeys 1822. The remittance amount input screen 1820 has a remittance button 1824 which accepts an instruction to remit the remittance amount displayed on the display unit 1823. The remittance amount input screen 1820 shows "xx" as the name of the PS user of the remittance destination, and shows a state in which "1,000 yen" has been 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 PS user's sending operation 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 to be performed by the electronic payment server 102. After this, 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 that displays the remittance amount. 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, when the notification setting is enabled in the second terminal 1320 and the electronic payment server 102 receives 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. The electronic payment server 102 then 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 receipt request notification.
[0125] 19 shows a receipt request notification screen 1901 displayed on the display unit of the second terminal 1320. As the receipt request notification 1901, a message indicating that a receipt request has been received from the first PS user is displayed.
[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 PS user's operation 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 the second PS user's operation (e.g., a tap operation) 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. 19 .
[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 app for receiving electronic money equivalent to 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 PS user's operation 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 app. 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 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 settlement server 102 transmits a remittance completion notice indicating that the remittance process has been 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 has been completed, 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 settlement server 102 sends a remittance completion notice indicating that the remittance process is completed 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-described FIG. 18 (the flow from 1800 to 1820) explains the second remittance procedure. As a comparative example, the first remittance procedure will be explained. In the first remittance procedure, which does not conform to the present embodiment, the remittance source PS user operates the electronic payment app icon 1801 on the home screen 1800. The remittance source PS user then operates a remittance screen (not shown) displayed on the electronic payment app to search for and specify the remittance destination PS user from a list. This search can be time-consuming if there are a large number of PS users registered in the list. 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 launch the electronic payment app and provide their identification information to the remittance source PS user to have the remittance destination PS user register them as a user. After completing these remittance procedures, the first terminal can display the screen 1820 on the electronic payment app. Unlike the comparative example, according to the second remittance procedure, the screen 1820 can be displayed without having to specify the PS user as the remittance destination, thereby reducing the burden on the user. As explained in this embodiment, by storing transition information to a screen where the remittance service is available in the wireless tag, when using the remittance service, it is possible to immediately transition to the screen 1820, thereby improving usability.
[0133] <Usage example> The wireless tag in this embodiment is not used for the purpose of using electronic payment services, but for the purpose of using person-to-person remittance services. In other words, the wireless tag in this embodiment is not placed in a predetermined location within a store and used. As an example of how the wireless tag in this embodiment is used, the wireless tag is attached to a medium familiar to the user who owns the terminal device. For example, the wireless tag is used integrated with a sticker or medium with a strap, a card, or a business card.
[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 via 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-described 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 terminal device performing write processing) In this example, S1 to S5 in FIG. 1 are the same as the information processing explained in the first embodiment, and therefore explanations thereof will be omitted.
[0137] In S6, the writing device 103 acquires, from the My Code image in S5, identification information for identifying the PS user and transition information for transitioning to a screen for inputting the remittance amount, and then transmits this information along 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 in accordance with the instructions indicated in the write control information. In this way, when the wireless tag is built into 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 requests the electronic payment server 102 to write, into its built-in wireless tag, 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 settlement 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 at S2, it controls writing of the identification information and transition information to the wireless tag in accordance with 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, it is also possible to realize writing to the wireless tag.
[0143] The My Code in the above-described embodiment may or may not have a usable time limit 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 external electromagnetic waves through 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 acceptance / rejection screen 1910 to the terminal device 101 as an example. However, the electronic payment server 102 may send the remittance completion screen 1920 to the terminal device 101 instead of the remittance acceptance / rejection screen 1910.
[0146] For example, consider a case where an automatic receipt function that automatically accepts a receipt request without the second PS user having to accept or decline the receipt request can be set in the electronic payment app, as described with reference to the remittance acceptance / rejection screen 1910 in Fig. 19 . If the automatic receipt function is enabled in the electronic payment app of the terminal device 101, the electronic payment server 102 sends 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 so that receipt of the remittance amount of electronic money is automatically completed in response to the second PS user's operation on the receipt request notification 1901 shown on the receipt request notification screen 1900 in Fig. 19 , without the second PS user having to accept or decline the receipt request.
[0147] In the second embodiment, the short-range wireless communication function is effectively performed when the terminal device is in an activated state, but the present invention is not limited to this. For example, the short-range wireless communication function may be configured to be effectively performed when an application or software for performing short-range wireless communication is activated.
[0148] In the second embodiment, the first terminal requests a screen on which the remittance amount can be input from the electronic payment server 102 and receives the screen. However, this is not limiting. For example, if the first terminal has stored the screen to be displayed on the electronic payment app, 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 may be assumed in which the remittance source user has previously sent electronic money to the remittance destination user, and the first terminal has received and stored from the electronic payment server 102 a screen on which the remittance amount can be input, in which the remittance destination user is designated as the remittance destination. 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 settlement 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 make up the screen from the electronic payment server 102.
[0150] Furthermore, the configuration of the first and second terminals described above can be flexibly changed, for example, by calling an external platform or the like using an API or network computing, depending on the function.
[0151] Furthermore, the above-described embodiments can be combined as appropriate within the scope of not causing any contradiction in the processing content. [Explanation of symbols]
[0152] 101 Terminal equipment 102 Electronic payment server 103 Writing device
Claims
1. a receiving unit that receives from a terminal device an identification code including identification information for identifying a remittance destination user in an electronic settlement server that provides a remittance service, and including transition information for transitioning to a screen for remittance to the remittance destination user; a control unit that controls writing of the identification information and the transition information into a communication control medium that can communicate by NFC (Near Field Communication); An information processing device comprising:
2. 2. The information processing apparatus according to claim 1, wherein the receiving unit receives the identification code as a code image in which the identification information and the transition information are embedded.
3. The information processing device according to claim 1 , wherein the transition information is information for starting an electronic payment application provided by the electronic payment server and transitioning to a predetermined screen.
4. The information processing apparatus according to claim 1 , further comprising an acquisition unit that decodes the identification code and acquires the identification information and the transition information.
5. a receiving step of receiving from a terminal device an identification code including identification information for identifying a remittance destination user in an electronic settlement server that provides a remittance service, and including transition information for transitioning to a screen for remittance to the remittance destination user; a control step of controlling writing of the identification information and the transition information into a communication control medium capable of communicating via NFC; An information processing method comprising:
6. On the computer, a receiving step of receiving from a terminal device an identification code including identification information for identifying a user of a remittance destination in an electronic settlement server that provides a remittance service, and including transition information for transitioning to a screen for remittance to the user of the remittance destination; a control procedure for controlling writing of the identification information and the transition information into a communication control medium capable of communicating via NFC; A program for an information processing device, characterized by causing the information processing device to execute the above.
7. An information processing device that provides a remittance service and communicates with a terminal device having a communication function using NFC by a communication means other than NFC, a receiving unit that receives a request for control to write, into the terminal device, identification information for identifying the remittance destination user in the information processing device and transition information for transitioning to a screen for remittance to the remittance destination user; a transmitting 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:
8. 8. The information processing apparatus according to claim 7, wherein the terminal device has a built-in communication control medium capable of communicating by NFC.
9. 9. The information processing apparatus according to claim 8, wherein the instruction instructs the terminal device to write the identification information and the transition information onto the communication control medium.
Citation Information
Patent Citations
Information registering terminal, service terminal, program and information registering system
JP2005338909A
Apparatus and method for installing application for IC card to mobile terminal, and program
JP2011100423A
Settlement program, settlement device, and settlement method
JP2021135805A
Information processing device, information processing method, and information processing program
JP7481523B1