JP6081861B2 - Payment support system, payment support method, and payment support program - Google Patents

Description

  The present invention relates to a payment support system, a payment support method, and a payment support program for supporting payment.

  When paying for merchandise transactions in mail order sales, etc., payment may be made at convenience stores. In this case, the payment slip provided by the sales company is read by the POS terminal of the convenience store. A settlement system for improving the efficiency of payment of this price has been studied (for example, see Patent Document 1). In the technique described in this document, a portable information terminal is connected to an authentication server via the Internet. The portable information terminal requests the return of the barcode information, receives the barcode information, and displays the barcode pattern on the display. The POS register reads this barcode pattern via a barcode reader and supplies the obtained barcode information to the payment controller. The payment controller obtains payment information by connecting to a payment server via a dedicated line. The POS register calculates the amount billed according to the payment information acquired via the payment controller. When the amount received from the user is input, the POS register issues a receipt on which payment information is printed.

Japanese Patent Laid-Open No. 2001-5883 (first page, FIG. 1)

  In the technique described in Patent Document 1, the POS register acquires payment information from the payment server in accordance with the barcode pattern acquired from the mobile phone terminal, and calculates a bill amount according to the payment information. However, when a plurality of payments are made at a storefront, an operation for individually displaying a plurality of barcode patterns is required. This operation is complicated, and there is a possibility that payment may be lost or double payment may be caused by an erroneous operation.

  An object of the present invention is to provide a payment support system, a payment support method, and a payment support program for efficiently paying a price using a code image.

A payment support system that solves the above problems includes a control unit connected to a management server including a billing information storage unit that stores billing data for payment at a store terminal, and a payment information storage unit that stores the billing data. , Ru using the mobile terminal having a display unit and a sound collector Metropolitan displaying the code image. Then, the control unit of the portable terminal, the billing data acquired from the management server to record in the payment information storage section, and outputs the claims list the billing data recorded in the payment information storage section on the display unit, When the sound collecting unit collects the reading sound of the code image at the store terminal , and when a plurality of billing data is selected in the billing list, when it is determined that the detection of the reading sound is not difficult, A code image corresponding to the billing data, the code image readable by the code reader of the store terminal is acquired from the management server, and the code image is sequentially displayed on the display unit based on the sound collection. and outputs, when said detection of the read sound is determined that the difficulty is to display a message prompting the billing integration process, in the preceding list, collectively performs payment請Is specified, the integration request including the specified request is transmitted to the management server, and the management server newly adds the integrated request based on the claim data included in the integration request. A code image corresponding to the code, the code image readable by the code reader of the store terminal is acquired from the management server, the code image is output to the display unit, and according to the sound collection, The payment information storage unit includes means for recording information indicating payment with respect to the billing data of the code image displayed before the sound collection . According to this configuration, code images corresponding to a plurality of selected billing data are sequentially output to the display unit, so that payment for a plurality of bills can be performed efficiently.

Further, according to this configuration, the code image corresponding to the selected billing data is sequentially output to the display unit based on the reading sound of the code image, so that payment for a plurality of bills can be made efficiently and accurately. Can be performed.

Furthermore, according to this configuration, since information indicating payment is recorded according to the sound collection, double payment based on the same billing data can be suppressed.

In the payment support system, the control unit of the mobile terminal specifies billing data in which information indicating payment is not recorded in the payment information storage unit, specifies a payment due date of the billing data, and sets the payment due date It is preferable to output an alert based on this. According to this configuration, forgetting to pay within the due date can be alerted.

In the payment support system, when the control unit of the portable terminal acquires a payment confirmation for the bill from the management server, the payment information storage unit may record paid information for the bill. preferable. According to this configuration, the storage status in the management server can be grasped.

  In the payment support system, the control unit of the mobile terminal transmits an integration request for integrating a plurality of billing data selected in the billing list to the management server, and the management server responds to the integration request, Generating new billing data including information related to the billing data to be integrated, and transmitting a code image of the new billing data to the mobile terminal, and the control unit of the mobile terminal displays the code image on the display unit Is preferably output. According to this configuration, it is possible to efficiently pay for a plurality of bills with one code image.

  In the payment support system, when the portable terminal stores a failure area designated on the display unit and outputs the code image to the display unit, the failure area is specified and a display other than the failure area is displayed. It is preferable to display the code image on the part. According to this configuration, since the code image is displayed avoiding the failure area, the code image can be accurately read by the code reader of the store terminal.

  According to the present invention, it is possible to efficiently pay the price using the code image.

The schematic block diagram explaining the structure of the payment assistance system in embodiment. It is a block diagram explaining the data structure of each memory | storage part of embodiment, (a) is a customer information memory | storage part, (b) is a claimant information memory | storage part, (c) is a billing information memory | storage part, (d) is payment Information storage unit. The flowchart explaining the process sequence of the process at the time of charge in embodiment. The flowchart explaining the process sequence of the process at the time of payment in embodiment. The flowchart explaining the process sequence of the storage management process in embodiment. The flowchart explaining the process sequence of the payment time limit management process in embodiment. The flowchart explaining the process sequence of the bill integration process in the example of a change. It is a flowchart explaining the process sequence of the process when the failure has arisen in the touch panel display in the example of a change, (a) is a failure response process, (b) is a barcode display process.

Hereinafter, an embodiment embodying the present invention will be described with reference to FIGS.
As shown in FIG. 1, the payment support system of the present embodiment uses a merchant server 10, a management server 20, and a portable terminal 30 connected to a network such as the Internet. At the time of payment, a POS terminal 40 installed at a convenience store or the like is used. The POS terminal 40 is connected to the POS server 50 via a network. The POS server 50 communicates with the management server 20 via a network.

First, the outline of this service will be described.
The merchant server 10 transmits billing data for the user to the management server 20 based on the transaction with the user. The management server 20 transmits a billing mail including payment slip data to the user.

  The user displays a barcode corresponding to the payment slip data of the billing mail on the display of the portable terminal 30. Then, the bar code is read by the code reader of the POS terminal 40. In this case, the POS terminal 40 transmits the storage data to the POS server 50. Then, the POS server 50 transmits the storage data to the management server 20. With this stored data, the management server 20 performs remittance to the seller.

Next, each hardware configuration will be described.
The merchant server 10 is a server computer of a merchant that conducts a transaction (for example, a mail order transaction) with a user. The seller server 10 generates billing data based on the transaction with the user and transmits the billing data to the management server 20.

  The management server 20 is a server computer for supporting the seller's price collection. The management server 20 includes a billing processing unit 21, a customer information storage unit 22, a biller information storage unit 23, and a billing information storage unit 24.

  The billing processing unit 21 acquires billing data from the seller server 10 and executes a process for billing the user based on the billing data. Further, the billing processing unit 21 executes processing for providing the payment support application program to the portable terminal 30.

  As shown in FIG. 2A, the customer information storage unit 22 stores a customer management record 220 for managing customers who are users. This customer management record 220 is recorded when a customer is registered. The customer management record 220 includes data related to a customer code, name, and address.

Data relating to an identifier for identifying a customer is recorded in the customer code data area.
Data related to the customer's name is recorded in the name code data area.
In the address code data area, data related to the customer's e-mail address is recorded.

  As shown in FIG. 2B, the biller information storage unit 23 stores a biller management record 230 for managing biller information for dealing with customers. This claimant management record 230 is recorded when a claimant is registered. The biller management record 230 includes data relating to a biller and a remittance destination.

In the claimant data area, data relating to an identifier for identifying the seller who made the claim is recorded. In this embodiment, a seller's name, identification code, etc. are used as claimant data.
In the remittance destination data area, data relating to the remittance destination (for example, an account of a financial institution) of the deposit for this seller is recorded.

  As shown in FIG. 2C, the billing information storage unit 24 records a billing management record 240 for managing billing to customers. This billing management record 240 is recorded when billing data is acquired from the seller server 10. The billing management record 240 includes billing code, billing person, billing contents, customer code, billing date, payment deadline, amount of money, and storage status data.

In the billing code data area, data relating to an identifier for identifying each bill to the customer is recorded.
In the claimant data area, data relating to an identifier for identifying the seller who made the claim is recorded.

In the billing content data area, data related to the transaction content with the user is recorded. For example, data relating to the transaction code and sales product content at the seller is recorded.
In the customer code data area, data relating to an identifier for identifying a customer who has made a transaction with the seller is recorded.

In the billing date data area, data relating to the date of billing is recorded.
In the payment deadline data area, data relating to the payment deadline for the billing is recorded.
Data related to the billing amount is recorded in the amount data area.
In the storage status data area, a flag for specifying the payment status for the charge is recorded. In this data area, an unpaid flag and a stored flag are recorded.

  A portable terminal 30 shown in FIG. 1 is a computer terminal used by a customer. As this portable terminal 30, a smart phone terminal or a tablet terminal provided with a touch panel display 35 can be used. The portable terminal 30 includes a control unit 31, a mail storage unit 32, and a payment information storage unit 33. The portable terminal 30 further includes a microphone (sound collecting unit) that collects ambient sounds.

  The control unit 31 functions as a mail processing unit 311 by executing a mailer program. The control unit 31 functions as a billing management unit 312 and a payment processing unit 313 by executing a payment support program.

The mail processing unit 311 executes mail transmission / reception processing via the Internet.
The billing management unit 312 executes processing for managing the payment slip acquired by the billing mail. The billing management unit 312 stores data relating to a predetermined number of days used to identify a bill that is close to the due date.

  The payment processing unit 313 executes processing for generating a barcode used for payment based on the payment slip. The payment processing unit 313 holds data related to the frequency pattern of the reading sound (beeper sound) generated when the bar code is read by the code reader of the POS terminal 40.

In the mail storage unit 32, the mail received by the mail processing unit 311 is recorded.
As shown in FIG. 2D, a payment management record 330 generated based on the billing mail is recorded in the payment information storage unit 33. This payment management record 330 is registered when a billing mail is received. The payment management record 330 includes data relating to a billing code, a billing party, billing details, a payment deadline, an amount, and a payment status.

In the billing code data area, data relating to an identifier for identifying each bill to the customer is recorded.
In the claimant data area, data relating to an identifier for identifying the seller who made the claim is recorded.

In the billing content data area, data related to the transaction content with the user is recorded. For example, data relating to the transaction code and sales product content at the seller is recorded.
In the payment deadline data area, data relating to the payment deadline for the billing is recorded.
Data related to the billing amount is recorded in the amount data area.
In the payment status data area, a flag for specifying the payment status for billing is recorded. In this data area, an unpaid flag, a checking flag, and a paid flag are recorded.

  A POS terminal 40 shown in FIG. 1 is a computer terminal that manages customer payments at a cash register such as a convenience store. The POS terminal 40 is connected to a code reader for reading bar codes printed on products and payment slips. When the barcode is read by the code reader, the POS terminal 40 acquires a product code and a product price. Further, the POS terminal 40 is provided with a speaker, and emits a reading sound (a beep sound) having a predetermined frequency pattern when a bar code is read by a code reader.

  The POS server 50 is a computer system that manages sales at convenience store stores. The POS server 50 acquires information regarding the barcode read by the POS terminal 40. Further, when the barcode information of the payment slip is acquired, the storage data is transmitted to the management server 20. This stored data includes data related to the billing code.

Next, a processing procedure related to billing will be described with reference to FIGS. Here, the billing process, the payment process, the storage management process, and the payment deadline management process will be described in this order.
(Process when billing)
First, the billing process will be described with reference to FIG.
Here, the billing processing unit 21 of the management server 20 executes billing data acquisition processing (step S1-1). Specifically, when the seller charges the customer, the seller server 10 inputs billing data. Then, the merchant server 10 transmits billing data to the management server 20. This billing data includes data relating to the biller, billing details, customer code, billing date, payment deadline, and billing amount. Upon receiving the billing data, the billing processing unit 21 of the management server 20 assigns an unused billing code and generates a billing management record 240 including this billing code. In this case, the billing processing unit 21 includes the received billing data in the billing management record 240. The billing processing unit 21 registers the billing management record 240 in the billing information storage unit 24.

  Next, the billing processing unit 21 of the management server 20 executes an address specifying process (step S1-2). Specifically, the billing processing unit 21 specifies the customer management record 220 in which the customer code recorded in the billing management record 240 is recorded in the customer information storage unit 22. Then, the bill processing unit 21 acquires the address recorded in the customer management record 220.

  Next, the billing processing unit 21 of the management server 20 executes billing mail transmission processing (step S1-3). Specifically, the billing processing unit 21 generates a billing mail based on information recorded in the billing management record 240. This billing mail includes data related to payment slip data (billing code, billing party, billing details, payment deadline, amount). Then, the billing processing unit 21 transmits this billing mail to the address acquired in step S1-2.

  Next, the control part 31 of the portable terminal 30 performs the reception process of a claim mail (step S2-1). Specifically, the mail processing unit 311 of the control unit 31 receives a billing mail from the management server 20.

  Next, the control part 31 of the portable terminal 30 performs the determination process about whether it is first time starting (step S2-2). Specifically, a script included in the billing mail is executed. In this case, the control unit 31 confirms whether or not the payment support application program is installed in the mobile terminal 30. If it is not installed, it is determined to be the first activation.

  When it determines with starting for the first time (in the case of "YES" in step S2-2), the control part 31 of the portable terminal 30 performs an application download process (step S2-3). Specifically, the control unit 31 accesses the management server 20 and requests a payment support application program. Then, the control unit 31 downloads the payment support application program from the management server 20.

  When it determines with it not being the first time starting (in the case of "NO" in step S2-2), the control part 31 of the portable terminal 30 skips an application download process (step S2-3).

  Next, the control part 31 of the portable terminal 30 performs an application starting process (step S2-4). Specifically, the control unit 31 activates the installed payment support application program. Thereby, the billing management unit 312 and the payment processing unit 313 function.

  Next, the control part 31 of the portable terminal 30 performs the payment slip taking-in process (step S2-5). Specifically, the billing management unit 312 of the control unit 31 specifies a billing mail recorded in the mail storage unit 32. Furthermore, the billing management unit 312 identifies a mail that is not registered in the payment information storage unit 33 in the billing mail. Then, the billing management unit 312 generates a payment management record 330 based on the specified billing mail and records it in the payment information storage unit 33. This payment management record 330 includes payment slip data included in the billing mail. Then, an unpaid flag is recorded in the payment status data area of the payment management record 330.

  Next, the control unit 31 of the portable terminal 30 executes a billing list display process (step S2-6). Specifically, the charge management unit 312 of the control unit 31 includes an unpaid request including a charge in which an unpaid flag is recorded as a payment status in the payment management record 330 recorded in the payment information storage unit 33. A list screen is generated and output to the touch panel display 35. This unpaid request list screen is provided with a check box for selecting a request for payment.

(Payment processing)
Next, the payment process will be described with reference to FIG.
First, the control part 31 of the portable terminal 30 performs the specific process of payment object (step S3-1). Specifically, when the user pays for billing, the user selects a check box for billing to be paid in the unpaid billing list screen displayed on the touch panel display 35. In this case, the payment processing unit 313 of the control unit 31 temporarily stores the payment management record 330 for the specified bill in the memory.

  Next, the control part 31 of the portable terminal 30 performs the amount calculation process (step S3-2). Specifically, the payment processing unit 313 of the control unit 31 calculates the payment amount by summing the amounts recorded in the payment management record 330 temporarily stored in the memory. Then, the payment processing unit 313 outputs the calculated payment amount to the touch panel display 35.

  Next, the control unit 31 of the mobile terminal 30 executes barcode acquisition processing (step S3-3). Specifically, the payment processing unit 313 of the control unit 31 transmits a barcode request to the management server 20. The barcode request includes data related to the billing code of the payment management record 330 temporarily stored in the memory. The management server 20 that has received the barcode request extracts the billing management record 240 in which the billing code included in the barcode request is recorded from the billing information storage unit 24. And the management server 20 produces | generates the barcode containing the information regarding a billing code, a billing person, a billing content, and an amount. Here, when a plurality of billing codes are included in the barcode request, all the payment management records 330 corresponding to each billing code are extracted, and a barcode is generated for each payment management record 330. Then, the management server 20 transmits a barcode file including the generated barcode to the mobile terminal 30. In this case, the payment processing unit 313 of the mobile terminal 30 acquires the barcode file. When there are a plurality of billing codes included in the barcode request, the barcode file includes a plurality of barcodes corresponding to each billing code.

  Next, the control unit 31 of the mobile terminal 30 executes barcode display processing (step S3-4). Specifically, the payment processing unit 313 of the control unit 31 displays the generated barcode on the touch panel display 35. When a plurality of barcodes are generated, the first barcode is output.

  In this case, the clerk at the convenience store reads the barcode output on the touch panel display 35 of the portable terminal 30 using the code reader connected to the POS terminal 40.

  Then, the POS terminal 40 executes a barcode reading process (step S4-1). Specifically, the POS terminal 40 decodes the barcode read by the barcode reader, and acquires data relating to the billing code, billing party, billing content, and amount.

  Next, the POS terminal 40 executes a reading sound output process (step S4-2). Specifically, the POS terminal 40 emits a reading sound of a specific frequency pattern through a speaker when reading of the barcode is completed.

  Next, the control part 31 of the portable terminal 30 performs the determination process about whether it is the sound collection of a read sound (step S3-5). Specifically, the payment processing unit 313 of the control unit 31 waits for the reading sound of the POS terminal 40 using a microphone. And the payment process part 313 determines whether it is a reading sound based on the frequency pattern of the sound collected through the microphone.

When the reading sound is not detected (“NO” in step S3-5), the reading sound collection is awaited.
When it is determined that the reading sound is detected (in the case of “YES” in Step S3-5), the control unit 31 of the mobile terminal 30 executes a payment recording process (Step S3-6). Specifically, the payment processing unit 313 of the control unit 31 records the in-confirmation flag in the payment status data area of the payment management record 330 in which the barcode is displayed on the touch panel display 35.

  Next, the control part 31 of the portable terminal 30 performs the determination process about whether there exists the next charge (step S3-7). Specifically, the payment processing unit 313 of the control unit 31 determines whether or not there is a charge for which a barcode has not yet been displayed in the payment management record 330 temporarily stored in the memory. If there is still a charge for which the bar code is not displayed, it is determined that there is a next charge.

  If it is determined that there is a next charge (in the case of “YES” in step S3-7), the control unit 31 of the mobile terminal 30 repeats the processes in and after step S3-4. Here, one of the remaining bar codes of the bill to be paid is displayed on the touch panel display 35.

  On the other hand, when it determines with there being no next charge (in the case of "NO" in step S3-7), the control part 31 of the portable terminal 30 performs an end message process (step S3-8). Specifically, the payment processing unit 313 of the control unit 31 outputs a message on the touch panel display 35 indicating that the display of the barcode of the payment slip has been completed.

In addition, the POS terminal 40 executes a determination process as to whether or not to end (step S4-3). Specifically, the store clerk who sees the end message on the touch panel display 35 of the portable terminal 30 performs reading completion input at the POS terminal 40. The POS terminal 40 determines the end based on the presence / absence of this read completion input.
If it is determined that the process is not finished (in the case of “NO” in step S4-3), the POS terminal 40 returns to the barcode reading process (step S4-1) and stands by.

  On the other hand, when it is determined that the process is finished (in the case of “YES” in step S4-3), the POS terminal 40 executes a deposit process (step S4-4). Specifically, the POS terminal 40 specifies the amount of each payment based on the read barcode, and calculates the total amount. Then, the POS terminal 40 outputs the total amount. Based on this total amount, the user pays the clerk of the convenience store. In this case, the store clerk uses the POS terminal 40 to input payment completion.

  When the payment completion input is performed, the POS terminal 40 transmits the storage data to the POS server 50. The stored data includes data relating to the billing code read from the barcode, the billing party, the billing content, and the amount of money.

(Storage management processing)
Next, storage management processing will be described with reference to FIG. The POS server 50 that has acquired the storage data from the POS terminal 40 transmits the storage data to the management server 20.

  First, the billing processing unit 21 of the management server 20 executes a stored money settlement process (step S5-1). Specifically, the billing processing unit 21 extracts from the billing information storage unit 24 the billing management record 240 in which the billing code and the billing party included in the storage data acquired from the POS server 50 are recorded. Then, the claim processing unit 21 extracts the remittance destination of the claimant from the claimant information storage unit 23, and performs remittance processing for the remittance destination.

  Next, the billing processing unit 21 of the management server 20 executes a storage process for paid information (step S5-2). Specifically, the billing processing unit 21 records a stored flag in the storage status data area of the billing management record 240.

  Then, the control part 31 of the portable terminal 30 performs a confirmation process (step S6-1). Specifically, the payment support application program of the portable terminal 30 is activated to output a payment confirmation screen. In this case, the billing management unit 312 of the control unit 31 accesses the management server 20. Then, the billing management unit 312 acquires the storage status information recorded in the billing information storage unit 24 for the payment management record 330 recorded in the payment information storage unit 33.

  Next, the control part 31 of the portable terminal 30 performs the update process of a payment condition (step S6-2). Specifically, the billing management unit 312 of the control unit 31 updates the payment status of the payment management record 330 for the bill whose storage status has been updated. For example, when the stored flag is recorded in the storage status data area of the billing management record 240, the billing management unit 312 pays the paid flag in the payment status data area of the payment management record 330 recorded in the payment information storage unit 33. Record.

  Here, when confirming the paid bill, the bill is selected on the payment confirmation screen. In this case, the control unit 31 of the mobile terminal 30 executes a payment confirmation display process (step S6-3). Specifically, the billing management unit 312 of the control unit 31 acquires the payment status of the payment management record 330 for the confirmation target billing. Here, when the paid flag is recorded, and when the bill with the paid flag is specified in the billing list, the billing management unit 312 displays the payment confirmation for the bill on the touch panel. This is displayed on the display 35.

(Payment deadline management process)
Next, a payment time limit management process will be described with reference to FIG.
First, the control unit 31 of the mobile terminal 30 executes an unpaid search process (step S7-1). Specifically, the billing management unit 312 of the control unit 31 extracts a payment management record 330 in which an unpaid flag is recorded in the payment status data area in the payment information storage unit 33. Next, the billing management unit 312 identifies the payment due date of the extracted payment management record 330.

  Next, the control part 31 of the portable terminal 30 performs the payment deadline specification process (step S7-2). Specifically, the billing management unit 312 of the control unit 31 specifies the payment due date in the payment management record 330.

  Next, the control part 31 of the portable terminal 30 performs the determination process about whether there exists a charge with a near deadline (step S7-3). Specifically, the billing management unit 312 of the control unit 31 compares the payment due date specified in the payment management record 330 with the current date and the payment due date. Then, if the current date is a predetermined number of days before the payment deadline, it is determined that there is a charge that is close to the payment deadline.

  If it is determined that there is a charge that is close to the deadline (in the case of “YES” in step S7-3), the control unit 31 of the mobile terminal 30 executes an alert process (step S7-4). Specifically, the billing management unit 312 of the control unit 31 outputs a message indicating that there is a bill nearing the due date on the initial screen displayed on the touch panel display 35.

According to the payment support system of the present embodiment, the following effects can be obtained.
(1) In the present embodiment, the billing processing unit 21 of the management server 20 executes billing mail transmission processing (step S1-3). The control unit 31 of the portable terminal 30 executes a payment slip fetch process (step S2-5), a bill list display process (step S2-6), and a payment target specifying process (step S3-1). The control unit 31 of the portable terminal 30 repeatedly executes the barcode acquisition process (step S3-3) and the barcode display process (step S3-4) according to the specified payment object. As a result, the code image corresponding to the plurality of selected billing data is sequentially output to the display unit in the mobile terminal 30, so that a plurality of payments can be efficiently made using the code image corresponding to the plurality of billing data. Can be performed.

  (2) In this embodiment, the control part 31 of the portable terminal 30 performs the determination process about whether it is the sound collection of a reading sound (step S3-5). When it is determined that the reading sound is detected (in the case of “YES” in Step S3-5), the control unit 31 of the mobile terminal 30 executes a payment recording process (Step S3-6). This makes it possible to identify billing data for which payment has already been made, so double payment due to re-displaying the barcode of the billing data that has already been paid can be suppressed.

  (3) In this embodiment, the control part 31 of the portable terminal 30 performs the determination process about whether it is the sound collection of a reading sound (step S3-5). If it is determined that the reading sound has been detected ("YES" in step S3-5), it is determined whether there is a next charge. If it is determined that there is a next charge (in the case of “YES” in step S3-7), the control unit 31 of the mobile terminal 30 repeats the processes in and after step S3-4. Thereby, when the barcode is read, the barcode of the next billing data is displayed, so that payment for a plurality of bills can be performed efficiently.

  (4) In this embodiment, the control part 31 of the portable terminal 30 performs a confirmation process (step S6-1), and performs the payment status update process (step S6-2). When the request for confirming the paid request is selected, the control unit 31 of the mobile terminal 30 executes a payment confirmation display process (step S6-3). Thereby, it can grasp | ascertain that it accommodated in the management server.

  (5) In the present embodiment, the control unit 31 of the mobile terminal 30 executes an unpaid search process (step S7-1) and a payment deadline specifying process (step S7-2). If it is determined that there is a charge that is close to the deadline (in the case of “YES” in step S7-3), the control unit 31 of the mobile terminal 30 executes an alert process (step S7-4). Accordingly, it is possible to notify that there is billing data whose payment deadline is imminent and to alert the user that he or she has forgotten to pay within the payment deadline.

Moreover, you may change the said embodiment as follows.
In the above embodiment, the control unit 31 of the mobile terminal 30 executes barcode generation processing (step S3-3) and barcode display processing (step S3-4). When it is determined that the reading sound is detected (in the case of “YES” in Step S3-5), the control unit 31 of the mobile terminal 30 executes a payment recording process (Step S3-6). If it is determined that there is a next charge (in the case of “YES” in step S3-7), the control unit 31 of the mobile terminal 30 repeats the processes in and after step S3-4. Here, the barcode generation process (step S3-3) may be repeated.

  In the above embodiment, when making payments for a plurality of bills, the payment processing unit 313 of the mobile terminal 30 individually generates a barcode. Instead of this, payment may be made collectively. In this case, the integration process is executed in the management server 20 and the portable terminal 30.

(Billing integration process)
Here, the bill integration process will be described with reference to FIG.
First, the control part 31 of the portable terminal 30 performs the specific process of payment object (step S8-1). Specifically, the billing management unit 312 of the control unit 31 specifies billing to be collectively paid on the billing list screen.

  Next, the control part 31 of the portable terminal 30 performs the integration request process of a claim (step S8-2). Specifically, the billing management unit 312 of the control unit 31 transmits an integration request to the management server 20. This integration request includes data related to a plurality of billing codes designated on the billing list screen.

  Next, the billing processing unit 21 of the management server 20 executes billing data generation processing that summarizes billing (step S9-1). Specifically, the billing processing unit 21 acquires an integration request from the mobile terminal 30. The billing processing unit 21 generates a new integrated billing code for the billing code included in the integration request. The billing processing unit 21 generates a billing management record 240 in which the integrated billing code is recorded and records it in the billing information storage unit 24. Then, the billing processing unit 21 extracts a billing management record 240 corresponding to the billing code included in the consolidation request as a consolidation target record. The billing processing unit 21 records a flag indicating that it is an integrated billing related to the integration request in the biller data area of the new billing management record 240, and the billing code included in the integration request is stored in the billing content data area. Record. Further, the billing processing unit 21 records the earliest payment due date among the payment due dates of the integration target records in the payment due date data area of the new billing management record 240. Further, the billing processing unit 21 records the sum total of the sums of the integration target records in the amount data area of the new billing management record 240. Further, an identifier for identifying the customer, a current date, and an unpaid flag are recorded in the customer code data area, the billing date data area, and the storage status data area of the new billing management record 240, respectively.

  Next, the billing processing unit 21 of the management server 20 executes billing mail transmission processing (step S9-2). Specifically, the billing processing unit 21 generates a billing mail including the integrated billing code and transmits the billing mail to the customer's mail address.

  Next, the control unit 31 of the portable terminal 30 executes a billing mail reception process (step S8-3). Specifically, the mail processing unit 311 of the control unit 31 receives a billing mail from the management server 20. This billing mail includes data related to the integrated billing code.

Next, the control part 31 of the portable terminal 30 performs the payment slip taking-in process as in step S2-5 (step S8-4).
Next, the control part 31 of the portable terminal 30 performs the display process of a bill list similarly to step S2-6 (step S8-5).

  And the control part 31 of the portable terminal 30 performs the process at the time of payment similar to FIG. 4 (step S8-6). In this case, the barcode related to the integrated billing code is acquired in the same manner as the barcode acquisition process (step S3-3). Then, the payment processing unit 313 of the mobile terminal 30 displays a barcode related to the integrated billing code on the touch panel display 35. Then, the barcode is read at the POS terminal 40 installed in the convenience store.

  The POS terminal 40 that has read the integrated billing code transmits storage data to the POS server 50 in the same manner as other storage processing. The POS server 50 transmits the storage data acquired from the POS terminal 40 to the management server 20.

  Next, the billing processing unit 21 of the management server 20 determines whether there is an integrated billing. Specifically, the billing processing unit 21 extracts a billing management record 240 in which a billing code is recorded. Here, when the flag which shows that it is an integrated charge is recorded on the claim content data area | region of the claim management record 240, it determines with an integrated charge.

  If it is determined to be integrated billing, the expansion process is performed on each piece of storage information (step S10-1). Specifically, the billing processing unit 21 extracts, from the billing information storage unit 24, the individual billing management record 240 in which the billing code acquired from the billing content data area of the billing management record 240 of the integrated billing is recorded.

  Next, the billing processing unit 21 of the management server 20 executes a stored money settlement process (step S10-2). Specifically, the billing processing unit 21 executes a deposit money settlement process for each billing code.

  Next, the billing processing unit 21 of the management server 20 executes a process for accumulating paid information, similarly to step S5-2 (step S10-3). Thereby, a plurality of payments can be efficiently performed with one code image. In addition, it is also possible to perform processing at the time of payment including an integrated code image and a non-integrated code image.

  Furthermore, when it is difficult to detect the reading sound in the mobile terminal 30, the control unit 31 of the mobile terminal 30 may execute the billing integration process. In this case, the control unit 31 of the portable terminal 30 holds data related to the failure reference volume and the failure frequency band for determining whether or not the billing integration process is necessary. The failure reference volume is a volume at which it is difficult to collect the read sound. The fault frequency band is a frequency band including the frequency of the read sound.

  Then, the control unit 31 counts the number of bills to be paid in the payment process. Here, when there is only one bill selected as a payment target, the payment process shown in FIG. 4 is performed. On the other hand, when a plurality of bills are selected as payment targets, environmental sounds (ambient sounds) are collected using a microphone. Here, when the volume of the environmental sound is larger than the failure reference volume, or when the frequency band of the environmental sound overlaps with the failure frequency band, it is determined that it is difficult to detect the read sound. In this case, a message prompting the billing integration process is displayed on the touch panel display 35. Thereby, the user who is in a noisy environment can pay efficiently and accurately by the bill integration process.

  If it is determined that it is difficult to detect the read sound, the control unit 31 of the mobile terminal 30 may make a request for integration in the barcode acquisition process (step S3-3). In this case, the billing processing unit 21 of the management server 20 generates a billing management record 240 in which billing is integrated and records it in the billing information storage unit 24 as in the billing data generation processing (step S9-1). . Furthermore, the billing processing unit 21 of the management server 20 generates a barcode based on the billing management record 240 for the integrated billing and transmits it to the mobile terminal 30. As a result, even in a noisy environment, payment can be made efficiently and accurately without burden on the user.

  In the above embodiment, the control unit 31 of the mobile terminal 30 performs barcode display processing (step S3-4). Here, the display of the barcode may be changed according to the state of the touch panel display 35 of the mobile terminal 30. For example, the touch panel display 35 of the mobile terminal 30 may have a failure such as a screen stain or crack. If a bar code is displayed in such an obstacle area, the code reader may not be able to read it accurately. Therefore, the failure handling process is executed in the mobile terminal 30. A display processing unit is provided in the portable terminal 30. The display processing unit includes a memory that records position information for identifying a failure area.

The failure handling processing and barcode display processing will be described with reference to FIG.
(Failure handling process)
First, the failure handling process will be described with reference to FIG.
Here, the control unit 31 of the portable terminal 30 executes a failure area designation process (step S11-1). Specifically, the display processing unit of the control unit 31 outputs a message so as to designate a failure area. In this case, the user traces with the finger so as to surround the failure area on the touch panel display 35. In this case, the display processing unit identifies the enclosed area as a failure area.

  Next, the control unit 31 of the portable terminal 30 executes a failure area recording process (step S11-2). Specifically, the display processing unit of the control unit 31 records the position information of the specified failure area in the memory.

(Barcode display processing)
Next, a barcode display process when displaying a barcode will be described with reference to FIG.

  Here, the control unit 31 of the portable terminal 30 executes a failure area reading process (step S12-1). Specifically, the display processing unit of the control unit 31 checks whether or not a failure area is recorded in the memory. When the failure area is recorded, the position information of the failure area is read from the memory.

  Next, the control part 31 of the portable terminal 30 performs a display process other than a failure area (step S12-2). Specifically, the display processing unit of the control unit 31 specifies a healthy region other than the failure region. And a display process part displays a barcode using this healthy area | region. In this case, a barcode is output according to the direction of the display of the portable terminal 30. As a result, the bar code can be accurately read in the POS terminal 40 by displaying the bar code while avoiding the obstacle area.

  DESCRIPTION OF SYMBOLS 10 ... Seller server, 20 ... Management server, 21 ... Claim processing part, 22 ... Customer information storage part, 23 ... Claimer information storage part, 24 ... Claim information storage part, 30 ... Portable terminal, 31 ... Control part, 32 ... mail storage unit, 33 ... payment information storage unit, 35 ... touch panel display, 40 ... POS terminal, 50 ... POS server, 311 ... mail processing unit, 312 ... billing management unit, 313 ... payment processing unit.

Claims (6)

In the store terminal, a control unit connected to a management server having a billing information storage unit for storing billing data for payment;
A payment information storage unit for storing the billing data;
A payment support system using a mobile terminal including a display unit for displaying a code image and a sound collection unit,
The control unit of the mobile terminal is
Said management record the billing data acquired from the server to the payment information storage section, and outputs the claims list the billing data recorded in the payment information storage section on the display unit,
The sound collecting unit collects the reading sound of the code image at the store terminal,
When a plurality of billing data is selected in the billing list, and it is determined that the detection of the reading sound is not difficult, the code image corresponding to the billing data is read by the code reader of the store terminal Obtaining a possible code image from the management server, and sequentially outputting the code image to the display unit based on the sound collection ;
If it is determined that it is difficult to detect the reading sound, a message prompting a bill integration process is displayed. If a bill to be paid together is specified in the bill list, the integration including the specified bill is performed. A request is transmitted to the management server, and the management server is a code image corresponding to a newly assigned integrated billing code based on the billing data included in the integration request, and the code of the store terminal A code image readable by a reader is acquired from the management server, and the code image is output to the display unit ,
In accordance with the sound collection , the payment support system includes means for recording information indicating payment for the billing data of the code image displayed before the sound collection in the payment information storage unit . The control unit of the mobile terminal is
In the payment information storage unit, specify billing data in which information indicating payment is not recorded,
Payment support system according to claim 1, wherein identifying the payment date of billing data, and outputs an alert based on the due date. 2. The control unit of the portable terminal, when acquiring a payment confirmation for the bill from the management server, records paid information for the bill in the payment information storage unit. Or the payment support system according to 2; The control unit of the mobile terminal is
Storing the fault area designated on the display screen;
The payment according to any one of claims 1 to 3 , wherein when the code image is output to the display unit, the code image is displayed in an area other than the stored failure area. Support system. In the store terminal, a control unit connected to a management server having a billing information storage unit for storing billing data for payment;
A payment information storage unit for storing the billing data;
A payment support method using a mobile terminal including a display unit for displaying a code image and a sound collection unit,
The control unit of the mobile terminal is
Said management record the billing data acquired from the server to the payment information storage section, and outputs the claims list the billing data recorded in the payment information storage section on the display unit,
The sound collecting unit collects the reading sound of the code image at the store terminal,
When a plurality of billing data is selected in the billing list, and it is determined that the detection of the reading sound is not difficult, the code image corresponding to the billing data is read by the code reader of the store terminal Obtaining a possible code image from the management server, and sequentially outputting the code image to the display unit based on the sound collection ;
If it is determined that it is difficult to detect the reading sound, a message prompting a bill integration process is displayed. If a bill to be paid together is specified in the bill list, the integration including the specified bill is performed. A request is transmitted to the management server, and the management server is a code image corresponding to a newly assigned integrated billing code based on the billing data included in the integration request, and the code of the store terminal A code image readable by a reader is acquired from the management server, and the code image is output to the display unit ,
In accordance with the sound collection, the payment information storage unit executes a step of recording information indicating payment for the billing data of the code image displayed before the sound collection. . In the store terminal, a control unit connected to a management server having a billing information storage unit for storing billing data for payment;
A payment information storage unit for storing the billing data;
A payment support program for supporting payment using a portable terminal including a display unit for displaying a code image and a sound collection unit,
A control unit of the mobile terminal;
Said management record the billing data acquired from the server to the payment information storage section, and outputs the claims list the billing data recorded in the payment information storage section on the display unit,
The sound collecting unit collects the reading sound of the code image at the store terminal,
When a plurality of billing data is selected in the billing list, and it is determined that the detection of the reading sound is not difficult, the code image corresponding to the billing data is read by the code reader of the store terminal Obtaining a possible code image from the management server, and sequentially outputting the code image to the display unit based on the sound collection ;
If it is determined that it is difficult to detect the reading sound, a message prompting a bill integration process is displayed. If a bill to be paid together is specified in the bill list, the integration including the specified bill is performed. A request is transmitted to the management server, and the management server is a code image corresponding to a newly assigned integrated billing code based on the billing data included in the integration request, and the code of the store terminal A code image readable by a reader is acquired from the management server, and the code image is output to the display unit ,
A payment support program for causing the payment information storage unit to function as means for recording information indicating payment for the billing data of the code image displayed before the sound collection in accordance with the sound collection. .

Images