Sales data processing apparatus and program

Abstract

To provide a sales data processing apparatus and program configured to improve the convenience related to electronic settlement.SOLUTION: A sales data processing apparatus includes: transmission means which transmits a use request including identification information of a consumer who uses an electronic settlement service and the amount used for the electronic settlement service, to a settlement service which provides the electronic settlement service; confirmation means which confirms a validity period in which the electronic settlement service is available, based on a response to the use request from the settlement server; and settlement means which executes settlement processing for a transaction using the electronic settlement service if it is confirmed to be within the validity period by the confirmation means. When expiration is confirmed at re-transmission of the use request after it is confirmed to be within the validity period by the confirmation means in the same transaction, the settlement means forcibly executes the settlement processing for the transaction.SELECTED DRAWING: Figure 8

Description

[Technical Field]

[0001] An embodiment of the present invention relates to a sales data processing device and a program. [Background technology]

[0002] In recent years, cashless transactions have become more common, and consumers are now using electronic payments when purchasing goods and services (hereinafter collectively referred to as "goods"). In electronic payments, information is sent and received between a payment terminal, such as a POS (Point of Sales) terminal installed in a store, and a payment server managed by a payment service provider, and payment for one transaction is made.

[0003] For example, in a prepaid payment service, which is a form of electronic payment, a payment server manages the balance (hereinafter also referred to as prepaid balance) deposited in advance by the consumer in association with the consumer's identification information, along with the expiration date, etc. In addition, the payment device obtains information on the expiration date and prepaid balance from the payment server by transmitting the identification information of the consumer using the service together with the usage amount to be settled.

[0004] Furthermore, when the prepaid balance is insufficient to cover the cost of the product, the payment terminal allows for a combined payment method using cash or other payment methods to pay the remaining amount. In such a case, the payment terminal sends the amount used equal to the prepaid balance to the payment server, and the payment is made using the prepaid balance, and the remaining amount is paid using the other payment method.

[0005] However, with the above-described configuration, the expiration date may change during a transaction at the payment terminal, causing the expiration date to expire. For example, even if the expiration date was not reached when the prepaid balance was confirmed to be insufficient, the date may have changed and the expiration date may have expired by the time the combined payment is made. In such cases, conventional payment devices cannot execute electronic payment (prepaid payment) if the expiration date has expired at the time of payment, and require operations such as canceling the transaction or selecting another payment method, resulting in a lack of convenience. Summary of the Invention [Problem to be solved by the invention]

[0006] The problem to be solved by the present invention is to provide a sales data processing device and a program that can improve the convenience of electronic payments. [Means for solving the problem]

[0007] The sales data processing device of the embodiment comprises a transmission means for transmitting a usage request including identification information of a consumer using an electronic payment service and the amount used for the electronic payment service to a payment server that provides the electronic payment service; a confirmation means for confirming the expiration date for using the electronic payment service based on the response from the payment server to the usage request; and a payment means for executing payment processing for a transaction using the electronic payment service if the confirmation means confirms that the expiration date is within the expiration date, and if the confirmation means confirms that the expiration date has expired upon re-transmission of the usage request for the same transaction, the payment means forcibly executes payment processing for the transaction. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a payment system according to an embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of a sales data processing device according to the embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example of a hardware configuration of the payment server according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of a data configuration of a consumer management table according to the embodiment. [Figure 5] FIG. 5 is a diagram illustrating an example of the functional configuration of the sales data processing device and the settlement server according to the embodiment. [Figure 6]FIG. 6 is a sequence diagram showing an example of data exchange relating to code payment performed between the sales data processing device and the payment server according to the embodiment. [Figure 7] FIG. 7 is a flowchart illustrating an example of sales data processing performed by the sales data processing device according to the embodiment. [Figure 8] FIG. 8 is a flowchart illustrating an example of code payment processing performed by the sales data processing device according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] A sales data processing device and a program according to an embodiment will be described below with reference to the drawings. In the embodiment described below, an example will be described in which the device is applied to a payment system installed in a retail store such as a supermarket. Note that the present invention is not limited to the embodiment described below.

[0010] 1 is a diagram showing an example of the configuration of a payment system 1 according to an embodiment. As shown in FIG. 1, the payment system 1 includes a sales data processing device 10, a management server 20, and a payment server 30.

[0011] The sales data processing device 10 and the management server 20 are communicatively connected via a network Na. The network Na may be a LAN (Local Area Network), a public communication network, a mobile communication network, or the like, either alone or in combination as appropriate.

[0012] The sales data processing device 10 is a sales data processing device such as a POS (Point Of Sales) terminal installed in the store ST. The sales data processing device 10 performs sales data processing such as registration processing and payment processing of products purchased by customers in response to operations by an operator. The operator of the sales data processing device 10 is not limited to a sales clerk at the store ST, but may also be the customer himself / herself.

[0013] The product registration process is a process for registering information that can identify the product that the consumer is purchasing. The payment process is a process for settling the price of the product related to one transaction registered in the registration process with the amount paid by the consumer (hereinafter also referred to as the payment amount). Hereinafter, the registration process and the payment process are collectively referred to as sales data processing.

[0014] The management server 20 is a server device such as a store server. The management server 20 manages the sales data processing performed in the store ST by working in cooperation with the sales data processing device 10. For example, the management server 20 manages a product master (not shown) of products sold in the store ST and provides it to each sales data processing device 10. The product master is a database or data table that associates identification information (hereinafter also referred to as product code) that can identify each product with product information such as the product name and price. The management server 20 also collects sales data related to the sales data processing performed by the sales data processing device 10. The management server 20 manages the sales of products at the store based on the collected sales data.

[0015] In this embodiment, the management server 20 is provided in the store ST, but the present invention is not limited to this and may be provided in a data center or the like outside the store ST. In addition, in this embodiment, the management server 20 is realized by one server device, but the present invention is not limited to this and may be realized in the form of a cloud server or the like by multiple server devices.

[0016] The sales data processing device 10 and management server 20 of the store ST can communicate with the payment server 30 connected to the network Nb via the network Na. The network Nb can be the Internet, a VPN (Virtual Private Network), a LAN, a public communication network, a mobile communication network, etc., either alone or in combination as appropriate. As an example, the network Nb can be a combination of the Internet and a mobile communication network.

[0017] The payment server 30 is a server device managed by a payment service provider that provides electronic payment services. Specifically, the payment server 30 of this embodiment manages the charge balance deposited in advance by the consumer and cooperates with the sales data processing device 10 to provide a prepaid payment service in which payments are made within the charge balance. Note that in this embodiment, the payment server 30 will be described as providing an electronic payment service that uses code symbols such as barcodes and two-dimensional codes (hereinafter also referred to as code payment).

[0018] The configurations of the main devices included in the payment system 1 will be described below.

[0019] Fig. 2 is a diagram showing an example of the hardware configuration of the sales data processing device 10. As shown in Fig. 2, the sales data processing device 10 includes a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, a storage unit 14, a display unit 15, an operation unit 16, a reading unit 17, a printing unit 18, and a communication unit 19.

[0020] The CPU 11 is an example of a processor and controls the overall operation of the sales data processing device 10. The ROM 12 stores various programs. The RAM 13 is a workspace for expanding the programs and various data. The RAM 13 also stores information about the products registered in the registration process, flags (described later), and the like.

[0021] The CPU 11, ROM 12, and RAM 13 are connected via a bus or the like to form a computer-configured control unit 100. The control unit 100 realizes various functions by the CPU 11 operating in accordance with a program stored in the ROM 12 or the storage unit 14 and loaded into the RAM 13.

[0022] The storage unit 14 has a storage medium such as a hard disk drive (HDD), a solid state drive (SSD), or a flash memory, and maintains its stored contents even when the power is turned off. The storage unit 14 stores programs that can be executed by the CPU 11 and various setting information. The storage unit 14 may also store other information. For example, the storage unit 14 may store a product master provided by the management server 20.

[0023] The display unit 15 is a display device such as an LCD (Liquid Crystal Display). The display unit 15 displays various information under the control of the CPU 11. The operation unit 16 is an input device such as a keyboard or a pointing device. For example, the operation unit 16 has operation keys for instructing the end of the registration process or the start of the transaction process. The operation unit 16 outputs the operation content input via the input device to the CPU 11. The operation unit 16 may also be a touch panel provided on the display unit 15.

[0024] The reading unit 17 is a reading device that reads information from various media. Specifically, the reading unit 17 is a reading device that can read code symbols such as barcodes and two-dimensional codes. For example, the reading unit 17 reads the product code of a product from a code symbol attached to the product. The reading unit 17 also reads identification information (hereinafter referred to as consumer ID) that can identify a consumer from a code symbol for code payment displayed on a mobile terminal (e.g., a smartphone) carried by the consumer.

[0025] Furthermore, reading unit 17 may be a reading device capable of reading information from a card medium. For example, in a store that uses a magnetic card as a card medium, reading unit 17 capable of reading a magnetic card can be used. In a store that uses a card with a wireless tag attached as a card medium, reading unit 17 capable of reading a wireless tag can be used. In this case, reading unit 17 reads information necessary for credit card payment, such as a credit number that can identify a consumer, from a card medium such as a credit card.

[0026] The printing unit 18 is a printing device such as a thermal printer. For example, under the control of the control unit 100, the printing unit 18 issues receipts or the like on which the details of the merchandise for which payment has been processed and the purchase amount are printed. The communication unit 19 is a wired or wireless communication interface connectable to the network Na. The communication unit 19 communicates with external devices such as the management server 20 and the payment server 30 via the network Na.

[0027] Fig. 3 is a diagram showing an example of the hardware configuration of the payment server 30. As shown in Fig. 3, the payment server 30 includes a CPU 31, a ROM 32, a RAM 33, a storage unit 34, a communication unit 35, and the like.

[0028] The CPU 31 is an example of a processor, and controls the overall operation of the payment server 30. The ROM 32 stores various programs. The RAM 33 is a workspace for expanding programs and various data.

[0029] The CPU 31, ROM 32, and RAM 33 are connected via a bus or the like to form a computer-configured control unit 300. The control unit 300 realizes various functions by the CPU 31 operating in accordance with a program stored in the ROM 32 or the storage unit 34 and loaded into the RAM 33.

[0030] The storage unit 34 has a storage medium such as an HDD, SSD, or flash memory, and maintains its stored contents even when power is cut off. The storage unit 34 stores programs that the CPU 31 can execute and various setting information.

[0031] The storage unit 34 also stores a consumer management table 341 and the like. The consumer management table 341 is a database or data table for storing and managing the charge balance and the like of consumers who use code payment.

[0032] FIG. 4 is a diagram showing an example of the data configuration of the consumer management table 341. As shown in FIG. 4, the consumer management table 341 stores and manages each consumer's consumer ID, charge balance, and expiration date in association with each other. Here, the consumer ID is identification information that can identify each consumer who uses code payment. The charge balance is information that indicates the amount that the consumer corresponding to the consumer ID has previously charged. The expiration date is information that indicates the expiration date (year, month, day) until which code payment can be used.

[0033] 3, the communication unit 35 is a wired or wireless communication interface connectable to the network Nb. The communication unit 35 communicates with external devices such as the sales data processing device 10 via the network Nb and the network Na.

[0034] Next, the functional configurations of the sales data processing device 10 and the settlement server 30 will be described with reference to Fig. 5. Fig. 5 is a diagram showing an example of the functional configurations of the sales data processing device 10 and the settlement server 30.

[0035] First, we will explain the functional configuration of the sales data processing device 10. The control unit 100 of the sales data processing device 10 cooperates with programs stored in the ROM 12 and the storage unit 14 to include a reading control unit 101 and a sales data processing unit 102 as functional components.

[0036] The reading control unit 101 controls the reading unit 17 and accepts or acquires information read by the reading unit 17. For example, when the reading unit 17 reads a product code from a code symbol attached to a product, the reading control unit 101 accepts input of the product code. Also, for example, when the reading unit 17 reads a consumer ID from a code symbol displayed on the consumer's terminal, the reading control unit 101 accepts input of the consumer ID. It is assumed that the product code and the consumer ID can be distinguished from each other by differences in code systems, etc.

[0037] The sales data processing unit 102 is an example of a transmission means, a confirmation means, a settlement means, a determination means, an output means, and a display means. When the sales data processing unit 102 receives an operation to start a transaction via the operation unit 16, for example, the sales data processing unit 102 starts processing sales data related to one transaction.

[0038] When the sales data processing unit 102 starts sales data processing, it waits for the input of a product code in cooperation with the reading control unit 101. When a product code is input, the sales data processing unit 102 acquires product information corresponding to the product code by referencing the product master. Next, the sales data processing unit 102 associates the acquired product information with the input product code and stores it in the RAM 13 or the like, thereby executing registration processing for the product corresponding to the product code. Furthermore, the sales data processing unit 102 displays details such as the product name and price on the display unit 15 based on the product information of the registered product.

[0039] When the sales data processing unit 102 receives a closing operation via the operation unit 16 to instruct the end of the registration process or the start of the payment process, it calculates a total amount based on the prices of the registered products, etc. Next, the sales data processing unit 102 displays a screen for selecting a payment method (hereinafter referred to as a payment method selection screen) on the display unit 15. For example, the sales data processing unit 102 displays a payment method selection screen on the display unit 15, which includes operators that allow selection of multiple payment methods, such as cash, code payment, and credit card payment.

[0040] When the sales data processing unit 102 accepts the selection of a payment method, it executes a payment process to settle the total amount of the products using the accepted payment method. For example, when code payment is selected, the sales data processing unit 102 cooperates with the reading control unit 101 to wait for the input of a consumer ID. When the consumer ID is input, the sales data processing unit 102 sends a usage request including the input consumer ID and the total amount of the products to the payment server 30. The payment server 30 checks whether code payment is available based on the usage request.

[0041] When the code payment is executed in the payment server 30, the sales data processing unit 102 acquires response information indicating the completion of the code payment from the payment server 30 as a response to the usage request.

[0042] Furthermore, if the payment server 30 determines that code payment is not available, the sales data processing unit 102 acquires response information indicating the reason for the impossibility as a response to the usage request from the payment server 30. For example, if code payment cannot be performed due to expiration of the validity period or insufficient prepaid balance, the sales data processing unit 102 acquires response information indicating the reason for the impossibility from the payment server 30.

[0043] For example, if the response information includes information indicating an expiration date, the sales data processing unit 102 determines that the consumer's account related to the code payment has expired and is unusable. In this case, the sales data processing unit 102 displays a payment method selection screen on the display unit 15, which allows the consumer to select a payment method other than the code payment. The sales data processing unit 102 then executes the payment process using the selected other payment method.

[0044] Furthermore, for example, if the response information includes information indicating an insufficient balance in the charge balance, the sales data processing unit 102 determines that the consumer's account for code payment is within its expiration date and has an insufficient balance. In other words, the sales data processing unit 102 determines that code payment is available within the charge balance. In this case, the sales data processing unit 102 displays a payment method selection screen on the display unit 15, allowing the consumer to select a payment method for the remaining amount after subtracting the charge balance from the total price of the goods. The sales data processing unit 102 then sends a usage request including the input consumer ID and the amount of the charge balance to the payment server 30 to execute code payment, and also executes payment processing for the remaining amount using the selected other payment method. In other words, the sales data processing unit 102 executes a combined payment using code payment and another payment method.

[0045] Then, when the sales data processing unit 102 completes the settlement process, it controls the printing unit 18 to cause the printing unit 18 to print a detailed receipt showing the details of the transaction.

[0046] On the other hand, the control unit 300 of the payment server 30 cooperates with programs stored in the ROM 32 and the storage unit 34, as shown in FIG. 5, to provide a code payment processing unit 301 as a functional configuration.

[0047] The code payment processing unit 301 executes code payment based on a usage request sent from the sales data processing device 10. Specifically, when the code payment processing unit 301 receives a usage request from the sales data processing device 10, it reads the charge balance and expiration date corresponding to the consumer ID included in the usage request from the consumer management table 341 and determines whether code payment is possible.

[0048] For example, if the current date is the expiration date, the code payment processing unit 301 determines that code payment is unavailable. In this case, the code payment processing unit 301 transmits response information indicating the expiration date to the sales data processing device 10 as response information to the usage request.

[0049] Furthermore, even if the current date is within the expiration date, if the charge balance is insufficient to cover the amount specified in the usage request, the code payment processing unit 301 determines that code payment is not available. In this case, the code payment processing unit 301 transmits response information indicating an insufficient balance to the sales data processing device 10 as response information to the usage request. Note that the code payment processing unit 301 may transmit the charge balance together with the response information indicating the insufficient balance to the sales data processing device 10.

[0050] Furthermore, if the current date is within the expiration date and the charge balance is equal to or greater than the amount specified in the usage request, the code payment processing unit 301 determines that code payment is available. In this case, the code payment processing unit 301 executes code payment by subtracting the amount specified in the usage request from the charge balance. The code payment processing unit 301 then sends response information indicating that code payment has been completed to the sales data processing device 10.

[0051] In the above-described configuration of the payment system 1, if the date changes during a transaction at the sales data processing device 10, the validity period may expire.

[0052] For example, suppose the expiration date of the code payment is "June 21, 2023," and the date and time when the sales data processing device 10 first sent a usage request was "June 21, 2023, 11:59 PM." In this case, the payment server 30 determines that the expiration date is within the expiration date, but if the charge balance is insufficient, the code payment is not performed and response information indicating the insufficient balance is sent to the sales data processing device 10. When the sales data processing device 10 receives the response information indicating the insufficient balance, the operator confirms with the consumer whether to cancel the code payment or to perform combined payment using another payment method in addition to the code payment.

[0053] If code payment is to be used in combination with another payment method, the sales data processing device 10 will resend a usage request to the payment server 30, but if the date at this point is "June 22, 2023," the payment server 30 will determine that the expiration date has passed. Therefore, even though the sales data processing device 10 has been instructed to execute code payment in combination with another payment method, the code payment cannot be used due to the expiration date, and the user will have to cancel the transaction or select the payment method again.

[0054] Therefore, in the sales data processing device 10 of this embodiment, after confirming that the expiration date is not yet reached within the same transaction, even if the expiration date has expired due to a change in date, the code payment is continued as it is still within the expiration date.

[0055] Specifically, the sales data processing unit 102 confirms that the consumer's account is within its expiration date based on the response information from the payment server 30, and then considers the code payment to be valid and continues the payment process, even if the response information sent again from the payment server 30 in a combined payment, etc. indicates that the account has expired. However, since the payment server 30 cannot execute code payment using an expired charge balance, the sales data processing unit 102 forcibly executes the payment process by considering that code payment has been executed by the payment server 30.

[0056] This allows the sales data processing device 10 to make payment even if the code payment expiration date has expired during the transaction. Therefore, the consumer can purchase the product in the same way as if the code payment had been executed normally, without having to cancel the transaction or select another payment method.

[0057] When the sales data processing unit 102 forcibly performs an expired payment process, it is preferable that the sales data processing unit 102 outputs data such as a log recording details of the payment process, such as the amount paid in the payment, the consumer ID of the consumer, and the date and time of the transaction, to the storage unit 14. This allows the store to easily apply for a deduction of the amount paid in the payment process from the charge balance of the payment server 30 based on the log.

[0058] Furthermore, the details of the payment process are not limited to being recorded in a log format, but may be recorded in other formats such as a journal. Furthermore, the details of the payment process are not limited to being stored locally in the sales data processing device 10. For example, the sales data processing unit 102 may cause the printing unit 18 to output the details of the payment process. Furthermore, when an expired payment process is forcibly executed, the sales data processing unit 102 may cause the display unit 15 to display the details of the payment process and a screen informing the user that an expired payment process has been performed.

[0059] The sales data processing unit 102 may transmit logs to the management server 20, thereby allowing the management server 20 to perform centralized management. In this case, the management server 20 may be configured to automatically request the payment server 30 or the like to deduct the amount paid in the payment process from the charge balance, based on the logs transmitted from each sales data processing device 10.

[0060] FIG. 6 is a sequence diagram showing an example of data exchange relating to code payment performed between the sales data processing device 10 and the payment server 30. As shown in FIG.

[0061] When code payment is performed in the sales data processing device 10, the reading unit 17 reads the consumer ID from the code symbol for code payment. When the consumer ID is input (step S11), the sales data processing unit 102 sends a usage request including the consumer ID and the usage amount to be paid by code payment to the payment server 30 (step S12). Here, the usage amount is, for example, the total amount of the products registered in the registration process.

[0062] When the code payment processing unit 301 of the payment server 30 receives a usage request from the sales data processing device 10, it refers to the consumer management table 341 and identifies a data entry related to the consumer ID specified in the usage request (step S13). Next, the code payment processing unit 301 compares the expiration date included in the identified data entry with the current date and determines whether the expiration date is still valid (step S14).

[0063] If the code payment processing unit 301 determines that the expiration date has passed, it sends response information indicating the expiration date to the sales data processing device 10 (step S15). In this case, the sales data processing unit 102 of the sales data processing device 10 confirms that the consumer's account has passed the expiration date based on the response information from the payment server 30.

[0064] On the other hand, if the code payment processing unit 301 determines that the expiration date is within the expiration date, it compares the usage amount specified in the usage request with the charge balance included in the identified data entry and determines whether the charge balance is sufficient for the usage amount (step S16).

[0065] If the code payment processing unit 301 determines that the charge balance is less than the usage amount, that is, the balance is insufficient, it transmits response information indicating the balance is insufficient to the sales data processing device 10 (step S17). In this case, the sales data processing unit 102 of the sales data processing device 10 confirms, based on the response information from the payment server 30, that the consumer's account is within its expiration date and that the balance is insufficient.

[0066] Furthermore, when the code payment processing unit 301 determines that the charge balance is sufficient, that is, the charge balance is equal to or greater than the usage amount, it executes the code payment by subtracting the usage amount from the charge balance (step S18). Next, the code payment processing unit 301 transmits response information indicating the completion of the code payment to the sales data processing device 10 (step S19). In this case, based on the response information from the payment server 30, the sales data processing unit 102 of the sales data processing device 10 confirms that the consumer's account is within its expiration date, that the charge balance is sufficient for the usage amount, and that the code payment has been completed.

[0067] Next, an example of the processing performed by the sales data processing device 10 will be described. First, an example of the sales data processing performed by the sales data processing device 10 will be described with reference to Fig. 7. Fig. 7 is a flowchart showing an example of the sales data processing performed by the sales data processing device 10.

[0068] When a transaction is started, the sales data processing unit 102 determines whether a product code has been input (step S21). If a product code has not been input (step S21; No), the sales data processing unit 102 proceeds to step S23. If a product code has been input (step S21; Yes), the sales data processing unit 102 reads product information corresponding to the input product code from the product master and executes a registration process to store the information in the RAM 13 or the like (step S22).

[0069] Next, the sales data processing unit 102 determines whether or not a closing operation has been received via the operation unit (step S23). If the closing operation has not been received (step S23; No), the sales data processing unit 102 proceeds to step S21 and waits for the input of a product code. If the closing operation has been received (step S23; Yes), the sales data processing unit 102 displays a payment method selection screen on the display unit 15 (step S24) and waits until a payment method is selected.

[0070] If code payment is selected (step S25; Yes), the sales data processing unit 102 executes code payment processing (step S26), which will be described later, and proceeds to step S28. If a payment method other than code payment is selected (step S25; No), the sales data processing unit 102 executes payment processing to settle the amount of the product using the selected payment method (step S27), and proceeds to step S28.

[0071] Then, the sales data processing unit 102 causes the printing unit 18 to issue a detailed receipt showing the details of the transaction (step S28), and ends this process.

[0072] Next, the code payment processing performed by the sales data processing device 10 will be described with reference to Fig. 8. Fig. 8 is a flowchart showing an example of the code payment processing performed by the sales data processing device 10. Note that this processing is an example of the code payment processing of step S26 described in Fig. 7.

[0073] When the code payment process is started, the sales data processing unit 102 waits until the consumer ID is input (step S31; No). When the consumer ID is input by reading the code symbol for code payment (step S31; Yes), the sales data processing unit 102 sends a usage request including this consumer ID and the total amount of the products registered in the registration process to the payment server 30 (step S32). Here, the total amount of the products included in the usage request corresponds to the usage amount used for code payment.

[0074] When the payment server 30 sends response information to the usage request, the sales data processing unit 102 receives the response information (step S33). Next, the sales data processing unit 102 checks the expiration date for the consumer to use code payment based on the received response information (step S34). If the sales data processing unit 102 confirms that the expiration date is not yet reached (step S34; No), it sets a flag indicating that the expiration date is still reached (step S35) and proceeds to step S36.

[0075] In step S36, the sales data processing unit 102 determines whether the consumer's charge balance is insufficient to cover the usage amount based on the response information (step S36). If it is determined in step S36 that the balance is not insufficient, that is, if it is confirmed that code payment has been made by the payment server 30, the sales data processing unit 102 proceeds to step S45.

[0076] Furthermore, if it is determined that the balance is insufficient (step S36; Yes), the sales data processing unit 102 displays a confirmation screen on the display unit 15 to confirm whether or not to continue the code payment (step S37), and waits for an operator's operation.

[0077] Here, if an instruction is given to cancel the code payment (step S38; No), the sales data processing unit 102 proceeds to step S24 in Figure 7 and displays a payment method selection screen, allowing the operator to select a payment method to replace the code payment.

[0078] On the other hand, if an instruction to continue code payment is given (step S38; Yes), the sales data processing unit 102 displays a payment method selection screen on the display unit 15 to perform combined payment (step S39), and prompts the operator to select a payment method other than code payment. When the sales data processing unit 102 accepts the selection of another payment method, it determines whether the shortfall can be satisfied with the selected other payment method (step S41). If the shortfall cannot be satisfied (step S41; No), the sales data processing unit 102 returns the process to step S40 and waits until a payment method that can satisfy the shortfall is selected.

[0079] If the shortage can be met (step S41; Yes), the sales data processing unit 102 returns the process to step S32 and transmits a usage request to the settlement server 30 with the usage amount set to the prepaid balance.

[0080] In response to the transmission of the usage request, response information is returned from the settlement server 30, so the sales data processing unit 102 receives the response information (step S33) and executes the process of step S34 again. Here, when the sales data processing unit 102 confirms that the expiration date has expired (step S34; No), it determines whether the flag has been set (step S42).

[0081] If the flag is not set (step S42; No), the sales data processing unit 102 proceeds to step S24 in Fig. 7 and displays a payment method selection screen to allow the operator to select a payment method alternative to code payment. In this case, the sales data processing unit 102 may display on the display unit 15 a screen informing the operator that code payment is not available because the expiration date has expired.

[0082] If the flag has been set (step S42; Yes), the sales data processing unit 102 forcibly executes the settlement process (step S43). Next, the sales data processing unit 102 outputs a log (deemed settlement log) that records the details of the settlement process (step S44), and proceeds to step S45.

[0083] In the next step S45, the sales data processing unit 102 determines whether or not the combined payment method is being executed (step S45). If the combined payment method is not being executed (step S45; No), that is, if no other payment method was selected in step S40, the sales data processing unit 102 proceeds to step S28 in FIG.

[0084] On the other hand, if a combined payment method is being used (step S45; Yes), that is, if another payment method is selected in step S40, the sales data processing unit 102 proceeds to step S27 in Figure 7 and performs payment processing for the remaining amount using the selected other payment method.

[0085] As described above, when performing code payment, the sales data processing device 10 of this embodiment sends a usage request including the consumer's consumer ID and the usage amount to the payment server 30, and checks the expiration date during which the consumer can use code payment based on the response information returned from the payment server 30. If the sales data processing device 10 confirms that the expiration date is not yet reached, it executes the payment process for the transaction using code payment. Furthermore, if the sales data processing device 10 confirms that the expiration date is still not reached for the same transaction, and then confirms that the expiration date has expired upon resending the usage request, it considers code payment to have been performed and forcibly executes the payment process for the transaction.

[0086] As a result, even if the validity period of code payment expires during a transaction due to an operation when the balance is insufficient, the sales data processing device 10 can make the payment possible without canceling the transaction or forcing the user to select another payment method, etc. Therefore, the sales data processing device 10 can improve the convenience of electronic payments.

[0087] The above-described embodiment can be modified as needed by partially changing the configuration or functions of each of the above-described devices. Therefore, several modifications of the above-described embodiment will be described below as other embodiments. The following mainly focuses on differences from the above-described embodiment, and detailed descriptions of commonalities with the content already described will be omitted. The modifications described below may be implemented individually or in appropriate combination.

[0088] (Variation 1) In the above embodiment, the explanation is given using code payment as an example, but the present invention is not limited to this and may be applied to other prepaid payments or non-prepaid electronic payments. Specifically, the present invention may be applied to electronic payments that have an expiration date set, such as credit cards.

[0089] (Variation 2) In the above embodiment, when the charge balance is insufficient, the user is prompted to select another payment method to pay for the product. However, the response to the insufficient balance is not limited to this.

[0090] For example, when the charge balance is insufficient, the sales data processing device 10 may perform a charge process to add an amount equal to or greater than the shortfall to the charge balance. Specifically, the sales data processing device 10 performs a charge process to add the deposited amount to the charge balance of the consumer ID by sending a charge request including the amount deposited by the consumer and the consumer ID to the payment server 30.

[0091] Furthermore, if the payment server 30 determines the expiration date when charging the charge balance, there is a possibility that the expiration date may expire during the transaction, as in the above-described embodiment. In this case, the sales data processing device 10 may assume that the charge process has been performed in the payment server 30, as in the above-described embodiment, and forcibly execute the payment process. In this case, the sales data processing device 10 records the charged amount and the amount used for code payment in a log.

[0092] As a result, similar to the above-described embodiment, even if the validity period of code payment expires during a transaction due to an operation when the balance is insufficient, the sales data processing device 10 can make the payment possible without canceling the transaction or forcing the user to select another payment method, etc. Therefore, the sales data processing device 10 can improve the convenience of electronic payments.

[0093] (Variation 3) In the above embodiment, the sales data processing device 10 executes the registration process and the payment process, but this is not limiting and the sales data processing device 10 may be configured to exclusively perform the payment process. In this case, the sales data processing device 10 may be a registration device exclusively performing the registration process or a payment device exclusively performing the payment process.

[0094] The method for transmitting product information registered by the registration device to the payment device is not particularly limited. For example, product information registered by the registration device may be transmitted to the payment device via the management server 20. In this case, the registration device associates the product information registered in the registration process with a transaction ID that can identify the transaction and registers it in the management server 20. Meanwhile, when the transaction ID of the transaction to be settled is input, the payment device obtains product information associated with the transaction ID from the management server 20 and executes the payment process based on the obtained information.

[0095] As a result, even if the registration device and the settlement device are configured to cooperate with each other to function as a sales data processing device, the same effects as those of the above-described embodiment can be achieved.

[0096] Although the embodiments of the present invention have been described above, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, combinations, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, and are also included in the inventions and their equivalents as set forth in the claims.

[0097] Furthermore, the programs executed by each device in the above embodiments are provided by being pre-installed in a storage medium (ROM or storage unit) included in the device, but this is not intended to be limiting. For example, the programs may be provided by being recorded in an installable or executable file format on a computer-readable storage medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a DVD (Digital Versatile Disk). Furthermore, the storage medium is not limited to a medium independent of the computer or embedded system, but also includes a storage medium that stores or temporarily stores a program downloaded via a LAN, the Internet, or the like.

[0098] In addition, the programs executed by each device in the above embodiments may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network, or may be configured to be provided or distributed via a network such as the Internet. [Explanation of symbols]

[0099] 1. Payment system 10 Sales data processing device 20 Management Server 30 Payment Server 101 Reading control unit 102 Sales data processing section 301 Code payment processing unit [Prior art documents] [Patent documents]

[0100] [Patent Document 1] Japanese Patent Application Publication No. 2020-204884

Claims

1. a transmitting means for transmitting a usage request including identification information of a consumer using an electronic payment service and a usage amount of the electronic payment service to a payment server that provides the electronic payment service; a confirmation means for confirming an expiration date for which the electronic payment service is available based on a response from the payment server to the usage request; a payment means for executing a payment process for a transaction using the electronic payment service when the confirmation means confirms that the card is within the expiration date; Equipped with A sales data processing device in which the payment means forcibly executes the payment process for the transaction if, for the same transaction, the confirmation means confirms that the expiration date is within the expiration date and then confirms that the expiration date has expired upon re-transmission of the usage request.

2. The electronic payment service is a prepaid payment service that performs payment within the range of a prepaid balance, The payment server further includes a determination unit that determines whether the consumer's balance is equal to or greater than the usage amount based on a response from the payment server to the usage request. When it is determined that the balance of the consumer is less than the usage amount, the transmission means transmits a usage request with the balance of the consumer as the usage amount to the payment server. The sales data processing device according to claim 1 .

3. When the balance of the consumer is less than the usage amount, the payment means displays a screen for confirming whether or not to continue using the electronic payment service; When an instruction to continue using the electronic payment service is given, the transmission means transmits a usage request to the payment server, the usage request including the consumer's balance as the usage amount. The sales data processing device according to claim 2 .

4. 2. The sales data processing device according to claim 1, further comprising output means for outputting data recording details relating to the settlement process when the settlement process is forcibly executed.

5. 2. The sales data processing device according to claim 1, further comprising: a display unit that, when the settlement process is forcibly executed, displays a screen informing the user that the settlement process has been forcibly executed.

6. The computer of the sales data processing device, a transmitting means for transmitting a usage request including identification information of a consumer using an electronic payment service and a usage amount of the electronic payment service to a payment server that provides the electronic payment service; a confirmation means for confirming an expiration date for which the electronic payment service is available based on a response from the payment server to the usage request; a payment means for executing a payment process for a transaction using the electronic payment service when the confirmation means confirms that the card is within the expiration date; and make it work, The payment means forcibly executes the payment process for the transaction if the verification means confirms that the validity period is within the validity period for the same transaction, and then confirms that the validity period has expired upon re-transmission of the usage request.

Images