KR20230123196A - An apparatus and an system for payment, and a medium storing a program to run a method for payment - Google Patents

Abstract

According to one embodiment of the present invention, a medium recording a program for executing an apparatus, a system, and a method for payment of expenses is provided. The main service server according to an embodiment of the present invention includes a communication unit for communicating with a user terminal and an additional service server, a storage unit for storing setting information necessary for a transaction, and at least two or more approvals based on the setting information. and a control unit generating payment execution information for performing a complex payment including a request, and transmitting the payment execution information to the user terminal through the communication unit.

Description

An apparatus and an system for payment, and a medium storing a program to run a method for payment}

The present invention relates to a medium recording a program for executing a device, a system, and a method for receiving payment for supplying energy, such as oil or electricity, to a vehicle or the like.

In order to drive a vehicle, it is necessary to supply an energy source such as oil or electricity to the vehicle. Vehicle operators generally use various types of value-added services provided by operators that supply energy such as oil or electricity and/or separate operators contracted with these operators when paying for fuel costs. These additional services include accumulating points at a certain rate or amount for the payment amount, allowing points accumulated in advance to be used for payment, and paying fuel costs at a certain amount or rate by using a specific card or coupon. discounts, etc.

In the conventional case, a vehicle operator brought a payment card, a point card, a coupon, a discount card, etc., and then sequentially entered them in several stages to receive fueling or charging services and utilize additional services.

Republic of Korea Patent No. 10-1894074

According to one embodiment of the present invention, a medium for storing a program for executing an apparatus, system, and method that enables a person who pays for a fee, such as a vehicle operator, to more conveniently use an additional service related to the cost is provided.

According to one embodiment of the present invention, a medium for storing a program for executing a device, system, and method for more conveniently using various types of supplementary services is provided.

The objects of the present invention are not limited to the above-mentioned objects, and other objects and advantages of the present invention not mentioned above can be understood by the following description and will be more clearly understood by the examples of the present invention. It will also be readily apparent that the objects and advantages of the present invention may be realized by means of the instrumentalities and combinations indicated in the claims.

The main service server according to an embodiment of the present invention includes a communication unit for communicating with a user terminal and an additional service server, a storage unit for storing setting information necessary for a transaction, and at least two or more approvals based on the setting information. and a control unit generating payment execution information for performing a complex payment including a request, and transmitting the payment execution information to the user terminal through the communication unit.

According to one embodiment of the present invention, the approval request includes a credit card payment approval request, a point accumulation request, a point use approval request, a discount coupon use approval request, and a discount card application approval request. At least two of the requests may be included.

The communication unit of the main service server according to an embodiment of the present invention may communicate with the payment server.

When receiving information on the complex payment from the payment server, the control unit of the main service server according to an embodiment of the present invention transmits complex payment execution information for execution of the complex payment to the payment server through the communication unit. can do.

The control unit of the main service server according to an embodiment of the present invention generates modified complex payment execution information based on the actual transaction information when the payment information used for the complex payment execution information and the actual transaction information are different, and the Modified complex payment execution information may be transmitted to the payment server through the communication unit.

A payment server according to an embodiment of the present invention includes a communication unit communicating with a payment terminal, a main service server, and an additional service server, and payment information received from the payment terminal, including at least two approval requests. In case of payment information, a controller transmits the complex payment information to the main service server through the communication unit and processes the at least two or more approval requests based on complex payment execution information received from the main service server. .

When actual transaction information is received from the payment terminal, the controller of the payment server according to an embodiment of the present invention may transmit a request for retransmission of the complex payment execution information together with the actual transaction information to the main service server. .

The program of the medium storing the program according to an embodiment of the present invention sets setting information necessary for a transaction and stores it in a main service server, complex payment including at least two approval requests from the main service server. The step of receiving payment execution information for performing and the step of displaying the payment execution information may be executed by the control unit of the user terminal.

According to one embodiment of the present invention, the setting information includes at least two or more of information on the type of oil to be refueled, refueling amount, automatic use of points, automatic use of coupons, bonus card information, and payment card information. can do.

A payment system according to an embodiment of the present invention generates payment execution information for performing a complex payment including at least two or more approval requests, and a main service server for transmitting the payment execution information to a user terminal, and the user terminal A payment terminal that receives the payment execution information from and transmits payment information corresponding to the payment execution information, and a payment that receives the payment information and requests information for execution of the complex payment from the main service server. and a server, wherein the main service server transmits complex payment execution information for execution of the complex payment to a payment server in response to a request from the payment server, and the payment server transmits the complex payment execution information based on the complex payment execution information. Process at least two approval requests.

When the payment information and actual transaction information are different from each other, the payment terminal of the payment system according to an embodiment of the present invention may transmit the actual transaction information to the payment server.

The payment server of the payment system according to an embodiment of the present invention may transmit the actual transaction information to the main service server.

The main service server of the payment system according to an embodiment of the present invention may generate modified complex payment execution information based on the actual transaction information and transmit the modified complex payment execution information to the payment server.

According to a medium recording a program for executing an apparatus, system, and method for payment according to an embodiment of the present invention, a person who pays expenses, such as a vehicle operator, can more conveniently provide additional services related to expenses. available.

According to the media recording the program for executing the device, system, and method for payment according to an embodiment of the present invention, a person who pays for expenses, such as a vehicle operator, can more conveniently use various types of additional services. available.

In addition to the effects described above, specific effects of the present invention will be described together while explaining specific details for carrying out the present invention.

1 schematically illustrates a system including a device for payment according to an embodiment of the present invention.
2 is a block diagram schematically showing the configuration of an apparatus for payment according to an embodiment of the present invention.
FIG. 3 is an operation flow chart for explaining the operation of the main service server of the system shown in FIG. 1 .
FIG. 4 is an operational flowchart for explaining the operation of a user terminal of the system shown in FIG. 1 .
Each of FIGS. 5 to 10 is a diagram for explaining an operation of a user terminal of the system shown in FIG. 1 .
FIG. 11 is an operation flow chart for explaining the operation of the payment server of the system shown in FIG. 1 .
12 is a diagram for explaining a method for payment of expenses according to an embodiment of the present invention.

The above objects, features and advantages will be described later in detail with reference to the accompanying drawings, and accordingly, those skilled in the art to which the present invention belongs will be able to easily implement the technical spirit of the present invention. In describing the present invention, if it is determined that the detailed description of the known technology related to the present invention may unnecessarily obscure the subject matter of the present invention, the detailed description will be omitted. Hereinafter, preferred embodiments according to the present invention will be described in detail with reference to the accompanying drawings. In the drawings, the same reference numerals are used to indicate the same or similar components.

Although first, second, etc. are used to describe various components, these components are not limited by these terms, of course. These terms are only used to distinguish one component from another component, and unless otherwise stated, the first component may be the second component, of course.

In addition, when a component is described as "connected", "coupled" or "connected" to another component, the components may be directly connected or connected to each other, but other components may be "interposed" between each component. ", or each component may be "connected", "coupled" or "connected" through other components.

Throughout the specification, unless otherwise stated, each element may be singular or plural.

Singular expressions used herein include plural expressions unless the context clearly dictates otherwise. In this application, terms such as "consisting of" or "comprising" should not be construed as necessarily including all of the various components or steps described in the specification, and some of the components or some of the steps It should be construed that it may not be included, or may further include additional components or steps.

Throughout the specification, when it says "A and/or B", it means A, B or A and B, unless otherwise specified, and when it says "C to D", it means unless otherwise stated As long as there is no, it means C or more and D or less.

Hereinafter, a medium recording a program for executing a device, a system, and a method for payment according to some embodiments of the present invention will be described. In addition, hereinafter, a case of paying for oil fueled in a vehicle will be described as an example, but the present invention is not limited thereto. That is, the embodiment of the present invention can be used even when charging a vehicle with electricity and paying for it. Also, embodiments of the present invention may be used when paying for maintenance services for vehicles or when paying for other services or items.

1 schematically shows a system including a device for payment according to an embodiment of the present invention, the system according to an embodiment of the present invention includes a main service server 100, a user terminal 200, payment It may include a user terminal 300, a payment server 400, and an additional service server 500. The user terminal 200 may be a mobile terminal such as a smart phone.

The main service server 100 may store various types of user setting information based on information received from the user terminal 200 . The setting information may include direct refueling setting information and reserved refueling setting information. Each setting information includes information on the type of oil, information on the amount to be refueled, information on the amount of fuel to be refueled, information on whether points are automatically used, information on whether coupons are automatically used, information on bonus cards used for accumulation of points, etc. It may include at least one of information, information on a card capable of discounting fuel costs, and information related to a payment card.

The main service server 100 may transmit setting information to the user terminal 200 when the user terminal 200 accesses the main service server 100 .

The main service server 100 may generate payment execution information and transmit the generated payment execution information to the user terminal 200 . The payment execution information may have various forms such as a barcode form, a pin number form, and/or a QR code form.

In addition, the main service server 100 may receive complex payment information from the payment server 400 and transmit complex payment execution information for a plurality of approvals to the payment server 400 based on the received complex payment information. .

In addition, the main service server 100 may receive information (actual transaction information) on services and/or goods actually provided from the payment server 400 . The main service server 100 may receive actual transaction information when set payment information and actually performed transaction information are different. For example, the main service server 100 may receive information about the amount and/or amount of fuel actually refueled from the payment server 400 . At this time, when the information received from the payment server 400 is different from the setting information, the main service server 100 may modify the payment information and transmit the corrected payment information to the payment server 400 . For example, the main service server 100 recalculates at least one of the card payment amount, the point usage amount, and the coupon usage amount according to the amount of fuel actually refueled, and the payment information corrected according to the recalculated result is sent to the payment server. (400).

In addition, the main service server 100 may store information about the user's payment history (eg, fueling history) and transmit the information to the user terminal 200 .

In addition, the main service server 100 may access the payment server 400 and/or the additional service server 500 to obtain information about whether the user's service is valid or not. For example, the main service server 100 provides information related to the validity of the user's card, information about the accumulated amount of points of the user, information about whether the user has a coupon, information related to the validity of the coupon held by the user, and At least one piece of information related to the validity of the on-site discount card held may be acquired.

The user terminal 200 may store the above-described setting information according to a user's input. In addition, the user terminal 200 may transmit the setting information to the main service server 100 .

The user terminal 200 may provide payment execution information to the payment terminal 300 . The payment execution information may have various forms such as a barcode form, a pin number form, and/or a QR code form. The user terminal 200 may receive payment execution information from the main service server 100 and display the received payment execution information.

In addition, the user terminal 200 may display a plurality of setting information and transmit the setting information selected by the user to the main service server 100 . At this time, the main service server 100 may generate payment execution information based on setting information selected by the user and transmit the generated payment execution information to the user terminal 200 . Depending on the embodiment, the user terminal 200 may generate payment execution information.

In addition, the user terminal 200 may receive information on payment history (eg, information on refueling history) or information on individual receipts from the main service server 100 and display them.

The payment terminal 300 may receive the above-described payment execution information from the user terminal 200 . For example, the payment terminal 300 may receive payment execution information by reading a barcode or QR code displayed on the user terminal 200 . Alternatively, payment execution information may be received by inputting the pin number displayed on the user terminal 200 to the payment terminal 300 . The payment terminal 300 may transmit the input payment execution information to the payment server 400 . The payment terminal 300 may receive payment completion information (or gas approval information) indicating that payment has been completed from the payment server 400 . When the payment terminal 300 receives payment completion information (or fueling approval information), a gas pump or the like may be switched to a state in which fuel can be supplied to the vehicle.

The payment terminal 300 may transmit information (actual transaction information) on services or goods actually provided to the payment server 400 . For example, when fuel is supplied to the vehicle by a gas pump or the like, the payment terminal 300 may transmit information about the amount of fuel actually provided and/or the price of fuel to the payment server 400 . The payment terminal 300 may transmit actual transaction information to the payment server 400 when the previously approved payment information and actually provided information do not match.

The payment server 400 may receive payment execution information from the payment terminal 300 . In addition, when the received payment execution information is composite payment information in which several approvals are combined, the payment server 400 may transmit it to the main service server 100 . Complex payment information is, for example, at least two of payment information on the amount used through a credit card, information on the amount of point deduction and / or accumulated points by point card, use information such as coupons, discount information by on-site discount cards, etc. It may be information including one or more.

In addition, the payment server 400 may receive complex payment execution information from the main service server 100 and perform a function such as actual cost settlement according to the received complex payment execution information. For example, the payment server 400 may access the credit card company's server, request approval of the corresponding payment amount, and receive a reply as to whether or not the payment has been approved, based on the payment information of the amount used through the credit card. Alternatively, the payment server 400 accesses the supplementary service server 500 based on information about the point deduction amount and/or point accumulation amount by the point card, requests approval for point deduction and/or accumulation, etc., and determines whether or not it is approved. can receive a reply. In addition, the payment server 400 may transmit payment completion information (or gas approval information) to the payment terminal 300 when approval for cost and/or points is completed.

The payment server 400 may receive actual transaction information from the payment terminal 300 . Also, the payment server 400 may transmit actual transaction information to the main service server 100 . The payment server 400 may transmit the actual transaction information to the main service server 100 when the previously approved payment information differs from the actual transaction information. Thereafter, the payment server 400 may receive the corrected payment information from the main service server 100 and perform a cost settlement operation based on the corrected payment information. For example, the payment server 400 may cancel previously approved payment information and perform an operation for card payment, point deduction and/or accumulation based on the modified payment information.

The additional service server 500 includes at least one of various services related to the user's payment, such as card payment, user's point deduction and/or accumulation, user's use of coupons, and user's on-site discount service. It may be a server for providing. The supplementary service server 500 is the main service server 100, and transmits at least one or more of information about points owned by the user, information about coupons owned by the user, and information about on-site discount services available to the user to the main service. It can be provided to the server 100. In addition, the additional service server 500 provides at least one or more of additional services such as card payment, deduction of points owned by the user, additional accumulation of user points, and use of coupons owned by the user, according to the approval request of the payment server 400. can be done The additional service server 500 may include a plurality of servers.

Figure 2 schematically shows the configuration of a device for payment according to an embodiment of the present invention. The main service server 100, user terminal 200, payment terminal 300, payment server 400, and additional service server 500 of the system shown in FIG. 1 may have the same configuration as that shown in FIG. there is. An apparatus for payment of expenses according to an embodiment of the present invention may include a communication unit 610, a control unit 620, and a storage unit 630. Also, the device 600 shown in FIG. 2 may be an application server for transmitting a program for executing a method according to an embodiment of the present invention to the user terminal 200 .

The communication unit 610 may transmit a signal to the outside under the control of the control unit 620 . Also, the communication unit 610 may receive a signal from the outside and output the received signal to the controller 620 . The communication unit 610 may transmit and receive signals by wire and/or wirelessly. Communication unit 610 may include a modem, network interface card (NIC), integrated network interface, radio frequency transmitter/receiver, infrared port, USB connection, or other interface for communication with other computing devices.

The controller 620 may include at least one processing unit and/or memory. Here, the processing unit may include, for example, a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor, an Application Specific Integrated Circuit (ASIC), Field Programmable Gate Arrays (FPGA), and the like, It can have multiple cores. Memory 1218 may be volatile memory (eg, RAM, etc.), non-volatile memory (eg, ROM, flash memory, etc.), or a combination thereof.

Also, the controller 620 may include additional storage. Storage includes, but is not limited to, magnetic storage, optical storage, and the like. A program for implementing one or more embodiments described in this specification may be stored in the storage. The program may include at least one or more computer readable instructions. In addition, other computer readable instructions for implementing an operating system, an application program, and the like may also be stored in the storage. Programs stored in storage may be loaded into memory for execution by the processing unit.

Depending on the embodiment, the control unit 620 transfers a program for executing the method according to an embodiment of the present invention stored in the storage unit 630 to a mobile terminal (eg, the user terminal 200) through the communication unit 610. ) can be sent.

The storage unit 630 may store various information necessary for executing an embodiment of the present invention and/or a program for executing a method according to an embodiment of the present invention.

FIG. 3 is an operational flowchart for explaining the operation of the main service server 100 of the system shown in FIG. 1 . The main service server 100 may perform a setting step of storing setting information as a whole, an activation step for complex payment, and a payment execution step. Each step shown in FIG. 3 may be performed by a control unit (more specifically, a processing unit of the control unit) of the main service server 100 .

A program for performing each step shown in FIG. 3 may be stored in the storage unit of the main service server 100 . Programs stored in the storage may be loaded into the control unit to be executed by the control unit of the main service server 100 .

First, the main service server 100 may store setting information (step S110). The setting information is information set by the user, and may include frequently used payment information and/or reservation payment information to be performed at a specific time point. For example, the setting information may include direct fueling setting information for making payment for the type and amount of oil frequently used by the user more conveniently, and reserved fueling setting information for reserving the amount to be refueled at a specific time as a unit price for reservation. there is. When specifying a gas station to refuel, the reserved unit price may be a current unit price or a discounted unit price. The current unit price may be a unit price at the time of reservation. The discount unit price may be a unit price to which a discount service usable by the user, such as an on-site discount card or discount coupon, is applied. In the case of a discounted unit price, the time point at which the discount service can be applied may be a current time point or the specific time point. When a gas station to be refueled is not specified, the reserved unit price may be a mobile single unit price. The mobile single unit price may be an amount set by a service provider providing gas service using the main service server 100 . Depending on the embodiment, the user may select the most advantageous one among the current unit price, the discounted unit price, and the mobile single unit price. Step S110 may be performed by the main service server 100 receiving information from the user terminal 200 and storing the received information. Step S110 may correspond to the above-described setting step.

Next, the main service server 100 may check information necessary for payment (step S120). For example, the main service server 100 may receive information for additional services. The information for the additional service may include at least one of information about points owned by the user, information about coupons owned by the user, and information about discount cards owned by the user. Also, the main service server 100 may check information on a card to be used by the user. Information on the card to be used by the user may be information about the validity of the set card. Step S120 may be performed when the main service server 100 receives a service start request from the user terminal 100 . In addition, step S120 may be performed based on the setting information stored in step S110. At this time, the main service server 100 may be performed based on the setting information selected when there is a plurality of setting information.

Next, the main service server 100 may transmit setting information and/or payment execution information to the user terminal 200 (step S130). The payment execution information may include at least one form of a barcode form, a pin number form, and a QR code form. The payment execution information may be a combination of a plurality of approval requests. For example, the payment execution information may be a combination of at least two or more of a plurality of approval requests, such as credit card payment, deduction and/or accumulation of points, use of coupons, and application of discount cards.

Steps S120 and S130 may be the above-described activation steps.

Next, the main service server 100 may return complex payment information in response to the confirmation request for complex payment information (step S140). For example, the main service server 100 may receive a request for confirmation of complex payment information from the payment server 400 . The main service server 100 may transmit complex payment execution information capable of executing a plurality of approvals included in the complex payment information to the payment server 400 in response to a request of the payment server 400 .

Next, the main service server 100 may receive actual transaction information from the payment server 400 (step S160). The actual transaction information may be actual refueling information including an actual refueling amount.

Next, the main service server 100 may recalculate payment information based on actual transaction information and transmit the corrected payment information to the payment server 400 (step S170). In step S170, the main service server 100 may recalculate the discount amount by points, coupons, and/or discount cards to be deducted and/or accumulated based on the actual refueling amount.

Steps S160 and S170 may be performed only when the payment amount included in the setting information and the transaction amount included in the actual transaction information are different.

Steps S140 to S170 may correspond to the above-described payment execution steps.

FIG. 4 is an operation flowchart for explaining the operation of the user terminal 200 of the system shown in FIG. 1, and each of FIGS. 5 to 10 is a diagram for explaining the operation of the user terminal 200.

Similar to the main service server 100, the user terminal 200 may also perform a setting step of storing setting information as a whole, an activation step for complex payment, and a payment execution step. Each step shown in FIG. 4 may be performed by a control unit (more specifically, a processing unit of the control unit) of the user terminal 200 .

A program for performing each step shown in FIG. 4 may be stored in an application server. The user terminal 200 may download a program for performing each step shown in FIG. 4 from an application server. The downloaded program may be stored in the storage unit of the user terminal 200 . Programs stored in the storage may be loaded into the control unit to be executed by the control unit of the user terminal 200 .

First, the user terminal 200 may set information for payment (step S210). The setting information is information set by the user, and may include frequently used payment information and/or reservation payment information to be performed at a specific time point. Setting information may be stored in the user terminal 200 and/or the main service server 100 .

Referring to FIG. 5 , the user terminal 200 may directly set a pattern frequently used by the user as refueling setting information. More specifically, as shown in FIG. 5 (a), the user can set the type and amount of oil to refuel frequently. At this time, a nickname can be attached to the saved pattern. A plurality of immediately refueling setting information may be set. In addition, as shown in FIG. 5(b), it is possible to set whether points and/or coupons are automatically used. When set to automatic use, the main service server 100 may operate to settle at least a part of the payment amount through points and/or coupons according to the set contents. In addition, as shown in FIG. 5(c), bonus card information to be used can be set. A bonus card may be a card used for accumulation and/or deduction of points. In addition, as shown in FIGS. 5(d) and 5(e), a payment card and a payment password may be set. When setting for immediate fueling is completed, set information may be displayed on the user terminal 200 as shown in FIG. 5(f).

Referring to FIG. 6 , the user terminal 200 may set a refueling amount and a refueling amount based on the reserved unit price, and may set reserved refueling setting information for paying a refueling cost according to the set information. Reservation fueling is to allow the user to select a condition favorable to himself/herself between the time of reservation and the time of payment, and may be provided by a business operator to the user as an event benefit. As described above, the reserved unit price may be a current unit price, a discounted unit price, or a mobile single unit price. A selection range of the reserved unit price may be determined depending on whether or not a gas station is specified, and the user may select a unit price advantageous to the user among the above unit prices.

When the user selects reservation on the initial screen of FIG. 6 (a) and the user cannot set reserved fueling, the user terminal 200 may display that reservation fueling cannot be set as shown in FIG. 6 (b). and, when the user can set gas reservation, information on gas stations where reservation is possible can be displayed on the user terminal 200 as shown in FIG. 6(c) and/or FIG. 6(d). As shown in FIG. 6(c) and/or FIG. 6(d), after selecting a reserved gas station, a refueling amount may be set as shown in FIG. 6(e). Unlike FIG. 6(e), the refueling amount may be set. As described above, the unit price applied in this step may be one of a current unit price, a discounted unit price, and a mobile single unit price. Next, as shown in FIG. 6(f), reserved fueling setting information is displayed on the user terminal 200, and when reservation completion is selected, reserved fueling setting information can be set.

Also, as shown in FIG. 7 , the user terminal 200 may manage payment cards by performing operations such as adding/editing/deleting payment cards.

Step S210 of FIG. 4 and the process shown in FIGS. 5 to 7 may correspond to the above-described setting step.

Next, the user terminal 200 may receive the set information or select one of the set information (step S220). For example, the user terminal 200 may access the main service server 100 and receive set information. Also, the user terminal 200 may display information received from the main service server 100 . Depending on the embodiment, the user terminal 200 may display stored setting information. A user may select setting information displayed on the user terminal 200 .

8 illustrates an example of information displayed on the user terminal 200 in step S220. As shown in FIG. 8 (a), the user terminal 200 may directly display refueling setting information. As shown in FIG. 8( b ), the user may change the price of fuel setting information displayed on the user terminal 200 . At this time, the refueling setting information may be updated immediately according to the changed amount. In addition, as shown in FIG. 8(c), reserved fueling setting information may be displayed on the user terminal 200.

Next, the user terminal 200 may display payment execution information. As described above, the payment execution information may include at least one of a barcode form, a pin number form, and a QR code form.

9 is a diagram showing an embodiment of payment execution information displayed on the user terminal 200 when gas is selected directly in FIG. 8 (a), and FIG. It is a diagram showing an embodiment of payment execution information displayed on the user terminal 200 in this case.

Referring to FIGS. 9 and 10 (a) , payment execution information displayed on the user terminal 200 when refueling is selected includes payment and other discount details such as barcodes, pin numbers, coupons and/or point deduction details, and other discount details. A variety of related information may be included.

In addition, as shown in FIG. 10 (b), when the user selects reserved fueling, it is possible to check once again whether to cancel the reservation. At this time, the user terminal 200 may display the current unit price (ie, the unit price at the time of actual refueling when using the reserved gas service) and the unit price at the time of reservation (ie, the reserved unit price). That is, the user compares the current unit price with the unit price at the time of reservation, and if the current unit price is advantageous to the user, he or she can delete reserved fuel setting information and proceed with payment at the current unit price.

Depending on the embodiment, the main service server 100 may process the user through the user terminal 200 to prevent the user from selecting reserved refueling if the unit price at the time of reservation is higher than the current unit price.

Step S230 of FIG. 4 and the process shown in FIGS. 11 and 12 may correspond to the above-described activation step.

Next, the payment execution step is performed by the payment terminal 300 reading the payment execution information displayed on the user terminal 200 and transmitting it to the payment server 300, and the result is the user terminal 200 It can be displayed on (step S240). Step S240 may be the aforementioned payment execution step.

FIG. 11 is an operational flowchart for explaining the operation of the payment server 400 of the system shown in FIG. 1 . Each step shown in FIG. 10 may be performed by a control unit (more specifically, a processing unit of the control unit) of the payment server 400 .

A program for performing each step shown in FIG. 11 may be stored in the storage unit of the payment server 400 . Programs stored in the storage unit may be loaded into the controller of the payment server 400 to be executed by the controller.

First, the payment server 400 may receive payment information from the payment terminal 300 (step S310). The payment information may be information generated by the payment terminal 300 according to payment execution information displayed on the user terminal 200 . Payment information may include at least one payment approval request.

Next, the payment server 400 may determine whether the received payment information is complex payment information (step S320). For example, the payment server 400 may determine that the payment information received from the payment terminal 300 is complex payment information when it includes a predefined pattern or includes a plurality of payment approvals. there is.

As a result of the determination in step S320, if it is determined that the received payment information is not complex payment information, the payment server 400 may perform an operation for payment approval based on the received payment information (step S350). For example, the payment server 400 requests card payment approval from the additional service server 500 (eg, credit card approval server) based on the received payment information, and the additional service server 500 (eg, credit card approval server) For example, if approval completion is received from the credit card approval server), transaction approval information may be transmitted to the payment terminal 300 .

As a result of the determination in step S320, if it is determined that the received payment information is complex payment information, the payment server 400 may transmit the complex payment information to the main service server 100 and request execution information for the complex payment (S330). step).

Next, the payment server 400 may perform an operation for payment approval based on the complex payment execution information received from the main service server 100 (step S350). For example, the payment server 400 may access the additional service server 400 (eg, credit card approval server) and perform an operation for credit card payment approval. In addition, the payment server 400 may access the additional service server 400 (eg, a point card company server) to perform an operation for deducting and/or accumulating points. In addition, the payment server 400 may access the additional service server 400 (eg, coupon server) and perform an operation for using a discount coupon.

12 is a diagram for explaining a method for payment of expenses according to an embodiment of the present invention.

First, the user terminal 200 may request a service from the main service server 100 (step S401). Step S401 may be performed by selecting direct oiling in FIG. 8 (a) or selecting reserved oiling in FIG. 8 (c).

Next, the main service server 100 may check information necessary for payment based on the setting information (step S402). For example, the main service server 100 communicates with the additional service server 500, information on bonus points possessed by the user, information on discount coupons possessed by the user, and on-site discounts possessed by the user. Information on the card and information on the credit card to be used for payment by the user may be checked.

Next, the main service server 100 may generate payment execution information based on the information received in steps S401 and S402 and setting information, and transmit the generated payment execution information to the user terminal 200 ( Step S403). The payment execution information may include at least one of a barcode form, a QR code form, and a pin number form.

Next, the user terminal 200 may display payment execution information, and the payment terminal 300 may recognize the payment execution information by reading the payment execution information displayed on the user terminal 200 (step S404). .

Next, the payment terminal 300 may transmit payment information to the payment server 400 based on the recognized payment execution information (step S405).

Next, when the received payment information is complex payment information, the payment server 400 may request confirmation of the complex payment information to the main service server 100 (step S406). The payment server 400 may determine that the received payment information is complex payment information when a predetermined pattern or a plurality of approval requests are included in the received payment information. In step S406, if the received payment information is not complex payment information, the payment server 400 may process a payment request such as card approval included in the payment information.

Next, the main service server 100 may return complex payment execution information for executing complex payment information to the payment server 400 in response to a request from the payment server 400 (step S407). Complex payment execution information may include information on a plurality of approval processes related to payment, such as card payment, deduction and/or accumulation of bonus points, use of discount coupons, and application of on-site discount cards.

Next, the payment server 400 may perform an operation for processing a plurality of approvals based on the complex payment execution information received from the main service server 100 . For example, the payment server 400 may access the additional service server 400 (eg, credit card approval server) and perform an operation for credit card payment approval. In addition, the payment server 400 may access the additional service server 400 (eg, a point card company server) to perform an operation for deducting and/or accumulating points. In addition, the payment server 400 may access the additional service server 400 (eg, coupon server) and perform an operation for using a discount coupon.

Next, the payment server 400 may receive an approval completion from the additional service server 400 (step S409). Upon receiving an approval completion reply from the additional service server 400, the payment server 400 may transmit transaction approval information to the payment terminal 300 (step S410).

Although not shown, in step S410, the payment server 400 may transmit information on approval completion to the main service server 100, and the main service server 100 may transmit approval completion details to the user terminal 200. can Alternatively, the payment terminal 300 may transmit approval completion details to the user terminal 200 .

When transaction approval information is received in the payment terminal 300, an actual transaction may be made. For example, gas service may be performed.

At this time, approved existing payment information and actual transaction information may be different. For example, under-fueling, in which an amount of fuel is less than the fueling amount of the payment information, may occur.

When less than fueling occurs, the payment terminal 300 may transmit actual transaction information to the payment server 400 (step S411). At this time, the payment terminal 300 provides information on approved existing payment information and/or Alternatively, information indicating that under-fueling has occurred may also be transmitted to the payment server 400 .

In this case, the payment server 400 may request the main service server 100 to recalculate the complex payment information together with the actual transaction information (step S412).

The main service server 100 may recalculate complex payment information based on actual transaction information and previously stored setting information, and transmit modified complex payment execution information to the payment server 400 (step S413). . In this case, the main service server 100 may recalculate the deduction amount and/or accumulated amount of bonus points or the discount amount based on the actual transaction amount.

Next, the payment server 400 performs an operation for canceling an existing payment and processing a new payment based on the modified complex payment execution information received in step S413 (step S414), and processing from the additional service server 500. A reply about completion may be received (step S415). Steps S414 and S415 may be performed similarly to steps S408 and S409.

Upon receiving a reply about processing completion from the additional service server 500, the payment server 400 may transmit the processing result to the payment terminal 300 (step S416).

Although not shown, in step S416, the payment server 400 may transmit information about processing completion to the main service server 100, and the main service server 100 may transmit processing completion details to the user terminal 200. can Alternatively, the payment terminal 300 may transmit processing completion details to the user terminal 200 .

As described above, the payment terminal 300 may determine whether the approved existing payment information and the actual transaction information are different. However, unlike this, it may be determined whether the existing payment information approved by the main service server 100 or the payment server 400 is different from the actual transaction information.

As described above, the present invention has been described with reference to the drawings illustrated, but the present invention is not limited by the embodiments and drawings disclosed in this specification, and various modifications are made by those skilled in the art within the scope of the technical idea of the present invention. It is obvious that variations can be made. In addition, although the operational effects according to the configuration of the present invention have not been explicitly described and described while describing the embodiments of the present invention, it is natural that the effects predictable by the corresponding configuration should also be recognized.

100: main service server 200: user terminal
300: terminal for payment 400: payment server
500: Additional service server

Claims (14)

A communication unit that performs communication with a user terminal and an additional service server;
a storage unit for storing setting information necessary for a transaction; and
Based on the setting information, a main service including a control unit generating payment execution information for performing a complex payment including at least two or more approval requests, and transmitting the payment execution information to the user terminal through the communication unit. server.
The method of claim 1, wherein the approval request
A main service server including at least two of an approval request for credit card payment, an approval request for point accumulation, an approval request for point use, an approval request for discount coupon use, and an approval request for discount card application.
According to claim 1,
The communication unit performs communication with the payment server,
The main service server, wherein the control unit transmits complex payment execution information for execution of the complex payment to the payment server through the communication unit when receiving information on the complex payment from the payment server.
The method of claim 1, wherein the controller
When the payment information used for the complex payment execution information is different from the actual transaction information, modified complex payment execution information is generated based on the actual transaction information, and the modified complex payment execution information is transmitted to the payment server through the communication unit. main service server.
a communication unit communicating with a terminal for payment, a main service server, and an additional service server; and
When the payment information received from the payment terminal is complex payment information including at least two approval requests, the complex payment information is transmitted to the main service server through the communication unit, and received from the main service server. A payment server comprising a control unit for processing the at least two or more approval requests based on complex payment execution information.
The method of claim 5, wherein the approval request
A payment server including at least two of an approval request for credit card payment, an approval request for point accumulation, an approval request for point use, an approval request for discount coupon use, and an approval request for discount card application.
The method of claim 5, wherein the control unit
When actual transaction information is received from the payment terminal, the payment server transmits a request for retransmission of the complex payment execution information together with the actual transaction information to the main service server.
Setting the setting information necessary for the transaction and storing it in the main service server;
Receiving payment execution information for performing a complex payment including at least two or more approval requests from the main service server; and
A medium recording a program for causing a control unit of a user terminal to execute the displaying of the payment execution information.
The method of claim 8, wherein the approval request is
A medium recording a program including at least two of a credit card payment approval request, a point accumulation request, a point use approval request, a discount coupon use approval request, and a discount card application approval request. .
The method of claim 8, wherein the setting information
A medium on which a program is recorded including at least two of information on the type of oil to be refueled, fuel amount, automatic use of points, automatic use of coupons, bonus card information, and payment card information.
A main service server generating payment execution information for performing a complex payment including at least two approval requests and transmitting the payment execution information to a user terminal;
a payment terminal receiving the payment execution information from the user terminal and transmitting payment information corresponding to the payment execution information; and
A payment server for receiving the payment information and requesting information for execution of the complex payment from the main service server;
The main service server transmits complex payment execution information for execution of the complex payment to a payment server in response to a request from the payment server,
The payment server processes the at least two or more approval requests based on the complex payment execution information.
12. The method of claim 11, wherein the approval request is
A payment system including at least two of an approval request for credit card payment, an approval request for point accumulation, an approval request for point use, an approval request for discount coupon use, and an approval request for discount card application.
The method of claim 11, wherein the payment terminal
When the payment information and the actual transaction information are different, the payment system transmits the actual transaction information to the payment server.
According to claim 13,
The payment server transmits the actual transaction information to the main service server,
The main service server generates modified complex payment execution information based on the actual transaction information, and transmits the modified complex payment execution information to the payment server.

Images