Remittance management device, remittance management method, and program

Abstract

Making it difficult to misunderstand the purpose of using the remittance service. [Solution] A remittance management device that provides a remittance service that accepts requests for remittance from a user account of a user who is the sender of the remittance to a receiver account of a receiver who is the recipient of the remittance, and includes: an acquisition unit that acquires code information obtained by reading a code image with the user's terminal device and transmitted by the terminal device; and a remittance processing unit that accepts the remittance request from the terminal device and moves the accepted electronic money for the remittance from the user's account to the receiver's account, wherein the code image includes a code unit that includes remittance destination information regarding the remittance destination, and a decoration unit that decorates the code unit in a manner that differs depending on the remittance type.

Description

[Technical Field]

[0001] The present invention relates to a remittance management device, a remittance management system, a remittance management method, and a program. [Background technology]

[0002] BACKGROUND ART Conventionally, there have been proposed techniques relating to remittance services that provide a means for remittance between accounts by electronic settlement using code information such as QR Codes (registered trademark) and barcodes (see, for example, Patent Documents 1 and 2). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 7185083 [Patent Document 2] Patent No. 7202493 Summary of the Invention [Problem to be solved by the invention]

[0004] Conventional technology provided a uniform remittance method regardless of purpose or use, which made it easy for users of remittance services to misunderstand the purpose of using the remittance service.

[0005] The present invention has been made in consideration of these circumstances, and one of its objects is to provide a remittance management device, a remittance management system, a remittance management method, and a program that make it less likely that the purpose of using a remittance service will be mistaken. [Means for solving the problem]

[0006] One aspect of the present invention is a remittance management device that provides a remittance service that accepts requests for remittance from a user account of a user who is the sender of the remittance to a receiver account of a receiver who is the recipient of the remittance, and includes: an acquisition unit that acquires code information that is obtained by reading a code image with the user's terminal device and transmitted by the terminal device; and a remittance processing unit that identifies the remittance destination based on the code information, accepts the remittance request from the terminal device, and transfers electronic money equivalent to the accepted remittance amount from the user's account to the receiver's account, wherein the code image includes a code unit that includes remittance destination information regarding the remittance destination, and a decoration unit that decorates the code unit in a manner that differs depending on the remittance type. [Effects of the Invention]

[0007] According to one aspect of the present invention, it is possible to provide a remittance management device, a remittance management system, a remittance management method, and a program that make it difficult to mistake the purpose of using a remittance service. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of a configuration for realizing an electronic payment service. [Figure 2] This is a sequence diagram (part 1) illustrating the general flow of electronic payment. [Figure 3] This is a sequence diagram (part 2) illustrating the general flow of electronic payment. [Figure 4] 1 is a configuration diagram of a payment server 100 according to an embodiment. [Figure 5] FIG. 10 is a diagram showing an example of the contents of user information 172. [Figure 6] FIG. 10 is a diagram showing an example of the contents of affiliated store / store information 176. [Figure 7] FIG. 10 is a diagram showing an example of the contents of donation receiver information 177. [Figure 8] FIG. 1 is a diagram illustrating the flow of a remittance service. [Figure 9]FIG. 10 is a diagram showing an example of the contents of service setting information 180. [Figure 10] FIG. 10 is a diagram showing an example of using remittance services according to remittance type (donation). [Figure 11] FIG. 10 is a diagram showing an example of using remittance services according to remittance type (donation). [Figure 12] FIG. 10 is a diagram showing an example of using remittance services according to remittance type (offerings). [Figure 13] FIG. 10 is a diagram showing an example of using remittance services according to remittance type (offerings). [Figure 14] FIG. 10 is a diagram showing an example of a first donation code image 62A. [Figure 15] FIG. 10 is a diagram showing an example of a second donation code image 62B. [Figure 16] FIG. 10 is a diagram showing an example of a third donation code image 62C. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, with reference to the drawings, embodiments of the remittance management device, remittance management system, remittance management method, and program of the present invention will be described. The application program and payment server work together to provide electronic payment services. The electronic payment services include a purchase payment service for payments related to purchases and a remittance service for remittances. In the following description, the application program used for the purchase payment service and remittance service will be referred to as a payment app.

[0010] A purchase settlement service is a service that supports payments for the purchase of goods or services at a store. A store is, for example, a physical store (real-world store) that exists in real space, but may also include virtual stores for e-commerce. Virtual stores may also include those provided by entities other than the operator of the electronic payment service. In such cases, when making payments for purchases at the virtual store, the user is controlled to transition to the interface screen of the purchase settlement service. In a purchase settlement service, a store is treated as belonging to, for example, an affiliated store (brand), and when a purchase is made at the store or when payments are made through donations, the process is primarily carried out between the user and the affiliated store. Alternatively, the process of payment may be carried out between the user and the store.

[0011] On the other hand, a remittance service is a service for users that provides a means for users to remit money to a member store for a purpose previously set by the member store. The remittance service includes services that support donations such as donations to fundraising organizations, temples and shrines as donation acceptors, and offerings (votive money). Multiple remittance methods may be set according to the purpose of the remittance, and multiple remittance methods with different purposes may be set for one member store. The operator of the electronic payment service provides a service to member stores that enables them to accept remittances from users using the remittance service.

[0012] Merchants include general corporations that provide goods and services, and donation recipients that accept donations such as donations and offerings. Merchants that use electronic payment services are businesses such as corporations that have entered into a contract for the use of electronic payment services with a service provider of the electronic payment service (i.e., the operator of the electronic payment service). A general corporation that serves as a merchant using a purchase payment service is, for example, a business that conducts commercial transactions with users (hereinafter referred to as a for-profit business), and is, in other words, a commercial transaction business. Merchants that use remittance services are donation recipients such as individuals that accept donations, non-profit organizations or for-profit corporations that operate fundraising organizations that accept donations, religious corporations or educational corporations that operate temples and shrines, political parties, and organizers of crowdfunding. A commercial transaction business may also serve as a donation recipient. A donation recipient is one example of a recipient.

[0013] [Overall structure of electronic payment services] FIG. 1 is a diagram showing an example of a configuration for realizing an electronic payment service. The electronic payment service is managed by an electronic payment system 1 (remittance management system) and is realized mainly by a payment server 100. The payment server is an example of a remittance management device. The electronic payment system 1 includes, for example, one or more user terminal devices 10, one or more first store terminal devices 50, one or more second store terminal devices 70, one or more donation receiver terminal devices 80, a code image generation device 90, and a payment server 100. The one or more user terminal devices 10, one or more first store terminal devices 50, one or more second store terminal devices 70, one or more donation receiver terminal devices 80, and the payment server 100 communicate with each other via a network NW. The code image generation device 90 may communicate with the one or more user terminal devices 10, one or more first store terminal devices 50, one or more second store terminal devices 70, the donation receiver terminal device 80, and the payment server 100. The network NW includes, for example, the Internet, a LAN (Local Area Network), a wireless base station, a provider device, and the like.

[0014] The user terminal device 10 is, for example, a portable terminal device such as a smartphone or tablet terminal. The user terminal device 10 is a computer device having at least an optical reading function, a communication function, a display function, an input acceptance function, and a program execution function. In the following description, components for realizing these functions are referred to as a camera, a communication device, a touch panel, a CPU (Central Processing Unit), etc. In the user terminal device 10, a processor such as a CPU executes a payment app 20, which operates in cooperation with the payment server 100 to provide electronic payment services to users. The payment app 20 is installed on the user terminal device 10 from, for example, an application store, and controls the camera, communication device, touch panel, etc.

[0015] The first store terminal device 50 is installed in a store, for example. The first store terminal device 50 is a computer device having at least a product price acquisition function, an optical reading function, a program execution function, and a communication function. The first store terminal device 50 may include a so-called POS (Point of Sale) device, and the product price acquisition function and the optical reading function may be realized by the POS device.

[0016] In a store where the first store terminal device 50 is installed, for example, a store code image 60 and a donation code image 62 used for donations and offerings are installed. Both the store code image 60 and the donation code image 62 are placed in the store and are code images such as QR Code (registered trademark) printed on paper or plastic media. The store code image and the donation code image 62 may be displayed on a display placed in the store (which may be the display of a terminal device such as a smartphone). The donation code image 62 is an example of a code image.

[0017] The second store terminal device 70 is used, for example, by the operator of a member store of the purchase settlement service. The second store terminal device 70 is a smartphone, tablet terminal, personal computer, etc. An interface for member stores 72 runs on the second store terminal device 70. The interface for member stores 72 may be an app for member stores or a browser. The interface for member stores 72 accepts coupon settings and the like from the operator of the member stores and transmits them to the settlement server 100. The second store terminal device 70, which is a smartphone, has the function of displaying display code images corresponding to the store code image 60 and the donation code image 62 and reading display code images displayed by the user terminal device 10 by executing the app for member stores.

[0018] Donation recipient terminal device 80 is used by donation recipients at affiliated stores of the remittance service. Donation recipient terminal device 80 is a smartphone, tablet terminal, personal computer, etc. Donation recipient interface 82 runs on donation recipient terminal device 80. Donation recipient interface 82 may be an app for donation recipients or a browser.

[0019] The donation recipient uses the donation recipient interface 82 to request registration for the remittance service and the generation of the donation code image 62. When requesting registration for the remittance service, the donation recipient interface 82 accepts the donation recipient's settings such as the donation recipient ID and remittance type (product type), and generates setting information for registering the remittance service (hereinafter, service setting information 180, see FIG. 9 ) and sends it to the payment server 100. The payment server 100 newly registers the sent service setting information. In addition to the donation recipient ID, the setting of the installation location ID may also be accepted.

[0020] When starting to use the remittance service or when the installed donation code image 62 has deteriorated and become unreadable, the donation recipient operates the donation recipient interface 82 to request the generation of the donation code image 62. When requesting the generation of the donation code image 62, the donation recipient interface 82 generates code image generation request information requesting the generation of a code image to be used in the remittance service related to donations and offerings in accordance with the donation recipient's operation, and transmits the code image generation request information to the code image generation device 90. The code image generation request information includes, for example, information for identifying the donation recipient who is the remittance destination (e.g., an installation location URL) and remittance type information for identifying the remittance type. The installation location URL is the domain of the electronic payment service to which information capable of identifying the donation code image 62 has been added, and is associated in the payment server 100 with the donation recipient ID, installation location ID, remittance type, etc. The installation location URL is an example of remittance destination information.

[0021] The code image generation device 90 generates the donation code image 62 based on, for example, code image generation request information transmitted by the donation recipient terminal device 80. The code image generation device 90 includes, for example, a generation unit 92 and a storage unit 94. The generation unit 92 generates the donation code image 62 by encoding information including information for identifying the donation recipient (for example, an installation location URL). The donation code image 62 includes a code section in which the code information is encoded and a decoration section that decorates the code section. The code information includes, for example, the installation location URL. Note that the code image generation request information includes a donation recipient ID and an installation location ID, and the code image generation device 90 may generate the installation location URL based on the donation recipient ID and the installation location ID.

[0022] The storage unit 94 stores a library 94A for generating the donation code image 62. The library 94A stores template images that can be used for each remittance type as information regarding the decorative portion. The generation unit 92 generates the decorative portion of the donation code image 62 using, for example, the remittance type information included in the code image generation request information transmitted by the donation acceptor terminal device 80 and information regarding the types of decorative portion included in the library 94A. The generation unit 92 generates the donation code image 62 using the information regarding the types of decorative portion included in the library 94A.

[0023] The code image generating device 90, for example, prints the donation code image 62 or requests a printing shop or the like to print the donation code image 62. The code image generating device 90 and the printing shop that has been requested to print print the donation code image 62 on a paper or plastic medium, and provides the medium on which the donation code image 62 is printed to the store where the first store terminal device 50 is installed.

[0024] The code image generation device 90 may provide the information contained in the library 94A stored in the storage unit 94 to the donation recipient terminal device 80, so that the donation recipient can generate code image generation request information while viewing the information contained in the library 94A. The information contained in the library 94A may be stored in the donation recipient terminal device 80 or made public on the cloud.

[0025] The donation code image 62 may be placed next to a store's cash register or next to a donation box installed in the store to accept donations. The donation code image 62 may be placed, for example, on a signboard-like mount placed next to a store's cash register or other location, or on the donation box itself. The location where the donation code image 62 is placed is designated in advance by the donation recipient when registering for the remittance service, for example. The donation code image 62 may be printed on a sticker and affixed to a mount, donation box, or the like, and then taken out on the street. The code image generation device 90 may be included in another device, such as the payment server 100.

[0026] The payment server 100 accepts registration for use of the electronic payment service and performs processing when the electronic payment service is executed. When executing the purchase payment service among the electronic payment services, the payment server 100 realizes electronic payment based on payment information received from the user terminal device 10 or the first store terminal device 50.

[0027] The payment server 100 performs the remittance service based on the remittance trigger information and remittance information sent by the user terminal device 10 as part of its processing. The remittance trigger information and remittance information will be described later. The first store terminal device 50 may include a POS device and an affiliated store server, in which case payment information is sent from the POS device to the payment server 100 via the affiliated store server. In the following description, no distinction will be made between these two, and it is assumed that payment information is sent from the first store terminal device 50. In explaining the contents of the electronic payment service below, we will first explain the contents of the purchase payment service in the electronic payment service, then explain the payment server 100, and then explain the contents of the remittance service.

[0028] [Electronic payment (purchase payment service)] 2 and 3 are sequence diagrams illustrating the general flow of electronic payment. There may be two patterns for electronic payment: Pattern 1 and Pattern 2. In the case of Pattern 1 (hereinafter referred to as "user scan") shown in FIG. 2, the user terminal device 10, with the payment application 20 running, decodes the store code image 60 using its optical reading function (S1). The store code image 60 contains information about the store's URL (Uniform Resource Locator, hereinafter referred to as "store URL"). The store URL is the domain of the electronic payment service to which information that can identify the store has been added, and is associated with the affiliated store ID, store ID, etc. in the payment server 100.

[0029] The payment application 20 sends first payment information including the store URL and account ID to the payment server 100 (S2). The payment server 100 searches for store information using the affiliated store ID or store ID corresponding to the store URL, acquires the affiliated store name and store name information (S3), and sends this to the payment application 20 (S4). The user inputs the payment amount into the user terminal device 10 on the screen displaying the affiliated store name and store name (S5).

[0030] The user terminal device 10 generates second payment information including at least the payment amount and sends it to the payment server 100 (S6). The payment server 100 performs electronic payment based on the received second payment information (S7). Then, the payment server 100 sends a payment completion notice (information for displaying a payment completion screen) to the payment application 20 (S8), and the payment application 20 displays the payment completion screen (S9).

[0031] When the store code image 60 is displayed on a display installed in a store, the store code image 60 may include not only the store URL but also information on the payment amount. In this case, the procedure for the user to input the payment amount is omitted, and the information on the affiliated store name and store name, which is included in the information on the payment amount in the first payment information and transmitted to the payment server 100, may be displayed together with the payment completion screen.

[0032] In the case of pattern 2 (hereinafter referred to as store scan) shown in FIG. 3, the payment app 20 sends a request to issue a one-time code to the payment server 100 when the payment app 20 is launched, when a payment operation is performed in the payment app 20, at the automatic update timing (e.g., every minute), and at other timings (S11). The payment server 100 generates a one-time code (S12) and sends it to the payment app 20 (S13). The payment app 20 displays a code image, such as a QR code (registered trademark) or barcode, generated based on the one-time code (S14). The user holds (presents) the display surface of the user terminal device 10 over the first in-store terminal device 50, and the first in-store terminal device 50 decodes the code image using its optical reading function and acquires the one-time code, etc. (S15). The first in-store terminal device 50 then generates payment information including the one-time code, payment amount, affiliated store ID, store ID, etc., and sends it to the payment server 100 (S16). The payment amount information is acquired in advance by reading a barcode, manually entering it, etc. Based on the received information, the payment server 100 identifies the user corresponding to the one-time code and performs electronic payment (S17). Then, the payment server 100 sends a payment completion notice to the payment application 20 (S18), and the payment application 20 displays a payment completion screen (S19).

[0033] Note that electronic payment may be performed using only one of the patterns of user scanning or store scanning. Furthermore, the "account ID" described in FIG. 2 may be other information (e.g., a phone number) that can be used as user identification information. Furthermore, issuing a one-time code may be omitted in the store scanning, and the payment application 20 may display a code image generated based on the user's account ID. In this case, the payment server 100 identifies the user corresponding to the account ID instead of identifying the user corresponding to the one-time code.

[0034] [Payment server] 4 is a configuration diagram of the payment server 100 according to the embodiment. The payment server 100 includes, for example, a communication unit 110, a distribution unit 115, a payment content providing unit 120, a payment processing unit 130, an acquisition unit 132, a remittance processing unit 134, a determination unit 136, an information management unit 140, and a storage unit 170. The components other than the communication unit 110 and the storage unit 170 are implemented by, for example, a hardware processor such as a CPU executing a program (software). Some or all of these components may be implemented by hardware (including circuitry) such as an LSI (Large Scale Integration), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a GPU (Graphics Processing Unit), or may be implemented by a combination of software and hardware. The program may be stored in advance in a storage device such as an HDD (Hard Disk Drive) or flash memory (a storage device with a non-transitory storage medium), or may be stored in a removable storage medium (a non-transitory storage medium) such as a DVD or CD-ROM, and installed in the storage device by inserting the storage medium into a drive device.

[0035] Storage unit 170 is a hard disk drive (HDD), flash memory, RAM (Random Access Memory), etc. Storage unit 170 may be a NAS (Network Attached Storage) device that payment server 100 can access via a network. Storage unit 170 stores information such as user information 172, payment content information 174, affiliated store / shop information 176, donation acceptor information 177, and service setting information 180.

[0036] The communication unit 110 is a communication interface for connecting to the network NW. The communication unit 110 is, for example, a network interface card. The communication unit 110 receives information transmitted by the user terminal device 10 or the first store terminal device 50, such as payment information (first payment information) or received information that is remittance trigger information. The remittance trigger information is information that requests the start of remittance processing, and includes code information contained in the code portion of the donation code image 62 and decoration part identification information for identifying the decoration part. The decoration part identification information may be an image of the decoration part, or may be a character string (text characters) or a design (icon) included in the decoration part. The communication unit 110 outputs the received information to the sorting unit 115.

[0037] The sorting unit 115 sorts the received information output by the communication unit 110 into payment information and remittance trigger information. For example, if the received information contains information that is used for electronic payment services but not for remittance services, such as a store URL (described below), the sorting unit 115 sorts the received information into payment information. For example, if the received information contains information that is not used for electronic payment services but is used for remittance services, such as an installation location URL (described below), the sorting unit 115 sorts the received information into payment information. For example, the sorting unit 115 determines whether the URL in the received information is an installation location URL by referencing the donation acceptor information 177 in FIG. 7 and the service setting information 180 in FIG. 9 (described below). This determination may be made by the payment application 20, and the determination result may be provided to the payment server 100. In this case, information indicating whether the URL is a remittance service URL is managed in the payment application 20.

[0038] The sorting by the sorting unit 115 may be performed in any manner. For example, the payment information and remittance trigger information may each include a sorting flag such as a payment flag or a remittance flag, and the sorting unit 115 may perform sorting by determining the sorting flag included in the received information. The sorting flag may be included in the store code image 60 or the donation code image 62 used to generate the payment information or the remittance trigger information, or may be added to the payment information or the remittance trigger information in the user terminal device 10 and the first store terminal device 50.

[0039] The payment content providing unit 120 has, for example, a function of a web server, and provides information (content) for displaying various screens of the electronic payment service to the user terminal device 10. The payment content providing unit 120 reads out necessary content from the payment content information 174 as appropriate and provides it to the user terminal device 10. The user terminal device 10 accepts various inputs from the user while content is being played by the payment application 20, and transmits the above-mentioned payment information and the like to the payment server 100.

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

[0041] FIG. 5 is a diagram showing an example of the contents of the user information 172. The user information 172 includes, for example, a user URL, account ID, telephone number, and password, as well as other information such as an email address, user ID, name, address, date of birth, registration date, remaining balance, deferred payment settings, deferred payment limit, deferred payment usage amount, available deferred payment amount, payment method settings, bank account, credit card number, charge history information, and payment history information. The user URL is used for remittance processing between users. When registering for the electronic payment service, registration of a phone number and password is required. The account ID is issued to the user by the payment server 100, and the user ID can be set arbitrarily by the user (although it does not have to be set). Similarly, the email address, name, address, and date of birth can also be set arbitrarily by the user (although it does not have to be set). The registration date is the date the user registered for the electronic payment service (the date the account was created). Hereinafter, a user instance (electronic payment account) to which this information is associated is referred to as an account.

[0042] The charge balance indicates the balance of electronic money set by the user by transferring funds to the account in advance. Transfer methods include transfers from a designated service provider (bank) ATM (Automatic Teller Machine) or from a registered bank account. The deferred payment setting indicates whether the setting for deferred payment electronic payments has been completed and is set to either "completed" or "not completed." The deferred payment limit is the monthly deferred payment limit. The deferred payment usage amount is the amount of deferred payment already used in the current month. The available deferred payment amount is the amount of deferred payment available in the current month, calculated by subtracting the deferred payment usage amount from the deferred payment limit. While the figure shows only one deferred payment limit, in reality, there may also be daily upper limits, and the lower of these may be set as the deferred payment limit. Further details on deferred payment will be discussed later. The payment method setting indicates whether the user will make electronic payments using the charge balance or by deferred payment at that time. The bank account and credit card number are information on the bank account or credit card number (account number, card number) that can be used to deposit funds into the electronic payment service. The charge history information is a history of the user's previous transfers to the electronic payment service to increase the charge balance. The payment history information is information that shows the breakdown of payments made by the user for each payment (date and time, store ID of the store where the purchase was made, payment amount, payment method, etc.).

[0043] 6 is a diagram showing an example of the contents of affiliated store / store information 176. The affiliated store / store information 176 includes, for example, a first table 176A in which an affiliated store ID and a store ID are associated with a store URL, a second table 176B in which an affiliated store ID is associated with an affiliated store name and sales amount (described above), and a third table 176C in which a store ID is associated with a store name. In addition to this information, the affiliated store / store information 176 may also include information such as the category of the affiliated store or store, the store's location, and payment patterns.

[0044] When payment information is acquired from the user terminal device 10 or the first store terminal device 50, the payment processing unit 130 references the user information 172 to acquire the "payment method setting" of the user. For users whose "payment method setting" is set to "charge balance," the payment processing unit 130 performs electronic payment as follows: For example, the payment processing unit 130 performs electronic payment by decreasing the charge balance managed in association with the user ID and increasing the item value of the affiliated store's sales proceeds. The item value of the affiliated store's sales proceeds is not itself used as electronic money, for example, but rather the amount corresponding to the item value of the sales proceeds is transferred to a bank account in a cycle according to an agreement between the affiliated store and the electronic payment service.

[0045] The payment processing unit 130 performs electronic payments for users whose "setting information" is set to "deferred payment" as follows. Deferred payment is set separately from "credit card payment," which is set in cooperation with a credit card company, which is a separate entity from the operator of the electronic payment service. The operator of the electronic payment service acts as the creditor, and allows electronic payments within the deferred payment limit, independent of the remaining balance. To receive the deferred payment service, a user may be required to obtain a credit card provided by the operator of the electronic payment service. The amount used for deferred payment is settled in full on the following month's payment date, for example, by debit from a bank account. In this case, the payment processing unit 130 makes a provisional payment by adding the payment amount to the deferred payment amount and subtracting the same amount from the available deferred payment balance. On the closing date, the payment processing unit 130 performs the process described above to debit the current month's payment on the following month's payment date, or requests the credit card operator to perform this process. If the payment amount exceeds the available deferred payment balance at the time of provisional payment, an error notification is returned to the payment app 20.

[0046] The acquisition unit 132 acquires remittance trigger information transmitted by the user terminal device 10. The remittance trigger information includes code information, which includes information for identifying the user, such as an installation location URL and an account ID. Furthermore, the acquisition unit 132 acquires, for example, remittance information transmitted by the user terminal device 10. The remittance information includes, for example, remittance amount information that identifies the remittance amount, and information that identifies the user, such as an account ID.

[0047] The remittance processing unit 134 identifies the donation recipient ID by referencing the installation location URL included in the remittance trigger information in the donation recipient information 177. The remittance processing unit 134 transfers electronic money equivalent to the remittance amount information included in the remittance information acquired by the acquisition unit 132 from the user account corresponding to the account ID, etc., to the affiliated store account (donation recipient account) corresponding to the identified donation recipient ID. The remittance processing unit 134 realizes the remittance service, for example, in cooperation with the payment application 20 running on the user terminal device 10. The user can use the remittance service by reading, with the payment application 20, code information issued for the registered remittance service (code information included in the donation code image 62 generated by the code image generation device 90, if the affiliated store is the donation recipient).

[0048] 7 is a diagram showing an example of the contents of donation recipient information 177. Donation recipient information 177 includes, for example, a first table 177A in which a donation recipient ID and an installation location ID are associated with an installation location URL, a second table 177B in which a donation recipient ID is associated with a donation recipient name and a collected amount (amount of donations, offerings, etc.), and a third table 177C in which an installation location ID is associated with the actual installation location of donation code image 62. In addition to this information, donation recipient information 177 may also include information such as the category of donation recipient, the location of the donation recipient, and payment pattern.

[0049] If the donation is an offering or dedication, the donation receiver information 177 may include information such as the name of the offering, the purpose of use, the country in which the received money will be used, the location where the donation code image 62 is installed and managed (name, address, telephone number), the total number of locations where the donation code image 62 is displayed, the location where the donation code image 62 is displayed (building, floor), etc. If the donation is a donation, the donation receiver information 177 may include information such as the name of the donation, the purpose of use, the country in which the received money will be used, the location where the donation code image 62 is installed and managed (name, address, telephone number).

[0050] The determination unit 136 determines the appropriateness of the code information transmitted by the user terminal device 10. For example, when the acquisition unit 132 acquires remittance information, the determination unit 136 analyzes the remittance type corresponding to the decoration part specifying information included in the remittance trigger information corresponding to the acquired remittance information. The determination unit 136 determines whether the code information is appropriate based on the analyzed remittance type and the remittance type corresponding to the decoration part specifying information included in the remittance information.

[0051] Information management unit 140 manages various types of information stored in memory unit 170. For example, information management unit 140 manages user information 172, affiliated store / store information 176, and donation receiver information 177 based on information acquired from user terminal device 10, first store terminal device 50, and donation receiver terminal device 80. Information management unit 140 adds new records, edits, deletes, etc. for user information 172, affiliated store / store information 176, and donation receiver information 177.

[0052] [Remittance service] Figure 8 is a diagram illustrating the flow of the remittance service. In the remittance service, first, the user identifies the remittance service to be used (S21), and then reads the code information for using the remittance service using the payment application 20 (S22). Here, "identifying the remittance service" in S21 means that the user identifies the donation code image 62 as the code image to be read in the next S22. In this case, S21 corresponds to the user visiting a store where the donation code image 62 is installed and recognizing the donation code image 62 to be read.

[0053] Donation code image 62 is placed at a designated installation location or taken out on the street, as specified by the donation recipient. Payment application 20 generates remittance trigger information including code information based on donation code image 62 read in S22 and transmits the generated information to payment server 100 (S23). The code information includes an installation location URL, an account ID, etc. Payment server 100 identifies the donation recipient ID by referencing the installation URL included in the code information of the transmitted remittance trigger information in donation recipient information 177, and generates remittance content by referencing the identified donation recipient ID in service setting information 180.

[0054] For example, registration for the remittance service and issuance of code information included in donation code image 62 are performed by cooperation between donation recipient interface 82 and information management unit 140. For example, a donation recipient operates donation recipient interface 82 to input service setting information 180 for the remittance service and send it to payment server 100. In payment server 100, information management unit 140 stores (registers) service setting information 180 received from donation recipient interface 82 in memory unit 170.

[0055] FIG. 9 is a diagram showing an example of the contents of the service setting information 180. The service setting information shown in FIG. 9 is service setting information corresponding to the code information included in the donation code image 62. The service setting information 180 includes, for example, information associating a donation recipient name with a donation recipient ID, a remittance type, and additional information. Typically, the donation recipient name and the remittance type are designated by the donation recipient when registering for the transmission service. The donation recipient name may be automatically assigned to the remittance service to be registered by the remittance service system (e.g., the payment server 100). The additional information is additional information related to the remittance service to be registered. The additional information may be set arbitrarily and may be used for any purpose. For example, images, text information, etc. may be registered as additional information and included in the remittance content of the remittance service. The service setting information 180 may also associate an installation location ID with a donation recipient ID.

[0056] The means for registering the remittance service to the payment server 100 is provided to the payment server 100 by, for example, an interface for donation recipients 82. The donation recipient operates the interface for donation recipients 82 to input donation recipient information 177 (donation recipient ID, installation location ID, remittance type, and donation recipient name) and send it to the payment server 100. In the payment server 100, the information management unit 140 stores (registers) the various setting information and donation recipient information 177 received from the interface for donation recipients 82 in the memory unit 170.

[0057] Returning to Figure 8, payment server 100 then refers to the code information (installation location URL) included in the remittance trigger information received from payment application 20 in S23 in donation recipient information 177 shown in Figure 7 to identify the donation recipient ID to be used, and then refers to service setting information 180 shown in Figure 8 to identify the remittance type. Payment server 100 transmits remittance content corresponding to the remittance type to payment application 20 (S24).

[0058] The payment application 20 receives the remittance content sent from the payment server 100 in S24 and plays the remittance content to display, for example, a user interface screen of the remittance service (hereinafter referred to as the remittance screen) (S25). The payment application 20 accepts input of remittance amount information on the remittance screen, generates remittance information including the input remittance amount information and the user ID, and sends it to the payment server 100 (S26).

[0059] The remittance processing unit 134 identifies the donation recipient ID by referencing the installation location ID included in the code information transmitted by payment application 20 and acquired by acquisition unit 132 in S23 in donation recipient information 177. After transmitting the remittance content in S24, the remittance processing unit 134 identifies the remittance amount based on the remittance amount information included in the remittance information transmitted by payment application 20 and acquired by acquisition unit 132 in S26, for example.

[0060] The remittance processing unit 134 identifies the donation acceptor account based on the donation acceptor ID identified after S23, and identifies the user account based on the user ID included in the remittance information acquired by the acquisition unit 132 after S26. The remittance processing unit 134 reduces the charge balance of the user who is the sender of the remittance by the remittance amount, and increases the charge balance of the affiliated store who is the recipient of the remittance by the remittance amount (S27: remittance processing). For each remittance service, an electronic settlement account (hereinafter referred to as the remittance destination account) for managing the charge balance of the affiliated store who is the recipient of the remittance is registered in advance in the payment server 100. For example, the remittance destination account is created when registering for the remittance service.

[0061] Next, the payment server 100 withdraws an amount equivalent to the charge balance of the remittance destination account to the financial institution account of the affiliated store linked to the identified donation recipient account (S28). This allows the donation recipient to ultimately collect the amount remitted from the user in the form of electronic money using the remittance service it provides as a cash balance in the financial institution account. If the user specifies the charge balance and point balance as the source of funds for the remittance amount, the payment server 100 may apply the amount of points specified by the user to part of the remittance amount in the withdrawal process.

[0062] Next, examples of using the remittance service according to the remittance type will be explained. Figs. 10 to 13 are diagrams showing examples of using the remittance service according to the remittance type. Figs. 10 and 11 show an example of use when the remittance type is "donation," and Figs. 12 and 13 show an example of use when the remittance type is "offering." "Donation" and "offering" shown here are examples of remittance types, and the remittance type may be set arbitrarily by the donation recipient. Affiliated stores that provide remittance services may be businesses that act as both for-profit businesses and donation recipients, or may be businesses that are not for-profit businesses.

[0063] Here, the donation recipient is a non-profit business. The types of remittances in the remittance service may include "donations," "offerings," "membership fees," etc., in addition to "donations" and "offerings." If the donation recipient is also a profit-making business, a comprehensive code image containing all of the information contained in the store code image 60 and the donation code image 62 may be used.

[0064] [Remittance service for "Donation" remittance type] 10 and 11, when the remittance type is "donation," for example, the payment application 20 transitions through the following screens in order: top screen IM1, remittance screen IM2, confirmation screen IM3, and remittance completion screen IM4. First, the user of the remittance service operates button BT11 (scan) on the top screen IM1 of the payment application 20 to invoke the function for reading the donation code image 62, and reads the donation code image 62 for the remittance service to be used. The payment application 20 transmits the code information included in the read donation code image 62 to the payment server 100.

[0065] The payment server 100 identifies the remittance type for the remittance service to be used based on the code information received from the payment application 20, generates remittance content according to the remittance type, and provides it to the payment application 20. The payment application 20 plays the remittance content received from the payment server 100 to display the remittance screen IM2.

[0066] The remittance screen IM2 is configured to include, for example, contents CT20 to CT24. Content CT20 is content that serves as a template for the remittance screen IM2, and contents CT21 to CT24 are arranged in the manner shown in the figure. Content CT20 may include, as part of the template, a user interface that is common to remittances as "donations." The content CT20 in the example of FIG. 10 includes a user interface IF25 that accepts an input operation for the remittance amount and a user interface IF25 that accepts an operation for selecting a source of funds that can be used for remittance.

[0067] The content CT21 is image content related to a remittance service. The content CT21 may be, for example, a brand logo of the remittance service or a logo of a donation acceptor who provides the remittance service. The content CT21 may be set as additional information in the service setting information 180, for example.

[0068] Content CT22 is information content representing the name of the donation acceptor providing the remittance service. Content CT22 may be obtained, for example, from donation acceptor information 177 based on the donation acceptor ID in service setting information 180. Content CT23 is information content representing the service name of the remittance service. For example, the donation acceptor name in service setting information 180 may be used for content CT23. Content CT24 is information content representing precautions regarding the use of the remittance service.

[0069] The options for funding sources presented by the user interface IF26 may include a point balance in addition to a charge balance. Points are given to users in response to their use of electronic payment services and are points that can be used as monetary value. Points are managed for each user. The point balance may be managed, for example, as part of the user information 172, in association with the user ID of each user.

[0070] On the remittance screen IM2, the user inputs the remittance amount and selects the source of funds, and then operates the confirmation button BT27, causing the remittance screen IM2 to transition to a confirmation screen IM3. The confirmation screen IM3 is a screen that allows the user to confirm the details of the remittance before executing the remittance. Similar to the remittance screen IM2, the confirmation screen IM3 is configured by arranging contents CT31 to CT34 in content CT30, which serves as a template. Content CT30 includes an area AR35 that displays the planned remittance amount, an area AR36 that displays a breakdown of the source of funds to be used, and a remittance execution button BT37 for entering instructions to execute the remittance.

[0071] When the user operates the remittance execution button BT37 on the confirmation screen IM3, the remittance information is sent to the payment server 100, and the remittance process is carried out by the payment server 100. When the remittance process is completed successfully, the confirmation screen IM3 transitions to a remittance completion screen IM4. The remittance completion screen IM4 is a screen that notifies the user that the remittance specified on the top screen IM1 has been completed successfully. Like the remittance screen IM2 and the confirmation screen IM3, the remittance completion screen IM4 is constructed by arranging contents CT41 to CT43 in content CT40, which serves as a template. Content CT40 includes an area AR44 that displays the time when the remittance has been completed, an area AR45 that displays the remitted amount, an area AR46 that displays that the remittance has been completed, an area AR47 that displays the breakdown of the remittance amount paid, and an area AR48 that displays the settlement number, which is the identification number of the electronic settlement that settled the payment of the remittance amount, and the fund transfer service provider of that electronic settlement.

[0072] On the remittance completion screen IM4, the information displayed in areas AR44 to AR48 can be used as information (receipt information) to prove to a third party that the user has used the remittance service to remit money (here, a donation). For example, if the remittance type is "donation," providing such receipt information to the user reduces the effort required for the user to apply for a donation deduction, which is expected to motivate the user to make donations.

[0073] [Remittance service for "offerings"] 12 and 13 show an example of screen transitions when the remittance type is "offerings." The remittance screen IM5 is configured, for example, by arranging content CT51 (image of a shrine), CT52 (name of the shrine), CT53 (name of the donation recipient), and CT54 (image of an offering box) on content CT50, which serves as a template. Content CT50 includes a user interface IF55 that accepts input of the remittance amount, a user interface IF56 that accepts selection of a funding source that can be used for remittance, and a confirmation button BT57.

[0074] The remittance confirmation screen IM6 is constructed, for example, by arranging contents CT61 to CT64 on content CT60, which serves as a template. Content CT60 includes an area AR65 that displays the planned remittance amount, an area AR66 that displays a breakdown of the source of funds to be used, and a remittance execution button BT67 for inputting an instruction to execute the remittance. The remittance completion screen IM7 is constructed, for example, by arranging contents CT71 to CT74 on content CT70, which serves as a template. Content CT70 includes an area AR75 that displays the remitted amount, an area AR76 that displays a message that the remittance has been completed, and an area AR77 that displays a breakdown of the remittance amount paid.

[0075] In this case, too, the flow of transitioning from the top screen IM1 to the money transfer screen IM5, the money transfer confirmation screen IM6, and the money transfer completion screen IM7 is the same as when the money transfer type is "donation." However, because the money transfer types are different, different types of money transfer content are provided to the payment app 20 for "offerings" than for "donations." The provision of such money transfer content is realized by generating money transfer content according to the money transfer type. For example, because offerings are not subject to donation deductions, some of the receipt information, such as the receipt timing and payment number, is omitted from the money transfer completion screen IM7 for "offerings."

[0076] [Donation Code Image 62] Next, several examples of the donation code image 62 will be described. Fig. 14 is a diagram showing an example of a first donation code image 62A. Fig. 15 is a diagram showing an example of a second donation code image 62B shown in the middle diagram. Fig. 16 is a diagram showing an example of a third donation code image 62C. The first donation code image 62A, the second donation code image 62B, and the third donation code image 62C all show one aspect of the donation code image 62.

[0077] The donation code image 62 includes a code section 62-1, a pattern decoration section 62-2, and a text decoration section 62-3. In the following explanation, the first donation code image will be designated by the letter "A," the second donation code image by the letter "B," and the third donation code image by the letter "C," and the contents of each will be explained accordingly. The first donation code image 62A shown in FIG. 14 is a code image for which the remittance type is "donation." The second donation code image 62B shown in FIG. 15 and the third donation code image 62C shown in FIG. 16 are both code images for which the remittance type is "offering."

[0078] The code section 62-1 includes a location URL, which is remittance destination information related to the remittance destination. The graphic decoration section 62-2 includes an icon with a different design for each remittance type, and decorates the code section 62-1 in a different manner for each remittance type. The text decoration section 62-3 includes a text information image that differs for each remittance type.

[0079] The first donation code image 62A includes a first code portion 62A-1, a first pattern decoration portion 62A-2, and a first text decoration portion 62A-3. The first code portion 62A-1 is composed of a QR code (registered trademark) into which code information indicating that the remittance type is "donation" is encoded. The first pattern decoration portion 62A-2 includes a first icon image showing a coin-like design with a "yen mark" attached to it being placed inside a wallet-like design with a "heart mark" attached.

[0080] The first text decoration portion 62A-3 includes a text information image consisting of the text characters "Donation." The text information image may include hiragana, katakana, numerals, alphabetic characters, and special characters other than kanji. The first pattern decoration portion 62A-2 is arranged in the center of the first code portion 62A-1, and the first text decoration portion 62A-3 is arranged around the first code portion 62A-1, for example, below it.

[0081] The second donation code image 62B includes a second code section 62B-1, a second pattern decoration section 62B-2, and a second text decoration section 62B-3. The second code section 62B-1 is composed of a QR code (registered trademark) encoded with code information specifying "offering" as the type of remittance. The second pattern decoration section 62B-2 includes a second icon image showing a coin-like design with a "yen mark" placed inside an offering box-like design. The second text decoration section 62B-3 includes a text information image consisting of the text characters "offering" formed below the second code section 62B-1.

[0082] The third donation code image 62C includes a third code section 62C-1, a third pattern decoration section 62C-2, and a third text decoration section 62C-3. The third code section 62C-1 is composed of a QR code (registered trademark) encoded with code information specifying "offering" as the type of remittance. The third pattern decoration section 62C-2 includes a third icon image showing an offering box design and a large bell design placed above it. The third text decoration section 62C-3 includes a text information image consisting of the text characters "offering" formed below the third code section 62C-1.

[0083] The first icon image, second icon image, and third icon image included in the first pattern decoration section 62A-2, the second pattern decoration section 62B-2, and the third pattern decoration section 62C-2 differ for each remittance type. For example, the first icon image is an icon of code information specifying "donation" as the remittance type, and the second icon and third icon are icons of code information specifying "offerings" as the remittance type. The first icon image, second icon image, and third icon image are icons in a manner that evokes the remittance type, such as "donation" or "offerings," respectively. The donation code image 62 uses an icon with a different design from the store code image 60. Furthermore, the donation code image 62 uses an icon with a different design for each remittance type.

[0084] The generation unit 92 of the code image generation device 90 generates a code portion 62-1 based on, for example, code image generation request information transmitted by the donation acceptor terminal device 80. Next, the generation unit 92 selects from the library 94A an image to be used for the decoration portion corresponding to the remittance type according to the installation location URL included in the code image generation request information, and generates a graphic decoration portion 62-2 by embedding it in the center of the code portion 62-1. Next, the generation unit 92 selects from the library 94A a text information image corresponding to the remittance type, and places it around the code portion 62-1 to generate a text decoration portion 62-3.

[0085] For example, when the donation recipient becomes an affiliated store and is approved for use of the remittance service, the donation recipient terminal device 80 generates code image generation request information and transmits it to the code image generation device 90. The code image generation device 90 generates a donation code image 62 based on the transmitted code image generation request information.

[0086] The donation code image 62 may be placed next to the store code image 60. The store code image 60 may include, for example, an image corresponding to the code portion and an image corresponding to the decorative portion. The image corresponding to the decorative portion may be, for example, the brand logo of the remittance service or affiliated store, or an icon that collectively represents the product.

[0087] A user who wishes to make a donation or offer a donation at an offering counter reads the donation code image 62 into the user terminal device 10 and performs the operation for the remittance process. Generally, it is not easy for a natural person to distinguish the differences between the shapes (patterns) of the encoded first code portion 62A-1, second code portion 62B-1, and third code portion 62C-1. For this reason, a user who visually recognizes the donation code image 62 has difficulty recognizing the type of remittance just by looking at the code portion 62-1.

[0088] In this regard, the donation code image 62 includes an icon image in the pattern decoration section 62-2 and a text information image in the text decoration section 62-3 in addition to the code section 62-1. Therefore, for example, when a user attempts to read the donation code image 62 for the purpose of making a donation, it is easy to avoid accidentally reading the store code image 60.

[0089] When the user terminal device 10 reads the donation code image 62 and transmits the code information to the payment server 100, the determination unit 136 determines whether the code information is appropriate by using the information in the code section 62-1, the graphic decoration section 62-2, and the text decoration section 62-3 of the donation code image 62. For example, the determination unit 136 compares the remittance type corresponding to the installation location URL included in the code information with the remittance type corresponding to the decoration section identification information, and determines that the code information (installation location URL) is appropriate when the two match.

[0090] The decorative portion may be an icon image or a text image, but may consist of only an icon image or a text image, or may have other images added to the icon image or the text image. The donation code image 62 may be provided on the mount or displayed on the tablet display, in which case the decorative portion may be displayed as an animation.

[0091] The donation code image 62 containing the code information acquired by the payment server 100 of the embodiment includes a code section 62-1 containing an installation location URL, and a pattern decoration section 62-2 and a text decoration section 62-3 that decorate the code section 62-1 in different ways for each remittance type corresponding to the remittance destination. This makes it easier to distinguish between the donation code image 62 and the store code image 60, making it less likely that a user will confuse a payment for a donation with a payment for shopping. This makes it less likely that a user will mistake the purpose of using the remittance service.

[0092] In the payment server 100 of the embodiment, the pattern decoration part 62-2 included in the donation code image 62 is formed physically separate from the code part 62-1, but may be formed integrally with the code part 62-1. As an example of a decoration part integrated with the code part 62-1, the color of the code part 62-1 may be different from that of the code part 62-1 so that it functions as a decoration part.

[0093] <Modification> In the embodiment, the control of the screen displayed by the payment application 20 regarding the remittance service is controlled solely by the remittance content transmitted by the payment server 100, but part of the screen control may be performed by the payment application 20. For example, the payment application 20 may have content that serves as a template, and the payment application 20 may apply content provided by the payment server 100 to the content that serves as the template and play it back.

[0094] When the remittance type includes donations that are subject to donation deductions and donations that are not subject to donation deductions (for example, the above-mentioned offerings), the payment server 100 may be configured to provide the payment app 20 with remittance content that displays whether or not a donation deduction is available depending on the remittance type corresponding to the remittance destination information (installation location URL) included in the code information. The presence or absence of a donation deduction may be displayed, for example, in a note on the remittance screen.

[0095] In the embodiment, the donation code image 62 is provided on a mount next to a donation box installed in a store, but may be provided in other locations. The donation code image 62 may be provided on a mount installed, for example, in a street donation box taken out for street donations, next to an offering box at a temple or shrine, or at a temple or shrine's talisman sales counter. The donation code image 62 may be provided with different decorative parts depending on the location where it is installed. For example, the decorative parts of a donation code image 62 installed inside a store and a donation code image 62 installed on a donation box taken outside may be different.

[0096] The above describes the form for carrying out the present invention using an embodiment, but the present invention is not limited to such an embodiment, and various modifications and substitutions can be made within the scope that does not deviate from the gist of the present invention. [Explanation of symbols]

[0097] 1. Electronic payment systems 10 User terminal device 20. Payment App 50 First store terminal device 60 Store Code Image 62 Donation Code Image 62-1 Code section 62-2 Decorative pattern 62-3 Text decoration section 70 Second store terminal device 80 Donation acceptance terminal device 82 Donation Acceptor Interface 90 Code image generator 92 Generation part 94,170 storage section 94A Library 100 Payment Server 110 Communications Department 115 Sorting section 120 Payment Contents Department 130 Payment processing unit 132 Acquisition Department 134 Remittance Processing Unit 136 Judgment section 140 Information Management Department 172 User information 174 Payment Content Information 176 Store Information 176A, 177A Table 1 176B, 177B 2nd table 176C, 177C Third Table 177 Donation Recipient Information 180 Service setting information IM1 top screen IM2 remittance screen IM3 confirmation screen IM4 Remittance completion screen IM5 Remittance screen IM6 Remittance confirmation screen IM7 Remittance completion screen NW Network

Claims

1. A remittance management device that provides a remittance service that accepts a request for remittance from a user account of a user who is a remitter to a receiver account of a receiver who is a remittance destination, an acquisition unit that acquires code information obtained by reading a code image using the terminal device of the user and transmitted by the terminal device; a remittance processing unit that identifies the remittance destination based on the code information, accepts the remittance request from the terminal device, and transfers electronic money equivalent to the accepted remittance amount from the user's account to the acceptor's account, the code image includes a code portion including remittance destination information relating to the remittance destination, and a decoration portion that decorates the code portion in a different manner for each remittance type corresponding to the remittance destination, Further comprising a determination unit for determining whether the code information is appropriate; the acquiring unit acquires, from the terminal device, code information obtained from the code image and decorative part identification information for identifying the decorative part of the code image; The determination unit Refer to the information in which the identification information, the remittance type, and the decorative part specifying information are associated with each other, comparing the remittance type identified from the identification information included in the code information with the remittance type identified from the decoration part identification information to determine whether the code information is appropriate; Money transfer management device.

2. The decoration section includes a different icon for each remittance type. The remittance management device according to claim 1.

3. The icon is positioned in the center of the code portion. The remittance management device according to claim 2.

4. the decoration portion includes a text information image that differs for each remittance type; The remittance management device according to claim 1.

5. The text information image is arranged around the code portion.

5. The remittance management device according to claim 4.

6. The decorative portion includes a color of the code portion that differs for each remittance type. The remittance management device according to claim 1.

7. the remittance processing unit identifies a remittance destination based on a preset remittance type; The remittance management device according to claim 1.

8. A computer of a remittance management device that provides a remittance service that accepts a request for remittance from a user account of a user who is a remitter to a receiver account of a receiver who is a remittance destination, Acquire code information obtained by reading a code image using the user's terminal device and transmitted by the terminal device; Identifying the remittance destination based on the code information, accepting the remittance request from the terminal device, and transferring electronic money equivalent to the accepted remittance amount from the user's account to the receiver's account; the code image includes a code portion including remittance destination information relating to the remittance destination, and a decoration portion that decorates the code portion in a different manner for each remittance type corresponding to the remittance destination, acquiring, from the terminal device, code information obtained from the code image, and decorative part identification information for identifying the decorative part of the code image; Refer to the information in which the identification information, the remittance type, and the decorative part specifying information are associated with each other, comparing the remittance type identified from the identification information included in the code information with the remittance type identified from the decoration part identification information to determine whether the code information is appropriate; How to manage remittances.

9. A computer of a remittance management device that provides a remittance service that accepts a request for remittance from a user account of a user who is a remitter to a receiver account of a receiver who is a remittance destination, reading a code image with the terminal device of the user to obtain code information transmitted by the terminal device; identifying the remittance destination based on the code information, accepting the remittance request from the terminal device, and transferring electronic money equivalent to the accepted remittance amount from the user's account to the acceptor's account; the code image includes a code portion including remittance destination information relating to the remittance destination, and a decoration portion that decorates the code portion in a different manner for each remittance type corresponding to the remittance destination, acquires, from the terminal device, code information obtained from the code image together with decorative part identification information for identifying the decorative part of the code image; Refer to information in which the identification information, the remittance type, and the decorative part specifying information are associated with each other; a remittance type identified from the identification information included in the code information and a remittance type identified from the decoration part identification information are compared to determine whether the code information is appropriate; program.

Images