Method, device, and system for paying for intelligent electronic meal coupon when communication failure occurs

Abstract

Disclosed are a method, a device, and a system for paying for an intelligent electronic meal coupon when a communication failure occurs. According to an embodiment of the present disclosure, a system for paying for an intelligent electronic meal coupon may comprise: a user terminal for receiving a first code issued from a management server and generating a second code when a communication failure occurs; a complex payment terminal for scanning the first code or the second code to store offline payment details and updating the offline payment details; a manager terminal for determining a processing state of payment details by using the offline payment details, and generating final offline payment details by using the processing state of the payment details; and the management server for generating and managing the first code, and processing the payment of one or more payment items included in the final offline payment details.

Description

Method, device and system for paying with an intelligent electronic ticket in the event of a communication failure

[0001] The present disclosure relates to a method, device, and system for making payments using intelligent electronic vouchers in the event of a communication failure. More specifically, the present disclosure relates to a method, device, and system for storing payment details using a QR code or barcode when a server or network failure occurs, and for making payments using the payment details when the failure is resolved.

[0002] The content described below merely provides background information related to the present embodiment and does not constitute prior art.

[0003] Typically, companies issue meal coupons (paper or electronic) to their employees (hereinafter referred to as "users") for use at cafeterias or nearby restaurants. This meal coupon system requires users to submit the coupons directly to the franchisee, creating inconveniences for both users and franchisees in managing the coupons.

[0004] Research is actively underway on technologies that allow users to use electronic meal coupon applications to pay for their meal tickets. Current electronic meal coupon applications generate electronic meal tickets in the form of coupon screens. When users present the coupon screens to merchants, merchants verify that a matching coupon is already present on their terminals and then authorize their use.

[0005] However, in the event of a communication failure, such as a server or network failure, electronic ticket payments cannot be made using the electronic ticket application. In this case, merchants can manually record the user's payment details and settle the transaction later. However, this method causes inconvenience to both merchants and users and can lead to inaccurate settlements.

[0006] The purpose of this disclosure is to store a user's payment history using a QR code or barcode, etc., in case of a server failure or network failure.

[0007] Additionally, according to one embodiment, the purpose is to pay for electronic tickets using an offline payment mode in the event of a server failure or network failure.

[0008] Additionally, according to one embodiment, the purpose is to increase the accuracy of settlement and ensure the convenience of payment by using offline payment mode in case of server failure or network failure.

[0009] The problems to be solved by the present invention are not limited to the problems mentioned above, and other problems not mentioned will be clearly understood by those skilled in the art from the description below.

[0010] According to the present disclosure, a system for paying for an electronic meal ticket may include a user terminal for receiving a first code from a management server and generating a second code when a communication failure occurs, a composite payment terminal for scanning the first code or the second code to store offline payment details and update the offline payment details, an administrator terminal for determining a processing status of the payment details using the offline payment details and generating a final offline payment details using the processing status of the payment details, and the management server for generating and managing the first code and processing one or more payment items included in the final offline payment details.

[0011] According to the present disclosure, a method for paying for an electronic meal ticket may include, and may include, a process of scanning a first code or a second code and storing offline payment details when a communication failure occurs, a process of determining a processing status of the payment details using the offline payment details, a process of generating a final offline payment details using the processing status of the payment details, a process of processing one or more payment items included in the final offline payment details, and a process of updating the offline payment details using the one or more payment items.

[0012] According to the present disclosure, a computer-readable recording medium is a computer-readable recording medium having stored thereon a command, which, when executed by the computer, causes the computer to perform a process of scanning a first code or a second code and storing offline payment details when a communication failure occurs, a process of determining a processing status of the payment details using the offline payment details, a process of generating a final offline payment details using the processing status of the payment details, a process of processing one or more payment items included in the final offline payment details, and a process of updating the offline payment details using the one or more payment items.

[0013] According to the present disclosure, there is an effect in which a user's payment history can be stored using a QR code or barcode, etc. in the event of a server failure or network failure.

[0014] Additionally, according to one embodiment, there is an effect that allows electronic ticket payment using offline payment mode in the event of a server failure or network failure.

[0015] Additionally, according to one embodiment, in the event of a server failure or network failure, the offline payment mode can be used to increase the accuracy of settlement and ensure the convenience of payment.

[0016] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.

[0017] FIG. 1 is a block diagram for explaining an electronic ticket system (10) according to one embodiment of the present disclosure.

[0018] FIG. 2 is a drawing for explaining a process of performing an offline payment mode using a barcode according to one embodiment of the present disclosure.

[0019] FIG. 3 is a drawing for explaining a process of performing an offline payment mode using a QR code according to one embodiment of the present disclosure.

[0020] FIG. 4 is a diagram illustrating a process of storing offline payment details using the validity of a QR code according to one embodiment of the present disclosure.

[0021] FIG. 5 is a drawing for explaining a method for paying for an electronic ticket when a communication failure occurs according to one embodiment of the present disclosure.

[0022] Hereinafter, some embodiments of the present disclosure will be described in detail using exemplary drawings. When designating components in each drawing, it should be noted that, where possible, identical components are given the same reference numerals, even if they appear in different drawings. Furthermore, when describing the present disclosure, detailed descriptions of related known structures or functions will be omitted if they are deemed to obscure the gist of the present disclosure.

[0023] In describing components of embodiments according to the present disclosure, symbols such as first, second, i), ii), a), b) may be used. These symbols are only for distinguishing the components from other components, and the nature, order, or sequence of the components are not limited by the symbols. When a part in the specification is said to "include" or "have" a component, this does not mean that other components are excluded, but rather that other components may be included, unless explicitly stated otherwise.

[0024] The detailed description set forth below, together with the accompanying drawings, is intended to explain exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure may be practiced.

[0025] FIG. 1 is a block diagram for explaining an electronic ticket system (10) according to one embodiment of the present disclosure.

[0026] Referring to FIG. 1, the electronic meal ticket system (10) according to the present embodiment includes all or part of a user terminal (110), a composite payment terminal (130), an electronic meal ticket management server (150), and a corporate terminal (160). The electronic meal ticket system (10) illustrated in FIG. 1 is according to one embodiment, and not all blocks illustrated in FIG. 1 are essential components, and some blocks included in the electronic meal ticket system (10) in other embodiments may be added, changed, or deleted. For example, a terminal management server for managing a user terminal (110) or a merchant terminal management server for managing a composite payment terminal (130) may be added.

[0027] The electronic meal ticket system (10) can provide an electronic meal ticket platform to process settlement between a merchant and a company when a user (hereinafter, "user"), such as a company employee, uses an electronic meal ticket generated by a user terminal (110). Hereinafter, each component included in the electronic meal ticket system (10) will be described.

[0028] The user terminal (110) is equipped with an electronic meal coupon application (120) for generating, using, and managing electronic meal coupons. The user terminal (110) can operate the electronic meal coupon application (120) by the user's operation or command, and use the operated electronic meal coupon application (120). The electronic meal coupon application (120) includes all or part of a merchant list generation unit (121), a point management unit (122), an expiration date renewal unit (123), a cancellation unit (124), an electronic meal coupon generation unit (125), an electronic meal coupon payment unit (126), an electronic meal coupon use unit (127), an input unit (128), and an offline processing unit (129). However, although FIG. 1 illustrates these as components operated as components, this is not necessarily limited thereto, and each component may be implemented as a module included in the user terminal (110).

[0029] The user terminal (110) according to this embodiment can generate an electronic meal ticket by prepaying for a meal using stored corporate points and personal points. The user can use the generated electronic meal ticket. Here, the electronic meal ticket may include a touch area that moves according to a preset pattern. Corporate points are points that the company grants to employees to use when paying for electronic meal tickets. Personal points are points that the user charges to use when paying for electronic meal tickets.

[0030] The affiliated store list generation unit (121) can generate an affiliated store list based on information about affiliated stores that have signed up for the electronic meal ticket service. The affiliated store list generation unit (121) can extract affiliated store information that satisfies one or more conditions among affiliated stores located within a preset area, affiliated stores located within a preset distance based on the current location of the user terminal (110), affiliated stores pre-selected from a corporate terminal (160), and affiliated stores available in real time based on the affiliated store's holidays or operating hours, and can generate an affiliated store list using the extracted affiliated store information.

[0031] The affiliated store list generation unit (121) can sort the affiliated store list according to a classification request signal input by the user, if such a classification request signal exists. For example, the affiliated store list generation unit (121) can sort the affiliated store list generated based on the classification request signal according to conditions such as time zone, restaurant type, main menu, popularity, and distance.

[0032] The point management unit (122) can store and manage corporate and individual points. The point management unit (122) can store corporate points. Corporate points can be issued regularly, such as monthly or yearly, based on company policy. Corporate points can be issued regularly by department or user.

[0033] The point management unit (122) can store personal points purchased separately from corporate points using any of the following payment methods: credit card, T-Money, prepaid card, or simple payment. Here, personal points can be points that users can personally recharge and use. Personal points alone or a combination of personal and corporate points can be used.

[0034] The point management unit (122) can separately store the charging and usage records of corporate points and individual points. When a point history request signal is input by the user, the point management unit (122) can output the status of charging and usage records for each of the corporate points and individual points using the display unit (not shown) provided in the user terminal (110). For example, when a point history request signal is input, the point management unit (122) can provide information such as integrated point information combining corporate points and individual points, available point information for each of the corporate points and individual points, and used point information based on the point history request signal. In addition, the point management unit (122) can modify and manage corporate points and individual points in real time by reflecting the points deducted as the meal cost is paid.

[0035] The electronic meal ticket payment unit (126) can process meal payments by combining corporate points and individual points with reference to a preset usage limit. The electronic meal ticket payment unit (126) can process meal payments by combining corporate points and individual points with reference to a preset corporate usage limit when paying for meals based on menu information provided by a selected merchant from a list of merchants.

[0036] The electronic meal ticket payment unit (126) can process payment using only corporate points if the price of the corresponding menu item can be paid using only corporate points. Meanwhile, the electronic meal ticket payment unit (126) can process payment using additional personal points if corporate points cannot be used due to reasons such as a corporate use limit or if the price of the corresponding menu item exceeds the corporate use limit. In other words, the electronic meal ticket payment unit (126) can process payment for the meal item using only corporate points, personal points, or a combination of corporate points and personal points. Here, the corporate use limit may be an upper limit of corporate points that can be used to pay for the meal item, such as a daily use limit or a maximum use limit. Here, the daily use limit may be a limit set according to corporate policy, which limits the amount of corporate points that can be used in a single payment. The maximum use limit may be a limit set, which limits the maximum amount of corporate points that can be used in a single payment.

[0037] If the company's usage limit is set to a daily usage limit, the electronic meal ticket payment unit (126) can automatically deduct an amount corresponding to the daily usage limit from the company's points as part of the meal cost, and process the meal cost by deducting the remaining meal cost from the individual's points. Here, the individual points can be automatically deducted or manually deducted based on the user's input.

[0038] If the company's usage limit is set to the maximum usage limit, the electronic meal ticket payment unit (126) can first deduct an amount corresponding to all or part of the maximum usage limit from the company's points as part of the meal cost, and then process the payment by deducting the remaining meal cost from the personal points. Here, the company points and personal points can be deducted according to the user's input.

[0039] The electronic meal ticket payment unit (126) can automatically distribute the corporate points and individual points according to the use ratio when combining corporate points and individual points, so that the meal cost can be paid. For example, if the use ratio of corporate points and individual points is set to '6:4', the electronic meal ticket payment unit (126) can automatically deduct '6,000 points' from the corporate points and '4,000 points' from the individual points to pay the meal cost of '10,000 won'.

[0040] In addition, the electronic meal ticket payment unit (126) can process multiple payment modes or user location-based payment modes. In 'multiple payment modes', that is, when multiple users' meal expenses are paid by one user first and then shared later, the electronic meal ticket payment unit (126) can process payment by linking with multiple terminals to generate a single integrated meal ticket. Among multiple users, User 1 using multiple payment modes can be granted the right to select a member. User 1 can select a member who participated in the payment together. User 1 inputs the meal expenses to be paid together into his / her user terminal (110). After input, the electronic meal ticket payment unit (126) sends an approval request signal requesting individual points corresponding to the shared payment amount to the individual terminals of the members of the multiple payment modes. The electronic meal ticket payment unit (126) can process the integrated meal expenses by adding up the approved individual points. The electronic meal ticket generation unit (125) can generate an electronic meal ticket corresponding to the integrated meal expenses.

[0041] In the case of a 'payment mode based on user position', that is, when payment is to be made based on the user's location, the user terminal (110) can obtain location information (latitude, longitude, etc.) using GPS reception or other methods. The information for generating a list of merchants is based on the premise that the location information of each merchant is included. The electronic meal ticket payment unit (126) can obtain the location information of the user terminal (110) and select a specific merchant that matches the location information of the user terminal (110) from the generated list of merchants. If the merchant can be selected, the electronic meal ticket payment unit (126) can output the menu information of the selected merchant using the display unit and allow the user to immediately pay for the meal based on the menu information. If an electronic meal ticket that can be used at the corresponding merchant has already been generated, the electronic meal ticket payment unit (126) can output the list of electronic meal tickets instead of the menu information of the merchant using the display unit. If the merchant cannot be selected, the electronic ticket payment unit (126) can output a notification that selection is not possible using the display unit.

[0042] The electronic meal ticket generation unit (125) can generate an electronic meal ticket corresponding to the meal price. The electronic meal ticket may include a touch area that moves according to a preset pattern. The "pre-set pattern" may be a pattern set by the merchant using the composite payment terminal (130) before the electronic meal ticket is generated. The "merchant" may be a merchant using the composite payment terminal (130) according to the present embodiment.

[0043] The touch area of ​​the electronic ticket can be visually displayed on the display of the user terminal (110). The pattern must be set before the electronic ticket is generated. However, there are cases where the merchant does not set a pattern before the electronic ticket is generated. To prepare for such cases, it is preferable for the composite payment terminal (130) or electronic ticket management server (150) to set a default pattern. In this case, this default pattern may be a "pre-set pattern."

[0044] The pattern can be any pattern created by the merchant. The preset pattern can be changed by the merchant even after the electronic ticket is generated. For example, the merchant can set different patterns depending on the day of the week or time of day. Specifically, the composite payment terminal (130) may include a pattern designation unit (141) that designates a pattern that moves according to the touch area of ​​the electronic ticket. The composite payment terminal (130) can set a notification to change the pattern, allowing the pattern to be changed periodically. The pattern applied may vary depending on the day of the week or time of day.

[0045] When a merchant selects a pattern setting menu using a combination payment terminal (130) to set a pattern, a list of configurable patterns may be displayed on the combination payment terminal (130). When the merchant selects a specific pattern, the pattern setting unit (141) may store the specific pattern in the combination payment terminal (130) and transmit the stored pattern information to the electronic meal ticket management server (150).

[0046] To set a pattern, the merchant can select the user-created pattern setting menu and then input any pattern into the composite payment terminal (130). The pattern setting unit (141) can store the input pattern in the composite payment terminal (130) and transmit the stored pattern information to the electronic meal ticket management server (150).

[0047] To set a pattern, the merchant can select a day-of-the-week or hour-of-the-hour setting menu, then determine a day-of-the-week list or hour-of-the-hour list and a pattern to be set for the corresponding day or hour on the composite payment terminal (130). The pattern setting unit (141) can store a pattern applied to a specific day or hour on the composite payment terminal (130) and transmit the stored information to the electronic meal ticket management server (150).

[0048] To set a pattern, the merchant can select the "Pattern Change Notification Settings" menu and then select a specific notification time and cycle. The pattern setting unit (141) can store the notification time and cycle information in the composite payment terminal (130) and transmit the information to the electronic meal ticket management server (150).

[0049] The electronic meal ticket generation unit (125) can generate an electronic meal ticket that includes personal information such as the user's name, phone number, department, and position, as well as identification information identical to that of the complex payment terminal (130). Here, the identification information may include personal information, the processed meal price, the color of the electronic meal ticket, and an identification code number assigned when generating the electronic meal ticket.

[0050] Specifically, the electronic meal ticket generation unit (125) can generate electronic meal tickets using different colors each time an electronic meal ticket is generated. Electronic meal tickets can be generated using a color randomly selected from a number of colors to facilitate identification. Electronic meal tickets can be generated using colors determined in response to preset criteria such as price range, franchise, and meal time (e.g., lunch or dinner).

[0051] When the electronic meal ticket generation unit (125) receives a payment completion signal from the merchant terminal, it adds meal ticket usage information to the used electronic meal ticket. In this case, the electronic meal ticket generation unit (125) can process the used electronic meal ticket as completed. The electronic meal ticket may have an expiration date set. In this case, if there is a preset expiration date, the electronic meal ticket generation unit (125) can generate an electronic meal ticket with such an expiration date set. If the expiration date is set after the electronic meal ticket is generated, the electronic meal ticket generation unit (125) can include the expiration date information in the electronic meal ticket when receiving the expiration date information. If the expiration date is changed, the electronic meal ticket generation unit (125) can change the expiration date of the electronic meal ticket when receiving the change information. In this case, the newly included or changed expiration date may become the 'preset expiration date.'

[0052] When the electronic meal ticket application (120) is executed, the validity period renewal unit (123) can check which of the generated electronic meal tickets are within the renewal period. The renewal period may be a period set by default in the electronic meal ticket application (120) or a period specified by the user. The renewal period may be set based on the expiration date of each meal ticket. The validity period renewal unit (123) can check whether the generated electronic meal tickets are within the extension period of the validity period and provide the user with the confirmation result. If the user inputs the relevant information into the user terminal (110) to extend the validity period, the validity period renewal unit (123) can extend the validity period of the electronic meal ticket. If the validity period of the electronic meal ticket has expired but has not been extended, the cancellation unit (124) can delete the electronic meal ticket in the electronic meal ticket application (120).

[0053] When the electronic ticket touch area (not shown) receives a touch input, the electronic ticket user (127) can process the electronic ticket as completed. The entity touching the electronic ticket touch area may be the franchisee. At this time, the franchisee can verify whether the electronic ticket touch area moves according to a preset pattern to confirm the use of a valid ticket.

[0054] The touch of the touch area is used to confirm the validity of the electronic meal ticket, and the completion of use of the electronic meal ticket can be performed when the user terminal (110) and the composite payment terminal (130) transmit and receive a signal regarding the use of the electronic meal ticket. In this case, the completion of use of the electronic meal ticket can be performed only when conditions 1 and 2 are met at the same time. Here, condition 1 is that the touch of the touch area is performed, and condition 2 is that the user terminal (110) receives a signal regarding the use of the composite payment terminal (130). The electronic meal ticket touch area can be implemented in the form of a confirmation button that receives a payment completion signal from a merchant or the composite payment terminal (130).

[0055] The input unit (128) can perform operations for receiving or acquiring various input signals for using the electronic ticket service. The input unit (128) can acquire input signals input in various forms such as touch input, voice input, text input, and button input, and transmit the input signals to the corresponding components of the user terminal (110) so that an operation corresponding to the input signal is performed.

[0056] The wireless communication unit (not shown) can be connected to terminals that are linked to the electronic meal ticket system (10) and perform operations to transmit and receive various data and signals between them. Here, the wireless communication unit can change the status of the electronic meal ticket through wireless communication. For example, the wireless communication unit can change the pattern of movement according to the touch area of ​​the electronic meal ticket by using one of the wireless communication methods such as Near Field Communication (NFC), Bluetooth Low Energy (BLE), Wi-Fi, Ultra Wideband (UWB), Radio Frequency (RF), Infrared Data Association (IrDA), Zigbee, QR Code (Quick Response Code), etc. The offline processing unit (129) can process the tasks performed by the user terminal (110) to perform an offline payment mode. Here, the offline payment mode is a mode in which, when a server failure or network failure occurs due to a communication failure, the user's payment details are saved and, when the failure is resolved, the payment is processed by linking with the electronic meal ticket management server (150).

[0057] The composite payment terminal (130) may be a terminal installed in a merchant that has subscribed to the electronic meal ticket service in order to provide the electronic meal ticket service. Here, the composite payment terminal (130) may be a terminal carried by the merchant, but is not necessarily limited thereto, and may be implemented as, for example, a POS (Point of Sale) device or a KIOSK device, as long as the manager application (140) is installed and can be operated. The composite payment terminal (130) may provide the electronic meal ticket service by linking with the user terminal (110) using the NFC (Near Field Communication) method, Bluetooth Low Energy (BLE), wireless LAN (WIFI), Ultra Wideband (UWB), radio frequency (RF), infrared communication (IrDA: Infrared Data Association), Zigbee, QR code (Quick Response Code), etc.

[0058] The complex payment terminal (130) is equipped with a manager application (140). The manager application (140) can provide electronic meal ticket services such as pattern designation, settlement, and management of electronic meal tickets. The complex payment terminal (130) can run the manager application (140) according to the operation or command of the merchant, and provide electronic meal ticket services using the run manager application (140). The manager application (140) is illustrated as being run including a pattern designation unit (141), a payment confirmation unit (142), a sales management unit (144), a payment cancellation unit (146), a settlement processing unit (148), and an offline processing unit (149), but is not necessarily limited thereto, and each component can be implemented as a module included in the complex payment terminal (130).

[0059] Regarding the pattern setting unit (141), it is similar to what was described in relation to the electronic meal ticket generation unit (125) of the user terminal (110). The payment confirmation unit (142) can perform an operation of checking and displaying whether the electronic meal ticket generated by the user terminal (110) has been used. The payment confirmation unit (142) can obtain and store an electronic meal ticket for the affiliated store. When the electronic meal ticket is used, the payment confirmation unit (142) can process the electronic meal ticket for the affiliated store to be marked as having been used. For example, the payment confirmation unit (142) can store and display used and unused electronic meal tickets separately, and change the display of a stamp with the phrase "used" on the used electronic meal ticket.

[0060] The sales management department (144) can perform operations to manage sales information of affiliated stores. The sales management department (144) can provide sales information for a manually entered period, a preset period, a monthly period, a daily period, or other inquiry periods. While it is preferable that the sales information be obtained through linkage with the electronic meal ticket management server (150), it is not necessarily limited thereto.

[0061] The payment cancellation unit (146) can cancel payment for a previously processed electronic meal ticket. If a payment cancellation request exists due to a merchant's request or other reasons, the payment cancellation unit (146) can input the identification code number of the electronic meal ticket to check whether the electronic meal ticket has been used and cancel the payment for the electronic meal ticket. The settlement processing unit (148) can classify and provide the completed meal expenses by company or payment method using corporate points and individual points. The settlement processing unit (148) can process the amount paid by the corporate payment method or individual payment method to be settled on a preset date and provide the unprocessed settlement details. The offline processing unit (149) can process the tasks performed by the composite payment terminal (130) to perform the offline payment mode.

[0062] The electronic meal ticket management server (150) can transmit and receive various data related to the electronic meal ticket service, and store and manage various data related to the electronic meal ticket. The electronic meal ticket management server (150) can store and manage various data related to the electronic meal ticket transmitted and received between the user terminal (110) and the complex payment terminal (130), such as data related to the number of electronic meal tickets created, the number of electronic meal tickets used, the pattern of the electronic meal ticket touch area, meal cost, usage amount by company, usage amount by department, and usage amount by individual, etc.

[0063] The electronic meal ticket management server (150) can register detailed information about affiliated stores (e.g., business hours, event information, etc.) as affiliated store information in a database, and can manage businesses that have subscribed to the electronic meal ticket service and affiliated store owners belonging to the businesses by registering them in the database. The electronic meal ticket management server (150) can also be implemented to process some of the functions of the components of the user terminal (110). For example, the electronic meal ticket management server (150) can be implemented to create a list of affiliated stores using information about businesses that have already subscribed to the electronic meal ticket service, or to store corporate points and individual points and provide only combined points to the user terminal (110) according to a preset usage limit.

[0064] The electronic meal ticket management server (150) can generate statistical data for affiliated stores or businesses. When the electronic meal ticket management server (150) receives a statistics request signal from a composite payment terminal (130) or a business terminal (160), the electronic meal ticket management server (150) can use data related to previously stored electronic meal tickets to generate statistical data according to conditions such as daily, monthly, periodic, company, and job title, and provide the statistical data to the composite payment terminal (130) or business terminal (160). The electronic meal ticket management server (150) registers various event information or discount information obtained from the composite payment terminal (130) in a database, and sends the registered event information or discount information to the user terminal (110) in the form of a text message, etc.

[0065] The corporate terminal (160) can link with the electronic meal ticket management server (150) to provide payment details paid using corporate points to the user terminal (110). The corporate terminal (160) can perform operations to manage various data and status regarding the electronic meal ticket service. The corporate terminal (160) can access the electronic meal ticket management server (150) to perform employee management, point management, and settlement management, and can check the merchant list and / or electronic meal ticket usage status.

[0066] FIG. 2 is a drawing for explaining a process of performing an offline payment mode using a barcode according to one embodiment of the present disclosure.

[0067] Referring to FIG. 2, the management server can generate and manage barcodes (S210). The management server can receive an authentication key from a user terminal (110) and generate a barcode using the received authentication key. The management server can generate a barcode that can only be used by a specific user. The management server can transmit the generated barcode to the user terminal (110).

[0068] The user terminal (110) can receive a barcode from the management server (S220). When the user terminal (110) runs the electronic meal ticket application, the user terminal (110) can receive a barcode from the management server. The user terminal (110) can store the issued barcode. If a server or network failure occurs due to a communication failure, the user terminal (110) can present the barcode (S230). If a server or network failure occurs, an error may occur when connecting to the management server. The network failure may be caused by a problem with the router or line. If a server or network failure occurs, the user terminal (110) can present a meal ticket card in addition to the barcode.

[0069] The complex payment terminal (130) can scan a barcode (S240). The complex payment terminal (130) can perform offline payment mode. The complex payment terminal (130) can change the general payment mode to offline payment mode. The complex payment terminal (130) can scan a barcode after receiving the user's payment amount. The barcode can be scanned using a mobile phone camera. If the barcode cannot be scanned, the barcode number can be directly entered into the complex payment terminal (130). If the server or network failure is resolved, the complex payment terminal (130) can store offline payment details (S250). The offline payment details can include information such as payment approval status, merchant number, menu name, menu number, number of menu items, payment amount, payment time, meal ticket card number, and barcode number. Even before the server or network failure is resolved, the complex payment terminal (130) can store offline payment details. The composite payment terminal (130) can transmit offline payment details to the management server.

[0070] The management server can receive offline payment details (S260). The management server can transmit the offline payment details to the administrator terminal. The administrator terminal can receive the offline payment details. The administrator terminal can use the offline payment details to search payment details. The administrator terminal can generate a final offline payment details (S270). The administrator terminal can review the offline payment details and determine the processing status of the payment details. The processing status of the payment details can include approval status, pending status, and cancellation status. The administrator terminal can generate a final offline payment details using the review results of the offline payment details. The final offline payment details can include information such as the transaction number, barcode number, meal ticket number, payment amount, payment time, management server registration date, merchant name, and payment processing status. The administrator terminal can transmit the final offline payment details to the management server.

[0071] The management server can receive the final offline payment details. The management server can process the payment using the final offline payment details. The management server can transmit the payment processing result to the composite payment terminal (130). The composite payment terminal (130) can update the offline payment details. If there is an unsaved payment details in the offline payment details, the composite payment terminal (130) can update the offline payment details and register the unsaved payment details in the offline payment details. The composite payment terminal (130) can update the offline payment details when the offline payment mode ends, when the electronic meal ticket application is launched, or when the electronic meal ticket application is terminated.

[0072] FIG. 3 is a drawing for explaining a process of performing an offline payment mode using a QR code according to one embodiment of the present disclosure.

[0073] Referring to Figure 3, if a server or network failure occurs before the user launches the electronic ticket application, the user terminal (110) can generate a QR code (S310). The QR code can be generated when the user clicks "Generate Offline Payment QR Code" displayed on the interface of the user terminal (110).

[0074] The complex payment terminal (130) can scan a QR code (S320). The complex payment terminal (130) can perform offline payment mode. The complex payment terminal (130) can change the general payment mode to offline payment mode. The complex payment terminal (130) can scan a QR code after receiving the user's payment amount. The QR code can be scanned using a mobile phone camera. If a server or network failure is resolved, the complex payment terminal (130) can store offline payment details (S330). The offline payment details can include information such as payment approval status, merchant number, menu name, menu number, number of menus, payment amount, payment time, QR code, etc. Even before the server or network failure is resolved, the complex payment terminal (130) can store offline payment details. The complex payment terminal (130) can transmit the offline payment details to the management server.

[0075] The management server can receive offline payment details (S340). The management server can transmit the offline payment details to the administrator terminal. The administrator terminal can receive the offline payment details. The administrator terminal can use the offline payment details to search payment details. The administrator terminal can generate a final offline payment details (S350). The administrator terminal can review the offline payment details and determine the payment details processing status. The payment details processing status may include approval status, pending status, and cancellation status. The administrator terminal can generate a final offline payment details using the review results of the offline payment details. The final offline payment details may include information such as the transaction number, QR code, payment amount, payment time, management server registration date, merchant name, and payment details processing status. The administrator terminal can transmit the final offline payment details to the management server.

[0076] The management server can receive the final offline payment details. The management server can process the payment using the final offline payment details. The management server can transmit the payment processing result to the composite payment terminal. The composite payment terminal (130) can update the offline payment details. If there is a payment details that are not saved in the offline payment details, the composite payment terminal (130) can update the offline payment details and register the unsaved payment details in the offline payment details. The composite payment terminal (130) can update the offline payment details when the offline payment mode ends, when the electronic meal ticket application is launched, or when the electronic meal ticket application is terminated.

[0077] FIG. 4 is a diagram illustrating a process of storing offline payment details using the validity of a QR code according to one embodiment of the present disclosure.

[0078] Referring to FIG. 4, a user terminal (110) can generate a QR code. The user terminal (110) can generate a QR code using the user's personal information. The user's personal information can include information such as the user's company identification number, the user's identification number, the current time, and an encryption key. The complex payment terminal (130) determines whether the QR code is valid (S410). The complex payment terminal (130) can scan the QR code to determine its validity. The complex payment terminal (130) can check the validity of the QR code by confirming whether the user's personal information used to generate the QR code matches the user's personal information stored in the complex payment terminal (130).

[0079] If the QR code is determined to be invalid (S410-NO), the composite payment terminal (130) may output a payment failure notification (S420). In this case, the composite payment terminal (130) may not save the corresponding payment details. If the QR code is determined to be valid (S410-YES), the composite payment terminal (130) may determine whether the QR code generation time exceeds 5 minutes after generation (S430). If the QR code generation time exceeds 5 minutes after generation (S430-YES), the composite payment terminal (130) may output a payment failure notification (S420). In this case, the composite payment terminal (130) may not save the corresponding payment details. If the QR code generation time does not exceed 5 minutes after generation (S430-NO), the composite payment terminal (130) may save the corresponding payment details in the offline payment details (S440).

[0080] FIG. 5 is a drawing for explaining a method for paying for an electronic ticket when a communication failure occurs according to one embodiment of the present disclosure.

[0081] Referring to FIG. 5, a system for paying for electronic meal tickets (hereinafter, “electronic meal ticket payment system”) may scan a first code or a second code and store offline payment details in the event of a communication failure (S510). The first code may be a barcode. The second code may be a QR code. The second code may be a code generated by a user terminal using at least one of the user’s company’s unique number, the user’s unique number, the generation time, and the encryption key. The process of storing offline payment details may include a process of verifying the validity of the second code using at least one of the user’s company’s unique number, the user’s unique number, the generation time, and the encryption key, and a process of storing offline payment details based on the validity of the second code. The offline payment details may include at least one of information regarding payment approval, information regarding the merchant number, information regarding the menu name, information regarding the menu number, information regarding the number of menus, information regarding the payment amount, information regarding the payment time, information regarding the first code number, and information regarding the second code.

[0082] The electronic meal ticket payment system can determine the processing status of the payment details using offline payment details and generate a final offline payment details using the processing status of the payment details (S520). The processing status of the payment details may include at least one of an approval status, a pending status, and a cancellation status. The electronic meal ticket payment system can process one or more payment items included in the final offline payment details (S530). The final offline payment details may include at least one of a transaction number, a first code number, a meal ticket number, a payment amount, a payment time, a management server registration date, a merchant name, and a payment details processing status. The electronic meal ticket payment system can update the offline payment details using one or more payment items (S540).

[0083] Each component of the device or method according to the present invention may be implemented in hardware, software, or a combination of hardware and software. Furthermore, the functions of each component may be implemented in software, with a microprocessor executing the software functions corresponding to each component.

[0084] Various implementations of the systems and techniques described herein may be implemented as digital electronic circuits, integrated circuits, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), computer hardware, firmware, software, and / or combinations thereof. These various implementations may include implementations of one or more computer programs executable on a programmable system. The programmable system includes at least one programmable processor (which may be a special purpose processor or a general purpose processor) coupled to receive data and instructions from and transmit data and instructions to a storage system, at least one input device, and at least one output device. Computer programs (also known as programs, software, software applications, or code) include instructions for the programmable processor and are stored on a "computer-readable recording medium."

[0085] A computer-readable recording medium includes any type of recording device that stores data that can be read by a computer system. Such a computer-readable recording medium may be a non-volatile or non-transitory medium such as a ROM, CD-ROM, magnetic tape, floppy disk, memory card, hard disk, magneto-optical disk, storage device, and may further include a transitory medium such as a data transmission medium. Furthermore, the computer-readable recording medium may be distributed across network-connected computer systems, so that computer-readable code can be stored and executed in a distributed manner.

[0086] Although the flowchart of this specification describes each process as being executed sequentially, this is merely an illustrative description of the technical idea of ​​one embodiment of the present disclosure. In other words, a person of ordinary skill in the art to which one embodiment of the present disclosure pertains may modify and apply various modifications and variations, such as changing the order described in the flowchart and executing it or executing one or more of the processes in parallel, without departing from the essential characteristics of one embodiment of the present disclosure. Therefore, the flowchart is not limited to a chronological order.

[0087] The above description is merely an example of the technical idea of ​​the present embodiment, and those skilled in the art will appreciate that various modifications and variations can be made without departing from the essential characteristics of the present embodiment. Therefore, the present embodiments are not intended to limit the technical idea of ​​the present embodiment, but rather to explain it, and the scope of the technical idea of ​​the present embodiment is not limited by these embodiments. The scope of protection of the present embodiment should be interpreted by the claims below, and all technical ideas within a scope equivalent thereto should be interpreted as being included in the scope of rights of the present embodiment.

[0088]

[0089] CROSS-REFERENCE TO RELATED APPLICATION

[0090] This patent application claims priority to Korean Patent Application No. 10-2023-0109019, filed on August 21, 2023, the entire contents of which are incorporated herein by reference.

Claims

1. In the event of a communication failure, in the system for paying for electronic tickets, A user terminal for receiving a first code from the management server and generating a second code in the event of a communication failure; A composite payment terminal for storing offline payment details by scanning the first code or the second code and updating the offline payment details; An administrator terminal for determining the processing status of payment details using the above offline payment details and generating a final offline payment details using the processing status of the above payment details; and A system comprising a management server for generating and managing the first code and processing one or more payment items included in the final offline payment details.

2. In paragraph 1, The above user terminal, A system that generates the second code using at least one of the user's company's unique number, the user's unique number, the generation time, and the encryption key.

3. In paragraph 1, The above complex payment terminal, A system that verifies the validity of the second code using at least one of the user's company's unique number, the user's unique number, the generation time, and the encryption key, and stores the offline payment details based on the validity of the second code.

4. In paragraph 1, A system in which the above offline payment details include at least one of information on whether payment has been approved, information on the number of the merchant, information on the name of the menu, information on the number of the menu, information on the payment amount, information on the payment time, information on the number of the first code, and information on the second code.

5. In paragraph 1, A system in which the processing status of the above payment details includes at least one of an approval status, a pending status, and a cancellation status.

6. In paragraph 1, A system in which the final offline payment details include at least one of information about a transaction number, information about the number of the first code, information about a meal ticket number, information about a payment amount, information about a payment time, information about a management server registration date, information about a merchant name, and information about a payment details processing status.

7. In paragraph 1, The above complex payment terminal, A system that updates the offline payment details using one or more of the payment items.

8. In a method performed by a system for paying for electronic tickets, In case of communication failure, the process of scanning the first or second code and saving offline payment details; A process of determining the processing status of payment details using the above offline payment details and creating a final offline payment details using the processing status of the above payment details; The process of processing one or more payment items included in the final offline payment details; and A method comprising a process of updating the offline payment details using the one or more payment items.

9. In paragraph 8, The above second code is a method in which the user terminal generates a code using at least one of the user's company's unique number, the user's unique number, the generation time, and the encryption key.

10. In paragraph 8, The process of saving the above offline payment details is: A process of verifying the validity of the second code using at least one of the user's company's unique number, the user's unique number, the creation time, and the encryption key; and A method comprising a process of storing the offline payment details based on the validity of the second code.

11. In paragraph 8, A method wherein the offline payment details include at least one of information regarding payment approval, information regarding the number of the merchant, information regarding the menu name, information regarding the menu number, information regarding the number of menus, information regarding the payment amount, information regarding the payment time, information regarding the number of the first code, and information regarding the second code.

12. In paragraph 8, A method wherein the processing status of the above payment details includes at least one of an approval status, a pending status, and a cancellation status.

13. In paragraph 8, A method wherein the final offline payment details include at least one of information about a transaction number, information about the number of the first code, information about a meal ticket number, information about a payment amount, information about a payment time, information about a management server registration date, information about a merchant name, and information about a payment details processing status.

14. A computer-readable recording medium having stored thereon a command, wherein the command, when executed by the computer, causes the computer to: In case of communication failure, the process of scanning the first or second code and saving offline payment details; A process of determining the processing status of payment details using the above offline payment details and creating a final offline payment details using the processing status of the above payment details; The process of processing one or more payment items included in the final offline payment details; and A computer-readable recording medium that causes a process of updating the offline payment details using one or more of the above payment items.

Images