CN111833136A

CN111833136A - Order processing method and device

Info

Publication number: CN111833136A
Application number: CN201910829572.3A
Authority: CN
Inventors: 区觅; 刘洋; 梁孟醒
Original assignee: Beijing Didi Infinity Technology and Development Co Ltd
Current assignee: Beijing Didi Infinity Technology and Development Co Ltd
Priority date: 2019-09-03
Filing date: 2019-09-03
Publication date: 2020-10-27

Abstract

The management platform enables a user to confirm payment information before the user pays the order fee, and then determines the order amount to be paid by the user based on payment appeal information fed back by the user, so that the accuracy of the order amount paid by the user is effectively improved, the processing time of a travel order is shortened, the processing efficiency of the travel order is improved, and the processing resource of the travel order is saved. Meanwhile, after receiving the payment appeal information, the method or the device sends the payment appeal information to the service providing end; and determining a second target payment value needing to be paid to the service provider based on the appeal feedback information sent by the service provider aiming at the payment appeal information. The exact order amount which should be paid to the driver, namely the second target payment value, can be determined based on the appeal feedback information, so that the accuracy of the order amount paid to the driver is improved.

Description

Order processing method and device

Technical Field

The present application relates to the field of data and information processing technologies, and in particular, to an order processing method and apparatus.

Background

At present, with the appearance and the development of the network appointment car, the travel efficiency of a user is effectively improved. In the process that a user uses a network car to make an appointment for travel, a travel order needs to be issued, and after a driver end receives the travel order issued by the user, the user is delivered according to the starting place and the destination in the travel order. After the user is sent to the destination, the driver end sends the amount of the order to be paid to the user end used by the user, and the user pays the vehicle fee according to the amount of the order issued by the driver end.

In the actual operation process of the online taxi appointment, the amount of the order sent by the driver end may be inaccurate due to various reasons, at this time, the user can only pay the taxi fee according to the amount of the order sent by the driver end firstly, then complain or feedback is carried out by using a telephone and the like, after the complain or feedback is verified, the amount of the order of the travel order can be corrected, and then operations such as fee deduction on or fee return for the driver are carried out. Therefore, in the processing flow in the prior art, the trip amount of the trip order is not accurate enough, the processing time of the trip order is increased seriously, the processing efficiency of the trip order is reduced, and the waste of resources is increased.

Disclosure of Invention

In view of this, an object of the present application is to provide an order processing method and apparatus, which enable a user to firstly confirm payment information before the user pays an order fee, and then determine an order amount to be paid by the user based on payment appeal information fed back by the user, thereby effectively improving accuracy of the order amount of a travel order, reducing processing time of the travel order, improving processing efficiency of the travel order, and saving processing resources of the travel order.

In a first aspect, the present application provides an order processing method, including:

acquiring a payment request initiated by a service provider aiming at a target order and service characteristic information corresponding to the target order;

if the payment request is determined to be abnormal based on the service characteristic information, payment confirmation information aiming at the payment request is initiated to a service request end corresponding to the target order;

receiving payment appeal information generated by the service request end in response to the payment confirmation information;

determining a first target payment value of a service request end aiming at the target order based on the payment appeal information.

In a second aspect, the present application further provides an order processing method, including:

sending the payment appeal information to the service provider;

receiving appeal feedback information sent by the service providing end in response to the payment appeal information;

a second target payment value to be paid to the service provider is required based on the appeal feedback information.

In a third aspect, the present application further provides an order processing apparatus, including:

the system comprises a first information acquisition module, a second information acquisition module and a third information acquisition module, wherein the first information acquisition module is used for acquiring a payment request initiated by a service provider aiming at a target order and service characteristic information corresponding to the target order;

the first payment confirmation module is used for initiating payment confirmation information aiming at the payment request to a service request end corresponding to the target order when the payment request is determined to be abnormal based on the service characteristic information;

the first appeal receiving module is used for receiving payment appeal information generated by the service request end in response to the payment confirmation information;

the appeal confirmation module is used for determining a first target payment value of the service request end aiming at the target order based on the payment appeal information.

In a fourth aspect, the present application further provides an order processing apparatus, including:

the second information acquisition module is used for acquiring a payment request initiated by a service provider for a target order and service characteristic information corresponding to the target order;

the second payment confirmation module is used for initiating payment confirmation information aiming at the payment request to a service request end corresponding to the target order when the payment request is determined to be abnormal based on the service characteristic information;

the second appeal receiving module is used for receiving payment appeal information generated by the service request end responding to the payment confirmation information;

the second appeal forwarding module is used for sending the payment appeal information to the service provider;

the second feedback receiving module is used for receiving appeal feedback information sent by the service providing end in response to the payment appeal information;

and the second feedback confirmation module is used for determining a second target payment value needing to be paid to the service provider.

In a fifth aspect, an embodiment of the present application further provides an electronic device, including: the electronic device comprises a processor, a storage medium and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, when the electronic device runs, the processor and the storage medium communicate through the bus, and the processor executes the machine-readable instructions to execute the steps in any one of the possible implementation manners of the first aspect and the second aspect of the embodiment of the present application.

In a sixth aspect, an embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and the computer program is executed by a processor to perform the steps in the first aspect of the present application, in any possible implementation manner of the first aspect, and in the second aspect.

According to the order processing method and device provided by the embodiment of the application, a management platform firstly acquires a payment request initiated by a service provider aiming at a target order and service characteristic information corresponding to the target order; if the payment request is determined to be abnormal based on the service characteristic information, payment confirmation information aiming at the payment request is initiated to a service request end corresponding to the target order; receiving payment appeal information generated by the service request end in response to the payment confirmation information; a first target payment value of the service requester for the target order is determined based on the payment appeal information. According to the technical scheme, the service request terminal can firstly confirm the payment information before the service request terminal pays the order fee, and then the order amount to be paid by the service request terminal is determined based on the fed-back payment appeal information, so that the accuracy of the order amount paid by the service request terminal is effectively improved, the processing time of a travel order is shortened, the processing efficiency of the travel order is improved, and the processing resource of the travel order is saved.

Further, after receiving the payment appeal information, the order processing method and the order processing device send the payment appeal information to the service provider; receiving appeal feedback information sent by a service providing end in response to the payment appeal information; and determining a second target payment value needing to be paid to the service provider based on the appeal feedback information. According to the technical scheme, the accurate order amount which is to be paid to the service provider, namely the second target payment value, can be determined based on the appeal feedback information, and the accuracy of the order amount paid to the service provider is further improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.

FIG. 1 is a block diagram illustrating an architecture of an order processing system according to an embodiment of the present disclosure;

FIG. 2 is a flow chart illustrating an order processing method according to an embodiment of the present application;

FIG. 3A is a schematic diagram showing page information of a target value for which an additional fee needs to be filled in the embodiment of the present application;

3B, 3D and 3E are schematic diagrams of page information of target values with additional fees filled in the embodiment of the application;

FIG. 3C is a schematic diagram illustrating first expense settlement page information in an embodiment of the present application;

FIG. 3F is a schematic diagram of page information including sensitive words and target values with surcharges filled in the embodiment of the application;

FIG. 3G is a schematic diagram illustrating the successful re-pricing page information in the embodiment of the present application;

FIG. 3H is a schematic diagram illustrating checkout counter page information in an embodiment of the present application;

FIG. 3I shows a schematic diagram of information of a page to be paid in the embodiment of the application;

fig. 3J illustrates a secondary confirmation page information diagram of the service provider agreeing to pay appeal information in the embodiment of the present application;

fig. 3K illustrates a secondary confirmation page information diagram of the service provider disapproving payment appeal information in the embodiment of the present application;

FIG. 3L is a diagram illustrating reason filling page information in an embodiment of the present application;

fig. 3M shows a schematic diagram of filled-in page information after filling in the embodiment of the present application;

FIG. 3N is a diagram illustrating information of a filled-in page after filling of sensitive words occurs in the embodiment of the present application;

FIG. 3O is a schematic diagram illustrating page information waiting for reply in an embodiment of the present application;

FIG. 3P is a schematic diagram illustrating page information of overdue service providers in the embodiment of the present application;

fig. 3Q is a schematic diagram illustrating page information of the service provider agreeing to pay appeal information in the embodiment of the present application;

fig. 3R illustrates a schematic diagram of page information of a service provider that does not agree with payment appeal information in an embodiment of the present application;

FIG. 3S is a schematic diagram illustrating page information for renegotiation in an embodiment of the present application;

FIG. 3T is a schematic diagram illustrating page information of a negotiated submitting client in an embodiment of the present application;

fig. 4A is a schematic diagram illustrating page information for filling in target payment information in the embodiment of the present application;

fig. 4B is a schematic diagram illustrating page information in which target payment information is required to be filled in the embodiment of the present application;

FIGS. 4C and 4D are schematic diagrams illustrating third fee confirmation page information in the embodiment of the present application;

FIG. 4E is a schematic diagram illustrating modification of payment page information in an embodiment of the present application;

FIG. 5A is a schematic diagram showing page information for which a reason for non-ride needs to be filled in the embodiment of the application;

FIG. 5B is a schematic diagram illustrating payment page information for closing a target order in an embodiment of the present application;

FIG. 5C is a diagram illustrating a second expense settlement page information according to an embodiment of the present application;

FIG. 5D is a schematic diagram illustrating the end-of-travel page information in an embodiment of the present application;

FIG. 6A is a flow chart illustrating the determination of a second target value payment value in an embodiment of the present application;

fig. 6B shows a schematic diagram of page information including payment appeal information when there is an exception in the surcharge in the embodiment of the present application;

fig. 6C illustrates a page information diagram of a journey or route with an exception, including payment complaint information, in an embodiment of the present application;

fig. 6D illustrates a page information diagram including payment appeal information when there is an anomaly in the course or route in the embodiment of the present application;

fig. 6E, 6F, and 6G are schematic diagrams illustrating page information of the service provider agreeing to pay appeal information feedback in the embodiment of the present application;

fig. 6H, 6I, and 6J illustrate schematic page information diagrams of the service provider not agreeing to the payment appeal information feedback in the embodiment of the present application;

6K, 6L, 6M show the abnormal prompt information page schematic diagram in the embodiment of the application;

6N, 6O and 6P are schematic diagrams illustrating page information of a service provider end to be processed after exception in the embodiment of the application;

fig. 7 illustrates a payment complaint page information diagram in an embodiment of the present application;

FIG. 8 is a flow chart illustrating a further method of order processing according to an embodiment of the present application;

FIG. 9 is a flow chart illustrating another method of order processing according to an embodiment of the present application;

fig. 10 is a schematic structural diagram illustrating an order processing apparatus according to an embodiment of the present application;

fig. 11 is a schematic structural diagram illustrating a further order processing apparatus provided in an embodiment of the present application;

fig. 12 shows a schematic structural diagram of an electronic device provided in an embodiment of the present application.

Detailed Description

In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it should be understood that the drawings in the present application are for illustrative and descriptive purposes only and are not used to limit the scope of protection of the present application. Additionally, it should be understood that the schematic drawings are not necessarily drawn to scale. The flowcharts used in this application illustrate operations implemented according to some embodiments of the present application. It should be understood that the operations of the flow diagrams may be performed out of order, and steps without logical context may be performed in reverse order or simultaneously. One skilled in the art, under the guidance of this application, may add one or more other operations to, or remove one or more operations from, the flowchart.

In addition, the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present application without making any creative effort, shall fall within the protection scope of the present application.

To enable those skilled in the art to use the present disclosure, the following embodiments are given in conjunction with the specific application scenario "network appointment order processing". It will be apparent to those skilled in the art that the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the application. Although the present application is described primarily in the context of order payment for online appointments, it should be understood that this is merely one exemplary embodiment.

It should be noted that in the embodiments of the present application, the term "comprising" is used to indicate the presence of the features stated hereinafter, but does not exclude the addition of further features.

The terms "passenger," "requestor," "service requestor," and "customer" are used interchangeably in this application to refer to an individual, entity, or tool that can request or order a service. The terms "driver," "provider," "service provider," and "provider" are used interchangeably in this application to refer to an individual, entity, or tool that can provide a service. The term "user" in this application may refer to an individual, entity or tool that requests a service, subscribes to a service, provides a service, or facilitates the provision of a service. For example, the user may be a passenger, a driver, an operator, etc., or any combination thereof.

The terms "service request" and "travel order" are used interchangeably herein to refer to a request initiated by a passenger, a service requester, a driver, a service provider, a supplier, or the like, or any combination thereof. Accepting the "service request" or "order" may be a passenger, a service requester, a driver, a service provider, a supplier, or the like, or any combination thereof. The service request may be charged or free.

The Positioning technology used in the present application may be based on a Global Positioning System (GPS), a Global Navigation Satellite System (GLONASS), a COMPASS Navigation System (COMPASS), a galileo Positioning System, a Quasi-Zenith Satellite System (QZSS), a Wireless Fidelity (WiFi) Positioning technology, or the like, or any combination thereof. One or more of the above-described positioning systems may be used interchangeably in this application.

One aspect of the present application relates to an order processing system. The system can enable the user to confirm the payment information before the user pays the order fee, and then determine the order amount to be paid by the user based on the payment appeal information fed back by the user, so that the accuracy of the order amount paid by the user is effectively improved, the processing time of the travel order is reduced, the processing efficiency of the travel order is improved, and the processing resource of the travel order is saved. Meanwhile, after receiving the payment appeal information, the system sends the payment appeal information to a service providing end; and determining a second target payment value needing to be paid to the service provider based on the appeal feedback information sent by the service provider aiming at the payment appeal information. The exact order amount which should be paid to the driver, namely the second target payment value, can be determined based on the appeal feedback information, and the accuracy of the order amount paid to the driver is further improved.

Fig. 1 is a schematic structural diagram of an order processing system 100 according to an embodiment of the present disclosure. For example, the order processing system 100 may be an online transportation service platform for transportation services such as taxi cab, designated drive service, express, carpool, bus service, driver rental, or shift service, or any combination thereof. The order processing system 100 may include one or more of a server 110, a network 120, a service requester 130, a service provider 140, and a database 150.

In some embodiments, the server 110 may include a processor. The processor may process information and/or data related to the service request to perform one or more of the functions described herein. For example, the processor may determine the target vehicle based on a service request obtained from the service requester 130. In some embodiments, a processor may include one or more processing cores (e.g., a single-core processor (S) or a multi-core processor (S)). Merely by way of example, a Processor may include a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), an Application Specific Instruction Set Processor (ASIP), a Graphics Processing Unit (GPU), a Physical Processing Unit (PPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a controller, a microcontroller Unit, a reduced Instruction Set computer (reduced Instruction Set computer), a microprocessor, or the like, or any combination thereof.

In some embodiments, the device types corresponding to the service request end 130 and the service providing end 140 may be mobile devices, such as smart home devices, wearable devices, smart mobile devices, virtual reality devices, or augmented reality devices, and the like, and may also be tablet computers, laptop computers, or built-in devices in motor vehicles, and the like.

In some embodiments, a database 150 may be connected to the network 120 to communicate with one or more components in the order processing system 100 (e.g., the server 110, the service requester 130, the service provider 140, etc.). One or more components in the order processing system 100 may access data or instructions stored in the database 150 via the network 120. In some embodiments, the database 150 may be directly connected to one or more components in the order processing system 100, or the database 150 may be part of the server 110.

The following describes in detail the order processing method provided in the embodiment of the present application with reference to the content described in the order processing system 100 shown in fig. 1.

Referring to fig. 2, a flowchart of an order processing method provided in the embodiment of the present application is shown, where the method may be executed by the server 110 in the order processing system 100, and the specific execution process is as follows:

s210, a payment request initiated by a service provider for a target order and service characteristic information corresponding to the target order are obtained.

After completing the target order, the service provider generates a payment request and sends the payment request to the service platform, i.e. the server 110. The payment request comprises payment information, and the payment information comprises the total payment fee, the values of various additional fees and the like. The service characteristic information comprises first route information of the service providing terminal for completing the target order, second route information of the service providing terminal for completing the target order, an origin corresponding to the target order, a destination corresponding to the target order and the like.

S220, if the payment request is determined to be abnormal based on the service characteristic information, payment confirmation information aiming at the payment request is sent to a service request end corresponding to the target order.

After receiving the payment request and the service characteristic information, the service platform can determine the estimated payment cost, the additional fee estimated value and the like of the target order based on the service characteristic information, and compares the estimated value with the corresponding value in the payment request, so that whether the payment request is abnormal or not can be determined.

In a specific application scenario, the payment appeal information includes at least one type of appeal information:

appeal information of the additional fee exception type; appeal information of the type of the non-riding vehicle; a range exception type of appeal information.

And S230, receiving payment appeal information generated by the service request end responding to the payment confirmation information.

After receiving the payment confirmation information, the service request end can confirm to continue payment or feed back payment appeal information, and fills the specific appeal in the corresponding page to send the specific appeal to the service platform when the payment appeal information needs to be fed back.

And S240, determining a first target payment value based on the payment appeal information.

After receiving the payment appeal information fed back by the service request end, the service platform can directly obtain the first target payment value based on the payment appeal information, or determine the first target payment value based on the payment appeal information and the total payment cost in the payment request.

According to the technical scheme, before the user pays the order form fee, the user firstly confirms the payment information, and then determines the order form amount to be paid by the user based on the payment appeal information fed back by the user, so that the accuracy of the order form amount paid by the user is effectively improved, the processing time of the travel order form is reduced, the processing efficiency of the travel order form is improved, and the processing resource of the travel order form is saved.

It should be noted that after the first target payment value is determined, the first target payment value may be sent to the service request end, so that the service request end completes payment for the target order based on the first target payment value.

In some embodiments, the determining the first target payment value based on the payment appeal information may be implemented by:

step one, obtaining the type of the payment appeal information, if the payment appeal information is the appeal information of the additional fee abnormal type, obtaining an additional fee target value from the payment appeal information, and obtaining an additional fee initial value from the payment information of the payment request.

The surcharge target value may include a target value for each of a plurality of surcharges. For example, a target value of a bridge fee, a target value of a parking fee, and the like may be included.

In the implementation, the service platform first sends page information of a target value for which an additional fee needs to be filled out to the service requester, as shown in fig. 3A. And after receiving the page information of the target value of the additional fee, the service request end fills the target value of the additional fee into the page information and feeds the page information back to the service platform. The service platform obtains the surcharge target value from the page information fed back by the service request end, as shown in fig. 3B, 3D and 3E.

In some embodiments, the page information to be filled in the target value of the surcharge further includes an input box for inputting text information, after the service request terminal sends the text information input box to the service platform, the service platform will recognize the input text information, and if there is sensitive words, the page information shown in fig. 3F is fed back to the service request terminal to prompt the service request terminal to generate the sensitive words. Of course, the service request end can also be used for reminding the service request end of performing sensitive vocabulary recognition on the input words.

And step two, determining a surcharge difference value based on the surcharge target value and the surcharge initial value.

The surcharge difference may be obtained by subtracting the surcharge initial value from the surcharge target value.

And step three, determining the first target payment value based on the additional fee difference value and the total payment fee obtained from the payment information of the payment request.

In a specific implementation, if the service provider receives more surcharges, the surcharge difference may be subtracted from the total payment cost to obtain the first target value. If the service provider receives less surcharges, the sum of the total payment and the surcharge difference can be used as the first target value.

and obtaining the type of the payment appeal information, if the payment appeal information is the appeal information of the abnormal route type, obtaining target payment information determined by a service provider from the payment appeal information, and determining the first target payment value based on the target payment information.

After determining the first target payment value, the service platform generates price change success page information as shown in fig. 3G, and sends the page information to the service request end for displaying. The page information of successful price change includes a payment removal control, and after the payment removal control is triggered, the service platform generates cash register table page information, as shown in fig. 3H. The service platform sends the checkout counter page information to the service request terminal for displaying, the checkout counter page information includes a payment control, and after the payment control is triggered, the service platform generates page information to be paid, as shown in fig. 3I. The service platform sends the page information to be paid to the service request terminal for displaying, and the service request terminal completes payment of the target order by using the page information to be paid.

In specific implementation, the payment value corresponding to the target payment information is used as the first target payment value.

In the implementation, the service platform first sends page information for filling the information of the required target payment to the service requester, as shown in fig. 4A. And after receiving the page information needing to be filled with the target payment information, the service request end fills the target payment information into the page information and feeds the page information back to the service platform. The service platform obtains the target payment information from the page information fed back by the service request end, as shown in fig. 4B.

and acquiring the type of the payment appeal information, and if the payment appeal information is the appeal information of the non-riding type, setting the first target payment value to be 0.

When the payment demand information is the demand information of the non-riding type, the service request end is indicated to be not riding, and the fee to be paid by the service request end is 0 at the moment, so that the first target payment value is set to be 0.

In specific implementation, the service platform first sends a page message to the service requester, where the page message needs to fill out the reason for the non-ride, as shown in fig. 5A. And after receiving the page information needing to fill the non-riding reason, the service request end fills the non-riding reason into the page information and feeds the non-riding reason back to the service platform. The service platform performs judgment based on the page information fed back by the service request terminal, sets the first target payment value to 0 if the audit is passed, and closes the payment page of the target order, as shown in fig. 5B. After the payment page of the target order is closed, the service platform generates an end-of-travel page, as shown in fig. 5D, which includes a control for selecting the satisfaction level of the service provider.

In some embodiments, the determining that the payment request is abnormal based on the service characteristic information may be implemented by: determining an additional fee estimated value based on the first route information; and if the initial value of the additional fee in the payment information of the payment request is different from the estimated value of the additional fee, determining that the additional fee corresponding to the payment request is abnormal.

In practical application, the service platform can identify the type of the surcharge and the amount of each surcharge which may occur based on the driving route of the service provider, so that the service platform can determine a surcharge pre-evaluation value based on the first route information, and determine that the surcharge corresponding to the payment request is abnormal when the surcharge pre-evaluation value is different from the surcharge initial value in the payment information.

When the surcharge is abnormal, the step of initiating the payment confirmation information for the payment request to the service request terminal corresponding to the target order can be implemented by the following steps:

step one, if the additional fee corresponding to the payment request is abnormal, first fee confirmation page information comprising a first control and a second control is generated; the first control is used for indicating that the surcharge is normal and paying, and the second control is used for indicating that the surcharge is abnormal and needs to be fed back.

As shown in fig. 3C, the first fee confirmation page information is generated and then sent to the service request end, so that the service request end determines to directly pay the target order or feed back the exceptional fee. Specifically, if the service request end triggers the first control, the service request end does not perform a payment appeal, and the payment is directly performed. And if the service request end triggers the second control, the payment appeal of the service request end is represented.

And step two, after the second control is triggered, sending first feedback page information including information indicating input of target additional cost to the service request terminal.

The first feedback page information here is shown in fig. 3A, and is used to fill out the surcharge target value for each type of surcharge, i.e., the above-mentioned target surcharge information. And after filling, sending the information to a service platform, and acquiring the additional fee target value from the fed-back page information by the service platform.

In some embodiments, the determining that the payment request is abnormal based on the service characteristic information may be further implemented by:

and if the first route information comprises different positioning information of continuous positions and the second route information only comprises the positioning information of the passenger waiting point, determining whether the riding information corresponding to the payment request is abnormal.

And when the service providing end travels a certain distance and the service request end does not travel, determining that the service request end does not take a car.

When the riding is abnormal, the payment confirmation information for the payment request is initiated to the service request terminal corresponding to the target order in the above steps, which can be implemented by using the following steps:

step one, if the riding information corresponding to the payment request is abnormal, generating second expense confirmation page information comprising a third control and a fourth control; the third control is used for indicating that the bus is confirmed and payment is carried out, and the fourth control is used for indicating that the bus is not taken and needs feedback.

As shown in fig. 5C, the second fee confirmation page information is generated and then sent to the service request end, so that the service request end determines to directly pay the target order or feed back whether to take the car. Specifically, if the service request end triggers the third control element, it indicates that the service request end does not perform a payment appeal, and directly performs payment. And if the service request end triggers the fourth control, the payment appeal of the service request end is represented.

And step two, after the fourth control is triggered, sending second feedback page information including an instruction for inputting the reason for charging without taking a bus to the service request terminal.

The second feedback page information here is shown in fig. 5A, and is used to fill in the reason for the fare of the non-ride. And sending the information to a service platform after filling, and acquiring the reason of the charge without taking the bus from the feedback page information by the service platform.

determining estimated payment cost of the target order based on an origin corresponding to the target order and a destination corresponding to the target order; and if the difference value between the estimated payment cost and the total payment cost in the payment request is larger than a preset threshold value, determining that the driving distance corresponding to the payment request is abnormal.

If the total payment cost in the payment request is much larger than the estimated payment cost, the distance of the service providing end is abnormal, and the user may intentionally detour the path, and at this time, the travel distance corresponding to the payment request is determined to be abnormal.

When the route is abnormal, the payment confirmation information for the payment request is initiated to the service request terminal corresponding to the target order in the above steps, which can be implemented by using the following steps:

step one, if the driving distance corresponding to the payment request is abnormal, generating third expense confirmation page information comprising a fifth control and a sixth control; the fifth control is used for indicating that the route is normal and payment is carried out, and the sixth control is used for indicating that the route is bypassed and feedback is needed.

As shown in fig. 4C and 4D, the third fee confirmation page information is generated and then sent to the service request end, so that the service request end determines to directly pay the target order or feed back the detour. Specifically, if the service request end triggers the fifth control, the service request end does not perform a payment appeal, and the payment is directly performed. And if the service request end triggers the sixth control, the payment appeal of the service request end is represented. Among them, the difference between the estimated route and the travel route of the service provider is large in 4C, and the charging point is different between the estimated route and the travel route of the service provider in fig. 4D.

And step two, after the sixth control is triggered, third feedback page information including the input target payment information is sent to the service request end.

Here, the third feedback page information is shown in fig. 4A, and is used to fill in the input target payment information. And after filling, sending the information to a service platform, and acquiring target payment information from the fed-back page information by the service platform.

In a specific implementation, the third feedback page information further includes input box information indicating a reason for inputting the detoured route.

After receiving the page information fed back by the service request end, the service platform determines a first target payment value, generates modified payment page information including the first target payment value, as shown in fig. 4E, and sends the modified payment page information to the service request end.

In some embodiments, as shown in fig. 6A, the order processing method further includes the following steps:

s610, sending the payment appeal information to the service provider.

After receiving the payment appeal information, the service platform generates page information including the payment appeal information and sends the page information to the service providing end. As shown in fig. 6B, the generated page information including the payment appeal information is used when there is an exception in the surcharge corresponding to the payment request; as shown in fig. 6C, the generated page information including the payment appeal information is generated when there is an abnormality in the route or route corresponding to the payment request; as shown in fig. 6D, the generated page information includes the payment appeal information when there is an abnormality in the presence or absence of a ride corresponding to the payment request.

And S620, receiving appeal feedback information sent by the service providing end in response to the payment appeal information.

After receiving the page information including the payment appeal information, the service provider sends the page information including the appeal feedback information to the service platform, and the appeal feedback information sent by the service provider can be acquired from the page. Fig. 6E, 6F, and 6G show page information for the service provider agreeing to pay the appeal information feedback; fig. 6H, 6I, and 6J show page information that the service provider does not agree with the payment appeal information feedback.

And S630, determining a second target payment value needing to be paid to the service provider based on the appeal feedback information.

In particular implementations, if the appeal feedback information indicates that the service provider agrees to pay the appeal information, the second target payment value is determined based on the payment appeal information. In this case, it is determined that the first target payment value determined as described above is the correct payment value corresponding to the target order, and in this case, it is necessary to set the second target payment value to be equal to the first target payment value.

If the appeal feedback information indicates that the service providing end does not agree with the payment appeal information, the responsibility of the service providing end or the responsibility of the service requesting end can be determined in a manual responsibility judgment mode.

It should be noted that, before generating the page information including the payment appeal information, the service platform also generates an exception prompt information page, as shown in fig. 6K, 6L, and 6M, and sends the exception prompt information page to the service provider, and the service provider confirms to perform exception handling through the page.

If the service providing end does not process the abnormity within the set time period, the service platform judges the responsibility according to the payment complaint information and the complaint feedback information, generates page information such as fig. 6N, 6O and 6P, and then sends the page information to the service providing end for displaying.

It should be noted that after the second target payment value is determined, payment to the service provider may be completed based on the second target payment value.

In order to reduce the pressure of the staff and improve the accuracy of the order amount, the method can also perform the toronto negotiation between the service providing terminal and the service requesting terminal, and specifically, when the appeal feedback information indicates that the service providing terminal does not agree with the payment appeal information, the method can perform the toronto negotiation by using the following steps:

step one, if the appeal feedback information indicates that the service providing end does not agree with the payment appeal information, the appeal feedback information is sent to the service request end, so that the service request end feeds back new payment appeal information according to the appeal feedback information.

The charge value or the like involved in the new payment complaint information may be different from the charge value in the last payment complaint information.

In this step, when the service provider does not agree with the payment appeal information of the service request terminal, the service platform sends the appeal feedback information fed back by the service provider to the service request terminal. And after receiving the appeal feedback information, the service request end sends new payment appeal information which agrees or disagrees with the appeal feedback information.

And step two, if the new payment appeal information indicates that the service request end agrees to the appeal feedback information, taking the total payment cost in the payment information of the payment request as the second target payment value.

And the new payment appeal information indicates that the service request end agrees to the appeal feedback information, and then indicates that the payment information in the payment request initiated by the service providing end is taken as the standard, and at the moment, the second target payment value is set as the value of the total payment cost in the payment information.

And step three, if the new payment appeal information indicates that the service request end does not agree with the appeal feedback information, sending the new payment appeal information to the service providing end, and returning to the step of receiving the appeal feedback information sent by the service providing end in response to the payment appeal information.

The new payment appeal information indicates that the service request end does not agree with the appeal feedback information, the new payment appeal information is sent to the service providing end, and the step of receiving the appeal feedback information sent by the service providing end responding to the payment appeal information is returned, so that the service providing end and the service request end can negotiate with each other in a Torontal mode.

Compared with one round of negotiation, the multi-party negotiation increases the chance of the service providing terminal and the service requesting terminal to reach the same, and compared with manual operation such as manual responsibility judgment, the processing efficiency of the order amount can be improved, resources are saved, and the accuracy of the order amount can be improved.

It should be noted that no matter the service provider agrees to pay the appeal information or disagrees with the payment appeal information, the service platform generates secondary confirmation page information and sends the secondary confirmation page information to the service provider, as shown in fig. 3J and 3K, where 3J is the secondary confirmation page information for the service provider agreeing to pay the appeal information, and 3K is the secondary confirmation page information for the service provider disagrees with the payment appeal information.

When the service provider does not agree with the payment appeal information, the service platform fills in the page information according to the generation reason shown in fig. 3L and sends the page information to the service provider. The service provider fills in the page as shown in fig. 3M, and sends the page information shown in fig. 3M to the service platform.

If the above-mentioned reason is sensitive words, the service provider can recognize the words, generate page information as shown in fig. 3N, and send the page information to the service platform.

After the service request end sends the payment appeal information to the service platform and before the service providing end gives no feedback, the service platform may generate the page information waiting for reply as shown in fig. 3O and send the page information to the server request end for presentation. The page information comprises a control for canceling the price change and a control for retransmitting the payment appeal information, the control for canceling the price change is triggered, the payment appeal information can be canceled, the control for retransmitting the payment appeal information is triggered, and the payment appeal information can be retransmitted.

After the service provider agrees to pay the appeal information, the service platform generates page information agreed by the service provider and sends the page information to the service request end, as shown in fig. 3Q.

After the service provider does not agree with the payment appeal information, the service platform generates page information that the service provider does not agree with and sends the page information to the service request side, as shown in fig. 3R. The payment appeal information or the contact customer service can be cancelled by triggering the corresponding control through the page service request end.

After the payment appeal information is revoked, that is, after the negotiation is revoked, the service platform generates the page information shown in fig. 3S, and sends the page information to the service request terminal.

After the customer service is negotiated and submitted, the service platform generates page information as shown in fig. 3T and sends the page information to the service request end. The customer service processing result can be checked through the control in the page information.

When the service provider does not process the abnormal payment appeal information within the set time period, the service platform generates expected unprocessed page information and sends the expected unprocessed page information to the service request end, as shown in fig. 3P.

In the above embodiment, the first target payment value is directly determined based on the payment appeal information of the service request terminal, and after the determination is made, the service request terminal pays the fee according to the changed amount. However, the payment appeal information provided by the service request end may be inaccurate, and at this time, an error must exist in the first target payment value determined directly according to the payment appeal information, and the above problem is solved by adopting a hosting manner for the order fee paid by the service request end.

Specifically, as shown in fig. 7, after the payment request is sent to the service platform, the service platform pushes the payment appeal page information to the service request end, and the service request end needs to pay the target order according to the total payment cost in the payment information. After payment, the service platform trusts the payment paid by the service request terminal, namely, the total payment is stored as the payment value to be confirmed of the target order. After the hosting, determining whether to return the fee to the service request terminal and the second target payment value paid to the service provider terminal based on the result of the single round or the Toronto negotiation between the service provider terminal and the service request terminal.

Specifically, the method comprises the following steps: if the received appeal feedback information indicates that a service providing end agrees to pay appeal information, determining information of fees payable for the service requesting end based on the latest payment appeal information and the payment information in the payment request, and initiating a fee updating process for the service requesting end based on the information of fees payable for the services and the first target payment value. Or if the received payment appeal information indicates that the service request end agrees to the appeal feedback information, the payment value to be confirmed of the target order is used as the information of the fees to be paid, and the second target payment value is set as the value of the total payment fee in the payment information.

In a specific implementation, the difference between the information of the fees to be paid and the first target payment value may be solved, and then a fee updating process for the service request end may be initiated.

If the service request end and the service providing end do not reach the same after the above toronto negotiation, the responsibility judgment needs to be performed, which can be specifically realized by the following steps:

step one, if the quantity of the received appeal feedback information exceeds a preset value, the received appeal feedback information indicates that the service providing end disagrees with the payment appeal information, and the received payment appeal information indicates that the service requesting end disagrees with the appeal feedback information, determining first payment abnormal responsibility information based on the service characteristic information, all the appeal feedback information and all the payment appeal information.

In specific implementation, semantic recognition can be performed on all appeal feedback information and all payment appeal information by utilizing semantic recognition, and liability judgment is performed on the basis of semantic recognition results and service characteristic information to obtain the first payment abnormal responsibility information.

For example, the service provider adds the parking fee generated in the process of waiting for taking over the order in the airport to the total payment fee of the target order through semantic recognition, and at this time, the service provider can be directly determined to be responsible according to the semantic recognition.

And step two, if the first payment abnormal responsibility information indicates that the service provider is responsible, determining a first target payment value based on the latest payment appeal information and payment information, and setting the second target payment value to be equal to the first target payment value.

Here, the method of determining the first target payment value based on the latest payment appeal information is the same as the above method of determining the first target payment value based on the payment appeal information, and details thereof are omitted here.

If the hosting of the fee is already realized at this time, when a service providing end is responsible, determining the information of the fee to be paid according to the payment appeal information, returning the monitored fee and the like, specifically, determining the information of the fee to be paid for the service requesting end based on the latest payment appeal information and payment information, initiating a fee updating process for the service requesting end based on the information of the fee to be paid and the first target payment value, and taking the value of the fee to be paid indicated by the information of the fee to be paid as the second target payment value.

And step three, if the first payment abnormal responsibility information indicates that the service request end is responsible, the total payment cost in the payment information of the payment request is used as the second target payment value.

If the hosting of the fee is already realized at this time, when the service providing terminal is not responsible, the payment value to be confirmed of the target order is taken as the information of the fee to be paid, and the total payment in the payment information of the payment request is taken as the second target payment value to be paid to the service providing terminal.

If the service providing end or the service requesting end cannot be determined to be responsible through the steps in the embodiment, the service characteristic information, all appeal feedback information and all payment appeal information are sent to the manual responsibility judgment device end, the manual responsibility judgment device end displays the information, and after manual responsibility judgment, the manual responsibility judgment device end receives a responsibility judgment result, namely the following second payment abnormal responsibility information.

After receiving a responsibility judgment result received by the manual responsibility judgment device end, if the second payment abnormal responsibility information indicates that the service providing end is responsible, determining the first target payment value based on the latest payment appeal information and payment information, and setting the second target payment value to be equal to the first target payment value. And if the second payment abnormal responsibility information indicates that a service request end is responsible, taking the total payment cost in the payment information of the payment request as the second target payment value.

If the hosting of the fee is already realized at the moment, when a service providing end is responsible, determining the information of the fee to be paid aiming at the service request end based on the latest payment appeal information and payment information, initiating a fee updating process aiming at the service request end based on the information of the fee to be paid and the first target payment value, and taking the value of the fee to be paid indicated by the information of the fee to be paid as the second target payment value; and when the service request end is responsible, taking the payment value to be confirmed of the target order as the information of the payment due, and taking the total payment as the second target payment value.

After the above responsibility judgment is finished, if the service provider is judged to be responsible, the following steps are required to be executed:

step one, show the complaint confirmation page information including the second target payment value to the service provider.

And step two, receiving the complaint information fed back by the service provider aiming at the complaint confirmation page information.

And step three, determining first complaint result information based on the complaint information, the service characteristic information, all complaint feedback information and all payment complaint information.

And step four, if the first complaint result information indicates that the complaint of the service provider is successful, taking the payment value to be confirmed of the target order as the information of the payment amount to be paid, and taking the total payment amount as the second target payment value.

And when the service provider complains successfully, taking the total payment cost of the payment information in the payment request as the second target payment value.

If the first complaint result information indicates that the complaint of the service provider is failed, performing secondary complaint by using the following steps:

and step six, sending indication information of complaint failure to the service provider.

And step seven, receiving the complaint feedback information sent by the service provider in response to the indication information of the complaint failure.

And step eight, if the complaint feedback information indicates that the service provider agrees with the first complaint result information of the complaint failure, taking the second target payment value as a final second target payment value.

And step nine, if the complaint feedback information indicates that the service providing end does not agree with complaint result information of complaint failure, sending the complaint feedback information, the complaint information, the service characteristic information, all complaint feedback information and all payment complaint information to the manual complaint equipment end.

And after the complaint is manually performed, inputting a result, namely second complaint result information into the manual complaint equipment terminal, and sending the second complaint result information to the service platform by the manual complaint equipment terminal.

And step ten, receiving second complaint result information sent by the manual complaint equipment terminal.

Step eleven, if the second complaint result information indicates that the complaint of the service provider is successful, taking the payment value to be confirmed of the target order as the information of the fee to be paid, and taking the total payment fee as the second target payment value.

And step twelve, if the second complaint result information indicates that the complaint of the service provider is failed, taking the second target payment value as a final second target payment value.

Taking prepaid car fees and fee escrow as an example, in the order processing method of the present application, specifically, as shown in fig. 8, in the order processing method of the above embodiment, firstly, the service platform performs an abnormal judgment on a payment request initiated by the service provider, sends payment confirmation information to the service requester for the abnormal payment request, and if the service requester considers that the payment request is really abnormal, that is, accepts the payment request intercepted by the service platform, the service requester firstly prepays the car fees according to the total payment fee in the payment information of the payment request, and the service platform escrows the prepaid car fees. And then, negotiating between the service providing terminal and the service request terminal by using the payment appeal information and the appeal feedback information, if the negotiation is agreed and the service providing terminal agrees the payment appeal information of the service request terminal, determining the cost returned to the service request terminal based on the latest payment appeal information, if the negotiation is agreed and the service request terminal agrees the appeal feedback information of the service providing terminal, not refunding the service request terminal, and setting a second target payment value to be equal to the total payment cost.

And if the service providing end and the service request end cannot reach the same after multiple rounds of negotiation, applying for intervention of the service platform, carrying out machine judgment responsibility by the service platform based on all the appeal feedback information, all the payment appeal information and other information, and if the service providing end is judged to be responsible, taking the payment due value indicated by the payment due information as the second target payment value, and carrying out deduction, punishment and the like on the service providing end. And if the service request end is determined to be responsible, taking the payment value to be confirmed of the target order as the information of the payment due, and taking the total payment as the second target payment value, namely, printing all the mandated cost to the service providing end.

And if the service platform cannot determine whether responsibility is on the service providing end or the service request end, sending all the appeal feedback information and all the payment appeal information to the manual accountability judgment equipment end for manual accountability judgment, and if the manual accountability judgment determines that responsibility is on the service providing end, taking the value of the charge to be paid indicated by the information of the charge to be paid as the second target payment value, and carrying out deduction, punishment and the like on the service providing end. And if the service request end is determined to be responsible, taking the payment value to be confirmed of the target order as the information of the payment due, and taking the total payment as the second target payment value, namely, printing all the mandated cost to the service providing end.

And if the manual responsibility judgment cannot determine whether the responsibility is on a service provider or a service requester, initiating a charge updating process for the service requester based on the information of the fees to be paid and the first target payment value, and taking the total payment cost as the second target payment value. The service platform incurs a corresponding capital loss.

As shown in fig. 9, the present application further provides an order processing method, which includes the following steps:

s910, acquiring a payment request initiated by a service provider for a target order and service characteristic information corresponding to the target order.

S920, if it is determined that the payment request is abnormal based on the service characteristic information, initiating payment confirmation information aiming at the payment request to a service request end corresponding to the target order.

And S930, receiving payment appeal information generated by the service request end in response to the payment confirmation information.

And S940, the payment appeal information is sent to the service provider.

And S950, receiving appeal feedback information sent by the service providing end in response to the payment appeal information.

And S960, rating a second target payment value which needs to be paid to the service provider based on the appeal feedback information.

Based on the same inventive concept, the embodiment of the present application further provides an order processing apparatus corresponding to the order processing method, and since the principle of solving the problem of the apparatus in the embodiment of the present application is the same as that of the order processing method in the embodiment of the present application, the implementation of the apparatus may refer to the implementation of the method, and repeated details are not described.

Referring to fig. 10, an order processing apparatus according to another embodiment of the present application includes:

a first information obtaining module 1001, configured to obtain a payment request initiated by a service provider for a target order and service feature information corresponding to the target order;

a first payment confirmation module 1002, configured to initiate payment confirmation information for the payment request to a service request end corresponding to the target order when it is determined that the payment request is abnormal based on the service feature information;

a first appeal receiving module 1003, configured to receive payment appeal information generated by the service request end in response to the payment confirmation information;

an appeal confirmation module 1004 configured to determine a first target payment value for the target order by the service requester based on the payment appeal information.

In one possible embodiment, the payment complaint information includes at least one of the following types of complaint information:

In one possible implementation, the appeal confirmation module 1004, in determining the first target payment value based on the payment appeal information, comprises:

acquiring the type of the payment appeal information, and if the payment appeal information is the appeal information of the additional fee abnormal type, acquiring an additional fee target value from the payment appeal information and acquiring an additional fee initial value from the payment information of the payment request;

determining a surcharge difference value based on the surcharge target value and the surcharge initial value;

determining the first target payment value based on the surcharge difference value and the total payment fee obtained from the payment information of the payment request.

In a possible implementation manner, the service characteristic information includes first route information of the service provider for completing the target order;

the first payment confirmation module 1002, when determining that there is an abnormality in the payment request based on the service feature information, includes:

determining an additional fee estimated value based on the first route information;

and if the initial value of the additional fee in the payment information of the payment request is different from the estimated value of the additional fee, determining that the additional fee corresponding to the payment request is abnormal.

In a possible implementation manner, when the first payment confirmation module 1002 initiates payment confirmation information for the payment request to a service requesting end corresponding to the target order, the method includes:

if the additional fee corresponding to the payment request is abnormal, first fee confirmation page information comprising a first control and a second control is generated; the first control is used for indicating that the additional fee is normal and paying, and the second control is used for indicating that the additional fee is abnormal and needs to be fed back;

and after the second control is triggered, sending first feedback page information including information indicating input of target additional cost to the service request terminal.

In a possible implementation manner, the service characteristic information further includes second route information of the service request terminal for the target order;

if the riding information corresponding to the payment request is abnormal, generating second expense confirmation page information comprising a third control and a fourth control; the third control is used for indicating that the bus is confirmed and payment is carried out, and the fourth control is used for indicating that the bus is not taken and needs feedback;

and after the fourth control is triggered, sending second feedback page information including an indication of inputting a non-ride charging reason to the service request terminal.

In a possible implementation manner, the service characteristic information includes an origin corresponding to the target order and a destination corresponding to the target order;

the first payment confirmation module 1002, in determining that the payment request is abnormal based on the service feature information, includes:

determining estimated payment cost of the target order based on an origin corresponding to the target order and a destination corresponding to the target order;

and if the difference value between the estimated payment cost and the total payment cost in the payment request is larger than a preset threshold value, determining that the driving distance corresponding to the payment request is abnormal.

if the driving distance corresponding to the payment request is abnormal, generating third cost confirmation page information comprising a fifth control and a sixth control; the fifth control is used for indicating that the route is normal and paying, and the sixth control is used for indicating that the route is bypassed and feedback is needed;

and after the sixth control is triggered, sending third feedback page information including input target payment information to the service request end.

In a possible implementation manner, the third feedback page information further includes input box information indicating a reason for inputting the detoured route.

In one possible embodiment, the method further comprises:

a first appeal forwarding module 1005, configured to send the payment appeal information to the service provider;

a first feedback receiving module 1006, configured to receive appeal feedback information sent by the service provider in response to the payment appeal information;

a first feedback confirmation module 1007 configured to determine a first target payment value for the target order by the service requester based on the payment complaint information.

In one possible implementation, the first feedback confirmation module 1007, in determining the second target payment value based on the appeal feedback information, includes:

if the appeal feedback information indicates that the service providing end agrees to pay the appeal information, setting the second target payment value to be equal to the first target payment value;

if the appeal feedback information indicates that the service providing end does not agree with payment appeal information, the appeal feedback information is sent to the service request end, so that the service request end feeds back new payment appeal information aiming at the appeal feedback information;

if the new payment appeal information indicates that the service request end agrees to the appeal feedback information, taking the total payment cost in the payment information of the payment request as the second target payment value;

and if the new payment appeal information indicates that the service request end does not agree with the appeal feedback information, sending the new payment appeal information to the service providing end, and returning to the service providing end to respond to the appeal feedback information sent by the payment appeal information.

In one possible embodiment, the payment appeal information includes the total payment fee;

the appeal confirmation module 1004, in determining a first target payment value based on the payment appeal information, comprises:

taking the total payment cost as the first target payment value, storing the first target payment value as a payment value to be confirmed of the target order, and sending the first target payment value to a service request end;

the apparatus further includes a escrow decision module 1008 to:

if the received appeal feedback information indicates that a service providing end agrees to pay appeal information, determining information of fees to be paid for the service requesting end based on the latest payment appeal information and the payment information in the payment request, and initiating a fee updating process for the service requesting end based on the information of fees to be paid and the first target payment value;

or if the received payment appeal information indicates that the service request end agrees to the appeal feedback information, the payment value to be confirmed of the target order is used as the information of the fees to be paid.

In a possible implementation manner, the apparatus further includes a first discriminant module 1009, configured to:

if the number of the received appeal feedback information exceeds a preset value, the received appeal feedback information indicates that the service providing end disagrees with the payment appeal information, and the received payment appeal information indicates that the service requesting end disagrees with the appeal feedback information, determining first payment abnormal responsibility information based on the service characteristic information, all the appeal feedback information and all the payment appeal information;

if the first payment abnormity responsibility information indicates that a service providing end is responsible, determining the first target payment value based on the latest payment appeal information and payment information, and setting the second target payment value to be equal to the first target payment value;

and if the first payment abnormal responsibility information indicates that a service request end is responsible, taking the total payment cost in the payment information of the payment request as the second target payment value.

In a possible implementation manner, the system further includes a second discriminant module 1010, configured to:

if the first payment abnormal responsibility information cannot be determined based on the service characteristic information, all appeal feedback information and all payment appeal information, sending the service characteristic information, all appeal feedback information and all payment appeal information to a manual responsibility judgment device end;

receiving second payment abnormal responsibility information sent by the manual liability judgment equipment end;

if the second payment abnormity responsibility information indicates that a service providing end is responsible, determining the first target payment value based on the latest payment appeal information and payment information, and setting the second target payment value to be equal to the first target payment value;

and if the second payment abnormal responsibility information indicates that a service request end is responsible, taking the total payment cost in the payment information of the payment request as the second target payment value.

In a possible implementation, the apparatus further includes a first complaint module 1011 configured to:

displaying complaint confirmation page information including the second target payment value to the service provider;

receiving complaint information fed back by a service provider aiming at the complaint confirmation page information;

determining first complaint result information based on the complaint information, the service characteristic information, all complaint feedback information and all payment complaint information;

and if the first complaint result information indicates that the complaint of the service provider is successful, taking the payment value to be confirmed of the target order as the information of the payment due, and taking the total payment as the second target payment value.

In one possible implementation, the first complaint module 1011 is further configured to:

if the first complaint result information indicates that the complaint of the service provider is failed, sending indication information of the complaint failure to the service provider;

receiving complaint feedback information sent by a service provider end in response to the indication information of complaint failure;

and if the complaint feedback information indicates that the service provider agrees with the first complaint result information of the complaint failure, taking the second target payment value as a final second target payment value.

In a possible implementation, a second complaint module 1012 is further included for:

if the complaint feedback information indicates that the service providing end does not agree with complaint result information of complaint failure, the complaint feedback information, the complaint information, the service characteristic information, all complaint feedback information and all payment complaint information are sent to the manual complaint equipment end;

receiving second complaint result information sent by the manual complaint equipment terminal;

if the second complaint result information indicates that the complaint of the service provider is successful, taking the payment value to be confirmed of the target order as information of the fee to be paid, and taking the total payment fee as the second target payment value;

and if the second complaint result information indicates that the complaint of the service provider is failed, taking the second target payment value as a final second target payment value.

The present application also provides an order processing apparatus, as shown in fig. 11, including:

a second information obtaining module 1101, configured to obtain a payment request initiated by a service provider for a target order and service feature information corresponding to the target order;

a second payment confirmation module 1102, configured to initiate payment confirmation information for the payment request to a service request end corresponding to the target order when it is determined that the payment request is abnormal based on the service feature information;

a second appeal receiving module 1103, configured to receive payment appeal information generated by the service request end in response to the payment confirmation information;

a second appeal forwarding module 1104, configured to send the payment appeal information to the service provider;

a second feedback receiving module 1105, configured to receive appeal feedback information sent by the service provider in response to the payment appeal information;

a second feedback confirmation module 1106, configured to determine a second target payment value to be paid to the service provider.

Fig. 12 illustrates a structure of an electronic device 1200 according to an embodiment of the present invention, where the electronic device 1200 includes: at least one processor 1201, at least one network interface 1204 or other user interface 1203, memory 1205, at least one communication bus 1202. A communication bus 1202 is used to enable connective communication between these components. The electronic device 1200 optionally contains a user interface 1203 including a display (e.g., a touch screen, LCD, CRT, Holographic (Holographic) or projection (Projector), etc.), a keyboard or a pointing device (e.g., a mouse, trackball (trackball), touch pad or touch screen, etc.).

The memory 1205 may include both read-only memory and random-access memory, and provides instructions and data to the processor 1201. A portion of the memory 1205 may also include non-volatile random access memory (NVRAM).

In some embodiments, the memory 1205 stores the following elements, executable modules or data structures, or a subset thereof, or an expanded set thereof:

an operating system 12051 containing various system programs for implementing various basic services and for handling hardware-based tasks;

the application module 12052 contains various applications, such as a desktop (launcher), a Media Player (Media Player), a Browser (Browser), etc., for implementing various application services.

In an embodiment of the present invention, the processor 1201, by calling a program or instructions stored in the memory 1205, is configured to:

a first target payment value is determined based on the payment complaint information.

Sending the payment appeal information to the service provider;

determining a second target payment value based on the appeal feedback information.

The computer program product of the order processing method and apparatus provided in the embodiment of the present application includes a computer readable storage medium storing a program code, and instructions included in the program code may be used to execute the method in the foregoing method embodiment, and specific implementation may refer to the method embodiment, which is not described herein again.

In particular, the storage medium can be a general-purpose storage medium, such as a removable disk, a hard disk, or the like, and the computer program on the storage medium, when executed, can perform the order processing method described above.

It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the system and the apparatus described above may refer to corresponding processes in the method embodiments, and are not described in detail in this application. In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. The above-described apparatus embodiments are merely illustrative, and for example, the division of the modules is merely a logical division, and there may be other divisions in actual implementation, and for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or modules through some communication interfaces, and may be in an electrical, mechanical or other form.

The modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a non-volatile computer-readable storage medium executable by a processor. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. An order processing method, comprising:

2. The order processing method of claim 1, wherein the payment complaint information includes at least one of the following types of complaint information:

3. The order processing method of claim 2, wherein determining the first target payment value based on the payment complaint information comprises:

4. The order processing method of claim 2, wherein determining the first target payment value based on the payment complaint information comprises:

5. The order processing method of claim 2, wherein determining the first target payment value based on the payment complaint information comprises:

6. The order processing method according to claim 1, wherein the service characteristic information includes first route information on completion of the travel of the target order by a service provider;

the determining that the payment request is abnormal based on the service characteristic information comprises:

7. The order processing method according to claim 6, wherein the initiating payment confirmation information for the payment request to a service request terminal corresponding to the target order comprises:

8. The order processing method according to claim 6, wherein the service characteristic information further includes second route information traveled by a service request terminal for the target order;

9. The order processing method according to claim 8, wherein the initiating payment confirmation information for the payment request to a service request terminal corresponding to the target order comprises:

10. The order processing method according to claim 1, wherein the service characteristic information includes an origin corresponding to the target order and a destination corresponding to the target order;

11. The order processing method according to claim 10, wherein the initiating payment confirmation information for the payment request to a service requesting end corresponding to the target order comprises:

12. The order processing method according to claim 11, wherein the third feedback page information further includes input box information indicating a reason for inputting the detour.

13. The order processing method according to claim 1, further comprising:

sending the payment appeal information to the service provider;

determining a second target payment value to be paid to the service provider based on the appeal feedback information.

14. The order processing method of claim 13, wherein determining the second target payment value based on the appeal feedback information comprises:

and if the new payment appeal information indicates that the service request end does not agree with the appeal feedback information, sending the new payment appeal information to the service providing end, and returning to the step of receiving the appeal feedback information sent by the service providing end in response to the payment appeal information.

15. The order processing method as claimed in claim 14, wherein the payment appeal information includes the total payment fee;

determining the first target payment value based on the payment appeal information, including:

the method further comprises the following steps:

16. The order processing method according to claim 14, further comprising:

if the first payment abnormal responsibility information indicates that a service providing end is responsible, determining the first target payment value based on the latest payment appeal information and the payment information of the payment request, and setting the second target payment value to be equal to the first target payment value;

17. The order processing method according to claim 16, further comprising:

18. The order processing method according to claim 17, further comprising, after determining that the second payment abnormality responsibility information indicates that a service provider is responsible and determining a second target payment value:

and if the first complaint result information indicates that the complaint of the service provider is successful, taking the total payment as the second target payment value.

19. The order processing method according to claim 18, further comprising:

20. The order processing method according to claim 19, further comprising:

if the second complaint result information indicates that the complaint of the service provider is successful, taking the total payment cost as the second target payment value;

21. An order processing method, comprising:

sending the payment appeal information to the service provider;

22. An order processing apparatus, comprising:

23. An order processing apparatus, comprising:

24. An electronic device, comprising: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium communicating via the bus when the electronic device is operating, the processor executing the machine-readable instructions to perform the steps of the method according to any one of claims 1 to 21.

25. A computer-readable storage medium, having stored thereon a computer program which, when being executed by a processor, is adapted to carry out the steps of the method according to any one of claims 1 to 21.