KR20200038073A - Method and system for managing payment based on expected amount of service - Google Patents

Abstract

Provided is a payment management method and a payment management system based on a service estimated amount. The present invention can provide a service if payment with regard to the service estimated amount can be made by determining the service estimated amount before the service proceeds, and pre-approving the service estimated amount with a payment means registered by a user. Therefore, an occurrence of an outstanding amount after the service progresses can be reduced through this process.

Description

Payment management method and payment management system based on the estimated service amount {METHOD AND SYSTEM FOR MANAGING PAYMENT BASED ON EXPECTED AMOUNT OF SERVICE}

The present invention relates to a payment management method and a payment management system based on an estimated service amount, and more particularly, to a method and system for pre-establishing a service in advance after estimating a cost that may occur when the service is in progress. .

As various payment methods have been recently introduced, a method of receiving a service after registering a payment method in advance has been used. In this case, the user can perform payment more conveniently because there is no need to present a payment method every time or enter information of the payment method every time.

However, in the case of a service provider performing the service directly, if the user has a problem with the validity of the payment method after receiving the service, there may be a receivable for the progress of the service. Because, for the convenience of the service, the user leaves the service immediately after receiving the service, but in reality, the payment needs to be finally processed with the payment method registered by the user. If there is a problem with the validity of the payment method, even if the service is completed, There is a problem that accounts receivable occurs.

Therefore, in the method of providing such a service, there is a need for a payment method of reducing the amount of receivable or not generating the receivable.

The present invention provides a method and system for providing a service when approved as a service estimated amount by determining a service expected amount before providing a requested service from a user and paying in advance for the service estimated amount.

The present invention provides a method and system for using various service details to minimize a difference from a determined service amount determined after actually performing a service in determining an estimated service amount.

The present invention provides a method and system for variously presenting a process of final payment with a service confirmation amount generated by a user receiving a service after pre-approving the service schedule amount.

Payment management method performed by the payment management server according to an embodiment of the present invention comprises the steps of receiving a request to provide a service from a user terminal; Determining an estimated service amount based on service detailed information included in the provision request; Forwarding a request for approval to proceed with a service including the estimated service amount to a financial server; And informing a user terminal whether to provide a service according to the approval result received from the financial server.

The estimated service amount may be determined differently based on a service providing time, a service providing location, and a service providing type included in service detailed information input from the user terminal.

The financial server may determine whether the payment method registered in the user terminal can be paid with the estimated service amount included in the approval request, and the approval result may indicate whether payment is possible with the payment method.

A payment management method performed by a payment management server according to an embodiment of the present invention includes receiving a service confirmation amount for a service requested by a user terminal from a service provider terminal; Delivering a request to cancel approval of the estimated service amount for the service to a financial server; Transmitting a request for approval of the service confirmation amount for the service to the financial server; Receiving an approval result for a service confirmation amount from the financial server; And providing a notification of completion of the service including the approval result to the user terminal.

The estimated service amount may be determined differently based on a service providing time, a service providing location, and a service providing type included in service detailed information input from the user terminal.

The service may be performed when the payment is possible for the estimated service amount at the financial server and the approval is successful.

A payment management method performed by a payment management server according to another embodiment of the present invention includes receiving a service confirmation amount for a service requested by a user terminal from a service provider terminal; Comparing a service expected amount and a service determined amount for the service; If the estimated service amount is greater than the determined service amount, transmitting a request for cancellation of approval to the financial server for a difference between the estimated service amount and the determined service amount; If the service confirmation amount is greater than the service expected amount, the user is notified of the completion of the service including the step of forwarding an additional approval request to the financial server for the difference between the service confirmation amount and the expected service amount, and the approval result received from the financial server. It may include the step of providing to the terminal.

The estimated service amount may be determined differently based on a service providing time, a service providing location, and a service providing type included in service detailed information input from the user terminal.

The service may be performed when the payment is possible for the estimated service amount at the financial server and the approval is successful.

A payment management server performing a payment management method according to an embodiment of the present invention includes a processor, and the processor receives a request to provide a service from a user terminal, and based on service detailed information included in the provision request , It is possible to determine the estimated service amount, deliver an approval request for the progress of the service including the estimated service amount to the financial server, and notify the user terminal whether to provide the service according to the approval result received from the financial server.

The estimated service amount may be determined differently based on a service providing time, a service providing location, and a service providing type included in service detailed information input from the user terminal.

The financial server may determine whether payment is possible with the estimated service amount included in the authorization request for the payment method registered in the user terminal, and the approval result may indicate whether payment is possible with the payment method.

A payment management server performing a payment management method according to an embodiment of the present invention includes a processor, and the processor receives a service determination amount for a service requested by a user terminal from a service provider terminal, and services for the service A service that delivers a request to cancel the approval of the estimated amount to a financial server, sends a request to proceed with approval of a service determination amount for the service to the financial server, receives an approval result for the service determination amount from the financial server, and includes the approval result The progress completion notification of may be provided to the user terminal.

The estimated service amount may be determined differently based on a service providing time, a service providing location, and a service providing type included in service detailed information input from the user terminal.

The service may be performed when the payment is possible for the estimated service amount at the financial server and the approval is successful.

A payment management server performing a payment management method according to an embodiment of the present invention includes a processor, and the processor receives a service determination amount for a service requested by a user terminal from a service provider terminal, and services for the service Compares the expected amount and the determined service amount, and if the estimated service amount is greater than the determined service amount, a request for cancellation of approval is transmitted to the financial server for a difference between the estimated service amount and the determined service amount, and if the determined service value is greater than the expected service amount, the service An additional approval request may be transmitted to the financial server for the difference between the determined amount and the planned service amount, and a notification of completion of the service including the approval result received from the financial server may be provided to the user terminal.

The estimated service amount may be determined differently based on a service providing time, a service providing location, and a service providing type included in service detailed information input from the user terminal.

The service may be performed after the approval of the estimated service amount in the financial server is completed.

According to an embodiment of the present invention, it is possible to reduce the incidence of accounts receivable by providing a service when the service estimate is approved by determining a service estimate amount and paying for the service estimate amount before providing the requested service from the user.

According to an embodiment of the present invention, in determining the estimated service amount, it is possible to reduce the occurrence of the receivable by using various service detailed information in order to minimize the difference from the determined service amount determined after the actual service is performed.

According to an embodiment of the present invention, a process of final payment with a service settlement amount generated by a user receiving a service after pre-approving the service schedule amount may be variously presented.

1 is a view showing the overall structure of a payment management system according to an embodiment of the present invention.
2 is a flowchart showing a process before proceeding with a service according to an embodiment of the present invention.
3 is a flowchart illustrating a process for approving a service confirmation amount according to an embodiment of the present invention.
4 is a flowchart illustrating a process for approving a service confirmation amount according to another embodiment of the present invention.
5 is a diagram illustrating an example of an interface of a user terminal that provides an estimated service amount before performing a service according to an embodiment of the present invention.
FIG. 6 is a diagram illustrating an example of an interface of a user terminal showing a final payment process according to a service determination amount after performing a service according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a view showing the overall structure of a payment management system according to an embodiment of the present invention.

Referring to FIG. 1, a payment management system may include a user terminal 101, a payment management server 102, a financial server 103, and a service provider terminal 104.

The user terminal 101 may register payment means, such as a credit card, bank account, or virtual money, with the payment management server 102 to use the service performed by the service provider. Here, the financial server 103 may vary depending on the payment method registered by the user.

The service provided by the service provider in the present invention may include a taxi call service, a surrogate driving call service, a parking lot service, and the like. The service referred to in the present invention may generate a difference between the estimated service amount and the determined service amount, and may be possible as long as the user pre-registers a payment method for payment for the use of the service. Here, the estimated service amount means an amount that is expected to be generated after the service is performed based on information provided by the user or information set by the service provider before the user is actually provided with the service. For example, when the service is a taxi paging service, the estimated service amount may mean a taxi cost corresponding to a distance between a user's designated origin and destination.

In addition, the service confirmation amount means an amount actually generated while the user provides the service after the user actually receives the service. For example, when the service is a taxi calling service, it means a taxi cost incurred until the user finally arrives. At this time, due to a vehicle congestion or an accident, the determined service amount may increase more than the expected service amount.

According to an embodiment of the present invention, before the service provider proceeds with the service, the service estimated amount is determined according to the detailed information of the service requested by the user, and when the authentication is successful with the payment method registered by the user, the service will proceed. You can. At this time, it is necessary to minimize the difference between the estimated service amount and the service determination amount after the service is performed according to detailed information of the service set by the user.

In the related art, before proceeding with the service, simply check whether there is a payment method, or whether the payment method can be approved for a minimum cost, and an uncollected amount is generated because payment cannot be performed for the amount generated after the service actually proceeds. In the case of the present invention, the present invention determines the maximum service estimate that can be generated according to the detailed information of the service requested by the user, and approves the total amount of the service estimate in advance, so that payment is made for the costs incurred after the service is performed. You can minimize the amount of receivables that cannot be made.

The processing of the payment management method of the present invention will be described in detail in the following drawings.

2 is a flowchart showing a process before proceeding with a service according to an embodiment of the present invention.

In step 201, the user terminal 101 may deliver a service provision request to the payment management server 102. At this time, the service providing request may include service detailed information. For example, the service detailed information may include a service providing time, a service providing location, and a service providing type included in service information input from a user terminal.

For example, if the service is a taxi paging service, the service details include (i) the request time of the service, (ii) the taxi route (origin and destination), and (iii) the type of taxi (general, exemplary, advanced, Large size, etc.), (iv) additional information (such as whether to use a function to call a taxi by adding an additional fee (ex. Smart call), whether to use an additional toll such as whether to use a toll road, etc.).

And, if the service is a surrogate operation call service, the service details include (i) the service request time, (ii) the route for the surrogate operation (departure and destination, stopover), and (iii) the surrogate operation range (Seoul, Gyeonggi, Incheon, etc.).

In addition, if the service is a parking lot service, the service detailed information may include (i) the request time of the service related to the parking lot usage time (1 hour, 2 hours, etc.), (ii) parking lot information, (iii) the type of vehicle, etc. You can.

In step 202, the payment management server 102 may determine the estimated service amount based on the service detail information.

For example, the service estimate amount may be determined adaptively according to the service detail information input by the user or may be determined by the maximum cost arbitrarily set by the payment management server 102 regardless of the service detail information input by the user. The estimated service amount may be determined in a fixed form or in a range between the minimum amount and the maximum amount.

When the service is a taxi paging service, a movement method and a travel time are determined according to a travel route through a taxi origin and a destination, and an estimated service amount can be determined according to the result. At this time, even if the origin and destination are the same, whether a discount coupon is used, whether the discount is applied according to the user's class, whether a toll road is used in the travel route, a stopover is added to the driving route, or the type of taxi ( General, advanced, best, etc.), whether the service route is in the city / intercity premium area, whether additional options (ex. Smart calls) are applied, the degree of traffic congestion in the service route, the service request time is The estimated service amount may be different depending on whether it is work time or late night premium.

If the service is a proxy call service, even if the user's origin and destination are the same, the discount coupon is used, the user is applied to the discount according to the user's class, whether the toll road is used on the travel route, or the waypoint on the driving route The estimated service amount may be different depending on whether it is added or whether it moves to an area (regional areas such as the Seoul area and the metropolitan area) where the fare section is different.

When the service is a parking lot service, even if the parking time is the same in the same parking lot, the estimated service amount may be differently determined according to whether a discount coupon is used, a user who applies a discount according to the user's level, whether it is a weekday / holiday, and the like.

In step 203, the payment management server 102 may deliver a request for approval for the estimated service amount to the financial server 103 corresponding to the payment method registered in the user terminal 101. Here, the meaning of approval may be set differently for each type of payment method. For example, if the payment method is a credit-based payment rather than an immediate payment such as a credit card, approval means determining whether the credit limit is greater than the estimated service amount. And, if the payment method is an immediate payment, such as a check card, virtual money, bank account, etc., approval means determining whether the amount currently held in the payment method is greater than the estimated service amount.

In step 204, the financial server 103 may determine whether approval is possible for the estimated service amount.

If the estimated service amount cannot be approved by the payment method registered in the user terminal 101, in step 205, the financial server 103 may transmit a non-approval notification to the payment management server 102. Then, in step 206, the payment management server 102 may deliver a service disabling notification to the user terminal 101 along with a result of disapproval of the estimated service amount.

If it is possible to approve the estimated service amount by the payment method registered in the user terminal 101, in step 207, the financial server 103 may perform approval for the estimated service amount. At this time, the estimated service amount is pre-approved before the service proceeds. According to the present invention, it is confirmed that the payment method can be paid as much as the estimated service amount as well as the validity of the payment method registered in the user terminal 101 by determining whether to approve the service estimated amount to be generated when the service is actually used. .

Then, in step 208, the financial server 103 may deliver the approval result (approval completed) notification for the estimated service amount to the payment management server 102. In step 209, the payment management server 102 may transmit a notification to the user terminal 101 that the service is provided. To this end, the payment management server 102 may broadcast whether a service can be performed to a plurality of service providers who will provide the service.

3 is a flowchart illustrating a process for approving a service confirmation amount according to an embodiment of the present invention.

In step 301, the service provider terminal 104 may deliver a service provision notification to the payment management server 102.

Here, the service provider terminal 104 may mean a taxi driver terminal performing a taxi call service, a proxy driver terminal performing a proxy driving service, and a parking lot management terminal providing a parking lot service.

Here, the service provision notification may be a notification when a service is available because approval is possible for the estimated service amount, or a notification after the service is actually provided. For example, when the service is a taxi call service, the service provision notification may mean that a taxi driver is assigned and a taxi call is successful, or a user actually boards and gets off the taxi after the taxi call.

In step 302, the payment management server 102 may deliver a request for cancellation of the approval of the estimated service amount performed in FIG. 2 to the financial server 103. As described above, the request to cancel the approval of the estimated service amount may proceed when the approval of the estimated service amount is successful or may be performed when the service is actually performed and completed.

In step 303, the financial server 103 may perform an authorization cancellation with the payment method registered by the user with respect to the estimated service amount already pre-approved.

On the other hand, in step 304, the payment management server 102 may deliver a request to proceed to the approval of the service determination amount that is finally determined after the service is completed to the financial server 103. At this time, the service confirmation amount may be the same as or different from the expected service amount.

Then, in step 305, the financial server 103 may perform the approval process with the payment method registered by the user for the service confirmation amount.

In step 306, the financial server 103 may determine whether approval is possible with the payment method registered by the user for the service confirmation amount. At this time, the service determination amount may be larger or smaller than the expected service amount.

If the service settlement amount is greater than the service prediction amount and the service settlement amount is not approved by the payment method pre-approved as the service prediction amount, in step 307, the financial server 103 may again approve the service prediction amount. In this case, the approval actually means a process that proceeds to payment using a payment method. Thereafter, the financial server 103 may transmit a notification to the payment management server 102 that the approval has progressed with the estimated service amount.

In addition, there may be a case in which the settlement amount of the service is smaller than the estimated service amount, and approval for the determined service amount is not possible using a payment method pre-approved as the estimated service amount. In addition, there may be a case in which the confirmation amount of the service is larger than the expected value of the service, and approval is not possible as the expected value of the service. This may occur when a user performs payment for a service irrelevant to a service that is pre-approved for an estimated service amount as a payment method, and the credit limit or balance of the payment method is smaller than the expected service amount.

Then, it may not be possible to re-approve the estimated service amount with a pre-approved payment method for the estimated service amount. At this time, the financial server 103 may perform the re-approval of the service confirmation amount using a payment method different from the payment method that approved the estimated service amount. Here, the payment means that approves the estimated service amount and the other payment means means a payment method that the user has registered in advance to perform the service. If the service settlement amount cannot be approved using a payment method different from the payment method that approved the service estimation amount, the financial server 103 may perform re-approval with the other payment method for the service estimation amount. In this case, the payment management server 102 may notify that the authorization has been generated as the service confirmation amount or the service estimate amount by another payment method previously registered by the user.

In step 308, the payment management server 102 may inform the service provider terminal 104 that the number of attempts has been generated by the difference between the service determination amount and the service estimate amount. Then, in step 309, the payment management server 102 can inform the user terminal 101 that the service has been completed, and that the service has been approved by the estimated service amount and the number of attempts by the difference between the service confirmation amount and the service prediction amount has occurred. have. In addition, the payment management server 102 may provide a notification to the user terminal 101 that the future use of the service is not possible due to some attempts.

On the other hand, in step 306, if the approval is possible for the service determination amount, in step 310, the financial server 103 may proceed with the approval for the service determination amount. Subsequently, in step 311, the payment management server 102 may provide the service provider terminal 104 with a notification that the approval for the service settlement amount is completed. In addition, in step 312, the payment management server 102 may provide the user terminal 101 with a notification that the service is completed along with an approval completion notification for the service confirmation amount.

3 shows a process of finally paying for a service provided by a user by canceling the pre-approval of the estimated service amount pre-approved by the payment method registered through the user terminal 101 and then re-approving the service confirmation amount.

4 is a flowchart illustrating a process for approving a service confirmation amount according to another embodiment of the present invention.

Unlike FIG. 3, FIG. 4 illustrates a process after the service is provided without canceling approval for the estimated service amount.

In step 401, the service provider terminal 104 may deliver a service provision completion notification to the payment management server 102. Here, the service provider terminal 104 may mean a taxi driver terminal performing a taxi call service, a proxy driver terminal performing a proxy driving service, and a parking lot management terminal providing a parking lot service.

In step 402, the payment management server 102 may compare the service confirmation amount with the service estimate amount. If the service confirmation amount is greater than the service prediction amount, in step 403, the payment management server 102 may request the financial server 103 to approve the difference between the service determination amount and the service prediction amount. In step 403, the financial server 103 may determine whether additional approval is possible as a payment method for the difference between the service confirmation amount and the service prediction amount.

If, in step 403, additional approval is possible for the difference between the service commitment and the service estimate, in step 404, the financial server 103 may proceed with additional approval as much as the difference between the service commitment and the service estimate. Then, in step 405, the financial server 103 may deliver a result notification for additional approval by the difference between the service confirmation amount and the service estimate amount to the payment management server 102. In step 406, the payment management server 102 may deliver a result notification for additional approval by the difference between the service confirmation amount and the service prediction amount to the service provider terminal 104.

However, if it is impossible to further approve the difference between the service confirmation amount and the service prediction amount in step 403, in step 411, the financial server 103 may perform the approval process for the service estimate amount. Thereafter, in step 412, the financial server 103 may deliver the approval result notification that the approval has been finally processed for the estimated service amount to the payment management server 102. In step 413, the payment management server 102 may deliver an approval result notification to the service provider terminal 104 along with the content that additional approval is not possible as much as the difference between the service confirmation amount and the service prediction amount.

On the other hand, in step 402, if the estimated service amount is greater than the determined service amount, in step 407, the payment management server 102 may request approval cancellation by the difference between the estimated service amount and the estimated service amount to the financial server 103. Then, in step 408, the financial server 103 may perform approval cancellation by the difference between the estimated service amount and the estimated service amount. Thereafter, in step 409, the financial server 103 may deliver the notification of the result of the cancellation of the approval to the payment management server 102 by the difference between the estimated service amount and the determined service amount. In step 410, the payment management server 102 may deliver the notification of the result of the cancellation of the approval to the service provider terminal 104 by the difference between the estimated service amount and the estimated service amount.

In addition, in step 402, if the estimated service amount is greater than the determined service amount, in step 407, the payment management server 102 sets the service confirmation amount together with the cancellation of the entire approval to the previously estimated service estimate amount in the financial server 103. You can request full approval. Then, in step 408, the financial server 103 may cancel the entire approval for the pre-approved service estimate, and then approve the service confirmation amount again. Thereafter, in step 409, the financial server 103 may deliver the entire approval cancellation for the pre-approved service estimate and the overall approval for the service confirmation amount to the payment management server 102. In step 410, the payment management server 102 may deliver a notification of the result of the entire approval for the service approval amount and the cancellation of the entire approval for the estimated service amount pre-approved to the service provider terminal 104.

When the above process is completed, in step 414, the payment management server 102, along with the service completion notification, displays the additional approval result performed in step 404 and the result of partial approval cancellation performed in step 408, the user terminal 101 ). In addition, in step 415, the payment management server 102 transmits a notification that a partial attempt has occurred and a service unavailable notification to the user terminal 101 in the future along with the final approval result for the estimated service amount in step 411. You can.

FIG. 4 shows the service provided by the user by performing additional approval or partial cancellation of approval as a difference between the estimated service amount and the estimated service amount without canceling the pre-approval of the estimated service amount pre-approved by the payment method registered through the user terminal 101. Finally, it shows the process of payment.

5 is a diagram illustrating an example of an interface of a user terminal that provides an estimated service amount before performing a service according to an embodiment of the present invention.

Referring to (A) of FIG. 5, a service application performed in the user terminal 101 may provide an interface for inputting service detailed information for a service requested by a user. The user can input detailed service information through the corresponding interface. Then, the user can make a request to proceed with the service.

Referring to (B) of FIG. 5, a service application performed in the user terminal 101 may provide an estimated service amount that may occur when a user is provided with a service according to service detailed information. The user can make a request to proceed with the service by referring to the estimated service amount. At this time, the interface related to the service progress request may be displayed only when the pre-approval has been made for the estimated service amount. If the service estimated amount is not paid by the payment method registered through the user terminal 101 through the pre-approval, the corresponding interface is It may be marked as unavailable.

Referring to (C) of FIG. 5, a service application performed in the user terminal 101 may provide an interface indicating service progress along with service information guidance. For example, when the service is a taxi paging service, the service information guide may include various information related to the service, such as a taxi driver's name, photo, taxi vehicle number, expected arrival time, and departure and destination. And, the service progress may include the current travel route, the current location, and the like of the taxi.

FIG. 6 is a diagram illustrating an example of an interface of a user terminal showing a final payment process according to a service determination amount after performing a service according to an embodiment of the present invention.

Referring to (A) of FIG. 6, a service application performed in the user terminal 101 may display an interface indicating service information guidance and service progress as shown in FIG. 5C.

If the service is completed by the service provider, the service confirmation amount may be displayed as shown in FIG. 6 (B).

Then, as shown in (C) of FIG. 6, the service completion guide may be displayed on the user terminal 101 along with the approval result guide considering the service determination amount. Here, the approval result guidance is: (i) the difference between the service confirmation amount and the service prediction amount in the situation where the prior approval for the estimated service amount is canceled and the approval result guide for the total amount of the service confirmation amount is maintained or (ii) the pre-approval for the service estimate amount is maintained. In some cases, it may include guidance on approval results reflecting the results of additional approvals or partial cancellations.

On the other hand, the method according to the present invention can be implemented in various recording media such as a magnetic storage medium, an optical reading medium, and a digital storage medium by writing a program executable on a computer.

Implementations of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or combinations thereof. Implementations are computer program products, ie, information carriers, eg machine readable storage, for processing by, or controlling, the operation of a data processing apparatus, eg a programmable processor, a computer, or multiple computers. It may be embodied as a computer program embodied tangibly in a device (computer readable medium) or a radio wave signal. Computer programs, such as the computer program (s) described above, may be written in any form of programming language, including compiled or interpreted languages, and as a standalone program or in a module, component, subroutine, or computing environment. It can be deployed in any form, including as another unit suitable for use. A computer program can be deployed to be processed on one computer or multiple computers at one site or distributed across multiple sites and interconnected by a communication network.

Processors suitable for processing a computer program include, by way of example, both general purpose and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, the processor will receive instructions and data from read-only memory or random access memory or both. Elements of a computer may include at least one processor executing instructions and one or more memory devices storing instructions and data. In general, a computer may include one or more mass storage devices that store data, such as magnetic, magneto-optical disks, or optical disks, or receive data from or transmit data to them, or both. It may be combined as possible. Information carriers suitable for embodying computer program instructions and data include, for example, semiconductor memory devices, eg, magnetic media such as hard disks, floppy disks, and magnetic tapes, compact disk read only memory (CD-ROM). ), Optical Media such as DVD (Digital Video Disk), Magnetic-Optical Media such as Floptical Disk (Magneto-Optical Media), ROM (ROM, Read Only Memory), RAM (RAM) , Random Access Memory), Flash memory, Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EPMROM), and the like. The processor and memory may be supplemented by, or incorporated in, special purpose logic circuitry.

In addition, the computer-readable medium can be any available medium that can be accessed by a computer, and can include both computer storage media and transmission media.

This specification includes details of many specific implementations, but these should not be understood as limiting on the scope of any invention or claim, but rather as a description of features that may be specific to a particular embodiment of a particular invention. It should be understood. Certain features that are described in this specification in the context of separate embodiments may be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable subcombination. Further, although features may operate in a particular combination and may be initially depicted as so claimed, one or more features from the claimed combination may in some cases be excluded from the combination, and the claimed combination subcombined. Or sub-combinations.

Likewise, although the operations are depicted in the drawings in a particular order, it should not be understood that such operations should be performed in the particular order shown or in sequential order, or that all shown actions should be performed in order to obtain desirable results. In certain cases, multitasking and parallel processing may be advantageous. In addition, the separation of various device components of the above-described embodiments should not be understood as requiring such separation in all embodiments, and the described program components and devices will generally be integrated together into a single software product or packaged in multiple software products. You should understand that you can.

On the other hand, the embodiments of the present invention disclosed in the specification and drawings are merely presented as specific examples to aid understanding, and are not intended to limit the scope of the present invention. It is apparent to those skilled in the art to which the present invention pertains that other modified examples based on the technical idea of the present invention can be implemented in addition to the embodiments disclosed herein.

Claims (19)

In the payment management method performed by the payment management server,
Receiving a request to provide a service from a user terminal;
Determining an estimated service amount based on service detailed information included in the provision request;
Forwarding a request for approval to proceed with a service including the estimated service amount to a financial server;
Informing the user terminal whether to provide a service according to the approval result received from the financial server
Payment management method comprising a. According to claim 1,
The estimated service amount is
A payment management method that is determined differently based on a service provision time, a service provision location, and a service provision type included in service details input from the user terminal. According to claim 1,
The financial server,
It is determined whether the payment method registered in the user terminal can be paid with the estimated service amount included in the approval request,
The approval result,
A payment management method indicating whether payment is possible with the payment method. In the payment management method performed by the payment management server,
Receiving a service confirmation amount for the service requested by the user terminal from the service provider terminal;
Delivering a request to cancel approval of the estimated service amount for the service to a financial server;
Transmitting a request for approval of the service confirmation amount for the service to the financial server;
Receiving an approval result for a service confirmation amount from the financial server;
Providing a notification of the completion of the service including the approval result to the user terminal
Payment management method comprising a. According to claim 4,
The estimated service amount is
A payment management method that is determined differently based on a service provision time, a service provision location, and a service provision type included in service details input from the user terminal. According to claim 4,
The service,
Payment management method that proceeds when the payment is successful by the payment method registered in advance with respect to the estimated service amount in the financial server. In the payment management method performed by the payment management server,
Receiving a service confirmation amount for the service requested by the user terminal from the service provider terminal;
Comparing a service expected amount and a service determined amount for the service;
If the estimated service amount is greater than the determined service amount, transmitting a request for cancellation of approval to the financial server for a difference between the estimated service amount and the determined service amount;
If the service confirmation amount is greater than the service expected amount, forwarding an additional approval request to the financial server for the difference between the service confirmation amount and the planned service amount.
Providing a notification of the completion of the service including the approval result received from the financial server to the user terminal
Payment management method comprising a. The method of claim 7,
The estimated service amount is
A payment management method that is determined differently based on a service provision time, a service provision location, and a service provision type included in service details input from the user terminal. The method of claim 7,
The service,
Payment management method that proceeds when the payment is possible with the payment method registered in advance for the estimated service amount in the financial server, and the service is successfully approved as a payment method. In the payment management server performing a payment management method,
The payment management server includes a processor,
The processor,
Receiving a request to provide a service from a user terminal,
Based on the service details included in the offer request, the service estimate is determined,
A request for approval to proceed with a service including the estimated service amount is delivered to a financial server,
A payment management server that notifies a user terminal whether to provide a service according to the approval result received from the financial server. The method of claim 10,
The estimated service amount is
A payment management server that is determined differently based on a service provision time, a service provision location, and a service provision type included in service details input from the user terminal. The method of claim 10,
The financial server,
The payment method registered in the user terminal is pre-approved for the payment method by determining whether payment is possible based on the estimated service amount included in the approval request,
The approval result,
A payment management server indicating whether payment is possible with the payment method. In the payment management server performing a payment management method,
The payment management server includes a processor,
The processor,
From the service provider terminal, receives the service confirmation amount for the service requested by the user terminal,
A request to cancel approval of the estimated service amount for the service is delivered to the financial server,
The request to proceed with approval of the service confirmation amount for the service is transmitted to the financial server,
Receiving an approval result for the service confirmation amount from the financial server,
Payment management server that provides a notification of the completion of the service including the approval result to the user terminal. The method of claim 13,
The estimated service amount is
A payment management server that is determined differently based on a service provision time, a service provision location, and a service provision type included in service details input from the user terminal. The method of claim 13,
The service,
Payment management server that proceeds after approval is completed with the payment method registered in advance for the estimated service amount in the financial server. In the payment management server performing a payment management method,
The payment management server includes a processor,
The processor,
From the service provider terminal, receives the service confirmation amount for the service requested by the user terminal,
Compare the service estimate for the service with the service commitment,
When the estimated service amount is greater than the determined service amount, a request for cancellation of approval is transmitted to the financial server for a difference between the estimated service amount and the determined service amount,
If the service confirmation amount is greater than the service expected amount, an additional approval request is transmitted to the financial server for a difference between the service confirmation amount and the service expected amount,
Payment management server that provides a notification of the completion of the service including the approval result received from the financial server to the user terminal. The method of claim 16,
The estimated service amount is
A payment management server that is determined differently based on a service provision time, a service provision location, and a service provision type included in service details input from the user terminal. The method of claim 16,
The service,
Payment management server that proceeds after approval is completed with the payment method registered in advance for the estimated service amount in the financial server. A computer-readable recording medium on which a program for executing the method of any one of claims 1 to 9 is recorded.

Images