Information processing device, information processing method and program

Abstract

To provide an information processing device that reduces a load responding to a plurality of code settlement brands.SOLUTION: An information processing device according to an embodiment includes an acquisition unit, a processing unit and an output unit. The acquisition unit acquires a first settlement code. The processing unit selects a first code settlement business operator on the basis of a first business operator identification code included in the first settlement code, requests settlement to a first server of the first code settlement business operator, and receives a settlement result. The output unit outputs the settlement result.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] An embodiment of the present invention relates to an information processing device, an information processing method, and a program. [Background technology]

[0002] In recent years, multiple brands have been developed by multiple code payment operators, and code payments using these multiple brands have become widespread. The code system of the payment code differs for each brand, and the person in charge of the payment device operates to start up a payment program corresponding to the brand used for the payment. Based on the start-up operation, the payment device starts up a payment application program corresponding to the brand used for the payment, reads the presented payment code, and executes payment processing based on the read payment code. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2008-217277 A Summary of the Invention [Problem to be solved by the invention]

[0004] The clerk is required to perform complicated operations according to the brand used for the payment, and the payment device is required to have a payment program according to the brand used for the payment. This places a burden on both the clerk and the payment device, and there is a demand for technology to improve these issues.

[0005] An object of the present invention is to provide an information processing device, an information processing method, and a program that reduce the burden of dealing with multiple code payment brands. [Means for solving the problem]

[0006] The information processing device according to the embodiment includes an acquisition unit, a processing unit, and an output unit. The acquisition unit acquires a first payment code. The processing unit selects a first code payment company based on a first company identification code included in the first payment code, requests a payment from a first server of the first code payment company, and receives a payment result. The output unit outputs the payment result. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram illustrating an example of a schematic configuration of a payment system according to an embodiment. [Diagram 2] FIG. 2 is a functional block diagram illustrating an example of a processor of the payment device according to the embodiment. [Diagram 3] FIG. 3 is a diagram showing an example of a format of a unified payment code applied to the payment system according to the embodiment. [Figure 4] FIG. 4 is a flowchart illustrating an example of a payment process of the payment system according to the embodiment. [Diagram 5] FIG. 5 is a diagram showing an example of a confirmation screen displayed by the settlement device according to the embodiment. [Figure 6] FIG. 6 is a diagram showing an example of a guide screen regarding other acceptable unified code payment brands according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, an embodiment will be described with reference to the drawings. FIG. 1 is a diagram illustrating an example of a schematic configuration of a payment system according to an embodiment. As shown in Fig. 1, a payment system S includes a payment device 1 and a code reader 2. The payment device 1 is an information processing device and can be realized by one computer or a combination of multiple computers. The payment device 1 includes a processor 11, a main memory unit 12, an auxiliary memory unit 13, an input unit 14, an output unit 15, a device interface 16, and a communication interface 17.

[0009] Processor 11 corresponds to the central part of the computer and performs calculations related to the payment processing. Processor 11 executes control to realize the payment processing based on programs such as system software and application software stored in at least one of main memory unit 12 and auxiliary memory unit 13. Processor 11 is, for example, a central processing unit (CPU), a micro processing unit (MPU), or a digital signal processor (DSP). Alternatively, processor 11 is a combination of two or more of these.

[0010] The main memory unit 12 includes a read-only memory (ROM) which is a non-transitory computer-readable storage medium, and a random-access memory (RAM) which stores data to be used temporarily. The ROM stores part or all of the programs executed by the processor 11, and further stores data and various setting values ​​used by the processor 11 when performing various processes. The RAM 13 is a work area for storing data to be used temporarily by the processor 11 when performing various processes, and data generated by the processes in the processor 11.

[0011] The auxiliary storage unit 13 is a non-transitory computer-readable storage medium, such as an EEPROM (electric erasable programmable read-only memory) (registered trademark), a HDD (hard disk drive), or an SSD (solid state drive). The auxiliary storage unit 13 stores a part or all of the programs executed by the processor 11, data used by the processor 11 in performing various processes, data generated by the processes in the processor 11, various setting values, and the like.

[0012] The program stored in at least one of the main memory unit 12 and the auxiliary memory unit 13 includes a program for payment processing. For example, the payment device 1 is transferred to a code payment business operator with the above program stored in at least one of the main memory unit 12 and the auxiliary memory unit 13. Alternatively, the payment device 1 may be transferred to a code payment business operator or the like by a non-transitory computer-readable storage medium in which the above program is stored. In this case, the program stored in the non-transitory computer-readable storage medium is written to at least one of the main memory unit 12 and the auxiliary memory unit 13 under the operation of a person in charge. The non-transitory computer-readable storage medium in which the above program is stored is, for example, a removable storage medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory. Alternatively, the above program may be downloaded via a network or the like and written to at least one of the main memory unit 12 and the auxiliary memory unit 13.

[0013] The input unit 14 includes a keyboard, a numeric keypad, a person in charge touch panel, and a user touch panel. The output unit 15 includes a person in charge display, a user display, and a speaker. For example, a person in charge touch panel display may be configured by the person in charge touch panel and the person in charge display. Similarly, a user touch panel display may be configured by the user touch panel and the user display. The input unit 14 accepts instruction input from the person in charge or the user and notifies the processor 11. The output unit 15 displays various information to the person in charge or the user.

[0014] The device interface 16 connects to each device such as the code reader 2. For example, the device interface 16 acquires various codes such as a product code, a billing code, or a payment code read by the code reader 2.

[0015] The communication interface 17 connects to an external device such as an external server via a communication network. For example, the communication interface 17 communicates with a point of sale (POS) server, transmits a product code to the POS server, and receives product data corresponding to the product code from the POS server. The POS server stores product data corresponding to each product, and the product data corresponding to one product includes information such as a product code, a product name, a product unit price, and a discount amount. The communication interface 17 also communicates with a billing processing server, transmits a billing code to the billing processing server, and receives billing data corresponding to the billing code from the billing processing server. The billing processing server stores billing data corresponding to each bill, and the billing data includes information such as a billing code, product details, and billing amount. The communication interface 17 also communicates with a payment server of each payment code business operator, and transmits and receives information related to payment.

[0016] The code reader 2 reads various codes such as product codes, billing codes, and payment codes, and outputs the read codes. For example, the code reader 2 optically reads a product code recorded on or attached to a product, and outputs the read payment code to the device interface 16 of the payment device 1. The code reader 2 also optically reads a billing code recorded on an invoice or the like, and outputs the read billing code to the device interface 16 of the payment device 1. The code reader 2 also optically reads a payment code displayed on the display of a communication terminal such as a smartphone, and outputs the read payment code to the device interface 16 of the payment device 1.

[0017] Fig. 2 is a functional block diagram showing an example of a processor of the payment device according to the embodiment. As shown in Fig. 2, the processor 11 includes an acquisition unit 111, a processing unit 112, and an output unit 113. The processor 11 executes a program stored in at least one of the main memory unit 12 and the auxiliary memory unit 13, and realizes acquisition of a payment code by the acquisition unit 111, selection of a code payment business operator and receipt of a payment result by the processing unit 112, output of the payment result by the output unit 113, etc. The processor 11 also realizes acquisition of a payment code, selection of a code payment business operator and receipt of a payment result, and output of the payment result in cooperation with a hardware configuration such as an input unit 14, an output unit 15, a device interface 16, and a communication interface 17.

[0018] The acquisition unit 111 acquires a code received by the device interface 16. For example, the acquisition unit 111 acquires a payment code received by the device interface 16. The payment codes include unified payment codes and non-unified payment codes for each code payment brand. The unified payment code is a payment code whose format has been unified among code payment businesses that are members of a unified payment code business. The unified payment code includes a business identification code that identifies the business. The acquisition unit 111 acquires a first payment code including a first business identification code that indicates a first business, and a second payment code including a second business identification code that indicates a second business, etc. The non-unified payment code is a payment code with a unique format.

[0019] The processing unit 112 selects a code payment company based on the company identification code included in the unified payment code, requests payment to the server of the selected code payment company, and receives the payment result from this server. For example, the processing unit 112 selects a second code payment company based on the first company identification code included in the first payment code, requests payment to the first server of the selected first code payment company, and receives the payment result from this first server. The processing unit 112 processes the second payment code in the same manner.

[0020] The output unit 113 outputs the payment result to the output unit 15. The output unit 15 displays a payment screen showing the payment result.

[0021] FIG. 3 is a diagram showing an example of a format of a unified payment code applied to the payment system according to the embodiment. All code payment businesses participating in the unified payment code project use the unified payment code. As shown in Figure 3, the unified payment code includes a payment ID information area and a free area. The payment ID information area includes a business identification code section and a token section. The business identification code section includes a fixed identification code that identifies it as a unified payment code, and a business identification code that identifies the code payment business.

[0022] FIG. 4 is a flowchart illustrating an example of a payment process of the payment system according to the embodiment. The payment device 1 acquires information related to the payment amount or billing amount, etc., and executes payment based on the acquired information. For example, the processor 11 of the payment device 1 acquires one or more product codes from the code reader 2, receives product data corresponding to the one or more product codes from the POS server, calculates the payment amount based on the product data, and waits for payment.

[0023] A user who uses the unified payment code displays and presents the unified payment code on the display of a communication terminal such as a smartphone. The person in charge selects or specifies the unified code payment mode from the payment screen of the input unit 14 of the payment device 1. The processor 11 starts the unified code payment program in response to the selection of the unified code payment mode. Note that in this embodiment, it is not necessary to select or specify a code payment brand for each code payment business operator and start a code payment program for each code payment brand. This reduces the operational burden on the person in charge and the processing load of the code payment program of the payment device 1.

[0024] The clerk holds the reading unit of the code reader 2 over the display on which the unified payment code is displayed. The code reader 2 reads the displayed unified payment code through the reading unit and outputs the read unified payment code to the device interface 16. The device interface 16 receives the unified payment code and outputs it to the processor 11.

[0025] The acquisition unit 111 of the processor 11 acquires the unified payment code (ACT1, YES). It is also possible to make it unnecessary to select the code payment mode described above, and to start the unified code payment program when the unified payment code read by the code reader 2 is acquired by the acquisition unit 111 as a trigger. In this case, the person in charge can omit the operation of selecting or specifying the unified code payment mode, which can further reduce the burden.

[0026] The processing unit 112 detects a fixed identification code that identifies the unified payment code from the unified payment code (ACT2, YES), and when it detects a business identification code that identifies the code payment business (ACT3, YES), it selects a code payment business based on the business identification code (ACT4). For example, the processing unit 112 selects a first code payment business based on a first business identification code included in the acquired first unified payment code.

[0027] The processing unit 112 selects a code payment business operator to be the payment destination from among all code payment business operators affiliated with the unified code payment business based on the business identification code included in the unified payment code. The auxiliary memory unit 13 stores an affiliate list including business identification codes corresponding to all code payment business operators affiliated with the unified code payment business. If the first business identification code is included in the affiliate list, the processing unit 112 approves the first code payment business operator as the payment destination of the unified code payment business. Also, if the first business identification code is not included in the business limited list, the processing unit 112 denies the first code payment business operator as the payment destination of the unified code payment business.

[0028] Furthermore, the processing unit 112 determines whether or not to accept the selected code payment business operator as a payment destination based on the business identification code. The decision of which business operator to accept payment from among all code payment businesses affiliated with the unified code payment business is up to the business using code payment, such as a retailer that introduces the payment device 1. The auxiliary memory unit 13 stores a business limited list including business identification codes corresponding to the accepted code payment businesses. If the first business identification code is included in the business limited list, the processing unit 112 accepts the first code payment business operator as a payment destination (ACT5, YES). Also, if the first business identification code is not included in the business limited list, the processing unit 112 does not accept the first code payment business operator as a payment destination (ACT5, NO).

[0029] The processing unit 112 checks whether the first code payment company that was accepted as the payment destination can make the payment. For example, if the remaining balance that can be paid by the first code payment company is equal to or greater than the payment amount (ACT6, YES), the processing unit 112 outputs confirmation information for the output unit 113 to confirm that the payment is requested to the first code payment company (ACT7). In response to this, the output unit 15 such as a display displays a confirmation screen for confirming that the payment is requested to the first code payment company. FIG. 5 is a diagram showing an example of a confirmation screen displayed by the payment device according to the embodiment. For example, the user touch panel display of the output unit 15 displays the confirmation screen. The confirmation screen includes information about the code payment brand (first code payment company) selected in ACT4, and an input button for confirmation, etc.

[0030] The payment device 1 that supports the unified payment code does not require the selection or designation of a code payment brand offered by each code payment business operator. In other words, the person in charge does not need to know in advance which code payment brand the unified payment code presented by the user belongs to. Even if the user presents a unified payment code of an unintended code payment brand, the payment device 1 can proceed with the payment based on the presented unified payment code. In this embodiment, when the user presents a unified payment code of an unintended code payment brand, confirmation information is output to make the user aware of the fact that the user has presented the unified payment code of an unintended code payment brand, and to make the user aware of the fact that the first code payment business operator selected as the payment destination is requested to make the payment. This makes it possible to prevent payment by a code payment brand that the user does not intend.

[0031] When an input button such as "Confirm" displayed on the user touch panel display of the output unit 15 is selected, the input unit 14 detects this, and the processing unit 112 determines that the confirmation is OK (ACT8, YES). Based on this determination, the processing unit 112 requests payment from the first server of the first code payment company (ACT9). The communication interface 17 communicates with the first server of the first code payment company, sends a payment request, and receives the payment result. The processing unit 112 receives the payment result (ACT10), and the output unit 113 outputs the payment result (ACT11). The output unit 15 displays the payment result. The payment result includes information such as the code payment brand name and the payment amount.

[0032] Also, in ACT5, if the first code payment company is not accepted as a payment destination (ACT5, NO), the processing unit 112 instructs the output of guidance information regarding other acceptable unified code payment brands instead of the first code payment company. The output unit 113 outputs guidance information regarding other acceptable unified code payment brands (ACT12). The user touch panel display composed of the input unit 14 and the output unit 15 displays a guidance screen regarding other acceptable unified code payment brands. For example, the output unit 113 outputs guidance information indicating that a second code payment company can be selected as a payment destination instead of the first code payment company. The user touch panel display displays a guidance screen indicating that a second code payment company can be selected as a payment destination instead of the first code payment company.

[0033] 6 is a diagram showing an example of a guide screen for other acceptable unified code payment brands according to an embodiment. As shown in FIG. 6, the guide screen includes a list of code payment brands corresponding to the unified payment code presented and read by the user, and other acceptable unified code payment brands.

[0034] Next, a user who wishes to use the unified payment code displays and presents the desired unified payment code on the display of a communication terminal such as a smartphone. The clerk holds the reading unit of the code reader 2 over the display on which the unified payment code is displayed. The code reader 2 reads the displayed unified payment code via the reading unit and outputs the read unified payment code to the device interface 16. The device interface 16 receives the unified payment code and outputs it to the processor 11.

[0035] The acquisition unit 111 of the processor 11 acquires the unified payment code (ACT1), and the processing unit 112 detects a fixed identification code that identifies the unified payment code (ACT2, YES), and detects a business identification code that identifies the code payment business (ACT3, YES). For example, if the business identification code is a second code payment business, the processing unit 112 changes the selected first code payment business to the second code payment business. That is, after the first code payment business is selected, when the acquisition unit 111 acquires the second payment code, the processing unit 112 changes the payment destination from the first code payment business to the second code payment business based on the second business identification code included in the second payment code (ACT4).

[0036] In this way, the payment device 1 displays a guide screen regarding other acceptable unified code payment brands, and changes the selected code payment brand to the desired code payment brand simply by acquiring the desired unified payment code presented by the user. This change process reduces the burden on the person in charge.

[0037] In addition, in ACT6, if the remaining balance payable by the first code payment company is less than the payment amount (ACT6, NO), the output unit 113 outputs guidance information indicating that the remaining balance payable is less than the payment amount. In response to this, the output unit 15 such as a display displays a guidance screen indicating that the remaining balance payable is less than the payment amount (ACT13).

[0038] A user who wishes to continue using another unified payment code displays and presents the desired unified payment code on the display of a communication terminal such as a smartphone. The clerk holds the reading unit of the code reader 2 over the display on which the unified payment code is displayed. The code reader 2 reads the displayed unified payment code via the reading unit and outputs the read unified payment code to the device interface 16. The device interface 16 receives the unified payment code and outputs it to the processor 11.

[0039] The acquisition unit 111 of the processor 11 acquires the unified payment code (ACT1), and the processing unit 112 detects a fixed identification code that identifies the unified payment code (ACT2, YES), and detects a business identification code that identifies the code payment business (ACT3, YES). For example, if the business identification code is a second code payment business, the processing unit 112 changes the selected first code payment business to the second code payment business. That is, after the first code payment business is selected, when the acquisition unit 111 acquires the second payment code, the processing unit 112 changes the payment destination from the first code payment business to the second code payment business based on the second business identification code included in the second payment code (ACT4).

[0040] In this way, the payment device 1 displays a guide screen regarding other acceptable unified code payment brands, and changes the selected code payment brand to the desired code payment brand simply by acquiring the desired unified payment code presented by the user. This change process can reduce the burden on the person in charge when the remaining balance is insufficient.

[0041] Also, in ACT7, a user who wishes to change the code payment destination does not select an input button such as "Confirm" displayed on the user touch panel display composed of the input unit 14 and the output unit 15. The user then displays and presents the desired unified payment code on the display of a communication terminal such as a smartphone. The person in charge holds the reading unit of the code reader 2 over the display on which the unified payment code is displayed. The code reader 2 reads the displayed unified payment code via the reading unit and outputs the read unified payment code to the device interface 16. The payment device 1 receives the unified payment code via the device interface 16 and executes the payment process.

[0042] Also, if the user displays and presents a non-uniform payment code on the display of a communication terminal such as a smartphone, in ACT2, a fixed identification code that identifies the unified payment code is not detected (ACT2, NO). In this case, the processing unit 112 determines whether the code payment brand is manually selectable, that is, whether the code payment brand adopts a non-uniform payment code, based on the acquired payment code. If the processing unit 112 determines that the code payment brand is manually selectable (ACT14, YES), the person in charge selects the code payment brand from the payment screen of the input unit 14 of the payment device 1 (ACT15). The processing unit 112 starts a code payment program corresponding to the selected code payment brand, requests payment from the server of the selected code payment brand (ACT9), receives the payment result (ACT10), and the output unit 113 outputs the payment result (ACT11).

[0043] When the processing unit 112 determines that the code payment brand is not manually selectable (ACT14, NO), the processing proceeds to payment processing using other payment methods such as cash or credit card (ACT16).

[0044] According to the present embodiment described above, it is possible to provide an information processing device, an information processing method, and a program that reduce the burden of dealing with multiple code payment brands.

[0045] Although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope and spirit of the invention, and are included in the scope of the invention and its equivalents described in the claims. [Explanation of symbols]

[0046] S: Payment system 1. Payment device 2...Code reader 11…Processor 12...Main memory 13…Auxiliary storage unit 14...Input section 15...Output section 16...Equipment Interface 17...Communication interface 111…Acquisition Department 112... Processing section 113...Output section

Claims

1. an acquisition unit that acquires a first payment code; A processing unit that selects a first code payment company based on a first company identification code included in a first payment code, requests a payment to a first server of the first code payment company, and receives a payment result; an output unit that outputs the settlement result; An information processing device comprising:

2. The information processing device of claim 1 , wherein the output unit outputs confirmation information for confirming that the first code payment company has been selected as a payment destination and that payment is to be requested.

3. 3. The information processing device of claim 1 or 2, wherein the output unit outputs guidance information indicating that a second code payment company can be selected as the payment destination instead of the first code payment company when payment by the first code payment company is not accepted.

4. 4. An information processing device according to claim 1, wherein when the first code payment company is selected and a second payment code is acquired by the acquisition unit, the processing unit changes the payment destination from the first code payment company to the second code payment company based on a second company identification code contained in the second payment code.

5. Obtain a first payment code; Selecting a first code payment company based on a first company identification code included in the first payment code, requesting payment from a first server of the first code payment company, and receiving a payment result; and outputting the settlement result.

6. The information processing method according to claim 5 , further comprising outputting confirmation information for confirming that the first code payment company is selected as the payment destination and a payment is requested.

7. An information processing method according to claim 5 or 6, which outputs guidance information indicating that a second code payment company can be selected as the payment destination instead of the first code payment company when payment by the first code payment company is not accepted.

8. An information processing method according to any one of claims 5 to 7, wherein after the first code payment company is selected and a second payment code is obtained, the payment destination is changed from the first code payment company to the second code payment company based on a second company identification code contained in the second payment code.

9. On the computer, obtaining a first payment code; A step of selecting a first code payment company based on a first company identification code included in a first payment code, requesting a payment to a first server of the first code payment company, and receiving a payment result; A procedure for outputting the settlement result and a program for executing the procedure.

10. On the computer, A program according to claim 9 for executing a procedure for outputting confirmation information for confirming that the first code payment company is selected as the payment destination and that payment is requested.

11. On the computer, A program according to claim 9 or 10 for executing a procedure for outputting guidance information indicating that a second code payment company can be selected as the payment destination instead of the first code payment company when payment by the first code payment company is not accepted.

12. On the computer, Any one of claims 9 to 11, a program for executing a procedure for changing the payment destination from the first code payment provider to the second code payment provider based on a second provider identification code contained in the second payment code when the first code payment provider is selected and a second payment code is obtained.

Images